互联网服务
SQL1042C 发生了意外的系统错误。SQLSTATE=58004 问题请教
SELECT * FROM SYSIBMADM.SNAPTBSP_PART WITH UR;
[IBM][CLI Driver][DB2/AIX64] SQL1042C 发生了意外的系统错误。 SQLSTATE=58004
db2diag
2012-07-30-15.09.28.779121+480 I40927719A515 LEVEL: Severe
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerAddFmpToPool, probe:20
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6600 : FFFF FBEE ....
2012-07-30-15.12.25.386176+480 I40928235A742 LEVEL: Error
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : Warning! No segment was created for running fenced routines.
DB2_FMP_COMM_HEAPSZ is set to 0. This means no fmps (including Health
Monitor) and automatic maintenance features of DB2 will be started.
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6320 : 0000 0000 ....
2012-07-30-15.12.25.386402+480 E40928978A597 LEVEL: Warning
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : ADM11001E DB2 did not create a memory segment for running fenced
routines. This was specified by the use of DB2_FMP_COMM_HEAPSZ
registry variable.
2012-07-30-15.12.25.386694+480 I40929576A515 LEVEL: Severe
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerAddFmpToPool, probe:20
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6600 : FFFF FBEE
[IBM][CLI Driver][DB2/AIX64] SQL1042C 发生了意外的系统错误。 SQLSTATE=58004
db2diag
2012-07-30-15.09.28.779121+480 I40927719A515 LEVEL: Severe
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerAddFmpToPool, probe:20
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6600 : FFFF FBEE ....
2012-07-30-15.12.25.386176+480 I40928235A742 LEVEL: Error
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : Warning! No segment was created for running fenced routines.
DB2_FMP_COMM_HEAPSZ is set to 0. This means no fmps (including Health
Monitor) and automatic maintenance features of DB2 will be started.
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6320 : 0000 0000 ....
2012-07-30-15.12.25.386402+480 E40928978A597 LEVEL: Warning
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : ADM11001E DB2 did not create a memory segment for running fenced
routines. This was specified by the use of DB2_FMP_COMM_HEAPSZ
registry variable.
2012-07-30-15.12.25.386694+480 I40929576A515 LEVEL: Severe
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerAddFmpToPool, probe:20
DATA #1 : Hexdump, 4 bytes
0x07000001B2FF6600 : FFFF FBEE
3同行回答
0x07000001B2FF6320 : 0000 0000 ....
2012-07-30-15.12.25.386402+480 E40928978A597 LEVEL: Warning
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : ADM11001E DB2 did not create a memory segment for running fenced
routines. This was specified by the use of DB2_FMP_COMM_HEAPSZ
registry variable
db2set -all . check the current value of DB2_FMP_COMM_HEAPSZ
Below are common example calculations:
- DB2 LUW v9.5 on AIX, DB2_FMP_COMM_HEAPSZ is not set (default 256M), ASLHEAPSZ=15 (default)
256M / (2 * 15 * 4K) = # db2fmp processes + # db2fmp threads
(268435456 bytes) / (2 * 15 * 4096 bytes) = 2184.53
In this particular case, the current setting should be able to accommodate approximately 2184 db2fmp processes and threads combined.
- DB2 LUW v9.5 on non-AIX, DB2_FMP_COMM_HEAPSZ is not set (default 20 MB, or enough space to run 10 fenced routines (whichever is larger)), ASLHEAPSZ=15 (default)
20M / (2 * 15 * 4K) = # db2fmp processes + # db2fmp threads
(20971520 bytes) / (2 * 15 * 4096 bytes) = 170.66
In this particular case, the current setting should be able to accommodate approximately 170 db2fmp processes and threads combined.
- DB2 LUW v9.5, DB2_FMP_COMM_HEAPSZ set to a specific value such as DB2_FMP_COMM_HEAPSZ=10000, ASLHEAPSZ=15
In this case both DB2_FMP_COMM_HEAPSZ and ASLHEAPSZ are both measured in 4K pages, so the calculation is as follows:
10000 / (2 * 15) = 333.33
In this particular case, the current setting should be able to accommodate approximately 333 db2fmp processes and threads combined.收起
2012-07-30-15.12.25.386402+480 E40928978A597 LEVEL: Warning
PID : 635292 TID : 31139 PROC : db2sysc 0
INSTANCE: db2admin NODE : 000 DB : DATAIRSS
APPHDL : 0-44160 APPID: 192.168.20.31.17873.12073005525
AUTHID : DB2ADMIN
EDUID : 31139 EDUNAME: db2agent (DATAIRSS) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFMPIPC, probe:35
MESSAGE : ADM11001E DB2 did not create a memory segment for running fenced
routines. This was specified by the use of DB2_FMP_COMM_HEAPSZ
registry variable
db2set -all . check the current value of DB2_FMP_COMM_HEAPSZ
Below are common example calculations:
- DB2 LUW v9.5 on AIX, DB2_FMP_COMM_HEAPSZ is not set (default 256M), ASLHEAPSZ=15 (default)
256M / (2 * 15 * 4K) = # db2fmp processes + # db2fmp threads
(268435456 bytes) / (2 * 15 * 4096 bytes) = 2184.53
In this particular case, the current setting should be able to accommodate approximately 2184 db2fmp processes and threads combined.
- DB2 LUW v9.5 on non-AIX, DB2_FMP_COMM_HEAPSZ is not set (default 20 MB, or enough space to run 10 fenced routines (whichever is larger)), ASLHEAPSZ=15 (default)
20M / (2 * 15 * 4K) = # db2fmp processes + # db2fmp threads
(20971520 bytes) / (2 * 15 * 4096 bytes) = 170.66
In this particular case, the current setting should be able to accommodate approximately 170 db2fmp processes and threads combined.
- DB2 LUW v9.5, DB2_FMP_COMM_HEAPSZ set to a specific value such as DB2_FMP_COMM_HEAPSZ=10000, ASLHEAPSZ=15
In this case both DB2_FMP_COMM_HEAPSZ and ASLHEAPSZ are both measured in 4K pages, so the calculation is as follows:
10000 / (2 * 15) = 333.33
In this particular case, the current setting should be able to accommodate approximately 333 db2fmp processes and threads combined.收起
浏览1891