db2start fails on Solaris 8.2 (SQL1042C)

[_link98]

New installation of DB2 ESE 8.1 and Fixpak 9a on
Solaris 8.2, on FUJITSU 450 server(sparc), 64 bit mode, and 64-bit
instance.

db2start fails (after approx 60 seconds) with SQL1042C (unexpected
system error occurred), so the instance does not start.

db2diag.log shows a timeout error. sqloWaitIPCWaitPost.
ENOMSG(35) no message of desired type.

db2trc shows SQLO_SEM_TIMEOUT.

Any suggestions? (PMR already opened, just checking if someone already
saw this and found a workaround).

The db2 Pre-reqs for Solaris 8.2 are in place (patch levels as per IBM
website solaris_prereq.pdf document) and kernel parameters changed to
those recommended for machines with more than 16gig of RAM (msginfo_*,
seminfo_*, shminfo_* ).

[Larry]

Did you do a db2iupdt after application of the fp?

Larry Edelstein

_l*****@yahoo.com wrote:

New installation of DB2 ESE 8.1 and Fixpak 9a on
Solaris 8.2, on FUJITSU 450 server(sparc), 64 bit mode, and 64-bit
instance.

db2start fails (after approx 60 seconds) with SQL1042C (unexpected
system error occurred), so the instance does not start.

db2diag.log shows a timeout error. sqloWaitIPCWaitPost.
ENOMSG(35) no message of desired type.

db2trc shows SQLO_SEM_TIMEOUT.

Any suggestions? (PMR already opened, just checking if someone already
saw this and found a workaround).

The db2 Pre-reqs for Solaris 8.2 are in place (patch levels as per IBM
website solaris_prereq.pdf document) and kernel parameters changed to
those recommended for machines with more than 16gig of RAM (msginfo_*,
seminfo_*, shminfo_* ).

[_link98]

Larry wrote:

Did you do a db2iupdt after application of the fp?

Larry Edelstein

No, I could not, because there was no instance to update.

The installation was a response-file-installation that
did the base installation (V8.1) and then applied FP9a.

Prior to the installation there was no DB2 on the box,
and the base installation did not create any instances.

Only after installation of base+fp9a completed without
error did I manually create the instance+DAS server
without any problems. It is at this point that the
db2start fails (after configuring SVCENAME first).

Any other suggestion?

[_link98]

Solved: applied a set of Solaris 8.2 patches (different
from those specified on the IBM websites). Dropped instance,
Uninstalled
and re-installed, manually created instance, and it works fine now.

_l*****@yahoo.com wrote:

New installation of DB2 ESE 8.1 and Fixpak 9a on
Solaris 8.2, on FUJITSU 450 server(sparc), 64 bit mode, and 64-bit
instance.

db2start fails (after approx 60 seconds) with SQL1042C (unexpected
system error occurred), so the instance does not start.

db2diag.log shows a timeout error. sqloWaitIPCWaitPost.
ENOMSG(35) no message of desired type.

db2trc shows SQLO_SEM_TIMEOUT.

Any suggestions? (PMR already opened, just checking if someone already
saw this and found a workaround).

The db2 Pre-reqs for Solaris 8.2 are in place (patch levels as per IBM
website solaris_prereq.pdf document) and kernel parameters changed to
those recommended for machines with more than 16gig of RAM (msginfo_*,
seminfo_*, shminfo_* ).