OMB02904 Namespace Conflict Creating Mapping

Hi, we are running OWB 11GR2 on Windows and I am having trouble creating a mapping as allegedly it already exists. I can find no trace of this either through the GUI, through OMBPlus, or even using the JAVA APIs to find the offending mapping. It is also not visible in owbsys.all_iv_xform_maps or owbsys.all_iv_objects.
I cannot OMBDROP the mapping as it does not exist !
The full message in OMBPLUS is OMB02904 Namespace Conflict for map name WORK_SELF_EMPLOYED_INCOM_TA1M1: API0408 Within same namespace domain one object has already used the name WORK_SELF_EMPLOYED_INCOM_TA1M1
If you have any suggestions they would be gratefully received !
Phil

Our repository DB uses a Windows character set WE8MSWIN1252.
I have done a trawl through mappings and tables through all our Modules in a couple of ways (note my OMBPlus may not be the best you have ever seen). Note that these code snippets do work with 'real' mappings, but they do not find my phantom mapping.
set objectToFind WORK_SELF_EMPLOYED_INCOM.*
OMBCC '/IDP'
set moduleList [OMBLIST MODULES]
#set moduleList [list IPS2_SA1]
foreach moduleName $moduleList {
puts "Module name = $moduleName"
OMBCC '/IDP/$moduleName'
set tableList [OMBLIST TABLES '$objectToFind']
foreach tableName $tableList {
puts "=== Found table $moduleName/$tableName"
set mapList [OMBLIST MAPPINGS '$objectToFind']
foreach mapName $mapList {
puts "=== Found mapping $moduleName/$mapName"
============================================
Java API based search
set mapToFind WORK_SELF_EMPLOYED_INCOM_TA1M1
set repManager [java::call oracle.owb.connection.RepositoryManager getInstance]
set owbConnection [$repManager getConnection]
set projectManager [java::call oracle.owb.project.ProjectManager getInstance]
set project [$projectManager getWorkingProject]
# for every module
set modList [$project getOracleModuleNames]
set modCnt [$modList length]
for {set ic1 0} {$ic1 < $modCnt} {incr ic1} {
# Find your Oracle module
set modName [$modList get $ic1]
set modObj [$project findOracleModule $modName]
if {("$modName" != "RELEASES") && ("$modName" != "ARCHIVE")} {
# Proc logit defined earlier to output to a file
logit "Processing module $projName/$modName"
set mapList [$modObj getMapNames ]
set mapCnt [$mapList length]
for {set ic2 0} {$ic2 < $mapCnt} {incr ic2} {
set mapName [$mapList get $ic2]
if { "$mapName" == "$mapToFind" } {
logit "======= Found the bugger $mapName"
===============================
Nothing here either ....
SELECT *
FROM owbsys.all_iv_xform_maps
WHERE business_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';
SELECT *
FROM owbsys.all_iv_objects
WHERE object_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';

Similar Messages

  • OMB02904: Namespace conflict for map name

    Hello all,
    I was running an OMB script which was to create the several Mappings, and after the creation of all the mappings it was supposed to commit. This script was being run in UNIX env, but unfortunately the UNIX session got killed and script terminated, persumably before commit, because I do not see any of the mappings in OWB.
    So I started the script again but got this message,
    OMB02904: Namespace conflict for map name MAP_1: PRS-00303: Name <MAP_1> Already reserved under your user name. with
    oracle session ID: 31
    I cleaned up the oracle sessions in Design Rep, but still getting the same error message both at command line and in GUI.
    Has anyone else in the forum experienced similar problem. Any suggestions or pointer on How to fix thi will be appreciated.
    TIA

    It seems that the mapping got created. Have you tried to refresh the OWB client to see the mapping by clicking on the "Synchronize this view with the repository" button (second icon from the left just under the "Project" menu entry)? If this is true, you will either have to delete the existing mapping and commit, or rename your mapping.
    Regards:
    Igor

  • How to create Map report?

    Hello experts.
    I'd like to know how map report works in OBIEE 11G..
    Upon researching and trials, I have successfully downloaded and loaded the MVdemo stuff into my DB. I am able to import layers and back ground map into OBIEE. So at this point, I think I have set up the map metadata successfullly and I am able to use map as one of the view.
    However, I'd like to know how to actually use the map view to create reports that are meaningful with my data..
    I have 1 table, base table, where I have base name, attribute 1...10, latitude and longitude. I also have some fact tables that goes with this table.
    It seems, as I was going through the MVdemo metadata, the cities table doesn't store all of the cities in the world (this is understandable), so the part of Russia where my bases are located aren't found in the spatial data.
    My base table only has latitude and longitude, it doesn't have geographic region names.
    Now I want to create one report that shows all of my bases over east part of Russia on a map, so I want to see a map of Russia with Base names plot all over it.
    How would I be able to do it? Do I need additional tables or data to do it?
    The examples I get from internet seems to be too generic
    Please let me know your thoughts
    Thanks

    Hello
    I like this article:
    http://prasadmadhasi.com/tag/obiee-11g-maps/
    However, I have a few beginner's question..
    1. I notice that the author has a subject area 'Map', which was used to create map.. Is this subject area any different from normal subject or is it created specifically for making maps?
    2. The author has state, city columns in the DB, which was used to map to the report.. In my case, I only have longitude and altitude of my base in the base table, what can I do in this case?
    Thanks

  • How to create/Map a User as Adminstrator in BPM Worklist to view all tasks

    Hi all,
    How to create/Map a User as Adminstrator in BPM Worklist to view all the tasks.
    Version :Jdev 11.1.1.1.0
    Regards
    C.Karukkuvel

    go to EM , right click on soa-infra -> security -> Applicaiton roles, then click on BPMWorkflowAdmin role. Add your user to this role.
    This user will be able to view all tasks in Worklist. you have to click on "Administration Tasks" tab.
    Thanks
    --Sreeny
    Edited by: sreeny on Sep 22, 2010 12:54 PM

  • How to create/Map a User as Adminstrator in BPM Worklist to view all the ta

    Hi all,
    How to create/Map a User as Adminstrator in BPM Worklist to view all the tasks.
    Version :Jdev 11.1.1.1.0
    Regards
    C.Karukkuvel

    Sounds like a great question for the [url http://forums.oracle.com/forums/forum.jspa?forumID=560]BPM Suite Forum, but then again, I see you've already posted the question there ;)
    Good luck,
    John

  • Unexpected namespace change after mapping change

    Unexpected namespace change after mapping change
    Posted: Apr 18, 2006 5:17 AM    Reply 
    Hi all
    We developped a mapping about one year ago on XI SP9.
    The source of the message was an Idoc and the target an XML sample (and not a xsd!) of what our customer expected.
    Everything was working fine at that point.
    Here is an extract of the output we had:
    <?xml version="1.0" encoding="UTF-8" ?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header xmlns:p="http://localhost/webs/msgDetails.xsd">
    <p:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd">
    <p:sender>
    <p:senderId>XXX</p:senderId>
    <p:senderName>AUSTRALIA/NEW ZEALAND</p:senderName>
    </p:sender>
    We are now running SP14 and we had to change the mapping. Since we changed it the namespaces defined in the sample XML we use as a target structure are not used anymore, instead they are replaced by ns0, ns1...
    Now the output looks like this:
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns0:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" ns1:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
    <ns0:Header>
    <ns2:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd" xmlns:ns2="http://localhost/webs/msgDetails.xsd">
    <ns2:sender>
    <ns2:senderId>21873</ns2:senderId>
    <ns2:senderName>XXX</ns2:senderName>
    </ns2:sender>
    Any idea what has happened here?
    Thanks in advance
    Gregory

    Hi Gregory,
    after a short view I would say that the two structures you have posted are logically equivalent.
    I try to make it clear for the sender-element.
    In the first example you have a tag <p:sender>. Obviously the namespace prefix 'p' is used here. In order to find out the qualified name of the element represented by that tag you have to find the namespace declaration for prefix p. As the tag itself does not contain such a declaration you have to go to the parent-tag. Indeed, here you find a declaration for p which says that p is just an alias for 'http://localhost/webs/msgDetails.xsd'. Hence the qualified name for the element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
    Now let us look at the corresponding tag <ns2:sender> in the second document. In oder to identify the qualified name of the element you have to find out, which namespace is bound to the namespace prefix ns2 which has been used here. Again you cannot find this in the tag itself but in its parent. Here you find that ns2 is bound to 'http://localhost/webs/msgDetails.xsd'. (Indeed, here you see that prefix p is also bound to that namespace. This seems to be superfluous to me, as the prefix is never used.)
    Consequently, the qualified name of that element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
    Thus, both tags represent elements with the same qualified name. For more details look at http://www.w3.org/TR/REC-xml-names/.
    Greetings Stephan

  • URGENT: How to create Map IDs

    I am using RH7, have inherited a help project in which all topics have been assigned map IDs. I have created several new topics (at the root level) and do not know how to create map IDs for the new topics. I need step-by-step help on how to create IDs without disrupting the current IDs.

    Thanks William. I'm all set now.
    Date: Tue, 18 Aug 2009 08:47:58 -0600
    From: [email protected]
    To: [email protected]
    Subject: URGENT: How to create Map IDs
    Hi,
    Start by reading the article on Peter's site: http://www.grainge.org/pages/authoring/calling_webhelp/using_map_ids.htm
    If you have any questions after that, just post back. You'll be able to make your question more specific.
    Greet,
    Willam
    >

  • Get Message ID and namespace from ABAP Mapping

    Hi XI Expert,
    Please advise how to get the message ID and namespace from ABAP Mapping.
    Thank You and best Regards
    Fernand

    Hi,
    To access the message ID, use the method GET_MESSAGE_ID of the controller object:
           1.      Fetch a protocol instance for the protocol IF_WSPROTOCOL_MESSAGE_ID.
           2.      To have the system return the message ID after the sender has sent a request message or the receiver has received a request message, use the method GET_MESSAGE_ID of this instance. This returns the ID by using the parameter MESSAGE_ID of type SXMSGUID.
    Also you could do the same by this way also:
    IF_WSPROTOCOL_XI_HEADER
    has attributes messageid and interface namespace.
    using this  you can read the XI message header

  • Create Mapping As a Flat File Source

    Hi,
    I'm new to OWB, my first project is to load data through flat file to oracle.
    step i follow is,
    =>Create Flat File Module
    =>Create Location Directory
    =>Create Flat File
    =>Create External Table (Synch with my Flat File)
    =>Create Mapping (Simple External Table mapped to table operator)
    =>Create and bind table Operator
    Mapping successfully deployed and but when i want to run it gives me following Error
    ORA-29913: error in executing ODCIEXTTABLEOPEN callout
    ORA-29400: data cartridge error
    KUP-04040: file IPDirectory.txt in FLAT_FILE_MOD_LOC_0 not found
    When I directly mapped flat file to Table in mapping it gives another error
    RPE-01013: SQL Loader reported error condition, number 4.
    SQL*Loader-522: lfiopn failed for file (\\sfs\Analytics\Reference\SIMPLE_MAP.log)
    I mention here that im working on my pc with OWB Client not on server and want to load data through flat file which is on my pc or on our sharing drive.
    Please help me on this issue
    Regards

    Hi,
    OWB generates SQL * Loader code for Flat File operator, if you try to change the configuration parameter to PL/SQL it results in error.
    External tables would be a better choice as it reduces the processing time, disk space required and also makes it possible to use SQL and other complex transformations.

  • Creating Map IDs using HTM File Name

    Is it possible to create Map IDs using the File name of the HTM, instead of its Topic Title?

    While Generating Map IDs, we get an ID along with a Map # for each HTM in the CSH.
    For Example, I have a HTM in my CSH with the following Details:
    Topic Title - Access Masks
    File Name - admpr00001.htm
    Now when I create a Map ID for this page. I can customise the Map ID by setting any/all of the three options: - 'Prefix Map IDs with', 'Make Uppercase' and 'Start Numbering with'. But the Map ID is generated only based on the Topic Title.
    Like - ebACCESS_MASKS 1000   where, eb is the set prefix.
    Is it possible for me to create a MAP ID using the File Name. In this case, as ebadmpr00001 1000?
    Hope I am clear .

  • DBMS_XMLSCHEMA.CopyEvolve produces ORA-30945: Could not create mapping tabl

    Hi,
    I am trying to update a XML Schema concerning the documents relaties.xsd (the old one) and relaties_v2.xsd (the new one containing only a minor change).
    The document relaties.xsd looks like this:
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xdb="http://xmlns.oracle.com/xdb"
    elementFormDefault="unqualified"
    attributeFormDefault="unqualified"
    version="1.0">
         <xsd:element name="Relatie" xdb:defaultTable="">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element name="Voornaam" type="xsd:string"/>
                        <xsd:element name="Achternaam" type="xsd:string"/>
                        <xsd:element name="Tussenvoegsel" type="xsd:string"/>
                        <xsd:element name="Geboortedatum" type="xsd:date"/>
                        <xsd:element name="Geslacht">
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="M"/>
    <xsd:enumeration value="V"/>
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
                        <xsd:element name="Sofinummer">
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:pattern value="\d{9}"/>
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
                        <xsd:element name="Straatnaam" type="xsd:string"/>
                        <xsd:element name="Huisnummer" type="xsd:string"/>
                        <xsd:element name="Woonplaats" type="xsd:string"/>
                        <!--xsd:element name="Postcode" type="xsd:string"/-->
                        <xsd:element name="Postcode">
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:pattern value="\d{4} [A-Z]{2}"/>
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
                        <xsd:element name="Zrn">
    <xsd:simpleType>
    <xsd:restriction base="xsd:integer">
    <xsd:minInclusive value="1000000"/>
    <xsd:maxInclusive value="99999999999999"/>
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
                   </xsd:sequence>
              </xsd:complexType>
         </xsd:element>
    </xsd:schema>
    Here are the steps I took.
    DECLARE
    res BOOLEAN;
    BEGIN
    res := DBMS_XDB.createResource('/xsd/relaties.xsd',
    bfilename('XSDDIR', 'relaties.xsd')
    END;
    DECLARE
    res BOOLEAN;
    BEGIN
    res := DBMS_XDB.createResource('/xsd/relaties_v2.xsd',
    bfilename('XSDDIR', 'relaties_v2.xsd')
    END;
    BEGIN
    DBMS_XMLSCHEMA.registerSchema(
    'http://localhost:8080/xsd/relaties.xsd',
    XDBURIType('/xsd/relaties.xsd').getClob(),
    TRUE,
    FALSE,
    FALSE,
    TRUE);
    END;
    CREATE
    TABLE relatie_documenten OF XMLTYPE
    XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
    ELEMENT "Relatie"
    CREATE OR REPLACE
    TRIGGER upo_rdt_ai
    AFTER INSERT ON relatie_documenten
    FOR EACH ROW
    DECLARE
    doc XMLType;
    BEGIN
    doc := :new.SYS_NC_ROWINFO$;
    XMLType.schemaValidate(doc);
    END;
    Then I inserted some xml documents into the table relatie_documenten. The XSD worked fine.
    Then I executed the following statement:
    BEGIN
    DBMS_XMLSCHEMA.copyEvolve
    ( schemaURLs => xdb$string_list_t('http://localhost:8080/xsd/relaties.xsd')
    , newSchemas => XMLSequenceType(XDBURIType('/xsd/relaties_v2.xsd').getXML())
    , preserveOldDocs => TRUE
    , mapTabName => 'RELATIE_DOCUMENTEN_TEMP'
    , generateTables => FALSE
    END;
    This resulted in:
    ERROR at line 1:
    ORA-30945: Could not create mapping table 'RELATIE_DOCUMENTEN_TEMP'
    ORA-00600: internal error code, arguments: [kqludp2], [0x66AB407C], [0], [],
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 113
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 210
    ORA-06512: at line 2
    I checked system priviliges as documented in XML DB Developers Guide, Chapter 8 XML Schema Evolution. No other users were connected. The mapping table RELATIE_DOCUMENTEN_TEMP nor any other object named RELATIE_DOCUMENTEN_TEMP did not exist.
    Anyone an idea why I cannot create my mapping table ?
    Gregor

    Which release / platform are you working with
    With 10.2.0.2.1 on Widows I get
    SQL> var schemaURL varchar2(256)
    SQL> var schemaPath varchar2(256)
    SQL> --
    SQL> begin
      2    :schemaURL := 'http://localhost:8080/xsd/relaties.xsd';
      3    :schemaPath := '/public/relaties.xsd';
      4  end;
      5  /
    PL/SQL procedure successfully completed.
    SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
      2  /
    Call completed.
    SQL> declare
      2    res boolean;
      3    xmlSchema xmlType := xmlType(
      4  '<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      5              xmlns:xdb="http://xmlns.oracle.com/xdb"
      6                 elementFormDefault="unqualified"
      7                 attributeFormDefault="unqualified"
      8                 version="1.0">
      9     <xsd:element name="Relatie" xdb:defaultTable="">
    10             <xsd:complexType>
    11                     <xsd:sequence>
    12                             <xsd:element name="Voornaam" type="xsd:string"/>
    13                             <xsd:element name="Achternaam" type="xsd:string"/>
    14                             <xsd:element name="Tussenvoegsel" type="xsd:string"/>
    15                             <xsd:element name="Geboortedatum" type="xsd:date"/>
    16                             <xsd:element name="Geslacht">
    17                 <xsd:simpleType>
    18                    <xsd:restriction base="xsd:string">
    19                       <xsd:enumeration value="M"/>
    20                       <xsd:enumeration value="V"/>
    21                    </xsd:restriction>
    22                 </xsd:simpleType>
    23              </xsd:element>
    24                     <xsd:element name="Sofinummer">
    25                 <xsd:simpleType>
    26                    <xsd:restriction base="xsd:string">
    27                       <xsd:pattern value="\d{9}"/>
    28                    </xsd:restriction>
    29                 </xsd:simpleType>
    30              </xsd:element>
    31                             <xsd:element name="Straatnaam" type="xsd:string"/>
    32                             <xsd:element name="Huisnummer" type="xsd:string"/>
    33                             <xsd:element name="Woonplaats" type="xsd:string"/>
    34                             <!--xsd:element name="Postcode" type="xsd:string"/-->
    35                             <xsd:element name="Postcode">
    36                 <xsd:simpleType>
    37                    <xsd:restriction base="xsd:string">
    38                       <xsd:pattern value="\d{4} [A-Z]{2}"/>
    39                    </xsd:restriction>
    40                 </xsd:simpleType>
    41              </xsd:element>
    42                             <xsd:element name="Zrn">
    43                 <xsd:simpleType>
    44                    <xsd:restriction base="xsd:integer">
    45                       <xsd:minInclusive value="1000000"/>
    46                       <xsd:maxInclusive value="99999999999999"/>
    47                    </xsd:restriction>
    48                 </xsd:simpleType>
    49              </xsd:element>
    50                     </xsd:sequence>
    51             </xsd:complexType>
    52     </xsd:element>
    53  </xsd:schema>');
    54  begin
    55    if (dbms_xdb.existsResource(:schemaPath)) then
    56      dbms_xdb.deleteResource(:schemaPath);
    57    end if;
    58    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    59  end;
    60  /
    PL/SQL procedure successfully completed.
    SQL> BEGIN
      2    DBMS_XMLSCHEMA.registerSchema(
      3      :schemaURL,
      4      XDBURIType(:schemaPath).getClob(),
      5      TRUE,
      6      FALSE,
      7      FALSE,
      8      TRUE);
      9  END;
    10  /
    PL/SQL procedure successfully completed.
    SQL> DROP TABLE relatie_documenten FORCE
      2  /
    Table dropped.
    SQL> CREATE TABLE relatie_documenten OF XMLTYPE
      2         XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
      3         ELEMENT "Relatie"
      4  /
    Table created.
    SQL> CREATE OR REPLACE TRIGGER upo_rdt_ai
      2  AFTER INSERT ON relatie_documenten
      3  FOR EACH ROW
      4  DECLARE
      5     doc XMLType;
      6  BEGIN
      7     doc := :new.SYS_NC_ROWINFO$;
      8     XMLType.schemaValidate(doc);
      9  END;
    10  /
    Trigger created.
    SQL> INSERT
      2  INTO   relatie_documenten
      3  VALUES (XMLType
      4           ('<Relatie>
      5                <Voornaam>Johan</Voornaam>
      6                <Achternaam>Hermans</Achternaam>
      7                <Tussenvoegsel/>
      8                <Geboortedatum>1978-01-02</Geboortedatum>
      9                <Geslacht>M</Geslacht>
    10                <Sofinummer>233300417</Sofinummer>
    11                <Straatnaam>Stationstraat</Straatnaam>
    12                <Huisnummer>10</Huisnummer>
    13                <Woonplaats>Weesp</Woonplaats>
    14                <Postcode>1383 AK</Postcode>
    15                <Zrn>1234567</Zrn>
    16             </Relatie>'
    17          ).CreateSchemaBasedXML(:schemaURL))
    18  /
    1 row created.
    SQL> commit
      2  /
    Commit complete.
    SQL> INSERT
      2  INTO   relatie_documenten
      3  VALUES (XMLType
      4           ('<Relatie>
      5                <Voornaam>Johanna</Voornaam>
      6                <Achternaam>Gurts</Achternaam>
      7                <Tussenvoegsel/>
      8                <Geboortedatum>1975-11-12</Geboortedatum>
      9                <Geslacht>V</Geslacht>
    10                <Sofinummer>234109807</Sofinummer>
    11                <Straatnaam>Stationstraat</Straatnaam>
    12                <Huisnummer>10</Huisnummer>
    13                <Woonplaats>Weesp</Woonplaats>
    14                <Postcode>1383 AK</Postcode>
    15                <Zrn>7654321</Zrn>
    16             </Relatie>').CreateSchemaBasedXML(:schemaURL))
    17  /
    1 row created.
    SQL> commit
      2  /
    Commit complete.
    SQL> INSERT
      2  INTO   relatie_documenten
      3  VALUES (XMLType
      4           ('<Relatie>
      5                <Voornaam>Johanna</Voornaam>
      6                <Achternaam>Gurts</Achternaam>
      7                <Tussenvoegsel/>
      8                <Geboortedatum>1975-11-12</Geboortedatum>
      9                <Geslacht>O</Geslacht>
    10                <Sofinummer>234109807</Sofinummer>
    11                <Straatnaam>Stationstraat</Straatnaam>
    12                <Huisnummer>10</Huisnummer>
    13                <Woonplaats>Weesp</Woonplaats>
    14                <Postcode>1383 AK</Postcode>
    15                <Zrn>7654321</Zrn>
    16             </Relatie>').CreateSchemaBasedXML(:schemaURL))
    17  /
    VALUES (XMLType
    ERROR at line 3:
    ORA-31038: Invalid enumeration value: "O"
    ORA-06512: at "SYS.XMLTYPE", line 345
    ORA-06512: at "SCOTT.UPO_RDT_AI", line 5
    ORA-04088: error during execution of trigger 'SCOTT.UPO_RDT_AI'
    SQL> commit
      2  /
    Commit complete.
    SQL> declare
      2    xmlschema xmltype;
      3    res       boolean;
      4  begin
      5    select xdburitype(:schemaPath).getXML()
      6      into xmlSchema
      7      from dual;
      8    dbms_xdb.deleteResource(:schemaPath);
      9    select insertChildXML
    10           (
    11             xmlschema,
    12             '/xsd:schema//xsd:element[@name="Geslacht"]/xsd:simpleType/xsd:restriction',
    13             'xsd:enumeration',
    14             xmltype('<xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>'),
    15             'xmlns:xsd="http://www.w3.org/2001/XMLSchema"'
    16           )
    17    into xmlSchema
    18    from dual;
    19    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    20  end;
    21  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> set long 100000 pages 200 lines 140
    SQL> --
    SQL> select xdburitype(:schemaPath).getXML()
      2    from dual
      3  /
    XDBURITYPE(:SCHEMAPATH).GETXML()
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="unqualified" attributeF
    ormDefault="unqualified" version="1.0">
      <xsd:element name="Relatie" xdb:defaultTable="">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Voornaam" type="xsd:string"/>
            <xsd:element name="Achternaam" type="xsd:string"/>
            <xsd:element name="Tussenvoegsel" type="xsd:string"/>
            <xsd:element name="Geboortedatum" type="xsd:date"/>
            <xsd:element name="Geslacht">
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:enumeration value="M"/>
                  <xsd:enumeration value="V"/>
                  <xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
            <xsd:element name="Sofinummer">
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:pattern value="\d{9}"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
            <xsd:element name="Straatnaam" type="xsd:string"/>
            <xsd:element name="Huisnummer" type="xsd:string"/>
            <xsd:element name="Woonplaats" type="xsd:string"/>
            <!--xsd:element name="Postcode" type="xsd:string"/-->
            <xsd:element name="Postcode">
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:pattern value="\d{4} [A-Z]{2}"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
            <xsd:element name="Zrn">
              <xsd:simpleType>
                <xsd:restriction base="xsd:integer">
                  <xsd:minInclusive value="1000000"/>
                  <xsd:maxInclusive value="99999999999999"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:schema>
    SQL> DROP TABLE RELATIE_DOCUMENTEN_TEMP
      2  /
    Table dropped.
    SQL> BEGIN
      2    DBMS_XMLSCHEMA.copyEvolve
      3      ( schemaURLs      => xdb$string_list_t(:schemaURL)
      4      , newSchemas      => XMLSequenceType(XDBURIType(:schemaPath).getXML())
      5      , preserveOldDocs => TRUE
      6      , mapTabName      => 'RELATIE_DOCUMENTEN_TEMP'
      7      , generateTables  => FALSE
      8      );
      9  END;
    10  /
    PL/SQL procedure successfully completed.
    SQL> CREATE TABLE relatie_documenten OF XMLTYPE
      2         XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
      3         ELEMENT "Relatie"
      4  /
    Table created.
    SQL> CREATE OR REPLACE TRIGGER upo_rdt_ai
      2  AFTER INSERT ON relatie_documenten
      3  FOR EACH ROW
      4  DECLARE
      5     doc XMLType;
      6  BEGIN
      7     doc := :new.SYS_NC_ROWINFO$;
      8     XMLType.schemaValidate(doc);
      9  END;
    10  /
    Trigger created.
    SQL> declare
      2    tablename varchar2(2000);
      3  begin
      4    select temp_tabname
      5      into tablename
      6      from RELATIE_DOCUMENTEN_TEMP
      7     where table_name = USER || '.' || upper('relatie_documenten');
      8    execute immediate 'insert into relatie_documenten select xmltype(data) from ' || tablename;
      9    commit;
    10  end;
    11  /
    PL/SQL procedure successfully completed.
    SQL> select *
      2    from relatie_documenten
      3  /
    SYS_NC_ROWINFO$
    <Relatie>
      <Voornaam>Johan</Voornaam>
      <Achternaam>Hermans</Achternaam>
      <Tussenvoegsel/>
      <Geboortedatum>1978-01-02</Geboortedatum>
      <Geslacht>M</Geslacht>
      <Sofinummer>233300417</Sofinummer>
      <Straatnaam>Stationstraat</Straatnaam>
      <Huisnummer>10</Huisnummer>
      <Woonplaats>Weesp</Woonplaats>
      <Postcode>1383 AK</Postcode>
      <Zrn>1234567</Zrn>
    </Relatie>
    <Relatie>
      <Voornaam>Johanna</Voornaam>
      <Achternaam>Gurts</Achternaam>
      <Tussenvoegsel/>
      <Geboortedatum>1975-11-12</Geboortedatum>
      <Geslacht>V</Geslacht>
      <Sofinummer>234109807</Sofinummer>
      <Straatnaam>Stationstraat</Straatnaam>
      <Huisnummer>10</Huisnummer>
      <Woonplaats>Weesp</Woonplaats>
      <Postcode>1383 AK</Postcode>
      <Zrn>7654321</Zrn>
    </Relatie>
    SQL> INSERT
      2  INTO   relatie_documenten
      3  VALUES (XMLType
      4           ('<Relatie>
      5                <Voornaam>Johanna</Voornaam>
      6                <Achternaam>Gurts</Achternaam>
      7                <Tussenvoegsel/>
      8                <Geboortedatum>1975-11-12</Geboortedatum>
      9                <Geslacht>O</Geslacht>
    10                <Sofinummer>234109807</Sofinummer>
    11                <Straatnaam>Stationstraat</Straatnaam>
    12                <Huisnummer>10</Huisnummer>
    13                <Woonplaats>Weesp</Woonplaats>
    14                <Postcode>1383 AK</Postcode>
    15                <Zrn>7654321</Zrn>
    16             </Relatie>').CreateSchemaBasedXML(:schemaURL))
    17  /
    1 row created.
    SQL> commit
      2  /
    Commit complete.
    SQL> select *
      2    from relatie_documenten
      3  /
    SYS_NC_ROWINFO$
    <Relatie>
      <Voornaam>Johan</Voornaam>
      <Achternaam>Hermans</Achternaam>
      <Tussenvoegsel/>
      <Geboortedatum>1978-01-02</Geboortedatum>
      <Geslacht>M</Geslacht>
      <Sofinummer>233300417</Sofinummer>
      <Straatnaam>Stationstraat</Straatnaam>
      <Huisnummer>10</Huisnummer>
      <Woonplaats>Weesp</Woonplaats>
      <Postcode>1383 AK</Postcode>
      <Zrn>1234567</Zrn>
    </Relatie>
    <Relatie>
      <Voornaam>Johanna</Voornaam>
      <Achternaam>Gurts</Achternaam>
      <Tussenvoegsel/>
      <Geboortedatum>1975-11-12</Geboortedatum>
      <Geslacht>V</Geslacht>
      <Sofinummer>234109807</Sofinummer>
      <Straatnaam>Stationstraat</Straatnaam>
      <Huisnummer>10</Huisnummer>
      <Woonplaats>Weesp</Woonplaats>
      <Postcode>1383 AK</Postcode>
      <Zrn>7654321</Zrn>
    </Relatie>
    <Relatie>
      <Voornaam>Johanna</Voornaam>
      <Achternaam>Gurts</Achternaam>
      <Tussenvoegsel/>
      <Geboortedatum>1975-11-12</Geboortedatum>
      <Geslacht>O</Geslacht>
      <Sofinummer>234109807</Sofinummer>
      <Straatnaam>Stationstraat</Straatnaam>
      <Huisnummer>10</Huisnummer>
      <Woonplaats>Weesp</Woonplaats>
      <Postcode>1383 AK</Postcode>
      <Zrn>7654321</Zrn>
    </Relatie>
    SQL>Here's the SQL, can you cut'n'paste and run the whole thing as XML_OWNER
    var schemaURL varchar2(256)
    var schemaPath varchar2(256)
    begin
      :schemaURL := 'http://localhost:8080/xsd/relaties.xsd';
      :schemaPath := '/public/relaties.xsd';
    end;
    call dbms_xmlSchema.deleteSchema(:schemaURL,4)
    declare
      res boolean;
      xmlSchema xmlType := xmlType(
    '<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                xmlns:xdb="http://xmlns.oracle.com/xdb"
                   elementFormDefault="unqualified"
                   attributeFormDefault="unqualified"
                   version="1.0">
         <xsd:element name="Relatie" xdb:defaultTable="">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element name="Voornaam" type="xsd:string"/>
                        <xsd:element name="Achternaam" type="xsd:string"/>
                        <xsd:element name="Tussenvoegsel" type="xsd:string"/>
                        <xsd:element name="Geboortedatum" type="xsd:date"/>
                        <xsd:element name="Geslacht">
                   <xsd:simpleType>
                      <xsd:restriction base="xsd:string">
                         <xsd:enumeration value="M"/>
                         <xsd:enumeration value="V"/>
                      </xsd:restriction>
                   </xsd:simpleType>
                </xsd:element>
                     <xsd:element name="Sofinummer">
                   <xsd:simpleType>
                      <xsd:restriction base="xsd:string">
                         <xsd:pattern value="\d{9}"/>
                      </xsd:restriction>
                   </xsd:simpleType>
                </xsd:element>
                        <xsd:element name="Straatnaam" type="xsd:string"/>
                        <xsd:element name="Huisnummer" type="xsd:string"/>
                        <xsd:element name="Woonplaats" type="xsd:string"/>
                        <!--xsd:element name="Postcode" type="xsd:string"/-->
                        <xsd:element name="Postcode">
                   <xsd:simpleType>
                      <xsd:restriction base="xsd:string">
                         <xsd:pattern value="\d{4} [A-Z]{2}"/>
                      </xsd:restriction>
                   </xsd:simpleType>
                </xsd:element>
                        <xsd:element name="Zrn">
                   <xsd:simpleType>
                      <xsd:restriction base="xsd:integer">
                         <xsd:minInclusive value="1000000"/>
                         <xsd:maxInclusive value="99999999999999"/>
                      </xsd:restriction>
                   </xsd:simpleType>
                </xsd:element>
                   </xsd:sequence>
              </xsd:complexType>
         </xsd:element>
    </xsd:schema>');
    begin
      if (dbms_xdb.existsResource(:schemaPath)) then
        dbms_xdb.deleteResource(:schemaPath);
      end if;
      res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    end;
    BEGIN
      DBMS_XMLSCHEMA.registerSchema(
        :schemaURL,
        XDBURIType(:schemaPath).getClob(),
        TRUE,
        FALSE,
        FALSE,
        TRUE);
    END;
    DROP TABLE relatie_documenten FORCE
    CREATE TABLE relatie_documenten OF XMLTYPE
           XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
           ELEMENT "Relatie"
    CREATE OR REPLACE TRIGGER upo_rdt_ai
    AFTER INSERT ON relatie_documenten
    FOR EACH ROW
    DECLARE
       doc XMLType;
    BEGIN
       doc := :new.SYS_NC_ROWINFO$;
       XMLType.schemaValidate(doc);
    END;
    INSERT
    INTO   relatie_documenten
    VALUES (XMLType
             ('<Relatie>
                  <Voornaam>Johan</Voornaam>
                  <Achternaam>Hermans</Achternaam>
                  <Tussenvoegsel/>
                  <Geboortedatum>1978-01-02</Geboortedatum>
                  <Geslacht>M</Geslacht>
                  <Sofinummer>233300417</Sofinummer>
                  <Straatnaam>Stationstraat</Straatnaam>
                  <Huisnummer>10</Huisnummer>
                  <Woonplaats>Weesp</Woonplaats>
                  <Postcode>1383 AK</Postcode>
                  <Zrn>1234567</Zrn>
               </Relatie>'
            ).CreateSchemaBasedXML(:schemaURL))
    commit
    INSERT
    INTO   relatie_documenten
    VALUES (XMLType
             ('<Relatie>
                  <Voornaam>Johanna</Voornaam>
                  <Achternaam>Gurts</Achternaam>
                  <Tussenvoegsel/>
                  <Geboortedatum>1975-11-12</Geboortedatum>
                  <Geslacht>V</Geslacht>
                  <Sofinummer>234109807</Sofinummer>
                  <Straatnaam>Stationstraat</Straatnaam>
                  <Huisnummer>10</Huisnummer>
                  <Woonplaats>Weesp</Woonplaats>
                  <Postcode>1383 AK</Postcode>
                  <Zrn>7654321</Zrn>
               </Relatie>').CreateSchemaBasedXML(:schemaURL))
    commit
    INSERT
    INTO   relatie_documenten
    VALUES (XMLType
             ('<Relatie>
                  <Voornaam>Johanna</Voornaam>
                  <Achternaam>Gurts</Achternaam>
                  <Tussenvoegsel/>
                  <Geboortedatum>1975-11-12</Geboortedatum>
                  <Geslacht>O</Geslacht>
                  <Sofinummer>234109807</Sofinummer>
                  <Straatnaam>Stationstraat</Straatnaam>
                  <Huisnummer>10</Huisnummer>
                  <Woonplaats>Weesp</Woonplaats>
                  <Postcode>1383 AK</Postcode>
                  <Zrn>7654321</Zrn>
               </Relatie>').CreateSchemaBasedXML(:schemaURL))
    commit
    declare
      xmlschema xmltype;
      res       boolean;
    begin
      select xdburitype(:schemaPath).getXML()
        into xmlSchema
        from dual;
      dbms_xdb.deleteResource(:schemaPath);
      select insertChildXML
               xmlschema,
               '/xsd:schema//xsd:element[@name="Geslacht"]/xsd:simpleType/xsd:restriction',
               'xsd:enumeration',
               xmltype('<xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>'),
               'xmlns:xsd="http://www.w3.org/2001/XMLSchema"'
      into xmlSchema
      from dual;
      res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    end;
    commit
    set long 100000 pages 200 lines 140
    select xdburitype(:schemaPath).getXML()
      from dual
    DROP TABLE RELATIE_DOCUMENTEN_TEMP
    BEGIN
      DBMS_XMLSCHEMA.copyEvolve
        ( schemaURLs      => xdb$string_list_t(:schemaURL)
        , newSchemas      => XMLSequenceType(XDBURIType(:schemaPath).getXML())
        , preserveOldDocs => TRUE
        , mapTabName      => 'RELATIE_DOCUMENTEN_TEMP'
        , generateTables  => FALSE
    END;
    CREATE TABLE relatie_documenten OF XMLTYPE
           XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
           ELEMENT "Relatie"
    CREATE OR REPLACE TRIGGER upo_rdt_ai
    AFTER INSERT ON relatie_documenten
    FOR EACH ROW
    DECLARE
       doc XMLType;
    BEGIN
       doc := :new.SYS_NC_ROWINFO$;
       XMLType.schemaValidate(doc);
    END;
    declare
      tablename varchar2(2000);
    begin
      select temp_tabname
        into tablename
        from RELATIE_DOCUMENTEN_TEMP
       where table_name = USER || '.' || upper('relatie_documenten');
      execute immediate 'insert into relatie_documenten select xmltype(data) from ' || tablename;
      commit;
    end;
    select *
      from relatie_documenten
    INSERT
    INTO   relatie_documenten
    VALUES (XMLType
             ('<Relatie>
                  <Voornaam>Johanna</Voornaam>
                  <Achternaam>Gurts</Achternaam>
                  <Tussenvoegsel/>
                  <Geboortedatum>1975-11-12</Geboortedatum>
                  <Geslacht>O</Geslacht>
                  <Sofinummer>234109807</Sofinummer>
                  <Straatnaam>Stationstraat</Straatnaam>
                  <Huisnummer>10</Huisnummer>
                  <Woonplaats>Weesp</Woonplaats>
                  <Postcode>1383 AK</Postcode>
                  <Zrn>7654321</Zrn>
               </Relatie>').CreateSchemaBasedXML(:schemaURL))
    commit
    select *
      from relatie_documenten
    /

  • Regarding where to find namespace when create receiver determination

    Hi all :
          Could you please tell me how to find or how to create namespace , as it is needed when create
    receiver determination .  Thank you very much!

    HI Sony,
    Do you mean how to select the Namespace in the Receiver Determination ?
    You have to use the Name space of the Sender Interface in the Receiver Determination. The Namespace should create in Integration Repository after importing the Software Component from the SLD.
    You can get the namespace from the Search help in the Receiver Determination.
    Regards
    Sridhar Goli

  • Time Dimension Wizard Hangs Creating Map

    I'm running OWB 11.1.0.7 and trying to create a time dimension using the time dimension wizard and when I get to the progress screen it just hangs when it gets to 60% progress and the message window says it's creating the map.
    There is no indication of any kind of error that might say why it's hanging, or any indication other than "creating map" that says what it's trying to do at the time. Is there anyway to dig under the covers anywhere to see what the wizard is trying to do that is causing it to hang?
    Another question is how I can create the same kind of dimension manually that the wizard would have created? It appears to be creating a special kind of dimension, specifically for time but I can't see anyway to create it manually if the wizard doesn't work. I found another message that mentioned a time dimension template that the wizard uses but that post was about how to use OMBPlus to remove the time template type so it could be edited manually, not how to create one using it.
    So, anyone have any suggestions for how I can track this problem down and/or create that time dimension manually? Thanks.
    Regards, Bob

    Are you using OWB 11.1.0.7 or greater?
    We encountered the same problem from that version on. try to use an older version (11.1.0.6 client definitely works).
    We will put this into metalink as it is definitely a bug.
    Cheers,
    Knut

  • Anyone using openstreetmap and mapviewer/mapbuilder to create maps

    anyone using openstreetmap and mapviewer/mapbuilder to create maps?

    Ok, I do exactly as you specify here. In addition I import the needed jars from the import folder of j2mepolish. Also, I put the resources folder from the polish sample (MenuMidlet) in the project, and all marked errors disappears.
    Then I try to run it as an Ant build, and get the following error:
    BUILD FAILED
    D:\Program Files\eclipse31\j2me\sample\build.xml:115: The MIDlet [source.src.de.enough.polish.example.MenuMidlet] could not be found. Check your <midlet>-setting in the file [build.xml] or adjust the [sourceDir] attribute of the <build>-element.The MIDlet should be in D:\Program Files\eclipse31\j2me\sample\source\src\source\src\de\enough\polish\example\MenuMidlet.java
    Ok - so it seems that it for some reason gets "source\src" two times. So I go back to the <midlet class and remove the source.src, leaving just de.enough.polish.example.
    Then I run as Ant again, and it compiles successfully.
    However, when I try to run the MenuMidlet class as a j2me midlet (in eclipse) it starts, and then crash with this error:
    java.lang.NoClassDefFoundError: de/enough/polish/util/Locale
         at source.src.de.enough.polish.example.MenuMidlet.<init>(+11)
         at java.lang.Class.runCustomCode(+0)
         at com.sun.midp.midlet.MIDletState.createMIDlet(+19)
         at com.sun.midp.midlet.Scheduler.schedule(+52)
         at com.sun.midp.main.Main.runLocalClass(+28)
         at com.sun.midp.main.Main.main(+116)
    So - seemingly - to compile it I need to give it one address, but for the midlet to run it must be compiled with an address that won't let it compile :-)
    Well - then I create a J2ME package from the project, and run the deployed/sample.jad file. Then the midlet actually starts, but when I click Launch, the display shows:
    New Midlet de.enough.polish.ui.MenuBar Exception: java.lang.classNotFoundException: de/enough/polish/ui/MenuBar
    I can't find a reference to MenuBar anywhere in the sample code.

  • A problem due to a namespace conflict!!

    Dear Edwin,
    The problem of the proxy, was partially solved. this
    has been "overcame" by using a private ISP
    and not our university network. Though the
    compilation of the example
    orabpel/samples demos/AmazonFlow.bpel
    was successful, there is still a problem.....
    as shown in (1), since I am not able to execute the
    AmazonFlow process instance with BPEL manager (see 2).
    I would appreciate any help from you..
    Thank you very much in advance!!!
    Abdelkder
    --------------- (1) -------------------
    C:\orabpel\samples\demos\AmazonFlow>SETLOCAL
    Buildfile: build.xml
    main:
    [bpelc] [Error] AmazonWebServices.wsdl:9:45: src-resolve.4.2: Error resolvin
    g component 'soapenc:Array'. It was detected that 'soapenc:Array' is in namespac
    e 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespac
    e are not referenceable from schema document 'http://soap.amazon.com/schemas3/Am
    azonWebServices.wsdl'. If this is the incorrect namespace, perhaps the prefix of
    'soapenc:Array' needs to be changed. If this is the correct namespace, then an
    appropriate 'import' tag should be added to 'http://soap.amazon.com/schemas3/Ama
    zonWebServices.wsdl'.
    [bpelc] bpelc> validating "C:\orabpel\samples\demos\AmazonFlow\AmazonFlow.bp
    el" ...
    [bpelc] bpelc> BPEL suitcase deployed to: C:\orabpel\domains\default\deploy
    BUILD SUCCESSFUL
    Total time: 1 minute 41 seconds
    C:\orabpel\samples\demos\AmazonFlow>ENDLOCAL
    When I execute the process with the BPEL manager I get
    the following error in the BPEL server command prompt.
    ----------------- (2)------------------
    <BaseCubeSessionBean::logError> Error while invoking bean "process manager": Fai
    led to read wsdl.
    Error happened when reading wsdl at "http://dekdouk:9700/orabpel/default/AmazonF
    low/1.0/AmazonFlow.wsdl", because "WSDLException: faultCode=PARSER_ERROR: Error
    reading file: No route to host: connect".
    Make sure wsdl exists at that URL and is valid.
    <2005-01-22 03:16:41,406> <ERROR> <default.collaxa.cube.engine.agents> <SimpleJo
    b::execute> Error while executing agent.
    An error occured while attempting to execute the job "dispatch" for agent "dispa
    tch". The exception reported was : Dispatcher schedule error.
    An error occurred while scheduling a batch message with the dispatcher. The exce
    ption is: Couldn't initialize JMS resources.
    An exception thrown while initializing JMS destination "java:comp/env/jms/collax
    a/BPELWorkerQueue", the reason is Unable to create a connection to "dekdouk/213
    .181.171.6:9,127" as user "null".
    Please check your jms server configuration and make sure that you have configure
    d the "java:comp/env/jms/collaxa/BPELWorkerQueue" destination and make sure that
    your JMS server is up and running.

    Dear Edwin,
    The problem of the proxy, was partially solved. this
    has been "overcame" by using a private ISP
    and not our university network. Though the
    compilation of the example
    orabpel/samples demos/AmazonFlow.bpel
    was successful, there is still a problem.....
    as shown in (1), since I am not able to execute the
    AmazonFlow process instance with BPEL manager (see 2).
    I would appreciate any help from you..
    Thank you very much in advance!!!
    Abdelkder
    --------------- (1) -------------------
    C:\orabpel\samples\demos\AmazonFlow>SETLOCAL
    Buildfile: build.xml
    main:
    [bpelc] [Error] AmazonWebServices.wsdl:9:45: src-resolve.4.2: Error resolvin
    g component 'soapenc:Array'. It was detected that 'soapenc:Array' is in namespac
    e 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespac
    e are not referenceable from schema document 'http://soap.amazon.com/schemas3/Am
    azonWebServices.wsdl'. If this is the incorrect namespace, perhaps the prefix of
    'soapenc:Array' needs to be changed. If this is the correct namespace, then an
    appropriate 'import' tag should be added to 'http://soap.amazon.com/schemas3/Ama
    zonWebServices.wsdl'.
    [bpelc] bpelc> validating "C:\orabpel\samples\demos\AmazonFlow\AmazonFlow.bp
    el" ...
    [bpelc] bpelc> BPEL suitcase deployed to: C:\orabpel\domains\default\deploy
    BUILD SUCCESSFUL
    Total time: 1 minute 41 seconds
    C:\orabpel\samples\demos\AmazonFlow>ENDLOCAL
    When I execute the process with the BPEL manager I get
    the following error in the BPEL server command prompt.
    ----------------- (2)------------------
    <BaseCubeSessionBean::logError> Error while invoking bean "process manager": Fai
    led to read wsdl.
    Error happened when reading wsdl at "http://dekdouk:9700/orabpel/default/AmazonF
    low/1.0/AmazonFlow.wsdl", because "WSDLException: faultCode=PARSER_ERROR: Error
    reading file: No route to host: connect".
    Make sure wsdl exists at that URL and is valid.
    <2005-01-22 03:16:41,406> <ERROR> <default.collaxa.cube.engine.agents> <SimpleJo
    b::execute> Error while executing agent.
    An error occured while attempting to execute the job "dispatch" for agent "dispa
    tch". The exception reported was : Dispatcher schedule error.
    An error occurred while scheduling a batch message with the dispatcher. The exce
    ption is: Couldn't initialize JMS resources.
    An exception thrown while initializing JMS destination "java:comp/env/jms/collax
    a/BPELWorkerQueue", the reason is Unable to create a connection to "dekdouk/213
    .181.171.6:9,127" as user "null".
    Please check your jms server configuration and make sure that you have configure
    d the "java:comp/env/jms/collaxa/BPELWorkerQueue" destination and make sure that
    your JMS server is up and running.

Maybe you are looking for