db2start gives an error after DB2 installation

[Jurgen Haan]

Hey hey all...

I'm in the following situation:

I installed SuSE SLES9 on a dual core Opteron 275 (proliant DL385).
2GB Mem, hardware raid.

I performed an install of DB2 for X86_64 8.2 FP 1 (8.1 FP 8)
Install went ok, status log says success on every action taken.
rights are ok, users are ok, etc.
I immediatly upgrade to X86_64 8.2 FP 3 (8.1 FP 10)
Completes just fine, no errors whatsoever.

After upgrading I create /etc/sysctl.conf containing
# Added for 64-bit DB2
kernel.sem=250 32000 32 1024
kernel.msgmni=1 024
kernel.shmmni=6 5536
kernel.shmmax=1 073741824
#end additions for DB2

and run sysctl -p /etc/sysctl.conf and place this line in the bootscripts.

When I execute db2start as the db2inst user (default instance) I get:
"SQL1042C An unexpected system error occurred. SQLSTATE=58004"

Can't figure out what's the cause of this... dragged db2start through a
strace, nothing strange happens. ldd says all libraries are ok and I can
invoke the CLI without problems...
The only thing I cannot do, is start DB2 :P

Does anyone have any ideas on what may be the cause of this happening?

Thanks.

-R-

[Jurgen Haan]

Jurgen Haan wrote:

Hey hey all...

I'm in the following situation:

I installed SuSE SLES9 on a dual core Opteron 275 (proliant DL385).
2GB Mem, hardware raid.

Needless to say, but the SuSE install is also 64 bit

-R-

[Knut Stolze]

Jurgen Haan wrote:

Jurgen Haan wrote:

Hey hey all...

I'm in the following situation:

I installed SuSE SLES9 on a dual core Opteron 275 (proliant DL385).
2GB Mem, hardware raid.

Needless to say, but the SuSE install is also 64 bit

Have a look at your instance's sqllib/db2dump/db2diag.log file. There
should be some more information in there.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Jurgen Haan]

Knut Stolze wrote:

Jurgen Haan wrote:

Jurgen Haan wrote:

Hey hey all...

I'm in the following situation:

I installed SuSE SLES9 on a dual core Opteron 275 (proliant DL385).
2GB Mem, hardware raid.

Needless to say, but the SuSE install is also 64 bit

Have a look at your instance's sqllib/db2dump/db2diag.log file. There
should be some more information in there.

Well... Nothing that makes sense to me actually...

2005-12-07-10.43.15.941124 +000 I42046E1632 LEVEL: Event
PID : 7322 TID : 182968220384PRO C : db2start
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSi ngleNode, probe:1130
DATA #1 : String, 33 bytes
/home/db2inst/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x0000007FBFFFA CE0 : 2F68 6F6D 652F 6462 3269 6E73 742F 7371
/home/db2inst/sq
0x0000007FBFFFA CF0 : 6C6C 6962 2F61 646D 2F64 6232 7374 6172
llib/adm/db2star
0x0000007FBFFFA D00 : 3200 0000 0000 0000 0000 0000 0000 0000
2.............. .
0x0000007FBFFFA D10 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D20 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D30 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D40 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D50 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D60 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D70 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D80 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA D90 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA DA0 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA DB0 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA DC0 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..
0x0000007FBFFFA DD0 : 0000 0000 0000 0000 0000 0000 0000 0000
............... ..

[Knut Stolze]

Jurgen Haan wrote:

Well... Nothing that makes sense to me actually...

2005-12-07-10.43.15.941124 +000 I42046E1632 LEVEL: Event
PID : 7322 TID : 182968220384PRO C : db2start
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSi ngleNode, probe:1130
DATA #1 : String, 33 bytes
/home/db2inst/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x0000007FBFFFA CE0 : 2F68 6F6D 652F 6462 3269 6E73 742F 7371
/home/db2inst/sq
0x0000007FBFFFA CF0 : 6C6C 6962 2F61 646D 2F64 6232 7374 6172
llib/adm/db2star
0x0000007FBFFFA D00 : 3200 0000 0000 0000 0000 0000 0000 0000
2.............. .

This just says that "db2star2" is invoked with the options
"/home/db2inst/sqllib/adm/db2star2". This looks quite fine as far as it
goes.

Stupid question, maybe: you did update your instange after you applied the
FP? (Or when did you create the instance in the whole process?)

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Jurgen Haan]

Knut Stolze wrote:

Jurgen Haan wrote:

Well... Nothing that makes sense to me actually...

2005-12-07-10.43.15.941124 +000 I42046E1632 LEVEL: Event
PID : 7322 TID : 182968220384PRO C : db2start
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSi ngleNode, probe:1130
DATA #1 : String, 33 bytes
/home/db2inst/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x0000007FBFF FACE0 : 2F68 6F6D 652F 6462 3269 6E73 742F 7371
/home/db2inst/sq
0x0000007FBFF FACF0 : 6C6C 6962 2F61 646D 2F64 6232 7374 6172
llib/adm/db2star
0x0000007FBFF FAD00 : 3200 0000 0000 0000 0000 0000 0000 0000
2............ ...

This just says that "db2star2" is invoked with the options
"/home/db2inst/sqllib/adm/db2star2". This looks quite fine as far as it
goes.

Stupid question, maybe: you did update your instange after you applied the
FP? (Or when did you create the instance in the whole process?)

Hmmm.. during the initial install...

Should I perhaps recreate the instance with the fixpak installed?
Is this always needed?
It's not actually in the spirit of updating, is it? :)

-R-

[Jurgen Haan]

Jurgen Haan wrote:

Knut Stolze wrote:

Jurgen Haan wrote:

Well... Nothing that makes sense to me actually...

2005-12-07-10.43.15.941124 +000 I42046E1632 LEVEL: Event
PID : 7322 TID : 182968220384PRO C : db2start
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSi ngleNode,
probe:1130
DATA #1 : String, 33 bytes
/home/db2inst/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x0000007FBFFFA CE0 : 2F68 6F6D 652F 6462 3269 6E73 742F 7371
/home/db2inst/sq
0x0000007FBFFFA CF0 : 6C6C 6962 2F61 646D 2F64 6232 7374 6172
llib/adm/db2star
0x0000007FBFFFA D00 : 3200 0000 0000 0000 0000 0000 0000 0000
2.............. .

This just says that "db2star2" is invoked with the options
"/home/db2inst/sqllib/adm/db2star2". This looks quite fine as far as it
goes.

Stupid question, maybe: you did update your instange after you applied
the
FP? (Or when did you create the instance in the whole process?)

Hmmm.. during the initial install...

Should I perhaps recreate the instance with the fixpak installed?
Is this always needed?
It's not actually in the spirit of updating, is it? :)

-R-

Manually recreated the instance, and it works like a charm...
Thanks :)

-R-

[Knut Stolze]

Jurgen Haan wrote:

Should I perhaps recreate the instance with the fixpak installed?
Is this always needed?

No, you just can run the "db2iupdt" command. You'll find it here:

/opt/IBM/db2/V8.1/instance/db2iupdt

The reason why you must update the instance is simply that a few files and
executables reside as a _copy_ in the instance's directory. If you install
a new FP, only the system-wide files are updated, and you have to ensure
that the copies pick up any changes as well.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Larry]

Jurgen Haan wrote:

Jurgen Haan wrote:

Knut Stolze wrote:

Jurgen Haan wrote:
Well... Nothing that makes sense to me actually...

2005-12-07-10.43.15.941124 +000 I42046E1632 LEVEL: Event
PID : 7322 TID : 182968220384PRO C : db2start
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSi ngleNode,
probe:1130
DATA #1 : String, 33 bytes
/home/db2inst/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x0000007FBFFFA CE0 : 2F68 6F6D 652F 6462 3269 6E73 742F 7371
/home/db2inst/sq
0x0000007FBFFFA CF0 : 6C6C 6962 2F61 646D 2F64 6232 7374 6172
llib/adm/db2star
0x0000007FBFFFA D00 : 3200 0000 0000 0000 0000 0000 0000 0000
2.............. .


This just says that "db2star2" is invoked with the options
"/home/db2inst/sqllib/adm/db2star2". This looks quite fine as far as it
goes.

Stupid question, maybe: you did update your instange after you
applied the
FP? (Or when did you create the instance in the whole process?)

Hmmm.. during the initial install...

Should I perhaps recreate the instance with the fixpak installed?
Is this always needed?
It's not actually in the spirit of updating, is it? :)

-R-

Manually recreated the instance, and it works like a charm...
Thanks :)

-R-

You don't need to recreate the instance after a fixpak install, you just
need to update it. See the fixpak readme instructions.

Larry Edelstein

[Jurgen Haan]

Knut Stolze wrote:

Jurgen Haan wrote:

Should I perhaps recreate the instance with the fixpak installed?
Is this always needed?

No, you just can run the "db2iupdt" command. You'll find it here:

/opt/IBM/db2/V8.1/instance/db2iupdt

The reason why you must update the instance is simply that a few files and
executables reside as a _copy_ in the instance's directory. If you install
a new FP, only the system-wide files are updated, and you have to ensure
that the copies pick up any changes as well.

Lol... sorry for the ignorance...

I never updated a DB2 install before...
Most were test databases which never lasted long enough to need an update :)

Thanks for the info people.

-R-