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 IC98679 Status: Closed

WHEN RUNNING DB2GCF AS ROOT TO STOP A PARTITION THE COMMAND EXITS WITH RC=3
AND ERROR MESSAGE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If the following command to stop a DB2 partition is executed as 
root: 
"db2gcf -t xxx -d -p 0 -i instance_name -L" 
 
It exits with rc=3 and the following error message: 
"db2gcf Error : GCF Module function failed." 
 
even though the partition is successfully stopped. Issuing this 
command should instead return the following: 
 
host02:~ # /home/db2inst1/sqllib/bin/db2gcf -t 600 -d -p 0 -i 
db2inst1 -L 
 
Instance  : db2inst1 
DB2 Stop : Success 
Member 0 : Success
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V10.5 FP3                                  * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in V10.5 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.01.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList