To install One Identity Manager 9.3 for the first time, follow the installation instructions in the One Identity Manager Installation Guide. For detailed instructions about updating, see the One Identity Manager Installation Guide.
IMPORTANT: Note the Advice for updating One Identity Manager.
Take note of the following information when updating One Identity Manager.
One Identity Manager version 9.3 does not support the Data Governance Edition. If you want to update a database on which the Data Governance module is installed, you must uninstall this module before you can perform the update. For more information about how to remove modules, see the One Identity Manager Installation Guide.
Evaluate changes in a test system before you load a migration package into a production system. Use a copy of the production database for testing.
Ensure that the administrative system user, who is going to compile the database, has a password before you update the database to version 9.3. Otherwise the schema update cannot be completed successfully.
For One Identity Manager databases on SQL Servers, it is recommended, on performance grounds, that you set the database to the Simple recovery model for the duration of the schema update.
During the update of a One Identity Manager database to version 9.3, different columns that were already semantically defined as mandatory fields become physical mandatory fields.
During the schema update with the Configuration Wizard, errors may occur due to inconsistent data. The update quits with an error message.
<table>.<column> must not be null
Cannot insert the value NULL into column '<column>', table '<table>'; column does not allow nulls.
UPDATE fails
Check and correct data consistency before updating a One Identity Manager database. In the add-on for the Configuration Module on the installation medium, a test script (\SDK\SQLSamples\MSSQL2K\30374.sql) is provided. In case it fails, correct the data and restart the update.
One Identity Manager uses In-Memory OLTP (Online Transactional Processing) for memory-optimized data accesses. The database server must support Extreme Transaction Processing (XTP). If XTP is not enabled, the installation or update will not start. Check whether the SQL Server property Supports Extreme Transaction Processing (IsXTPSupported) is set to True.
The following prerequisites must be fulfilled to create memory-optimized tables:
A database file with the file type Filestream data must exist.
A memory-optimized data filegroup must exist.
The Configuration Wizard checks whether these prerequisites are fulfilled before the One Identity Manager database can be installed or updated. The Configuration Wizard offers repair methods for creating the database file and database group.
During the update, calculation tasks are queued in the database. These are processed by the DBQueue Processor. Processing calculation tasks may take some time depending on the amount of data and system performance.
This is particularly the case if you save large amounts of historical data in the One Identity Manager database, such as change data or data from process handling.
Therefore, ensure that you have configured an appropriate procedure for archiving the data before you update the database. For more information about archiving data, see the One Identity Manager Data Archiving Administration Guide.
For the period of the update, the database is set to single user mode. Close all existing connections to the database before starting the schema update.
You may experience problems activating single-user mode when using database mirroring.
After the update has completed, the database switches automatically to multi-user mode. If this is not possible, you receive a message in which you can manually switch to multi-user mode.
Once this version has been installed, users that need to access the REST API in the application server require the Enables access to the REST API on the application server (AppServer_API) function. Assign this program function to the users. For more information, see the One Identity Manager Authorization and Authentication Guide.
Use the Modules\QBM\dvd\AddOn\SDK\SQLSamples\MSSQL2K\SDK_Remove_Rights_on_msdb.sql SDK script to remove permissions that are no longer required for the msdb database.
It is not recommended to perform an upgrade of the existing modules to a new One Identity Manager version and install additional modules at the same time. This may cause dependencies between modules to be constructed incorrectly. First update the existing modules to the new One Identity Manager version. Then restart the Configuration Wizard and install the additional modules.
IMPORTANT: Note the Advice for updating One Identity Manager.
IMPORTANT: One Identity Manager version 9.3 does not support Data Governance Edition. If you want to update a database on which the Data Governance module is installed, you must uninstall this module before you can perform the update. For more information about how to remove modules, see the One Identity Manager Installation Guide.
NOTE: This One Identity Manager version contains significant updates that do not allow the use of automatic software updates for Job servers and web applications. Therefore, update your Job servers and web applications manually.
To update an existing One Identity Manager installation to version 9.3
End and uninstall the web applications.
Stop the One Identity Manager Service on all Job servers.
Run all the consistency checks in the Designer in Database section.
In the Designer, start the Consistency Editor with the Database > Check data consistency menu item.
In the Test options dialog, click 
Under the Database node, enable all the tests and click OK.
Start testing with the Consistency check > Run menu item.
All the database tests must be successful. Correct any errors. Some consistency checks offer repair options for correcting errors.
Update the administrative workstation, on which the One Identity Manager database schema update is started.
Run the autorun.exe program from the root directory on the One Identity Manager installation medium.
Change to the Installation tab. Select the Edition you have installed.
Click Install.
This starts the installation wizard.
Follow the installation instructions.
IMPORTANT: On the Installation Settings page, select the directory for your current installation as the installation directory. Otherwise, the components are not updated and a new installation is created in the second directory instead.
Make a backup of the One Identity Manager database.
Update the One Identity Manager database. Start the on the administrative workstation and follow the instructions.
Select a user who has at least administrative permissions for the One Identity Manager database to update the One Identity Manager schema with the Configuration Wizard.
Use the same user as you used for initially installing the schema.
If you created an administrative user during schema installation, use that one.
If you selected a user with Windows authentication to install the schema, you must use the same one for updating.
Reinstall the web applications.
Update all program and service components on all Job servers. Use the installation wizard.
Start the One Identity Manager Service on all Job servers.
Update the other workstations. You can use the automatic software update method for updating existing installations.
To update synchronization projects to version 9.3
If you have set up synchronization projects for connecting cloud applications in the Universal Cloud Interface, update the target system schema in these synchronization projects using the Synchronization Editor.
Any required changes to system connectors or the synchronization engine are made available when you update One Identity Manager. These changes must be applied to existing synchronization projects to prevent target system synchronizations that are already set up, from failing. Patches are made available for this.
NOTE: Some patches are applied automatically. A process that migrates all existing synchronization project is queued in the Job queue to do this. To run the process, the One Identity Manager Service must be started on all synchronization servers.
Check whether the process DPR_Migrate_Shell has been started successfully.
If the patch cannot be applied because the target system could not be reached, for example, you can manually apply it.
For more information, see Applying patches to synchronization projects.
|
|
CAUTION: Patches do not alter custom changes in synchronization projects. This means that conflicts may occur if patches are applied to synchronization projects that have been customized. It may cause loss of data. Before you apply a patch
|
NOTE: If you update existing synchronization projects, the connection parameters from the default variable set are always used. Ensure that the variables in the default variable set contain valid values.
To apply patches
In the Synchronization Editor, open the synchronization project.
Select the Edit > Update synchronization project menu item.
In Available patches, select the patches you want to apply. Multi-select is possible.
In Details - Installation summary, all patches are displayed in order of installation.
Click Apply selected patches.
Enter any user input as prompted.
Use the patch log to check whether customization need to be reworked.
If required, rework customizations in the synchronization configuration.
Run a consistency check.
Simulate the synchronization.
(Optional) Activate the synchronization project.
NOTE: A patch does not take effect until the changes associated with it are saved in the database. If consistency check or simulation errors occur that cannot be corrected, you can dismiss the patch changes by reloading the synchronization project without saving the changes.
For detailed information about updating synchronization projects, see the One Identity Manager Target System Synchronization Reference Guide.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center
