Archive Environment Registration

Archive environments must be registered before they can be utilized. Registering an archive environment involves running an environment registration utility, specifying information about both production and the archive environment being registered. Your implementation's database administrator must execute the registration utility as the utility performs functions on the database that require administrative access.

When using Oracle as your database, you have the choice of configuring the archive database to be in the same Oracle instance (recommended) or a separate Oracle instance. For other databases, separate database instances are required.

The following summarizes the functions performed by the registration utility:

• Adds an environment reference in the production environment specifying the target environment's role (in this case Archive), the target environment's universal environment ID, as well as a prefix character used for creating synonyms described below.
• Creates synonyms in the production environment database that reference tables in the target environment database over a database relationship. Refer to Database Users and Database Relationships below. These synonyms are prefixed with the environment reference's name prefix that is used in place of the "C" in a normal table name. For example, assuming the environment reference's name prefix is A, the CI_BILL table in the target environment database is referenced via the AI_BILL synonym in the production environment database.
• If the archive database is configured as a separate database instance, the utility also creates super views in the archive environment's database that is being registered. Each super view is a database view defined as a union of a given archive environment database table and its corresponding production environment database table (over another database relationship). Refer to Database Users and Database Relationships below.