DB2 - Problembeschreibung
| Problem IC77120 | Status: Geschlossen |
WHEN DIAGPATH IS SET TO SPLIT PER NODE ( $N ), DB2ROCM PROCESS ON CF KEEPS ON LOGGING ERRORS, AND DB2TOP MAY FAIL ON CF BOX | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. ) | |
| verfügbare FixPacks: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
| Lösung | |
Problem was first fixed in Version 9.8 FixPak 4 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.06.2011 12.08.2011 12.08.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.8. | |
| Problem behoben lt. FixList in der Version | |
| 9.8.0.4 |
|