|
Problem IC79228
|
Status: Closed |
The SQLBFTPQ API function may return an incorrect SQL2032N error message |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 Fixpack 6 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 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in v9.7 Fixpack 6 or higher |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84295
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.10.2011
13.06.2012
13.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
