DB2启动故障案例一

数据库无法正常启动故障分析

 

数据库版本："DB2 v8.1.11. 

 

OS:win2003

 

基本情况描述： 开发人员清除磁盘空间后，当重新启动数据库时，无法正常启动，具体信息忘记了。

2009-09-24-11.54.09.953000+480 I1H931             LEVEL: Event
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
START   : New db2diag.log file
DATA #1 : Build Level, 124 bytes
Instance "DB2" uses "32" bits and DB2 code release "SQL08024"
with level identifier "03050106".
Informational tokens are "DB2 v8.1.11.973", "s060120", "WR21365", FixPak "11".
DATA #2 : System Info, 1564 bytes
System: WIN32_NT AVIVA-9WY6H3VF8 Service Pack 1 5.2 x86 Family 15, model 3, stepping 4
CPU: total:2 online:2 Cores per socket:1 Threading degree per core:2
Physical Memory(MB): total:2047 free:1033 available:1033
Virtual  Memory(MB): total:4972 free:4749
Swap     Memory(MB): total:2925 free:3716
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2009-09-24-11.54.09.953000+480 I935H1528          LEVEL: Event
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 30 bytes
C:\IBM\SQLLIB\bin\DB2STAR2.EXE
DATA #2 : Hexdump, 256 bytes
0x0012A8B8 : 433A 5C49 424D 5C53 514C 4C49 425C 6269    C:\IBM\SQLLIB\bi
0x0012A8C8 : 6E5C 4442 3253 5441 5232 2E45 5845 0000    n\DB2STAR2.EXE..
0x0012A8D8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A8E8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A8F8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A908 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A918 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A928 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A938 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A948 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A958 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A968 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A978 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A988 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A998 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0012A9A8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................

2009-09-24-11.55.51.140000+480 I2465H683          LEVEL: Severe
PID     : 5900                 TID  : 4472        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:60
MESSAGE : Failed to create the memory segment used for communication with
          fenced routines. If re-starting db2, ensure no db2fmp processes were
          on the instance prior to start. Otherwise, you can ajust this value
          through DB2_FMP_COMM_HEAPSZ db2set value, or by decreasing your
          ASLHEAPSZ setting.
DATA #1 : Hexdump, 4 bytes
0x0122FADC : 8084 5E01                                  ..^.

2009-09-24-11.55.51.140000+480 E3150H678          LEVEL: Error
PID     : 5900                 TID  : 4472        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:60
MESSAGE : ADM11003E  DB2 failed to create the memory segment used for
          communication with fenced routines. If restarting DB2, ensure that no
          db2fmp processes are active on the instance prior to start. Otherwise,
          you can adjust the value through the DB2_FMP_COMM_HEAPSZ registry
          variable, or you can decrease the value of ASLHEAPSZ in the database
          manager configuration.

2009-09-24-11.55.51.156000+480 I3830H357          LEVEL: Severe
PID     : 5900                 TID  : 4472        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:80
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0122FDDC : EEFB FFFF                                  ....

2009-09-24-11.55.51.156000+480 I4189H348          LEVEL: Severe
PID     : 5900                 TID  : 4472        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:115
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0122FF94 : EEFB FFFF                                  ....

2009-09-24-11.55.51.171000+480 I4539H359          LEVEL: Severe
PID     : 5900                 TID  : 2012        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0006FD30 : 0000 0000                                  ....

2009-09-24-11.55.51.171000+480 I4900H435          LEVEL: Severe
PID     : 5900                 TID  : 2012        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:10
MESSAGE : DiagData
DATA #1 : Hexdump, 20 bytes
0x00413DC8 : 496E 7374 616E 6365 206E 6F74 2061 6374    Instance not act
0x00413DD8 : 6976 6500                                  ive.

2009-09-24-11.55.51.406000+480 I5337H492          LEVEL: Error
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloStartDB2Service, probe:50
DATA #1 : Hexdump, 39 bytes
0x00129BA4 : 4442 3220 3A20 B7FE CEF1 D2D1 B7B5 BBD8    DB2 : ..........
0x00129BB4 : CCD8 B6A8 B5C4 B7FE CEF1 B4ED CEF3 B4FA    ................
0x00129BC4 : C2EB A1A3 0D0A 0A                          .......

2009-09-24-11.55.51.406000+480 I5831H515          LEVEL: Severe
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:70
MESSAGE : DiagData
DATA #1 : Hexdump, 39 bytes
0x0012A278 : 4442 3220 3A20 B7FE CEF1 D2D1 B7B5 BBD8    DB2 : ..........
0x0012A288 : CCD8 B6A8 B5C4 B7FE CEF1 B4ED CEF3 B4FA    ................
0x0012A298 : C2EB A1A3 0D0A 0A                          .......

2009-09-24-11.55.51.406000+480 I6348H357          LEVEL: Error
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlex_read_aud_cfg, probe:20
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.

2009-09-24-11.55.51.406000+480 I6707H305          LEVEL: Error
PID     : 1044                 TID  : 5164        PROC : db2start.exe
INSTANCE: DB2                  NODE : 000
MESSAGE : Audit error.  sqlcode is:
DATA #1 : Hexdump, 4 bytes
0x0012E774 : EEFB FFFF                                  ....

查看日志信息，提示审计配置文件找不到和无法创建内存段。

 

恢复db2audit.cfg配置文件。重启数据库，依然无法启动，提示错误信息相同，只是少了

FUNCTION: DB2 UDB, bsu security, sqlex_read_aud_cfg, probe:20
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.

 

根据这种情况，很可能是无法创建内存段导致数据库不能正常启动，重新启动主机，数据库可以

正常启动。