home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97668 Status: Closed

PROCEDURE SYSPROC.GET_DBSIZE_INFO MAY INCORRECTLY RETURN ERROR SQL0493

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
Solution
This problem was first fixed in V9.7 Fix Pack 10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.11.2013
19.01.2015
19.01.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList