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

POTENTIAL OUT OF BOUND MEMORY ACCESS WITH ALTER DATABASE ADD/DROP COMMAND
USING CLUSTER MANAGER ENVIRONMENT.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If the path name of a new storage path is very long, a stack 
variable designed to hold it might not be big enough to hold it, 
resulting from out-of-bound memory access. The stack memory 
might be corrupted.  If it happens then the database might trap 
and a stack trace file showing function sqlbAlterDatabaseStorage 
will be created.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Environment using cluster manager with DB2 automatic storage * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the path name of a new storage path is very long, a stack * 
*                                                              * 
* variable designed to hold it might not be big enough to hold * 
* it,                                                          * 
* resulting from out-of-bound memory access. The stack memory  * 
*                                                              * 
* might be corrupted.  If it happens then the database might   * 
* trap                                                         * 
* and a stack trace file showing function                      * 
* sqlbAlterDatabaseStorage                                     * 
* will be created.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to fixpak 4, or avoid using a long path name for     * 
* storage paths.                                               * 
****************************************************************
Local Fix:
Try using a shorter path name.
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
The problem is fixed in v97 fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.01.2011
28.04.2011
28.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.