In the Studio of BEA WorkSpace XML schema Validation error

When I validate my XML schemas through the BEA WorkSpace Studio Version: version 1.1: 1090602 identifier the track happens error:

Reference file contains errors (file:/MyPath/MyXMLSchema1.xsd).
For more information, click with the right button on the message and select "show details...". »

See details:
The below errors were detected during the validation of the 'MyXMLSchema1.xsd' file via the file 'MyXMLSchema2.xsd '.
In most cases, these errors can be detected by validating 'MyXMLSchema1.xsd' directly.
However, it is possible that errors occur only when MyXMLSchema1.xsd is posted under MyXMLSchema2.xsd.

CBC-resolve: could not resolve the name 'srv:Services' component 'type definition' a (e)

When I validate my XML schemas through the oepe_11gR1PS4 (Eclipse platform Version: 3.6.2 Build id: M20110210-1200) no errors not found.

My project is a (project ALSB) OSB.

What is happen?

BEA WorkSpace Studio Version: version 1.1: 1090602 identifier use xerces bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org.apache.xerces_2.8.0.v200606131651

oepe_11gR1PS4 (Eclipse platform Version: 3.6.2 Build id: M20110210-1200) use xerces Oracle\Middleware_10.3.5\oepe_11gR1PS4\plugins\org.apache.xerces_2.9.0.v201005080400.jar

If you replace the follow-up files:
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org. Apache.xerces_2.8.0.v200606131651\resolver.jar
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org. Apache.xerces_2.8.0.v200606131651\xercesImpl.jar
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org. Apache.xerces_2.8.0.v200606131651\xml-APIs.jar

for:
Oracle\Middleware_10.3.5\oepe_11gR1PS4\plugins\org. Apache.xerces_2.9.0.v201005080400.jar

BEA WorkSpace Studio Version: version 1.1: 1090602 identifier is validated without errors (the same oepe_11gR1PS4 behavior)

Tags: Fusion Middleware

Similar Questions

To its relevant xml schema xml file validation error
Hi all

I have 3 files to schema files to xml where I generated an XML using PLSQL. I get this error when I try to validate the xml schema file:
' ' * WMWROOT ' UNDECLARED *. Can someone help me with this, I included the main schema file and also the generated XML.

XML schema file:

Itemdownload.xsd:

<? XML version = "1.0" encoding = "utf-8"? >
< xs: Schema id = "Elementtelecharger" targetNamespace = "http://www.manh.com/ILSNET/Interface" elementFormDefault = "qualified".
xmlns = "http://www.manh.com/ILSNET/Interface" xmlns: XS = "http://www.w3.org/2001/XMLSchema" version = "2007" >
< xs: include schemaLocation = "Item.xsd" / > "

< xs: element name = "WMWROOT" nillable = "true" type = "WMWROOT" / >
< name XS: complexType = "WMWROOT" >
< xs: SEQUENCE >
< xs: ELEMENT minOccurs = "0" maxOccurs = "1" name = "WMWDATA" type = "WMWDATA" / >
< / xs: SEQUENCE >
< / xs: complexType >

< xs: element name = "WMWDATA" nillable = "true" type = "WMWDATA" / >
< name XS: complexType = "WMWDATA" >
< xs: SEQUENCE >
< xs: ELEMENT minOccurs = "0" maxOccurs = "1" name = "Items" type = "ItemList" / >
< / xs: SEQUENCE >
< / xs: complexType >

< xs: element name = "Items" nillable = "false" type = "ItemList" / >
< name XS: complexType "ItemList" = >
< xs: SEQUENCE >
< xs: ELEMENT minOccurs = "1" maxOccurs = "unbounded" name = "Item" nillable = "true" type = "Item" / >
< / xs: SEQUENCE >
< / xs: complexType >
< / xs: Schema >

The generated xml file is:

<? XML version = "1.0"? >
< WMWROOT >
< WMWDATA >
elements <>
< item > < Action > save < / Action > < UserDef8 > 10074 < / UserDef8 > < Y Active > < / assets > < AvailableOnWeb > N < / AvailableOnWeb > < company > OR: ResMed Corp < / company > < cost > 285.93 < / cost > < Desc > HP DESKJET PRINTER (EMBLA) < / Desc > < HarmCode > < UserDef8 > 10074 < / UserDef8 > < / HarmCode > < point > R145-794 < / Item > < InventoryTracking > Y < / InventoryTracking > < LongDesc > HP DESKJET PRINTER (EMBLA) < / LongDesc > < LotControlled > Y < / LotControlled > < SerialNumTrackOutbound > 7 < / SerialNumTrackOutbound > < StorageTemplate > < model > each < / model > < / StorageTemplate > < xrefs > < Xref > < XRefItem > < / XRefItem > < / XRef > < / XRefs > < / Item >
< item > < Action > Save < / Action > < UserDef8 > 80862 < / UserDef8 > < Y Active > < / assets > < AvailableOnWeb > N < / AvailableOnWeb > < company > UO: ResMed Corp < / company > < cost > 54.27 < / cost > < Desc > Mirage Micro mask MED & amp; LG-Internet Pkg < / Desc > < HarmCode > < UserDef8 > 80862 < / UserDef8 > < / HarmCode > < point > 16359 < / Item > < InventoryTracking > Y < / InventoryTracking > < LongDesc > Mirage Micro mask MED & amp; LG-Internet Pkg < / LongDesc > < LotControlled > Y < / LotControlled > < SerialNumTrackOutbound > N < / SerialNumTrackOutbound > < StorageTemplate > < model > each < / model > < / StorageTemplate > < xrefs > < Xref > < XRefItem > 619498163597 < / XRefItem > < / XRef > < / XRefs > < / Item >
< / object >
< / WMWDATA >
< / WMWROOT >

