|
Problem IC75300
|
Status: Closed |
DB2 CONNECT GATEWAY MAY END ABNORMALLY AFTER CONTINUOUS NETWORK ERRORS. |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
The DB2 Connect gateway may end abnormally with an ADM0502C
error after
the continuous occurrence of TCP/IP error, DIA3202C.
The following is an example of the db2diag.log messages that
might be recorded for
this issue.
2011-03-04-16.19.19.242279+540 I35277120G409 LEVEL: Error
PID : 6242 TID : 2121264016 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-44088
EDUID : 729 EDUNAME: db2agentg (DBNAME)
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr,
probe:110
MESSAGE : DIA3202C The TCP/IP call "connect" returned an
errno="111".
2011-03-04-16.19.36.652577+540 E35277530G561 LEVEL: Severe
PID : 6242 TID : 2121264016 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-44088
EDUID : 729 EDUNAME: db2agentg (DBNAME)
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:10
MESSAGE : ADM0502C The DB2 instance has terminated abnormally.
To remedy this
problem, increase the AGENT_STACK_SZ DBM configuration
parameter.
Contact IBM Support for further assistance.
The following kind of stack trace could be observed for this
issue.
<StackTrace>
--Frame--- ------Function + Offset------
0x7E611010
_ZN13SQLO_MEM_POOL10MemTreeGetEjjPPvPP17SqloChunkSubgroupPP12SMe
mLostNode
+ 0x0029
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E611058
_ZN13SQLO_MEM_POOL19allocateMemoryBlockEjjjjjPPvPP17SqloChunkSub
groupPP12SMemLostNodeP12SMemLogEvent
+ 0x007d
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E611F18 sqlogmblkEx + 0x0366
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E611F4C address: 0xB476A955 ; dladdress: 0xB351A000 ; offset
in lib: 0x01250955 ;
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E611F68 _Z8sqledaccP8SQLE_BWAc + 0x0052
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E611FC0 _Z7sqledrdP8SQLE_BWA + 0x0031
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E6177E0 _Z19sqleGetActiveServerPcP10tcpip_addr. + 0x0094
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E6177FC
_Z24sqleGetCurrentServerInfoP14db2UCinterfaceP10tcpip_addrPbb +
0x0061
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E617964 _Z26sqljrConnectBasedOnCatalogP14db2UCconHandlePibPb
+ 0x00f3
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E6202A0 _Z20sqljrInternalConnectP14db2UCconHandlePbPib +
0x08eb
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E6202D0 _Z30sqljrFindBestAddressAndConnectP14db2UCconHandle +
0x0053
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E6202F8 _Z23sqljrDrdaArAuthenticateP14db2UCinterfaceiPj +
0x04e4
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E620334 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + 0x0089
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E620364 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + 0x00d5
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
0x7E620394 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + 0x00d5
(/home/db2inst1/sqllib/lib32/libdb2e.so.1)
<snippet> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using DB2 Connect Gateway. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The DB2 Connect gateway may end abnormally with an ADM0502C *
* error after *
* the continuous occurrence of TCP/IP error, DIA3202C. *
* *
* *
* The following is an example of the db2diag.log messages that *
* might be recorded for *
* this issue. *
* *
* 2011-03-04-16.19.19.242279+540 I35277120G409 LEVEL: *
* Error *
* PID : 6242 TID : 2121264016 PROC : *
* db2sysc *
* INSTANCE: db2inst1 NODE : 000 DB : DBNAME *
* APPHDL : 0-44088 *
* EDUID : 729 EDUNAME: db2agentg (DBNAME) *
* FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, *
* probe:110 *
* MESSAGE : DIA3202C The TCP/IP call "connect" returned an *
* errno="111". *
* *
* 2011-03-04-16.19.36.652577+540 E35277530G561 LEVEL: *
* Severe *
* PID : 6242 TID : 2121264016 PROC : *
* db2sysc *
* INSTANCE: db2inst1 NODE : 000 DB : DBNAME *
* APPHDL : 0-44088 *
* EDUID : 729 EDUNAME: db2agentg (DBNAME) *
* FUNCTION: DB2 UDB, oper system services, *
* sqloEDUCodeTrapHandler, *
* probe:10 *
* MESSAGE : ADM0502C The DB2 instance has terminated *
* abnormally. *
* To remedy this *
* problem, increase the AGENT_STACK_SZ DBM *
* configuration *
* parameter. *
* Contact IBM Support for further assistance. *
* *
* The following kind of stack trace could be observed for this *
* issue. *
* *
* <StackTrace> *
* --Frame--- ------Function + Offset------ *
* 0x7E611010 *
* _ZN13SQLO_MEM_POOL10MemTreeGetEjjPPvPP17SqloChunkSubgroupPP1 *
* 2SMe *
* mLostNode *
* + 0x0029 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E611058 *
* _ZN13SQLO_MEM_POOL19allocateMemoryBlockEjjjjjPPvPP17SqloChun *
* kSub *
* groupPP12SMemLostNodeP12SMemLogEvent *
* + 0x007d *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E611F18 sqlogmblkEx + 0x0366 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E611F4C address: 0xB476A955 ; dladdress: 0xB351A000 ; *
* offset *
* in lib: 0x01250955 ; *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E611F68 _Z8sqledaccP8SQLE_BWAc + 0x0052 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E611FC0 _Z7sqledrdP8SQLE_BWA + 0x0031 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E6177E0 _Z19sqleGetActiveServerPcP10tcpip_addr. + 0x0094 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E6177FC *
* _Z24sqleGetCurrentServerInfoP14db2UCinterfaceP10tcpip_addrPb *
* b + *
* 0x0061 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E617964 *
* _Z26sqljrConnectBasedOnCatalogP14db2UCconHandlePibPb *
* + 0x00f3 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E6202A0 _Z20sqljrInternalConnectP14db2UCconHandlePbPib + *
* 0x08eb *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E6202D0 *
* _Z30sqljrFindBestAddressAndConnectP14db2UCconHandle + *
* 0x0053 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E6202F8 _Z23sqljrDrdaArAuthenticateP14db2UCinterfaceiPj + *
* 0x04e4 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E620334 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + *
* 0x0089 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E620364 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + *
* 0x00d5 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* 0x7E620394 _Z14sqlexGwCRRetryP20SQLEX_GW_WORK_AREA_TiPj + *
* 0x00d5 *
* (/home/db2inst1/sqllib/lib32/libdb2e.so.1) *
* *
* <snippet> *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Increasing the agent stack size. |
| 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 |
The issue was fixed in V9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.03.2011
08.12.2011
08.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
|
 |
