Schema validation problem in oracle 11g

Question

Hi,
I am facing the following problem.
The Issue.xsd contains two elements (element1, element2) described as below. It contains two types
1. simpleType - MyStringType
2. complexType - MyType, an extension of MyStringType
Oracle XML DB can able to validate element2(simpleType), but not element1(complexType).
---------------------Issue.xsd File ------------------
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="ConfigRoot" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="ConfigRoot" elementFormDefault="qualified">
     <xsd:element name="ConfigRoot" xdb:defaultTable="CONFIG_TBL_ISSUE">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="element1" type="MyType"/>
                    <xsd:element name="element2" type="MyStringType"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:simpleType name="MyStringType">
          <xsd:restriction base="xsd:string">
               <xsd:pattern value="\d{2}([\W])\d{2}([\W])\d{2}"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="MyType">
          <xsd:simpleContent>
               <xsd:extension base="MyStringType">
                    <xsd:attribute name="id" type="xsd:integer"/>
               </xsd:extension>
          </xsd:simpleContent>
     </xsd:complexType>
</xsd:schema>
--------------------- XML File -----------------
<?xml version="1.0" encoding="UTF-8"?>
<ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <element1 id="1">19-12-222</element1>
     <element2>19-12-555</element2>
</ConfigRoot>
Though the schema is registered as binary, oracle could not able to validate the element1. The XML gets properly validated in the XML editors.

Answer 1

"Issue.xsd"
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="ConfigRoot" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="ConfigRoot" elementFormDefault="qualified">
<xsd:element name="ConfigRoot" xdb:defaultTable="CONFIG_TBL_ISSUE">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="element1" type="MyType"/>
<xsd:element name="element2" type="MyStringType"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="MyStringType">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{2}(\W)\d{2}(\W)\d{2}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="MyType">
<xsd:simpleContent>
<xsd:extension base="MyStringType">
<xsd:attribute name="id" type="xsd:integer"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
"Issue.xml"
<?xml version="1.0" encoding="UTF-8"?>
<ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<element1 id="1">19-12-222</element1>
<element2>19-12-555</element2>
</ConfigRoot>
[oracle@srv01-18-102 20081010]$ sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Oct 10 14:46:09 2008
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
PL/SQL Release 11.1.0.7.0 - Production
CORE    11.1.0.7.0      Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
SQL> create user otn identified by otn account unlock;
User created.
SQL> -- The Quick and Dirty way regarding granting privileges
SQL> grant dba, xdbadmin  to otn;
Grant succeeded.
SQL> connect otn/otn
Connected.
SQL> create directory "XMLDIR_SCHEMA" as '/home/oracle/OTN/20081010';
Directory created.
SQL> -- Issue.xsd and Issue.xml are created and copied to the directory /home/oracle/OTN/20081010, on which I have read, write access as Linux user "oracle" (the oracle software owner)
SQL> BEGIN
  2  DBMS_XMLSCHEMA.registerSchema(
  3  SCHEMAURL => 'Issue.xsd',
  4  SCHEMADOC => bfilename ('XMLDIR_SCHEMA', 'Issue.xsd'),
  5  GENTYPES => FALSE,
  6  OWNER => USER,
  7  OPTIONS => 3);
  8  end;
  9* /
PL/SQL procedure successfully completed.
SQL> select * from tab;
TNAME                          TABTYPE  CLUSTERID
CONFIG_TBL_ISSUE               TABLE
SQL> set long 100000000
SQL> desc "CONFIG_TBL_ISSUE"
Name                                      Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "Issue.xsd" Element "ConfigRoot") STORAGE BINARY
SQL> set pages 5000
SQL>  select dbms_metadata.get_ddl('TABLE','CONFIG_TBL_ISSUE',user) from dual;
DBMS_METADATA.GET_DDL('TABLE','CONFIG_TBL_ISSUE',USER)
  CREATE TABLE "OTN"."CONFIG_TBL_ISSUE" OF "SYS"."XMLTYPE"
  XMLTYPE STORE AS BASICFILE BINARY XML  (
  TABLESPACE "USERS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10  
  NOCACHE LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS  1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
XMLSCHEMA "Issue.xsd" ELEMENT "ConfigRoot" ID 4768 DISALLOW NONSCHEMA PCTFREE 10
  PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
  TABLESPACE "USERS"
INSERT INTO "CONFIG_TBL_ISSUE"
VALUES
(XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')));
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
  2  VALUES
  3  (XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')))
  4  ;
(XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')))
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "19-12-555" is not valid with respect to the pattern
SQL> -- TESTING EXCEPTIONS
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
  2  VALUES
  3  (XMLTYPE(
  4   '<?xml version="1.0" encoding="UTF-8"?>
  5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  6   <element1 id="1">01-11-11</element1>
  7   <element2>02-11-11</element2>
  8   </ConfigRoot>
  9  '));
1 row created.
SQL> rollback;
Rollback complete.
SQL> -- ELEMENT 1 and 2 ARE WRONG (correct response)
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
  2  VALUES
  3  (XMLTYPE(
  4   '<?xml version="1.0" encoding="UTF-8"?>
  5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  6   <element1 id="1">01-11-111</element1>
  7   <element2>02-11-111</element2>
  8   </ConfigRoot>
  9  '));
(XMLTYPE(
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "02-11-111" is not valid with respect to the pattern
SQL> -- ELEMENT 1 is WRONG (OOPS)
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
  2  VALUES
  3  (XMLTYPE(
  4   '<?xml version="1.0" encoding="UTF-8"?>
  5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  6   <element1 id="1">01-11-111</element1>
  7   <element2>02-11-11</element2>
  8   </ConfigRoot>
  9  '));
1 row created.
SQL> rollback;
Rollback complete.
SQL> -- ELEMENT 2 is WRONG (correct response)
SQL> SQL> INSERT INTO "CONFIG_TBL_ISSUE"
  2  VALUES
  3  (XMLTYPE(
  4   '<?xml version="1.0" encoding="UTF-8"?>
  5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  6   <element1 id="1">01-11-11</element1>
  7   <element2>02-11-111</element2>
  8   </ConfigRoot>
  9  '));
INSERT INTO "CONFIG_TBL_ISSUE"
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "02-11-111" is not valid with respect to the patternIt looks like if, if I interpret the XML schema correctly, that it doesn't comply to the extension "myStringType" of the restriction base "MyType". I am not absolutely sure if this is correct behavior or not, because of the nesting. If it should comply to the extend and therefore also should comply to the restriction pattern then this would mean that you discovered a bug.
If it is a bug or not, I think you should create a service request for this, asking Oracle Support for help.
Grz
Marco