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

CRASH USING ARRAY DATA TYPE AND NESTED TYPES WITH PL SQL PRAGMA AUTONOMOUS
TRANSACTION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 instance will crash when using the PL SQL PRAGMA AUTONOMOUS 
TRANSACTION involving array data type with nested data types 
scenario.  For example array of rows.  The crash will occur 
only if array data types and nested data types are used with 
PRAGMA AUTONOMOUS TRANSACTION. 
 
A trap file will be created with the function stack below: 
 
<freeArrayOfRowLobMem> 
<sqlriArrayDescriptor::destroyChild> 
<sqlriArrayDescriptor::destroyAllChildren> 
<sqlriArrayDescriptor::destroy> 
<sqlerCopyRowOrArrayNestedData> 
<sqlerAutonomousRoutine::applicationSessionUnpackPsrs> 
<sqlerAutonomousRoutine::Finalize> 
<sqlerAutonomousInvoker> 
<sqlriAutonomousCall> 
(rest of stack truncated)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 version 10 Fixpack 2 to the database server.       * 
****************************************************************
Local Fix:
Do not use PRAGMA AUTONOMOUS TRANSACTION with array data types 
involving nested data types
Solution
Problem first fixed in DB2 version 10 Fixpack 2.  This fix 
should be applied to the DB2 database server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.07.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)