DB2 - Problem description
| Problem IT04247 | Status: Closed |
DB2 MAY TRAP WHEN CHECKING FOR PROCEDURE DATA CONFLICTS WHEN DBMS_SQL ROUTINES ARE USED | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
When a procedure is invoked from a trigger, a dynamic compound
statement, an SQL function or SQL method checking is required
to ensure the integrity of the database and raise SQL0746N
errors if need be.
(See "Data conflicts when procedures read from or write to
tables" in the product documentation for more information
on this topic.)
When the procedures make use of DBMS_SQL routines, references
to internal constructs related to this checking are cached
and are not correctly purged when the constructs are freed,
leaving stale references.
Problems only occur when further executions of the DBMS_SQL
routines take place within the same connection as they
attempt to use the stale references.
Stacks associated with the problem will normally start with
memory management functions - likely falsely reporting memory
corruption - but will always include a function starting with
"sqlriRWCon".
An example stack:
sqloCrashOnCriticalMemoryValidationFailure
sqloCrashOnCriticalMemoryValidationFailure@glue707
sqlofmblkEx
sqlra_sqlC_mem_free_block__FP8sqlrr_cbUlPv
sqlriRWConCheck__FP8sqlrr_cbUiP14sqlriTableInfo
sqlriRWConCheck__FP8sqlrr_cbUiP14sqlriTableInfo@glue1032
sqlriSectInitializeSimple__FP8sqlrr_cbP9sqlri_shdb
... | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5. * **************************************************************** | |
| Local Fix: | |
| Solution | |
First fixed in DB2 Version 10.1 Fix Pack 5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.09.2014 14.07.2015 14.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|