|
Problem IC74555
|
Status: Closed |
DB2STOP FORCE MAY GET AN ADM14011C AND TRAP IN A FEDERATED ENVIRONMENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Db2stop force may get an ADM14011C and trap in a federated
environment.
You will see a similar message at
$INSTANCEHOME/sqllib/db2dump/db2diag.log as below when you hit
this problem.
...
2011-01-14-12.02.49.972360+540 E82678A1433 LEVEL:
Critical
PID : 15552 TID : 2199165856080PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:90
MESSAGE : ADM14011C A critical failure has caused the following
type of error:
"Trap". The DB2 database manager cannot recover from
the failure.
First Occurrence Data Capture (FODC) was invoked in
the following
mode: "Automatic". FODC diagnostic information is
located in the
following directory:
"/db2/db2dump/FODC_Trap_2011-01-14-12.02.43.841173/".
DATA #1 : Signal Number Recieved, 4 bytes
11
...
.
And the associated trap file
/db2/db2dump/FODC_Trap_2011-01-14-12.02.43.841173/15552.1.000.tr
ap.txt
will have a similar stack trace as below.
...
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x0000020005115BF6 ossDumpStackTrace + 0x0102
0x0000020005110E32 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00d2
0x00000200028424AE sqlo_trce + 0x0702
0x00000200028DB3F8 sqloEDUCodeTrapHandler + 0x016c
0x0000020008409DF0 address: 0x20008409df0
0x00000200015E65BC
_Z25sqleUCagentTrustedEduTermP15sql_static_dataP16sqloModuleHand
le
+ 0x009c
0x00000200014E5C42
_ZN14sqeAppServices17ForceApplicationsEP14sqeApplicationiP12SQLZ
_APP_HDLiii
+ 0x044a
0x0000020001421DC4
_Z15sqleForceAgentsiiP12SQLZ_APP_HDLP5sqlcaiii + 0x0110
0x00000200014E9960 _ZN14sqeAppServices16ExecuteStopForceEi +
0x027c
0x000000008000B336 _Z14sqleRunSysCtlrv + 0x10ba
0x000000008000FC94 _Z11sqleSysCtlrv + 0x00a4
...
There is a problem in sqleUCagentTrustedEduTerm() and it may not
handle "db2stop force" as expected.
Running queries will be rollbacked when hit this problem.
"db2stop force" will work without any error when a fix is
integrated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 FixPack 5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.02.2011
16.12.2011
16.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
