IBM Support

IC82190: DB2 CONNECTIONS BECOME CONSUMED AND NOT RELEASED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 becomes in-accessible.   Database connections are being
    created , and for some reason,  the connections are not being
    closed or released. Ultimately occupying a db2 connection
    until there are no more to be consumed.
    
    Once all available connections are consumed, TPC GUI may receive
    Alert messages, and DB2 delivers the error: SQL CODE: -1040N
    SQLSTATE: 57030.
    
    The maximum number of applications is already connected to the
    database.
    
    Explanation:
    The number of applications connected to the database is equal to
    the maximum value defined in the configuration file for the
    database.The command cannot be processed.
    
    
    RECREATE STEPS:
    
    
    Varies depending on environment. Check db2 for
    similiar errors if database goes offline and becomes
    in-accessible. Possible db alerts may generated to the
     TPC GUI.
    
    
    ________________________________________________________________
    
    DB2 Version used for Server: 9.5.5
    The defect is against component: 5608TPCD0
    Server/Manager build/release (TPC): 4.2.2.95
    Agent build/release (TPC): N/A
    Server/Manager (OS):  AIX 6.1
    Agent (OS):  N/A
    ________________________________________________________________
    
    Problem as described by customer:
    
    Recently we have been experiencing issues with the TPC database
    going offline/online.
     The Alert log in the TPC GUI is flooded with these messages.
     The only way to clear this condition is to restart DB2.
    DB2 produces the following message:
     SQL1040N SQLSTATE=57030
     The maximum number of applications is already connected to the
    database.
    
    Initial customer impact (low/med/high):  Med
    

Local fix

  • Contact Support
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: TPC 4.2.x users deploying Storage Resource   *
    *                 Agents                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 connections in use should not       *
    *                      increase after each Storage Resource    *
    *                      Agent deployment.  See ERROR            *
    *                      DESCRIPTION.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    -
    

Problem conclusion

  • The fix for this APAR is targeted for the following
    maintenance package:
    
    | fix pack | 4.2.2-TIV-TPC-FP0002 - target June 2012
    
    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 number

    IC82190

  • Reported component name

    TPC FOR DATA

  • Reported component ID

    5608TPCD0

  • Reported release

    422

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-23

  • Closed date

    2012-03-29

  • Last modified date

    2012-03-29

  • 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 FOR DATA

  • Fixed component ID

    5608TPCD0

Applicable component levels

  • R422 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SS8JB5","label":"Tivoli Storage Productivity Center for Data"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"422"}]

Document Information

Modified date:
19 September 2021