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 IC91613 Status: Geschlossen

V10.1 ONLY: DB2IUPDT COMMAND OVERRIDES FENCEDID BY INSTANCE OWNER IF -U
OPTION IS NOT SPECIFIED.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The db2iupdt command overrides fencedID by instance owner when 
-u option is not specified. 
This command should set fencedID as it is if user does not 
provide -u option. 
 
The following scenario illustrates the problem. 
 
1. Create instance user and fenced user, then create a instance. 
  # db2icrt -u db2fenc db2inst1 
2. Make sure expected fenced user is set. 
  $ cat $HOME/sqllib/ctrl/.fencedID 
  db2fenc 
3. Update the instance. 
  # db2iupdt db2inst1 
4. The command overrides fencedID by instance owner. 
  $ cat $HOME/sqllib/ctrl/.fencedID 
  db2inst1 
 
Please note that installFixpack runs db2iupdt <instance_name> 
implicitly.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who run db2iupdt command (including installFixpack).   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V10.1 FixPack 3 or later.                  * 
****************************************************************
Local-Fix:
Please use -u option when running db2iupdt. 
Users can also change current fencedID by db2iupdt with -u 
option.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
This problem was first fixed in DB2 V10.1 FixPack 3.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95316 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.04.2013
08.10.2013
08.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList