Parsing XML stored in CLOB (PL/SQL)

Hello,
I would like to parse XML document like the example below.
When it is stored in VARCHAR2 column, parsing works well.
When it is stored in CLOB column, I get error message:
"ORA-20100: Error occurred while parsing: Invalid char in text."
The <text> section contains valid characters of ISO-8859-2 encoding.
If <text> section contains only ASCII compatible characters, parsing works well.
<?xml version="1.0" encoding="ISO-8859-2"?>
<body>
<text> ìèø}amizù </text>
</body>
Is it a bug? Or where is problem?
Any help would be appreciated.

I used such an example to parse several Varchar2 strings in a given DB session:
BEGIN
parser := xmlparser.newparser ;
xmlparser.parsebuffer(parser,xmlout) ;
domdoc := xmlparser.getDocument(parser) ;
xmlparser.FREEPARSER(parser) ;
parser.id := -1 ;
nodes := xslprocessor.selectNodes(
xmldom.makenode(domdoc),
'Positionen/Position') ;
for i in 1 .. xmldom.getLength(nodes) loop
node := xmldom.item(nodes,i-1) ;
-- do s/thing with the node
end loop ;
xmldom.freedocument(domdoc) ;
RETURN(komponenten) ;
EXCEPTION
WHEN OTHERS THEN
if parser.id <> -1 then xmlparser.freeparser(parser) ;
end if ;
if domdoc.id <> -1 then xmldom.freedocument(domdoc) ;
end if ;
RAISE ;
END ;
However, after about 2000 of nodes lists parsed, I get an ArrayIndexOutOfBoundsException from XMLNodeCover. Obviously, I should release the nodes or the nodelist, but I have not found any procedure to do this.
Pascal

Similar Messages

Parsing XML passed as CLOBs to stored procedures

I am a newbie using XML with PL/SQL. I would like to pass XML as a CLOB to a stored procedure, parse the nodes in a loop and insert or update records. Something like this:
The xml:
<emps>
<emp>
<empno>7369</empno>
<ename>SMITH</ename>
</emp>
<emp>
<empno>7499</empno>
<ename>ALLEN</ename>
</emp>
</emps>
In the stored procedure:
CREATE update_emps( xmlCLob in CLOB )
begin
load xmlClob into parser p
nodelist = p.someMethod( '/emps/emp' )
for each node in nodelist
insert into emp( empno, ename) values ( node.empno, node.ename
end loop
cleanup
end
Any assistance you could provide would be greatly appreciated.
TIA

If the file size is not large, it seems easier to use XSLT to transform the doc and using XSU to do the updates.

Parsing XML from a CLOB

I was trying to check the well-formedness of XML in a CLOB. I have an xml file called Claim77804.xml. I was working on Building Oracle XML applications by Steve Muench. I created the procedure and it was created succesfully but it does not do what it says in the code:
SQL> CREATE OR REPLACE PROCEDURE CheckXMLInCLOB(c CLOB,
2 wellFormed OUT BOOLEAN,
3 error OUT VARCHAR2) IS
4 parser xmlparser.Parser;
5 xmldoc xmldom.DOMDocument;
6 XMLParseError EXCEPTION;
7
8 -- Associate the XMLParseError exception with the -20100 error code
9 PRAGMA EXCEPTION_INIT( XMLParseError, -20100 );
10
11 BEGIN
12
13 -- (1) Create a new parser
14 parser := xmlparser.newParser;
15
16 -- (2) Attempt to parse the XML document in the CLOB
17 xmlparser.ParseCLOB(parser,c);
18
19 -- (3) Free the parser.
20 xmlparser.freeParser(parser);
21
22 -- If the parse succeeds, we'll get here
23 wellFormed := TRUE;
24 EXCEPTION
25 -- If the parse fails, we'll jump here.
26 WHEN XMLParseError THEN
27 xmlparser.freeParser(parser);
28 wellFormed := FALSE;
29 error := SQLERRM;
30 END;
31
32 /
Procedure created.
Is there anything i should be doing? Please advise me.

Don't worry. I have solved the question. Don't bother answering. Thanks for nothing guys.

Retrieve XML stored in CLOB as columns

Hi,
I have the below table that holds XML in a CLOB
CREATE TABLE testxml
(idcol NUMBER(3), xml_data CLOB
INSERT
INTO testxml VALUES
    201,
<TRADE>
   <TRADETYPE>SWAP</TRADETYPE>
   <SUBTYPE>CDS</SUBTYPE>
   <TRADEHEADER>
      <ACTION>NEW</ACTION>
      <SOURCEID>ABS-CD</SOURCEID>
      <TRADEID>20595896</TRADEID>
   </TRADEHEADER>
   <TRADELEGS>
      <TRADELEG>
         <PAY_OR_RECEIVE>P</PAY_OR_RECEIVE>
         <FIXED_FLOAT_IND>FLT</FIXED_FLOAT_IND>
         <DAY_COUNT_BASIS>A365F</DAY_COUNT_BASIS>
         <ORIG_PRIMARY_CURRENCY>ZAR</ORIG_PRIMARY_CURRENCY>
         <FIRST_VALUE_DATE>20120511</FIRST_VALUE_DATE>
      </TRADELEG>
      <TRADELEG>
         <PAY_OR_RECEIVE>R</PAY_OR_RECEIVE>
         <FIXED_FLOAT_IND>FIX</FIXED_FLOAT_IND>
         <DAY_COUNT_BASIS>A365F</DAY_COUNT_BASIS>
         <ORIG_PRIMARY_CURRENCY>ZAR</ORIG_PRIMARY_CURRENCY>
         <FIRST_VALUE_DATE>20120511</FIRST_VALUE_DATE>
      </TRADELEG>
   </TRADELEGS>
   <PVS>
      <PV_SOURCE>ABS-CD</PV_SOURCE>
      <PV>
         <NPV>0</NPV>
         <NPV_CCY>ZAR</NPV_CCY>
         <VALUATION_DATE>20130628</VALUATION_DATE>
         <LEG_NUMBER>1</LEG_NUMBER>
      </PV>
      <PV>
         <NPV>2214864.54</NPV>
         <NPV_CCY>ZAR</NPV_CCY>
         <VALUATION_DATE>20130628</VALUATION_DATE>
         <LEG_NUMBER>2</LEG_NUMBER>
      </PV>
   </PVS>
   <CREDIT_DERIVATIVES>
      <CREDIT_DERIVATIVE>
         <NOMINAL>100000000</NOMINAL>
         <MATURITY_DATE>20170620</MATURITY_DATE>
         <BUY_SELL_INDICATOR>SELL</BUY_SELL_INDICATOR>
         <CURRENCY>ZAR</CURRENCY>
      </CREDIT_DERIVATIVE>
      <CREDIT_DERIVATIVE>
         <NOMINAL>100002000</NOMINAL>
         <MATURITY_DATE>20170620</MATURITY_DATE>
         <BUY_SELL_INDICATOR>BUY</BUY_SELL_INDICATOR>
         <CURRENCY>USD</CURRENCY>
      </CREDIT_DERIVATIVE>
   </CREDIT_DERIVATIVES>
</TRADE>
I need the data to be retrieved as columns. I have tried the below SQL but it works for one XMLTable i.e. TRADELEGS. But If I try to use another XMLTable for PVS then it does a cartesian join.
SELECT id,
xmltype(xml_data).extract('/TRADE/TRADETYPE/text()').getStringVal()          AS TRADETYPE,
xmltype(xml_data).extract('/TRADE/SUBTYPE/text()').getStringVal()            AS SUBTYPE,
xmltype(xml_data).extract('/TRADE/TRADEHEADER/ACTION/text()').getStringVal() AS ACTION,
x.PAY_OR_RECEIVE,
x.FIXED_FLOAT_IND
FROM testxml,
XMLTable( '/TRADE/TRADELEGS/TRADELEG' passing XMLTYPE(xml_data)
columns
PAY_OR_RECEIVE VARCHAR2(20) PATH 'PAY_OR_RECEIVE'
, FIXED_FLOAT_IND VARCHAR2(20) PATH 'FIXED_FLOAT_IND' ) x;
The below query does not work:
SELECT id,
xmltype(xml_data).extract('/TRADE/TRADETYPE/text()').getStringVal()          AS TRADETYPE,
xmltype(xml_data).extract('/TRADE/SUBTYPE/text()').getStringVal()            AS SUBTYPE,
xmltype(xml_data).extract('/TRADE/TRADEHEADER/ACTION/text()').getStringVal() AS ACTION,
tradeleg.PAY_OR_RECEIVE,
tradeleg.FIXED_FLOAT_IND
,xmltype(xml_data).extract('/TRADE/PVS/PV_SOURCE/text()').getStringVal() AS PV_SOURCE
,pvs.npv,
pvs.VALUATION_DATE
FROM testxml,
XMLTable( '/TRADE/TRADELEGS/TRADELEG' passing XMLTYPE(xml_data)
columns
PAY_OR_RECEIVE VARCHAR2(1) PATH 'PAY_OR_RECEIVE'
, FIXED_FLOAT_IND VARCHAR2(3) PATH 'FIXED_FLOAT_IND' ) tradeleg
,XMLTable( '/TRADE/PVS/PV' passing XMLTYPE(xml_data)
columns
NPV NUMBER PATH 'NPV'
, VALUATION_DATE VARCHAR2(8) PATH 'VALUATION_DATE' ) pvs
WHERE id = 1;
I need the output for TRADELEGS, PVS and CREDIT_DERIVATIVES.
Regards,
Vikram

But If I try to use another XMLTable for PVS then it does a cartesian join.
Of course it does. You have to use a join condition of some kind.
What's the correlation between TRADELEGS, PVS and CREDIT_DERIVATIVES?
I guess you can relate a PV to a TRADELEG via the LEG_NUMBER, right? But what about CREDIT_DERIVATIVE to PV or to TRADELEG?
I need the output for TRADELEGS, PVS and CREDIT_DERIVATIVES.
Explain what that output should look like.

Use of XML parser to read/parse xml stored in DB as CLOB

Hello,
I am new to XML technology. I have xml data stored in DB as
CLOB. I need to parse this data to retrieve VALUE fro certain
tags. I would greatly appreciate any help. Any examples that
manipulate xml data stored in DB can be of extreme help.
DesiDBA

As you use Oracle 9.0.1. We suggest you use XMLType instead of
CLOB to store your XML documents.
You can use xmlType.extract() to get the elements within the
XMLDocuments.
Please refer to our Oracle9i XML Demo for examples.
http://otn.oracle.com/tech/xml/xdk_sample/xdkdemo_faq.html
For Instructions:
http://ws5.olab.oracle.com/faqdemo/source/instruction.xsql?
pagename=ins_xmltype
Or you have to do the SQL query to get XML documents and parse
each document and extract the content yourself using XML Parser
for PL/SQL.
Thanks.

Validating XML stored in CLOB without exceptions for malformed XML

Hello,
I have a CLOB column that should contain an XML which conforms to a registered XSD schema. However, there might also be cases, in which the CLOB content violates the XSD or is not even wellformed XML at all. Now I am trying to find a way to either
identify all records, for which the CLOB contains well-formed XML that validates against my schema (find all "good" records) , or
find all the other records (those with either no XML at all, malformed XML, or XML that does not validate against the XSD) (find all "exceptions")
The problem is that all XML-validation methods I know of (e.g. isXmlValid or XmlType.isSchemaValid) require an XmlType instance, and that records, for which no proper XmlType can be constructed from the CLOB, because the CLOB does not contain well-formed XML, will cause an exception, rather than just returning false or NULL or something else I could filter out.
Is there a way to do something like
SELECT * FROM MYTABLE where <MY_XML_COL is wellformed XML> and <MY_XML_COL validates against 'blabla.xsd'>
without getting an ORA-31011 or whatever other kind of exception as soon as there is a row that does not contain proper XML?
Thank you...

So here is my example - this will be quiet a long post now...
First, I create the table with the CLOBs
CREATE TABLE ZZZ_MINITEST_CLOB (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_DOC CLOB,
REMARKS VARCHAR2(1000),
CONSTRAINT PK_ZZZ_MINITEST_CLOB PRIMARY KEY (ID)
) NOLOGGING;
Then I insert some examples
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
10,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>one.one</l2Name>
</l2Node>
<minitestId>1</minitestId>
<minitestName>One</minitestName>
</minitest_root>',
'Basic valid example');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
20,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>two.one</l2Name>
</l2Node>
<minitestId>2</minitestId>

</minitest_root>',
'Invalid - minitestName element is missing');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
30,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>three.one</l2Name>
</l2Node>

