DB2建nickname导致CRASH解决方法
nickname时导致DB2 CRASH的解决方法(Linux)
(注:DB2 II 已经改名为Websphere II)
在使用 II4O时，创建Wrapper, user mapping都没问题，但是，当创建nickname时，DB2 crash。
在db2diag.log 中，有如下信息:
2005-03-13-14.22.36.412133+480 E7747G606 LEVEL: Severe
PID : 19883 TID : 3007177376 PROC : db2agent
(SAMPLE)
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-14 APPID: GAC80471.NE04.00F483062900
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:10
MESSAGE : ADM0503C An unexpected internal processing error has occurred. ALL
DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.
.
.
.
2005-03-13-14.22.36.421935+480 I16005G624 LEVEL: Severe
PID : 19883 TID : 3007177376 PROC : db2agent
(SAMPLE)
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-14 APPID: GAC80471.NE04.00F483062900
MESSAGE : RDS UCINTFC: pStatementText =
DATA #1 : Hexdump, 59 bytes
0xB33849E0 : 4352 4541 5445 204E 4943 4B4E 414D 4520 CREATE NICKNAME
0xB33849F0 : 4442 3249 4E53 5431 2E4F 5241 4C4F 4341 DB2INST1.ORALOCA
0xB3384A00 : 4C20 464F 5220 5453 4831 2E44 4232 494E L FOR TSH1.DB2IN
0xB3384A10 : 5354 312E 224C 4F43 414C 22 ST1."LOCAL"
.
.
.
2005-03-13-14.22.36.476913+480 I39423G431 LEVEL: Severe
PID : 19824 TID : 3007177376 PROC : db2tcpcm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler, probe:50
DATA #1 : String, 158 bytes
Detected the death of an EDU with process id 19883
The signal number that terminated this process was 11
Look for trap files (t19883.*) in the dump directory |
检查trap文件， t19883.000, 在 call stack，会发现:
|
