IC88163: TPC API IS THROWING EXCEPTION NOW BECAUSE IT CAN'T CONNECT TO THE DATABASE.

4.2.2 Fix Pack 7 (July 2014) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 8 (March 2015) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 9 (May 2015) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 10 (August 2015) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• TPC is creating numerous database connections and now it is
  stuck with full connections to the database.
  Every TPC API is throwing exception now because it can't
  connect to the database.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: TPC 4.2.2.143 (FP3) and older,               *
  *                 particularly those using it with IBM         *
  *                 Systems Director                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: TPC jobs fail after running for a       *
  *                      while.                                  *
  *                                                              *
  *                      ----------------------                  *
  *                      SystemError.log                         *
  *                      dbtrace.log                             *
  *                      msgTPCDeviceServer.log                  *
  *                      ----------------------                  *
  *                      The primary exception in these files    *
  *                      report SQL1040N (http://ibm.co/PMpwWu)  *
  *                                                              *
  *                      com.ibm.db2.jcc.b.SqlException: DB2     *
  *                      SQL error: SQLCODE: -1040, SQLSTATE:    *
  *                      57030, SQLERRMC: null                   *
  *                                                              *
  *                      This error indicates the maximum        *
  *                      number of applications is already       *
  *                      connected to the database.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Connections leaked from testStorageSubsystem() call.
  

Problem conclusion

• Database connection leak was fixed.  The fix for this APAR is
  targeted for the following maintenance package:
  
  | fix pack | 4.2.2-TIV-TPC-FP0004 - target 2013
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future fix packs do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  

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

  TPC STANDARD ED

• Fixed component ID

  5608TPCS0

Applicable component levels

• R422 PSY

     UP