Setting the Seed Migration Priority System Preference

When migrating from a development (source or Design Time Repository) to a production (target or Runtime Repository) environment, you should set the Seed Migration Priority system preference as required in the target environment in order to resolve any conflicts that might arise when migrating from the DR to RR environment. Set Seed Migration Priority in the target (RR) environment to one of the following values:

1. Source. Precedence is given to the seed data in the DR environment.

2. Target. Precedence is given to the seed data in the RR environment.

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.

Note the following:

• If data on the target environment has not been modified and Last Updated Source is set to dataimp (seed data indication), then independently of the seed migration priority system preference value, target data will be replaced by the source data if it was modified at source.

• The conflict resolution is based on LOV data (About Record - Last Updated Source value). If an LOV's Last Updated Source value is one of the following, this means that the LOV has been modified and that the target setting will take precedence: User, Object Manager - Default, or EIM.

  After the migration plan is executed, Last Updated Source will default to User for all modified LOVs.

Before performing your first Full Runtime Repository migration, you must synchronize Siebel LOV data between development (source) and production (target) environments. Set Seed Migration Priority to Source for the first migration – you can subsequently change this to "Seed Migration Priority" = Target as required.

For more information about the Seed Migration Priority system preference, see the topic about modifying LOVs in RR environments in Siebel Applications Administration Guide.