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

DB2ISETUP SHOWS MISLEADING ERRORS RELATING TO GLOBAL PROFILE REGISTRY
VARIABLES IN A NON-ROOT CONFIGURATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After a non-root DB2 setup, running 
$HOME/sqllib/instance/db2isetup will result in a minor error 
indicating several registry variables could not be added to the 
Global Profile Registry. 
 
e.g. 
 
... 
 
ERROR: The value "DB2SYSTEM=machine-01" could not be added to 
the Global 
Profile Registry. Return value is "255". 
 
Setting default global profile registry variables 
:.......Failure 
 
... 
 
ERROR: The value "DB2COMM=TCPIP" could not be added to the 
Profile Registry for 
the "db2inst1" instance. Return value is "5094". 
 
ERROR: The value "DB2AUTOSTART=NO" could not be added to the 
Profile Registry 
for the "db2inst1" instance. Return value is "5094". 
 
These errors can be ignored and the profile registry can be 
queried to verify these values already exist. 
 
$ /home/db2inst1/sqllib/instance/db2iset -all 
[i] DB2COMM=tcpip 
[i] DB2AUTOSTART=NO 
[g] DB2SYSTEM=machine-01 
[g] DB2INSTDEF=db2inst1 
 
After applying the fix, the minor errors from db2isetup will not 
appear in the log.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* This problem occurs in Non-Root configurations using         * 
* db2isetup in DB2 V9.7                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After a non-root DB2 setup, running                          * 
* $HOME/sqllib/instance/db2isetup will result in a minor error * 
* indicating several registry variables could not be added to  * 
* the Global Profile Registry.                                 * 
*                                                              * 
* e.g.                                                         * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* ERROR: The value "DB2SYSTEM=machine-01" could not be added   * 
* to the Global                                                * 
* Profile Registry. Return value is "255".                     * 
*                                                              * 
* Setting default global profile registry variables            * 
* :.......Failure                                              * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* ERROR: The value "DB2COMM=TCPIP" could not be added to the   * 
* Profile Registry for                                         * 
* the "db2inst1" instance. Return value is "5094".             * 
*                                                              * 
* ERROR: The value "DB2AUTOSTART=NO" could not be added to the * 
* Profile Registry                                             * 
* for the "db2inst1" instance. Return value is "5094".         * 
*                                                              * 
* These errors can be ignored and the profile registry can be  * 
* queried to verify these values already exist.                * 
*                                                              * 
* $ /home/db2inst1/sqllib/instance/db2iset -all                * 
* [i] DB2COMM=tcpip                                            * 
* [i] DB2AUTOSTART=NO                                          * 
* [g] DB2SYSTEM=machine-01                                     * 
* [g] DB2INSTDEF=db2inst1                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply the DB2 V9.7 FixPack 2.                                * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Apply the DB2 V9.7 FixPack 2. After applying the fix, the minor 
errors from db2isetup will not appear in the log.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68150 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2010
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList