home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC80068 Status: Closed

DB2CLUSTER -CREATE -FILESYSTEM FAILS WITH 0518-506 ODMGET: CANNOT OPEN
OBJECT CLASS CUAT.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
db2cluster -create -filesystem command may not create a new 
cluster filesystem due to an error like as below: 
 
# db2cluster -create -filesystem data1 -disk /dev/hdisk12 -mount 
/db2/data1 
There was an internal db2cluster error. Refer to the diagnostic 
logs (db2diag.log or 
/tmp/ibm.db2.cluster.*) and the DB2 Information Center for 
details. 
A diagnostic log has been saved to 
'/tmp/ibm.db2.cluster.-ZafEa'. 
 
# cat /tmp/ibm.db2.cluster.-ZafEa 
2011-10-18-18.23.14.456237+540 I1915A1005           LEVEL: 
Warning 
PID     : 12320858             TID  : 1             PROC : 
db2cluster 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: member1 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
GPFSCommandAdaptor::executeCommand, probe:3675 
DATA #1 : String, 25 bytes 
/usr/lpp/mmfs/bin/mmcrnsd 
DATA #2 : String, 28 bytes 
-F./tmp/ibm.db2.gpfs.__afE2. 
DATA #3 : String, 33 bytes 
mmcrnsd: Processing disk hdisk12 
DATA #4 : String, 404 bytes 
0518-506 odmget: Cannot open object class CuAt 
    Check path name and permissions. 
mmcrnsd: chdev failed to set PR_key_value for hdisk12. 
mmcrnsd: 6027-1940 Unable to set reserve policy PR_shared on 
disk hdisk12 on node c1mem01. 
mmcrnsd: 6027-1661 Failed while processing disk descriptor 
/dev/hdisk12 on node c1mem01. 
mmcrnsd: 6027-1639 Command failed.  Examine previous error 
messages to determine cause. 
DATA #5 : signed integer, 4 bytes 
1 
DATA #6 : signed integer, 4 bytes 
0 
DATA #7 : signed integer, 4 bytes 
0 
 
This error occurs if ODMDIR environment setting is not 
propagated to GPFS command. The fix have the forked process that 
executes GPFS command to inherit the caller enviroment instead 
of overwrite it.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2cluster -create -filesystem command on AIX  * 
* system.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2cluster -create -filesystem command may not create a new  * 
* cluster filesystem because ODMDIR environment setting is not * 
* propagated to GPFS command.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V9.8 FixPack 5 or later.               * 
****************************************************************
Local Fix:
Create cluster file system by GPFS commands manually.
Solution
This problem was first fixed in DB2 V9.8 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2011
18.06.2012
18.06.2012
Problem solved at the following versions (IBM BugInfos)
9.8.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList