Hi,

We have applied DB2 8.1 Fixpack 17 64 bit in Linux Box, but the instance is failing to start. After applying fixpack, we updated the instance using db2iupt command. Please find the diaglog output and help us ???

2010-12-13-21.44.48.830776+480 I46699E362 LEVEL: Severe
PID : 25394 TID : 46984514242464PROC : db2sysc 0
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloInitPriorityManagementDaemon, probe:30
MESSAGE : ZRC=0x00000016=22
DIA8022C Incompatible data type "" used with an EXECUTE or OPEN.

2010-12-13-21.44.48.831316+480 E47062E332 LEVEL: Error (OS)
PID : 25394 TID : 46984514242464PROC : db2sysc 0
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloInitPriorityManagementDaemon, probe:35
CALLED : OS, -, unspecified_system_function OSERR: EINVAL (22)

2010-12-13-21.44.48.831373+480 I47395E362 LEVEL: Severe
PID : 25394 TID : 46984514242464PROC : db2sysc 0
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloInitEDUServices, probe:281
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x00007FFF3F490C24 : 1600 0083 ....

2010-12-13-21.45.48.803491+480 E47758E318 LEVEL: Error (OS)
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost, probe:80
CALLED : OS, -, unspecified_system_function OSERR: ENOMSG (42)

2010-12-13-21.45.48.803802+480 I48077E360 LEVEL: Severe
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost, probe:0
MESSAGE : timeout:
DATA #1 : Hexdump, 4 bytes
0x00007FFFA016CD4C : 0000 0000 ....

2010-12-13-21.45.48.804248+480 I48438E511 LEVEL: Severe
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost, probe:0
DATA #1 : String, 239 bytes
CALL STACK:
[0] 0x00002B2C0C35A973 sqloWaitIPCWaitPost + 0x343
[1] 0x00000000004092AB DB2StartMain + 0x4AFB
[2] 0x000000360E41D974 __libc_start_main + 0xF4
[3] 0x0000000000403CAA sqlt_system_error + 0x42
[4] 0x0000000000000000 (nil) + 0x0

2010-12-13-21.45.48.804328+480 I48950E635 LEVEL: Severe
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost, probe:0
DATA #1 : String, 181 bytes
{
pc = 0x0
cs = {
lock = { 0x01 [ locked ] }
identity = sqlo_waitpost::cs (4)
}

state = 0x2
guard = initialized
flags = 0x2
np = 1
}
DATA #2 : Hexdump, 24 bytes
0x00000002000200B8 : 0000 0000 01CC 0400 0200 0000 FEAB 0000 ................
0x00000002000200C8 : 0200 0000 0100 0000 ........

2010-12-13-21.45.48.804424+480 I49586E380 LEVEL: Error
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:660
MESSAGE : db2sysc exited prematurely. sqlcode :
DATA #1 : Hexdump, 4 bytes
0x00007FFFA016D3C4 : 2A00 0083 *...

2010-12-13-21.45.48.804470+480 I49967E355 LEVEL: Error
PID : 25392 TID : 47468221646800PROC : db2star2
INSTANCE: db2inst8 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:670
MESSAGE : db2syscPID :
DATA #1 : Hexdump, 4 bytes

Did you perform all of the steps after installing the fix pack? Did you do the bind steps?

Version 8 has been out of service for a couple of years now. You really should upgrade.

Andy

Had the same on an AIX machine: the db2stop did not complete. I had forgotten the "db2iupdt" as root. After that all worked well.

Hi All,

Finally, the issue got resolved and the instance is working fine.

We had already run db2iupdt but the still was arising. The main problem was the instance owner didnt had suid privilage due to which the db2sysc process was failing to start.

Please note this....

and this: We had another task-user assigned as SYSADM so this user-id could also run the scripts in which the db2start/db2stop were executed. This user had a limitation that files could not be greater than 2 Gb. Guess what happens when this user issued the db2start and a tablespace wanted to expand.....db2diag complaints about a file-system being full which is not the case.
You check the rights of the instance-owner and they are all set correctly, you never suspect that db2 will inherit the rights of the user issuing the db2start. Perhaps I've mentioned this before on this forum but I cannot warn you all enough