Db2 issue on HP UX

Former Member · ‎04-20-2009

Hi ,

We are having SAP on High Availability landscape . . Now the issue is that the db2 goes down after 5 or 6 hours .. i have to manually restart db2 on Db Server .

please find below the log file

dew:db2vbp 17> tail -n 250 db2diag.log

PID : 5735 TID : 1 PROC : db2acd 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2acd 0

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2009-04-20-12.17.39.317392+330 I1092950985A414 LEVEL: Error

PID : 5735 TID : 4 PROC : db2acd 0

INSTANCE: db2vbp NODE : 000

EDUID : 4 EDUNAME: db2acd 0

FUNCTION: DB2 UDB, Health Monitor, hmonMainLoop, probe:50

MESSAGE : Internal Health monitor error

DATA #1 : Hexdump, 4 bytes

0x9FFFFFFFBD5C0C30 : 9000 000C ....

2009-04-20-12.17.39.401431+330 I1092951400A425 LEVEL: Severe

PID : 5735 TID : 1 PROC : db2acd 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2acd 0

FUNCTION: DB2 UDB, Health Monitor, hmonStopMainHmonThread, probe:30

MESSAGE : Internal Health monitor error

DATA #1 : Hexdump, 4 bytes

0x9FFFFFFFFFFFF300 : 9000 000C ....

2009-04-20-12.21.54.392731+330 I1092951826A1642 LEVEL: Event

PID : 10651 TID : 1 PROC : db2start

INSTANCE: db2vbp NODE : 000

EDUID : 1

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2vbp/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x9FFFFFFFFFFF78B0 : 2F64 6232 2F64 6232 7662 702F 7371 6C6C /db2/db2vbp/sqll

0x9FFFFFFFFFFF78C0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x9FFFFFFFFFFF78D0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x9FFFFFFFFFFF78E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF78F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7900 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7910 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7920 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7930 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7940 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7950 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7960 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7970 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7980 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF7990 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x9FFFFFFFFFFF79A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2009-04-20-12.21.55.244567+330 I1092953469A531 LEVEL: Event

PID : 10656 TID : 1 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2sysc 0

FUNCTION: DB2 UDB, fast comm manager, sqkfBufferManager::initBufferManager, prob

e:10

START : Starting FCM Buffer Manager

1 resource group(s).

128 buffers allocated.

Maximum number of buffers supported is 8192.

Total buffer manager memory required for 1 logical and 0 fail-over partition(s)

is 925712 bytes.

2009-04-20-12.21.55.246983+330 I1092954001A538 LEVEL: Event

PID : 10656 TID : 1 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2sysc 0

FUNCTION: DB2 UDB, fast comm manager, sqkfChannelManager::initChannelManager, pr

obe:10

START : Starting FCM Channel Manager

1 resource group(s).

128 channels allocated.

Maximum number of channels supported is 8192.

Total channel manager memory required for 1 logical and 0 fail-over partitions(s

) is 507928 bytes.

2009-04-20-12.21.55.248298+330 I1092954540A537 LEVEL: Event

PID : 10656 TID : 1 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2sysc 0

FUNCTION: DB2 UDB, fast comm manager, sqkfSessionManager::initSessionManager, pr

obe:10

START : Starting FCM Session Manager

1 resource group(s).

128 sessions allocated.

Maximum number of sessions supported is 64000.

Total session manager memory required for 1 logical and 0 fail-over partitions i

s 1400832 bytes.

2009-04-20-12.21.55.249956+330 I1092955078A418 LEVEL: Event

PID : 10656 TID : 1 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2sysc 0

FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500

START : FCM infrastructure started

FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IP

v4

2009-04-20-12.21.55.414218+330 E1092955497A360 LEVEL: Warning

PID : 10656 TID : 1 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 1 EDUNAME: db2sysc 0

FUNCTION: DB2 UDB, oper system services, sqloStartAIOCollectorEDUs, probe:10

MESSAGE : AIO disabled, no collector EDUs will be spawned.

2009-04-20-12.21.56.486014+330 E1092955858A1222 LEVEL: Event

PID : 10653 TID : 1 PROC : db2star2

INSTANCE: db2vbp NODE : 000

EDUID : 1

FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911

MESSAGE : ADM7513W Database manager has started.

START : DB2 DBM

DATA #1 : Build Level, 152 bytes

Instance "db2vbp" uses "64" bits and DB2 code release "SQL09050"

with level identifier "03010107".

Informational tokens are "DB2 v9.5.0.0", "special_19101", "HPIPF6495_19101", Fix

Pack "0".

DATA #2 : System Info, 104 bytes

System: HP-UX dew B.11.31 U ia64

