Configuring the Schema/Database for Data Archive
For data archival, you must create a separate schema (Oracle) or database (Microsoft SQL Server, MySQL).
Note:
The archive schema created for Oracle should be in the same database that hosts the production schema.
Install the ActiveTransferArchive component in the archive schema or database using Database Component Configurator (DCC). The ActiveTransferArchive component contains stored procedures required for the archival process. The component also creates a table for logging the execution history of the archival process. The ActiveTransferArchive component automatically installs the ActiveTransfer database component as well. The table structure in the archive schema or database is a mirror of the production schema or database.
The archive schema or database should have SELECT and DELETE permissions for the following tables that store runtime or transaction data in the production schema or database:
MFTTRANSACTION
MFTEVENTLOG
MFTACTIVITYLOG
MFTACTIVITYLOGMESSAGE
MFTACTIVITYDETAILS
MFTAGENTEVENTLOG
MFTAGENTACTIVITY
MFTAGENTACTIVITYDETAILS
The archive schema or database should have SELECT permissions for the following tables that store asset information such as actions, agents, and so on in the production schema or database:
SCHEDULEDACTIONS
POSTPROCESSEVENTS
INSTANCECONFIG
SERVERCONFIG
PARTNERMAPPING
MFTAGENT
MFTAGENTEVENTS