IBM Support

JR50004: ARRAYINDEXOUTOFBOUNDSEXCEPTION IN GETCALENDARDATEFROMFIXEDDATE()

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Any customer having many subscriptions with many table mappings
    configured to resolve conflicts and many conflicts occurring on
    different table mappings across the subscriptions. The tables
    that are across different tables mappings are subscriptions also
     need to contain timestamp data types. The error would happen
    when a timestamp data type would be formatted concurrently to be
     inserted into TS_CONFAUD metadata table.
    
    Target Apply:0{617} com.datamirror.ts.util.TsExceptionHandler
    processUnhandledException() An uncaught exception has occurred.
    The exception message is:
    Error: 73 java.lang.ArrayIndexOutOfBoundsException 73
        at
    sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate(Base
    Calendar.java:436)
        at
    java.util.GregorianCalendar.computeFields(GregorianCalendar.java
    :2081)
        at
    java.util.GregorianCalendar.computeFields(GregorianCalendar.java
    :1996)
        at java.util.Calendar.setTimeInMillis(Calendar.java:1110)
        at java.util.Calendar.setTime(Calendar.java:1076)
        at
    java.text.SimpleDateFormat.format(SimpleDateFormat.java:875)
        at
    java.text.SimpleDateFormat.format(SimpleDateFormat.java:868)
        at java.text.DateFormat.format(DateFormat.java:316)
        at
    com.datamirror.ts.util.TSDateTimeUtils.formatTimestampIso(TSDate
    TimeUtils.java:176)
        at
    com.datamirror.ts.target.apply.JdbcApply.convertImageToDelimitte
    dString(JdbcApply.java:2676)
        at
    com.datamirror.ts.target.publication.TargetApplyJob.logInfoIntoC
    drAuditTable(TargetApplyJob.java:1844)
        at
    com.datamirror.ts.target.publication.TargetApplyJob.resolveUpdat
    eConflict(TargetApplyJob.java:2134)
        at
    com.datamirror.ts.target.publication.TargetApplyJob.performUpdat
    e(TargetApplyJob.java:1012)
        at
    com.datamirror.ts.target.publication.TargetOperation.applyUpdate
    Operation(TargetOperation.java:1827)
        at
    com.datamirror.ts.target.publication.TargetOperation.applyUpdate
    Operation(TargetOperation.java:1750)
        at
    com.datamirror.ts.target.publication.TargetApplyJob.processOpera
    tion(TargetApplyJob.java:418)
        at
    com.datamirror.ts.target.publication.TargetMirrorApplyJob.proces
    sOperation(TargetMirrorApplyJob.java:157)
        at
    com.datamirror.ts.target.publication.TargetApplyJob.execute(Targ
    etApplyJob.java:268)
        at
    com.datamirror.ts.engine.component.PipelineThread.runThread(Pipe
    lineThread.java:205)
        at com.datamirror.ts.util.TsThread.run(TsThread.java:81)
    

Local fix

  • Options:
    - Move all CDR mappings in 1 subscriptions (will reduce
    concurrency)
    - Bring data between source and target in synch. (will reduce
    chances that concurrent conflicts will occur)
    

Problem summary

  • ISCDC 6.5.2 can fail with the following exception:
    Target Apply:0{617} com.datamirror.ts.util.TsExceptionHandler
    processUnhandledException() An uncaught exception has occurred.
    The exception message is:
    Error: 73 java.lang.ArrayIndexOutOfBoundsException 73
        at
    sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate(Base
    Calendar.java:436)
        at
    java.util.GregorianCalendar.computeFields(GregorianCalendar.java
    :2081)
        at
    java.util.GregorianCalendar.computeFields(GregorianCalendar.java
    :1996)
        at java.util.Calendar.setTimeInMillis(Calendar.java:1110)
    ...
    
    when tables with timestamp datatype colums in multiple
    subscriptions are configured for conflict detection, and
    conflicts are happening at the same time.
    

Problem conclusion

  • This issue is fixed by applying the following interim fix
    depending on the database flavor:
    - ISCDC 6.5.2 Interim Fix 40 for Oracle Redo.
    

Temporary fix

  • Configuring all tables under one subscription will minimize the
    risk of this issue to happen.
    

Comments

APAR Information

  • APAR number

    JR50004

  • Reported component name

    IS CDC ORACLE

  • Reported component ID

    5724U7008

  • Reported release

    652

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-17

  • Closed date

    2014-05-14

  • Last modified date

    2014-05-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IS CDC ORACLE

  • Fixed component ID

    5724U7008

Applicable component levels

  • R652 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSX3HK","label":"InfoSphere Change Data Capture"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"652","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
14 October 2021