To be able to use separate session for reading and writing to different databases servers, you need to adjust the connection data of the Data Source property.
The Data Source property can contain a pipe (|) delimited server list. The first server specified is the primary server used for write access. All other servers are read-only copies with read access only. The prerequisite for this is that the database name and the credentials on the secondary servers are identical to the primary server.
NOTE: In the connection dialog you can reach the property through the Options > Advanced options setting.
The internal physical read sessions are distributed randomly over the read-only copies and the primary server. With one primary server and two secondary servers, the primary server receives approximately 1/3 of the connections for read operations.
NOTE: The connection pool does not open a new connection for each operation. If no new parallel requests come, all requests run over the same connection and therefore on the same server.
The procedure relies on replication taking place between the servers and the data always being up to date in the copies as well.
Related topics
During a schema installation or schema update using the Configuration Wizard, the migration date and migration version are recorded in the database transport history.
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 display transport history
To obtain an overview of the system configuration
-
Start the Designer or the Manager and select the Help > Info menu item.
The System information tab provides an overview of your current system administration and the installed modules with their versions.
IMPORTANT: You will need to provide this information if you contact the Support Team.
NOTE: If you have enabled vendor notification, this report is sent once a month to One Identity.
Related topics
Problem
When logging in to a One Identity Manager tool, the following error message appears:
[810284] Failed to authenticate user.
[810015] Login for user {0} failed.
[810017] Wrong user name or password.
Possible cause
-
The specified user is not supported by the selected authentication module.
-
The specified password is incorrect.
-
The user account used for the login is locked.
-
The identity used to log in is temporarily or permanently deactivated.
-
The identity used for log in is classified as a security threat.
Possible solutions
-
Check your login credentials.
-
Check if the identity used to log in is locked. In the Manager, use the following menu items in the Identities category.
-
Inactive identities: This displays temporarily and permanently deactivated identities.
-
Security incidents: This displays the identities that are classified as security threats.
-
Locked identities: This displays identities that have exceeded the maximum number of failed logins and have been locked out.
-
Check if the system user used to log in is locked. Locked system users are displayed in the in the Permissions > System users > Locked system users category.
For more information about deactivated identities, see the One Identity Manager Identity Management Base Module Administration Guide.
You can reset the passwords of identities and system users who have been locked in Password Reset Portal. This unlocks the identities and system users again. For more information, see the One Identity Manager Web Portal User Guide and the One Identity Manager Web Application Configuration Guide.
Problem
When logging in to a One Identity Manager tool, the following error message appears:
[810374] You are not allowed to run this application.
Cause
The One Identity Manager tools can only be started if the user has the relevant program function permissions. You are logging in with a system user ID that does not have the required permissions to start the program.
Possible solutions
For more information about the One Identity Manager authentication modules, permissions groups and application roles, as well as program functions, see the One Identity Manager Authorization and Authentication Guide
