Executing start up sequences
By default, start up sequences are started using scheduled process plans. In the , it is also possible to start a start up sequence manually.
To start a start up sequence manually
- In the Synchronization Editor, select the Database | Manage start up sequences.
- In the Sequences pane, double-click the start up sequence.
- In the Included start up information, click .
Monitoring start up sequences
Once a start up sequence is running, an instance of the start up sequence in added in the DPRStartSequence table. This instance contains information about the runtime status and errors of the entire start up sequence. A DPRStartSequenceHasProjection table is also saved for every start up configuration that is run. This instance contains information about the runtime status and errors of the current .
Instances can be shown and monitored in the . The following instances are shown:
- Start up sequences that are still running.
- Start up sequences that quit on error assuming at least one start up configuration has the Sequence quits on error option set.
To display a start sequence instance
In the Synchronization Editor, select the Database | Manage start up sequences menu item.
In the Sequences pane, click .
Double-click on the start up sequence instance.
In the Included startup information view, you can see the runtime status of all the associated start up configurations.
To update the view, in the Sequences toolbar, click .
Table 69: Runtime status of an instance
The instance is created.
The start up configuration is waiting to run.
Synchronization is running.
Synchronization has successfully completed
Synchronization ended with an error.
Instances of completed start up sequences are deleted after a specified time period. The DPRStartSequence and DPRStartSequenceHasProjection tables are cleaned up in the process. By default, completed instances are kept for seven days.
To change the retention period for completed instances
- In the Designer, set the DPR | StartSequnce | LifeTime configuration parameter and enter the maximum retention period.
Handling unexpected termination of synchronization
If is executed with a start up configuration, some One Identity Manager processes are stopped. It is not possible to start this start up configuration again. The One Identity Manager saves start information of the current synchronization in the database. This start information is reset once synchronization is completely normally.
If synchronization was terminated unexpectedly, for example, a server was no available, you must manually reset the start information. You can only restart synchronization after this.
IMPORTANT: Start information may not be reset if synchronization is running normally.
Before you reset the start information, ensure that synchronization has really been aborted.
To reset synchronization start information
- Select the Configuration | Start up configurations category.
- Select a start up configuration in the document view and click Reset.
- Confirm the security prompt with Yes.
The status "Broken" is entered in the synchronization log.
NOTE: If necessary, start information can be reset automatically. To do this, customize the process DPR_DPRProjectionStartInfo_Run_Synchronization. Changes made to the process are applied to all target systems connected to the One Identity Manager database when synchronization takes place.
with revision filtering involves finding object pairs where one has newer change information than the last time it was synchronized. It may also be necessary to process those objects during synchronization, whose change information has not be updated since the last synchronization. This might be required if changes to data were made without the change information for the object being updated, for example. It is possible that data in one of the connected systems was restored from a backup. This means the change information for the objects is now older than before the last synchronization. Such objects are not processed by synchronization with revision filtering.
One Identity Manager provides an option to reset revision numbers in a start up configuration. The revision can be reset for one schema type or for all of a schema's types. The next time synchronization is run with this start up configuration, all affected objects are seen as changed.
To reset the revision number
- Select the category Configuration | Start up configurations.
- Select a start up-configuration in the document view and click Revisions...
This opens the Manage revisions... dialog window. which displays all the schema types with their respective revision numbers. types without a revision number, are not displayed.
- Select the schema for which you want to reset the revision number.
- OR -
From the target system schema or the One Identity Manager schema, select the schema type for which you want to reset the revision.
- Click Reset.
- Select another schema type if required.
- Click Apply.
- Confirm the security prompt with Yes.
The revisions of the selected schema types are deleted from the start up configuration.