JR47179: GET NOSUCHELEMENTEXCEPTION IN SYBASEOPERATIONLINKER

Fix list for IBM InfoSphere Change Data Capture

APAR status

• Closed as program error.

Error description

• Subscription can go down with following error found in trace
  file:
  127 2013-03-07 10:08:41.266 SHAREDSCRAPE LOG PARSER{907}
  com.datamirror.ts.util.TsExceptionHandler
  processUnhandledException() An uncaught exception has occurred.
  The exception message is:
  Error: null java.util.NoSuchElementException
      at java.util.LinkedList.getFirstImpl(LinkedList.java:526)
      at java.util.LinkedList.getFirst(LinkedList.java:518)
      at
  com.datamirror.ts.scrapers.sybasescraper.SybaseOperationLinker.p
  utEntry(SybaseOperationLinker.java:107)
      at
  com.datamirror.ts.scrapers.sybasescraper.SybaseLogParser.parseCo
  mmittedTxn(SybaseLogParser.java:274)
      at
  com.datamirror.ts.scrapers.cdc.LogParser.handleCommitEntry(LogPa
  rser.java:2440)
      at
  com.datamirror.ts.scrapers.cdc.LogParser.execute(LogParser.java:
  529)
      at
  com.datamirror.ts.scrapers.cdc.LogParser$LogParserPipelineJob.ex
  ecute(LogParser.java:145)
      at
  com.datamirror.ts.engine.component.PipelineThread.runThread(Pipe
  lineThread.java:205)
      at com.datamirror.ts.util.TsThread.run(TsThread.java:81)
  

Local fix

• N/A
  

Problem summary

• InfoSphere CDC can failed with the following exception:
  java.util.NoSuchElementException
  
  The following exception can be found on the trace file:
  Subscription can go down with following error found in trace
  file:
  127 2013-03-07 10:08:41.266 SHAREDSCRAPE LOG PARSER{907}
  com.datamirror.ts.util.TsExceptionHandler
  processUnhandledException() An uncaught exception has occurred.
  The exception message is:
  Error: null java.util.NoSuchElementException
      at java.util.LinkedList.getFirstImpl(LinkedList.java:526)
      at java.util.LinkedList.getFirst(LinkedList.java:518)
      at
  com.datamirror.ts.scrapers.sybasescraper.SybaseOperationLinker.p
  utEntry(SybaseOperationLinker.java:107)
      at
  com.datamirror.ts.scrapers.sybasescraper.SybaseLogParser.parseCo
  mmittedTxn(SybaseLogParser.java:274)
      at
  com.datamirror.ts.scrapers.cdc.LogParser.handleCommitEntry(LogPa
  rser.java:2440)
      at
  com.datamirror.ts.scrapers.cdc.LogParser.execute(LogParser.java:
  529)
      at
  com.datamirror.ts.scrapers.cdc.LogParser$LogParserPipelineJob.ex
  ecute(LogParser.java:145)
      at
  com.datamirror.ts.engine.component.PipelineThread.runThread(Pipe
  lineThread.java:205)
      at com.datamirror.ts.util.TsThread.run(TsThread.java:81)
  
  
  This issue affects users running ISCDC 6.5.1 Interim Fix 15 for
  Sybase (and below).
  

Problem conclusion

• This issue is fixed by applying ISCDC 6.5.1 Interim Fix 16 for
  Sybase.
  

Temporary fix

Comments

APAR Information

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

  JR47046

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

Fix information

• Fixed component name

  IS CDC SYBASE

• Fixed component ID

  5724U7006

Applicable component levels

• R651 PSY

     UP