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

WHEN DIAGPATH IS SET TO SPLIT PER NODE ( $N ), DB2ROCM PROCESS ON CF KEEPS
ON LOGGING ERRORS, AND DB2TOP MAY FAIL ON CF BOX

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
When DIAGPATH is set to split per node ( $n ) or per host per 
node ( $h$n ). the application process on CF box ( e.g. db2rocm, 
db2start/db2stop ) may have trouble getting default node number 
( 128 or 129 ), hence, errors may occur, such as db2rocm keeps 
on dumping error messages to db2diag.log, as below: 
 
  2011-04-13-13.10.50.177722+540 E4390A478            LEVEL: 
Error 
  PID     : 14876814             TID  : 1             PROC : 
db2rocm 
  INSTANCE: some_instance NODE : 000 
  HOSTNAME: db2inst1 
  EDUID   : 1                    EDUNAME: db2rocm 
  FUNCTION: DB2 UDB, RAS/PD component, 
pdReadFODCOptionsFromDisk, probe:10 
  MESSAGE : ZRC=0x070F00B8=118423736=SQLO_NOT_FOUND 
            "Environment/registry variable was not found." 
  DATA #1 : String, 29 bytes 
  Failed to reset FODC options.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* the CF node runs alone on a box                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When DIAGPATH is set to split per node ( $n ) or per host    * 
* per node ( $h$n ). the application process on CF box ( e.g.  * 
* db2rocm, db2start/db2stop ) may have trouble getting default * 
* node number ( 128 or 129 )                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.8 FixPak 4                          * 
****************************************************************
Local Fix:
Against db2start/db2stop error symptom, the following is valid 
as a temporary fix. 
  - add DB2NODE definition to ".profile" file on the instance 
account of the CF machine, then run it. 
    ( ex. add "export DB2NODE=128" statement in ".profile" of 
the instance acount on the CF machine. )
available fix packs:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in Version 9.8 FixPak 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2011
12.08.2011
12.08.2011
Problem solved at the following versions (IBM BugInfos)
9.8.
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList