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

IUD OPERATIONS AGAINST COLUMNAR TABLES COULD ENCOUNTER AN ABEND WHEN PLAN
IS COMPLEX AND NLJN IS PRESENT ABOVE IUD OPERATION

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
WHEN UPDATE/DELETE/INSERT FROM SELECT IS DONE AGAINST COLUMNAR
TABLES
AND PLAN HAS IUD LOLEPOP ON AN INNER OF ROWSTORE NLJN AND THE
INNER IS MORE COMPLEX THEN JUST CDE OPERATION,
AND WE NEED TO IUD MORE THEN ONE ROW,  THEN THE TRAP WITH THE
FOLLOWING STACK IS POSSIBLE:

      cdeInterface::getPRT
      sqlriCdeFastUpdate
      sqlriSectInvoke
      sqlrr_dss_router
      sqlrr_subagent_router

delete could trap with the following stack:
sqloEDUCodeTrapHandler
cdeTableAccessorInterface::deleteRow
cdeInterface::performDelete
sqlriCdeFastDelete
sqlriSectInvoke
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Try to force a different plan, one that does not have a rowstore
NLJN above an IUD operation.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.04.2018
27.11.2018
27.11.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)