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.

Database link name that connects the history database to the production database. This attribute is required when you create the history database as a source and you use transaction or cycle restore. For restore scenarios, the history database is the source, and the production database is the target.

During the restore job, the system uses this attribute for the database link value. If you do not provide a value, then the system dynamically creates the database link from the source to the ILM repository. After the restore job completes, the system drops the database link.

If the system needs to create the database link, then the administration or application database users need to have create and drop database link permissions.

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.

Host of the SAP application that you want to retire.

Required for SAP application retirement only.

Client in which the user logs in. Note that all clients in the SAP application are retired.

Required for SAP application retirement only.

System number in which the user logs in.

Required for SAP application retirement only.

Language in which the user logs in. Note that all languages in the SAP application are retired.

Required for SAP application retirement only.

User that logs in to the SAP application. The user must be assigned to the ZINFA_RETIREMENT_PREPARATION role and include RFC connection authorizations.

Required for SAP application retirement only.

Password for the SAP user.

Required for SAP application retirement only.

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.

User name to connect to the FTP server.

Required for SAP application retirement if you set up an FTP connection between the SAP application server and Data Archive.

Password for the FTP user.

Required for SAP application retirement if you set up an FTP connection between the SAP application server and Data Archive.

Host name of the FTP server.

Required for SAP application retirement if you set up an FTP connection between the SAP application server and Data Archive.

Port number of the FTP server. Default port is 21.

When you specify a port number, enable that port number for FTP on the host machine.

Required for SAP application retirement if you set up an FTP connection between the SAP application server and Data Archive.

Name of the FTP folder on the Data Archive server. For example,

ERP\

.

Required for SAP application retirement if you set up an FTP connection between the SAP application server and Data Archive.

For SAP application retirement projects, if you want Data Archive to save the BCP files in a compressed file format, enable the check box. When you enable the check box, Data Archive saves the BCP files as

.gz

files in the staging area.