|
Problem IT30008
|
Status: Closed |
XML QUERY ERRORS ON AIX PLATFORM
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
On the AIX platform certain queries that raise an error during
parsing of the XML document or XPATH string may result in an
assert failure and an error being returned. Furthermore
subsequent XML queries that are valid may then return an error
which persist until the database server is restarted.
An example query that has invalid syntax :
select
extractvalue("AAA_A21.2345NBBB_B1-1.098050
YCCC_C312.00
09X",
'(1//nd11/nd21/nd31)[2]')
from systables where tabid=1;
This should result in error 8351 "Function (extractvalue)
Invalid input XML document or input XPATH string" however a
general exception error such as 9791 "User Defined Routine
(extractvalue) execution failed" may be returned instead with an
assert failure message appearing in the database server's
message log. The AF file shows a stack similar to:
(oninit)afhandler
(oninit)affail_interface
(oninit)mt_ex_throw_sig@AF11_4
(oninit)afsig_handler
(*nosymtab*)0x900000000e5f904
(*nosymtab*)0x900000000e5fa38
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPathExecutionContextDefau
lt::error
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::findNodesOnUnknownA
xis
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::step
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::executeMore
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::executeMore
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::findNodeSet
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::step
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::locationPath
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::executeMore
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPath::execute
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPathEvaluator::evaluate
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPathEvaluator::evaluate
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPathEvaluator::evaluate
(.10.FC13/lib/libxml.udr)xslt4c_1_10::XPathEvaluator::selectNode
List
(.10.FC13/lib/libxml.udr)xmlextractvalue
(oninit)udrlm_clang_execute_internal
(oninit)udrlm_clang_execute
(oninit)udrlm_exec_routine
(oninit)udr_execute
(oninit)ev_udr
(oninit)new_eval
(oninit)evalcols
(oninit)getrow
(oninit)fetchrow
(oninit)exfetch
(oninit)sql_nfetch
(oninit)sq_nfetch
(oninit)sqmain
After this error subsequent valid XML queries fail with error
8354 "Function (extractvalue) Exception received for ICU memory
allocation." |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of IDS 12.10.xC13. *
****************************************************************
* PROBLEM DESCRIPTION: *
* On the AIX platform certain queries that raise an error *
* during *
* parsing of the XML document or XPATH string may result in an *
* assert failure and an error being returned. Furthermore *
* subsequent XML queries that are valid may then return an *
* error *
* which persist until the database server is restarted. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
An alternative to restarting the database server may be to stop
and start the idsxmlvp VPs using the onmode -p command. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of IDS 12.10.xC13. *
****************************************************************
* PROBLEM DESCRIPTION: *
* On the AIX platform certain queries that raise an error *
* during *
* parsing of the XML document or XPATH string may result in an *
* assert failure and an error being returned. Furthermore *
* subsequent XML queries that are valid may then return an *
* error *
* which persist until the database server is restarted. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Comment |
Fixed in IDS 12.10.xC14. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.08.2019
19.09.2019
19.09.2019 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC14
|
| Problem solved according to the fixlist(s) of the following version(s) |
