DBMS_XSLPROCESSOR.processXSL and ORA-03113

Question

Hi,
I got "ORA-03113: end-of-file on communication channel" error when use DBMS_XSLPROCESSOR.processXSL to transform an xml data.
The dump file contains:
----- PL/SQL Call Stack -----
object line object
handle number name
33C61A04 493 package body XDB.DBMS_XSLPROCESSOR
33C61A04 520 package body XDB.DBMS_XSLPROCESSOR
207BCF08 44 function DAN_DR_306.IMPACT1
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
_qmxdXobToLobStream           00000000            
+190
qmxdWriteToString+  CALLrel  qmxdXobToLobStream
37 +0
qmprprocessor_pxs CALLrel _qmxdWriteToString+  A6A4F90 0 7B4E358 7D0
ldoc2buf+280 0
__VInfreq__spefcmpa CALLreg 00000000 7CECD94 7B04D48 0 C 7B04D98 0
+210 C 7B04C58 0 C 7B4E358 7B4EBCC
7B4EBD4 7B4EBDC
spefmccallstd+147   CALLrel  spefcmpa+0 7CECB08 E 7B4EB48 7CEC5B8 0
Following is the simplified example that can be used to duplicate the error. If I use "<result/>" instead of "<!--result/-->" in the "xsldoc", the transformation works file. It seems the ora-03113 occurs when the transformation result is empty.
CREATE OR REPLACE FUNCTION impact1 (
          tsiModelUniqueName          varchar2
     ) RETURN integer IS
indoc VARCHAR2(2000);
xsldoc CLOB;
indomdoc DBMS_XMLDOM.DOMDocument;
xsltdomdoc DBMS_XMLDOM.DOMDocument;
myParser DBMS_XMLPARSER.parser;
proc DBMS_XSLPROCESSOR.processor;
xsl DBMS_XSLPROCESSOR.stylesheet;
result CLOB;
buf VARCHAR2(2000);
BEGIN
indoc := '<test>aaa</test>';
xsldoc := '<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml" version="1.0" encoding="UTF-8"/>
     <xsl:strip-space elements="*"/>
     <!-- process node comparison -->
     <xsl:template match="/test">     
     <!--result/-->     
     </xsl:template>
     </xsl:stylesheet>';
-- Get the new xml parser instance
myParser := DBMS_XMLPARSER.newParser;
-- Get the new xsl processor instance
proc := DBMS_XSLPROCESSOR.newProcessor;
-- Parse the XML document
DBMS_XMLPARSER.parseBuffer(myParser, indoc);
-- Get the XML's DOM document
indomdoc := DBMS_XMLPARSER.getDocument(myParser);
-- Parse the XSL document
DBMS_XMLPARSER.parseBuffer(myParser, xsldoc);
-- Get the XSL's DOM document
xsltdomdoc := DBMS_XMLPARSER.getDocument(myParser);
xsl := DBMS_XSLPROCESSOR.newStyleSheet(xsltdomdoc, '');
--apply stylesheet to DOM document  
DBMS_XSLPROCESSOR.processXSL(proc, xsl, indomdoc, buf);
DBMS_OUTPUT.put_line(buf);
DBMS_XMLDOM.freeDocument(indomdoc);
DBMS_XMLDOM.freeDocument(xsltdomdoc);
DBMS_XMLPARSER.freeParser(myParser);
DBMS_XSLPROCESSOR.freeProcessor(proc);
RETURN 1;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20100, 'Exception occurred in XSL Processsing Function :'||SQLERRM);
END;
Thanks for the input. /dan

Answer 1

The one I know if the DST patch. I am waiting for our DBA to let me know what has been installed since it last worked. I did notice that there are a number of SYS owned XML related JAVA CLASS objects with an INVALID statuses. They have "OracleXML" or "oracle/xdb/dom" in their names. I do not know if that is normal or not.
Mike