I can provide you with 2 other if necessary dependent schemas. Please answer me!
I don't know how this issue applies to the XML DB, but I'll answer anyway.

Your schema resides in the
targetNamespace = "http://www.manh.com/ILSNET/Interface."
namespace, so by default, all definitions can be found in this namespace
The generated XML is in no namespace. That's why you see the error
'WMWROOT' UNDECLARED
Since the schema has no definitions in the same XML namespace uses. You must put your XML file in the same namespace as the schema in order for validation to work, through the
xmlns = "http://www.manh.com/ILSNET/Interface."

How to fix the failed to save binary XML Schema

SQL> begin
  2   DBMS_XMLSCHEMA.registerSchema(
  3     SCHEMAURL  => 'http://www.mediawiki.org/xml/export-0.3/',
  4     SCHEMADOC  => xdbURIType('/public/export-0.3.ORG.bin.xsd').getClob(),
  5     LOCAL      => FALSE,  -- local
  6     GENTYPES   => FALSE,  -- generate object types
  7     GENBEAN    => FALSE,  -- no java beans
  8     GENTABLES  => FALSE,  -- generate object tables
  9     FORCE      => FALSE,          
 10     OPTIONS    => DBMS_XMLSCHEMA.REGISTER_BINARYXML,
 11     OWNER      => USER);
 12  end; 
 13  / 
begin
*
ERROR at line 1:
ORA-31094: incompatible SQL type "XDB$ENUM_T" for attribute or element "space"
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 20
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 31
ORA-06512: at line 2

