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

RETURN OF SQL0083C MAY CAUSE A HANG in an SMP environment.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Having SQL0083C returned may result in a hang of the database. 
This is only in a SMP env. (INTRA_PARALLEL YES) 
 
Stack: 
IntrptWaitLock 
sqlri_hsjnInit 
 
For example: 
 
insert into t.t4 select c.c1, c.c2 from t.t3 c, ( select b.c1, 
b.c2 from t.t1 a, t.t2 b where a.c1=b.c1 ) d where c.c2=d.c2 
 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0083C  A memory allocation error has occurred.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SMP                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install this fix.                                            * 
****************************************************************
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
See Error Description. Install this fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.06.2013
04.11.2013
04.11.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