Before the installation or update of the One Identity Manager database starts, the Configuration Wizard checks the settings of the database server and the database required for the installation and operation of the One Identity Manager database. For more information, see Settings for the database server and the One Identity Manager database on a SQL Server.
Some of these settings are corrected by the Configuration Wizard. If the correction is not possible, a corresponding message is issued in Configuration Wizard. In this case, correct the errors manually.
Table 41: Messages in the Configuration Wizard before starting the installation or update of a database
|
The database collation setting is not valid. SQL_Latin1_General_CP1_CI_AS is required. |
Set the Sort order (collation) database property to the value SQL_Latin1_General_CP1_CI_AS. |
|
The migration cannot be carried out because a replication is currently running. |
For more information, see Database errors migrating a database to SQL Server AlwaysOn availability groups. |
|
The value in DialogDatabase.DataOrigin is invalid. Start by running a database compilation. |
Use the Database Compiler to regenerate a database ID and to compile the database. All parts of the database need to be recompiled. Make sure that all the code snippets and all processes are marked. |
|
The database has no data-file group for in-memory OLTP. |
Use the repair method to create a data-file group. |
|
The database has not defined a file in the data-file group for in-memory OLTP. |
Use the repair method to create a database file. The file is created in the directory of the data file (*.mdf). |
|
The SQL Server has not activated in-memory OLTP. |
Set the Is XTP Supported database server property value to True. |
|
The Arithmetic Abort enabled database property is not enabled. |
Set the Arithmetic Abort enabled database property value to True. |
|
The Quoted Identifiers Enabled database property is not activated. |
Set the Quoted Identifiers Enabled database property value to True. |
|
You cannot run a migration if the recovery model is not Simple. |
Set the Recovery model database property value to Simple. |
|
The transaction mode cannot be set because other users are active. |
End the connections of other users to the database. |
|
The Job queue and/or the DBQueue is not empty. Refer to the documentation for additional information and suggested solutions for this test. |
Ensure that the Job queue processes and task in the DBQueue have been processed before starting the update. Use the Job Queue Info program to monitor process handling. For more information, see the One Identity Manager Process Monitoring and Troubleshooting Guide.
The Configuration Wizard has the option to ignore this message. Only use this option in test or development environments. By updating the database, modifications may be made that result in not being able to handle the processes anymore. |
|
The viadmin system user must have a valid password that is not empty. |
Make sure that the system user has a valid password. |
|
The database has the status 'Initialmigration'. Therefore the Configuration Wizard cannot be run. |
The initial schema installation of the database was not completely finished. This may have different reason. For example, the database or failover cluster could not be reached during the schema installation.
Create a new database and rerun the initial schema installation. For more information, see Installing and configuring a One Identity Manager database. |
|
The SQL Server login specified in QBMDBPrincipal.LoginName does not exist. |
Use the repair method to create the SQL Server login. |
Possible problems
-
The data does not start updating. The Configuration Wizard shows the message:
The migration cannot be carried out because a replication is currently running.
-
The following error occurs during a One Identity Manager schema update:
Database error 1468: The operation cannot be performed on database "<database name>" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group. ALTER DATABASE statement failed.
Cause
The database is part of an AlwaysOn availability group.
Solution
-
Remove the database from the AlwaysOn availability group.
-
Update the One Identity Manager schema.
-
Put the database back into the AlwaysOn availability group.
Problem
When email notifications are generated in processes, any error messages are logged.
The configuration parameter '{0}' still contains the default value '{1}'. Adjust this value to suit your system environment.
The configuration parameter '{0}' does not exist or is not set. It is a mandatory value and must be configured in your system.
Use the Designer to configure the parameter '{0}' or contact your administrator.
Cause
One Identity Manager sends email notifications about various actions taken within the system. One Identity Manager email notification system is not completely configured.
Solution
Check the configuration parameters for the email notification system. To do this, use the email configuration wizard.
To start the email configuration wizard in the Launchpad.
-
In the Launchpad, in the Configuration section, select Configure email connection.
-
Click Run.
To start the email configuration wizard in the Designer.
-
In the Designer, in the Base data > General > Configuration parameters category, select the Common | MailNotification configuration parameter.
-
In theConfiguration Parameter Editor, click ... next to the Value field.
Detailed information about this topic
You can remove modules from the One Identity Manager database that you no longer require in your system.
IMPORTANT:
-
By removing a module, you lose all the data that goes with it. So it is important to make a backup of the One Identity Manager database before removing any modules.
-
In certain circumstances, dependencies to other modules may be deleted by removing a module. Therefore, update the One Identity Manager schema after removing a module.
-
Other tests may be necessary after removing a module. Remove the module in your test environment first and test the One Identity Manager functionality thoroughly. Make sure to also check any custom adaptations that may use functions in the modules that have been removed.
To remove a module
-
Terminate all web applications using the Internet Information Services (IIS) Manager.
-
Close all One Identity Manager tools except for Job Queue Info.
-
Wait until all processes have stopped. You can do this using the .
-
Stop all One Identity Manager Services through the services manager.
-
Stop all application servers using the IIS Manager.
-
Wait until all DBQueue Processor tasks have completed. You can do this using the .
-
Close Job Queue Info.
-
Start a suitable program for running SQL queries.
IMPORTANT:
-
Select a user that you use for migrating the database to run the SQL queries.
-
Run the following steps separately using a suitable program for running SQL queries.
Test the output of the query after each step. The output provides additional tips for removing a module.
-
Activate single-user mode for the One Identity Manager database.
exec dbo.QBM_PSingleUserRequest @@spid
-
Delete all triggers in the database.
exec QBM_PTriggerDrop '%', @force = 1
-
Delete all constraints in the database.
exec QBM_PConstraintFKDrop '%','%','%'
-
Delete the module you no longer need.
exec QBM_PModuleRemove '<3-char module abbreviation>'
Example:
declare @ModulesToRemove varchar(100) = 'SAP' + char(7)
+ 'SHR' + char(7)
+ 'SBW' + char(7)
+ 'SAC' + char(7)
exec QBM_PModuleRemove @ModulesToRemove
go
-
If you delete the Business Roles Module (RMB), you must also delete the entries in the OrgRoot table.
exec QBM_PDeleteDeep '<Key><T>OrgRoot</T><P>3031e9af-6a53-4876-bbfb-0f7fbf264131</P></Key>
-
End single-user mode for the One Identity Manager database.
exec dbo.QBM_PSingleUserRelease @@spid
-
Update the One Identity Manager schema with the Configuration Wizard. Select all remaining modules for updating.
-
If support sent you hotfixes for this version, then these hotfixes must also be reinstalled.
-
Start the application server, the One Identity Manager Services and the web applications.
