IC86382: INFOSPHERE CDC FOR SOLIDDB SHUTS DOWN WITH SOLIDDB TRANSACTION TIMEOUT ERROR 10026

6.5 Fix Pack 11 download information for solidDB and solidDB Universal Cache

APAR status

• Closed as program error.

Error description

• In a solidDB Universal Cache setup with long transaction idle
  periods, InfoSphere for solidDB shuts down due to a solidDB
  server transaction time out, even though the
  solid_idle_timeout_min JDBC connection property has been set to
  0 when creating the InfoSphere CDC for solidDB instance.
  
  The following type of error is output to the InfoSphere CDC for
  solidDB log:
  
  Error event (id=2903) logged for subscription
  (name=SHAREDSCRAPE;evtAgtType=SOURCE): An exception has occurred
  in the log parser. A SQL exception has occurred. The SQL error
  code is '10026'. The SQL state is: HY000. The error message is:
  [Solid JDBC 6.5.0.8 Build 2011-12-02] SOLID Database Error
  10026: Transaction is timed out
  
  Thread ID: 169
  Thread Name: SHAREDSCRAPE LOG PARSER
  
  java.sql.SQLException: [Solid JDBC 6.5.0.8 Build 2011-12-02]
  SOLID Database Error 10026: Transaction is timed out
   at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown
  Source)
   at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown
  Source)
   at solid.jdbc.SolidPreparedStatement.s_exec(Unknown Source)
   at solid.jdbc.SolidPreparedStatement.executeQuery(Unknown
  Source)
   at
  com.datamirror.ts.jdbc.CdcPreparedStatement.executeQuery(CdcPrep
  aredStatement.java:170)
   at
  com.datamirror.ts.jdbc.CdcJdbcPreparedStatement.executeQuery(Cdc
  JdbcPreparedStatement.java:133)
   at
  com.datamirror.ts.scrapers.solidscraper.SolidLogParser.getTsRefr
  eshId(SolidLogParser.java:918)
   at
  com.datamirror.ts.scrapers.solidscraper.SolidLogParser.parseComm
  ittedTxn(SolidLogParser.java:171)
   at
  com.datamirror.ts.scrapers.cdc.LogParser.handleCommitEntry(LogPa
  rser.java:2223)
   at
  com.datamirror.ts.scrapers.cdc.LogParser.execute(LogParser.java:
  509)
   at
  com.datamirror.ts.scrapers.cdc.LogParser$LogParserPipelineJob.ex
  ecute(LogParser.java:140)
   at
  com.datamirror.ts.engine.component.PipelineThread.runThread(Pipe
  lineThread.java:205)
   at com.datamirror.ts.util.TsThread.run(TsThread.java:81)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Universal Cache and InfoSphere CDC replication users.    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IBM InfoSphere Change Data Capture solidDB        *
  * 6.5.0.11 Fix Pack 11.                                        *
  ****************************************************************
  

Problem conclusion

• Fix is included in IBM InfoSphere Change Data Capture solidDB
  6.5.0.11 Fix Pack 11.
  
  The solidDB server timed out in cases where InfoSphere CDC for
  solidDB accessed database metadata without issuing commits or
  rollbacks with the transaction. With the fix, commits or
  rollbacks are now issued as necessary.
  

Temporary fix

Comments

APAR Information

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

  IC83071

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

Fix information

• Fixed component name

  SOLIDDB-DB2/IDS

• Fixed component ID

  5724V1700

Applicable component levels

• R650 PSY

     UP

• R700 PSY

     UP