Recommendations for the Setting Up and Running of ODI Processes on DB2/400 Databases and iSeries Servers
(Doc ID 833627.1)
Last updated on NOVEMBER 02, 2023
Applies to:
Oracle Data Integrator - Version 3.2.03.01 to 11.1.1.9.99 [Release 3.2.03 to 11gR1]Information in this document applies to any platform.
Purpose
The purpose of this document is to:
- Assist the users that use Oracle Data Integrator (ODI) components (Agent, scheduler Agent and/or Scenarios) on iSeries and AS/400 systems.
- Provide a detailed troubleshooting guide for specific DB2/400 database issues.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| ODI components that may be installed on IBM iSeries and AS/400 |
| IBM PTF Cover Letters |
| IBM documentation |
| Using the ODI runtime (Agents, Scheduler Agents and Scenarios) on IBM iSeries and AS/400 |
| 1. Compiling the "sunopsis.zip" file |
| 2. Installing ODI runtime on IBM iSeries with access to DB2/400 databases located on the same server |
| 3. Running ODI Agents or Scenarios using CL programs |
| 4. Changing the Java Language settings for the ODI Agents or Scenarios using CL programs |
| 5. Resolve "Cursor state not valid" messages |
| 6. Avoiding the following message "qstrup : the requested heap space operation is invalid" |
| 7. Avoiding the following message "java.net.UnknownHostException: empty string" |
| 8. Avoiding the saturation of CPU with the QZDASOINIT process |
| Installing ODI Master and/or Work Repositories on IBM iSeries and AS/400 |
| 1. Corrective actions when SQL7008 messages are signaled |
| 2. Resolve SQL0204 messages |
| 3. Prevent locks on ODI Repository SNP_MODULE and/or SNP_HOST_MOD tables |
| Using the ODI Change Data Capture (CDC) based on native iSeries Transaction Journals |
| 1. Does CDCRTVJRN program require *ALLOBJ special authority? |
| 2. Restart Changed Data Capture (CDC) processing |
| 3. Unexpected resource usage is encountered after IPL (Initial Program Load) |
| 4. Other behaviors related to CDCRTVJRN program |
| Using IBM DB2/400 database |
| 1. Installing and configuring the JDBC driver on iSeries and AS/400 |
| 2. Installing and configuring the JDBC driver on servers other than iSeries and AS/400 systems |
| 3. Resolving issues related to the Physical Architecture |
| 4. Resolving DB2/400 reverse engineering specific issues |
| (i). Resolving behaviors related to DDS File descriptors |
| (ii). Resolving other issues related to reverse engineering operations |
| 5. Resolving loading issues |
| 6. Resolving Changed Data Capture (CDC) issues |
| 7. Resolving SQL7008 messages |
| 8. Resolving SQL0204 messages |
| 9. Working with dates before 1949 and after 2039 |
| 10. Resolving Date and Time conversion errors |
| 11. Resolving SQL0802 "Data conversion or data mapping" issues |
| 12. Resolving character set conversion issues on DB2/400 Datastores |
| 13. Resolving object locking issues on iSeries and AS/400 |
| 14. Manipulating data of other members in DB2/400 files |
| 15. Integration Interface runtime issues |
| Concerns with the IBM Toolbox JDBC driver for DB2/400 |
| 1. Problems due to the use of incorrect version of Toolbox JDBC driver |
| 2. Activating the IBM Toolbox / JTOpen tracing |
| 3. Resolving "The application requester cannot establish the connection" issues |
| References |