DB2 - Problem description
| Problem IC87862 | Status: Closed |
XML INPUT STORED PROCEDURE/UDF WITH PARAMETER MARKER AND REOPT ALWAYS ENABLED CAN RETURN SQL0901N | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
The following error may be returned to an application calling a
UDR or UDF :
SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed.
(Reason "QGM internal error: xpath does not have context qnc!".)
SQLSTATE=58004
This happens when REOPT ALWAYS was enabled when the procedure
was created
( via SYSPROC.SET_ROUTINE_OPTS('REOPT ALWAYS') ) and when one of
the input parameters is of data type XML.
There will be a trap file produced as well with the following
callstack :
sqloDumpEDU
sqldDumpContext
sqlrr_dump_ffdc
sqlzeDumpFFDC
sqlzeSqlCode
sqlnn_erds
sqlnq_xp_merge_xpaths
sqlnr_merge_compute_boxes
sqlnr_merge_and_create_mep
sqlnr_xq_native_optprep
sqlnr_optprep
sqlnr_optprep_action
sqlnr_comp
sqlnr_seq
sqlnr_rcc
sqlnr_exe
sqlnn_cmpl | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 101 fix pack 2 * **************************************************************** | |
| Local Fix: | |
Do not use REOPT ALWAYS for stored procedures that match the criteria of this apar. Recode the application to avoid using XML input parameters. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
Problem is fixed in DB2 version 101 fix pack 2 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 16.01.2013 16.01.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|