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

PROCEDURE SYSPROC.GET_DBSIZE_INFO MAY INCORRECTLY RETURN ERROR SQL0493

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When there is a problem during the execution of the 
SYSPROC.GET_DBSIZE_INFO procedure, 
the current error handling may obscure the real error and return 
a misleading error SQL0493 : 
 
 Routine "<routine-name>" (specific name "<specific-name>") has 
      returned a date, time or timestamp value which is 
syntactically or 
      numerically invalid. 
 
 
A common problem is a lack of select privileges on table 
"SYSTOOLS.STMG_DBSIZE_INFO" 
This should return error SQL0551 instead.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server to V9.7 Fix Pack 10 or higher         * 
****************************************************************
Local-Fix:
Try : grant select on table SYSTOOLS.STMG_DBSIZE_INFO to user 
"username"    to see if the problem is resolved.
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:
14.11.2013
19.01.2015
19.01.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList