home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC78358 Status: Geschlossen

"DB2AUDIT CONFIGURE DATAPATH" MAY DELETE THE RESOURCE GROUP
UNEXPECTEDLY.

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
Mount resources are created with a default usage count 
of 2, one for the DB2DIAGPATH and another for the resource 
itself.  The "db2audit configure datapath" command wasn't 
accounted for and once we change the db2audit datapath, the 
mount resource's usage count will drop by the number of 
members in the cluster;once the usage count drops down 
to zero, the resource group will be deleted.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.8                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.8 FixPack 5.                            * 
****************************************************************
Local-Fix:
Workaround: 
Set the mount resource's usage count to 2+(number of 
members in cluster). 
 
E.g. In a 4 member cluster setup, the mount resource's usage 
count would be set to 6 as follows: 
$>  db2hareg -upd Mount path='<mount path>'!useCount=6 
 
This change can then be confirmed by issuing: 
$>  db2hareg -dump 
<snip> 
MO,<mount path>, ,0,6,0 
 
and noting the value of the mount resource's usage count, which 
is set to 6 in this case. 
 
Note: Avoid altering the useCount value unless needed to resolve 
this specific issue.
Lösung
Problem was first fixed in DB2 UDB Version 9.8 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.08.2011
15.06.2012
15.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP5
Problem behoben lt. FixList in der Version
9.8.0.5 FixList