$ db2 get dbm cfg | grep DIAGLEVEL
Diagnostic error capture level (DIAGLEVEL) =3D 4
$ db2start
07/29/2005 18:31:20 0 0 SQL1063N DB2START processing was
successful.
07/29/2005 18:31:51 1 0 SQL1063N DB2START processing was
successful.
SQL1063N DB2START processing was successful.
$ db2 create database sam
SQL1229N The current transaction has been rolled back because of a
system
error. SQLSTATE=3D40504
Snippet from the diag.log:
2005-07-29-18.33.06.064062+330 I109523G356 LEVEL: Warning
PID : 15537 TID : 3019486912 PROC : db2agntp
INSTANCE: muk8mm32 NODE : 000
APPHDL : 0-52 APPID: *N0.muk8mm32.050729130215
MESSAGE : Path/Filename
DATA #1 : String, 67 bytes
/data1/db2/databases/muk8mm32/muk8mm32/NODE0000/SQL00001/SQLT0001.0
2005-07-29-18.33.06.064879+330 I109880G404 LEVEL: Warning
PID : 15537 TID : 3019486912 PROC : db2agntp
INSTANCE: muk8mm32 NODE : 000
APPHDL : 0-52 APPID: *N0.muk8mm32.050729130215
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
MESSAGE : errno:
DATA #1 : Hexdump, 4 bytes
0xBFFF0F00 : 1500 0000 ....
.
.
.
2005-07-29-18.33.16.012454+330 I111404G299 LEVEL: Info
PID : 15415 TID : 3019486912 PROC : db2fcmdm
INSTANCE: muk8mm32 NODE : 000
FUNCTION: DB2 UDB, fast comm manager, sqlkfRefreshDb2nodesCache,
probe:25
MESSAGE : Refreshing db2nodes.cfg cache is successful.
.
.
.
2005-07-29-18.33.56.061458+330 I112904G374 LEVEL: Info
PID : 15416 TID : 3019486912 PROC : db2pdbc
INSTANCE: muk8mm32 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleExecuteNodeRecovery, probe:9
MESSAGE : Performing node recovery for node =
DATA #1 : Hexdump, 2 bytes
0xBFFF7280 : 0100 ..
2005-07-29-18.33.56.061774+330 I113279G391 LEVEL: Warning
PID : 15416 TID : 3019486912 PROC : db2pdbc
INSTANCE: muk8mm32 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleCheckForDynDBMUpdate,
probe:50
MESSAGE : Attempted to recover dynamic config updates =
DATA #1 : Hexdump, 4 bytes
0xBFFF6F60 : 0000 0000 ....
2005-07-29-18.33.56.061764+330 I113671G380 LEVEL: Info
PID : 15536 TID : 3019486912 PROC : db2agent
(instance)
INSTANCE: muk8mm32 NODE : 000
APPHDL : 0-52 APPID: *N0.muk8mm32.050729130215
FUNCTION: DB2 UDB, buffer dist serv, sqlkd_rcv_buffer, probe:10
RETCODE : ZRC=0x81590016=-2124873706=SQLKF_NODE_FAILED "Node Recovery"
.
.
.
2005-07-29-18.33.56.564901+330 I114821G382 LEVEL: Error
PID : 15536 TID : 3019486912 PROC : db2agent
(instance)
INSTANCE: muk8mm32 NODE : 000
APPHDL : 0-52 APPID: *N0.muk8mm32.050729130215
FUNCTION: DB2 UDB, buffer dist serv, sqlkdReceiveReply, probe:10
RETCODE : ZRC=0x81590016=-2124873706=SQLKF_NODE_FAILED "Node Recovery"
2005-07-29-18.33.56.566463+330 I115204G283 LEVEL: Info
PID : 15415 TID : 3019486912 PROC : db2fcmdm
INSTANCE: muk8mm32 NODE : 000
FUNCTION: DB2 UDB, fast comm manager, sqlkf_proc_node_rec_comp, probe:20
MESSAGE : For information only: node 1.
2005-07-29-18.33.56.566702+330 I115488G984 LEVEL: Error
PID : 15536 TID : 3019486912 PROC : db2agent
(instance)
INSTANCE: muk8mm32 NODE : 000
APPHDL : 0-52 APPID: *N0.muk8mm32.050729130215
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : Hexdump, 136 bytes
0xB3F3BCE4 : 5351 4C43 4120 2020 8800 0000 33FB FFFF SQLCA ....3...
0xB3F3BCF4 : 0000 2020 2020 2020 2020 2020 2020 2020 ..
0xB3F3BD04 : 2020 2020 2020 2020 2020 2020 2020 2020
0xB3F3BD14 : 2020 2020 2020 2020 2020 2020 2020 2020
0xB3F3BD24 : 2020 2020 2020 2020 2020 2020 2020 2020
0xB3F3BD34 : 2020 2020 2020 2020 5351 4C45 4443 5245 SQLEDCRE
0xB3F3BD44 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xB3F3BD54 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
0xB3F3BD64 : 2020 2034 3035 3034 40504
Thanks
Rajesh
-----Original Message-----
From: DANIEL CALLAHAN
[mailto:db2udbdba-ezmlmshield-x78431151.[Email address protected]
Sent: Friday, July 29, 2005 6:08 PM
To: LazyDBA Discussion
Subject: RE: SQL1229N while creating database on multi-partitioned
instance
Can you turn up the diaglevel to 4 and create the database and send me
the
snippet from the diag.log
"Jaswal Rajesh "
<db2udbdba-ezmlms
hield-x5432165.x1
To
[Email Address Removed] "LazyDBA Discussion"
.com> <[Email address protected]
cc
07/29/2005 08:33
AM
Subject
RE: SQL1229N while creating
database on multi-partitioned
instance
Yes. ulimit is set to unlimited on both servers.
user/group ids/ passwords are also 100% identical:
cha8mm64:x:30000003:30000001:UDB
Instance:/data1/db2/databases/cha8mm64:/bin/ksh
cha8mm64:x:30000003:30000001:UDB
Instance:/data1/db2/databases/cha8mm64:/bin/ksh
db2admin:x:30000001:
db2admin:x:30000001:
rsh, db2_all work well.
64 bit one starts but only brings up instances on the first node as per
entries in the db2nodes.cfg. For other node's entries it gives "SQL6048N
Communication error..."
Thanks
Rajesh
-----Original Message-----
From: DANIEL CALLAHAN
[mailto:db2udbdba-ezmlmshield-x32659106.[Email address protected]
Sent: Friday, July 29, 2005 5:36 PM
To: LazyDBA Discussion
Subject: RE: SQL1229N while creating database on multi-partitioned
instance
What about ulimits for the instance id? and are the two userids 100%
equal
across both nodes down to the numeric id and groupid of each one?
So the 64 bit one doesnt start at all ?
"Satya"
<db2udbdba-ezmlms
hield-x54048967.x
To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
07/28/2005 09:42
PM
Subject
RE: SQL1229N while creating
database on multi-partitioned
instance
Have you made correct entry in .rhosts in the home directory of instance
owner and enabled rsh if multiple server.
"Jaswal Rajesh " <db2udbdba-ezmlmshield-x53282189.[Email address
protected]
07/28/05 09:23 PM
To: "LazyDBA Discussion" <[Email address protected]
cc:
Subject: RE: SQL1229N while creating database on
multi-partitioned instance
Hi Daniel,
/etc/services file has identical entries on both nodes.
db2c_muk8mm32 50002/tcp
DB2_muk8mm32 60004/tcp
DB2_muk8mm32_1 60005/tcp
DB2_muk8mm32_2 60006/tcp
DB2_muk8mm32_END 60007/tcp
Infact, I have successfully created multi-partitioned instances for both
V7.2 and V8.x on almost all UNIX/Windows operating systems. But I am
unable to do it on Redhat AS 4.0. Are there RHEL 4.0 specific issues?
On Redhat AS 4.0 IA64, db2start does not start the instances on other
node; giving SQL6048N - A communication error. And if db2start is
executed from other node, I get " SQL1042C An unexpected system
error..." Hardware in this case is HP Rx-2600(Itanium)
On Redhat AS 4.0 IA32 architecture, db2start successfully starts
instances on all physical nodes, but fails to create database with
SQL1229N error.
Logically partitioned instances / databases are working without any
problems individually on all these boxes.
Thanks
Rajesh
-----Original Message-----
From: DANIEL CALLAHAN
[mailto:db2udbdba-ezmlmshield-x11394225.[Email address protected]
Sent: Thursday, July 28, 2005 5:43 PM
To: LazyDBA Discussion
Subject: Re: SQL1229N while creating database on multi-partitioned
instance
Make sure that the /etc/services file is identical on the two nodes with
respect to the FCM ports. (DB2_db2inst1 - DB2_db2inst1_end)
"Jaswal Rajesh "
<db2udbdba-ezmlms
hield-x50866053.x
To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
07/28/2005 07:00
AM
Subject
SQL1229N while creating database
on
multi-partitioned instance
Hi All,
Am getting SQL1229N error while creating a database on a
multi-partitioned instance (two physical nodes). The DB2 V8 is at
fixpack 7 and the OS is Redhat AS 4.
$ db2start
07/28/2005 16:24:00 0 0 SQL1063N DB2START processing was
successful.
07/28/2005 16:24:31 1 0 SQL1063N DB2START processing was
successful.
SQL1063N DB2START processing was successful.
$ db2 create db sam
SQL1229N The current transaction has been rolled back because of a
system error. SQLSTATE=3D40504 $
Please help!
Thanks
Rajesh
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
This email is confidential. If you are not the addressee tell the sender
immediately and destroy this email without using, sending or storing it.
Emails are not secure and may suffer errors, viruses, delay,
interception
and amendment. Standard Chartered PLC and subsidiaries ("SCGroup") do
not
accept liability for damage caused by this email and may monitor email
traffic.
This email is confidential. If you are not the addressee tell the sender
immediately and destroy this email without using, sending or storing it.
Emails are not secure and may suffer errors, viruses, delay,
interception
and amendment. Standard Chartered PLC and subsidiaries ("SCGroup") do
not
accept liability for damage caused by this email and may monitor email
traffic.
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page