Validation with DTD: Bug in Oracle 10g?

Question

Hi
The following example works with Oracle 11g, but not with Oracle 10g.
I have a XML-document (familie.xml) and a DTD-Document (familie.dtd). The XML-document is not valide, because I changed the tag "Vater" into "Dad". Within
the DTD the "Vater"-element is described as follow: <!ELEMENT Familie (Vater, Mutter, Kind) >. If I validate the document, I get in Oracle 11g this exception:
Unexpected Error: ORA-31011: XML-Parsing not succesful
LPX-00104: Warning: Element "Dad" is not declared in the DTD.
Error at line 3 occured.
This Error is right!! But if I try the SAME example in Oracle 10g, I don't get a Exception!!!! But I should become one.
Have anyone tested DTD-Validation in Oracle 10g or is it a bug?
<?xml version='1.0' encoding='ISO-8859-15' ?>
<!-- Dokument beschreibt eine Familie -->
<Familie>
     <Dad>
          <Name>Meier</Name>
<Vorname>David</Vorname>
     </Dad>
     <Mutter>
          <Name>Baumann</Name>
          <Vorname>Charlotte</Vorname>
     </Mutter>
     <Kind>
          <Name>Slota</Name>
          <Vorname>Kaharina</Vorname>
     </Kind>
</Familie>
<!ELEMENT Familie (Vater, Mutter, Kind) >
<!ELEMENT Vater (Name, Vorname)>
<!ELEMENT Mutter (Name, Vorname)>
<!ELEMENT Kind (Name, Vorname) >
<!ELEMENT Name (#PCDATA) >
<!ELEMENT Vorname (#PCDATA) >
set directory TEST_DIR as '....';
DECLARE
v_parser xmlparser.parser;
v_document xmldom.DOMDocument;
v_nodeList xmldom.DOMNodeList;
v_number NUMBER;
v_xmlDatei VARCHAR2(32);
v_dtdDatei varchar2(32);
parserError EXCEPTION;
PRAGMA EXCEPTION_INIT(parserError, -20100);
BEGIN
v_xmlDatei := 'familie.xml';
v_dtdDatei := 'familie.dtd';
v_parser := xmlparser.newParser();
DBMS_XMLPARSER.setBaseDir(v_parser, 'TEST_DIR');
xmlparser.setValidationMode(v_parser, TRUE);
xmlparser.parseDTD(v_parser, v_dtdDatei, 'Familie');
xmlparser.parse(v_parser, v_xmlDatei);
v_document:=xmlparser.getDocument(v_parser);
xmlparser.freeParser(v_parser);
xmldom.freeDocument(v_document);
EXCEPTION
WHEN parserError THEN
xmlparser.freeParser(v_parser);
dbms_output.put_line('Fehler beim Parsen: ' || SQLERRM);
WHEN OTHERS THEN
dbms_output.put_line('Unerwarteter Fehler: ' || ' ' || SQLERRM);
END;
null
Message was edited by:
user638576

Answer 1

Do your sequence and column have the same name? In your code sample, it looks like they do:
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD.NEXTVAL, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
Maybe that has confused the parser.
As Oracle moves forward, you can expect more object-oriented functionality. That could mean that columns could have their own attributes or methods. If so, how is the parser to know whether in this code the value KPIIDD.NEXTVAL refers to the (external) sequence or a column attribute?
As a suggestion, try renaming the sequence.
create sequence KPIIDD_SEQ start with ... ;
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD_SEQ.NEXTVAL, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
HTH,
- Doug