<minitestName>Three</minitestName>
<minitestId>3</minitestId>
</minitest_root>',
'Invalid - minitestName and minitestId are switched');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
40,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>four.one</l2Name>
</l2Node>
<l2Node>
<l2Num>2</l2Num>
<l2Name>four.two</l2Name>
</l2Node>
<l2Node>
<l2Num>3</l2Num>
<l2Name>four.three</l2Name>
</l2Node>
<minitestId>4</minitestId>
<minitestName>Four</minitestName>
</minitest_root>',
'Valid - multiple l2Node elements');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
50,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>five.one</l2Name>
</l2Node>
<l2Node>
<l2Num>2</l2Num>
<l2Name>five.two</l2Name>
</l2Node>
<minitestId>4</minitestId>
<minitestName>Five</minitestName>

<l2Node>
<l2Num>3</l2Num>
<l2Name>five.three</l2Name>
</l2Node>
</minitest_root>',
'Invalid - another l2Node node, but too far down');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
60,
'something that is not even xml',
'Invalid - something that is not even xml');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
70,
NULL,
'Invalid - good old NULL');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
80,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>
<unexpected_node>
this one should not be here!
</unexpected_node>
</l2Name>
</l2Node>
<minitestId>8</minitestId>
<minitestName>Eight</minitestName>
</minitest_root>',
'Invalid - unexpected addl node');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
90,
'<something> that has tags but is no xml </either>',
'Invalid - something that has tags but is no xml either');
COMMIT;
Next I register the XSD...
BEGIN
DBMS_XMLSCHEMA.REGISTERSCHEMA(
'http://localhost/minitest.xsd',
'<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:oraxdb="http://xmlns.oracle.com/xdb" oraxdb:storeVarrayAsTable="true" oraxdb:schemaURL="http://localhost/minitest.xsd">
<xs:element name="minitest_root" oraxdb:SQLName="MINITEST_ROOT" oraxdb:SQLType="MINITEST_TYPE" oraxdb:defaultTable="" oraxdb:tableProps="NOLOGGING" oraxdb:maintainDOM="false">
    <xs:complexType oraxdb:SQLType="MINITEST_TYPE" oraxdb:maintainDOM="false">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" ref="l2Node" oraxdb:SQLName="L2_NODE" oraxdb:SQLType="L2_NODE_TYPE" oraxdb:SQLCollType="L2_NODE_COLL" oraxdb:maintainDOM="false"/>
        <xs:element ref="minitestId" oraxdb:SQLName="MINITEST_ID" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false"/>
        <xs:element ref="minitestName" oraxdb:SQLName="MINITEST_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:element name="l2Node" oraxdb:SQLName="L2_NODE" oraxdb:SQLType="L2_NODE_TYPE" oraxdb:defaultTable="" oraxdb:tableProps="TABLESPACE CATALOG NOLOGGING" oraxdb:maintainDOM="false">
    <xs:complexType oraxdb:SQLType="L2_NODE_TYPE" oraxdb:maintainDOM="false">
      <xs:sequence>
        <xs:element ref="l2Num" oraxdb:SQLName="L2_NUM" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false"/>
        <xs:element ref="l2Name" oraxdb:SQLName="L2_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:element name="l2Num" type="number10_0Type" oraxdb:SQLName="L2_NUM" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false" />
<xs:element name="l2Name" type="varchar100Type" oraxdb:SQLName="L2_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false" />
<xs:element name="minitestId" type="number10_0Type" oraxdb:SQLName="MINITEST_ID" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false" />
<xs:element name="minitestName" type="varchar100Type" oraxdb:SQLName="MINITEST_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false" />
<xs:simpleType name="varchar100Type">
    <xs:restriction base="xs:string">
      <xs:maxLength value="100"/>
    </xs:restriction>
</xs:simpleType>
<xs:simpleType name="number10_0Type">
    <xs:restriction base="xs:integer">
      <xs:totalDigits value="10"/>
    </xs:restriction>
</xs:simpleType>
</xs:schema>',
GENTABLES=>FALSE
END;
And then I create my XML tables - four different ones for four different test cases. I am trying unstructured binary XML and strucured OR-based XML, each with and without a trigger.
One with structured OR storage and no trigger
CREATE TABLE ZZZ_MINITEST_ORXML (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_ORXML PRIMARY KEY (ID)
) NOLOGGING
VARRAY "XML_CONTENT"."XMLDATA"."L2_NODE" STORE AS TABLE "ZZZ_OR_L2_NODE" (NOLOGGING) RETURN AS LOCATOR
XMLTYPE XML_CONTENT STORE AS OBJECT RELATIONAL XMLSCHEMA "http://localhost/minitest.xsd" ELEMENT "minitest_root";
One with structured OR storage which will also have a trigger added further down
CREATE TABLE ZZZ_MINITEST_ORXML_TRGR (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_ORXML_TRGR PRIMARY KEY (ID)
) NOLOGGING
VARRAY "XML_CONTENT"."XMLDATA"."L2_NODE" STORE AS TABLE "ZZZ_OR_L2_NODE_TRGR" (NOLOGGING) RETURN AS LOCATOR
XMLTYPE XML_CONTENT STORE AS OBJECT RELATIONAL XMLSCHEMA "http://localhost/minitest.xsd" ELEMENT "minitest_root";
One with unstructured binary XML in a SECUREFILE, no trigger
CREATE TABLE ZZZ_MINITEST_BINXML_TRGR (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_BINXML_TRGR PRIMARY KEY (ID)
) NOLOGGING
XMLTYPE COLUMN XML_CONTENT STORE AS SECUREFILE BINARY XML
(NOCOMPRESS NOCACHE NOLOGGING KEEP_DUPLICATES);
One with unstructured binary XML in a SECUREFILE, which will also have a trigger
CREATE TABLE ZZZ_MINITEST_BINXML (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_BINXML PRIMARY KEY (ID)
) NOLOGGING
XMLTYPE COLUMN XML_CONTENT STORE AS SECUREFILE BINARY XML
(NOCOMPRESS NOCACHE NOLOGGING KEEP_DUPLICATES);
Then I create the error logging tables
begin
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_BINXML', 'ZZZ_MINITEST_BINXML_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_BINXML_TRGR', 'ZZZ_MINITEST_BINXML_TRGR_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_ORXML', 'ZZZ_MINITEST_ORXML_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_ORXML_TRGR', 'ZZZ_MINITEST_ORXML_TRGR_E', NULL, NULL, TRUE);
END;
Now the two triggers
create or replace trigger TRG_ZZZ_MINITEST_BINXML
BEFORE UPDATE OR INSERT ON ZZZ_MINITEST_BINXML_TRGR
REFERENCING NEW AS NEW
for each row
BEGIN
:NEW.XML_CONTENT := :NEW.XML_CONTENT.createSchemaBasedXML('http://localhost/minitest.xsd');
:NEW.XML_CONTENT.SCHEMAVALIDATE();
END TRG_ZZZ_MINITEST_BINXML;
CREATE OR REPLACE TRIGGER TRG_ZZZ_MINITEST_ORXML
BEFORE UPDATE OR INSERT ON ZZZ_MINITEST_ORXML_TRGR
REFERENCING NEW AS NEW
for each row
BEGIN
:NEW.XML_CONTENT := :NEW.XML_CONTENT.createSchemaBasedXML('http://localhost/minitest.xsd');
:NEW.XML_CONTENT.SCHEMAVALIDATE();
END TRG_ZZZ_MINITEST_ORXML;
I also tried to just validate the XML using queries such as the below, since validating all without the WHERE also caused exception and abortion:
SELECT ID, DECODE(XMLISVALID(XMLTYPE(XML_DOC), 'http://localhost/minitest.xsd'), 1, 'Y', 0, 'N', '?') VALID
FROM ZZZ_MINITEST_CLOB WHERE ID=90;
The results are in column "VALID" in the below tables
I tried inserting all records from ZZZ_MINITEST_CLOB into the four test tables at once using a query such as
INSERT INTO ZZZ_MINITEST_ORXML_TRGR
SELECT ID, XMLPARSE(DOCUMENT XML_DOC WELLFORMED) FROM ZZZ_MINITEST_CLOB
LOG ERRORS INTO ZZZ_MINITEST_ORXML_TRGR_E REJECT LIMIT UNLIMITED;
I also tried different versions of creating the XML in the SELECT portion:
XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
XMLTYPE(XML_DOC)
XMLTYPE(XMLDOC, 'http://localhost/minitest.xsd', 0, 1)
Almost all combinations of the four test tables with the four ways to instantiate the XML caused exceptions and query abortion despite the LOG ERRORS INTO clause.
In order to find the exact problems, I started inserting records one by one using queries like
INSERT INTO ZZZ_MINITEST_ORXML
SELECT ID, XMLPARSE(DOCUMENT XML_DOC) FROM ZZZ_MINITEST_CLOB WHERE ID=10
LOG ERRORS INTO ZZZ_MINITEST_ORXML_E REJECT LIMIT UNLIMITED;
or
INSERT INTO ZZZ_MINITEST_BINXML_TRGR
SELECT ID, XMLTYPE(XMLDOC, 'http://localhost/minitest.xsd', 0, 1) FROM ZZZ_MINITEST_CLOB WHERE ID=20
LOG ERRORS INTO ZZZ_MINITEST_BINXML_TRGR_E REJECT LIMIT UNLIMITED;
I captured the results of each in the below four tables. "1" and "0" are number of rows inserted. 0 means there was no record inserted and instead, there was an error logged in the ERROR LOGGING table.
The ORA-????? exception numbers mean that this error actually caused the INSERT to fail and abort rather than just being logged in the LOGGING TABLE.These are the most critical cases for me. Why do these exceptions "bubble up" forcing the query to be aborted rather than being logged in the error log as well???
This table is for INSERT of XMLs using XMLTYPE(XML_DOC)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
EX
ORA-31011
ORA-31011
ORA-31011
ORA-31011
70
NULL
EX
ORA-06502
ORA-06502
ORA-06502
ORA-06502
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
EX
ORA-31011
ORA-31011
ORA-31011
ORA-31011
This table is for INSERT of XMLs using XMLTYPE(XML_DOC, 'http://localhost/minitest.xsd', 0, 1)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
EX
ORA-31043
ORA-31043
ORA-31043
ORA-31043
70
NULL
EX
ORA-06502
ORA-06502
ORA-06502
ORA-06502
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
EX
ORA-31043
ORA-31043
ORA-31043
ORA-31043
This table is for INSERT of XMLs using XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
ORA-31061
0
ORA-31011
ORA-31011
70
NULL
1
0
1
0
80
addl. Node
N
0
0
ORA-31187
ORA-31187
90
crappy xml
ORA-31061
0
ORA-30937
ORA-30937
This table is for INSERT of XMLs using XMLPARSE(DOCUMENT XML_DOC) (same as above, but without "WELLFORMED")
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
ORA-31011
ORA-31011
ORA-31011
ORA-31011
70
NULL
1
0
1
0
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
ORA-31011
ORA-31011
ORA-31011
ORA-31011
As you can see, different ways to instantiate the XML which is being inserted will cause different results for the most critical cases (60, 80 and 90). One will go through with an error logged in the logging table and no record inserted, others cause exceptions. Also, using XMLPARSE with or without WELLFORMED causes different ORA numbers for record 90...
It seems like the only way to not get any exceptions for my test records is inserting XMLs that were created using XMLPARSE (DOCUMENT ... WELLFORMED) into the trigger-protected binary XML table. However, that causes me to miss record number 80, which is one that I really need, because it is well formed and I could use XSLTs to fix the XML by removing the extra tags, as long as I know which ones those are.

Parse XML Elements/Attributes from CLOB in PL/SQL

Hi folks,
I'm new to XML development in Oracle...I need some help in Parsing a XML stored in a CLOB column using PL/SQL.
We are using Oracle 9i R2. Do i need install the XDK and /or XML DB?
Basically the xml has some quiz questions and the answers to the quiz. Once student submits the quiz we need parse the XML and calculate the grade.
Any help is appreciated...
Thanks,

A bit dirty but this works:
Create an XMLType based on the CLOB contents...
select extractvalue(value(x), '/PERSON/PER_ID/text()') PER_ID, extractvalue(value(x), '/PERSON/PER_ID/@changed') PER_ID_CHG
, extractvalue(value(x), '/PERSON/SURNAME/text()') PER_SURNAME, extractvalue(value(x), '/PERSON/SURNAME/@changed') PER_SURNAME_CHG
, extractvalue(value(x), '/PERSON/ADDRESS/STREET_NO/text()') PER_STREET_NO, extractvalue(value(x), '/PERSON/ADDRESS/STREET_NO/@changed') PER_STREET_NO_CHG
, extractvalue(value(x), '/PERSON/ADDRESS/POSTCODE/text()') PER_POSTCODE, extractvalue(value(x), '/PERSON/ADDRESS/POSTCODE/@changed') PER_POSTCODE_CHG
from table(xmlsequence(extract(xmltype('
<PERSON>
<PER_ID changed="1">260180</PER_ID>
<SURNAME changed="2">MARTIN</SURNAME>
<ADDRESS>
<STREET_NO changed="3">1</STREET_NO>
<POSTCODE changed="4">LE3 8RA</POSTCODE>
</ADDRESS>
</PERSON>')
, 'PERSON')
) x;

How to read XML data stored in CLOB in Concurrent prog Output

Hi All,
I'm trying to Generate the XML Data as concurrent Program output. I have a PL/SQL package which generated the XML data by using SQL/XML functions. I'm storing the generated XML data in a CLOB variable. But when i try to read the data using fnd_file.put_line(fnd_file.OUTPUT,XML_Data) it doesn't display data more than 32767 bytes.
Please help me out to understand what could be done to read the data in chunks. I have tried many logic's to print chunks of data but the output tags are either chopped off and errors out saying Tag not found.
My logic is as below:
v_handler:= DBMS_XMLGEN.newContext(v_xml_query);
--Sets NULL handling options
DBMS_XMLGen.SetNullHandling(v_handler, dbms_xmlgen.EMPTY_TAG ) ;
--Set special character handling
DBMS_XMLGEN.setConvertSpecialChars(v_handler, TRUE);
-- Specified whether to use an XML attribute to indicate NULLness of particular entity in the XML document
DBMS_XMLGen.useNullAttributeIndicator(v_handler,TRUE);
-- set Checking invalid chars
DBMS_XMLGEN.setCheckInvalidChars(v_handler, TRUE);
-- get the xml data as required
v_xml_data:= DBMS_XMLGEN.getXMLtype(v_handler);
SELECT XMLROOT(v_xml_data.extract('/*'),VERSION '1.0').getClobVal() into v_new_xml_Data from dual;
-- get the length of the xml generated
v_clob_len := dbms_lob.getlength(v_new_xml_Data);
FND_FILE.PUT_LINE(FND_FILE.LOG,'The Clob length is :'|| v_clob_len);
-- logic to process string more than 32767 Processing by each character
v_offset :=1;
while (v_offset <= v_clob_len)
LOOP
v_char := dbms_lob.substr(v_new_xml_Data, 1, v_offset);
IF (v_char = CHR(10))
then
fnd_file.new_line(fnd_file.output, 1);
else
fnd_file.put(fnd_file.output, v_char);
end if;
v_offset := v_offset + 1;
END LOOP;
FND_FILE.PUT_LINE(FND_FILE.LOG,'The offset is :'|| v_offset);
FND_FILE.NEW_LINE(FND_FILE.OUTPUT, 1);
THe above logic is for character by character which is a performance burden? Please let me know if there is any other work around for this

Hi,
Thanks for Replying. I have refered http://blog.oraclecontractors.com/?p=69 and then i added that piece of code. Basically, i'm trying to generate a report using XML publisher. To generate the XML data i'm writing a pl/sql package with SQl/XML functions. DBMS_XMLGEN would help me convert the XML Data as is. When the concurrent program runs this XML data will merge with RTF layout and generate required report. I'm able to generate the Report for data less then 32767 bytes. More than the limit i need to pass chunks of XML data to read as output. That's the reason i'm using fnd_file.output. But it reads only 32767 size at a time.
WHen i use the given logic, it works perfectly fine, but it loops for each character, for example if you have 30,000 characters it loops the same, which is peformance burden.
So i tried to write the logic of chunks but still i get the error that XML tag is not found or missing. I'm hoping this is very common issue, but after all my trails, i didn't find the right solution.
the other logic i tried was :
v_new_xml_data varchar2(32767)
v_iterations := CEIL(v_clob_len/v_chunk_length); -- v_chunk_length is 32767 and v_clob_length is length of the XML data stored inthe clob variable
For i in 0..v_iterations
LOOP
FND_FILE.put_line (fnd_file.log,'the loops v_pos :'||i||' and v_clob_length :'||v_clob_len);
v_new_xml_data := DBMS_LOB.SUBSTR ( V_XML_DATA,v_chunk_length,(i*v_chunk_length)+1);
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,v_new_xml_data); -- read the output for every 32767 chunks
FND_FILE.PUT_LINE(FND_FILE.LOG, 'Chunk length is :'||((i*v_chunk_length)+1));
END LOOP;
FND_FILE.put_line (fnd_file.log,'out of loop');
FND_FILE.put_line (fnd_file.log,'length of new xml is '||v_clob_len);
Please, let me know if you need Further clarifications on the same.

Update XML data stored in CLOB Column

Hi All,
i am new to Oracle and new to SQL
i am trying to update XML data stored in CLOB cloumn,data is stored with the follwoing format
<attrs><attr name="name"><string>Schade</string></attr></attrs>
i am using the following query for updating the value
UPDATE PRODUCT p SET ATTRIBUTES_nl_nl=UPDATEXML(XMLTYPE.createXML(ATTRIBUTES_nl_nl),'/attrs/attr[@name="name"]/string/text()','Schade').getClobVal() WHERE p.sku='000000000000040576_200911-5010057'
this query is working fine but it changing the data to the following format
<attrs><attr name="name">Schade</attr></attrs>
some how it is ommiting the <string> tag from it, i am unable to figure it out whats the reason.
any help in this regard will b e much appriciated
Thanks in Advance
-Umesh

Hi,
You should have created your own thread for this, and included database version.
This works for me on 11.2.0.2 and 10.2.0.5 :
SQL> create table t_org ( xml_clob clob );
Table created
SQL>
SQL> insert into t_org
2 values(
3 '<Message>
4 <Entity>
5 <ASSIGNMENT>
6 <OAVendorLocation> </OAVendorLocation>
7 <Vendorid>1</Vendorid>
8 </ASSIGNMENT>
9 </Entity>
10 </Message>'
11 );
1 row inserted
SQL> commit;
Commit complete
SQL> select '*' ||
2         extractvalue(xmltype(xml_clob),'/Message/Entity/ASSIGNMENT/OAVendorLocation')
3         || '*' as result
4 from t_org;
RESULT
SQL> update t_org set xml_clob =
2 updatexml(xmltype(xml_clob),
3 '/Message/Entity/ASSIGNMENT/OAVendorLocation/text()','LONDON').getClobVal()
4 ;
1 row updated
SQL> select '*' ||
2         extractvalue(xmltype(xml_clob),'/Message/Entity/ASSIGNMENT/OAVendorLocation')
3         || '*' as result
4 from t_org;
RESULT
*LONDON*
Does the OAVendorLocation really have a whitespace value?
If not then it's expected behaviour, you're trying to update a text() node that doesn't exist. In this case, the solution is to use appendChildXML to create the text() node, or update the whole element.
Is it your real document? Do you actually have some namespaces?

Parse a xml file from clob column.

Dear,
i have been suffreing a problem about xml.
i have a table with two columns, one is bfile data type other is clob data type. A xml data is stored into both cloumns
as clob and bfile. My xml data format is correct.
when i took xml data from bfile column, then dbms_xmlparser.parseClob successfully parse my xml data.
Code below:
=======================================
dbms_lob.createtemporary(l_clob, cache=>FALSE);
dbms_lob.loadFromFile(dest_lob => l_clob,
src_lob => l_bfile,
amount => dbms_lob.getLength(l_bfile));
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, l_clob); ========================================
But when i took xml data form clob clumn directly, then dbms_xmlparser.parseClob parse failed and go to exception.
Code below:
====================================================================
dbms_lob.createtemporary(l_clob, cache=>FALSE);
select xml_cfile,xml_bfile
into l_clob ,l_bfile
from xml_load_in
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, l_clob); --failed parse
====================================================================
declare
l_bfile BFILE;
l_clob CLOB;
l_parser dbms_xmlparser.Parser;
l_doc dbms_xmldom.DOMDocument;
begin
dbms_lob.createtemporary(l_clob, cache=>FALSE);
select xml_cfile,xml_bfile
into l_clob ,l_bfile
from xml_load_in
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, l_clob);
l_doc := dbms_xmlparser.getDocument(l_parser);
dbms_lob.freetemporary(l_clob);
dbms_xmlparser.freeParser(l_parser);
exception
dbms_lob.freetemporary(l_clob);
dbms_xmlparser.freeParser(l_parser);
dbms_xmldom.freeDocument(l_doc);
End;
Example:
======--File_name := Outward.xml;
CREATE OR REPLACE DIRECTORY
MY_INWARD AS
'D:\PBM\Inward\';
CREATE TABLE XML_LOAD_IN
( XML_CFILE CLOB,
XML_BFILE BFILE
INSERT INTO XML_LOAD_IN ( XML_CFILE, XML_BFILE )
VALUES (
'<?xml version="1.0" encoding="UTF-8"?>
<BACPSInterface>
<OCE>
<EHR>
<StandardLevel>03</StandardLevel>
<TestFiledIndicator>T</TestFiledIndicator>
<ImmediateDestRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ImmediateDestRoutingNumber>
<ImmediateOriginRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ImmediateOriginRoutingNumber>
<FileCreationDate>20090714</FileCreationDate>
<FileCreationTime>1047</FileCreationTime>
<ResendIndicator>N</ResendIndicator>
<ECESettlementDate>20090714</ECESettlementDate>
<ECESessionTime>1047</ECESessionTime>
<ECESettlementTime>1047</ECESettlementTime>
<ECEtype>01</ECEtype>
<CountryCode>BD</CountryCode>
</EHR>
<Collection>
<CHR>
<CashLetterBusinessDate>20090714</CashLetterBusinessDate>
<CashLetterCreationDate>20090714</CashLetterCreationDate>
<CashLetterCreationTime>1047</CashLetterCreationTime>
<CashLetterRecordTypeInd>I</CashLetterRecordTypeInd>
<CashLetterDocTypeIndicator>G</CashLetterDocTypeIndicator>
<CashLetterID>1</CashLetterID>
<OriginatorContactName>Bank Asia</OriginatorContactName>
<OriginatorContactPhoneNumber>XXX</OriginatorContactPhoneNumber>
</CHR>
<ForwardBundle>
<BHR>
<CollectionTypeIndicator>I</CollectionTypeIndicator>
<DestRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</DestRoutingNumber>
<ECEInstitutionRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ECEInstitutionRoutingNumber>
<BundleBusinessDate>20090714</BundleBusinessDate>
<BundleCreationDate>20090714</BundleCreationDate>
<BundleID>1</BundleID>
<ReturnLocationRoutingNumber>070127538</ReturnLocationRoutingNumber>
</BHR>
<CDR>
<CDR num="1">
<ECESettlementDate>20090714</ECESettlementDate>
<ECESessionTime>1047</ECESessionTime>
<ECESettlementTime>1047</ECESettlementTime>
<ECEItemType>N</ECEItemType>
<IssuingBranchRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</IssuingBranchRoutingNumber>
<AccountNumber>0000334008221</AccountNumber>
<ChequeSequenceNumber>1601735</ChequeSequenceNumber>
<ItemAmount>500</ItemAmount>
<ECEInstitutionItemSequencNum>0701275380000001</ECEInstitutionItemSequencNum>
<DocumentationTypeIndicator>I</DocumentationTypeIndicator>
<ReturnAcceptanceIndicator>6</ReturnAcceptanceIndicator>
<MICRValidIndicator>1</MICRValidIndicator>
<BOFDIndicator>Y</BOFDIndicator>
<ChequeDetailRecAddendumCount>0</ChequeDetailRecAddendumCount>
<CorrectionIndicator>0</CorrectionIndicator>
<RepresentmentIndicator>0</RepresentmentIndicator>
<ArchiveTypeIndicator>F</ArchiveTypeIndicator>
</CDR>
<CDR num="2">
<ECESettlementDate>20090714</ECESettlementDate>
<ECESessionTime>1047</ECESessionTime>
<ECESettlementTime>1047</ECESettlementTime>
<ECEItemType>N</ECEItemType>
<IssuingBranchRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</IssuingBranchRoutingNumber>
<AccountNumber>0000345682256</AccountNumber>
<ChequeSequenceNumber>1234567</ChequeSequenceNumber>
<ItemAmount>1000</ItemAmount>
<ECEInstitutionItemSequencNum>0701275380000002</ECEInstitutionItemSequencNum>
<DocumentationTypeIndicator>I</DocumentationTypeIndicator>
<ReturnAcceptanceIndicator>6</ReturnAcceptanceIndicator>
<MICRValidIndicator>1</MICRValidIndicator>
<BOFDIndicator>Y</BOFDIndicator>
<ChequeDetailRecAddendumCount>0</ChequeDetailRecAddendumCount>
<CorrectionIndicator>0</CorrectionIndicator>
<RepresentmentIndicator>0</RepresentmentIndicator>
<ArchiveTypeIndicator>F</ArchiveTypeIndicator>
</CDR>
</CDR>
<CDA>
<CDA num="1">
<AddendumRecordNumber>1</AddendumRecordNumber>
<BOFDRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>75</DistrictCode>
<BranchCode>12</BranchCode>
<CheckDigit>8</CheckDigit>
</BOFDRoutingNumber>
<BOFDBusinessEndorsementDate>20090714</BOFDBusinessEndorsementDate>
<BOFDDepositAccountNumber>0000334008221</BOFDDepositAccountNumber>
<BOFDDepositBranch>753</BOFDDepositBranch>
<PayeeName>XXX</PayeeName>
<TruncationIndicator>Y</TruncationIndicator>
<BOFDConversionIndicator>2</BOFDConversionIndicator>
<BOFDCorrectionIndicator>0</BOFDCorrectionIndicator>
</CDA>
<CDA num="2">
<AddendumRecordNumber>1</AddendumRecordNumber>
<BOFDRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>75</DistrictCode>
<BranchCode>12</BranchCode>
<CheckDigit>8</CheckDigit>
</BOFDRoutingNumber>
<BOFDBusinessEndorsementDate>20090714</BOFDBusinessEndorsementDate>
<BOFDDepositAccountNumber>0000345682256</BOFDDepositAccountNumber>
<BOFDDepositBranch>753</BOFDDepositBranch>
<PayeeName>XXX</PayeeName>
<TruncationIndicator>Y</TruncationIndicator>
<BOFDConversionIndicator>2</BOFDConversionIndicator>
<BOFDCorrectionIndicator>0</BOFDCorrectionIndicator>
</CDA>
</CDA>
<CDC>
<CDC num="1">
<AddendumCRecordNumber>1</AddendumCRecordNumber>
<EndorsingBankRountingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</EndorsingBankRountingNumber>
<EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
<EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
<EndorsingBankItemSequenceNum>0701275380000001</EndorsingBankItemSequenceNum>
<TruncationIndicator>Y</TruncationIndicator>
<EndorsingBankConversionInd>2</EndorsingBankConversionInd>
<EndorsingBankCorrectionInd>0</EndorsingBankCorrectionInd>
</CDC>
<CDC num="2">
<AddendumCRecordNumber>1</AddendumCRecordNumber>
<EndorsingBankRountingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</EndorsingBankRountingNumber>
<EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
<EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
<EndorsingBankItemSequenceNum>0701275380000002</EndorsingBankItemSequenceNum>
<TruncationIndicator>Y</TruncationIndicator>
<EndorsingBankConversionInd>2</EndorsingBankConversionInd>
<EndorsingBankCorrectionInd>0</EndorsingBankCorrectionInd>
</CDC>
</CDC>
<IVD>
<IVD num="1">
<ImageIndicator>1</ImageIndicator>
<ImageCreatorRountingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ImageCreatorRountingNumber>
<ImageCreatorDate>20090714</ImageCreatorDate>
<ImageViewFormatIndicator>0</ImageViewFormatIndicator>
<ImageViewCompressionAlg>0</ImageViewCompressionAlg>
<ViewSideIndicator>0</ViewSideIndicator>
<ViewDescriptor>0</ViewDescriptor>
<DigitalSignatureIndicator>1</DigitalSignatureIndicator>
<DigitalSignatureMethod>0</DigitalSignatureMethod>
<SecurityKeySize>12235</SecurityKeySize>
<ImageRecreateIndicator>0</ImageRecreateIndicator>
</IVD>
<IVD num="2">
<ImageIndicator>1</ImageIndicator>
<ImageCreatorRountingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ImageCreatorRountingNumber>
<ImageCreatorDate>20090714</ImageCreatorDate>
<ImageViewFormatIndicator>0</ImageViewFormatIndicator>
<ImageViewCompressionAlg>0</ImageViewCompressionAlg>
<ViewSideIndicator>0</ViewSideIndicator>
<ViewDescriptor>0</ViewDescriptor>
<DigitalSignatureIndicator>1</DigitalSignatureIndicator>
<DigitalSignatureMethod>0</DigitalSignatureMethod>
<SecurityKeySize>12235</SecurityKeySize>
<ImageRecreateIndicator>0</ImageRecreateIndicator>
</IVD>
</IVD>
<IVT>
<IVT num="1">
<ECEInstitutionRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ECEInstitutionRoutingNumber>
<BundleBusinessDate>20090714</BundleBusinessDate>
<CycleNumber>0</CycleNumber>
<ECEInstitutionItemSeqNumber>0701275380000001</ECEInstitutionItemSeqNumber>
<ClippingOrigin>
<Origin>0</Origin>
<CoordinateH1>0000</CoordinateH1>
<CoordinateH2>0000</CoordinateH2>
<CoordinateV1>0000</CoordinateV1>
<CoordinateV2>0000</CoordinateV2>
</ClippingOrigin>
<LengthofImageReferenceKey>0</LengthofImageReferenceKey>
<LengthofDigitalSignature>0</LengthofDigitalSignature>
<LengthofImageData>1</LengthofImageData>
<OffsetToImageData>01001000</OffsetToImageData>
</IVT>
<IVT num="2">
<ECEInstitutionRoutingNumber>
<BankCode>070</BankCode>
<DistrictCode>12</DistrictCode>
<BranchCode>75</BranchCode>
<CheckDigit>8</CheckDigit>
</ECEInstitutionRoutingNumber>
<BundleBusinessDate>20090714</BundleBusinessDate>
<CycleNumber>0</CycleNumber>
<ECEInstitutionItemSeqNumber>0701275380000002</ECEInstitutionItemSeqNumber>
<ClippingOrigin>
<Origin>0</Origin>
<CoordinateH1>0000</CoordinateH1>
<CoordinateH2>0000</CoordinateH2>
<CoordinateV1>0000</CoordinateV1>
<CoordinateV2>0000</CoordinateV2>
</ClippingOrigin>
<LengthofImageReferenceKey>0</LengthofImageReferenceKey>
<LengthofDigitalSignature>0</LengthofDigitalSignature>
<LengthofImageData>1</LengthofImageData>
<OffsetToImageData>01001000</OffsetToImageData>
</IVT>
</IVT>
<IVA>
<IVA num="1">
<GlobalImageQuality>0</GlobalImageQuality>
<GlobalImageUsability>1</GlobalImageUsability>
<ImagingBankSpecificTest>1</ImagingBankSpecificTest>
</IVA>
<IVA num="2">
<GlobalImageQuality>0</GlobalImageQuality>
<GlobalImageUsability>1</GlobalImageUsability>
<ImagingBankSpecificTest>1</ImagingBankSpecificTest>
</IVA>
</IVA>
<BCR>
<ItemsWithinBundleCount>2</ItemsWithinBundleCount>
<BundleTotalAmount>1500</BundleTotalAmount>
<MICRValidTotalAmount>1500</MICRValidTotalAmount>
</BCR>
</ForwardBundle>
<CCR>
<BundleCount>1</BundleCount>
<ItemWithinCashLetterCount>2</ItemWithinCashLetterCount>
<CashLetterTotalAmount>1500</CashLetterTotalAmount>
<ImagesWithinCashLetterCount>2</ImagesWithinCashLetterCount>
<ECEInstitutionName>Bank Asia</ECEInstitutionName>
<SettlementDate>20090714</SettlementDate>
</CCR>
</Collection>
<ECR>
<CashLetterCount>1</CashLetterCount>
<TotalRecordCount>2</TotalRecordCount>
<TotalItemCount>2</TotalItemCount>
<FileTotalAmount>1500</FileTotalAmount>
<ImmediateOriginContactName>Bank Asia</ImmediateOriginContactName>
<ImmediateOriginContactNumber>XXX</ImmediateOriginContactNumber>
</ECR>
</OCE>
</BACPSInterface>'
, BFILENAME('MY_INWARD','Outward.xml'));
COMMIT;

What version of Oracle (4 digits) and what is the error?
This runs without error on 10.2.0.4 (though you can go directly from a CLOB to a DOMDocument via dbms_xmldom)
-- Created on 9/14/2009 by JH20567
declare
-- Local variables here
l_clob   CLOB;
l_parser dbms_xmlparser.Parser;
l_doc    dbms_xmldom.DOMDocument;
begin
-- Test statements here
   l_clob := '<?xml version="1.0" encoding="UTF-8"?>
<BACPSInterface>
   <OCE>
      <EHR>
         <StandardLevel>03</StandardLevel>
         <TestFiledIndicator>T</TestFiledIndicator>
         <ImmediateDestRoutingNumber>
            <BankCode>070</BankCode>
            <DistrictCode>12</DistrictCode>
            <BranchCode>75</BranchCode>
            <CheckDigit>8</CheckDigit>
         </ImmediateDestRoutingNumber>
         <ImmediateOriginRoutingNumber>
            <BankCode>070</BankCode>
            <DistrictCode>12</DistrictCode>
            <BranchCode>75</BranchCode>
            <CheckDigit>8</CheckDigit>
         </ImmediateOriginRoutingNumber>
         <FileCreationDate>20090714</FileCreationDate>
         <FileCreationTime>1047</FileCreationTime>
         <ResendIndicator>N</ResendIndicator>
         <ECESettlementDate>20090714</ECESettlementDate>
         <ECESessionTime>1047</ECESessionTime>
         <ECESettlementTime>1047</ECESettlementTime>
         <ECEtype>01</ECEtype>
         <CountryCode>BD</CountryCode>
      </EHR>
      <Collection>
         <CHR>
            <CashLetterBusinessDate>20090714</CashLetterBusinessDate>
            <CashLetterCreationDate>20090714</CashLetterCreationDate>
            <CashLetterCreationTime>1047</CashLetterCreationTime>
            <CashLetterRecordTypeInd>I</CashLetterRecordTypeInd>
            <CashLetterDocTypeIndicator>G</CashLetterDocTypeIndicator>
            <CashLetterID>1</CashLetterID>
            <OriginatorContactName>Bank Asia</OriginatorContactName>
            <OriginatorContactPhoneNumber>XXX</OriginatorContactPhoneNumber>
         </CHR>
         <ForwardBundle>
            <BHR>
               <CollectionTypeIndicator>I</CollectionTypeIndicator>
               <DestRoutingNumber>
                  <BankCode>070</BankCode>
                  <DistrictCode>12</DistrictCode>
                  <BranchCode>75</BranchCode>
                  <CheckDigit>8</CheckDigit>
               </DestRoutingNumber>
               <ECEInstitutionRoutingNumber>
                  <BankCode>070</BankCode>
                  <DistrictCode>12</DistrictCode>
                  <BranchCode>75</BranchCode>
                  <CheckDigit>8</CheckDigit>
               </ECEInstitutionRoutingNumber>
               <BundleBusinessDate>20090714</BundleBusinessDate>
               <BundleCreationDate>20090714</BundleCreationDate>
               <BundleID>1</BundleID>
               <ReturnLocationRoutingNumber>070127538</ReturnLocationRoutingNumber>
            </BHR>
            <CDR>
               <CDR num="1">
                  <ECESettlementDate>20090714</ECESettlementDate>
                  <ECESessionTime>1047</ECESessionTime>
                  <ECESettlementTime>1047</ECESettlementTime>
                  <ECEItemType>N</ECEItemType>
                  <IssuingBranchRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </IssuingBranchRoutingNumber>
                  <AccountNumber>0000334008221</AccountNumber>
                  <ChequeSequenceNumber>1601735</ChequeSequenceNumber>
                  <ItemAmount>500</ItemAmount>
                  <ECEInstitutionItemSequencNum>0701275380000001</ECEInstitutionItemSequencNum>
                  <DocumentationTypeIndicator>I</DocumentationTypeIndicator>
                  <ReturnAcceptanceIndicator>6</ReturnAcceptanceIndicator>
                  <MICRValidIndicator>1</MICRValidIndicator>
                  <BOFDIndicator>Y</BOFDIndicator>
                  <ChequeDetailRecAddendumCount>0</ChequeDetailRecAddendumCount>
                  <CorrectionIndicator>0</CorrectionIndicator>
                  <RepresentmentIndicator>0</RepresentmentIndicator>
                  <ArchiveTypeIndicator>F</ArchiveTypeIndicator>
               </CDR>
               <CDR num="2">
                  <ECESettlementDate>20090714</ECESettlementDate>
                  <ECESessionTime>1047</ECESessionTime>
                  <ECESettlementTime>1047</ECESettlementTime>
                  <ECEItemType>N</ECEItemType>
                  <IssuingBranchRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </IssuingBranchRoutingNumber>
                  <AccountNumber>0000345682256</AccountNumber>
                  <ChequeSequenceNumber>1234567</ChequeSequenceNumber>
                  <ItemAmount>1000</ItemAmount>
                  <ECEInstitutionItemSequencNum>0701275380000002</ECEInstitutionItemSequencNum>
                  <DocumentationTypeIndicator>I</DocumentationTypeIndicator>
                  <ReturnAcceptanceIndicator>6</ReturnAcceptanceIndicator>
                  <MICRValidIndicator>1</MICRValidIndicator>
                  <BOFDIndicator>Y</BOFDIndicator>
                  <ChequeDetailRecAddendumCount>0</ChequeDetailRecAddendumCount>
                  <CorrectionIndicator>0</CorrectionIndicator>
                  <RepresentmentIndicator>0</RepresentmentIndicator>
                  <ArchiveTypeIndicator>F</ArchiveTypeIndicator>
               </CDR>
            </CDR>
            <CDA>
               <CDA num="1">
                  <AddendumRecordNumber>1</AddendumRecordNumber>
                  <BOFDRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>75</DistrictCode>
                     <BranchCode>12</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </BOFDRoutingNumber>
                  <BOFDBusinessEndorsementDate>20090714</BOFDBusinessEndorsementDate>
                  <BOFDDepositAccountNumber>0000334008221</BOFDDepositAccountNumber>
                  <BOFDDepositBranch>753</BOFDDepositBranch>
                  <PayeeName>XXX</PayeeName>
                  <TruncationIndicator>Y</TruncationIndicator>
                  <BOFDConversionIndicator>2</BOFDConversionIndicator>
                  <BOFDCorrectionIndicator>0</BOFDCorrectionIndicator>
               </CDA>
               <CDA num="2">
                  <AddendumRecordNumber>1</AddendumRecordNumber>
                  <BOFDRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>75</DistrictCode>
                     <BranchCode>12</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </BOFDRoutingNumber>
                  <BOFDBusinessEndorsementDate>20090714</BOFDBusinessEndorsementDate>
                  <BOFDDepositAccountNumber>0000345682256</BOFDDepositAccountNumber>
                  <BOFDDepositBranch>753</BOFDDepositBranch>
                  <PayeeName>XXX</PayeeName>
                  <TruncationIndicator>Y</TruncationIndicator>
                  <BOFDConversionIndicator>2</BOFDConversionIndicator>
                  <BOFDCorrectionIndicator>0</BOFDCorrectionIndicator>
               </CDA>
            </CDA>
            <CDC>
               <CDC num="1">
                  <AddendumCRecordNumber>1</AddendumCRecordNumber>
                  <EndorsingBankRountingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </EndorsingBankRountingNumber>
                  <EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
                  <EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
                  <EndorsingBankItemSequenceNum>0701275380000001</EndorsingBankItemSequenceNum>
                  <TruncationIndicator>Y</TruncationIndicator>
                  <EndorsingBankConversionInd>2</EndorsingBankConversionInd>
                  <EndorsingBankCorrectionInd>0</EndorsingBankCorrectionInd>
               </CDC>
               <CDC num="2">
                  <AddendumCRecordNumber>1</AddendumCRecordNumber>
                  <EndorsingBankRountingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </EndorsingBankRountingNumber>
                  <EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
                  <EndorsingBankEndorsementDate>20090714</EndorsingBankEndorsementDate>
                  <EndorsingBankItemSequenceNum>0701275380000002</EndorsingBankItemSequenceNum>
                  <TruncationIndicator>Y</TruncationIndicator>
                  <EndorsingBankConversionInd>2</EndorsingBankConversionInd>
                  <EndorsingBankCorrectionInd>0</EndorsingBankCorrectionInd>
               </CDC>
            </CDC>
            <IVD>
               <IVD num="1">
                  <ImageIndicator>1</ImageIndicator>
                  <ImageCreatorRountingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </ImageCreatorRountingNumber>
                  <ImageCreatorDate>20090714</ImageCreatorDate>
                  <ImageViewFormatIndicator>0</ImageViewFormatIndicator>
                  <ImageViewCompressionAlg>0</ImageViewCompressionAlg>
                  <ViewSideIndicator>0</ViewSideIndicator>
                  <ViewDescriptor>0</ViewDescriptor>
                  <DigitalSignatureIndicator>1</DigitalSignatureIndicator>
                  <DigitalSignatureMethod>0</DigitalSignatureMethod>
                  <SecurityKeySize>12235</SecurityKeySize>
                  <ImageRecreateIndicator>0</ImageRecreateIndicator>
               </IVD>
               <IVD num="2">
                  <ImageIndicator>1</ImageIndicator>
                  <ImageCreatorRountingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </ImageCreatorRountingNumber>
                  <ImageCreatorDate>20090714</ImageCreatorDate>
                  <ImageViewFormatIndicator>0</ImageViewFormatIndicator>
                  <ImageViewCompressionAlg>0</ImageViewCompressionAlg>
                  <ViewSideIndicator>0</ViewSideIndicator>
                  <ViewDescriptor>0</ViewDescriptor>
                  <DigitalSignatureIndicator>1</DigitalSignatureIndicator>
                  <DigitalSignatureMethod>0</DigitalSignatureMethod>
                  <SecurityKeySize>12235</SecurityKeySize>
                  <ImageRecreateIndicator>0</ImageRecreateIndicator>
               </IVD>
            </IVD>
            <IVT>
               <IVT num="1">
                  <ECEInstitutionRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </ECEInstitutionRoutingNumber>
                  <BundleBusinessDate>20090714</BundleBusinessDate>
                  <CycleNumber>0</CycleNumber>
                  <ECEInstitutionItemSeqNumber>0701275380000001</ECEInstitutionItemSeqNumber>
                  <ClippingOrigin>
                     <Origin>0</Origin>
                     <CoordinateH1>0000</CoordinateH1>
                     <CoordinateH2>0000</CoordinateH2>
                     <CoordinateV1>0000</CoordinateV1>
                     <CoordinateV2>0000</CoordinateV2>
                  </ClippingOrigin>
                  <LengthofImageReferenceKey>0</LengthofImageReferenceKey>
                  <LengthofDigitalSignature>0</LengthofDigitalSignature>
                  <LengthofImageData>1</LengthofImageData>
                  <OffsetToImageData>01001000</OffsetToImageData>
               </IVT>
               <IVT num="2">
                  <ECEInstitutionRoutingNumber>
                     <BankCode>070</BankCode>
                     <DistrictCode>12</DistrictCode>
                     <BranchCode>75</BranchCode>
                     <CheckDigit>8</CheckDigit>
                  </ECEInstitutionRoutingNumber>
                  <BundleBusinessDate>20090714</BundleBusinessDate>
                  <CycleNumber>0</CycleNumber>
                  <ECEInstitutionItemSeqNumber>0701275380000002</ECEInstitutionItemSeqNumber>
                  <ClippingOrigin>
                     <Origin>0</Origin>
                     <CoordinateH1>0000</CoordinateH1>
                     <CoordinateH2>0000</CoordinateH2>
                     <CoordinateV1>0000</CoordinateV1>
                     <CoordinateV2>0000</CoordinateV2>
                  </ClippingOrigin>
                  <LengthofImageReferenceKey>0</LengthofImageReferenceKey>
                  <LengthofDigitalSignature>0</LengthofDigitalSignature>
                  <LengthofImageData>1</LengthofImageData>
                  <OffsetToImageData>01001000</OffsetToImageData>
               </IVT>
            </IVT>
            <IVA>
               <IVA num="1">
                  <GlobalImageQuality>0</GlobalImageQuality>
                  <GlobalImageUsability>1</GlobalImageUsability>
                  <ImagingBankSpecificTest>1</ImagingBankSpecificTest>
               </IVA>
               <IVA num="2">
                  <GlobalImageQuality>0</GlobalImageQuality>
                  <GlobalImageUsability>1</GlobalImageUsability>
                  <ImagingBankSpecificTest>1</ImagingBankSpecificTest>
               </IVA>
            </IVA>
            <BCR>
               <ItemsWithinBundleCount>2</ItemsWithinBundleCount>
               <BundleTotalAmount>1500</BundleTotalAmount>
               <MICRValidTotalAmount>1500</MICRValidTotalAmount>
            </BCR>
         </ForwardBundle>
         <CCR>
            <BundleCount>1</BundleCount>
            <ItemWithinCashLetterCount>2</ItemWithinCashLetterCount>
            <CashLetterTotalAmount>1500</CashLetterTotalAmount>
            <ImagesWithinCashLetterCount>2</ImagesWithinCashLetterCount>
            <ECEInstitutionName>Bank Asia</ECEInstitutionName>
            <SettlementDate>20090714</SettlementDate>
         </CCR>
      </Collection>
      <ECR>
         <CashLetterCount>1</CashLetterCount>
         <TotalRecordCount>2</TotalRecordCount>
         <TotalItemCount>2</TotalItemCount>
         <FileTotalAmount>1500</FileTotalAmount>
               <ImmediateOriginContactName>Bank Asia</ImmediateOriginContactName>
               <ImmediateOriginContactNumber>XXX</ImmediateOriginContactNumber>
          </ECR>
     </OCE>
</BACPSInterface>';
   l_parser := dbms_xmlparser.newParser;
   dbms_xmlparser.parseClob(l_parser, l_clob);
   l_doc := dbms_xmlparser.getDocument(l_parser);
   dbms_lob.freetemporary(l_clob);
   dbms_xmlparser.freeParser(l_parser);
   dbms_xmldom.freeDocument(l_doc);
end;

Parsing xml in clob field remove non utf-8 characters

hi all,
i have an issue where a stored procedure runs during a nightly process and parses xml contained in a clob field. There are some records that contain non-utf8(they paste characters from word)characters and therefore the parse fails when using performing an xquery select against the clob field as xmltype. I was wondering if anyone knew of a handy way to handle such a situation? I have looked around a bit and not found anything that seemed tailored to my situation, and I would like something a bit more generic than doing a replace on individual characters that i have found causing issues...thx in advance! -- jp

Hi,
Like BluShadow I'm curious to see a test case...
Depending on the way it's been created, the encoding declared in the XML prolog doesn't necessarily reflects the actual encoding of the content.
What's your database character set, and version?
Please also post the error message you get (LPX-00200 probably?).

BPEL process to Insert XML into DB using pl/sql stored proc

Hi,
We have created a BPEL process in which we are taking input request and store it into Oracle Database using PL/SQL proc.
We have been unsuccessful in doing so because the data stored in table has root element missing.
Has any body done this (insert xml into DB using pl/sql stored proc) successfully ?
We can so this successfully if we do not use stored procedure and store data directly in table.
Regards

I have done this, stored it as a CLOB.
Also I received the payload as an opaque schema, so I had to convert the message from binary into string.
This way the root element doesn't get removed.
cheers
James

Write / store xml data in Xe and retrieve stored data using pl/sql

Hi to all,
i'm searching a tutorial on:
A - how to write / store xml data in Xe and retrieve stored data using pl/sql
I don't want to use other technologies, because i use htmldb and my best practice is with pl/sql.
I was reading an ebook (quite old maybe) however it's about oracle 9 and it's talking about xmltype:
1 - I don't understand if this is a user type (clob/varchar) or it's integrated in Oracle 9 however i will read it (it's chapter 3 titled Using Oracle xmldb).
Please dont'reply here: i would be glad if someone can suggest me a good tutorial / pdf to achieve task A in Oracle XE.
Thanx

Thank you very much Carl,
However my fault is that i've not tried to create the table via sql plus.
Infact i was wrong thinking that oracle sql developer allows me to create an xmltype column via the create table tool.
however with a ddl script like the following the table was created successfully.
create table example1
keyvalue varchar2(10) primary key,
xmlcolumn xmltype
Thank you very much for your link.
Message was edited by:
Marcello Nocito

Parse XML in PL/SQL

I need help with parsing xml data in PL/SQL. I was able to read the attribute name & values but not able to read the element text.Any help is greatly appreciated.Following is the anonymous block and the desired output -
Declare
nl xmldom.DOMNodeList;
len1 number;
len2 number;
n xmldom.DOMNode;
e xmldom.DOMElement;
nnm xmldom.DOMNamedNodeMap;
attrname varchar2(100);
attrval varchar2(100);
doc xmldom.DOMDocument;
p xmlparser.Parser;
in_xml clob;
begin
-- get all elements
p := xmlparser.newParser;
in_xml := '<?xml version="1.0" encoding="utf-8"?>
<Issue>
<T_ISSUE_TITLE ID = "1">Test Issue</T_ISSUE_TITLE>
<T_ISSUE_DESC ID = "2">Update Test Issue</T_ISSUE_DESC>
<STATUS ID = "3">2</STATUS>
<ISSUE_SD ID = "4">07/09/10</ISSUE_SD>
<ISSUE_ED ID = "5">09/09/10</ISSUE_ED>
<CREATE_DT ID = "6">07/09/10</CREATE_DT>
<CREATE_USER_ID ID = "7">John</CREATE_USER_ID>
<LST_UPD_USER_ID ID = "8">John</LST_UPD_USER_ID>
</Issue>';
xmlparser.parseClob(p,in_xml);
doc :=xmlparser.getDocument(p);
nl := xmldom.getElementsByTagName(doc, '*');
len1 := xmldom.getLength(nl);
-- loop through elements
for j in 0..len1-1 loop
n := xmldom.item(nl, j);
e := xmldom.makeElement(n);
dbms_output.put_line(xmldom.getTagName(e) || ':');
-- get all attributes of element
nnm := xmldom.getAttributes(n);
len2 := xmldom.getLength(nnm);
if (xmldom.isNull(nnm) = FALSE) then
len2 := xmldom.getLength(nnm);
-- loop through attributes
for i in 0..len2-1 loop
n := xmldom.item(nnm, i);
--dbms_output.put_line(n);
attrname := xmldom.getNodeName(n);
attrval := xmldom.getNodeValue(n);
dbms_output.put_line(' ' || attrname || ' = ' || attrval);
end loop;
end if;
end loop;
end;
/** Output
Issue:
T_ISSUE_TITLE:
ID = 1, Test Issue
T_ISSUE_DESC:
ID = 2, Update Test Issue
STATUS:
ID = 3, 2
ISSUE_SD:
ID = 4, 07/09/10
ISSUE_ED:
ID = 5, 09/09/10
CREATE_DT:
ID = 6, 07/09/10
CREATE_USER_ID:
ID = 7, John
LST_UPD_USER_ID:
ID = 8, John
Thank You.

Use dbms_xslprocessor.valueOf and dbms_xmldom.getnodevalue to get the value of node
eg: l_doc is paresed XML doc with nodes as partdetails and part
declare
l_n dbms_xmldom.DOMNode;
l_nl dbms_xmldom.DOMNodeList;
l_partname varchar2(100);
begin
---parsing code--
l_nl := dbms_xslprocessor.selectNodes(dbms_xmldom.makeNode(l_doc),'/PartDetails/Part');
FOR cur_emp IN 0 .. dbms_xmldom.getLength(l_nl) - 1 LOOP
l_n := dbms_xmldom.item(l_nl, cur_emp);
dbms_xslprocessor.valueOf(l_n,'Name/text()',l_partname);
dbms_output.put_line(l_partname);
end loop;
end;Edited by: SBH on Jul 13, 2010 11:06 AM

How to parsing xml data in sql statement??

Hi friends, I have a table which contain column as clob ,stores in xml format, for example my column contain xml data like this
<Employees xmlns="http://TargetNamespace.com/read_emp">
   <C1>106</C1>
   <C2>Harish</C2>
   <C3>1998-05-12</C3>
   <C4>HR</C4>
   <C5>1600</C5>
   <C6>10</C6>
</Employees>
Then how to extract the data in above xml column data using SQL statement...

Duplicate post
How to parsing xml data in sql statement??

Parsing XML stored in CLOB (PL/SQL)

Similar Messages

Maybe you are looking for