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

SQL0956C THROWN WHEN CALLING PARSE PROCEDURE WITH AN INPUT SQL S TATEMENT
CONTAINING A COMMENT WITH COLON (:) FOLLOWED BY A SPACE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When calling the following procedure, 
 
DBMS_SQL.PARSE(cursorID, SQL statement, Oracle syntax 
compatibility flag) 
 
if the input SQL statement contains a comment that includes a 
colon (:) followed by a space character, the following error is 
incorrectly thrown: 
 
SQL0956C  "Not enough storage is available in the database heap 
to process the  statement."
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP3.                                    * 
****************************************************************
Local Fix:
available fix packs:
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
Fixed in DB2 v10.1 FP3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList