Can One Creates ARCHIVE Process To Build ARCHIVE Schema On A Different Instance And Database? (Doc ID 2971030.1)

Last updated on JULY 20, 2024

Applies to:

Goal

In 6.4.3, the current OTM Purge and Archive process puts the archived data in the ARCHIVE_C schema on the OTM database. We would like to export the data from the current Purge and Archive process to the ARCHIVE_C schema on a different Instance/ Database.
The question is about its feasibility since the following found properties:
glog.database.archive.dbserver,
glog.database.archive.sid,
glog.database.archive.port,
glog.database.archive.user,
glog.database.archive.password: Use these properties to build a connection string to the data source,
"ARCHIVE.ARCHIVE", which points to the ARCHIVE_C schema.

Assuming the ARCHIVE_C schemas are located in the same database as GLOGOWNER, the installer needs only to add the archive_c user password to the shared wallet with key archive.archive_c,
or override the glog.database.archive.password' password in glog.properties.
That may imply that one can direct the archiving process to archive data on an outside database
Can you confirm this understanding?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.