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. Storage Classifications
  24. Appendix A: Datetime and Numeric Formatting
  25. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

IBM DB2 Native Utilities Properties

IBM DB2 Native Utilities Properties

Before you use IBM DB2 native utilities for data movement, configure properties for Data Archive to use IBM DB2 native utilities. Optionally, you can configure additional command parameters to use in the import and export commands. Uncomment the properties to enable them.

General Properties

The
conf.properties
file includes the following properties for IBM DB2 native utilities:
informia.db2ClientPath
Location of the IBM DB2 Connect client root directory. Required to use any of the IBM DB2 native utilities for data movement. The IBM DB2 Connect installation must be on the same machine that hosts the ILM application server.
If you do not configure this property, Data Archive uses JDBC for data movement.
informia.db2HPUPath
Location of the IBM DB2 HPU utility root directory. Enter the full path to the main directory of the IBM DB2 HPU utility installation. Required to use the IBM DB2 HPU utility to export data. The IBM DB2 HPU utility installation must be on the same machine that hosts the ILM application server.
If you do not configure this property, Data Archive uses the export utility to export data.
informia.exportLobLocation
Location on the IBM DB2 database that temporarily stores LOB data. Required for the load client utility to process tables that have LOB datatypes. The location must be on the same machine that hosts the ILM application server.
If you do not configure this property, the archive job uses the import utility to process tables with LOB datatypes. The import performance might be impacted if the archive job uses the import utility.
informia.exportUtilName
IBM DB2 utility that Data Archive uses to export data. Required if you want to use the IBM DB2 HPU utility to export data.
If enabled, default value is
HPU
. Data Archive uses the IBM DB2 HPU utility to export data.
If disabled, Data Archive uses the export utility to export data.
Default is disabled. By default, if you configure the informia.db2ClientPath property, Data Archive uses the export utility unless you specify another utility in this property.
informia.hpu.columnSeparator
Optional. Character that identifies the column separator for the IBM DB2 HPU utility to export data.
If enabled, the archive job passes the value to the control file that the IBM DB2 HPU utility uses to export data. The job uses this value to create export files. Configure to one byte length. The IBM DB2 HPU utility does not support multibyte length separators.
If disabled, the IBM DB2 HPU utility default separator is used to export data.
informia.hpu.rowSeparator
Optional. Character that identifies the row separator for the IBM DB2 HPU utility to export data.
If enabled, the archive job passes the value to the control file that the IBM DB2 HPU utility uses to export data. The job uses this value to export files. Configure to one byte length. The IBM DB2 HPU utility does not support multi-byte length separators.
If disabled, the IBM DB2 HPU utility default separator is used to export data.
informia.importUtilName
IBM DB2 native utility that Data Archive uses to import data.
If enabled, default is IMPORT. Data Archive uses the import utility. For IBM DB2 on AS/400 and z/OS, you must enable the property to use the import utility.
If disabled, default is LOAD_CLIENT. Data Archive uses the load client utility. The load client utility is available for IBM DB2 on AIX, Linux, UNIX, or Windows.
By default, if you configure the informia.db2ClientPath property, Data Archive uses the load client utility unless you specify another utility in this property.
informia.TempDirectory
Temporary directory that stores the import and export files for the IBM DB2 native utilities. Each table has a separate import and export file. Data Archive deletes the corresponding import and export files after it processes the table. The location must be on the same machine that hosts the ILM application server.
At a minimum, the size of the temporary directory should equal the size of the tables that you run in parallel. For example, you need at least 10 GB temporary storage if your average table size is 1 GB and you use 10 threads for parallel processing.
For the IBM DB2 HPU utility, location that temporarily stores the control file that Data Archive generates when the job copies data to the destination. The IBM DB2 HPU utility uses parameters in the file for the export process. After the job completes, the job deletes the control file.

Import and Export Command Parameter Properties

You can add IBM DB2 command parameters to the script that the export or import utility uses to import or export data. By default, no additional command parameters are required.
Add command parameters to the property that corresponds to the location in which you want to insert the statement. You can use any command parameters that the import and export commands support in that location. Enter the property values in the supported IBM DB2 syntax for the import and export commands.
You can add the following optional properties to the
conf.properties
file:
informia.db2ImpStart
Statement that is inserted after the load file name of the import command. If you configure separators for the HPU utility, you must add a statement for the import utility to use the same separators.
The following value is an example of a statement that creates a dump file:
MODIFIED BY chardel@ coldel% delprioritychar DUMPFILE=/u01/db2/Dump.dmp FASTPARSE ANYORDER warningcount 10000
informia.db2ImpMiddle
Statement that is inserted before the insert statement of the import command.
informia.db2ImpLast
Statement that is inserted after the insert statement of the import command.
informia.db2ExpStart
Statement that is inserted after the unload file name of the export command.
informia.db2ExpLast
Statement that is inserted after the select statement of the export command.

0 COMMENTS

We’d like to hear from you!