IFC Schema import to XDB

Hi,
IFC - Industry Foundation Classes released a latest schema called IFC2X3. the main schema file IFC2X3.xsd imports ex.xsd which inlcudes configuration.xsd.
when i try to register IFC2X3.xsd in oracle it raises an error that ex.xsd is not an XDB Schema.
These schema files contain elements, attributes and definitions. the schemas are valid using xmlspy. please advise with the best way forward for storing these into XDB and generating relational tables. and also loading data into database using files based on these schemas.
Many thanks
Edited by: 909882 on 24-Jan-2012 07:23

Thanks for input
I registered it via Grid Control using the force option but ii seems that dumped the xsd in the database and did not create any tables. I have selected storage as object relational.
BTW - here are the actual xsd. Oracle registered configuration.xsd successfully but not ex.xsd and IFC2X3.xsd
These files can be downloaded from http://www.iai-tech.org/ifcXML/IFC2x3/FINAL
Your input will be much regarded.
Configuration.xsd:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common"
xmlns:ex="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common"
xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="qualified">
     <xs:element name="configuration" nillable="true">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element ref="ex:include"/>
                    <xs:element ref="ex:option"/>
                    <xs:element ref="ex:type"/>
                    <xs:element ref="ex:entity"/>
               </xs:choice>
               <xs:attribute name="id" type="xs:ID" use="required"/>
               <xs:attribute name="targetNamespace" type="xs:anyURI" use="optional"/>
               <xs:attribute name="schema" type="xs:IDREF" use="optional"/>
               <xs:attribute name="configurationLocation" type="ex:Seq-anyURI" use="optional"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="include">
          <xs:complexType>
               <xs:attribute name="configuration" type="xs:IDREF" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="option">
          <xs:complexType>
               <xs:attribute name="inheritance" type="xs:boolean" default="false"/>
               <xs:attribute name="exp-type" type="ex:exp-type" default="unspecified"/>
               <xs:attribute name="exp-attribute" type="ex:exp-attribute" default="double-tag"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" default="false"/>
               <xs:attribute name="sparse" type="xs:boolean" default="false"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" default="unspecified"/>
               <xs:attribute name="naming-convention" type="ex:naming-convention" default="initial-upper"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="type">
          <xs:complexType>
               <xs:choice minOccurs="0">
                    <xs:element ref="ex:aggregate"/>
               </xs:choice>
               <xs:attribute name="select" type="xs:NMTOKEN" use="required"/>
               <xs:attribute name="name" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="map" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="exp-type" type="ex:exp-type" use="optional"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" use="optional"/>
               <xs:attribute name="sparse" type="xs:boolean" use="optional"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" use="optional"/>
               <xs:attribute name="notation" type="xs:normalizedString" use="optional"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="entity">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element ref="ex:attribute"/>
                    <xs:element ref="ex:inverse"/>
               </xs:choice>
               <xs:attribute use="required" name="select">
                    <xs:simpleType>
                         <xs:restriction>
                              <xs:simpleType>
                                   <xs:list itemType="xs:Name"/>
                              </xs:simpleType>
                              <xs:minLength value="1"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:attribute>
               <xs:attribute name="name" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="tag-source" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="tag-values" type="xs:NMTOKENS" use="optional"/>
               <xs:attribute name="exp-type" type="ex:exp-type" use="optional"/>
               <xs:attribute name="content" type="ex:content" use="optional"/>
               <xs:attribute name="exp-attribute" type="ex:exp-attribute" use="optional"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" use="optional"/>
               <xs:attribute name="sparse" type="xs:boolean" use="optional"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" use="optional"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="attribute">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element ref="ex:aggregate"/>
               </xs:choice>
               <xs:attribute name="select" type="xs:NMTOKEN" use="required"/>
               <xs:attribute name="name" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="exp-attribute" type="ex:exp-attribute" use="optional"/>
               <xs:attribute name="content" type="ex:content" use="optional"/>
               <xs:attribute name="keep" type="xs:boolean" default="false"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" use="optional"/>
               <xs:attribute name="sparse" type="xs:boolean" use="optional"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" use="optional"/>
               <xs:attribute name="notation" type="xs:normalizedString" use="optional"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="inverse">
          <xs:complexType>
               <xs:attribute name="select" type="xs:NMTOKEN" use="required"/>
               <xs:attribute name="name" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="exp-attribute" type="ex:exp-attribute" use="optional"/>
               <xs:attribute name="content" type="ex:content" use="optional"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" use="optional"/>
               <xs:attribute name="sparse" type="xs:boolean" use="optional"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" use="optional"/>
               <xs:attribute name="use-id" type="xs:boolean" use="optional"/>
               <xs:attribute name="invert" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="keep" type="xs:boolean" default="false"/>
               <xs:attribute name="minOccurs" type="xs:nonNegativeInteger" use="optional" default="0"/>
               <xs:attribute name="maxOccurs" type="ex:nonNegativeInteger_or_unbounded" use="optional" default="unbounded"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="aggregate">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element ref="ex:aggregate"/>
               </xs:choice>
               <xs:attribute name="name" type="xs:NMTOKEN" use="optional"/>
               <xs:attribute name="exp-attribute" type="ex:exp-attribute" use="optional"/>
               <xs:attribute name="flatten" type="ex:boolean_or_depth" use="optional"/>
               <xs:attribute name="sparse" type="xs:boolean" use="optional"/>
               <xs:attribute name="tagless" type="ex:boolean_or_unspecified" use="optional"/>
               <xs:attribute name="use-id" type="xs:boolean" use="optional"/>
          </xs:complexType>
     </xs:element>
     <xs:simpleType name="exp-type">
          <xs:restriction base="xs:string">
               <xs:enumeration value="root"/>
               <xs:enumeration value="value"/>
               <xs:enumeration value="unspecified"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="exp-attribute">
          <xs:restriction base="xs:string">
               <xs:enumeration value="double-tag"/>
               <xs:enumeration value="attribute-tag"/>
               <xs:enumeration value="entity-tag"/>
               <xs:enumeration value="no-tag"/>
               <xs:enumeration value="attribute-content"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="content">
          <xs:restriction base="xs:string">
               <xs:enumeration value="value"/>
               <xs:enumeration value="ref"/>
               <xs:enumeration value="unspecified"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="naming-convention">
          <xs:restriction base="xs:string">
               <xs:enumeration value="initial-upper"/>
               <xs:enumeration value="camel-case"/>
               <xs:enumeration value="preserve-case"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="boolean_or_unspecified">
          <xs:union memberTypes="xs:boolean">
               <xs:simpleType>
                    <xs:restriction base="xs:string">
                         <xs:enumeration value="unspecified"/>
                    </xs:restriction>
               </xs:simpleType>
          </xs:union>
     </xs:simpleType>
     <xs:simpleType name="boolean_or_depth">
          <xs:union memberTypes="xs:boolean xs:nonNegativeInteger"/>
     </xs:simpleType>
     <xs:simpleType name="nonNegativeInteger_or_unbounded">
          <xs:union memberTypes="xs:nonNegativeInteger">
               <xs:simpleType>
                    <xs:restriction base="xs:string">
                         <xs:enumeration value="unbounded"/>
                    </xs:restriction>
               </xs:simpleType>
          </xs:union>
     </xs:simpleType>
     <!-- xs:simpleType name="Seq-anyURI">
          <xs:list itemType="xs:anyURI"/>
     </xs:simpleType -->
</xs:schema>
ex.xsd:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ex="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <!-- INCLUDE the configuration schema holding the P28 configuration schema -->
     <xs:include schemaLocation="configuration.xsd"/>
     <!-- DEFINE the P28 root element -->
     <xs:element name="iso_10303_28">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="ex:iso_10303_28_header" minOccurs="0"/>
                    <xs:element ref="ex:uos"/>
                    <!-- <xs:choice minOccurs="0" maxOccurs="unbounded">
                              <xs:element ref="ex:express"/>
                              <xs:element ref="ex:schema_population"/>
                              <xs:element ref="ex:configuration"/>
                    </xs:choice> -->
               </xs:sequence>
               <xs:attribute name="version" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <!-- DEFINE the P28 schema population and express elements -->
     <!-- schema population is not used for ifcXML -->
     <xs:element name="schema_population">
          <xs:complexType>
               <xs:attribute name="governing_schema" type="xs:IDREF" use="required"/>
               <xs:attribute name="governed_sections" type="xs:IDREFS" use="optional"/>
               <xs:attribute name="determination_method" type="xs:normalizedString" default="section_boundary"/>
          </xs:complexType>
     </xs:element>
     <!-- express element is not used for ifcXML -->
     <xs:element name="express" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:string">
                         <xs:attribute name="schemaLocation" type="ex:Seq-anyURI" use="optional"/>
                         <xs:attribute name="id" type="xs:ID" use="required"/>
                         <xs:attribute name="schema_identifier" type="xs:normalizedString" use="optional"/>
                         <xs:attribute name="schema_name" type="xs:normalizedString" use="optional"/>
                         <xs:attribute name="schema_version" type="xs:normalizedString" use="optional"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <!-- DEFINE the P28 header element -->
     <xs:element name="iso_10303_28_header">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="name" type="xs:anyURI"/>
                    <xs:element name="time_stamp" type="xs:dateTime"/>
                    <xs:element name="author" type="xs:string"/>
                    <xs:element name="organization" type="xs:string"/>
                    <xs:element name="preprocessor_version" type="xs:string"/>
                    <xs:element name="originating_system" type="xs:string"/>
                    <xs:element name="authorization" type="xs:string"/>
                    <xs:element name="documentation" type="xs:string"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <!-- DEFINE the P28 base element UOS -->
     <xs:element name="uos" type="ex:uos" abstract="true"/>
     <xs:complexType name="uos">
          <xs:attribute name="id" type="xs:ID" use="required"/>
          <xs:attribute name="express" type="ex:Seq-anyURI" use="optional"/>
          <xs:attribute name="configuration" type="ex:Seq-anyURI" use="optional"/>
          <xs:attribute name="schemaLocation" type="ex:Seq-anyURI" use="optional"/>
          <xs:attribute name="edo" type="xs:anyURI" use="optional"/>
          <xs:attribute name="description" type="xs:string" use="optional"/>
     </xs:complexType>
     <!-- EX ENTITY DEFINTIONS and DECLARATIONS -->
     <xs:element name="Entity" type="ex:Entity" abstract="true"/>
     <xs:complexType name="Entity" abstract="true">
          <xs:attribute name="href" type="xs:anyURI" use="optional"/>
          <xs:attribute name="ref" type="xs:IDREF" use="optional"/>
          <xs:attribute name="proxy" type="xs:IDREF" use="optional"/>
          <xs:attribute name="edo" type="xs:anyURI" use="optional"/>
          <xs:attributeGroup ref="ex:instanceAttributes"/>
     </xs:complexType>
     <!-- GLOBAL ATTRIBUTE DECLARATIONS -->
     <xs:attribute name="arraySize">
          <xs:simpleType>
               <xs:restriction>
                    <xs:simpleType>
                         <xs:list itemType="xs:integer"/>
                    </xs:simpleType>
                    <xs:minLength value="1"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:attribute>
     <xs:attribute name="itemType" type="xs:QName"/>
     <xs:attribute name="cType">
          <xs:simpleType>
               <xs:list itemType="ex:aggregateType"/>
          </xs:simpleType>
     </xs:attribute>
     <xs:attribute name="attributeType">
          <xs:simpleType>
               <xs:restriction base="xs:normalizedString">
                    <xs:enumeration value="explicit"/>
                    <xs:enumeration value="inverse"/>
                    <xs:enumeration value="derived"/>
                    <xs:enumeration value="renamed"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:attribute>
     <xs:simpleType name="Seq-anyURI">
          <xs:list itemType="xs:anyURI"/>
     </xs:simpleType>
     <!-- GLOBAL ATTRIBUTE GROUP DECLARATIONS -->
     <xs:attributeGroup name="instanceAttributes">
          <xs:attribute name="id" type="xs:ID" use="optional"/>
          <xs:attribute name="path" type="xs:NMTOKENS" use="optional"/>
          <xs:attribute name="pos" use="optional">
               <xs:simpleType>
                    <xs:restriction>
                         <xs:simpleType>
                              <xs:list itemType="xs:integer"/>
                         </xs:simpleType>
                         <xs:minLength value="1"/>
                    </xs:restriction>
               </xs:simpleType>
          </xs:attribute>
     </xs:attributeGroup>
     <!-- GLOBAL SIMPLE TYPE DECLARATIONS -->
     <xs:simpleType name="aggregateType">
          <xs:restriction base="xs:normalizedString">
               <xs:enumeration value="array"/>
               <xs:enumeration value="list"/>
               <xs:enumeration value="set"/>
               <xs:enumeration value="bag"/>
               <xs:enumeration value="array-unique"/>
               <xs:enumeration value="array-optional"/>
               <xs:enumeration value="array-optional-unique"/>
               <xs:enumeration value="list-unique"/>
          </xs:restriction>
     </xs:simpleType>
     <!-- WRAPPERS (OR INSTANCE ELEMENTS) FOR ATOMIC SIMPLE TYPES -->
     <xs:element name="base64Binary-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="ex:base64Binary">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="base64Binary">
          <xs:simpleContent>
               <xs:extension base="xs:base64Binary">
                    <xs:attribute name="extraBits" type="xs:integer" use="optional"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:element name="hexBinary-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="ex:hexBinary">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="hexBinary">
          <xs:simpleContent>
               <xs:extension base="xs:hexBinary">
                    <xs:attribute name="extraBits" type="xs:integer" use="optional"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:element name="logical-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="ex:logical">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:simpleType name="logical">
          <xs:restriction base="xs:string">
               <xs:enumeration value="false"/>
               <xs:enumeration value="true"/>
               <xs:enumeration value="unknown"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:element name="boolean-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:boolean">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="decimal-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:decimal">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="double-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:double">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="long-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:long">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="integer-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:integer">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="string-wrapper" nillable="true">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:normalizedString">
                         <xs:attributeGroup ref="ex:instanceAttributes"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
