Define the valid test settings before you run a consistency check. Tests are performed at database, table, and object level. There are already predefined tests available. You can run your own custom tests.
To configure the settings for testing
-
Start Consistency Editor in the Designer or in the Manager by selecting Database | Check data consistency.
-
In the Consistency Editor toolbar, click 
.
-
Enable the test that is to be run and adjust the test settings further if necessary.
- Click OK.
The tests are grouped according to different criteria.
Table 36: Meanings of the icons used for test settings
 |
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 with Error severity are displayed. |
 |
Tests with Warning severity are displayed. |
 |
Tests with Information severity are displayed. |
Use user-defined tests to run your own tests. You can use the scripts from the script library for these tests. All scripts in the script library are provided for custom tests. The method call of these scripts corresponds to the following syntax.
Database test
Public Sub Methodname (ByRef con As IConnection)
Public Sub Methodname (ByVal con As IConnection)
Table test
Public Sub Methodname (ByRef dbTable As ITableDef)
Public Sub Methodname (ByVal dbTable As ITableDef)
Object test
Public Sub Methodname (ByRef dbObject As ISingleDBObject)
Public Sub Methodname (ByVal dbObject As ISingleDBObject)
For detailed information about scripts and the script library, see the One Identity Manager Configuration Guide.
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.
Table 37: Meaning of icons in the error log
|
|
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: For a detailed description of an error, double-click the error message.
Related topics
If automatic error correction is possible, the Consistency Editor error log offers a Repair button.
To correct faulty data
- Select the error entry in the Consistency Editor error log.
TIP: Use Shift + select or Ctrl + select to select several entries for repair.
- To start error correction, click Repair.
The correction is made directly in the One Identity Manager database. Resulting data changes are made using the One Identity Manager Service.
NOTE: When repairing templates, dependent objects can also be changed. In certain cases, a large number of dependent objects are changed and saved. Additional processes may be generated.
Related topics
After changes have been made to configuration data, such as changes to processes, scripts, templates, object definitions, task definitions or preprocessor-relevant configuration parameters, you must compile the database with the Database Compiler.
After a schema installation, a schema update or the import of a complete custom configuration package, the compilation from the Configuration Wizard or the Database Transporter is started immediately. After importing hotfix packages or restricted custom configuration packages, compile the database using the Database Compiler.
NOTE: The 
icon in the status bar indicates that the database needs to be compiled.
Detailed information about this topic