Schema "/ public/export-0.3.ORG.bin.xsd" is identical to [http://www.mediawiki.org/xml/export-0.3/ | http://www.mediawiki.org/xml/export-0.3/] on the internet.

Your registration does not work for "XML: Space" refers to http://www.w3.org/2001/xml.xsd in the registry, where "XML: Space" is defined as:

  <xs:attribute name="space" default="preserve" oraxdb:propNumber="2203" oraxdb:global="true"
    oraxdb:SQLName="space" oraxdb:SQLType="XDB$ENUM_T" 
    oraxdb:SQLSchema="XDB" oraxdb:memType="259">
    <xs:simpleType>
      <xs:restriction base="xs:NCName">
        <xs:enumeration value="default"/>
        <xs:enumeration value="preserve"/>
      </xs:restriction>
    </xs:simpleType>
  </xs:attribute>

Published by: Marco Gralike, Sep 12, 2008 12:24

Known Bug with xml.xsd import... Fixed in 11.1.0.7.0? Try xml.csx.xsd

XML schema validation

Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production
Hello everyone,
I have a xsd file in a directory of dba and save it in my program. The first time the validation works fine, but by the next call to the programm code below I get the error message:
Error: ORA-31000: resource "is not a document of schema XDB
Any suggestion?
Another Question: I want the program to always take the new Version of the xsd file, thatswhy, it will be recorded every time that the program starts (when existing).
Is there another way to inform the program the most recent version of the xsd file?
Thank you for advice!
```
select count(1) into l_row_count
  from user_xml_schemas
  where schema_url = 'test.xsd';

  if l_row_count > 0 then
    DBMS_XMLSCHEMA.deleteSchema('test.xsd', dbms_xmlSchema.DELETE_CASCADE_FORCE);
   
    DBMS_XMLSCHEMA.REGISTERSCHEMA(
        schemaurl => 'test.xsd',
        schemadoc => BFILENAME ('XSD_FILES','test.xsd')
        , local     => TRUE
        , genTypes  => FALSE
        , genbean   => FALSE
        , genTables => FALSE);
  else
     DBMS_XMLSCHEMA.REGISTERSCHEMA(
        schemaurl => 'test.xsd',
        schemadoc => BFILENAME ('XSD_FILES','test.xsd')
        , local     => TRUE
        , genTypes  => FALSE
        , genbean   => FALSE
        , genTables => FALSE);
  end if;
  -------------------------- ERROR after validation----------------------------------
    if xmlDoc.isSchemaValid() = 1 then
      dbms_output.put_line('Schema is Valid');
    else
      xmlDoc.schemaValidate();
    end if;
```
I'll use this programm in a PLSQL function that gets an XMLTYPE as an input parameter. This is the reason why I'm first instantiate the xmltype

Ok.

In this case, you must:
- cancel the definition of the schema on the XMLType entry (if necessary):
If l_xml.isSchemaBased () = 1 then

l_xml: = l_xml.createNonSchemaBasedXML ();

end if;
- do the things record schema
- then before validation:
l_xml: = l_xml.createSchemaBasedXML ();

(Note that you do not have to enter the url of the schema in the second case, it will be picked up in the attribute xsi)

Hello. I have a problem in the adobe extension manager. Where I have this message when I want the Photoshop module. (Cannot install the extension generator longshadow please make sure that the manifest.) This extension XML is valid and the extenison m

Help

How to be notified of the ftping file schema validation failure in XMLDB
Hi all

Oracle 10.2.0.4

We used RegisterSchema to register for an XSD. And we are ftp'ing the xml files in the database using port 2100 to load in the xmltype table.

How should we deal with the case where the XML file fails validation schema for the FTP "put" of the process, as with an enumeration error? We want to save the error and warn users that the file failed to load due to an error in xml validation.

Is there a log somewhere in Oracle who writes the error, as in the listener.log?
Can we have the FTP process will return the error ORA-31038 that gets triggered when a xml schema validation error occurs?

Thank you very much

Troy
This error is caught during the validation of light since we need to encode the value of the enumeration before we store. Therefore, it happens before any insert triggers fire. The only solution for this is 11.1.x using the repository event model.

InPlace schema evolution error: ORA-31166: error code internal etc...

Hello

I have a table in which I will be storing an XMLTYPE column based on an XML schema. I use the following version of the database:

SQL*Plus: Release 11.2.0.1.0 Production on Thu Aug 23 18:20:12 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Now, when I run my test InPlace Schema Evolution, I get the following error message:

< font color = "red" >

ORA-31166: internal error code to handle ignorable attributes

< / make >

I built a re-producable case of test for the purpose of this post on the forum. For starters, I have a database scheme grants the following privileges:

DIRECTLY GRANTED SYSTEM PRIVS
=============================
CREATE TRIGGER
ALTER SESSION
CREATE TABLE

EXECUTE PRIVS (SYS-OWNED PACKAGES)
=============
EXECUTE ON DBMS_XMLSCHEMA

ROLES GRANTED
=============
CONNECT
DATA_ROLE

DATA_ROLE DDL
=============
create role DATA_ROLE not identified;
grant create database link to DATA_ROLE;
GRANT CREATE MATERIALIZED VIEW TO DATA_ROLE;
grant create procedure to DATA_ROLE;
grant create sequence to DATA_ROLE;
GRANT CREATE SYNONYM TO DATA_ROLE;
grant create table to DATA_ROLE with admin option;
grant create trigger to DATA_ROLE;
grant create view to DATA_ROLE;
grant select any dictionary to DATA_ROLE;

All other scripts are run as the database schema. For the purposes of clarity, let's call the {*} TEST_DB_SCHEMA {*}. I follow the steps below in this scheme:

H3. 1. run this PL/SQL script to record the Version 1 of my XML schema:

PROMPT -------------------------------;
PROMPT INITIAL XML SCHEMA REGISTRATION;
PROMPT -------------------------------;

SET SERVEROUTPUT ON
SET FEEDBACK OFF

DECLARE
   l_xsd_url_con CONSTANT VARCHAR2(60) := 'http://home/xsd/test_binXML_v1.xsd';
   
   l_xml_schema VARCHAR2(32767);
   
   E_XSD_ALREADY_REGISTERED EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_ALREADY_REGISTERED, -31085);
BEGIN
   l_xml_schema :=
      '<xs:schema'||CHR(10)||
      'xmlns:xs="http://www.w3.org/2001/XMLSchema"'||CHR(10)||
      'xmlns:xdb="http://xmlns.oracle.com/xdb"'||CHR(10)||
      'version="1.0"'||CHR(10)||
      'xdb:storeVarrayAsTable = "true">'||CHR(10)||
      ' <xs:element name="TransactionBatch" type="TransactionBatchType" xdb:defaultTable="XSD_TEST_BATCH_BINXML1"/>'||CHR(10)||
      ' <xs:complexType name="TransactionBatchType">'||CHR(10)||
      '  <xs:sequence>'||CHR(10)||
      '   <xs:element name="Transaction" type="TransactionType" minOccurs="1" maxOccurs="unbounded" xdb:defaultTable="XSD_TEST_TRANSACTION_BINXML1"/>'||CHR(10)||
      '  </xs:sequence>'||CHR(10)||
      ' </xs:complexType>'||CHR(10)||
      ' <xs:complexType name="TransactionType">'||CHR(10)||
      '  <xs:sequence>'||CHR(10)||
      '   <xs:element name="Portal" type="PortalType" minOccurs="1" maxOccurs="1" />'||CHR(10)||
      '   <xs:element name="CustomerId" type="CustomerIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="TransactionQuantity" type="TransactionQuantityType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="AppTransactionId" type="AppTransactionIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="TransactionDetails" type="TransactionDetailType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="Username" type="UsernameType" minOccurs="1" maxOccurs="1" />'||CHR(10)||
      '  </xs:sequence>'||CHR(10)||
      ' </xs:complexType>'||CHR(10)||
      ' <xs:simpleType name="PortalType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="30"/>'||CHR(10)||
      '   <xs:enumeration value="TEST1"/>'||CHR(10)||
      '   <xs:enumeration value="TEST2"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="CustomerIdType">'||CHR(10)||
      '  <xs:restriction base="xs:string"/>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="TransactionQuantityType">'||CHR(10)||
      '  <xs:restriction base="xs:integer">'||CHR(10)||
      '   <xs:minExclusive value="0"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="AppTransactionIdType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="20"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="TransactionDetailType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="UsernameType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="30"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      '</xs:schema>';
   
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
      schemaurl       => l_xsd_url_con,
      schemadoc       => l_xml_schema,
      local           => TRUE,                             -- XSD must only be visible to the Owner DB Schema in which this script is run.
      genTypes        => FALSE,                            -- Don't want to generate object types, as we're using Binary XML.
      force           => FALSE,                            -- Raise all errors on creation
      owner           => USER,                             -- XML Schema will belong to the currently executing user.
      options         => DBMS_XMLSCHEMA.REGISTER_BINARYXML -- We wish to register the XSD as Binary XML.
   );
   
