Default administration database user for the source database server, such as SYSTEM.

The administration database user has DBA rights to the database, including the ability to run DDL and access system-level objects.

Database user that owns the application tables that you want archive, such as APPS for Oracle applications.

The production application user is either the owner of the tables that you want to archive or partition, or the user that has full rights to the tables that you want to archive or partition. During the archive process, you can use the production application user to delete from the source. Alternatively, you can configure the source connection to use the staging user to delete data from the source.

Use the default database user for the application or provide another value if you do not use the default user. If you provide a user that does not own or has full access to the application tables, then the archive job fails because the job cannot find the table or view.

The archive job uses the number of schemas in the source application to determine schema names. The archive job uses this attribute value for applications that have one schema, such as PeopleSoft and Siebel. The archive job uses the schema name from the mined application for applications that have multiple schemas, such as Oracle applications.

The ILM engine uses this field to generate the SQL SELECT statement to read data from the application tables. For example, if you enter SYSADMIN, the archive job generates the following SQL:

SELECT * from SYSADMIN.<OBJECT NAME>

Staging database user for the source database.

The staging database user stores interim tables for business rule validation and generates candidates during the archive and partitioning processes. If you enable staging for the archive source connection, the staging user also creates staging tables. The staging tables temporarily store a copy of the archived data before the archive job moves the data to the archive or history database. The staging user typically resides in the source database.

Tablespace in the staging database user that stores the interim and staging tables when you run an archive cycle. The archive job always stores the interim tables in this tablespace. The archive job stores staging tables if you enable staging.

Determines whether the archive job temporarily stores data in a staging area on the archive source before it moves data to the target. The archive job includes heavy select and delete operations on the tables that are selected in the archive job. The operations may impact performance on any user operations on the tables. For example, if you run an archive job that archives purchase orders, users may see a performance impact when they create a purchase order. The main benefit of staging is to reduce the number of operations on the production tables.

If enabled, the archive job copies data to the staging area after the archive job evaluates the business rules. The archive job copies data that meets the business rules from the archive source to the staging area. Then, the job deletes data from the source and moves data from the staging area to the target system.

If disabled, the job extracts data directly from the archive source to the archive target. The extraction and deletion occur simultaneously. You may want to disable staging if you do not want to create additional storage space on the production database.

Controls the number of rows that the system fetches in one batch from one table if you use JDBC to connect to the source database.

Only change the default value if you receive an out-of-memory error when the archive job copies data to the destination. You may get the out-of-memory error if the source table has large objects in each row, such as CLOBS or BLOBS data types. If you receive this error, then reduce the fetch size.

Default is 1000.

If enabled, the system issues a single commit after it restores all tables.

If disabled, the system issues a commit after it restores each table.

Default is disabled.

Determines which database user the archive job uses to delete data from the source database.

If enabled, the archive job uses the staging database user to delete from the source.

If disabled, the archive job uses the application database user to delete from the source.

Whether you enable this option depends on the authorizations that the application or staging database users have. For example, you may want to use the staging user for deletes if you have a read-only application database user.

Default is disabled.

This attribute only applies to external attachments.

This attribute only applies to external attachments.

Temporary location that stores the scripts that the archive job generates to move external attachments from the source to the target.

Enter a location that you have read and write access to. For Siebel attachments, enter a location that is accessible to the Data Vault Service for External Attachments server.

This attribute only applies to external attachments.

Determines whether the archive job automatically archives external attachments or whether you run a standalone job to move the attachments after the archive job completes. If you provide a source file location for attachments, the archive job creates SQL scripts in the file server location and associates the scripts with the archive job ID.

If enabled, the archive job runs the scripts during the archive process. The run procedures configuration in the entity determines when the archive job archives the attachments.

If disabled, you must initiate the movement after the archive job completes. You can manually run the scripts in the file server location or you can run a standalone job to move the attachments. If you run the standalone job, you must provide the archive job ID. The job then looks for the scripts that are associated to the archive job ID.

This attribute only applies to external attachments.

Determines the interim table names in the entity if you want to run the entity in parallel archive jobs. For example, you may extract data in parallel from two different organizations in the same human resource entity. The system creates interim tables in the staging database user. However, the tables need to be differentiated so the archive jobs know which interim tables are relevant for that job.

By default, the system creates interim table names with the same name in EDM. If you enable this attribute, then the system creates the interim table names with the following syntax:

<table name>_<job ID>

If you enable this attribute and the staging database user does not have authorization to create tables, then the archive job fails.

Determines if the archive job creates interim tables without logging.

If enabled, the archive job creates the interim tables in no logging mode. You may want to enable if you have a limited amount of logging space in the source. However, if you create tables without logging, then recovery ability is at risk.

If disabled, the archive job creates the interim tables with logging.

Default is disabled.

When you archive to an Oracle target, determines if the archive job creates target tables with the same compression as the source.

If enabled, the archive job creates target tables with the same compression as the source tables if the source tables have COMPRESS FOR DIRECT_LOAD OPERATIONS table compression.

If disabled, the archive job does not create target tables with compression.

Default is disabled.

When you archive to an Oracle target, determines if the archive job creates target tables with the same partitioning as the source.

If enabled, the archive job creates target tables with partitioning if the source tables include list and range partition types.

If disabled, the archive job does not create target tables with partitioning.

Default is disabled.

The name of the schema when you imported the table metadata from the source.

You must select

Use Imported Schema Name

when the tables in the entity are from more than one schema.