DB2报SQLEX_UNEXPECTED_SYSERR错误解决

DB2报SQLEX_UNEXPECTED_SYSERR错误解决

偶然发现自己的DB2测试环境无法使用，打开老是报错，之前一直以为是db2audit报错

DB2数据库性能调整和优化(第1、2版) PDF

DB2数据库性能优化介绍

DB2  9.7 for Linux 5.4安装详细步骤

2013-12-19-23.19.10.388418+480 E829168G1400      LEVEL: Event
PID    : 6743                TID  : 3054496656  PROC : db2syscr
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1
START  : DB2 DBM
DATA #1 : Build Level, 128 bytes
Instance "db2inst1" uses "32" bits and DB2 code release "SQL09075"
with level identifier "08060107".
Informational tokens are "DB2 v9.7.0.5", "s111017", "IP23291", Fix Pack "5".
DATA #2 : System Info, 436 bytes
System: Linux marven 6 2 i686
CPU: total:1 online:1 Cores per socket:1 Threading degree per core:1
Physical Memory(MB): total:1011 free:161
Virtual  Memory(MB): total:3059 free:2209
Swap    Memory(MB): total:2048 free:2048
Kernel  Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:1024
                msgNumberOfHeaders:65536 msgMaxQueueSize:65536
                msgMaxSegmentSize:16 shmMax:1059983360 shmMin:1 shmIDs:4096
                shmSegments:4096 semMap:256000 semIDs:1024 semNum:256000
                semUndo:256000 semNumPerID:250 semOps:32 semUndoSize:20
                semMaxVal:32767 semAdjustOnExit:32767
Cur cpu time limit (seconds)  = 0xFFFFFFFF
Cur file size limit (bytes) = 0xFFFFFFFF
Cur data size (bytes)  = 0xFFFFFFFF
Cur stack size (bytes)  = 0x00A00000
Cur core size (bytes)  = 0x00000000
Cur memory size (bytes) = 0xFFFFFFFF
nofiles (descriptors)  = 0x00000800

2013-12-19-21.35.24.548881+480 I1899G343          LEVEL: Error
PID    : 5979                TID  : 3050367200  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditGetNodeNum, probe:13176
MESSAGE : ZRC=0x070F00B8=118423736=SQLO_NOT_FOUND
          "Environment/registry variable was not found."

2013-12-19-23.08.04.323645+480 I733636G904        LEVEL: Error
PID    : 6306                TID  : 3050825424  PROC : db2fm
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 Common, Generic Control Facility, GcfCaller::getState, probe:40
MESSAGE : ECF=0x9000028C=-1879047540=ECF_GCF_GCF_FUNCTION_TIMED_OUT
          Timeout occured while calling a GCF interface function
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0xB7D19809 /opt/ibm/db2/V9.7/lib32/libdb2osse.so.1 + 0xBE809
  [1] 0xB7D1AA78 ossLog + 0x96
  [2] 0xB7C0F249 _ZN9GcfCaller8getStateEP12GCF_PartInfojP11GCF_RetInfo + 0x7D
  [3] 0x0804C385 main + 0xBE1
  [4] 0x00299E9C __libc_start_main + 0xDC
  [5] 0x0804B721 __gxx_personality_v0 + 0x111
  [6] 0x00000000 ?unknown + 0x0
  [7] 0x00000000 ?unknown + 0x0
  [8] 0x00000000 ?unknown + 0x0
  [9] 0x00000000 ?unknown + 0x0

2013-12-19-23.08.04.324035+480 I734541G1101      LEVEL: Error
PID    : 6306                TID  : 3050825424  PROC : db2fm
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 Common, Generic Control Facility, GcfCaller::getState, probe:40
MESSAGE : ECF=0x90000292=-1879047534=ECF_GCF_SERVICE_FUNCTION_FAILED
          The GCF function ran properly but the service did not behave accordingly
CALLED  : DB2 Common, Generic Control Facility, gcf_reset
RETCODE : ECF=0x90000298=-1879047528=ECF_GCF_FAILURE
          Failure as reported through GCF standard (GCF_FAILURE)
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0xB7D19809 /opt/ibm/db2/V9.7/lib32/libdb2osse.so.1 + 0xBE809
  [1] 0xB7D1A94D ossLogRC + 0x4F
  [2] 0xB7C0F29F _ZN9GcfCaller8getStateEP12GCF_PartInfojP11GCF_RetInfo + 0xD3
  [3] 0x0804C385 main + 0xBE1
  [4] 0x00299E9C __libc_start_main + 0xDC
  [5] 0x0804B721 __gxx_personality_v0 + 0x111
  [6] 0x00000000 ?unknown + 0x0
  [7] 0x00000000 ?unknown + 0x0
  [8] 0x00000000 ?unknown + 0x0
  [9] 0x00000000 ?unknown + 0x0

