JR63609: CDC FOR ORACLE (REDO) CONNECTION LEAK CAN OCCUR DURING METADATA MIGRATION

APAR status

• Closed as program error.

Error description

• CDC for Oracle (Redo) migration process can abort with
  ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit, if
  the instance has many published tables.
  
  For example:
  
  main{1}	c
  om.datamirror.ts.metadata.migration.Migration229	migrate()	V228
  to V229 migration started.
  
  main{1}	com.datamirror.ts.util.TsEnv
  ironment	openCustomerDatabaseConnection()	A SQL exception has
  occurred. The SQL error code is '2391'. The SQL state is:
  HY000. The error message is: |[CDC][Oracle JDBC
  Driver][Oracle]ORA-02391: exceeded simultaneous
  SESSIONS_PER_USER
  limit|?com.ibm.replication.jdbc.oraclebase.ddd6 [CDC][Oracle
  JDBC Driver][Oracle]ORA-02391: exceeded simultaneous
  SESSIONS_PER_USER limit|| at
  com.ibm.replication.jdbc.oraclebase.ddcj.a(Unknown Source)| at
  com.ibm.replication.jdbc.oraclebase.ddcj.b(Unknown Source)| at
  com.ibm.replication.jdbc.oraclebase.ddcj.a(Unknown Source)| at
  com.ibm.replication.jdbc.oraclebase.ddcj.a(Unknown Source)| at
  com.ibm.replication.jdbc.oracle.OracleImplConnection.b(Unknown
  Source)| at
  com.ibm.replication.jdbc.oracle.OracleImplConnection._(Unknown
  Source)| at
  com.ibm.replication.jdbc.oraclebase.BaseConnection.b(Unknown
  Source)| at
  com.ibm.replication.jdbc.oraclebase.BaseConnection.l(Unknown
  Source)| at
  com.ibm.replication.jdbc.oraclebase.ddae.run(Unknown Source)
  

Local fix

• Workaround:
  Increase Oracle SESSIONS_PER_USER limit for the CDC
  database user to the number of in-scope (published) tables for
  the CDC instance
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue may affect you if you upgraded to IDR             *
  * 11.4.0.3-5594 or older for Oracle.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When you start an instance following an upgrade, metadata    *
  * migration happens. This was failing.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.3-5596 or newer for Oracle.            *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.3-5596 or newer for Oracle resolves the
  issue.
  

Temporary fix

Comments

APAR Information

• 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

  5725E30OR

Applicable component levels