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

DB2UPDV97 RUN AGAINST A FP2 DATABASE WILL GRANT EXECUTE PRIVILEGE
TO PUBLIC FOR ROUTINES ON RESTRICTIVE DATABASES

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
db2updv97 is an optional tool executed after applying a new fix 
pack.  When moving from v9.7 Fix Pack 2 to v9.7 Fix Pack 3, 
db2updv97 will create two new routines and grant EXECUTE 
privilege to PUBLIC.  On restrictive databases, PUBLIC is not 
supposed to be granted EXECUTE privilege on these routines, 
however, it is currently being granted by default. 
 
The two functions that are granted EXECUTE privilege to PUBLIC 
on restrictive databases are : 
- SYSPROC.MON_GET_APPLICATION_HANDLE 
- SYSPROC.MON_GET_APPLICATION_ID
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Version 9.7 Fix Pack 3 servers on Linux, Unix and        * 
* Windows platforms, running db2updv97 on a Fix Pack 2         * 
* database that was created to be restrictive.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Execute privilege is granted to two newly created routines   * 
* by db2updv97.                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 Fix Pack 3a to run db2updv97, or run   * 
* db2updv97 with the -a option.  If you have already run       * 
* db2updv97 on DB2 Version 9.7 Fix Pack 3, then manually       * 
* revoke execute privilege from PUBLIC for these two routines. * 
****************************************************************
Local-Fix:
If you have applied v9.7 Fix Pack 3 and already run db2updv97, 
then issue two revoke execute from public statements against the 
two mentioned routines.  If you have not yet run db2updv97, then 
run it with the -a option like this: 
 
db2updv97 -d <dbname> -a 
 
which will ensure to assign the appropriate privileges for 
restrictive and non-restrictive databases alike.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in DB2 Version 9.7 Fix Pack 3a and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.10.2010
28.10.2010
28.10.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3,
9.7.FP3
Problem behoben lt. FixList in der Version