'RNX0233 unmonitored by CDCRTVJRN' Message Signalled Using ODI CDC Procedure With Native iSeries (AS400) V5R3 Or Later (Doc ID 1307955.1)

Last updated on JUNE 16, 2022

Applies to:

Symptoms

After having installed the Oracle Data Integrator (ODI) Journalization / Changed Data Capture (CDC) on iSeries V5R3 server using native iSeries Transaction Journals, the Integration Interface interrupts at the Retrieve iSeries Journal Entries step with the following message:

java.sql.SQLException: [CEE9901] Application error. RNX0233 unmonitored by CDCRTVJRN at statement *N

The command executed was:

call ODILIB.CDCRTVJRN ('ODILIB.SNP_SUBSCRIBERS', 'WAVEDLIB.F9F00','SUNOPSIS','Y')

Further investigation of the iSeries (AS400) spool file indicates a SQLCODE: -107, SQLSTATE: 42622 "table name too long" message which is caused by the concatenation of all the parameters passed to iSeries:

2011-03-07-14.29.52.360000 - * Program . . . : CDCRTVJRN
2011-03-07-14.29.52.360000 - * Version . . . : CDCRTVJRN v1.10 temp - v5r2
2011-03-07-14.29.52.360000 - Main(): Start
2011-03-07-14.29.52.360000 - Main() Arg1: ODILIB.SNP_SUBSCRIBERSWAVEDLIB.F9F00SUNOPSISY
2011-03-07-14.29.52.360000 - Main() Arg2: WAVEDLIB.F9F00SUNOPSISY
2011-03-07-14.29.52.360000 - Main() Arg3: SUNOPSISY
2011-03-07-14.29.52.360000 - Main(): Getting File Information
2011-03-07-14.29.52.365000 - pGetFileInfo() ----- Start ----
2011-03-07-14.29.52.365000 - Querying the subscriber table ODILIB.SNP_SUBSCRIBERSWAVEDLIB.F9F00SUNOPSISY for table WAVEDLIB.F9F00SUNOPSISY and subscriber SUNOPSISY
2011-03-07-14.29.52.366000 - SQL Action: PREPARE
2011-03-07-14.29.52.366000 - SQL Stmt : select JRN_JNAME, JRN_KEY_COL_LST, JRN_CURFROMDATE from ODILIB.SNP_SUBSCRIBERSWAVEDLIB.F9F00SUNOPSISY where JRN_TNAME = ? and JRN_SUBSCRIBER = ?
2011-03-07-14.29.52.366000 - SQLSTT=42622
2011-03-07-14.29.52.367000 - SQLCOD=-107
2011-03-07-14.29.52.367000 - SQLERM= SNP_SUBSCRIBERSWAVEDLIB 10
2011-03-07-14.29.52.367000 - SQLERP=QSQRPARS
2011-03-07-14.29.52.367000 - SQLERR=

Changes

Almost all application programs that generate printed output make use of the spooling support provided with the iSeries server.

Specifying SPOOL = *YES or SPOOL = *NO on the SPOOL parameter of a printer file determines if spooling support is requested.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.