Overview of Archiving Objects

Archiving is a process where you export objects from the repository to an archive file. You can then import objects from the archive file back into the repository. You can use an archive to back up sets of objects or move them to another environment that shares the same physical database schema as the source environment. Note the following:

• An archive does not depend on a database because it includes only repository information. You can use it to exchange repository data between environments with different database platforms, including local and server databases, as long as these databases use the same schema.

• If you import objects from an archive, then you can specify conflict resolution rules for each object. You can specify to ignore an imported object, replace an existing object with an imported object, or merge two objects according to object properties.

• You can archive individual objects or entire projects to an archive.

• You can use code control software to control an archive.

• If you want to back up or move the entire repository to another environment, then see Exporting and Importing Repositories.

  Note: Archiving is not supported nor intended for the migration of entire repositories from one environment to another.

For more information about the files that you use when archiving objects, see Files That You Use to Manage Repositories.

Using Export and Import for Different Versions of Siebel CRM

If you want export objects from one version of Siebel CRM to another version, then do not import those objects through .sif files into the different version of Siebel CRM because Siebel might modify object definitions between these versions. If you import an object that is not valid, then an invalid configuration might result. Oracle does not support an invalid configuration.