|
Problem IC69960
|
Status: Closed |
DB2STOP HANGS AFTER A TRAP HAS BEEN SUSTAINED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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 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. |
| 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 *
**************************************************************** |
| Local Fix: |
Issue the command db2stop -kill |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
V9.7 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.07.2010
11.11.2010
11.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
