cancel
Showing results for 
Search instead for 
Did you mean: 

Db 9.1 not starting after upgrade fixpack 12

Former Member
0 Kudos

Dear All,

We are currently on DB2 version 9.1, we planned to update db2 fixpack to fixpack12

we executed the installfixpack command and provided the path of DB binaries

./installfixpack -b <DB2 software path>

after which i need to start db with command db2start on user db2<SID> before executing ./db2_update_db.sh -d <SID>

but unable to start db2 after checking the log file db2diag.log file

db2diag.log

2014-01-15-10.23.17.752890+330 I1A1567            LEVEL: Event
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START   : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2ecq" uses "64" bits and DB2 code release "SQL0901C"
with level identifier "020D0107".
Informational tokens are "DB2 v9.1.0.12", "s120624", "U849202", Fix Pack "12".
DATA #2 : System Info, 1568 bytes
System: HP-UX w2erpqa B.11.31 U ia64
CPU: total:3 online:3 Threading degree per core:1
Physical Memory(MB): total:25595 free:20079
Virtual  Memory(MB): total:50171 free:44655
Swap     Memory(MB): total:24576 free:24576
Kernel   Params: msgMaxMessageSize:65535 msgMsgMap:4098 msgMaxQueueIDs:4096
                 msgNumberOfHeaders:4096 msgMaxQueueSize:65535
                 msgMaxSegmentSize:248 shmMax:4398046511104 shmMin:1
                 shmIDs:4096 shmSegments:512 semMap:8194 semIDs:8192
                 semNum:16384 semUndo:4092 semNumPerID:2048 semOps:500
                 semUndoPerProcess:100 semUndoSize:824 semMaxVal:32767
                 semAdjustOnExit:16384
Cur cpu time limit (seconds)  = 0xFFFFFFFF
Cur file size limit (bytes) = 0xFFFFFFFF
Cur data size (bytes)  = 0x00000000
Cur stack size (bytes)  = 0x40000000
Cur core size (bytes)  = 0x77359400
Cur memory size (bytes) = 0xFFFFFFFF
nofiles (descriptors)  = 0x0000F800

Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2014-01-15-10.23.17.752156+330 I1569A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0008                                  ....

2014-01-15-10.24.17.771508+330 I1940A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0007                                  ....

2014-01-15-10.25.17.782116+330 I2311A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0006                                  ....

2014-01-15-10.26.17.792129+330 I2682A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0005                                  ....

2014-01-15-10.27.17.801524+330 I3053A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0004                                  ....

2014-01-15-10.28.17.811527+330 I3424A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0003                                  ....

2014-01-15-10.29.17.821517+330 I3795A370          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:680
MESSAGE : Waiting for db2sysc. Retry# :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC164 : 0000 0002                                  ....

2014-01-15-10.29.17.822227+330 I4166A388          LEVEL: Error
PID     : 4366                 TID  : 1           PROC : db2star2
INSTANCE: db2ecq               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:690
MESSAGE : Timeout is reached for db2startWp. Error Code :
DATA #1 : Hexdump, 4 bytes
0x87FFFFFFFFFFC154 : 870F 00B9                                  ....

Dear all need your expect help.

Thanks in advance.

Neeraj

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear All,

The issue was resolved by restarting the machine and executing db2iupdt db2<dbsid>.

Cheers !!

Answers (0)