My Oracle Support Banner

Oracle Consistent Streams Based CDC - The Window ID Is Out of Range (Doc ID 1576058.1)

Last updated on OCTOBER 13, 2023

Applies to:

Oracle Data Integrator - Version and later
Oracle Data Integrator on Marketplace - Version 1.0.2 and later
Information in this document applies to any platform.


Using Oracle Data Integrator (ODI) "JKM Oracle 11g Consistent (Streams)" for incremental changes with Oracle Database 11g.

The Subscriber window is falling out of range for a couple of records, meaning that, when the subsequent *consumer* Integration Interfaces are being executed, certain rows are not being processed.

Following are the implemented steps:

  1. Add the Model to CDC, create Subscriber, and start the Journal.
  2. Make changes to table A, lets say 6 records of it. Verify that all the 6 records are getting captured in J$ journal tables.
  3. Extend the window, and lock the Subscriber.
  4. Run the Integration Interface, and observe that some of the records in the J$ journal tables are not *consumed*.

Following SQL command has been used to finger-point the records that are falling out of range:

select distinct decode(TARG.ROWID, null, 'D', 'I') JRN_FLAG,
       sysdate            JRN_DATE,
       JRN.TEST_ID        TEST_ID,
from   MYSCHEMA.J$TEST       JRN, 
       MYSCHEMA.TEST         TARG
where  JRN.TEST_ID      =  TARG.TEST_ID (+) 
and    JRN.CSCN$        >  SUB.MIN_WINDOW_ID
and    JRN.CSCN$       <=  SUB.MAX_WINDOW_ID;

For the rows that are not being picked up by the Integration Interface, the last condition in the above query doesn't return any record.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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