2013-12-19-23.08.04.324259+480 I735643G987        LEVEL: Error
PID    : 6306                TID  : 3050825424  PROC : db2fm
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:180
MESSAGE : ECF=0x9000034B=-1879047349=ECF_FM_FAIL_TO_GETSTATE_GCF_FM
          Failed to get the state of the GCF fm module
CALLED  : DB2 Common, Generic Control Facility, GcfCaller::getState
DATA #1 : signed integer, 4 bytes
-1879047540
DATA #2 : unsigned integer, 4 bytes
0
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0xB7D19809 /opt/ibm/db2/V9.7/lib32/libdb2osse.so.1 + 0xBE809
  [1] 0xB7D1A995 ossLogRC + 0x97
  [2] 0x0804C4A0 main + 0xCFC
  [3] 0x00299E9C __libc_start_main + 0xDC
  [4] 0x0804B721 __gxx_personality_v0 + 0x111
  [5] 0x00000000 ?unknown + 0x0
  [6] 0x00000000 ?unknown + 0x0
  [7] 0x00000000 ?unknown + 0x0
  [8] 0x00000000 ?unknown + 0x0
  [9] 0x00000000 ?unknown + 0x0

2013-12-19-23.08.06.128837+480 I736631G267        LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditGetNodeNum, probe:13165
MESSAGE : ZRC=0xFFFFE871=-6031

2013-12-19-23.08.06.129059+480 I736899G337        LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditGetLogFileName, probe:13273
MESSAGE : ZRC=0x875C00CD=-2024013619=

          "Unexpected System Error"

2013-12-19-23.08.06.129150+480 I737237G351        LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditBufferManager::writeAuditBuffe, probe:809
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
          "Unexpected System Error"

2013-12-19-23.08.06.129255+480 I737589G350        LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditBufferManager::finalizeBuffer, probe:196
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
          "Unexpected System Error"

2013-12-19-23.08.06.129338+480 I737940G758        LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditData::logEvent, probe:1075
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
          "Unexpected System Error"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -1042  sqlerrml: 3
 sqlerrmc: 205
 sqlerrp : SQLEXADT
 sqlerrd : (1) 0x875C00CD      (2) 0x000000CD      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)      (6)   
          (7)      (8)      (9)      (10)        (11)   
sqlstate:     

2013-12-19-23.08.06.129439+480 I738699G1226      LEVEL: Error
PID    : 6314                TID  : 3050506464  PROC : db2set
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlexAuditData::logEvent, probe:1116
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
          "Unexpected System Error"
DATA #1 : String, 25 bytes
SQEX overwrote this SQLCA
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA    sqlcabc: 136  sqlcode: 0  sqlerrml: 0
 sqlerrmc:
sqlerrp : SQL09075
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)      (6)   
          (7)      (8)      (9)      (10)        (11)   
sqlstate:     
DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -1042  sqlerrml: 3
 sqlerrmc: 205
 sqlerrp : SQLEXADT
 sqlerrd : (1) 0x875C00CD      (2) 0x000000CD      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)      (6)   
          (7)      (8)      (9)      (10)        (11)   
sqlstate:     

2013-12-19-23.08.37.843147+480 I739926G703        LEVEL: Severe
PID    : 6326                TID  : 3051058896  PROC : db2fm
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -6031  sqlerrml: 4
 sqlerrmc: 1 10
 sqlerrp : SQLFRCFG
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)      (6)   
          (7)      (8)      (9)      (10)        (11)   
sqlstate:     

2013-12-19-23.08.53.067143+480 I740630G705        LEVEL: Severe
PID    : 6331                TID  : 1769360    PROC : db2diag
INSTANCE: db2inst1            NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -6031  sqlerrml: 4
 sqlerrmc: 1 10
 sqlerrp : SQLFRCFG
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)      (6)   
          (7)      (8)      (9)      (10)        (11)   
sqlstate:     

一直怀疑是db2audit的错误，但是删除了相关审计归档日志文件还是不成后来根据上面的信息是共享内核参数存在问题，另外之前修改了hostname.然后就不得不改下db2node.cfg中的hostname，然后数据库竟然正常了，这个错误得好好研究一番，DB2的错误真的是不好推断，有的时候真的束手无策，看来还有好多需要学习的地方。

本文永久更新链接地址：