About Modifying LOVs in RR Environments

Since you can modify lists of values (LOVs) in both DR and RR environments, a potential conflict arises when you have changed LOVs in either DR or RR and you want to perform a full or incremental migration. For example:

• If the same record exists in both DR and RR and the record is modified in DR but not in RR, then which record takes priority?

• If the same record exists in both DR and RR and the record is modified in RR but not in DR, then which record takes priority?

• If the same record exists in both DR and RR and the record is modified in both DR and RR, then which record takes priority?

Seed Migration Priority

To resolve any conflicts that might arise when migrating from a DR to an RR environment, a system preference called Seed Migration Priority has been introduced. You can set Seed Migration Priority in the RR environment to one of the following values:

1. Source. If Seed Migration Priority is set to Source, then precedence is given to the seed data in the DR environment.

2. Target. If Seed Migration Priority is set to Target, then precedence is given to the seed data in the RR environment.

Note: The Seed Migration Priority system preference by default does not exist in Siebel database. If Seed Migration Priority is not set at all, then the default behavior is to assume Target as the priority and precedence is given to the seed data in the RR environment.

Caution: Prior to completing a full migration, set the value of the Seed Migration Priority system preference in the target database. Post full migration, do not modify the value of the Seed Migration Priority system preference. For any subsequent incremental migrations, the Seed Migration Priority setting must not be changed (it should remain the same as it was during full migration). Should you need to change the value of Seed Migration Priority, then full migration must be run again.

Note: The Seed Migration Priority system preference works as a conflict-resolution mechanism and applies only if there is a conflicting change during full or incremental migration (any new LOV data will migrate as normal). A conflict occurs when an existing LOV record is modified in both the DR and RR environments.

Example of Conflict Resolution for Full Migration

The following table shows how conflicts are handled during full migration from a DR to an RR environment.

If you do the following before migration:	Conflict	The seed record in RR when Seed Migration Priority = 'Source'	The seed record in RR when Seed Migration Priority = 'Target'
Modify record in DR only	No	DR record is imported to RR.	DR record is imported to RR.
Modify record in both DR and RR	Yes	DR record is imported to RR.	RR record is retained.
Modify record in RR only	Yes	DR record is imported to RR.	RR record is retained.

Example of Conflict Resolution for Incremental Migration

The following table shows how conflicts are handled during incremental migration from a DR to an RR environment.

If you do the following before migration:	Conflict	The seed record in RR when Seed Migration Priority = 'Source'	The seed record in RR when Seed Migration Priority = 'Target'
Modify record in DR only	No	DR record is imported to RR.	DR record is imported to RR.
Modify record in both DR and RR	Yes	DR record is imported to RR.	RR record is retained.
Modify record in RR only	No	RR record is retained.	RR record is retained.

Note: For incremental migrations, conflict resolutions are made only for those records which are modified in the DR (since incremental migration carries only delta changes from the DR).

Example of How Inserts are Handled During Full or Incremental Migration

The following table shows how inserts are handled when migrating from a DR to an RR environment.

If you do the following before migration:	Conflict	The seed record in RR when Seed Migration Priority = 'Source'	The seed record in RR when Seed Migration Priority = 'Target'
Insert a new record in DR	No	DR record is imported to RR.	DR record is imported to RR.
Insert a new record in RR	No	RR record is retained.	RR record is retained.
Insert a new record with the same Name, LIC and Type in both DR and RR	Yes	DR record is imported.	RR record is retained.

Users must log out of the application and then back in again for any changes to take effect.

About Conflict Resolution

The following points summarize how conflicts are resolved during migrations:

1. Only conflicting records honor the Seed Migration Priority setting. For non-conflicted records, the regular migration rule (that is, migration of data from source to target) applies.

2. New records in both (DR and RR) environments are handled as follows:

   1. New records created in DR are always migrated to RR no matter whether the Seed Migration Priority is Source or Target.

   2. New records created in RR are always retained in RR no matter whether the Seed Migration Priority is Source or Target.

   3. If a new record is created with the same name in both DR and RR, then the following behavior applies:

      • If Seed Migration Priority is Target, then source DR records are skipped and target RR records are retained.

      • If Seed Migration Priority is Source, then source DR records are imported and target RR records are deleted.

3. Deleting a seed record is a modification, which follows the same rules that apply for record modification. All deleted records become inactive.

Foreign Key References for Seed Data After Migration

As of Siebel CRM 21.6 Update, foreign key references (for example, from LOVs to Organization) are resolved as follows when migrating seed data from a development (DR) environment to any RR environment (such as Production):

• If the target environment has a record with a matching name (for example, Organization Name), then the seed data record will resolve the foreign key to that matching record.

• If the target environment has no record with a matching name, then it will not be possible to resolve the foreign key. In such cases, an error is logged indicating that the foreign key could not be resolved and the administrator of the RR environment must manually create a matching record and manually update the seed data record to point to that new record as follows:

  • Manually create an Organization in the RR environment with the same name as the DR environment.

  • Manually update the LOV record(s) to refer to the newly created Organization.