Before you run a consistency check you should set the test options you require.
|
NOTE: You can change the test options at anytime using the menu item Consistence check | Options.... |
Figure 11: Specifying Test Options
Icon | Meaning |
---|---|
Tests are grouped by themes. | |
Tests are grouped by types (database, tables , objects). | |
Tests are displayed as a list. | |
Tests are grouped by module association. | |
Tests are displayed with severity level "Error". | |
Tests are displayed with severity level "Warning". | |
Tests are displayed with severity level "Information". |
Test options are separated into test at database level, table level and object level. There are already predefined tests available. Use user defined tests to run your own tests. You can use the scripts from the script library for these tests. All the scripts from the library that use the following calling syntax are available:
Database test:
Public Sub Methodname (ByRef con As IConnection)
Table test:
Public Sub Methodenname (ByRef dbTable As ITableDef)
Object test:
Public Sub Methodname (ByRef dbObject As ISingleDBObject)
During the consistency check, the number of tested objects and the test status is updated in the editor’s list view. Once the test has completed, any error messages are outputted to the Consistency Editor error log.
Icon | Meaning |
---|---|
Shows all error messages. | |
Only shows errors in the selected objects list view. | |
A full description of the error is shown in a separate window. | |
Fixes the error. | |
Saves the error messages in a log file. | |
Deletes the error messages. |
|
TIP: Double-click an entry and a dialog box appears with a detailed description of the error. |
|
NOTE: This Consistency Editor repair function is only available if the current user is authorized to use the function "Option to start automatic consistency check repair function (Common_ConsistencyCheck_Repair)". |
The button Repair appears in the Consistency Editor error log if it is possible to repair the error automatically.
To repair incorrect data
|
TIP: Use SHIFT + CLICK or CTRL + CLICK to select multiple entries for repair. |
The error is corrected directly in the
|
NOTE: When you repair templates, dependent objects may also be changed when the template is rerun. In certain circumstances, this might in result in a large number of objects being changed, saved and even processes being generated. |
The One Identity Manager database must be compiled after changes to configuration data. The database compilation is started immediately from the Configuration Wizard or the Database Transporter after a migration package or a customer’s complete configuration package has been imported. Use the Database Compiler to compile the One Identity Manager database after importing hotfixes or when changes have been made to processes, scripts, formatting rules, object definitions, task definitions, and preprocessor relevant configuration parameters.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy