Not simple xml schema registration

How can i register schema from xsd file that contain includes of other xsd files, like "<xs:include schemaLocation="common/dataTypes.xsd"/>".

Similar Messages

"Source File does not match XML Schema"

Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.
This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?
Thanks, Don
IMPORT LOG ENTRY:
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
<MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@[email protected]"
>
 <Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
 <Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
 <Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
 <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
 <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
 <Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
 </Open>
</MDM_Log>
SOURCE FILE:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<MDMCUSTOMER>2463</MDMCUSTOMER>
<CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE>
- <RETURN>
<TYPE />
<MESSAGE />
</RETURN>
- <PT_CONTPART_RETURN>
- <item>
<MDM_CONTACT>0000000001</MDM_CONTACT>
<CONTACT>0001111119</CONTACT>
</item>
- <item>
<MDM_CONTACT>0000000004</MDM_CONTACT>
<CONTACT>0002222229</CONTACT>
</item>
</PT_CONTPART_RETURN>
- <PARTNERS>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>RE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001333329</PARTNER_NUMBER>
<DEFAULT_PARTNER>X</DEFAULT_PARTNER>
</item>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>WE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001555559</PARTNER_NUMBER>
<DEFAULT_PARTNER />
</item>
</PARTNERS>
</item>
</CUSTOMER>
</ns1:CustomerCreateResp>
SCHEMA:
 <?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
<xsd:element name="CustomerCreateResp" type="CustomerCreateResp" />
- <xsd:complexType name="CustomerCreateResp">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="CUSTOMER">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PARTNERS" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

You have to define the namespace in the URI field of XML Schmea in Console.
In MDM Console,
Admin -> XML Schemas -> Create XML Schema
You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.
Please update this post if fixed your problem.

XML SCHEMA registration for XML TYPE (storing XML files in Oracle 10g)

I have created the XML Schema for the XML file stored in Oracle 10g and also added this Schema into the database. I have related that schema with the column in the table which contains the XML file. When i execute the query to fetch the data from the stored file i am getting a blank resultset. Is registering the XML Schema is necessary, if yes then please let me know the process of doing it. I have tried following steps to register Schema, but it is not working
Step1:
DECLARE
v_return BOOLEAN;
BEGIN
v_return := dbms_xdb.createFolder('/home/');
v_return := dbms_xdb.createFolder('/home/DEV/');
v_return := dbms_xdb.createFolder('/home/DEV/xsd/');
v_return := dbms_xdb.createFolder('/home/DEV/messages/');
v_return := dbms_xdb.createFolder('/home/DEV/employees/');
COMMIT;
END;
STEP 2:
Connecting To XML DB
Step3:
Register XML schema
I am failing to execute step number 2 and hence not able to register the schema also.

<BLOCKQUOTE>quote:<HR>Originally posted by sudeepk:
If a java exception is thrown probably during ur install u might have forgotten
grant javauserpriv to scott;
grant javasyspriv to scott;
Thanks
[email protected]
<HR></BLOCKQUOTE>
Thank you!!!

Oracle Xml Schema Registration problem.

Hi Gurus,
I tried to register a schema using an xsd named 'EntityBase.xsd', using the following block. It got registered successfully.
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xmlns.oracle.com/xdb/EntityBase.xsd',
SCHEMADOC => bfilename('XMLDIR','EntityBase.xsd'),
LOCAL => FALSE,
CSID => nls_charset_id('AL32UTF8'));
END;
select local,schema_url,int_objname,qual_schema_url from dba_xml_schemas where schema_url like
'%http://xmlns.oracle.com/xdb/EntityBase.xsd%';
This gives me a record.
Now I have another xsd, VersionedEntity.xsd with which I would like to register another schema. In the xsd definition for VersionedEntity.xsd, it has Entity.xsd being used and which is already registered and the .xsd exists in the same directory 'XMLDIR'. But when I register using the following block,
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xmlns.oracle.com/xdb/VersionedEntity.xsd',
SCHEMADOC => bfilename('XMLDIR','VersionedEntity.xsd'),
CSID => nls_charset_id('AL32UTF8'));
END;
I get
ORA-31000: Resource 'EntityBase.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 61
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 126
ORA-06512: at line 2
Please help me with your expert advice. Am I doing something wrong?
Thanks and Regards,

There is a forum dedicated to XML...
XML DB

Simple xerces DOMParser. Why won't this validate? Very simple, xml schema

I have written a java program called "Validate.java" to validate an xml file. The program uses the xerces DOMParser. When I try and validate a correct .xml file with a correct schema in an .xsd file I get the following errors:
[Error] Document is invalid: no grammar found. line 2 column 6 - name5.xml
[Error] Document root element "name", must match DOCTYPE root "null". line 2 column 6 - name5.xmlThe XML file, the XSD file, and the Validate.java program are all in the same directory. My CLASSPATH includes xml-apis.jar, xercesImpl.jar, and xercesSamples.jar.
Here is the xml file (name5.xml):
<?xml version="1.0"?>
<name
 xmlns="http://www.myOwnURL.net/name"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.myOwnURL.net/name name5.xsd"
 title="Mr.">
<first>John</first>
<middle>Fitzgerald</middle>
<last>Doe</last>
</name>(I saved the file in the UTF-8 encoding, which causes it to look double spaced in some text editors.)
The schema is in the following xsd file (name5.xsd):
<?xml version="1.0"?>
<schema
 xmlns="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.myOwnURL.net/name"
 xmlns:target="http://www.myOwnURL.net/name"
 elementFormDefault="qualified">
<element name="name">
 <complexType>
 <sequence>
 <element name="first" type="string"/>
 <element name="middle" type="string"/>
 <element name="last" type="string"/>
 </sequence>
 <attribute name="title" type="string"/>
 </complexType>
</element>
</schema>(Again, the file is saved in UTF-8 format.)
Here is the code for Validate.java:
public class Validate implements org.xml.sax.ErrorHandler
 private String instance = null;
 private int warnings = 0;
 private int errors = 0;
 private int fatalErrors = 0;
 private org.apache.xerces.parsers.DOMParser parser = new org.apache.xerces.parsers.DOMParser();
 public Validate() // constructor
 parser.setErrorHandler(this); // Set the errorHandler
 public void setInstance(String s)
 instance = s;
 public boolean doValidate()
 try
 warnings = 0;
 errors = 0;
 fatalErrors = 0;
 try
 // Turn the validation feature on
 parser.setFeature( "http://xml.org/sax/features/validation", true);
 // Parse and validate
 System.out.println("Validating source document...");
 parser.parse(instance);
 // We parsed... let's give some summary info of what we did
 System.out.println("\nComplete " + warnings + " warnings " + errors + " errors " + fatalErrors + " fatal errors");
 // Return true if we made it this far with no errors
 return ((errors == 0) && (fatalErrors == 0));
 catch (org.xml.sax.SAXException e)
 System.err.println("\nCould not activate validation features - " + e.getMessage());
 return false;
 catch (Exception e)
 System.err.println("\n"+e.getMessage());
 return false;
 public void warning(org.xml.sax.SAXParseException ex)
 System.err.println("\n[Warning] " + ex.getMessage() + " line " + ex.getLineNumber()
 + " column " + ex.getColumnNumber() + " - " + instance);
 warnings++;
 public void error(org.xml.sax.SAXParseException ex)
 System.err.println("\n[Error] " + ex.getMessage() + " line " + ex.getLineNumber()
 + " column " + ex.getColumnNumber() + " - " + instance);
 errors++;
 public void fatalError(org.xml.sax.SAXParseException ex) throws org.xml.sax.SAXException
 System.err.println("\n[Fatal Error] " + ex.getMessage() + " line " + ex.getLineNumber()
 + " column " + ex.getColumnNumber() + " - " + instance);
 fatalErrors++;
 throw ex;
 public static void main(String[] args)
 Validate validate1 = new Validate();
 if (args.length == 0)
 System.out.println("Usage : java Validate <instance>");
 return;
 // Set the instance
 if (args.length >= 1) validate1.setInstance(args[0]);
 // Validate (the doValidate returns either true or false depending on
 // whether there were any errors.)
 if (!validate1.doValidate()) return;
}My question is: why do I get those errors??? Why doesn't everything just validate like it is supposed to??? Also, why does the error even mention DOCTYPE -- I thought that was for DTDs, and I am using XML Schema.
I will be very grateful to anyone who can tell me what is going on here.
Thanks,
Jon

I have solved my problem. I just needed to add the following line to my java program:
parser.setFeature("http://apache.org/xml/features/validation/schema", true);I'm still not sure how I was supposed to know this, however. I guess spending three hours searching on google is what you are supposed to do. Also, I was thrown for a bit of a loop by the following official faq found at http://xml.apache.org/xerces2-j/faq-pcfp.html:
[faq]
Question: How can I tell the parser to validate against XML Schema and not to report DTD validation errors?
Answer: Currently this is impossible. We hope that JAXP 1.2 will provide this capability via its schema language property. Otherwise, we might introduce a Xerces language property that will allow specifying the language against which validation will occur.
[faq]
I am very new to XML (less than a week), but that FAQ sure makes it sound like using only XML Schema and completely avoiding DTDs is impossible. On the other hand, I think that is what I was able to achieve by adding the above line to my code.
Oh well.
Jon

XML schema Registration ??

Hello,
Our environment is
SQL*Plus: Release 9.2.0.4.0
Oracle9i Enterprise Edition Release 9.2.0.4.0
OS Windows 2000
We registered XML schema in XML DB.
oraxdb:schemaURL="PORR_MT030001Fatalities"
<xsd:element name="BiologicsSafetyCase" type="PORR_MT030001.BiologicsSafetyCase" oraxdb:propNumber="271050" oraxdb:global="true" oraxdb:SQLName="BiologicsSafetyCase" oraxdb:SQLType="PORR_MT030001.Biologics1829_T" oraxdb:SQLSchema="HL7_KSMITH" oraxdb:memType="258" oraxdb:defaultTable="BiologicsSafetyCase1840_TAB" oraxdb:defaultTableSchema="HL7_KSMITH"/>
When we query user_xml_tables. It shows following.
SELECT "SYS"."USER_XML_TABLES"."TABLE_NAME" as "TABLE_NAME",
"SYS"."USER_XML_TABLES"."XMLSCHEMA" as "XMLSCHEMA",
"SYS"."USER_XML_TABLES"."ELEMENT_NAME" as "ELEMENT_NAME"
FROM "SYS"."USER_XML_TABLES"
WHERE ( "XMLSCHEMA" LIKE '%Fata%')
TABLE_NAME XMLSCHEMA ELEMENT_NAME
support1807_TAB PORR_MT030001Fatalities support
BiologicsSafetyCase1840_TAB PORR_MT030001Fatalities BiologicsSafetyCase
XXIfTRALI681800_TAB PORR_MT030001Fatalities XXIfTRALI68
location1587_TAB PORR_MT030001Fatalities location
XXEventDescription81799_TAB PORR_MT030001Fatalities XXEventDescription8
manufacturingProcess1793_TAB PORR_MT030001Fatalities manufacturingProcess
partOrganization1611_TAB PORR_MT030001Fatalities partOrganization
organization1616_TAB PORR_MT030001Fatalities organization
locatedPlace1583_TAB PORR_MT030001Fatalities locatedPlace
causedRecipientReacti1798_TAB PORR_MT030001Fatalities causedRecipientReaction
It shows additional O-R tables against different elements.
Is it normal?
How does these tables links with main table oraxdb:defaultTable="BiologicsSafetyCase1840_TAB" shows in registered schema header?
Do we able to segment this schema ?
Let me know your thought.
Thanks in advance.
Ram

Hello,
Our environment is
SQL*Plus: Release 9.2.0.4.0
Oracle9i Enterprise Edition Release 9.2.0.4.0
OS Windows 2000
We registered XML schema in XML DB.
oraxdb:schemaURL="PORR_MT030001Fatalities"
<xsd:element name="BiologicsSafetyCase" type="PORR_MT030001.BiologicsSafetyCase" oraxdb:propNumber="271050" oraxdb:global="true" oraxdb:SQLName="BiologicsSafetyCase" oraxdb:SQLType="PORR_MT030001.Biologics1829_T" oraxdb:SQLSchema="HL7_KSMITH" oraxdb:memType="258" oraxdb:defaultTable="BiologicsSafetyCase1840_TAB" oraxdb:defaultTableSchema="HL7_KSMITH"/>
When we query user_xml_tables. It shows following.
SELECT "SYS"."USER_XML_TABLES"."TABLE_NAME" as "TABLE_NAME",
"SYS"."USER_XML_TABLES"."XMLSCHEMA" as "XMLSCHEMA",
"SYS"."USER_XML_TABLES"."ELEMENT_NAME" as "ELEMENT_NAME"
FROM "SYS"."USER_XML_TABLES"
WHERE ( "XMLSCHEMA" LIKE '%Fata%')
TABLE_NAME XMLSCHEMA ELEMENT_NAME
support1807_TAB PORR_MT030001Fatalities support
BiologicsSafetyCase1840_TAB PORR_MT030001Fatalities BiologicsSafetyCase
XXIfTRALI681800_TAB PORR_MT030001Fatalities XXIfTRALI68
location1587_TAB PORR_MT030001Fatalities location
XXEventDescription81799_TAB PORR_MT030001Fatalities XXEventDescription8
manufacturingProcess1793_TAB PORR_MT030001Fatalities manufacturingProcess
partOrganization1611_TAB PORR_MT030001Fatalities partOrganization
organization1616_TAB PORR_MT030001Fatalities organization
locatedPlace1583_TAB PORR_MT030001Fatalities locatedPlace
causedRecipientReacti1798_TAB PORR_MT030001Fatalities causedRecipientReaction
It shows additional O-R tables against different elements.
Is it normal?
How does these tables links with main table oraxdb:defaultTable="BiologicsSafetyCase1840_TAB" shows in registered schema header?
Do we able to segment this schema ?
Let me know your thought.
Thanks in advance.
Ram

XML Schema registration error

We installed XMLDB on Oracle Server Enterprise Edition 9.2.0.3 (AIX 4.3 version).
The status from DBA_REGISTRY for Oracle XML DB is VALID.
When trying to register schema, we get following error:
ERROR at line 1:
ORA-01031: insufficient privileges
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 12
ORA-06512: at line 35
Here are the steps:
1. Connect as SYS
2. grant xdbadmin to wb_interface;
3. connect as wb_interface;
4. Try to register schema as follows
declare
doc varchar2(1000) := '<schema
targetNamespace="http://www.oracle.com/PO.xsd"
xmlns:po="http://www.oracle.com/PO.xsd"
xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="PurchaseOrderType">
<sequence>
<element name="PONum" type="decimal"/>
<element name="Company">
<simpleType>
<restriction base="string">
<maxLength value="100"/>
</restriction>
</simpleType>
</element>
<element name="Item" maxOccurs="1000">
<complexType>
<sequence>
<element name="Part">
<simpleType>
<restriction base="string">
<maxLength value="1000"/>
</restriction>
</simpleType>
</element>
<element name="Price" type="float"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
<element name="PurchaseOrder" type="po:PurchaseOrderType"/>
</schema>';
begin
dbms_xmlschema.registerSchema('http://www.oracle.com/PO.xsd', doc);
end;
Please Help!!!

check if the user already has the following privileges.
CREATE SESSION
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
ALTER SESSION
Else grant them.
The problem only comes when use do this in pl/sql.
here is a work around example.
create or replace function get_xml_data return varchar2 is
doc varchar2(1000) := '<schema
targetNamespace="http://www.oracle.com/PO.xsd"
xmlns:po="http://www.oracle.com/PO.xsd"
xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="PurchaseOrderType">
<sequence>
<element name="PONum" type="decimal"/>
<element name="Company">
<simpleType>
<restriction base="string">
<maxLength value="100"/>
</restriction>
</simpleType>
</element>
<element name="Item" maxOccurs="1000">
<complexType>
<sequence>
<element name="Part">
<simpleType>
<restriction base="string">
<maxLength value="1000"/>
</restriction>
</simpleType>
</element>
<element name="Price" type="float"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
<element name="PurchaseOrder" type="po:PurchaseOrderType"/>
</schema>';
begin
return doc;
end;
exec dbms_xmlschema.registerSchema('http://www.oracle.com/PO.xsd', get_xml_data);
good luck.

Data view not showing XML schema based Interface

Hi Experts,
I am trying to create a Interactive adobe form by following a step-by-step tutorial.The steps I have followed :
1. Created a WD ABAP component with just one field.
2. Created the context node and also an atribue for PDF Source.
3. Add an Interacive form UI element.
4. Activated the View.
5. Add template source and assigned the context node to generate a XML based interface.
6. It created Interface successfully.
7. But when I open the Adobe form, the context fields are not showing in data view as data sructure..
What could possibly be the reason for it. Please guide me why data structure is not showing.
Thanks and Regards
Sanket

Hello Snikat
Can you please give a brief how did yu solved this problem.. I'm also facing similar issue.
Thanks
Ajay

Exp XML Schema (.xsd) to another schema on same instance

Hello,
I hope someone on this forum can help me or point me in the correct direction. I want to export a schema which contains a table (EQUIPMENT) which has a XMLType column defined against a registered .xsd. I would then like to restored this schema to another schema on the same instance (development instance) and also onto another db instance.
I have been trying to do this with the help of "Chapter 30 Importing and Exporting XMLType Tables" from the Oracle® XML DB Developer's Guide
10g Release 2 (10.2). Unfortunately without success. At the end of this message I have encluded sample error messages that I am receiving for creation of TYPES which is causing my import to fail.
I cannot find any examples on the web on how to achieve an exp from one schema and imp in another either on the same instance or another one.
DDL for my table is :
create table EQUIPMENT
ID number(7) not null,
STATUSID number(7) not null,
ATTRIBUTEDATA xmltype
xmltype column ATTRIBUTEDATA xmlschema "EQUIPMENT.xsd" element EQUIPMENT_XML
tablespace TBS_DATA1;
Three test runs as follows:
1. Using an empty u2 schema and I register the .xsd file. Then I try to import (FROMUSER - TOUSER imp mode) my dump file which leads to the following error:
IMP-00017: following statement failed with ORACLE error 2304:
"CREATE TYPE "MTA1440_T" TIMESTAMP '2007-11-14:14:42:16' OID '3EE57B10307317"
"74E044080020C94102' AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T",""
"ATTRIBUTE_01" NUMBER(38),"ATTRIBUTE_02" VARCHAR2(4000 CHAR),"ATTRIBUTE_03" "
"VARCHAR2(4000 CHAR),"ATTRIBUTE_04" NUMBER(38),"ATTRIBUTE_05" VARCHAR2(4000 "
"CHAR))FINAL INSTANTIABLE "
IMP-00003: ORACLE error 2304 encountered
NOTE: Even though import failed, I now see a new TYPE created called "MTA1526_T".
2. If I try to create the TYPE as is from the error above I get the following error:
SQL> CREATE TYPE MTA1440_T
2 OID '3EE57B1030731774E044080020C94102'
3 AS OBJECT (SYS_XDBPD$ XDB.XDB$RAW_LIST_T,
4 ATTRIBUTE_01 NUMBER(38),
5 ATTRIBUTE_02 VARCHAR2(4000 CHAR),
6 ATTRIBUTE_03 VARCHAR2(4000 CHAR),
7 ATTRIBUTE_04 NUMBER(38),
8 ATTRIBUTE_05 VARCHAR2(4000 CHAR)) FINAL INSTANTIABLE;
9 /
CREATE TYPE MTA1440_T
ERROR at line 1:
ORA-02304: invalid object identifier literal
3. So now I create the "MTA1440_T" type without the OID value and retry the import.
IMP-00061: Warning: Object type "U2"."MTA1440_T" already exists with a different identifier
"CREATE TYPE "MTA1440_T" TIMESTAMP '2007-11-14:14:42:16' OID '3EE57B10307317"
"74E044080020C94102' AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T",""
"ATTRIBUTE_01" NUMBER(38),"ATTRIBUTE_02" VARCHAR2(4000 CHAR),"ATTRIBUTE_03" "
"VARCHAR2(4000 CHAR),"ATTRIBUTE_04" NUMBER(38),"ATTRIBUTE_05" VARCHAR2(4000 "
"CHAR))FINAL INSTANTIABLE "
Questions from me:
A. Can I export TYPES only as suggested by the online documentation ?
B. If importing onto same instance in another schema surely the OID for the TYPE will always fail - so then why can the import not create the required TYPE name itself during the import ?
C. Should I use global TYPES and Register the .XSD globally for all schema's in an instance to validate against .. would this prevent me from having errors on an import ?
I would appreciate any insight any one could provide me. Many thanks in advance.
Dom

Hi Guys,
Thank you all for the replies. I am dissappointed to hear that in 10g does not support exp/imp of schema's structured XML. However I am a little confused or should I say mislead by the "" documentation I
Here is an extract from chapter "30 - Importing and Exporting XMLType Tables" from the Oracle XML DB 10g Developers Guide documentation:
"..... Oracle Database supports the import and export of XML schema-based XMLType tables. An XMLType table depends on the XML schema used to define it. Similarly the XML schema has dependencies on the SQL object types created or specified for it. Thus, exporting a user with XML schema-based XMLType tables, consists of the following steps:
1. Exporting SQL Types During XML Schema Registration. As a part of the XML
schema registration process .....
2. Exporting XML Schemas. After all the types are exported, XML schemas are
exported as XML text .....
3. Exporting XML Tables. The next step is to export the tables. Export of each table consists of two steps:
A. The table definition is exported as a part of the CREATE TABLE statement....
B. The data in the table is exported as XML text. Note that data for out-of-line
tables is.....
From this documentation I was under the impression that the exp/imp of XML Schema-Based XMLType Tables was supported.
Regarding the backup mechanism/strategy for database schema's containing tables with Schema-Based XMLTypes what would you recommend the best online backup method to use - tablespace backups ?
What I need to be able to do in day-to-day work is to have the ability to be able to take a copy of a customers UAT or production database schema and apply it to a dev or test db instance here for bug testing etc. Do you have any advice on best to achieve this without the use of an exp/imp when the schema will contain Schema-Based XMLType tables.
Thank you all for your assistance so far.

Xml schema egistration

i am new to xml . i using oracle 11g.while reading xml i came to know that xml schema registration.
is it compulsary to work with xml data.what is the advantages of xml schema registration. with out registration also i am able to create xmltype tables and i am able to fetch data from tables. then what is the purpose of schema registration
schema registration means what happening exactly.

Schema Registration typically leads to better performance. With Binary XML / XML Index the differences are not critical for most applications. It also allows for better datatyping and compression, since if we tags and datatypes in advance we do do a more efficient encoding. For certain classes of applicaiton, where the object relational storage model is appropraite schema registration can lead to significantly better performance. See the XML DB basic demo for more info and the Hands on Lab for info related to Binary XML and XML Index

XML Schema Collection (SQL Server 2012): Complex Schema Collection with Attribute - Should xs or xsd be used in the coding?

Hi all,
I just got a copy of the book "Pro SQL Server 2008 XML" written by Michael Coles (published by Apress) and try to learn the XML Schema Collection in my SQL Server 2012 Management Studio (SSMS2012). I studied Chapter 4 XML Collection of the book
and executed the following code of Listing 4-8 Complex Schema with Attribute:
-- Pro SQL Server 2008 XML by Michael Coles (Apress)
-- Listing04-08.sql Complex XML Schema with Attribute
-- shcColes04-08.sql saved in C:\\Documents\XML_SQL_Server2008_code_Coles_Apress
-- 6 April 2015 8:00 PM
CREATE XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute
AS
N'<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
<xs:complexType>
<xs:sequence>
<xs:element name="name" />
<xs:element name="color" />
<xs:group ref="id-price" />
<xs:group ref="size-group" />
</xs:sequence>
<xs:attribute name="id" />
<xs:attribute name="number" />
</xs:complexType>
</xs:element>
<xs:group name="id-price">
<xs:choice>
<xs:element name="list-price" />
<xs:element name="standard-cost" />
</xs:choice>
</xs:group>
<xs:group name="size-group">
<xs:sequence>
<xs:element name="size" />
<xs:element name="unit-of-measure" />
</xs:sequence>
</xs:group>
</xs:schema>';
GO
DECLARE @x XML (dbo.ComplexTestSchemaCollection_attribute);
SET @x = N'<?xml version="1.0"?>
<item id="749" number="BK-R93R-62">
<name>Road-150 Red, 62</name>
<color>Red</color>
<list-price>3578.27</list-price>
<size>62</size>
<unit-of-measure>CM</unit-of-measure>
</item>';
SELECT @x;
GO
DROP XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute;
It worked nicely. But, I just found out the coding that was downloaded from the website of Apress and I just executed was different from the coding of Listing 4-8 listed in the book: all the <xs: ....> and </xs: ..> in my SSMS2012 are
listed as <xsd:...> and </xsd:...> respectively in the book!!?? The same thing happens in the Listing 4-3 Simple XML Schema, Listing 4-5 XML Schema and Valid XML Document with Comple Type Definition, Listion 4-6 XML Schema and XML
Document Document with Complex Type Using <sequence> and <choice>, and Listing 4-7 Complex XML Schema and XML Document with Model Group Definition (I executed last week) too. I wonder: should xs or xsd be used in the XML
Schema Collection of SSMS2012? Please kindly help, clarify this matter and explain the diffirence of using xs and xsd for me.
Thanks in advance,
Scott Chang

Hi Scott,
Using xs or xsd depends on how you declare the namespace prefix.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
I've posted a very good link in your last question, just in case you might have missed it, please see the below link.
Understanding XML Namespaces
In an XML document we use a namespace prefix to qualify the local names of both elements and attributes . A prefix is really just an abbreviation for the namespace identifier (URI), which is typically quite long. The prefix is first mapped to a namespace
identifier through a namespace declaration. The syntax for a namespace declaration is:
xmlns:<prefix>='<namespace identifier>'
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

How to create simple XML database in oracle 11g

Hi,
what are the steps to followed to create a simeple custormer XML database.
Like storing .xml file into XMLType, writing simple xml schema.....like that
how to register the .xsd
how to insert the xml data
how to querying the the data base with xquery
Thanks in Advance

Have a look a the FAQ on the main page of this XMLDB forum. That's a good source to start (besides the XMLDB Developer Guide manual).

JSTL - Problem parsing XML file w/ XML schema declarations

I'm having trouble parsing an xml document that contains XML schema declarations in the root element. I've included 2 snippets, the XML files they're supposed to parse, and their output below. The first one works and the second one doesn't. Could someone please tell me why? I find it hard to believe that no one's run into this before.
I'm running Tomcat 5.5 and I'm using JSP 2.0, jakarta standard taglibs jars (1.1.2), jdk 1.5.0_04, and the Xalan 2.7.0 jars.
Here's the first snippet:
<c:import url="/WEB-INF/config/schools.xml" var="xml" />
<x:parse doc="${xml}" var="schoolList"/>
There are <x:out select="count($schoolList//school)"/> schools in the file: 
<x:forEach select="$schoolList//school">
 <x:out select="name"/> 
</x:forEach>it parses the following xml file:
<?xml version="1.0" encoding="UTF-8"?>
<schools>
 <school id="34033">
 <name>Tumwater Middle School</name>
 <district>Tumwater</district>
 <type>middle</type>
 <active>false</active>
 </school>
 <school id="17001">
 <name>Garfield High School</name>
 <district>Seattle</district>
 <type>high</type>
 <active>true</active>
 </school>
 <school id="00023">
 <name>Tigard High School</name>
 <district>Tigard-Tualatin</district>
 <type>high</type>
 <active>true</active>
 </school>
</schools>and it outputs:
There are 3 schools in the file:
Tumwater Middle School
Garfield High School
Tigard High School-----------------------------------------
The second snippet:
<c:import url="/WEB-INF/config/schools2.xml" var="xml2" />
<x:parse doc="${xml2}" var="schoolList2"/>
There are <x:out select="count($schoolList2//school)"/> schools in the file: 
<x:forEach select="$schoolList2//school">
 <x:out select="name"/> 
</x:forEach>parses this xml file (note the xml schema declarations):
<?xml version="1.0" encoding="UTF-8"?>
<schools xmlns="http://www.serenus.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.serenus.com schools.xsd">
 <school id="34033">
 <name>Tumwater Middle School</name>
 <district>Tumwater</district>
 <type>middle</type>
 <active>false</active>
 </school>
 <school id="17001">
 <name>Garfield High School</name>
 <district>Seattle</district>
 <type>high</type>
 <active>true</active>
 </school>
 <school id="00023">
 <name>Tigard High School</name>
 <district>Tigard-Tualatin</district>
 <type>high</type>
 <active>true</active>
 </school>
</schools>and its output is:
There are 0 schools in the file:That's it! No errors at all! I'm 100% certain the variable names, filenames, etc. are correct. I've looked everywhere for an existing answer to this problem, but I can't find one. Is this a known issue? Please help.
-Ben

Hi Ben,
I got exactly the same problem and also could not find any solution.
Did you find a way out for this problem meanwhile?
Any help is welcome!

XML Schema validation in JDeveloper 10.1.3.2.0 - is it namespace-aware?

Hi everybody
Look at the following simple xml schema:
<?xml version="1.0" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="num" type="xsd:string"/>
<xsd:element name="amount" type="xsd:integer"/>
<xsd:element name="invoice">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="num"/>
<xsd:element ref="amount"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="invoices">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="xsd:invoice" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
When I open it in JDeveloper 10.1.3.2.0 and choose "Validate XML", validation executes without errors.
In spite of bad namespace declaration in <xsd:element ref="xsd:invoice" ...
For example, in XML Spy validation of this schema ends with error: "'xsd:invoice' must refer to an existing element".
If there any option on JDeveloper to turn on namespace-aware validation to prevent the above situation?

hi
Indeed, the "Validate XML" menu option only shows "Validate XML: 0 errors, 0 warnings.".
But, if you look at the "Design" tab for your schema, the "invoices" element node contains an "xsd:invoice" sequence shown in red. If you change "xsd:invoice" to "invoice" this becomes white and the node can be expanded.
One other thing, registering an XML Schema in JDeveloper like the one you posted, isn't possible without an "oracle.xml.parser.schema.XSDException" (without further details).
regards
Jan Vervecken

Unable to Generate XML Schema

Hi all,
 When i add a sales order it's giving an error like "Couldn't Generate XML schema"....can anybody pls give me some suggestions....i have tried all the possibilities but unable to rectify this error...
<?xml version="1.0"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Receiver</env:Value>
<env:Subcode>
<env:Value>-2053</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Could not Generate XML Schema</env:Text>
</env:Reason>
<env:Detail>
<Object>oDocuments</Object>
<Object>oDocuments</Object>
<ObjectIndex>1</ObjectIndex>
<Command>AddObject</Command>
<SessionID>2789C3B9-2E34-EC45-4F44-9E5F224CF30D</SessionID>
</env:Detail>
</env:Fault>
</env:Body>
</env:Envelope>
My coding for adding a sales order is given below:--
Private Sub btnClick_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnClick.Click
 Dim oQuotationXml As Xml.XmlElement
 Dim oBpCode As Xml.XmlNodeList
 Dim oDocNo As Xml.XmlNodeList
 Dim oItemCode As Xml.XmlNode
 Dim oDocDate As Xml.XmlNode
 Dim oItemQuantity As Xml.XmlNode
 Dim oDocumentLines As Xml.XmlNode
 oQuotationXml = DIS.GetEmptySalesXml(SessionID)
 oDocNo = oQuotationXml.SelectNodes("//DocEntry")
 oDocNo.Item(0).InnerText = "29"
 oBpCode = oQuotationXml.SelectNodes("//CardCode")
 oBpCode.Item(0).InnerText = "C3456"
 oDocDate = oQuotationXml.SelectSingleNode("//DocDueDate")
 oDocDate.InnerText = "20080909"
 oItemCode = oQuotationXml.SelectSingleNode("//ItemCode")
 oItemCode.InnerText = "A00006"
 oItemQuantity = oQuotationXml.SelectSingleNode("//Quantity")
 oItemQuantity.InnerText = "2"
 txtTmp.Text = oQuotationXml.OuterXml
 DIS.AddSalesOrder(SessionID, oQuotationXml.OuterXml)
regards,
shangai.

Hi Mohan,
I am facing a similar issue in creating XML from IDOC for MATMAS05, can you tell me how you fixed the issue? I am unable to follow your above comment about started with '\' in root? Can you tell me where was this please?
Thanks.
Manish

Not simple xml schema registration

Similar Messages

Maybe you are looking for