After updating the One IdentityAn identity usually represents a real person. In addition, identities that do not represent real people, such as machine identities or service identities, can be mappedList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. in One Identity Manager. (see also virtual identity; see also main identity/subidentity) Manager database, all synchronization projectsA collection of all data required for synchronizingThe processSequence of process steps for mapping an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this. are migrated. This updates the schemas and applies any automatic patches. The DPR_Migrate_Shell process is run to do this. If the process fails because, for example, the target systems could not be reached the effected synchronization project is deactivated. Therefore synchronization cannot run. When you open the synchronization project in the Synchronization EditorOne Identity Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by synchronization.., a detailed error message is displayed.
To use a synchronization project again after failed migration
-
Solve the issue that prevented the migration.
TIP: To display the error message
-
In the Synchronization Editor, select the Edit > Edit synchronization project menu item.
-
Select the Migration tab.
-
- Save the changes.
-
Re-enable the DPR_Migrate_Shell process.