</xs:schema>
IFC2X3.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- created with EXPTOOL V20070502 (perl 5 program) written by Thomas Liebich, AEC3, [email protected] -->
<!-- validated with XMLspy2007 sp2 (http://www.xmlspy.com) by Thomas Liebich, AEC3, [email protected] -->
<!-- configuration options used to create the following XML schema definitions following ISO 10303-28ed2 CD -->
<!-- global options within the <option> scoping element -->
<!-- + <inheritance> = "true" -->
<!-- + <exp-type> = "unspecified" -->
<!-- + <exp-attribute> = "double-tag" -->
<!-- + <flatten> = "false" -->
<!-- + <sparse> = "true" -->
<!-- + <tagless> = "false" -->
<!-- + <naming-convention> = "preserve-case" -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:ex="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ifc="http://www.iai-tech.org/ifcXML/IFC2x3/FINAL" attributeFormDefault="unqualified" targetNamespace="http://www.iai-tech.org/ifcXML/IFC2x3/FINAL">
<!-- root element declaration (for SCHEMA definitions) -->
     <xs:import namespace="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common" schemaLocation="http://www.iai-tech.org/ifcXML/IFC2x3/FINAL/ex.xsd">
     </xs:import>
     <xs:element substitutionGroup="ex:uos" name="uos" type="ifc:uos">
     </xs:element>
     <xs:complexType name="uos">
          <xs:complexContent>
               <xs:extension base="ex:uos">
                    <xs:choice minOccurs="0" maxOccurs="unbounded">
                         <xs:element ref="ex:Entity">
                         </xs:element>
                    </xs:choice>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
<!-- element and complex type declarations (for ENTITY definitions) -->
     <xs:element substitutionGroup="ifc:IfcCompositeCurve" name="Ifc2DCompositeCurve" nillable="true" type="ifc:Ifc2DCompositeCurve">
     </xs:element>
     <xs:complexType name="Ifc2DCompositeCurve">
          <xs:complexContent>
               <xs:extension base="ifc:IfcCompositeCurve">
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcControl" name="IfcActionRequest" nillable="true" type="ifc:IfcActionRequest">
     </xs:element>
     <xs:complexType name="IfcActionRequest">
          <xs:complexContent>
               <xs:extension base="ifc:IfcControl">
                    <xs:sequence>
                         <xs:element name="RequestID" type="ifc:IfcIdentifier">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcObject" name="IfcActor" nillable="true" type="ifc:IfcActor">
     </xs:element>
     <xs:complexType name="IfcActor">
          <xs:complexContent>
               <xs:extension base="ifc:IfcObject">
                    <xs:sequence>
                         <xs:element name="TheActor">
                              <xs:complexType>
                                   <xs:group ref="ifc:IfcActorSelect">
                                   </xs:group>
                              </xs:complexType>
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ex:Entity" name="IfcActorRole" nillable="true" type="ifc:IfcActorRole">
     </xs:element>
     <xs:complexType name="IfcActorRole">
          <xs:complexContent>
               <xs:extension base="ex:Entity">
                    <xs:sequence>
                         <xs:element name="Role" type="ifc:IfcRoleEnum">
                         </xs:element>
                         <xs:element name="UserDefinedRole" minOccurs="0" type="ifc:IfcLabel" nillable="true">
                         </xs:element>
                         <xs:element name="Description" minOccurs="0" type="ifc:IfcText" nillable="true">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcDistributionControlElementType" name="IfcActuatorType" nillable="true" type="ifc:IfcActuatorType">
     </xs:element>
     <xs:complexType name="IfcActuatorType">
          <xs:complexContent>
               <xs:extension base="ifc:IfcDistributionControlElementType">
                    <xs:sequence>
                         <xs:element name="PredefinedType" type="ifc:IfcActuatorTypeEnum">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ex:Entity" name="IfcAddress" nillable="true" type="ifc:IfcAddress" abstract="true">
     </xs:element>
     <xs:complexType name="IfcAddress" abstract="true">
          <xs:complexContent>
               <xs:extension base="ex:Entity">
                    <xs:sequence>
                         <xs:element name="Purpose" minOccurs="0" type="ifc:IfcAddressTypeEnum" nillable="true">
                         </xs:element>
                         <xs:element name="Description" minOccurs="0" type="ifc:IfcText" nillable="true">
                         </xs:element>
                         <xs:element name="UserDefinedPurpose" minOccurs="0" type="ifc:IfcLabel" nillable="true">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcFlowControllerType" name="IfcAirTerminalBoxType" nillable="true" type="ifc:IfcAirTerminalBoxType">
     </xs:element>
     <xs:complexType name="IfcAirTerminalBoxType">
          <xs:complexContent>
               <xs:extension base="ifc:IfcFlowControllerType">
                    <xs:sequence>
                         <xs:element name="PredefinedType" type="ifc:IfcAirTerminalBoxTypeEnum">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcFlowTerminalType" name="IfcAirTerminalType" nillable="true" type="ifc:IfcAirTerminalType">
     </xs:element>
     <xs:complexType name="IfcAirTerminalType">
          <xs:complexContent>
               <xs:extension base="ifc:IfcFlowTerminalType">
                    <xs:sequence>
                         <xs:element name="PredefinedType" type="ifc:IfcAirTerminalTypeEnum">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcEnergyConversionDeviceType" name="IfcAirToAirHeatRecoveryType" nillable="true" type="ifc:IfcAirToAirHeatRecoveryType">
     </xs:element>
     <xs:complexType name="IfcAirToAirHeatRecoveryType">
          <xs:complexContent>
               <xs:extension base="ifc:IfcEnergyConversionDeviceType">
                    <xs:sequence>
                         <xs:element name="PredefinedType" type="ifc:IfcAirToAirHeatRecoveryTypeEnum">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcDistributionControlElementType" name="IfcAlarmType" nillable="true" type="ifc:IfcAlarmType">
     </xs:element>
     <xs:complexType name="IfcAlarmType">
          <xs:complexContent>
               <xs:extension base="ifc:IfcDistributionControlElementType">
                    <xs:sequence>
                         <xs:element name="PredefinedType" type="ifc:IfcAlarmTypeEnum">
                         </xs:element>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element substitutionGroup="ifc:IfcDimensionCurveDirectedCallout" name="IfcAngularDimension" nillable="true" type="ifc:IfcAngularDimension">
     </xs:element>
     <xs:complexType name="IfcAngularDimension">
          <xs:complexContent>
               <xs:extension base="ifc:IfcDimensionCurveDirectedCallout">
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
>>> deleted a portion of it to fit oracle's 30000 character limit
</xs:schema>
---------------------------- END -------------------------------------------------------------------------------------------------------------------------------
Edited by: 909882 on Jan 25, 2012 9:34 AM

Similar Messages

  • Schema Import failed :IMP-00008: unrecognized statement in the export file:

    Hi ,
    I was running a database schema import from a database DMP file.
    I encountered the following error in the log file that was getting generated :
    IMP-00008: unrecognized statement in the export file:
    All the tables got copied except for one. Now what I have thought of is to import that one table again after taking an export from the prod schema.
    But what about the functions,triggers,procedures ?? How do i bring all of them in the schema ?
    If reimporting the schema again the only option ?
    Thanks
    Kk

    Hello,
    In this order:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#i1023988
    Table Objects: Order of Import
    Table objects are imported as they are read from the export file. The export file contains objects in the following order:
    1. Type definitions
    2. Table definitions
    3.Table data
    4.Table indexes
    5. Integrity constraints, views, procedures, and triggers
    6. Bitmap, function-based, and domain indexes
    The order of import is as follows: new tables are created, data is imported and indexes are built, triggers are imported, integrity constraints are enabled on the new tables, and any bitmap, function-based, and/or domain indexes are built. This sequence prevents data from being rejected due to the order in which tables are imported. This sequence also prevents redundant triggers from firing twice on the same data (once when it is originally inserted and again during the import).
    For example, if the emp table has a referential integrity constraint on the dept table and the emp table is imported first, all emp rows that reference departments that have not yet been imported into dept would be rejected if the constraints were enabled.
    When data is imported into existing tables, however, the order of import can still produce referential integrity failures. In the situation just given, if the emp table already existed and referential integrity constraints were in force, many rows could be rejected.
    A similar situation occurs when a referential integrity constraint on a table references itself. For example, if scott's manager in the emp table is drake, and drake's row has not yet been loaded, scott's row will fail, even though it would be valid at the end of the import.

  • Database full compile while doing schema import using impdp

    hi,
    oracle 10g
    Database full compile while doing schema import using impdp..
    what is happening here..
    regards,
    Deepak

    My scenario
    I need to import the particular schema from the full export dump. which has taken by using expdp. while importing i am using remap_schema for a single schema.
    But it try to import the full dump and compile all the schema objects.
    regards,
    Deepak

  • 2 level schema import: cvc-complex-type.2.4.a: Invalid content was found...

    HI
    I'm writing an application that gathers xml documents into batches, sends these batches to translation, receives them from translation and unpacks them.
    My documents are ads. I have a schema (x1.xsd) describing them. This schema imports another schema (x2.xsd). None of these are controlled by me (I need a very good reason to change them).
    I have created a new schema (x.xsd) for my batches. This schma imports the ad schema (x1.xsd).
    When I validate an example ad (x1.xml) using the ad schema (x1.xsd), validation is OK. This is the same for XML Spy, oracle.xml.schemavalidator.XSDValidator and org.dom4j.io.SAXReader
    When I validate an example batch (x.xml) with the same ad data in the batch,
    XML Spy says: Unexpected element 'AD' in element 'ADS'. Expected: AD
    oracle.xml.schemavalidator.XSDValidator says: XML-24521: (Error) Element not completed: 'ADS'org.dom4j.io.SAXReader says: cvc-complex-type.2.4.a: Invalid content was found starting with element 'AD'. One of '{"x/translation":AD}' is expected.
    By changing my batch xml by removing xmlns="x/ad" from the AD tag and prefix all "x/ad"-owned tags with ad:, I can make all validators validate.
    But I don't see the reason for this, and thus have some problems telling the supplier that we need to change the schema and xml...
    Notice that I do not have the corresponding problem in the x1.xsd / x2.xsd relationship !!??
    Any suggestions will be appreciated.
    /Jornsen
    I enclose a copy of the files mentioned above:
    x.xml:
    <TRANSLATION_BATCH batchId="8" xmlns="x/translation" xmlns:ad="x/ad" xmlns:gp="x/groups"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tl="x/translation" xsi:schemaLocation="x/translation
    C:\tmp\t.xsd">
      <LANGUAGES anattr="monoLanguageXmlAd">
        <LANG LangId="3"/>
        <LANG LangId="4"/>
      </LANGUAGES>
      <ADS>
        <AD adattr="hest" xmlns="x/ad" xmlns:gp="x/groups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <LANGLIST>
            <LANG LangId="17"/>
          </LANGLIST>
          <ITEMLIST>
            <ITEM xmlns="x/groups" anattr="hund">
              <ITEM_INFO name="hest"/>
            </ITEM>
          </ITEMLIST>
        </AD>
      </ADS>
    </TRANSLATION_BATCH>x1.xml:
    <AD adattr="hest" xmlns="x/ad" xmlns:gp="x/groups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="x/ad C:\tmp\t1.xsd">
      <LANGLIST>
        <LANG LangId="17"/>
      </LANGLIST>
      <ITEMLIST>
        <ITEM xmlns="x/groups" anattr="hund">
          <ITEM_INFO name="hest"/>
        </ITEM>
      </ITEMLIST>
    </AD>x.xsd:
    <xs:schema targetNamespace="x/translation" attributeFormDefault="unqualified" elementFormDefault="qualified"
    xmlns="x/translation" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tl="x/translation" xmlns:ad="x/ad">
      <xs:import namespace="x/ad" schemaLocation="t1.xsd"/>
      <xs:element name="TRANSLATION_BATCH">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="LANGUAGES">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="LANG" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:attribute name="LangId" type="xs:string" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="anattr" type="xs:string"/>
              </xs:complexType>
            </xs:element>
            <xs:element name="ADS">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="AD" type="ad:ADType"/>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="batchId" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:schema>x1.xsd:
    <xs:schema targetNamespace="x/ad" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns="x/ad"
    xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ad="x/ad" xmlns:gp="x/groups">
      <xs:import namespace="x/groups" schemaLocation="t2.xsd"/>
      <xs:element name="AD" type="ad:ADType">
      </xs:element>
      <xs:complexType name="ADType">
        <xs:sequence>
          <xs:element name="LANGLIST" type="ad:LANGLISTType">
          </xs:element>
          <xs:element name="ITEMLIST" type="gp:ITEMLISTType">
          </xs:element>
        </xs:sequence>
        <xs:attribute name="adattr" type="xs:string" use="optional"/>
      </xs:complexType>
      <xs:complexType name="LANGType">
        <xs:attribute name="LangId" type="xs:int" use="required"/>
      </xs:complexType>
      <xs:complexType name="LANGLISTType">
        <xs:sequence>
          <xs:element name="LANG" type="ad:LANGType" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>x2.xsd:
    <xs:schema xmlns="x/groups" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="x/groups"
    elementFormDefault="qualified" attributeFormDefault="unqualified">
      <xs:complexType name="ITEMLISTType">
        <xs:sequence>
          <xs:element name="ITEM" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="ITEM_INFO" maxOccurs="unbounded">
                  <xs:complexType>
                    <xs:attribute name="name" type="xs:string" use="required"/>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="anattr" type="xs:string"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>Message was edited by:
    Jornsen - formatting
    Message was edited by:
    Jornsen

    Hi Linyin,
    Please refer to: http://middlewaremagic.com/weblogic/?p=2034
    The Problem is missing element <web-resource-name> in your "web.xml" file..... which must be a Unique name of your Resource set which u want to make secure.....
    <security-constraint>
    <web-resource-collection>
    *<web-resource-name>MySecureResources</web-resource-name>*
    <description>Some Description</description>
    <url-pattern>/*</url-pattern>
    <http-method>GET</http-method>
    <http-method>POST</http-method>
    </web-resource-collection>
    <auth-constraint>
    <role-name>admin</role-name>
    </auth-constraint>
    </security-constraint>
    <login-config>
    <auth-method>BASIC</auth-method>
    </login-config>
    <security-role>
    <role-name>admin</role-name>
    </security-role>
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic   (Middleware Magic Is Here)

  • Validating WSDL with schema imports

    Hello,
    i'm trying to validate a WSDL that uses a schema import construction, like
    <wsdl:types>
    <xsd:schema>
    <!-- import foo.xsd which defines BarType-->
    <xsd:import namespace="http://foo" schemaLocation="http://localhost/foo.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="MyMessage">
    <wsdl:part name="bar" type="foo:BarType"/>
    </wsdl:message>
    I keep getting the error :
    Validating foo.wsdl
    Schema type not found: QName(http://foo, BarType)
    Validate WSDL: has errors.If I paste the content of foo.xsd inline in the wsdl file, it works ok.
    The wsdl file validates in XMLSpy; it can even successfully generate SOAP requests from it.
    Am I wrong somewhere ?
    Did anyone succeed in importing an external schema inside a wsdl file with JDev ?
    thx.

    Does anyone know if this is working in JDeveloper 10.1.3?
    Another (relared) question: we use multiple wsdl files to define our web services (according to the Venetian Blind design). Since the project uses WebLogic as AS we used their mechanism to generate the webservice. The only thing is that generating a stub via WebLogic JAX-RPC fails due to namespace errors.
    When I try to generate a stub based on the JDeveloper 10.1.3 wizards using the top-level wsdl (the one importing other wsdl's) I get an invalid wsdl message and the options in the wizard are disabled. Anyone know whether multiple wsdl's are supported in JDeveloper 10.1.3?
    Ronald

  • ESB & BPEL Schema importing problem

    All,
    Currently we have a normalized message schema which is used across my ESB and BPEL projects. The problem is whenever we have a change in schema mapping the entire translation had to be reworked in ESB and in the case of BPEL all the xpath mapping s gets altered. Please let me know what is the best practice of having the schema imported in ESB & BPEL which solves the problem.
    Regards,
    M.Rajesh

    Siva,
    We do accept there cannot be a system which has a varying I/P & O/P during desin time. Our area of concern is whenever a schema changes happen the entire design time gets affected. How can we minimize the amount of changes required of mapping the schema when a change occur?
    Regards,
    M.Rajesh

  • Unable to access objects in my own schema -- imported from SQL Server

    Hi All,
    I have imported some tables from MS SQL SERVER 2005 to Oracle 9i (9.2.0.1.0) on Windows machine.
    When I fire the query like "SELECT * FROM TAB", I can see the list of all those tables that I have imported, but the problem is that if I try to fetch the data from a specific table, the error is shown as "TABLE OR VIEW DOES NOT EXISTS".
    Can you please suggest me some work around to get the data from the tables?
    Thanks in advance
    Himanshu

    Replied in your Re: Unable to access objects in my own schema -- imported from SQL Server.
    Yoann.

  • Lax validation errors on schema import ('version' exceeds maximum length)

    I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
    Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
    I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
    Cheers,
    Daniel
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
         <xs:element name="edit">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="edit_id" type="xs:string"/>
                        <xs:element ref="br:business_rule"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="derivation">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="derivation_id" type="xs:string"/>
                        <xs:element ref="br:derivation_type"/>
                        <xs:element ref="br:business_rule"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="derivation_type">
              <xs:simpleType>
                   <xs:restriction base="xs:NMTOKENS">
                        <xs:enumeration value="complex"/>
                        <xs:enumeration value="format"/>
                        <xs:enumeration value="formula"/>
                        <xs:enumeration value="recode"/>
                        <xs:enumeration value="SAS code"/>
                        <xs:enumeration value="transfer"/>
                        <xs:enumeration value="count"/>
                        <xs:enumeration value="sum"/>
                        <xs:enumeration value="max"/>
                        <xs:enumeration value="min"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="business_rule"></xs:element>
    </xs:schema>

    Opps -- Sorry it's a decision we took when looking at Version
    When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
    SQL> desc xdb.xdb$schema_T
    Name                                      Null?    Type
    SCHEMA_URL                                         VARCHAR2(700)
    TARGET_NAMESPACE                                   VARCHAR2(2000)
    VERSION                                            VARCHAR2(12)
    NUM_PROPS                                          NUMBER(38)
    FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
    BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
    ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
    ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
    ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
    SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
    COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
    ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
    IMPORTS                                            XDB.XDB$IMPORT_LIST_T
    INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
    FLAGS                                              RAW(4)
    SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
    ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
    MAP_TO_NCHAR                                       RAW(1)
    MAP_TO_LOB                                         RAW(1)
    GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
    ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
    ID                                                 VARCHAR2(256)
    VARRAY_AS_TAB                                      RAW(1)
    SCHEMA_OWNER                                       VARCHAR2(30)
    NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
    LANG                                               VARCHAR2(4000)
    SQL>

  • Xsl schema import from within a wsdl file

    I have a namespace conflict issue validating a bpel process.
    The message error is as follow:
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
    // Here the BPEL file (SMSMulticast2.bpel)
    <pre>
    <!-- SMSMulticast2 BPEL Process [Generated by the Oracle BPEL Designer] -->
    <process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
         <!-- ================================================================= -->
         <!-- PARTNERLINKS -->
         <!-- List of services participating in this BPEL process -->
         <!-- ================================================================= -->
         <partnerLinks>
              <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
              <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
              <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
              <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
         </partnerLinks>
         <!-- ================================================================= -->
         <!-- VARIABLES -->
         <!-- List of messages and XML documents used within this BPEL process -->
         <!-- ================================================================= -->
         <variables>
              <!-- Reference to the message passed as input during initiation -->
              <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
              <!-- Reference to the message that will be sent back to the
    requester during callback
    -->
              <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
              <variable name="count" type="xsd:integer"/>
              <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
              <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
              <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
              <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
         </variables>
         <!-- ================================================================= -->
         <!-- ORCHESTRATION LOGIC -->
         <!-- Set of activities coordinating the flow of messages across the -->
         <!-- services integrated within this business process -->
         <!-- ================================================================= -->
         <sequence name="main">
              <!-- Receive input from requestor.
    Note: This maps to operation defined in SMSMulticast2.wsdl
    -->
              <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
              <!-- Asynchronous callback to the requester.
    Note: the callback location and correlation id is transparently handled
    using WS-addressing.
    -->
              <assign name="setProperties">
                   <copy>
                        <from expression="5"></from>
                        <to variable="count"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
                   </copy>
              </assign>
              <while name="foreach" condition="bpws:getVariableData('count') &gt; 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                        <assign name="decrease"><copy>
                                  <from expression="bpws:getVariableData('count') - 1"></from>
                                  <to variable="count"/>
                             </copy>
                        </assign>
                   </sequence>
              </while>
              <!--invoke name="callbackClient" partnerLink="client" portType="tns:SMSMulticast2Callback" operation="onResult" inputVariable="output"/-->
              <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
         </sequence>
    </process>
    // Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
         name="SMSSenderEnablerSEI"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
         <xsd:schema
              elementFormDefault="qualified"
              targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
              xmlns="http://www.w3.org/2001/XMLSchema"
              xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
              <xsd:complexType name="InvocationContext">
              <xsd:sequence>
              <xsd:element
              maxOccurs="unbounded"
              name="properties"
              nillable="true"
              type="xsd:string"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:complexType name="EnablerException">
              <xsd:sequence>
              <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
              <xsd:element name="errorCode" type="xsd:int"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
              </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
    <xsd:element name="sendSMS">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotification">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element
    name="sendSMSWithNotificationToAliasReturn"
    nillable="true"
    type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
                   <xsd:complexType name="SMSMessageETO">
    <xsd:sequence>
    <xsd:element name="content" nillable="true" type="xsd:string"/>
    <xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="priority" nillable="true" type="xsd:string"/>
    <xsd:element name="recipient" nillable="true" type="xsd:string"/>
    <xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
    <xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
    <xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
    <xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <xsd:complexType name="SMSException">
    <xsd:sequence>
    <xsd:element name="errorCode" type="xsd:int"/>
    <xsd:element name="message" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="sendSMSRequest">
    <wsdl:part element="impl:sendSMS" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasResponse">
    <wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="EnablerException">
    <wsdl:part element="tns2:EnablerException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasRequest">
    <wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasRequest">
    <wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasResponse">
    <wsdl:part
    element="impl:sendSMSWithNotificationToAliasResponse"
    name="parameters"/>
    </wsdl:message>
    <wsdl:message name="SMSException">
    <wsdl:part element="tns4:SMSException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationResponse">
    <wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationRequest">
    <wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSResponse">
    <wsdl:part element="impl:sendSMSResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="SMSSenderEnablerRemote">
    <wsdl:operation name="sendSMS">
    <wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
    <wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdl:input
    message="impl:sendSMSWithNotificationRequest"
    name="sendSMSWithNotificationRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationResponse"
    name="sendSMSWithNotificationResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSToAliasResponse"
    name="sendSMSToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdl:input
    message="impl:sendSMSWithNotificationToAliasRequest"
    name="sendSMSWithNotificationToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationToAliasResponse"
    name="sendSMSWithNotificationToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding
    name="SMSSenderEnablerRemoteSoapBinding"
    type="impl:SMSSenderEnablerRemote">
    <wsdlsoap:binding
    style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendSMS">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="SMSSenderEnablerRemoteService">
    <wsdl:port
    binding="impl:SMSSenderEnablerRemoteSoapBinding"
    name="SMSSenderEnablerRemote">
    <wsdlsoap:address
    location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
    </wsdl:port>
    </wsdl:service>
    <plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
    <plnk:role name="SMSSenderEnablerRemoteProvider">
    <plnk:portType name="impl:SMSSenderEnablerRemote"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </wsdl:definitions>
    Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
    Many Thanks
    Guillaume

    You need to use the XSLT before you do assignment to achieve this, to
    change the message to the correct namespace.
    Please refer to sample at
    "orabpel\samples\tutorials\114.XSLTTransformations" which talks about
    how to use XSLT transformation.
    And please refer to
    "orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
    especially "InvToPo.xslt" which talks about doing transformations
    between 2 structures pointing to different namespaces.

  • Presentation Director automated scheme import

    Hi All,
    hope everyone is well.
    Does anyone know if its possible to somehow import Presentation Director schemes from the command line or if there is any other way to do it?
    I wanted to create a single scheme on one of my test machines, export it and then create a package which can then be run on users machines which will import it.
    I hope someone can give me a little advice here. I have been looking up this topic on Google but I did not manage to find anything.
    Thanks a lot.
    Stu.
    Solved!
    Go to Solution.

    Hi,
    thanks very much for your reply, unfortunately that did not work for me :-(
    But I did manage to find another solution, if you export the relevant registry scheme from here: HKEY_CURRENT_USER\Software\Lenovo\NPdirect\Data\Common\Presentation Schemes\
    You can easily import it on other machines. Hope that will help other people who need to so the same steps.
    Thanks.

  • Problem in Schemas import from one database to another

    Hi,
    I have to import the schemas from one database (10g release 1) to another database (10g release 1).
    But the problem is that through simple import (imp) the system privileges, object privileges & other things are not importing to import file. There are various objects in the schemas which are inter-related & I can't manually grant on those objects.
    I have also tried Toad Export DDL Script. But my problem is not solve through the Toad. There are other various issues occuring with TOAD.
    I have also tried SQL Developer & PL/SQL Developer but CLOB problem is occuring with them.
    The schemas which I have been creating in different database is new schemas with same name.
    AB
    Edited by: adhondiyal on Dec 26, 2010 8:55 AM

    adhondiyal wrote:
    Hi,
    I have to import the schemas from one database (10g release 1) to another database (10g release 1).
    But the problem is that through simple import (imp) the system privileges, object privileges & other things are not importing to import file. There are various objects in the schemas which are inter-related & I can't manually grant on those objects.
    I have also tried Toad Export DDL Script. But my problem is not solve through the Toad. There are other various issues occuring with TOAD.
    I have also tried SQL Developer & PL/SQL Developer but CLOB problem is occuring with them.
    ABWhy can't you use EXPDP/IMPDP
    have you given grants=y ?
    mp system/***** file=schema.dmp log=schema.log fromuser=user1 touser=user2 grants=yis the usernames of source & dest are same?
    use as if schema name is same
    expdp system/**** directory=DATA_PUMP_DIR dumpfile=schema.dmp logfile=schema.log schemas=users
    impdp system/**** dumpfile=schema.dmp logfile=schema1.log
    if schema name is different then
    expdp system/**** directory=DATA_PUMP_DIR dumpfile=schema.dmp logfile=schema.log schemas=users
    impdp system/**** dumpfile=schema.dmp logfile=schema1.log remap_schema=(source:dest)
    Thanks

  • Physical Schema Import

    Hi i have a problem
    I have 2 schemas a and b ... I am logging in with a main_user that can see both schemas..
    I can import them fine using import - Then choose schema(s) and import..
    But when i row count its like it cant see the schemas... If i create a synonym for tables within schemas under the main_user its fine.. But i dont know why it cant make out that the tables are within schemas... so a.table_1 b.table_1 etc....
    I can see 2 physical schemas in the physical layer...
    thanks
    Edited by: 791465 on 24-Sep-2010 03:07

    2 Database Schemas A, B
    I have a Main_user that can see both database Schemas A & B
    I can import them Fine into The physical layer with 1 Connection Pool. I can see 2 Schemas.
    When i do a Row Count i get a Cant View Table errors for both Schemas..
    However if i create a synonym for tables under under the Main_user they row count fine (No Schema Prefix such as A.table1 etc.
    Why cant OBIEE in the physical layer recognise the Schema prefix before the table...
    Edited by: 791465 on 24-Sep-2010 03:13

  • To import oracle.xdb.XMLTYPE;

    Hi,
    Which library I must import in order to use oracle.xdb.XMLTYPE?

    ORA_HOME\rdbms\jlib\xdb.jar

  • EUL_US Schema Import

    my client got separated from its Parent company,
    now we in the process of setting up the Discoverer for my client, Actually my client's Parent company just gave us the EUL_US schema dump, we have created the EUL_US schema in our DB and Imported the dump,every thing is fine untill there. Now as we have the EUL_US schema, when connected to discoverer admin and we are able to see all the client related BA's, folders itemclass etc.... but we don't have the workbooks..!!
    if they would have given us the whole EUL export(.eex), then it would have been a straight forward task, we would have imported every thing including workbooks, but here we received just the EUL_US Schema Dump.(because of some client restrictions, parent company is not giving us complete EUL export)
    now if i query EUL5_QPP_STATS, EUL5_documents i can see all the report name and details associated with it. but we don't have the real workbooks to run.
    now my question is
    *1. Is there a way to bring/create/import all the workbook from the limited source (EUL_US schema) that we have.*
    i know this sounds like a crazy questions because EUL tables just store's workbook information like name,identifier,creator etc.. but i was just trying to find if there is any possibility to get these workbooks from the schema we have. (if noting works we have to create all the workbooks manually)

    Hi,
    Assuming you have an apps mode EUL, then you could share all workbooks with the APPS_USER using the following SQL:
    insert into EUL_US.eul5_access_privs
    (AP_ID,
      AP_TYPE,
      AP_EU_ID,
      AP_PRIV_LEVEL,
      GP_APP_ID,
      GBA_BA_ID,
      GD_DOC_ID,
      AP_ELEMENT_STATE,
      AP_CREATED_BY,
      AP_CREATED_DATE,
      AP_UPDATED_BY,
      AP_UPDATED_DATE,
      NOTM)
    select EUL_US.EUL5_ID_SEQ.nextval, 'GD', EU.EU_ID, 0, NULL, NULL, ED.DOC_ID, 0,
         'EUL_US', SYSDATE, 'EUL_US', SYSDATE, 0
    from (select doc_id
          from EUL_US.eul5_documents
       minus
       select gd_doc_id doc_id
       from EUL_US.eul5_access_privs
       where ap_eu_id =
             (select eu2.EU_ID
              from EUL_US.eul5_eul_users eu2
                 , APPLSYS.fnd_user fu
               where fu.USER_NAME = '&APPS_USER'
               and eu2.eu_username = '#'||fu.user_id and eu2.eu_security_model = 1
         ) ED,
       EUL_US.eul5_eul_users EU
    , APPLSYS.fnd_user fu
    where fu.USER_NAME = '&APPS_USER'
    and eu.eu_username = '#'||fu.user_id and eu.eu_security_model = 1Rod West

  • Schema importing less objects

    hi,
    I exported one schema from 10.2.0 with object 3120 using expdp and imported in oracle 11.2.0. but it is importing only 1080 objects. there is no invalid objects from two sides. what could be the problem. Please let me know..
    thank you

    Can you please check with this once:
    SOURCE:
    OBJECT_TYPE COUNT(*)
    INDEX 574
    TABLE 1683
    TRIGGER 16
    VIEW 1129
    PACKAGE BODY 1
    PACKAGE 11
    SEQUENCE 21
    expdp dumpfile=EXPDP_SCHEMA1.dmp logfile=EXPDP_SCHEMA1.log schemas=SCHEMA1
    Export: Release 10.2.0.1.0 - 64bit Production on Tuesday, 27 March, 2012 19:18:34
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Username: / as sysdba
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Starting "SYS"."SYS_EXPORT_SCHEMA_01": /******** AS SYSDBA dumpfile=EXPDP_SCHEMA1.dmp logfile=EXPDP_SCHEMA1.log schemas=SCHEMA1
    Estimate in progress using BLOCKS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    Total estimation using BLOCKS method: 803.1 MB
    Processing object type SCHEMA_EXPORT/USER
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
    Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
    Processing object type SCHEMA_EXPORT/VIEW/VIEW
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
    Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Processing object type SCHEMA_EXPORT/JOB
    . . exported "ADMGVDOMT1"."DM_UPDATE_STATS_COMMANDS" 148.9 MB 2802240 rows
    . . exported "ADMGVDOMT1"."DM_AUDITTRAIL_S" 166.8 MB 393826 rows
    . . exported "ADMGVDOMT1"."RETENTION_EXCEPTION_S" 0 KB 0 rows
    . . exported "ADMGVDOMT1"."TRAINING_RECORD_R" 0 KB 0 rows
    . . exported "ADMGVDOMT1"."TRAINING_RECORD_S" 0 KB 0 rows
    Master table "SYS"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
    Dump file set for SYS.SYS_EXPORT_SCHEMA_01 is:
    /software/oracle/app/oracle/admin/GVTDOMA/dpdump/EXPDP_SCHEMA1.dmp
    Job "SYS"."SYS_EXPORT_SCHEMA_01" successfully completed at 19:19:55
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Master table "SYS"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYS"."SYS_IMPORT_FULL_01": /******** AS SYSDBA dumpfile=EXPDP_SCHEMA1.dmp logfile=EXPDP_SCHEMA1.log remap_schema=SCHEMA1:SCHEMA1
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"ADMGVDOMT1" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    . . imported "ADMGVDOMT1"."DM_UPDATE_STATS_COMMANDS" 148.9 MB 2802240 rows
    . . imported "ADMGVDOMT1"."DM_AUDITTRAIL_S" 166.8 MB 393826 rows
    . . imported "ADMGVDOMT1"."DMI_QUEUE_ITEM_S" 85.33 MB 301132 rows
    . . imported "ADMGVDOMT1"."DMI_DD_COMMON_INFO_R" 28.86 MB 837596 rows
    . . imported "ADMGVDOMT1"."DMI_DD_ATTR_INFO_R" 22.29 MB 769740 rows
    . . imported "ADMGVDOMT1"."DMR_CONTENT_S" 4.157 MB 20791 rows
    . imported "ADMGVDOMT1"."RETENTION_EXCEPTION_S" 0 KB 0 rows
    . . imported "ADMGVDOMT1"."TRAINING_RECORD_R" 0 KB 0 rows
    . . imported "ADMGVDOMT1"."TRAINING_RECORD_S" 0 KB 0 rows
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
    Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
    Processing object type SCHEMA_EXPORT/VIEW/VIEW
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
    Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Processing object type SCHEMA_EXPORT/JOB
    Job "SYS"."SYS_IMPORT_FULL_01" completed with 1 error(s) at 19:35:49
    OBJECT_TYPE COUNT(*)
    INDEX 518
    VIEW 1129
    TRIGGER 4
    TABLE 424
    PACKAGE BODY 1
    PACKAGE 11
    SEQUENCE 21
    7 rows selected.

Maybe you are looking for

  • I can t install ios 6.1.3 on my iphone 4s

    i can t install ios 6.1.3 on my iphone 4s

  • Compound clip re-rendering

    Is it just me or are compound clips the very devil when it comes to rendering? You put a bunch of clips together in a compound clip for convenience, then maybe you need to go in there and edit an effect on one of the internal clips.  Bam, the entire

  • Cannot Empty the Trash

    Hi all, I had updated the OS to Leopard last week. After updated, the Trash cannot empty and hold on at emptying status for a very very long time. I need to relaunch the program and all the file still in the Trash. How to fix my problem? Thanks a lot

  • Bridge CS4 desaturating thumbnails

    Approximately 1 second or less after opening Bridge CS4 it slightly desaturates the colours of the thumbnails - this is especially noticeable with greens. When any image is then opened in PsCS4 it contimues to display the desaturated colours. I have

  • Runtime acces to Group Supress Formula

    Hello, I'm using Crystal Reports 2008. I want to remove a supress formula in runtime from a given group/section. I can only access to a readonly object (ReportDefController) where these formula is defined. Dim objGroupSection As CrystalDecisions.Repo