IBM Support

IT00778: NEW SESSIONS CANNOT BE OPENED TO A SUBSCRIBER SERVER, DUE TO OPEN TRANSACTIONS IN DB2 NOT BEING CLOSED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • New sessions cannot be opened to a subscriber server, due to
    open transactions in DB2 not being closed
    
    Problem Description:
    
    In a Tivoli Storage Manager Enterprise Environment, a subscriber
    server can eventually run out of
    semaphores due to "pings" from the configuration manager.
    
    When the configuration server "pings" the subscriber it opens a
    transaction and never closes it.
    This results in applications in DB2, which can eventually hit
    the semaphore limit.
    The transactions can still be seen in the Tivoli Storage Manager
    server, but the associated thread IDs no longer exist.
    
    Once the semaphore limit has been exhausted, new sessions to the
    subscriber server can not be opened.
    
    
    Customer/L2 Diagnostics:
    
    ipcs -u     (on Unix platform)
    
    will show the used and allocated arrays
    
    For example from the output:
    
    ------ Semaphore Status --------
    used arrays = xxxx
    allocated semaphores = yyyy
    
    If used arrays equals allocated semaphores, no more transactions
    can be opened.
    
    When the semaphores are exhausted db2diag.log will report this
    type of error:
    
    014-02-12-17.08.03.732001+060 I317996A472          LEVEL: Severe
    ID     : 2549                 TID : 4397752903952  PROC :
    db2sysc 0
    NSTANCE: tsminst1             NODE : 000
    OSTNAME: vlzdsm4p.cs.shb.se
    DUID   : 16                   EDUNAME: db2ipccm 0
    UNCTION: DB2 UDB, common communication, sqlccGetIPCs, probe:50
    ETCODE : ZRC=0x850F0081=-2062614399=SQLO_SSEM_EXCEED_MAX
             "Requesting too many semaphores"
             DIA8336C Requested too many semaphores.
    
    
    
    
    There will be many entries in "SHOW TXNT" output like this one:
    
     Tsn=0:1794, Resurrected=False, InFlight=True,
    Distributed=False, Persistent=True, Addr 0x3ffe017e0d8
       Start ThreadId=136, Timestamp=03/27/2014 08:21:17 PM,
    Creator=smcc.c(2544)
       Last known in use by ThreadId=136
       Participants=1, summaryVote=ReadOnly
       EndInFlight False, endThreadId 0, tmidx 0, processBatchCount
    0, mustAbort False.
         Participant DB: voteReceived=False, ackReceived=False
           DB: Txn 0x3ffe0144348, ReadOnly(YES),
    connP=0x3ffe0169c58, applHandle=814, openTbls=2:
           DB: --> OpenP=0x3ffe0188c58 for table=Server.Connect.
           DB: --> OpenP=0x3ffe0181888 for
    table=Server.Connect.Info.
    
    In this example the thread ID is 136.
    
    Looking at the "SHOW THREADS" there was no thread ID 136.
    
    Many threads will be in this state.
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager server version 6.2.x, 6.3.x and 7.1.0 on
    all supported platforms
    
    Initial Impact: Medium
    
    Additional Keywords: zz62 zz63 zz71 connection subscriber ping
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.3.5 and 7.1.1. Note that this is *
    *                                                              *
    *                 subject to change at the discretion of IBM.  *
    ****************************************************************
    *
    

Problem conclusion

  • This problem was fixed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT00778

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-04

  • Closed date

    2014-04-18

  • Last modified date

    2014-04-18

  • 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

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R62A PSY

       UP

  • R62H PSY

       UP

  • R62L PSY

       UP

  • R62S PSY

       UP

  • R62W PSY

       UP

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 71L

Reference #: IT00778

Modified date: 18 April 2014