IBM Support

IC69960: DB2STOP HANGS AFTER A TRAP HAS BEEN SUSTAINED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the event that a DB2 ESE instance has encountered a
    sustainable trap, subsequent issuance of db2stop or db2stop
    force may fail or hang.
    
    Issuing db2stop may result in the following message:
    
    SQL1025N  The database manager was not stopped because databases
    are still active.
    
    Issuing db2stop force will result in a hang.
    
    A user can check the db2diag.log for the message ADM14013C to
    determine if , prior to issuing db2stop, a sustained trap has
    
    occurred.
    
    Alternatively, to detect if there was any trap suspended db2
    agent, run
    the command:
    
    db2pdcfg -trapresilience
    
    or
    
    db2pdcfg -tra
    
    Example output from this command is as follows:
    
    db2pdcfg -trapresilience
    DB2 trap resilience is enabled.
       Current threshold setting:    0 ( disabled )
       Number of traps sustained:   1
    
    
    If "Number of traps sustained" is greater than zero then the
    Local Fix supplied should be used to stop the instance or the
    fix to this APAR should be applied to the system.
    

Local fix

  • Issue the command db2stop -kill
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * V9.7 GA, V9.7 FP1, V9.7 FP2                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In the event that a DB2 ESE instance has encountered a       *
    *                                                              *
    * sustainable trap, subsequent issuance of db2stop or db2stop  *
    *                                                              *
    * force may fail or hang.                                      *
    *                                                              *
    *                                                              *
    *                                                              *
    * Issuing db2stop may result in the following message:         *
    *                                                              *
    *                                                              *
    *                                                              *
    * SQL1025N  The database manager was not stopped because       *
    * databases                                                    *
    * are still active.                                            *
    *                                                              *
    *                                                              *
    *                                                              *
    * Issuing db2stop force will result in a hang.                 *
    *                                                              *
    *                                                              *
    *                                                              *
    * A user can check the db2diag.log for the message ADM14013C   *
    * to                                                           *
    * determine if , prior issuing db2stop, a sustained trap has   *
    *                                                              *
    * occurred.                                                    *
    *                                                              *
    *                                                              *
    *                                                              *
    * Alternatively, to detect if there was any trap suspended,    *
    * run                                                          *
    * the command:                                                 *
    *                                                              *
    *                                                              *
    *                                                              *
    * db2pdcfg -trapresilience                                     *
    *                                                              *
    *                                                              *
    *                                                              *
    * or                                                           *
    *                                                              *
    *                                                              *
    *                                                              *
    * db2pdcfg -tra                                                *
    *                                                              *
    *                                                              *
    *                                                              *
    * Example output from this command is as follows:              *
    *                                                              *
    *                                                              *
    *                                                              *
    * db2pdcfg -trapresilience                                     *
    *                                                              *
    * DB2 trap resilience is enabled.                              *
    *                                                              *
    *   Current threshold setting:    0 ( disabled )               *
    *                                                              *
    *   Number of traps sustained:  1                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * If "Number of traps sustained" is greater than zero then the *
    *                                                              *
    * Local Fix supplied should be used to stop the instance or    *
    * the                                                          *
    * fix to this APAR should be applied to the system.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Local fix or upgrade to V97 FP3                              *
    ****************************************************************
    

Problem conclusion

  • V9.7 FP3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC69960

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-15

  • Closed date

    2010-11-11

  • Last modified date

    2010-11-11

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

  • R970 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
11 November 2010