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 IC98357 Status: Closed

CALL CAPTURE_STORAGEMGMT_INFO FAILS WITH SQL0443N ON WINDOWS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
In DB2 v9.7 fix pack 8, the stored procedure 
CAPTURE_STORAGEMGMT_INFO fails with 
SQL0443N. And the error only occurs on Windows 64-bit 
platform. 
 
CALL CAPTURE_STORAGEMGMT_INFO(0, ' ', 'DB Name'); 
 
SQL0443N  Routine "SYSPROC.CAPTURE_STORAGEMGMT_INFO" (specific 
name "CAPT_STGMGMT_INF") has returned an error SQLSTATE with 
diagnostic text "SQL0303".  SQLSTATE=38553
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use the stored procedure CAPTURE_STORAGEMGMT_INFO  * 
* on windows.                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5FP3.                                     * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.12.2013
28.02.2014
28.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList