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

DB2PDCFG -FODC[DBCFG|DBMCFG|TRAPRESILIENCE] STATUS DOES NOT WORK FOR USER
WITH ONLY SYSMON AUTHORITY

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
If user has SYSMON authority only, the user won't be able to 
alter any db2pdcfg flags through following db2pdcfg options: 
-catch 
-cos 
-dbcfg 
-dbmcfg 
-fodc 
-trapresilience 
This is expected, but the user should be able to query the 
status of these options 
by specifying status sub-option. E.g. 
db2pdcfg -fodc status 
The problem is that, only 
db2pdcfg -catch status 
& 
db2pdcfg -cos status 
works for user with only SYSMON authority. The expected 
behaviour should be that other options with status sub-option 
should also work for user with only SYSMON authority.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4                       * 
****************************************************************
Local-Fix:
Lösung
First fixed in 10.5 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.04.2014
08.04.2015
08.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList