By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,286 Members | 1,290 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,286 IT Pros & Developers. It's quick & easy.

installing db2 8.2.2 on RHEL4

P: n/a
Chaps,

I'm having a small problem installing db2 on a Red Hat Enterprise
server (version 4)
Basically I installed DB2 V8.1 , applied fixpak 5 and then the 2.6
kernel specific fixpak 9 update. I then created the the administration
instance and some "user" instances

db2admin start works just fine but whenever I try and run db2start in
one of the "user" instances I get an SQL1024C error message.

Looking in sqllib\db2dump directory, the db2diag.log file has the
following contents. It looks like its the

#################
2005-06-16-08.47.25.783822+060 I2717G410 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:25
RETCODE : ZRC=0x800F0067=-2146500505=SQLO_ID_2LONG
"USERID/GROUPID is greater than the Shelby Supported
size/length"
DIA8111C Authorization failure.
#################
that's the problem.

Can anyone help?
Alex

dbdiag.log contents:-

2005-06-16-08.47.25.305262+060 I1G1209 LEVEL: Event
PID : 3638 TID : 3086911168 PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
START : New db2diag.log file
DATA #1 : Build Level, 124 bytes
Instance "db2inst1" uses "32" bits and DB2 code release "SQL08022"
with level identifier "03030106".
Informational tokens are "DB2 v8.1.2.88", "s050422", "MI00117", FixPak
"9".
DATA #2 : System Info, 364 bytes
System: Linux schubert 6 2 i686
CPU: total:2 online:2
Physical Memory(MB): total:2026 free:1662
Virtual Memory(MB): total:6027 free:5663
Swap Memory(MB): total:4001 free:4001
Kernel Params: msgMaxMessageSize:8192 msgMsgMap:16384
msgMaxQueueIDs:1024
msgNumberOfHeaders:16384 msgMaxQueueSize:16384
msgMaxSegmentSize:16 shmMax:268435456 shmMin:1
shmIDs:4096
shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000
semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
semMaxVal:32767 semAdjustOnExit:32767
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2005-06-16-08.47.25.304813+060 I1211G1505 LEVEL: Event
PID : 3638 TID : 3086911168 PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode,
probe:1130
DATA #1 : String, 34 bytes
/home/db2inst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0xBFE73654 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73
/home/db2inst1/s
0xBFE73664 : 716C 6C69 622F 6164 6D2F 6462 3273 7461
qllib/adm/db2sta
0xBFE73674 : 7232 0000 0000 0000 0000 0000 0000 0000
r2..............
0xBFE73684 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73694 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736A4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736B4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736C4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736D4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736E4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE736F4 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73704 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73714 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73724 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73734 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0xBFE73744 : 0000 0000 0000 0000 0000 0000 0000 0000
.................

2005-06-16-08.47.25.783822+060 I2717G410 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:25
RETCODE : ZRC=0x800F0067=-2146500505=SQLO_ID_2LONG
"USERID/GROUPID is greater than the Shelby Supported
size/length"
DIA8111C Authorization failure.

2005-06-16-08.47.25.800945+060 I3128G346 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:160
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFE696E4 : EEFB FFFF ....

2005-06-16-08.47.25.801200+060 I3475G336 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:115
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFE69744 : EEFB FFFF ....

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I'd take a look at the group that the instance owner(s) belong to. Since
"db2inst1", the instance owner is only 8 characters (and works fine on
my RHEL4 fp9 setup; the group name is the likely suspect. In the Windows
environment; it's limited to 8 or less characters. I didn't find any
reference to a limit on linux but I'd try 8 or less there too.

*** SOAPBOX ON ***
As usual; the error message shown in the first "RETCODE:" states what is
wrong without specifying exactly what is valid. How much additional work
would it have been to display the "Supported size/length"?
*** SOAPBOX OFF ***

Phil Sherman
alexs wrote:
Chaps,

I'm having a small problem installing db2 on a Red Hat Enterprise
server (version 4)
Basically I installed DB2 V8.1 , applied fixpak 5 and then the 2.6
kernel specific fixpak 9 update. I then created the the administration
instance and some "user" instances

db2admin start works just fine but whenever I try and run db2start in
one of the "user" instances I get an SQL1024C error message.

Looking in sqllib\db2dump directory, the db2diag.log file has the
following contents. It looks like its the

#################
2005-06-16-08.47.25.783822+060 I2717G410 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:25
RETCODE : ZRC=0x800F0067=-2146500505=SQLO_ID_2LONG
"USERID/GROUPID is greater than the Shelby Supported
size/length"
DIA8111C Authorization failure.
#################
that's the problem.

Can anyone help?
Alex

dbdiag.log contents:-

2005-06-16-08.47.25.305262+060 I1G1209 LEVEL: Event
PID : 3638 TID : 3086911168 PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
START : New db2diag.log file
DATA #1 : Build Level, 124 bytes
Instance "db2inst1" uses "32" bits and DB2 code release "SQL08022"
with level identifier "03030106".
Informational tokens are "DB2 v8.1.2.88", "s050422", "MI00117", FixPak
"9".
DATA #2 : System Info, 364 bytes
System: Linux schubert 6 2 i686
CPU: total:2 online:2
Physical Memory(MB): total:2026 free:1662
Virtual Memory(MB): total:6027 free:5663
Swap Memory(MB): total:4001 free:4001
Kernel Params: msgMaxMessageSize:8192 msgMsgMap:16384
msgMaxQueueIDs:1024
msgNumberOfHeaders:16384 msgMaxQueueSize:16384
msgMaxSegmentSize:16 shmMax:268435456 shmMin:1
shmIDs:4096
shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000
semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
semMaxVal:32767 semAdjustOnExit:32767
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2005-06-16-08.47.25.304813+060 I1211G1505 LEVEL: Event
PID : 3638 TID : 3086911168 PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode,
probe:1130
DATA #1 : String, 34 bytes
/home/db2inst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0xBFE73654 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73
/home/db2inst1/s
0xBFE73664 : 716C 6C69 622F 6164 6D2F 6462 3273 7461
qllib/adm/db2sta
0xBFE73674 : 7232 0000 0000 0000 0000 0000 0000 0000
r2..............
0xBFE73684 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73694 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736A4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736B4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736C4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736D4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736E4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE736F4 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73704 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73714 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73724 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73734 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0xBFE73744 : 0000 0000 0000 0000 0000 0000 0000 0000
................

2005-06-16-08.47.25.783822+060 I2717G410 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:25
RETCODE : ZRC=0x800F0067=-2146500505=SQLO_ID_2LONG
"USERID/GROUPID is greater than the Shelby Supported
size/length"
DIA8111C Authorization failure.

2005-06-16-08.47.25.800945+060 I3128G346 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:160
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFE696E4 : EEFB FFFF ....

2005-06-16-08.47.25.801200+060 I3475G336 LEVEL: Severe
PID : 3642 TID : 3086911168 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:115
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFE69744 : EEFB FFFF ....

Nov 12 '05 #2

P: n/a
Nope, all the instances have the same group name as the userid, with
the group names being members of the db2admin group as defined in
/etc/groups.

Nov 12 '05 #3

P: n/a
well,
checked allthe userid and group id stuff seemed o.k.

Did a chown db2inst1.db2inst1 db2inst1 in the home directory just to
make sure everything was owned by the instance deleted everything in
/tmp ... and it worked. Repeated the process for the other instances
I'd created and it sprang into life
alexs wrote:
Nope, all the instances have the same group name as the userid, with
the group names being members of the db2admin group as defined in
/etc/groups.


Nov 12 '05 #4

P: n/a
Ian
alexs wrote:
well,
checked allthe userid and group id stuff seemed o.k.

Did a chown db2inst1.db2inst1 db2inst1 in the home directory just to
make sure everything was owned by the instance deleted everything in
/tmp ... and it worked. Repeated the process for the other instances
I'd created and it sprang into life


Ugh, that's asking for trouble. Some of the files under the sqllib
directory should NOT be owned by the instance owner. If you suspect
ownership/permissions are incorrect, you should shut down the
instance and use 'db2iupdt'.
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.