I am running DB2/NT 8.2.9.
When I issue the CALL CAPTURE_STORAGEMGMT_INFO(0,'','MYDBNAME')
I keep getting the following error:
SQL0443N Routine "*GMT_INFO" (specific name "") has returned an
error SQLSTATE with diagnostic text "SQL0803 Reason code or
token: 1,SYSTOOLS.STMG_OBJECT ".
An SQLSTATE was returned to DB2 by routine "<routine-name>"
(specific name "<specific-name>"), along with message text
"<text>". The routine could be a user-defined function or a
The user will need to understand the meaning of the error. See
your Database Administrator, or the author of the routine.
Errors that are detected by the IBM supplied functions in the
SYSFUN schema all return the SQLSTATE 38552. The message text
portion of the message is of the form:
where nn is a reason code meaning:
01 Numeric value out of range
02 Division by zero
03 Arithmetic overflow or underflow
04 Invalid date format
05 Invalid time format
06 Invalid timestamp format
07 Invalid character representation of a timestamp duration
08 Invalid interval type (must be one of 1, 2, 4, 8, 16, 32, 64,
09 String too long
10 Length or position in string function out of range
11 Invalid character representation of a floating point number
12 Out of memory
13 Unexpected error
Errors that are detected by the IBM supplied routines in the
SYSIBM or SYSPROC schemas and IBM supplied procedures in the
SYSFUN schema all return the SQLSTATE 38553. The message text
portion of the message contains a message number that may be an
SQLCODE, (for example, SQL0572N), a DBA error message (for
example, DBA4747), or some other indication from the routine as
to what error was encountered. Note that if the message for the
message number would normally contain tokens, these token values
are only available in the db2diag.log file.
sqlcode : -443
sqlstate : (the SQLSTATE returned by the routine).
Does anyone know how I can fix this problem. We were at V8 Fixpak 15 and I applied 18 hoping this would fix the problem, but it has not. Any help would be greatly appreciated!