When an environment is installed initially, a database user is
defined as the owner of all the application database schema objects.
We'll call this database user CISADM. To use the archive engine, two additional database users are necessary
for each environment's database:
- Database user with read/write access to the application database
schema. We'll call this database user CISUSER.
- This database user is installed automatically when the system
is installed in an Oracle database.
- The application server(s) used to access the production environment
should be configured to access the production database as the CISUSER database user. This is
the default in an Oracle installation. For DB2, this is a manual operation
that must be performed manually following installation and prior to
environment registration.
- Database user with read-only access to the application database
schema. We'll call this database user CISREAD.
- Note that this database user is installed automatically when the
system is installed in an Oracle database.
- The application server(s) used to access the archive environment
should be configured to access the archive database as the CISREAD database user.
Prior to registering an Archive environment, the following database relationships must be configured
by your implementation's database administrator to match the diagram
below:
Note: Same Oracle Instance. If you configured your archiving
environment to be in the same Oracle instance as your production environment
then you don't need to configure a database link.
Notice that the database relationship originating from the production
environment's CISUSER database schema references the CISUSER schema in the archive environment's database.
A database relationship originating from the archive environment's
CISREAD database schema
references the master and configuration data in the CISREAD schema in the production
environment's database.
Archive database processes that are run from the production environment
move data into a given archive environment. When the process populates
tables in an archive environment's database, the CISUSER to CISUSER database relationship is
used.
Note:
Archiving Data Using Flat Files. As an alternative to archiving data using the database relationships
described above, you can move your archive data to flat files and
then subsequently import these flat files into your archive environment.
For some environments, bypassing the database relationships for the
archive step may provide better performance. Refer to
Step 4: Move or Delete Production Data for more information
about the background process that archives data to flat files.
Copyright © 2000, 2015, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.19.2015 16:18:51 [F1_1424305131000]