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

IBM DB2 Target Connections

IBM DB2 Target Connections

When you define an archive target connection for IBM DB2 databases, you can choose from multiple connection types. The connection type you choose depends on the database version.
Choose one of the following connection types to connect to an IBM DB2 database:
  • DB2_Adapter z/OS. Use to connect to IBM DB2 on z/OS.
  • DB2_Adapter UDB. Use to connect IBM DB2 on AIX, Linux, UNIX, or Windows (LUX).
  • DB2_AS400_Adapter. Use to connect to IBM DB2 on AS/400.
The properties that are available are based on the connection type that you choose. Also, the property names may vary slightly.
When you use IBM DB2 native utilities for data movement, the archive job uses the connections that you configure in IBM DB2 Connect to connect to the source and target databases. When you run an archive job, the job gets the DB2 connect connection name from the archive source and target connections. Then, the job uses connection name to get the connection details from DB2 Connect.
To use IBM DB2 native utilities for data movement, create connections to the source and target in IBM DB2 Connect first. Then, create source and target connections in Data Archive and add the DB2 Connect connection name.
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.
Database or Service Name
Unique identifier or system identifier for the target database server.
Admin Schema or ILM Repository Administrator User
Default administration database user for the target database server, such as SYSTEM.
Admin User Name or Admin Login Name
Login name for the administration database server. This user does not require special permissions as it is only used to connect to the target database. You can provide any user name, such as a database connection user or a read-only user.
Password
Password for the administration login name.
Apps Schema or Application User Name
Application database user that owns the tables that you want to archive to. Also commonly referred to as the history application user.
Apps User Name or 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.
Federated Server Name to Source or 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 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.
IBM DB2 Connect Data Source Name
Data source name that you configured for the target connection in IBM DB2 Connect. Required if you use IBM DB2 native utilities for data movement. The archive job uses the connections that you configure in IBM DB2 Connect to connect to the source and target databases. When you run an archive job, the job gets the IBM DB2 connect connection name from the archive source and target connections. Then, the job uses the connection name to get the connection details from IBM DB2 Connect.
If you do not configure a data source name and you use IBM DB2 native utilities for data movement, the archive job fails. The job can only connect to the database from IBM DB2 Connect.

0 COMMENTS

We’d like to hear from you!