Professional Documents
Culture Documents
Date: 2014-05-09
ISPA Database
Technical Administration Manual
This document describes the installation and configuration of the ISPA database IDB.
Valid from:
ISPA DB 1.2.1
BMW Group Page 2
List of Contents
1 Introduction ................................................................................................................................ 4
6 Restore .................................................................................................................................... 23
9 Troubleshooting ........................................................................................................................ 37
1 Introduction
The "ISPA Database Technical Administration Manual" describes the installation, configuration and
administration of the IDB. The document is addressed to the technical administrator of the ISPA
system in the workshops and sales companies. The following topics are covered:
Problem handling.
These hint / caution has to be read carefully, because otherwise problems can be caused.
Areas marked with this symbol provide you with additional information.
Blu-ray Disc provided with all installation packages for the setup of a new dealer (disc one of
four ISPI Next Applications).
NAS/Shared Storage with installation packages provided online via the ISPI Admin Client.
2 Installation of IDB
The IDB can be installed on the ISPA Hub or another external device. The installation described here,
creates a new and empty database together with the required Oracle Server 11gR2.
2.1 Requirements
The ISPA Hub or external database server hardware and including the operating system is
installed. For technical details please refer to the ISPI Planning Guide.
All important Windows updates have to be installed especially the updates for .Net.
The files listed in the following table are required for the installation. Please make sure, that
these files are available on your NAS / shared storage. The files can be provided from an
offline installation medium (Blu-ray Disc) or downloaded via ISPI Admin Client from the central
BMW systems.
e.g. BMW_ISPI_TRAC_OracleDBS_11.2.0.1.exe
ISPA DB BMW_ISPI_TRAC_IDB_<version>.msi
e.g. BMW_ISPI_TRAC_IDB_1.2.1.0.msi
2.2 Preparation
Before starting the installation you have to carry out the following tasks on the target
system:Login to your Windows OS with your administration user
Click Create.
Click Close.
Click on Add....
Type in shutdown r t 0.
Press Return.
If you want to store the backups of your IDB on an external device within your network, you have to
create a network share on this device.
Select the destination folder where you want to store the backups.
Share this folder to the network with write access for the user you have created before.
Later on during installation of the IDB, this information is required to configure the backup
parameters.
Copy both install packages for ISPA Oracle DBS and ISPA DB (see table in chapter 2.1) from your
NAS/Shared Storage into a temporary local folder on the ISPA Hub or your external database server.
During the installation you may have to accept User Access Control and Firewall
messages. In order to install IDB correctly, you must allow every access.
Start the install package for ISPA Oracle DBS and wait until the extraction has completed:
When the file extracting has completed without any error, the window will be closed. Otherwise you will
receive an error message.
Now start the install package for ISPA DB (see table in chapter 2.1) and the required files will be
copied to the target directory. Then the installation starts.
If the installation does not start automatically, please refer to chapter 9.1
Troubleshooting: Installation does not start.
Select your preferred Language for the IDB installation and the IDB Administration dialog and
click on Continue.
In the next step, you must not change the preconfigured paths to integrate the IDB into the default
BMW folder hierarchy.
If you change the preconfigured paths, the ISPI Admin Client cannot retrieve and upload
the log files of the IDB in case support is needed.
For the daily backups of your IDB you now have to configure the required parameters.
This can either be a local Dump path on your computer where the IDB is installed, or the path to an
external device within your network (UNC path).
To prevent a data loss, it is recommended to use a network share that is backed up also
to offline media. In case of loss of the hardware (local server or network share) the
backups might be lost also.
After having selected the target directory, it will be displayed in the field left to the Browse
button:
UNC path
To store the backup files on an external device within your network, click on the radio
button for the UNC path and define the required parameters:
UNC path the full path to the network share you have defined in chapter
2.2.4 Create a Network Share for Backup (optional) (required)
UNC username the user you have defined on the target device with write
access to the network share (required).
UNC password the password defined for the UNC username (required).
After you have clicked on the Test button and not all required parameters have been
defined, the following hints will be displayed:
After having defined the UNC parameters you can test the connectivity with a click on the
Test button. If the test failed, the Test button will turn to red and an error message is
displayed:
Check the UNC parameters you have entered and try again, until the Test button turns to
green:
Accept or change the number of backups in Maximum of saved backups. The default and
minimum is 14.
You will need about 200 MB free space per backup in your target backup
directory. For instance you should have 2800 MB free space for the minimum
amount of 14 backups.
Define your backup configuration and confirm with a click on Continue and proceed with the
Oracle installation.
If you want to abort the IDB installation, click on Cancel and confirm the following
message with Yes:
The next screen will give you an overview, how long the installation will take.
Be sure, ORACLE and SCORE are checked. Otherwise please refer to chapter 9.3
Troubleshooting: ORACLE or SCORE are not checked.
The progress of the installation is displayed, and each installation step executed is recorded.
After the installation has been completed, a confirmation message will be displayed:
Then confirm with Close and the installation of the IDB is completed and the Installer window
can be closed.
After the installation of the IDB has been completed, two scheduled tasks are created to take
the daily database backups of your IDB.
If .NET messages are displayed, please refer to chapter 9.1.2 Troubleshooting: .NET
Error Messages.
If the Oracle installation did not complete successfully, please refer to chapter 9.4
Troubleshooting: Oracle Installation has not finished successfully.
When the installation has completed successfully, additionally an icon with the shortcut to the IDB
Administration tool is created on the desktop of the local machine:
Press the Windows Key and type task scheduler. The result should be:
1 2
Open Task Scheduler Library (1) and there you should find the folder IDB with the following
two tasks (2):
If these tasks are not available, please refer to chapter 9.5 Troubleshooting: Tasks were
not created.
To verify the Oracle Services have been created successfully, perform the following teps:
Press the Windows Key and type services. The result should be:
Select Services and check, whether the following Oracle Services are shown in the services
screen:
The Oracle Services with Status Running in the picture above have also to be in Status
Running on your ISPA Hub.
If these Oracle Services are not shown or are not in the correct status, please refer to
chapter 9.6 Troubleshooting: Oracle Services were not created.
For the Restore of an existing the creation of an empty database is NOT required.
To install a completely new and empty database, confirm with Yes to continue.
Be always sure, that you really want to create an empty database and delete the existing
data!
The progress of the creation of an empty database is always displayed on the screen. After
completion the following message is displayed:
When the empty database has been created successfully, continue with one the following
steps:
(1) If you use the ISPA Client (with or without DMS integration) and you want to start with an
empty database, continue to initialize and configure the IDB as described in chapter 9 of the
ISPA Client Technical Administration Manual.
(2) If you use ISPA Light and you want to start with an empty database, continue with the
initial configuration of ISPA Light as described in chapter 9 of the ISPA Light Technical
Administration Manual.
5 Creation of Backup
Sometimes it may be necessary to create an instant backup besides the automatically created
backups, e.g. if you have to setup a new server hardware or you plan to install updates.
To create an instant backup of the IDB, start the IDB Administration icon on your desktop.
Select the radio button Backup database and start the backup with a click on the button
Start Backup.
After the backup has been completed successfully, the backup is stored at the configured
backup destination and a confirmation message will be displayed:
Additionally check, whether the backup files will appear in the destination folder configured
or in the default folder %ProgramFiles%\BMW\ISPI\TRAC\IDB\SCORE) including the log
files (in .zip format).
If the backup has not been completed successfully, please refer to chapter 9.8
Troubleshooting: Creating a Backup has finished with errors.
6 Restore
The restore of an existing database might be necessary:
To restore your IDB from backup, start the IDB Administration icon on your desktop.
Select the radio button Import database and Browse for existing backups:
Select the backup you want to restore, usually the latest one:
After the import has completed successfully, a confirmation message will be displayed:
If the Import has not been completed successfully, please refer to chapter 9.7
Troubleshooting: Importing a Backup has finished with Errors.
The Fixup script is a maintenance utility that is included with the ISPA Client. It checks the database
and rebuilds all indices and views. If you have installed ISPA Full / ISPA Basic you have to run the
Fixup after each database import.
Enter the following command from a command line on the ISPA Hub:
C:\Program Files (x86)\BMW\ISPI\TRAC\ISPA-Client Starter\ISPAStartHub.exe
fcs tkpm fixup m b
After the Fixup has started successfully the following screen will be displayed:
You just need to run the Fixup once per database restore.
Otherwise if the Fixup did not complete successfully (with error messages) or does not
respond, please refer to chapter 9.10 Troubleshooting: Fixup has not completed
successfully.
Click on DB configuration:
The path configuration in frame (1) can be changed only after clicking the button Edit
Configuration.
The backup settings in frame (2) can be changed directly without Edit Configuration.
The path configuration consists of the categories Installation Path and Backup Path.
To possibility to change the installation path for Oracle and the IDB is reserved for Support
personnel only.
Otherwise changes may cause unpredictable results and the database is not longer
available for your ISPA system!
This can either be a local Dump path on your computer where the IDB is installed, or the path to an
external device within your network (UNC path).
To prevent a data loss, it is recommended to use a network share that is backed up also
to offline media. In case of loss of the hardware (local server or network share) the
backups might be lost also.
To change the backup path configuration proceed with the following steps.
Possible changes
adapt the existing configuration for the UNC path or the local Dump path.
To store the backup files on an external device within your network, the radio button for the UNC path
has to be activated and the required parameters have to be defined.
If you want to switch from Dump path to UNC path you have to create first the Backup
Share on a remote device within your network as defined in chapter 2.2.4 Create a
Network Share for Backup (optional).
UNC path the full path to the network share you have defined in
chapter 2.2.4 Create a Network Share for Backup (optional) (required)
UNC username the user you have defined on the target device with write access to
the network share (required).
UNC password the password defined for the UNC username (required).
After having changed or defined the UNC parameters, test the connectivity with a click on the
Test button.
Check the UNC parameters you have entered and try again, until the test is successful.
If you want to store the backup on your local computer, you can select or change the target
directory or define a new folder using the Browse button behind the Dump path:
After having selected the target directory, it will be taken over as local Dump path.
The Backup amount, i.e. the number of backups to be stored at the target location configured.
8 Update IDB
If there is a new version available for the IDB, perform the following steps to update your existing IDB.
For the correct name of the current msi-file and probable installation details please refer to the release
notes always provided with a new release.
Copy the install package for ISPA DB (see table in chapter 2.1) from your NAS/Shared
Storage into a temporary local folder on the ISPA Hub or your external database server.
During the installation you may have to accept User Access Control and
Firewall messages. In order to install IDB correctly, you must allow every access.
Now start the install package for ISPA DB (see table in chapter 2.1) and the required files will
be copied to the target directory. Then the installation starts.
If the installation does not start automatically, please refer to chapter 9.1
Troubleshooting: Installation does not start.
Confirm the Installation paths without any changes (recommended) with Continue:
Confirm the Backup Configuration (or probably change it) and confirm with Continue:
The progress of the update is displayed, and each installation step executed is recorded:
When the installation of the IDB Update is completed, confirm with OK and the Installer
window can be closed.
To check the correctness of the IDB Update installed, verify your IDB installation as described
in chapter 3 Verification of the IDB Installation.
9 Troubleshooting
If you have started the install package ISPA DB (see table in chapter 2.1) but the installation window
does not start, start the IDB-Installer.exe from path
%ProgramFiles%\BMW\ISPI\TRAC\IDB\IDB-Installer\.
During the ORACLE install process, you might be prompted with messages, that some parts of the
.NET Framework are not found.
In this case there possibly is no .NET Framework installed on the target system. If you are
running the installation under Windows Server 2012 you have to install the most recent .NET
version as a feature.
If the most recent .NET Framework is already installed and you are prompted, that some parts
of the .NET Framework 3.5 are not found (see figure below), you can ignore those messages
and click them away as often as they appear. They have no impact on a successful installation.
Oracle services are not created, if the Oracle installation has run into an error. Restart the Oracle
Services or restart your ISPA Hub. If this does not solve the problem, please contact your Support.
If the Fixup has not completed successfully, try to use another dump file. If it fails again, please
contact your Support.
Click Properties.
Click OK.
Click OK.
Now the IDB Administration starts for all users with administration rights.
To allow everybody to start backup or restore might cause less effort in administration.
But this may cause problems if done by unauthorized or untrained staff!
If the ORACLE listener does not start, there could be a misconfiguration in the listener.ora
configuration file.
%ENTERYOURIP% by your actual IP address of the ISPA Hub or your external database
server, where the IDB is installed on.
[USERNAME] by the Username Oracle has been installed with. Be sure that the
ORACLE_HOME is correct.
After you have entered the right information, save the template to listener.ora and copy it to
C:\BMW\IDB\Oracle\[USERNAME]\product\11.2.0\dbhome_1\NETWORK\ADMIN to replace
the existing listener.ora.