EXCEPTION
   WHEN E_XSD_ALREADY_REGISTERED
   THEN
      DBMS_OUTPUT.PUT_LINE('XML Schema '||l_xsd_url_con||' is already registered.');
      
END;
/

SET FEEDBACK ON

H3. 2. create a bunch of Table with an XMLTYPE column based on version 1 of my XML schema:

PROMPT ----------------------;
PROMPT ONE-OFF DDL STATEMENTS;
PROMPT ----------------------;

DROP TABLE test_batch;
DROP SEQUENCE seq_test_batch_id;

CREATE TABLE test_batch
(
   batch_id        NUMBER(20),
   batch_timestamp TIMESTAMP   DEFAULT SYSTIMESTAMP,
   batch_xml       XMLTYPE,
   CONSTRAINT tbh_batch_id_nn        CHECK(batch_id IS NOT NULL),
   CONSTRAINT tbh_batch_timestamp_nn CHECK(batch_timestamp IS NOT NULL),
   CONSTRAINT tbh_batch_xml_nn       CHECK(batch_xml IS NOT NULL)
)
XMLTYPE COLUMN batch_xml STORE AS SECUREFILE BINARY XML
XMLSCHEMA "http://home/xsd/test_binXML_v1.xsd"
ELEMENT "TransactionBatch"
PARTITION BY RANGE(batch_timestamp)
INTERVAL (NUMTOYMINTERVAL(1, 'MONTH'))
(
   PARTITION P_TEST_BATCH_201208 VALUES LESS THAN (TO_DATE('01-SEP-2012', 'DD-MON-YYYY')) TABLESPACE &&TABLSPACE_OF_YOUR_CHOICE
);

CREATE UNIQUE INDEX idx_tbh_batch_id ON test_batch(batch_id)
TABLESPACE TXTREME_IDX_XLG;

ALTER TABLE test_batch
   ADD CONSTRAINT tbh_batch_id_pk PRIMARY KEY (batch_id) USING INDEX idx_tbh_batch_id;

CREATE SEQUENCE seq_test_batch_id
START WITH 1
INCREMENT BY 1
MAXVALUE 99999999999999999999
CYCLE
NOCACHE
NOORDER;

H3. 3. fill this table with the test data.

PROMPT --------------------------;
PROMPT CREATING INITIAL TEST DATA;
PROMPT --------------------------;

TRUNCATE TABLE TEST_BATCH;

SET TIMING ON
DECLARE
   l_batch_count_con CONSTANT NUMBER(4) := 200;
   
   l_transaction_count   PLS_INTEGER;
   l_total_transactions  PLS_INTEGER DEFAULT 0;
   l_transaction_xmlclob CLOB;
   l_transaction_xmldoc  XMLTYPE;
BEGIN
   FOR idx IN 1..l_batch_count_con
   LOOP
      l_transaction_count := TRUNC(DBMS_RANDOM.VALUE(1,100));
      
      -- Initialise XML CLOB String. 
      l_transaction_xmlclob := '<?xml version="1.0"?>'||CHR(10)||'<TransactionBatch>';
      
      -- Insert the contents of the XML CLOB String.
      FOR idx IN 1 .. l_transaction_count
      LOOP
         l_transaction_xmlclob := l_transaction_xmlclob||CHR(10)||
                                  '  <Transaction>'||CHR(10)||
                                  '    <Portal>TEST1</Portal>'||CHR(10)||
                                  '    <CustomerId>1234567891</CustomerId>'||CHR(10)||
                                  '    <TransactionQuantity>4</TransactionQuantity>'||CHR(10)||
                                  '    <AppTransactionId>1232K89C</AppTransactionId>'||CHR(10)||
                                  '    <TransactionDetails>This is another long free text field</TransactionDetails>'||
                                  '    <Username>Jimbo2</Username>'||CHR(10)||
                                  '  </Transaction>';
      END LOOP;
      
      --Terminate XML CLOB String.
      l_transaction_xmlclob := l_transaction_xmlclob||CHR(10)||'</TransactionBatch>';
      
      -- Create XMLTYPE XML Document.
      l_transaction_xmldoc := XMLTYPE.createXML(l_transaction_xmlclob);
      
      -- Populate the TEST_BATCH Table.
      INSERT INTO test_batch
        ( batch_id,
          batch_timestamp,
          batch_xml
        )
      VALUES
        ( SEQ_TEST_BATCH_ID.NEXTVAL,
          SYSTIMESTAMP,
          l_transaction_xmldoc
        );
        
      l_total_transactions := l_total_transactions + l_transaction_count;
   END LOOP;
   
   DBMS_OUTPUT.PUT_LINE('Inserted a total of '||l_total_transactions||' transaction XML pieces across '||l_batch_count_con||' Test Batches.');
   COMMIT;
   DBMS_OUTPUT.PUT_LINE('Commit complete.');
END;
/

SET TIMING OFF

H3. 4. save the Version 2 of my XML schema

PROMPT -----------------------------------------------------------------------------------;
PROMPT NEW XML SCHEMA REGISTRATION - IDENTICAL TO OLD SCHEMA EXCEPT FOR NEW <Test> ELEMENT;
PROMPT -----------------------------------------------------------------------------------;

SET FEEDBACK OFF

DECLARE
   l_xsd_url_con CONSTANT VARCHAR2(60) := 'http://home/xsd/test_binXML_v2.xsd';
   
   l_xml_schema VARCHAR2(32767);
   
   E_XSD_ALREADY_REGISTERED EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_ALREADY_REGISTERED, -31085);
BEGIN
   l_xml_schema :=
      '<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="true">'||CHR(10)||
      '<xs:element name="TransactionBatch" type="TransactionBatchType" xdb:defaultTable="XSD_TEST_BATCH_BINXML2"/>'||CHR(10)||
      '<xs:complexType name="TransactionBatchType">'||CHR(10)||
      ' <xs:sequence>'||CHR(10)||
      '  <xs:element name="Transaction" type="TransactionType" minOccurs="1" maxOccurs="unbounded" xdb:defaultTable="XSD_TEST_TRANSACTION_BINXML2"/>'||CHR(10)||
      ' </xs:sequence>'||CHR(10)||
      '</xs:complexType>'||CHR(10)||
      '<xs:complexType name="TransactionType">'||CHR(10)||
      ' <xs:sequence>'||CHR(10)||
      '  <xs:element name="Portal" type="PortalType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="CustomerId" type="CustomerIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="TransactionQuantity" type="TransactionQuantityType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="AppTransactionId" type="AppTransactionIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="TransactionDetails" type="TransactionDetailType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="Username" type="UsernameType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="Test" type="TestType" minOccurs="0" maxOccurs="1"/>'||CHR(10)||
      ' </xs:sequence>'||CHR(10)||
      '</xs:complexType>'||CHR(10)||
      '<xs:simpleType name="PortalType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      '  <xs:enumeration value="TEST1"/>'||CHR(10)||
      '  <xs:enumeration value="TEST2"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="CustomerIdType">'||CHR(10)||
      ' <xs:restriction base="xs:string"/>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TransactionQuantityType">'||CHR(10)||
      ' <xs:restriction base="xs:integer">'||CHR(10)||
      '  <xs:minExclusive value="0"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="AppTransactionIdType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="20"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TransactionDetailType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="UsernameType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TestType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '</xs:schema>';
   
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
      schemaurl       => l_xsd_url_con,
      schemadoc       => l_xml_schema,
      local           => TRUE,                             -- XSD must only be visible to the Owner DB Schema in which this script is run.
      genTypes        => FALSE,                            -- Don't want to generate object types, as we're using Binary XML.
      force           => FALSE,                            -- Raise all errors on creation
      owner           => USER,                             -- XML Schema will belong to the currently executing user.
      options         => DBMS_XMLSCHEMA.REGISTER_BINARYXML -- We wish to register the XSD as Binary XML.
   );
   
EXCEPTION
   WHEN E_XSD_ALREADY_REGISTERED
   THEN
      DBMS_OUTPUT.PUT_LINE('XML Schema '||l_xsd_url_con||' is already registered.');
      
END;
/

SET FEEDBACK ON

H3. 5 test to insert a new XML document in line with the second XML schema. This test fails as expected.

PROMPT ---------------------------------------------------------------;
PROMPT ATTEMPT TO INSERT V2 XSD-COMPLIANT XMLDOC INTO TEST_BATCH TABLE;
PROMPT ---------------------------------------------------------------;

DECLARE
   l_transaction_xmldoc XMLTYPE;
   
   E_XSD_VALIDATION_FAILURE EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_VALIDATION_FAILURE, -31061);
BEGIN
   l_transaction_xmldoc := XMLTYPE.createXML(
                              '<?xml version="1.0" encoding="UTF-8"?>'||CHR(10)||
                              '<TransactionBatch>'||CHR(10)||
                              '  <Transaction>'||CHR(10)||
                              '    <Portal>CARMAN</Portal>'||CHR(10)||
                              '    <CustomerId>1234567891</CustomerId>'||CHR(10)||
                              '    <TransactionQuantity>4</TransactionQuantity>'||CHR(10)||
                              '    <AppTransactionId>1232K89C</AppTransactionId>'||CHR(10)||
                              '    <TransactionDetails>This is a long free text field</TransactionDetails>'||CHR(10)||
                              '    <Username>Jimbo2</Username>'||CHR(10)||
                              '    <Test>This is an In-Place Schema Evolution Test</Test>'||CHR(10)||
                              '  </Transaction>'||CHR(10)||
                              '</TransactionBatch>'
                           );
   
   -- Attempt to populate the SUBMISSION_BATCH Table.
   INSERT INTO submission_batch
     ( batch_id,
       batch_timestamp,
       batch_xml
     )
   VALUES
     ( SEQ_SUB_BATCH_ID.NEXTVAL,
       SYSTIMESTAMP,
       l_transaction_xmldoc
     );
   
   DBMS_OUTPUT.PUT_LINE(SQL%ROWCOUNT||' row inserted.');
   COMMIT;
   DBMS_OUTPUT.PUT_LINE('Commit complete.');

EXCEPTION
   WHEN E_XSD_VALIDATION_FAILURE
   THEN
      DBMS_OUTPUT.PUT_LINE('Insert failed as expected.'||CHR(10));
      DBMS_OUTPUT.PUT_LINE(SQLERRM);
END;
/

H3. 6. try Inplace development of Version 1 of the XML schema in Version 2.

PROMPT --------------------------------------------------------------------------------------;
PROMPT PERFORM IN-PLACE EVOLUTION AND DE-REGISTER/PURGE OLD SCHEMA IF EVOLUTION IS SUCCESSFUL;
PROMPT --------------------------------------------------------------------------------------;

SET TIMING ON

DECLARE
   l_current_schema   XMLTYPE;
   l_new_schema       XMLTYPE;
   l_xsd_differences  XMLTYPE;
   
   l_resource         BOOLEAN;
BEGIN
   SELECT schema
     INTO l_current_schema
     FROM user_xml_schemas
    WHERE schema_url = 'http://home/xsd/test_binXML_v1.xsd';
   
   SELECT schema
     INTO l_new_schema
     FROM user_xml_schemas
    WHERE schema_url = 'http://home/xsd/test_binXML_v2.xsd';
   
   SELECT XMLDIFF(l_current_schema, l_new_schema)
     INTO l_xsd_differences
     FROM dual;
   
   DBMS_OUTPUT.PUT_LINE('Successfully extrapolated XDIFF XML Document.');
   
   DBMS_XMLSCHEMA.inPlaceEvolve( 'http://home/xsd/test_binXML_v1.xsd',
                                 l_xsd_differences,
                                 DBMS_XMLSCHEMA.INPLACE_TRACE
                               );
   
   DBMS_OUTPUT.PUT_LINE('Successfully evolved original XML Schema.');
   
EXCEPTION
   WHEN OTHERS
   THEN
      ROLLBACK;
      DBMS_OUTPUT.PUT_LINE('Error issued during InPlace XML Schema Evolution:');
      DBMS_OUTPUT.PUT_LINE(SQLERRM);
END;
/

H3. The scripts above provide the following Test output:

Connected to Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 
Connected as TEST_DB_SCHEMA@dbs02local
 
SQL> 
-------------------------------
INITIAL XML SCHEMA REGISTRATION
-------------------------------
 
XML Schema http://home/xsd/test_binXML_v1.xsd is already registered.
 
Executed in 0 seconds

----------------------
ONE-OFF DDL STATEMENTS
----------------------
  
Table created
 
Executed in 0.016 seconds
 
Index created
 
Executed in 0.016 seconds
 
Table altered
 
Executed in 0 seconds
 
Sequence created
 
Executed in 0 seconds

--------------------------
CREATING INITIAL TEST DATA
--------------------------
 
Table truncated
 
Executed in 0.032 seconds

Inserted a total of 10259 transaction XML pieces across 200 Test Batches.
Commit complete.
 
PL/SQL procedure successfully completed
 
Executed in 8.487 seconds

-----------------------------------------------------------------------------------
NEW XML SCHEMA REGISTRATION - IDENTICAL TO OLD SCHEMA EXCEPT FOR NEW <Test> ELEMENT
-----------------------------------------------------------------------------------
 
XML Schema http://home/xsd/test_binXML_v2.xsd is already registered.

---------------------------------------------------------------
ATTEMPT TO INSERT V2 XSD-COMPLIANT XMLDOC INTO TEST_BATCH TABLE
---------------------------------------------------------------
 
Insert failed as expected.

ORA-31061: XDB error: XML event error
ORA-19202: Error occurred in XML processing
LSX-00213: only 0 occurrences of particle "Transaction", minimum is 1
 
PL/SQL procedure successfully completed
 
--------------------------------------------------------------------------------------
PERFORM IN-PLACE EVOLUTION AND DE-REGISTER/PURGE OLD SCHEMA IF EVOLUTION IS SUCCESSFUL
--------------------------------------------------------------------------------------
 
Successfully extrapolated XDIFF XML Document.
Error issued during InPlace XML Schema Evolution:
ORA-31166: internal error code to handle ignorable attributes
 
PL/SQL procedure successfully completed
 
Executed in 0.046 seconds
SQL>

NOTE: When I ran the above tests, I had already created the test of XML schemas. That's why the output messages, say...

H4. Now, as it is the first time I've ever tried evolution of XML schema in Oracle XMLDB, is there someone who could potentially open the door please, re. solve the < font color = "red" >ORA-31166< / police > error?

Hello

First of all, thank you for your efforts on the provision of a decent test case.

However, there are a few inconsistencies:

-Step 5 attempts to insert into SUBMISSION_BATCH, but the table created above is TEST_BATCH
-Same for the sequence name

Now back to the real question...

I think the problem comes because you run XMLDiff against two versions saved of your drawings.
When Oracle stores a schema, it adds a large number of attributes for internal use (you can see them by querying USER_XML_SCHEMAS. DIAGRAM) but we as end users don't have to worry about them.
However, by building the Xdiff document based on these two 'internal' versions, we explicitly say Oracle whose internal attributes must be changed during the evolution of the scheme, leading to potential conflicts.

A few other comments:
-Given that you're using the binary XML schema, you must also set "genTables-online false" and more "genTypes-online false."
-Also delete all annotations from xdb:defaultTable and xdb:storeVarrayAsTable on the diagrams, they are of no use in this situation.
-Do not save the schema of the v2, it is not necessary. Just use a transient instance when calling XMLDiff

So, to summarize:

-XMLDiff run against both original patterns (do not save a new in any case, the process of evolution will take care of replacing the old).
-of course, don't forget to change the INPLACE_TRACE to INPLACE_EVOLVE when ready :)

Hope that helps.

Published by: odie_63 on August 23, 2012 16:31 - fixed some typos

Field force on the Validation error

I have a Date field with the date of Validation of model {MM/DD/YYYY}. Is it possible once the user get the error message the cursor goes back to the Date instead of going to the next field field.

Hello

You should be able to add the JavaScript code to the output of the date field event

If (this.formattedValue = this.rawValue)

{

xfa.host.setFocus (this);

}

This works because the only time where the formattedValue is the same as the rawValue is change when then schema validation fails (or what can model edit is YYYY-MM-DD... the model rawValue).

Note: this goes against Adobe guidelines for creating forms, they feel that the user should be able to move well shape, how they want, but there are a lot of real shapes out there that works this way.

Concerning

Bruce

Installed Adobe on the K drive, now my computer has assigned portable K:\ drive to my hard drive. I am reader not valid error 1327 J:\.

Last year I buy Nero software, and it was installed on my laptop hard drive which has been J:\. Now for some reason, my computer has received a portable K:\ drive on my hard drive. So, when I try to open the program, it gives me drive not valid error 1327 J:\. He also stated that there is insufficient space in J:\, AND it gives me a message "fatal error in installation. Why he did it assign a different drive letter?

I don't know how to change the registry, because I'm sure that WHAT I have uploaded in this device will give me a similar error code when I try to use it. Help!

original title: problems in car

Hello

You must be sure that programs use the drive letter that you define or
you will need to change it back when needed. The latter would be the
more great pain in the long term.

Most programs allow you to change the data reader. If the reader is a program
installed on and then after he moved to the drive letter, you will need to re - install the
program.

I hope this helps.

Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

How to show the component validation errors inline instead of in a popup note?

Hello
IM using jdeveloper v. 11.1.2.3.0
I want to show validation errors for an inline element, and not in a pop-up note without counting as the component.
I found that it is possible through the use of the af:message component.
The af:message works very well as long as the component must be committed, is not within a taskflow in a region.
If this is the case, it seems that the af:message component is ignored, and validation errors is still a time showed in a popup note.
For an example, see the code below. This works very well on an ordinary jspx page. If the same code is implemented within a fragment of jsff in a taskflow and taskflow is then implemented as a region in a regular jspx page - the validation error is displayed in a pop-up note instead of inline.
< af:message = "input1" ID = "message1" / >
< af:inputText id = value of '1' entry validator = "< some binding value > ' ="< some binding validator >"/ >

I solved the problem. Apparently there's a bug in the ADF, so that the attribute 'for' points to a component id wrong (client side). It simply puts the container of name in twice.

The solution is to prepend ":" in front of the id of the component in the attribute 'for' during the use of the af:message within a fragment of a page in a region. See the example below.

APEX_ITEMS does not store the value in the SESSION after the validation error
Hello

I'm build dynamically using APEX_ITEMS, but it does not keep the value when the page is submitted and the validation error occurs. Here are the following steps that I am following.

When I enter SUE (more than 8 characters), SUBMIT, validation fails and the error is displayed on the page (which is fine)
BUT it does not keep SUE value (which I got) and filled with the old value which is ABC.

WHY it does not keep the value that the user entered (even as the normal Page items)

Region PL\SQL
```
declare
  v_value varchar2(20);
begin
  v_value := 'ABC'; 
  htp.p(apex_item.text(7,v_value));
end;
```
Validation (function returning the error text)
```
DECLARE
 v_count number;
 v_value varchar2(50);
 v_value1 number;
BEGIN
  v_value := apex_application.g_f07(1);
  select length(v_value) into v_value1 from dual;

      if v_value1 > 8 then
          return 'Field must have less than 9 character';
      ELSE
         return null;
      END IF;
END;
```
You use collections if you want the State to show if, after a validation error. Unfortunately, this is the case if you do not use the normal tabular forms.

Denes Kubicek
-------------------------------------------------------------------
http://deneskubicek.blogspot.com/
http://www.Apress.com/9781430235125
https://Apex.Oracle.com/pls/Apex/f?p=31517:1
http://www.Amazon.de/Oracle-Apex-XE-Praxis/DP/3826655494
-------------------------------------------------------------------

XML schema to generate data from the table of data from a repeating subform

Hi all, I would like to have a check box that when checked, allows you to hide a quote form and make a purchase order form visible, carrying a part of the field of the form of citation data in a new table on the order form. I have attached to this form to https://workspaces.acrobat.com/?d=pqpsXx5VPi * LkMeVKrX57w if you want to take a look. If the check box is cleared, he hid the PO form and to make quite visible.
The idea behind this is that my client will create his quote and send t to his client. Once the customer accepts the quote, he simply click a button to generate its purchase order send it to its supplier.
It seems that I have buttons to add lines on the submission form that the problem is more complex. I would be able to do it myself if the table has a fixed number of lines and I was able to use global fields, and naming each cell something different, but because it's a single repeating subform, I can't operate at all.
I understand that, because it's a repeating subform that I need to create an XML schema to do this, but also can not know for the life of me how to create the schema. I read tons of tutorials, but no idea how to apply it to my specific needs. I've been able to find only info on how to bind the data source once it's been created.
I would be eternally grateful if someone could help out me.
Thank you!

I edited your form and put it here.

Here's what I did:
- Script inserted into your box renamed someone who mask/displays the purchase order / sales quotation
- I have included a script object with a function I wrote to transfer data from as named fields/subforms from one section to another
- Inserted a few fields in your table of purchase order
What you need to do is to complete the development of your purchase order table. Make sure that the common fields between the quote and purchase tables have the same name in order to transfer data.

No necessary schema.

Kyle

Access to the XML schemas from the connection manager?

The connection manager for a connection opened in version 4 is no longer an 'XML Schémas' icon (Java and XML patterns seem to have been deleted between versions 3 and 4). Is there a definition that can return the XML schemas?
Using lists yet... »
XML schemas
XML schemas are definitions of schema, written in XML, that describe the structure and various other semantics of XML instance documents. For conceptual and information on the use of XML schemas, see the Guide of Oracle XML DB Developer in the Oracle database documentation library.
You can change an XML schema by right clicking in the connections Navigator XML schema name and selecting open from the menu. You can delete a selected schema by selecting the Drop Schema menu. » ...

The XML node drawings missing in the connections Navigator is a known issue for the 4.0.1. The 4.0.2 patch is a fix.

Regarding the Java node, it seems to me in all versions 4.0.x. Maybe your Preferences... > Database > Navigation filter turned it off?

Kind regards
Gary

SQL development team

How to read the data with different XML schemas within the unique connection?
- I have Oracle database 11g
- I access it via JDBC: Slim, version 11.2.0.3, same as xdb.
- I have several tables, each has an XMLType column, all based on patterns.
- There are three XML schemas different registered in the DB
- Maybe I need to read the XML data in multiple tables.
- If all the XMLTypes have the same XML schema, there is no problem,
- If patterns are different, the second reading will throw BindXMLException.
- If I reset the connection between the readings of the XMLType column with different schemas, it works.
The question is: How can I configure the driver, or the connection to be able to read the data with different XML schemas without resetting the connection (which is expensive).
Code to get data from XMLType is the implementation of case study:
```
 1   ResultSet resultSet = statement.executeQuery( sql ) ; 
 2   String result = null ; 
 3    while(resultSet.next()) { 
 4   SQLXML sqlxml = resultSet.getSQLXML(1) ; 
 5   result = sqlxml.getString() ; 
 6   sqlxml.free(); 
 7   } 
 8   resultSet.close(); 
 9    return result ; 
```
It turns out, that I needed to serialize the XML on the server and read it as BLOB. Like this:
```
 1    final Statement statement = connection.createStatement() ;  2    final String sql = String.format("select xmlserialize(content xml_content_column as blob encoding 'UTF-8') from %s where key='%s'", table, key ) ;  3   ResultSet resultSet = statement.executeQuery( sql ) ;  4   String result = null ;  5    while(resultSet.next()) {  6   Blob blob = resultSet.getBlob( 1 );  7   InputStream inputStream = blob.getBinaryStream();  8   result = new Scanner( inputStream ).useDelimiter( "\\A" ).next();  9   inputStream.close(); 10   blob.free(); 11   } 12   resultSet.close(); 13   statement.close(); 14  15   System.out.println( result ); 16    return result ; 17
```
Then it works. Still, can't get it work with XMLType in resultset. On the customer XML unwrapping explodes trying to pass to another XML schema. JDBC/XDB problem?

Associate the Workspace with schema
Apex 3.2

I have a workspace and it has 2 schema assigned.
How can I remove one of these missions?

I went to manage the areas of work/manage Workspace to assignments/changing the workspace naming scheme.
It doesn't seem to be an option to delete the assignment

Thank you

Gus
Hello

It has no function in the APEX to drop the database schema.
You must file schema by yourself.

Kind regards
Jari
-----
My Blog: http://dbswh.webhop.net/htmldb/f?p=BLOG:HOME:0
Twitter: http://www.twitter.com/jariolai

In the Studio of BEA WorkSpace XML schema Validation error

Similar Questions

Maybe you are looking for