CPU: total:4 online:4 Threading degree per core:1

Physical Memory(MB): total:16361 free:6564

Virtual Memory(MB): total:64745 free:54948

Swap Memory(MB): total:48384 free:48384

Kernel Params: msgMaxMessageSize:65535 msgMsgMap:4098 msgMaxQueueIDs:4096

msgNumberOfHeaders:4096 msgMaxQueueSize:65535

msgMaxSegmentSize:248 shmMax:17179869184 shmMin:1 shmIDs:512

shmSegments:300 semMap:8194 semIDs:8192 semNum:16384

semUndo:4096 semNumPerID:2048 semOps:500 semUndoPerProcess:100

semUndoSize:824 semMaxVal:32767 semAdjustOnExit:16384

2009-04-20-12.21.56.539055+330 I1092957081A501 LEVEL: Event

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

CHANGE : CFG DB VBP : "Database_memory" From: "271220" <automatic> To: "26

2224" <automatic>

2009-04-20-12.21.56.640042+330 E1092957583A393 LEVEL: Info

PID : 10656 TID : 16 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000

EDUID : 16 EDUNAME: db2loggr (VBP) 0

FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInitDelOldLog, probe:1440

DATA #1 : <preformatted>

Cleaning up logs from RenameArchNum 3297 to delLimit 3305.

2009-04-20-12.21.56.685404+330 I1092957977A432 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30

MESSAGE : Crash Recovery is needed.

2009-04-20-12.21.57.286071+330 E1092958410A593 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, oper system services, sqlo_enable_dio_cio_using_ioctl, probe:

50

MESSAGE : ZRC=0x870F00B7=-2029059913=SQLO_UNSUPPORTED

"Operation is unsupported."

DATA #1 : String, 54 bytes

The file system does not have support for Direct I/O.

2009-04-20-12.21.58.659240+330 I1092959004A440 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, relation data serv, sqlrr_db_init, probe:700

MESSAGE : DB2_IMPLICIT_UNICODE enabled

2009-04-20-12.21.58.663494+330 I1092959445A495 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410

MESSAGE : Crash recovery started. LowtranLSN 00000044F97DFB1F MinbuffLSN

00000044F952CDB7

2009-04-20-12.21.58.663618+330 E1092959941A449 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410

MESSAGE : ADM1530E Crash recovery has been initiated.

2009-04-20-12.21.58.668762+330 I1092960391A492 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000

DATA #1 : <preformatted>

Using parallel recovery with 5 agents 36 QSets 144 queues and 64 chunks

2009-04-20-12.21.59.583158+330 I1092960884A505 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000

MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is

"00000044F98B4D36".

2009-04-20-12.21.59.600059+330 E1092961390A458 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170

MESSAGE : ADM1531E Crash recovery has completed successfully.

2009-04-20-12.21.59.600404+330 I1092961849A460 LEVEL: Warning

PID : 10656 TID : 10 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-9 APPID: 10.0.3.231.64044.090420065424

AUTHID : SAPVBP

EDUID : 10 EDUNAME: db2agent (VBP) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170

MESSAGE : Crash recovery completed. Next LSN is 00000044F98B4E00

2009-04-20-12.22.00.043400+330 E1092962310A459 LEVEL: Event

PID : 10656 TID : 33 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-18 APPID: *LOCAL.DB2.090420065207

AUTHID : SAPVBP

EDUID : 33 EDUNAME: db2stmm (VBP) 0

FUNCTION: DB2 UDB, Self tuning memory manager, stmmLog, probe:1008

DATA #1 : <preformatted>

Starting STMM log from file number 74

2009-04-20-12.25.00.083584+330 I1092962770A494 LEVEL: Event

PID : 10656 TID : 33 PROC : db2sysc 0

INSTANCE: db2vbp NODE : 000 DB : VBP

APPHDL : 0-18 APPID: *LOCAL.DB2.090420065207

AUTHID : SAPVBP

EDUID : 33 EDUNAME: db2stmm (VBP) 0

FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

CHANGE : STMM CFG DB VBP: "Database_memory" From: "262224" <automatic> To: "27

3540" <automatic>

2009-04-20-12.26.59.516974+330 I1092963265A332 LEVEL: Event

PID : 10660 TID : 7 PROC : db2acd 0

INSTANCE: db2vbp NODE : 000

EDUID : 7 EDUNAME: db2acd 0

FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsDaemon::run, probe:100

STARTUP : ATS Daemon Thread Started

dew:db2vbp 18>\

Rgds,

RKS

Former Member · ‎04-20-2009

<<MESSAGE : ADM1531E Crash recovery has completed successfully.