Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Oracle Target Connections

Oracle Target Connections

When you define an archive target connection for Oracle databases, you can choose from multiple connection types. The connection type that you choose depends on the database version.
Choose one of the following connection types to connect to an Oracle database:
  • Oracle 8i
  • Oracle 9i
  • Oracle 10g
  • Oracle 11g
  • Oracle 12c
  • Oracle 18c
Depending on the connection type, you can configure the following target connection properties:
Host
Host of the target application database server.
Port
Port of the target application database server.
Service Name
Unique identifier or system identifier for the target database server.
Admin Schema Name
Default administration database user for the target database server, such as SYSTEM.
Admin Login Name
Login name is the same as the schema name.
Password
Password for the administration login name.
Apps Schema Name
Application database user that owns the tables that you want to archive to. Also commonly referred to as the history application user.
Application Login Name
Login name for the target application database user.
Password
Password for the application login name.
Data Tablespace
Tablespace name in the application database user that stores the history tables when you run an archive cycle. The archive job always stores the history tables in this tablespace. The archive job only stores staging tables in this tablespace if you configure the source to use staging.
Index Tablespace
Index tablespace name for the history tables.
Database Link to Source
Database link name that connects the target database to the source database. The archive job uses the database link when the job copies data to the destination.
If you do not provide a value, then the archive job uses JDBC to move the data.
Target Attachment Location
Required to restore archived attachments from the history database or from the Data Vault to the source database.
Enter the target directory where you want to restore the external attachments. The directory is the location where the source application reads the attachments from. You must have write access to the directory.
Source/Staging Attachment Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. The definition depends on the archived attachment location and whether the attachments are encrypted.
To restore attachments from the history database and non-encrypted attachments from the Data Vault, enter the current location of the archived attachments. This is the location where you originally archived the attachments to. You must have read access to the directory.
To restore encrypted attachments, such as Siebel attachments, from the Data Vault, enter a temporary location that is accessible to the ILM engine and the Data Vault Service for External Attachments component. The restore job moves the attachments from the Data Vault Service AM_ATTACHMENTS table to this temporary location.
Staging Script Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. Enter a temporary location to store the script that the restore job generates.
For attachments in the history database and non-encrypted attachments from the Data Vault, the script moves the attachments from the source attachment location to the target attachment location.
For encrypted attachments in the Data Vault, the script uses the source application encryption utility to encrypt the attachments back into the source application proprietary format. Then, the script moves the attachments from the staging attachment location to the target attachment location.
Add-On URL
Required to restore encrypted attachments from the Data Vault to the source database. Enter the URL for the Data Vault Service for External Attachments. The Data Vault Service for External Attachments converts external attachments from the archived format into the source proprietary format.
Drop Destination Indexes
Controls whether the archive job drops the index on the history database before it inserts data in the history database. Use to improve performance when the archive job copies data to the destination.
Disable Triggers
Determines whether the system disables insert, update, and delete triggers when the archive job deletes rows from tables.
If enabled, the system disables triggers when the archive job deletes data from the source.
If disabled, the system retains the triggers.
Default is enabled.
Only valid for restore archive jobs.
SSL Enabled
Enable this property if you want to create an SSL connection to an Oracle database. This property is supported for Oracle 11g and later.
ASO Encryption Type
Specifies a list of encryption algorithms used when a client, or another server acting as a client, connects to the Oracle server. The Oracle server uses this list to negotiate a mutually acceptable algorithm with the client. If an algorithm that is not installed is specified, the connection fails with the ORA-12650 error message. This property is supported for Oracle 11g and later.
This property accepts single or multiple comma separated values. For example: AES256,AES192,AES128,3DES112
Based on the negotiation with the server, the Oracle server picks the best algorithm to establish the connection.
ASO Encryption Level
Specifies the data integrity behavior when a client, or another server acting as a client, connects to the Oracle server. The behavior partially depends on the setting used in the source database connection. This property is supported for Oracle 11g and later.
Use one the following values:
  • ACCEPTED
  • REJECTED
  • REQUESTED
  • REQUIRED
Default is ACCEPTED.
If you specify a value other than the above values, the connection fails with the following error:
Invalid parameter, use one of ACCEPTED, REJECTED, REQUESTED and REQUIRED
ASO Checksum Type
Specifies a list of data integrity algorithms that when a client, or another server acting as a client, connects to the Oracle server. The list of data integrity algorithms are listed in order of intended use. This list is used to negotiate a mutually acceptable algorithm with the other end of the connection. Each algorithm is checked against the list of available client algorithm types until a match is found. If an algorithm is specified that is not installed, the connection fails with the ORA-12650 error message. This property is supported for Oracle 11g and later. This property accepts single or multiple comma separated values. For example:
MD5, SHA1
ASO Checksum Level
Specifies the data integrity behavior when a client, or another server acting as a client, connects to this server. The behavior partially depends on the setting used in the source database connection. This property is supported for Oracle 11g and later.
Use one the following values:
  • ACCEPTED
  • REJECTED
  • REQUESTED
  • REQUIRED
Default is ACCEPTED.
If you specify a value other than the above values, the connection fails with the following error:
Invalid parameter, use one of ACCEPTED, REJECTED, REQUESTED and REQUIRED
OID Enabled
Oracle Internet Directory (OID) is an LDAP directory that uses an Oracle database for storage. When you enable OID, you must provide the OID database host name for the Host parameter. You must also provide the service name that specifies the distinguished name of the database, which is configured in OID.
For example:
ORA12C,cn=OracleContext,dc=informatica,dc=com
This property is available for Oracle 11g and 12c.

0 COMMENTS

We’d like to hear from you!