Guidelines to Avoid Duplicate Versioned Object Records

Follow these guidelines to avoid creating duplicate versioned object records:

• Use a single master database for product administration. This database ensures that object identifiers of objects can be preserved and easily migrated to different environments.

• All other databases must have the same object identifier for products, attribute and class records as the master database. As needed, data from the master product administration database must be replicated to other environments, ensuring that the object identifiers are preserved across the databases.

• Never manually create objects with the same name in two databases. They are different objects and do not merge into one record, using the import function or Application Deployment Manager (ADM). If the object identifier is different for the same object in the two databases, the versioned object is treated as a different object during the import even if the names match, hence the two objects are not merged. Instead, an existing object definition can be moved from one database to another using import or ADM, so that the object identifier is preserved.

• The product, attribute, and class master must initially be a copy of the upgraded production database.