ORA-19046 with valid xsd-file (on 11.2.0.2)

Hello Experts,
I got an xml-file and had to import it into some relational tables. The xsd-files are given.
I tried: creating ressources for the xsd-files - works; register schema's -> not possible, because of ORA-19046.
In XMLSpy validating all xsd-files (a total of seven files) is possible - not error found.
Are there any ideas, how to import the data to some tables? (I don't really need the xml-file in the database)
Thanky for any help!
Frank

XSD-Upload - Part 1/7
There are seven files - I will post the ORIGINAL Files without oracle annotations:
vda_root_V1.2.xsd
-> vda_header_V1.2.xsd
-> vda_body_V1.2.xsd
-> ehd_root_V1.40.xsd
-> keytabs_V1.40.xsd
-> ehd_header_V1.40.xsd
-> datentypen_V1.40.xsd
My Probelm-baby ist datentypen_V1.40.xsd
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- =======================================================================
Typdefinitionen für Schnittstellen,
Namensraum ist: keins
=======================================================================-->
<xs:schema xmlns="urn:ehd/001" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ehd/001" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <!--
     ============================================================
     Dokument/Instanz Identifikation
     ID-Elemente identifizieren eindeutig Objekte. Werte zur Identifizierung werden in
     Attribute EX, RT und RTV eingetragen:
     RT-Attribut (Root) enthält eine eindeutige OID des Objekts (Person/Organisation oder
     Schlüsseltabelle ...)
     EX-Attribut (Extension) enthält die Erweiterung zu OID z.B. fortlaufende Nummer,
     oder GUID bei XML-Dokumenten oder kodierten Wert aus der Schlüsseltabelle.
     RTV-Attribut wird bei Referenzierung auf Schlüsseltabellen verwendet. Hier wird
     Schlüsseltabellenversion eingegeben.
     ============================================================-->
     <xs:element name="id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="id_typ">
          <xs:attribute name="EX" type="xs:string" use="optional"/>
          <xs:attribute name="RT" type="xs:string" use="required"/>
          <xs:attribute name="RTV" type="xs:string" use="optional"/>
     </xs:complexType>
     <xs:complexType name="doc_id_typ">
          <xs:annotation>
               <xs:documentation>ist dem id_typ identisch</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="id_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="set_id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID, die über alle Versionen und zusammgengehörende Dokumente konstant bleibt</xs:documentation>
          </xs:annotation>
     </xs:element>
     <!--
     ============================================================
     Dokumentenverwaltung
     Die Zuordnung des Dokuments zu einem bestimmten Dokumenttyp wird über
     das Element <document_type_cd> erreicht. Die Dokumente werden mit
     Hilfe der Elemente <id>, <set_id>, <version_nbr> und <document_relationship>
     verwaltet. Mit <document_relationship> wird eine verkettete Liste von Dokumenten
     abgebildet, wie ein Pointer der auf den Vorgänger oder anderes Dokument zeigt.
     ============================================================
     -->
     <!-- ************************ version_nbr_typ ********************************* -->
     <xs:element name="version_nbr" type="version_nbr_typ">
          <xs:annotation>
               <xs:documentation>Versionnummer des XML-Dokuments</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="version_nbr_typ">
          <xs:attribute name="V" type="xs:nonNegativeInteger" use="required"/>
     </xs:complexType>
     <!-- ************************ document_relationship_typ ********************************* -->
     <xs:element name="document_relationship" type="document_relationship_typ">
          <xs:annotation>
               <xs:documentation>Beziehung zu anderen Dokumenten ("Anhang", "Ersatz")</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_relationship_typ">
          <xs:sequence>
               <xs:element name="document_relationship.type_cd" type="document_relationship.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>Art der Dokumentbeziehung ("Anhang", "Ersatz")</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="related_document"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="document_relationship.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.101"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ related_document_typ ********************************* -->
     <xs:element name="related_document" type="related_document_typ">
          <xs:annotation>
               <xs:documentation>Verweis auf das Original/Anhang-Dokument</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="related_document_typ">
          <xs:sequence>
               <xs:element ref="id"/>
               <xs:element ref="set_id" minOccurs="0"/>
               <xs:element ref="version_nbr" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <!-- ************************ document_type_cd_typ ********************************* -->
     <xs:element name="document_type_cd" type="document_type_cd_typ">
          <xs:annotation>
               <xs:documentation>Dokumenttype Code</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.100"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!--
     ============================================================
     Zeitangaben:
     service_tmr_typ: Gültigkeitszeitram der Daten (XML-Dokuments).
     origination_dttm_typ: Erstellungsdatum des XML-Dokuments
     ============================================================
     -->
     <!-- ************************ service_tmr_typ ********************************* -->
     <xs:element name="service_tmr" type="service_tmr_typ">
          <xs:annotation>
               <xs:documentation>Gültigkeitszeitraum (date..date)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="service_tmr_typ">
          <xs:complexContent>
               <xs:extension base="v_zeitraum_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ origination_dttm_typ ********************************* -->
     <xs:element name="origination_dttm" type="origination_dttm_typ">
          <xs:annotation>
               <xs:documentation>Erstellungsdatum</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="origination_dttm_typ">
          <xs:complexContent>
               <xs:extension base="v_date_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <!--
     ============================================================
     Person/Organisation- Angaben:
     intended_recipient_typ: beabsichtigter Empfänger/Zielgruppe.
     originator_typ: Ersteller/Urheber (Person oder Organisationi).
     provider_typ: Sender/Lieferer (Person oder Organisation).
     person_typ: Person
     person_name_typ: Name der Person
     organization_typ: Organisation
     addr_typ: Adersse
     ============================================================
     -->
     <!-- ************************ intended_recipient_typ ********************************* -->
     <xs:element name="intended_recipient" type="intended_recipient_typ">
          <xs:annotation>
               <xs:documentation>Empfänger / Zielgruppe der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="intended_recipient_typ">
          <xs:sequence>
               <xs:element name="intended_recipient.type_cd" type="intended_recipient.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="intended_recipient.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.102"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ originator_typ ********************************** -->
     <xs:element name="originator" type="originator_typ">
          <xs:annotation>
               <xs:documentation>Ersteller, Urheber des Dokuments / der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="originator_typ">
          <xs:sequence>
               <xs:element name="originator.type_cd" type="originator.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="originator.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.103"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ provider_typ ********************************** -->
     <xs:element name="provider" type="provider_typ">
          <xs:annotation>
               <xs:documentation>Sender, Lieferant des Dokuments (kann gleichzeitig der Urheber sein)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="provider_typ">
          <xs:sequence>
               <xs:element name="provider.type_cd" type="provider.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="provider.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.104"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="function_cd" type="function_cd_typ">
          <xs:annotation>
               <xs:documentation>Funktion/Rolle der Person/Organisation</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="function_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.105"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="participation_tmr" type="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum/Zeitpunkt der Teilnahme</xs:documentation>
          </xs:annotation>
     </xs:element>
     <!-- ************************ person_typ ********************************** -->
     <xs:element name="person" type="person_typ">
          <xs:annotation>
               <xs:documentation>Person-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:element name="group" type="group_typ">
          <xs:annotation>
               <xs:documentation>zugehörende Gruppe, Ausprägung (z.B. Augenarzt)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="group_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ">
                    <xs:sequence>
                         <xs:element ref="group.type_cd"/>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="group.type_cd" type="v_s_string_typ">
          <xs:annotation>
               <xs:documentation>Gruppebezeichnung (z.B. Facharztagruppe)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element ref="person_name" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="telecom" type="v_string_typ">
          <xs:annotation>
               <xs:documentation>Telekomunnikation (tel,mail,fax,...)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <!-- ************************ person_name_typ ********************************** -->
     <xs:element name="person_name" type="person_name_typ">
          <xs:annotation>
               <xs:documentation>Name der Person</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_name_typ">
          <xs:sequence>
               <xs:element name="nm" type="person_name_nm_typ"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="person_name_nm_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="GIV" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Vorname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="MID" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Zusatzname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="FAM" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Nachname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="PFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Titel (Dr.)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="SFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Namenzusatz</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="DEL" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Trennzeichen</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     <!-- ************************ organization_typ ********************************** -->
     <xs:element name="organization" type="organization_typ">
          <xs:annotation>
               <xs:documentation>Organisations-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="organization_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <!-- ************************ addr_typ ********************************** -->
     <xs:element name="addr" type="addr_typ">
          <xs:annotation>
               <xs:documentation>Adresse</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="addr_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="STR" type="v_string_typ"/>
               <xs:element name="HNR" type="v_string_typ"/>
               <xs:element name="POB" type="v_string_typ"/>
               <xs:element name="ZIP" type="v_string_typ"/>
               <xs:element name="CTY" type="v_string_typ"/>
               <xs:element name="STA" type="v_string_typ"/>
               <xs:element name="CNT" type="v_string_typ"/>
               <xs:element name="ADL" type="v_string_typ"/>
          </xs:choice>
     </xs:complexType>
     <!--
     ============================================================
     CDA-Hilfstypen (patient_typ)
     ============================================================
     -->
     <xs:element name="patient" type="patient_typ">
          <xs:annotation>
               <xs:appinfo>Patient-Informationen</xs:appinfo>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="patient_typ">
          <xs:sequence>
               <xs:element name="patient.type_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="person"/>
               <xs:element name="birth_dttm" type="v_date_typ" minOccurs="0"/>
               <xs:element name="administrative_gender_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     <!--
     ============================================================
     local_header,      Einzige Stelle, wo eigendefinierte Elemente und SCIPHOX SSUS
     verwendet werden können.
     ============================================================
     -->
     <xs:element name="local_header" type="local_header-cont.model">
          <xs:annotation>
               <xs:documentation>Element für weitere, datenartspezifische, Metainformationen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="local_header-cont.model" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
          </xs:choice>
          <xs:attribute name="ignore" type="ignore_typ" default="markup"/>
          <xs:attribute name="descriptor" type="xs:string"/>
          <xs:attribute name="render" type="xs:string"/>
     </xs:complexType>
     <!--
     ============================================================
     Komplexe Hilfstypen:
     v_string_typ: enthält nur den V-Attribut für einfache Daten-Angaben
     v_s_string_typ: wird für kodierte Wertepaare mit optionaler Schlüsseltabelle verwendet
     v_date_typ: enthält nur den V-Attribut für einfache Datums-Angaben
     v_zeitraum_typ: enthält nur den V-Attribut für Zeitraum-Angaben
     ============================================================
     -->
     <!-- ************************ v_string_typ ********************************** -->
     <xs:complexType name="v_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
     </xs:complexType>
     <!-- ************************ v_s_string_typ ********************************** -->
     <xs:element name="TRANSLTN" type="transltn_typ">
          <xs:annotation>
               <xs:documentation>interne/alternative Kodes und Schlüsseltabellen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="transltn_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="v_s_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="DN" type="xs:string" use="optional"/>
          <xs:attribute name="S" type="xs:string" use="optional"/>
          <xs:attribute name="SN" type="xs:string" use="optional"/>
          <xs:attribute name="SV" type="xs:string" use="optional"/>
     </xs:complexType>
     <!-- ************************ v_date_typ ********************************** -->
     <xs:complexType name="v_date_typ">
          <xs:attribute name="V" type="xs:date" use="required"/>
     </xs:complexType>
     <!-- ************************ v_zeitraum_typ ********************************** -->
     <xs:complexType name="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum: datum..datum</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="zeitraum_typ" use="required"/>
     </xs:complexType>
     <!-- ************************ pnxp_string_typ ********************************** -->
     <xs:complexType name="pnxp_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="QUAL" type="xs:NMTOKENS" use="optional"/>
     </xs:complexType>
     <!-- ======================================================================= -->
     <!-- Eigendefinierten Datentypen -->
     <!-- ======================================================================= -->
     <!--
     ============================================================
     Schnittstelle-Angaben:
     interface_typ: enthält Informationen über die Schnittstelle selbst.
     interface_nm_typ: Bezeichnung der Schnittstelle kann auch als kodierter Wert angegeben werden.
     interface_version_typ: Die Version der Schnittstelle
     description_typ: Kurzbeschreibung der Schnittstelle.
     ============================================================-->
     <!-- ************************ interface_typ ********************************* -->
     <xs:element name="interface" type="interface_typ">
          <xs:annotation>
               <xs:documentation>enthält Informationen über die Schnittstelle selbst</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="interface_typ">
          <xs:sequence>
               <xs:element name="id" type="interface_id_typ"/>
               <xs:element name="interface.nm" type="interface_nm_typ"/>
               <xs:element name="version" type="interface_version_typ"/>
               <xs:element ref="originator" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element name="description" type="description_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="interface_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.109"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ interface_nm_typ ********************************* -->
     <xs:complexType name="interface_nm_typ">
          <xs:annotation>
               <xs:documentation>Bezeichnung der Schnittstelle</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ interface_version_typ ********************************* -->
     <xs:complexType name="interface_version_typ">
          <xs:annotation>
               <xs:documentation>Version der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <!-- ************************ description_typ ********************************* -->
     <xs:complexType name="description_typ">
          <xs:annotation>
               <xs:documentation>Kurzbeschreibung oder Link auf die WebSite mit der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="URL" type="xs:anyURI" use="optional"/>
     </xs:complexType>
     <!--
     ============================================================
     Geltungsbereich:
     wenn die Daten nur in bestimmten KV-Bereichen gelten
     ============================================================-->
     <xs:element name="scope" type="scope_typ">
          <xs:annotation>
               <xs:documentation>Geltungsbereich</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="scope_typ">
          <xs:sequence>
               <xs:element name="id" type="scope_id_typ" maxOccurs="unbounded"/>
               <xs:element name="scope.type_cd" type="scope.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>z.B. 1=KV-Geltungsbereich</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="scope.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                         <xs:documentation>Name des Bereichs zu dem id-Element (z.B. KV-Nord)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="scope_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.106"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="scope.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.107"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <!--
     ============================================================
     Bearbeitungszustand:
     kann als kodierter Wert angegeben werden, im welchen Bearbeitungszustand das Dokument sich befindet
     ============================================================-->
     <xs:element name="state" type="state_typ">
          <xs:annotation>
               <xs:documentation>Bearbeitungszustand</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="state_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <!-- ======================================================================= -->
     <!-- einfache Typen -->
     <!-- ======================================================================= -->
     <xs:simpleType name="null.code.set">
          <xs:annotation>
               <xs:documentation>Ausprägungen für NULL-Attribut</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="NI"/>
               <xs:enumeration value="NA"/>
               <xs:enumeration value="UNK"/>
               <xs:enumeration value="NASK"/>
               <xs:enumeration value="ASKU"/>
               <xs:enumeration value="NAV"/>
               <xs:enumeration value="OTH"/>
               <xs:enumeration value="PINF"/>
               <xs:enumeration value="NINF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="guid_typ">
          <xs:annotation>
               <xs:documentation>Typ für einen Global Unique Identifier</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum datum..datum</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|(\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.)"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ignore_typ">
          <xs:restriction base="xs:string">
               <xs:enumeration value="all"/>
               <xs:enumeration value="markup"/>
          </xs:restriction>
     </xs:simpleType>
</xs:schema>

Similar Messages

  • XML Validation with multiple XSD files (referenced)

    Hello,
    I know that XML validation with version 7.1 is possible now. However I was provided with a set of XSD files that have references to each other and need to be placed in a hierachical file system order so that references can be resolved.
    An element <xsl:include schemaLocation="../../baseSchemas/baseSchema.xsd" /> is used for example. How can I handle that for XSD validation in PI? Can I create the same folder structure or do I need to put all XSD files in one directory and change the import manually?
    But most important question: Is it possible it all to use more than one XSD for schema validation?

    Dear Florian,
    I had encountered such case in a project.
    I was given 3 files. One main file and 2 others called Schema1.xsd and Schema2.xsd.
    This happens because your data type is not in single namespace, but is being referred across namespaces and software components.
    I am assuming that you have read the How to Guide for XML validations on PI 7.1
    Best way to do this quickly is as follows.
    1. Enable XML validation at adapter engine in the sender agreement.
    2. Post a message using HTTP post. (http://sappihttpclient.codeplex.com)
    3. Check communication channel in runtime workbench. There will be an error saying which is missing at what path.
    4. Create the path mentioned and place the file at that path.
    5. Repeat steps 2,3,4 for all the files.
    When you are done with this, you will get a proper validation error in case XML file is not correct. And remember to generate XSD from message type and not data type.
    Regards,
    Vikas
    Edited by: Vikas Aggarwal on Sep 2, 2009 8:45 PM
    Edited by: Vikas Aggarwal on Sep 2, 2009 8:48 PM

  • Validate a XML file with a XSD File in ABAP

    Hi everybody,
    I am searching a way for validating a XML File with an external XSD File in ABAP. I know to validate with dtd is possible, but what about XSD?
    Can you help me in my urgend problem ?
    Greetings from Germany
    ismail er

    anyone an idea for my issue ???

  • WebService - XI - WSDL with addtional XSD-files

    Hi all,
    i have a WSDL-File which contains only the operations of a webservice.
    Then i have different XSD-Files which contains the structure of the data.
    I can't find an external reference in the WSDL-file to the XSD files...
    How do i have to configure my interfaces in XI? If i use the WSDL-file only one parameter is shown (reqeuest).
    If i use the XSD-Files i can do the mapping... But I don't need the WSDL-file??!!
    Any ideas?
    regards

    Hi Wolfgang,
    There is a tag called xsd:location which relates the WSDL to external schema files .
    If you are calling a web service, then you can directly use xsd to create your data types but in some cases operation name is also required which is present in WSDL.
    Data Type is just an way to send the required data, but what operation you are calling from Web Service. A Web Service may contain various operations. So to distinguish, operation name is also required.
    Try creating your message throough XML SPY and see the input message generated , whether it matches with your XSD format or not.
    Regards,
    Piyush

  • SVG line chart raises ORA-20001 witha valid SQL query

    Hi,
    I am on version 1.6 & 10g database. I developed an SVG line chart which was working fine, but I wanted to fill in some sparse data by using data densification. So I enhanced my query with a partitioned outer join as follows:
    select null l, month_start, issue_count
    from
    (with dates as
    (select add_months
    ( to_date( '01-jul-2004' ),
    column_value-1) dt
    from table( vtable(12) )),
    iss as
    (select trunc(start_date, 'MON') mon , count(*) cnt
    from issues
    group by trunc(start_date, 'MON'))
    select dates.dt month_start, NVL(iss.cnt, 0) issue_count
    from dates left outer join iss on (dt=mon)
    Now the chart throws an ORA-20001 get_data error. The query is valid as it runs in SQL*plus no problems. What is it choking on?
    Thanks,
    Steve

    Steve,
    I didn't mean for you to put in on the Studio, just install the app in your workspace on htmldb.oracle.com, use SQL Workshop there to compile your procedures, tell us the app ID, and that's it.
    The error message presentation needs some improvement, give us time. We're spending most of our energy on improving the capability of the product.
    Scott

  • PI does not combine .wsdl file with .xsd files.

    Hi,
    I imported .wsdl file with necessary .xsd files in PI system (7.1).
    PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
    Is there anyone to help me to solve problem with test it in PI system.
    I send .wsdl file and necessary .xsd files as attachment his mail address.
    Thanks.

    Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
    Do you want me to send .wsdl and .xsd files zipped into your mail box
    instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
    Regards,
    Abhishek.

  • Create XML File from a specified XSD file

    Hi,
    I'd like to create an XML document with java. BUT How can we "bind" this creation with a XSD file. Hence, the creation may fail if the XSD binded file is not respected.
    So I know how to create XML file but not bind to this creation my proper XSD file (XML schema). With which tool can I do this ?
    Thanks.

    Hi,
    I'd like to create an XML document with java. BUT How can we "bind" this creation with a XSD file. Hence, the creation may fail if the XSD binded file is not respected.
    So I know how to create XML file but not bind to this creation my proper XSD file (XML schema). With which tool can I do this ?
    Thanks.

  • Best practice for how to access a set of wsdl and xsd files

    I've recently beeing poking around with the Oracle ESB, which requires a bunch of wsdl and xsd files from HOME/bpel/system/xmllib. What is the best practice for including these files in a BPEL project? It seems like a bad idea to copy all these files into every project that uses the ESB, especially if there are quite a few consumers of the bus. Is there a way I can reference this directory from the project so that the files can just stay in a common place for all the projects that use them?
    Bret

    Hi,
    I created a project (JDeveloper) with local xsd-files and tried to delete and recreate them in the structure pane with references to a version on the application server. After reopening the project I deployed it successfully to the bpel server. The process is working fine, but in the structure pane there is no information about any of the xsds anymore and the payload in the variables there is an exception (problem building schema).
    How does bpel know where to look for the xsd-files and how does the mapping still work?
    This cannot be the way to do it correctly. Do I have a chance to rework an existing project or do I have to rebuild it from scratch in order to have all the references right?
    Thanks for any clue.
    Bette

  • Rules Problem with multiple XSD

    Hi,
    I've done a jdev project for SOA Suite 11g including only one Business Rules which could be call by a Webservice.
    When I used 2 differents XSD to define 1 input fact and 1 output fact, the rule engine failed with an UNEXPECTED element Error
    <fault>
    <faultType>0</faultType>
    <operationErroredFault>
    <part name="payload">
    <errorInfo>
    <errorMessage>unexpected element (uri:"http://www.arvato.fr/formatPivot", local:"CUSTOMER"). Expected elements are <{http://www.arvato.fr/formatPivot}ADDRESS>,<{http://www.arvato.fr/formatPivot}DedoublonnageRule>,<{http://www.arvato.fr/formatPivot}StatusRule></errorMessage>
    </errorInfo>
    </part>
    </operationErroredFault>
    </fault>
    When I use only one XSD file in my facts fou my input and outpout values. It runs Well.
    Here are the facts definition with Multiple XSD FIle :
    http://lh5.ggpht.com/_noQvj60LDl4/S4-J8DcFEkI/AAAAAAAAAKU/fAtlSMgFS_8/separatedSchemas.png
    Here are the facts definition with Single XSD FIle :
    http://lh6.ggpht.com/_noQvj60LDl4/S4-J78qnj0I/AAAAAAAAAKQ/U1JNnaJyK50/includedSchema.png
    Could you please answer me how to use multiple xsd file in facts ?
    Regards,
    Jerome.

    Hi,
    Does anybody have any idea ?
    Regards,
    Jerome

  • Help With Ora-19046:Out-of-line table cannot be shared by two top-level tab

    Hi!
    My tutor asked me to store and query the xml files in a "native" way in xml db. First I tried to register the schemas on which those xml files are based. There are about 30 of schemas asscociated with each other, and I have to use "FORCE" to register them , like this:
    BEGIN
    DBMS_XMLSCHEMA.registerSchema(
    'http://www.isotc211.org/gmd/metadataEntity.xsd',
    bfilename('ISOGMD', 'metadataEntity.xsd'),
    TRUE,
    TRUE,
    FALSE,
    TRUE,
    TRUE);
    END;
    Then no tables are created automaticly. And when I wanted to create a XML table based on thses schemas manually, it proped the error: ORA-19046:Out-of-line table cannot be shared by two top-level tab. This has confused me for about a week. Does anyone know what's wrong with the registration? Waiting eagerly on line! Thanks!

    First of all, i create a "filename.txt" that contains all my schemas' names. the names are:
    acquisitionInformation.xsd
    applicationSchema.xsd
    basicTypes.xsd
    catalogues.xsd
    citation.xsd
    codelistItem.xsd
    constraints.xsd
    temporalTopology.xsd
    topology.xsd
    units.xsd
    uomItem.xsd
    valueObjects.xsd
    xlinks.xsd
    there are 72 schemas. Then I register them using "force":
    GRANT EXECUTE ON utl_file to fld;
    create table test (
    fld1 VARCHAR2(50));
    declare
    isto_file utl_file.file_type;
    fp_buffer varchar2(4000);
    begin
    isto_file := utl_file.fopen('MYXMLDIR', 'filename.txt', 'R');
    loop
    begin
    utl_file.get_line (isto_file , fp_buffer );
    insert into test values(fp_buffer);
    Exception
    when no_data_found then
    exit;
    end;
    end loop;
    utl_file.fclose(isto_file);
    end;
    declare
    cursor my_cursor is select fld1 from test;
    v_name varchar2(50);
    begin
    open my_cursor;
    loop
    fetch my_cursor into v_name;
    dbms_xmlschema.registerSchema(
    schemaurl=>v_name,
    schemadoc=>bfilename('MYXMLDIR',v_name),
    local=>TRUE,
    gentables=>true,
    force=>true,
    csid=>nls_charset_id('AL32UTF8')
    exit when my_cursor%NOTFOUND;
    end loop;
    close my_cursor;
    end;
    at last, when I check the types generated during registration, I found that only a small number of types are automatically generated. When I try to create table manually ( based on certain element of one schema), it props errors, sometimes "31079. 00000 - "unable to resolve reference to %s \"%s\"" ", sometimes other errors.
    If I manually register them one by one from the base schema, then the registeration fail at some point. this is the script:
    BEGIN
    DBMS_XMLSCHEMA.registerSchema(
    'geometryAggregates.xsd',
    bfilename('XSD', 'geometryAggregates.xsd'),
    TRUE,
    TRUE,
    FALSE,
    TRUE);
    END;
    ERRORS
    22881. 00000 - "dangling REF"
    Is that something wrong with my schemas? I wonder how can i paste them here. there are 72 files.......

  • XML Validation with External XSD

    Hi
    I have a xml file having DTD declaration, but my requirment is to validate this xml file with External XSD not with DTD which is declared inside the file.
    on executing java code below it is looking for DTD. how to supress validating against dtd.
    SAXParserFactory factory = SAXParserFactory.newInstance();
                   factory.setValidating(false);
                   factory.setNamespaceAware(true);
                   SchemaFactory schemaFactory =
                       SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema");
                   factory.setSchema(schemaFactory.newSchema(
                       new Source[] {new StreamSource("C:\\vittal\\Project\\received\\development-1\\da_xsd\\daAuthoring.xsd")}));
                   SAXParser parser = factory.newSAXParser();
                   XMLReader reader = parser.getXMLReader();
                   reader.setErrorHandler(new LogErrorHandler());
                   reader.parse(new InputSource("C:\\vittal\\Project\\received\\A-ADD\\DAContentExamples_2\\SampleGuidance_1.xml"));error i am getting is License file saxon-license.lic not found. Running in non-schema-aware mode
    java.io.FileNotFoundException: C:\vittal\Project\received\A-ADD\DAContentExamples_2\daAuthoring.dtd (The system cannot find the file specified)

    Hi
    I have a xml file having DTD declaration, but my requirment is to validate this xml file with External XSD not with DTD which is declared inside the file.
    on executing java code below it is looking for DTD. how to supress validating against dtd.
    SAXParserFactory factory = SAXParserFactory.newInstance();
                   factory.setValidating(false);
                   factory.setNamespaceAware(true);
                   SchemaFactory schemaFactory =
                       SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema");
                   factory.setSchema(schemaFactory.newSchema(
                       new Source[] {new StreamSource("C:\\vittal\\Project\\received\\development-1\\da_xsd\\daAuthoring.xsd")}));
                   SAXParser parser = factory.newSAXParser();
                   XMLReader reader = parser.getXMLReader();
                   reader.setErrorHandler(new LogErrorHandler());
                   reader.parse(new InputSource("C:\\vittal\\Project\\received\\A-ADD\\DAContentExamples_2\\SampleGuidance_1.xml"));error i am getting is License file saxon-license.lic not found. Running in non-schema-aware mode
    java.io.FileNotFoundException: C:\vittal\Project\received\A-ADD\DAContentExamples_2\daAuthoring.dtd (The system cannot find the file specified)

  • Validating a xml schema (xsd file)

    Hi,
    I was wondering - my program should accept schema files and before doing whatever it does with them I want to put them through a validation and present errors if any.
    I wasn't sure what is the right way to go about this - I know how to set up a validating parser with my own ErrorHandler and retrieve error info for simple xml files and xml schema instances, but how do I set up the parser to validate a schema definition?
    My first idea was to validate it like I would validate any schema instance, since xsd files also have their own schema definition, but that seems kind of funny, since obviously the parser already knows what a schema definition should look like.
    Has anyone done this?
    Thanks,
    Uri.

    Try something like this??
    DocumentBuilderFactory DBF = null;
    try
    DBF = DocumentBuilderFactory.newInstance();
    catch (Exception fce)
    // Set various configuration options
    DBF.setValidating(true);
    DBF.setNamespaceAware(true);
    DBF.setIgnoringComments(true);
    DBF.setIgnoringElementContentWhitespace(true);
    DBF.setCoalescing(true);
    DBF.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource", new File(Filename));
    DBF = DBF.newDocumentBuilder();
    DBF.setErrorHandler(this);
    DBF.setEntityResolver(this);
    catch (Exception pce)
    blah blah blah blah....
    I hope this is what you were looking/asking for... I could be way off base here 8-))

  • ORA-19563:  header validation failed for file

    hai all ,
    i faced problem when restore database from tape backup ,
    my current database 11.1.0.7.0 , with AIX OS
    im running RMAN to restore with set new name to change poiting to new lun.
    but when end of restore show this :
    channel c05: restore complete, elapsed time: 01:00:34
    channel c06: piece handle=PRFN_DB_bk_31518_1_831778821 tag=HOT_DB_BK_LEVEL0
    channel c06: restored backup piece 1
    channel c06: restore complete, elapsed time: 01:01:39
    Finished restore at 22-NOV-13
    released channel: c01
    released channel: c02
    released channel: c03
    released channel: c04
    released channel: c05
    released channel: c06
    released channel: c07
    released channel: c08
    released channel: c09
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of switch command at 11/22/2013 15:13:04
    ORA-19563:  header validation failed for file
    im open alert.log and see the error
    Errors in file /oracle/PROD/db/tech_st/11.1.0/admin/PROD_smjkt-prfn01/diag/rdbms/prod/PROD/trace/PROD_m000_5243492.trc:
    ORA-51106: check failed to complete due to an error.  See error below
    ORA-48251: Failed to open relation due to following error
    ORA-48122: error with opening the ADR block file [/oracle/PROD/db/tech_st/11.1.0/admin/PROD_smjkt-prfn01/diag/rdbms/prod/PROD/metadata/HM_FINDING.ams] [0]
    ORA-27041: unable to open file
    IBM AIX RISC System/6000 Error: 22: Invalid argument
    Additional information: 2
    ORA-01122: database file 30 failed verification check
    ORA-01110: data file 30: '/oradata51/PROD/data/ctxd01.dbf'
    ORA-01565: error in identifying file '/oradata51/PROD/data/ctxd01.dbf'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    Fri Nov 22 15:11:58 2013
    Errors in file /oracle/PROD/db/tech_st/11.1.0/admin/PROD_smjkt-prfn01/diag/rdbms/prod/PROD/trace/PROD_m000_5243494.trc:
    ORA-51106: check failed to complete due to an error.  See error below
    ORA-48251: Failed to open relation due to following error
    ORA-48122: error with opening the ADR block file [/oracle/PROD/db/tech_st/11.1.0/admin/PROD_smjkt-prfn01/diag/rdbms/prod/PROD/metadata/HM_INFO.ams] [0]
    ORA-27041: unable to open file
    IBM AIX RISC System/6000 Error: 22: Invalid argument
    Additional information: 2
    ORA-01122: database file 221 failed verification check
    ORA-01110: data file 221: '/oradata51/PROD/data/a_txn_data86.dbf'
    ORA-01565: error in identifying file '/oradata51/PROD/data/a_txn_data86.dbf'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    info
    '/oradata51/PROD/data/a_txn_data86.dbf' --> path original from production
    SET NEWNAME FOR DATAFILE 221 TO '/oracle/PROD/db/apps_st/data/a_txn_data86.dbf' --> path in Testing that do full restore
    this file already exist a_txn_data86.dbf
    someone can help me ?
    Imron

    Hi Imron,
    Ensure the file is available at the OS level, if yes then follow the below link and see if it helps you
    https://forums.oracle.com/thread/2544292
    https://forums.oracle.com/message/1237966
    https://forums.oracle.com/message/
    Thanks &
    Best Regards,

  • Loading XML(XSD) file into database by validating the format in file

    Hi,
    I have a file whose format is predefined as listed below
    <?xml version="1.0" encoding="utf-8" ?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
         <xs:element name="VVV">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="VVVHeader">
                        <xs:complexType>
                        <xs:sequence>
                        <xs:element name="UniqueIdentifier" type="xs:SEQ0001"/>
                        <xs:element name="VVVFileType" type="xs:123"/>
                        <xs:element name="FileCreatedDatetime" type="xs:23-MAY-2006"/>
                        <xs:element name="ScanDatetime" type="xs:23-MAY-2006"/>
                        <xs:element name="BatchID" type="xs:456"/>
                        <xs:element name="BatchSequence" type="xs:1001"/>
                        <xs:element name="DataEntryDatetime" type="xs:23-MAY-2006"/>
                        </xs:sequence>
                        </xs:complexType>
                        </xs:element>
                        <xs:element name="VVVDetail">
                        <xs:complexType>
                        <xs:sequence>
                        <xs:element name="RRRLocalOffice" type="xs:Mumbai"/>
                        <xs:element name="Duplicate" type="xs:No"/>
                        <xs:element name="ReRegMarker" type="xs:boolean"/>
                        <xs:element name="RegistrationMark" type="xs:Vishnu"/>
                        <xs:element name="RegMarkCheckDigit" type="xs:12S"/>
                        <xs:element name="TaxClassCode" type="xs:67"/>
                        <xs:element name="ExternalMakeCode" type="xs:Maruti"/>
                        <xs:element name="ExternalModelCode" type="xs:800LX"/>
                        <xs:element name="RRRMakeCode" type="xs:Mar"/>
                        <xs:element name="RRRModelCode" type="xs:800LV"/>
                        <xs:element name="RRRVehicleBodyCode" type="xs:98"/>
                        <xs:element name="RRRColourCode" type="xs:red"/>
                        <xs:element name="RegistrationDate" type="xs:23-MAY-2006"/>
                        <xs:element name="ChassisNumber" type="xs:num123"/>
                        <xs:element name="HC" type="xs:1.22"/>
                        <xs:element name="UnWeight" type="xs:90"/>
                        <xs:element name="NoSeats" type="xs:four"/>
                        <xs:element name="NOx" type="xs:2.22"/>
                        <xs:element name="RevenueWeight" type="xs:34"/>
                        <xs:element name="CO2" type="xs:55"/>
                        <xs:element name="Particulates" type="xs:long"/>
                        <xs:element name="CO" type="xs:3.33"/>
                        <xs:element name="HCNOx" type="xs:4.44"/>
                        <xs:element name="TrailerWeight" type="xs:66"/>
                        <xs:element name="StationaryLevel" type="xs:77"/>
                        <xs:element name="EngineSpeed" type="xs:88"/>
                        <xs:element name="DriveBynature" type="xs:99"/>
                        <xs:element name="SMMTFleetCode" type="xs:yel"/>
                        <xs:element name="Purchasercode" type="xs:4004"/>
                        <xs:element name="IndustryofUse" type="xs:office"/>
                        <xs:element name="OriginalDealerCode" type="xs:tr56"/>
                        <xs:element name="SellingDealerCode" type="xs:se23"/>
                        <xs:element name="bill110" type="xs:srira"/>
                        <xs:element name="bill111" type="xs:mula"/>
                        <xs:element name="SalesType" type="xs:krish"/>
                        </xs:sequence>
                        </xs:complexType>
                        </xs:element>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
    </xs:schema>
    I would like to update this into a a table by validating the format of the XSD file.
    I will be having several similar files.
    Steps I will be doing on this are
    1 > Pick up file from a directory one at a time
    2 > Validate the format of XSD file
    3 > If valid load into a table
    How can I achieve above steps using PL/SQL
    Pls mail me ur suggestions on very urgent basis
    Thanks in advance
    Vishnu

    Really this should be in the XML forum, but anyway....
    Just a small question... It looks as though you are using an XML schema (XSD) to store your table information along with it's data, am I correct? Seems very bizarre thing to do.
    If you are using Oracle 10g you can drop your file into the Oracle WebDAV area (XDB) and from there you can access the XML as an XMLTYPE using something like...
    SELECT rv.res.extract('/Resource/Contents/*')
    FROM   resource_view rv
    WHERE  lower(rv.any_path) = lower(lc_filename)Once you have it in the XMLTYPE variable from that query, and because your schema doesn't really define the datatypes etc. it's gonna be up to you to parse the XML using something like the DBMS_XMLDOM package and process that into create table statements or something.
    Certainly looks like you've got yourself a nice task to do there. Glad I'm not doing it.
    ;)

  • How to create java classes when multiple xsd files with same root element

    Hi,
    I got below error
    12/08/09 16:26:38 BST: [ERROR] Error while parsing schema(s).Location []. 'resultClass' is already defined
    12/08/09 16:26:38 BST: [ERROR] Error while parsing schema(s).Location []. (related to above error) the first definition appears here
    12/08/09 16:26:38 BST: Build errors for viafrance; org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.7.1:generate': Mojo execution failed.
    I tried genarate java classes from multiple xsd files, but getting above error, here in .xsd file i have the <xe: element="resultClass"> in all .xsd files.
    So I removed all .xsd files accept one, now genarated java classes correctly. but i want to genarte the java classes with diffrent names with out changing .xsd
    Can you please tell me any one how to resolve this one......
    regards
    prasad.nadendla

    Gregory:
    If you want to upload several Java classes in one script the solution is .sql file, for example:
    set define ?
    create or replace and compile java source named "my.Sleep" as
    package my;
    import java.lang.Thread;
    public class Sleep {
    public static void main(String []args) throws java.lang.InterruptedException {
    if (args != null && args.length>0) {
    int s = Integer.parseInt(args[0]);
    Thread.sleep(s*1000);
    } else
    Thread.sleep(1000);
    create or replace and compile java source named "my.App" as
    package my;
    public class App {
    public static void main(String []args) throws java.lang.InterruptedException {
    System.out.println(args[0]);
    exit
    Then the .sql file can be parsed using the SQLPlus, JDeveloper or SQLDeveloper tools.
    HTH, Marcelo.

Maybe you are looking for

  • Foreach syntax + generics, Possible compiler bug?

    I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question: for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {} for (String paramName : col.getParameterNames()) {}col is an

  • How to report an error from anonymous PL/SQL blocks

    Hello, The following SQL*Plus script WHENEVER OSERROR EXIT FAILURE WHENEVER SQLERROR EXIT FAILURE DECLARE EXIST_INDEXES BOOLEAN := FALSE; BEGIN FOR INDEX IN (SELECT * FROM INDEXES) LOOP EXIST_INDEXES := TRUE; DBMS_OUTPUT.PUT_LINE(INDEX.SCHEMA || '.'

  • Please help---merge function for two arrays.

    I am trying to create a merge function that merges two sorted arrays into a third array. I know what I am supposed to do, at least in theory, but I have been completely unsuccessful with actually getting the code to work. Since it is private, you can

  • Siebel - BIP Integration not working

    Hi, We are currently integrating Siebel 8.0.0.8 and BIP 10.1.3.4.1. Siebel - BIP Integration is not working. When we try to upload reports from Report Template Registration view, following error messages are displayed: [1] [0] Operation '<?>' of Web

  • UPS with Multiple RAIDS

    I have a SmartUPS and 2 RAIDS. How can I have the UPS shut down both RAIDS? Then when I get an Xserver, how do I get that UPS to shut down all of them? I seem to be unable to find much info relating to these topics except for APC not (yet, hopefully)