The One Identity Manager database is updated automatically by the Configuration Wizard. This procedure may take some time depending on the amount of data and system performance.
The Configuration Wizard performs the following steps:
-
Prepare the update.
NOTE: This step is performed only when updating a database that has at least One Identity Manager version 8.2.
This runs through the various phases for preparing the database update. This step-by-step preparation is intended to ensure that users are informed about the upcoming update and that processes can be terminated in a targeted manner. Alternatively, you can start the database update immediately. This skips the preparation phases.
These are the phases:
-
Normal operation mode: The database is in normal operating mode. The update process has not yet been initiated.
-
Updating information: All database users are informed about the upcoming update. The system does accept anymore processes. The preparation phase is displayed in the program's status bar.
-
Preparing update: New users cannot log in to the database anymore. All running processes will still be completed. If this is taking a long time, check the Job queue and the DB queue for processes. The preparation phase is displayed in the program's status bar.
-
Running update: The database is ready for updating. The update can start. The preparation phase is displayed in the program's status bar.
-
Updating the One Identity Manager schema.
Before the schema update, the Configuration Wizard checks the database. Error messages are displayed in a separate window. The errors must be corrected manually. The schema update cannot be started until these are resolved.
All the tables, data types, and database procedures that are required are loaded into the database by the schema update. When a migration package is imported into a One Identity Manager database, the following operations are carried out:
Table 24: Operations on importing a migration package
|
Paste |
If the object is not found in the target database, a new object is created with the key values. |
|
Refresh |
If the object is found in the target database, the object is updated. |
|
Delete |
Objects that are no longer needed are deleted. |
During a schema update, calculation tasks are queued in the database. These are processed by the DBQueue Processor.
During a schema update with the Configuration Wizard, the migration date and the migration status are recorded in the transport history of the database.
-
Compiling the system.
Scripts, templates, and processes are declared in the database. The System user authentication module with the specified system user is used for compilation.
-
Uploading files for automatic software update.
In order to distribute One Identity Manager files using the automatic software updating mechanism, the files are loaded into the One Identity Manager database.
-
Migrating synchronization projects.
A process that migrates all existing synchronization project is queued in the Job queue. This updates the One Identity Manager schema and applies automatic patches.
NOTE: Synchronization and provisioning processes are deferred until migration is complete. You can adjust the deferral time using the Common | Jobservice | RedoDelayMinutes configuration parameter.
-
Finalizing the update.
Processes queued by the schema update are in the final stage of processing. Finally, the database is switched back to normal operating mode.
Related topics
IMPORTANT: Test changes in a test system before you install a hotfix in a productive system.
Hotfix packages contain:
-
Transport packages that contain changes to the default configuration, such as templates, scripts, or processes in the One Identity Manager database
If you receive a transport package using a hotfix package, use the Database Transporter program to update the One Identity Manager database.
NOTE: If other configuration customizations are to be transferred to a One Identity Manager database in addition to a hotfix package, you can create a cumulative transport package to do this and, by using the Database Transporter, import the transport package into the target database.
-
Modified files, such as *.exe or *.dll
Hotfix packages that contain modified files are deployed as a Zip file. Unpack the Zip file and use the Software Loader to import the modified files into the database. The files are distributed to the workstations and servers by automatic software update. If you do not use automatic software update, update the workstations and servers manually.
Detailed information about this topic
You can display the contents of a transport package with the Database Transporter before you import.
NOTE: Always start the Database Transporter on an administrative workstation.
To display the contents of a transport package
-
Start the Launchpad and log in to the One Identity Manager database.
-
In the Change & Extend view, select the Transport custom modifications entry and click Start.
This starts the Database Transporter program.
-
Select Show transport file.
-
Select the transport package file browser and click Open.
-
Click Next on the Select transport file page.
-
The contents of the transport file are displayed on the Show transport file page.
-
To display the sequence in which the objects are imported
-
Click + to select an entry in the transport file and select Sort in import order from the context menu.
-
Click OK and enter the connection credentials for the database. This step is only required when you established the first in the order.
The order in which the entry's objects are imported into the database is found.
-
Repeat this step for all other entries for which you want to determine the import order.
-
To display the objects required for an import in the target environment, select the entry for the .xml file and select Show required objects from the context menu.
Objects that are dependent on another object that is not part of the transport package are highlighted.
-
To end the program, click Finish on the last page.
TIP: You can start the import of the transport package from display mode. On the Show transport file page, click the name of the transport package and use the Import context menu.
Related topics
IMPORTANT: Test changes in a test system before you install a hotfix in a productive system.
NOTE:
-
Use a copy of the production database for testing.
-
You can display the contents of a transport package with the Database Transporter before you import.
-
To import transport packages with the Database Transporter, users require the Transport_Import program function.
-
Start Database Transporter on an administrative workstation.
-
The database is set to single-user mode for the duration of the import. Close as many existing connections to the database as possible before starting the import. It is not mandatory to close the One Identity Manager Service connections. However, ensure that there are no processes running when the import is going to start.
-
When you import a transport package with schema extensions, the database is set to maintenance mode. Objects cannot be processed in the database during this time.
-
When you import a transport package with the Database Transporter, the import date and description, the database version, and the transport package name are recorded in the transport history of the target database.
To import a transport package
-
Start the Launchpad and log in to the One Identity Manager database.
-
In the Change & Extend view, select the Transport custom modifications entry and click Start.
This starts the Database Transporter program.
-
Select Import transport file on the home page.
-
On the Select the database connection page, check the One Identity Manager database connection data and change it if necessary.
-
Select the transport package file browser and click Open.
-
Specify your import options on Select transport file.
-
Create an import log file: Enable this option to create a log file for the data import. The log file is saved in the output directory of the transport file.
-
Import objects singly and ignore errors: Enable this option to import objects individually. Errors, which might occur during importing are ignored and displayed when importing is complete. If you do not enable this option, the import procedure is canceled when errors occur.
-
Ignore default data differences: Enable this option to ignore changes to default data. If you do not enable this option, the import procedure is canceled if changes to default data are included.
-
Import steps and import progress are displayed on the Importing transport data page. The import procedure can take some time. Calculation tasks are queued for the DBQueue Processor on termination.
NOTE: During import, if the expected value does not match with the actual value in the database, the Merge conflict dialog opens. For each conflict, you must decide which value is committed to the database.
-
If you want to keep database value, enable Current database value.
-
If you want the value from the transport package to overwrite the database value, enable Transport value.
-
If changes have been made to the system configuration, for example, processes, or scripts imported, you have to compile the database after the tasks have been processed. Compilation is started automatically once importing is complete.
-
To end the program, click Finish on the last page.
NOTE: Use the 
button to save any errors that occur whilst importing.
Related topics
