Repository Manager Guide

10.3 HotFix 1

Back Next

Considerations for the Import Process

Before you import, consider the following information:

Before you import design objects, consider making a back up copy of the target repository.

Importing (and renaming) involves changes to the target repository only—the source repository remains unchanged.

For import operations,

Repository Manager

requires a repository that has been validated and free of Errors, or FATAL issues.

In Informatica MDM Hub version 9.5, the Period_Start_Date and Period_End_Date columns replace the Rel_Start_Date and Rel_End_Date columns. If you import a pre-9.5 change list into a fresh 9.5 installation, you must run script

migrate_hm_rel_start_end_dates.sql

after you import the change list to update the pre-9.5 schema. See Update Relationship Base Object Start Date and End Date Mappings.

The

Repository Manager

export and import processes do not preserve ROWID_OBJECT values in design object records. When you export design objects, the ROWID_OBJECT values from the source ORS are not preserved in the export file. When you import these design objects into a target ORS, the import process assigns new ROWID_OBJECT values, which might differ from the corresponding records in the source ORS.

Problems can arise if you depend on ROWID_OBJECT values to uniquely identify design objects. For example, Hierarchy Manager could be configured to use ROWID_BO_CLASS as the reference to the C_RBO_BO_CLASS table on the source schema. If a SIF client application depended on this configuration, it would work correctly in the source ORS but not necessarily in the target ORS. Therefore, instead of ROWID_OBJECT values, use unique identifiers to identify specific design objects, such as BO_CLASS_CODE for entities, REL_TYPE_CODE for relationship types, and HIERARCHY_CODE for hierarchies.

Custom match populations are not imported from a change list. Instead, remove the custom match population element from the change list XML file, then either modify the target schema manually, or use direct database import/changelist options.

Before importing into a repository, make sure that both the source and target repositories have sufficient privileges to all required tablespaces.

If the source repository has the Admin system enabled as a state management override system, the import procedure does not update the state management override system indicator for the Admin system in the target repository. You must manually enable the Admin system in the target repository as a state management override system.

About Importing Design Objects

Issue Severity Levels

Considerations When Copying Metadata

Exporting a Repository

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal