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

SYSPROC.GET_DBSIZE_INFO ROUTINE INCORRECTLY REQUIRES SELECT PRIVILEGES ON
TABLE SYSTOOLS.STMG_DBSIZE_INFO

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Running procedure call sysproc.GET_DBSIZE_INFO(?, ?, ?, 0) as a 
user other than the instance owner, may return an error because 
of missing select privileges on table SYSTOOLS.STMG_DBSIZE_INFO. 
 
This is incorrect as the only privileges required to run this 
are : 
 
    SYSMON authority 
    EXECUTE privilege on the GET_DBSIZE_INFO procedure 
 
This is because the select on the SYSTOOLS.STMG_DBSIZE_INFO 
table is executed as dynamic sql within the admin stored 
procedure and the stored procedure has not been created with the 
DYNAMICRULES BIND option.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.7 Fix Pack 10 or higher    * 
****************************************************************
Local-Fix:
This can be resolved in 2 ways, either grant select privileges 
on SYSTOOLS.STMG_DBSIZE_INFO to the user executing the procedure 
or alternatively go to $HOME/sqllib/bnd  and run : 
db2 bind st_admin.bnd dynamicrules bind
Lösung
This problem was first fixed in V9.7 Fix Pack 10
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.11.2013
05.01.2015
05.01.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList