Before you run a consistency check you should set the test options you require.
To specify test options
Figure 45: 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 connected to 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. |
Define change labels under which changes are grouped together in order to swap data between development and test databases as well as the productive database.
You can create and edit change labels in different One Identity Manager tools. The method is similar in all tools. Change labels are allocated using different methods depending on the One Identity Manager tool. Changes are normally allocated before or on saving the changes in the database.
Change labels are available in the program "Database Transporter" as export criteria for creating custom configuration packages.
Change labels can contain:
When you create a custom configuration package, single object properties are added to the transport package. The properties contain the values given at the time they were added.
|
IMPORTANT: This is the default process when applying changes in the Designer. If you apply this method, be consistent in booking all changes to the change label when the object is saved. It is not possible to add changes of individual properties to the change label at a later date. |
When you create a custom configuration package, the object is added to the transport package with all its properties. The properties contain the values given at the time they were added.
When you create a custom configuration package, the object is added to the transport package with all its properties. The properties are determined at the time of export.
|
IMPORTANT: Object references cannot be grouped together with changes to single properties and snapshots of objects in the same change label. Book object references to their own change labels. |
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy