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

The SQLBFTPQ API function may return an incorrect SQL2032N error message

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If you are using the pre-v97 version of the structure 
SQLB_TBSPQRY_DATA and calling sqlbftpq this can return the 
following error: 
 
SQL2032N  The "version id" parameter is not valid. 
SQLSTATE=22531 
 
This can be mis-leading as what this means is that the 
Tablespace lifeLSN value exceeds the size allocated for the 
target area.  In the pre-v97 structure we have a size of 6bytes 
for the lifeLSN.  However in v9.7 we can have a lifeLSN of 
8bytes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpack 1 or Higher                         * 
****************************************************************
Local Fix:
- Recompile application and make it use the v9.7 structure 
SQLB_TBSPQRY_DATA. 
- Using the MON_GET_TABLESPACE and the MON_GET_CONTAINER table 
functions instead.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in v10.1 Fixpack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
13.11.2012
13.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList