When a schema is installed with the Configuration Wizard, migration date and migration revision are recorded in the database's 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
The System information tab gives you an overview of your system configuration. Have this information available when you contact support.
|
NOTE: This report is sent once a month to One Identity after you have enabled vendor notification. |
|
NOTE: Any compiler errors and warnings are recorded during compilation. You can view compiler errors and warnings after compilation is complete.
|
To display messaging during compilation and saving
In addition, a more detailed description of the error is displayed. Configure the amount of information to be displayed using the options in the error message window. Open the configuration with the button and enable or disable the options you want.
Option | Meaning |
---|---|
Show previous errors |
Specifies whether all previous errors that lead to the current error, should also be shown. |
Show One Identity error numbers |
Specifies whether internal error numbers are shown. |
Show error positions |
Specifies whether error position are also shown in the program code. |
Wrap long lines |
Specifies whether long error messages are wrapped. |
Show only user relevant |
Specifies whether all error messages or only message classified as "user relevant" are shown. |
Show asynchronous calls | Specifies whether error messages in asynchronous method calls are shown. |
Show crash report | Specifies whether error messages from the crash recorder are shown. |
|
NOTE: The button Send as mail creates a new email message in the default mail program and copies over the error text. |
If errors occur, these are shown immediately in a separate log window during compilation.
Figure 10: Error Message Log
The consistency check provides different tests for analyzing data objects and to ascertain the current state of their data. You can use your own tests as well as the predefined one and repair the data if necessary.
|
NOTE: You should run a consistency check at regular intervals or after major changes to the system configuration. |
You can run consistency checks in the Manager and in the Designer. Database tests are run in their entirety in the Manager and the Designer. In the case of table tests and object tests in the Manager, the application model is tested and in the Designer, the system model is tested.
|
NOTE: It is recommended to run consistency checks with an administrative system user. Consistency checks of type "Object test" are always run in user context. If the user does not have any permissions for a certain object, errors may not be identified or repairing errors may fail. |
To run a consistency check
During start up, One Identity Manager schema table definitions are loaded and database objects are made available for testing.
|
NOTE: To exclude individual test objects from the test, select them in the Consistency Editor list view and label them using Disable in the context menu before starting the test. |
Select the test object you want to test in the list view and start the test from the context menu item Verify.
|
TIP: Use SHIFT + SELECT or CTRL + SELECT to multi-select test objects for testing. |
After restoring a One Identity Manager database from a database backup, no more DBQueue Processor tasks are handled.
If the SQL Server in running on a virtual machine and the virtual machine is suspended, it is possible that no more DBQueue Processor tasks are handled after restarting the virtual machine.
You will get the following message in the Configuration Wizard when updating One Identity Manager:
Cannot enable broker because of other users are active.
The SQL Server Service Broker may not be reacting because of initializing the DBQueue Processor. The Service Broker is implemented for DBQueue Processor communications.
Execute the following steps in the database using a suitable query tool.
exec QBM_PWatchDogPrepare 1
go
exec QBM_PDBQueuePrepare 1
go
select *
from sys.sysprocesses p
where dbid = DB_ID()
and spid <> @@SPID
If there are still sessions active, they must be closed first.
alter database <database name> set NEW_BROKER
go
alter database <database name> set enable_broker
go
exec QBM_PDBQueuePrepare 0,1
go
exec QBM_PWatchDogPrepare
go
|
NOTE: If you restore a test or development database from a backup of another One Identity Manager database, these steps are executed by the Database Compiler. Manual execution of the steps is not necessary in this case. For more information, see Appendix: Creating a One Identity Manager Database for a Test or Development Environment from a Database Backup. |
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy