Weird case of simple parameter assignment

Hi, Guys !
Here's some challenge for you. I have a Package where one of the Functions used for Error_logging. It works fine, except rarely it gives an Error :
ORA-06512: at "CORE_PKG", line 295
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
272 PROCEDURE ERR_HANDLER_PRC
273 (iERR_CODE IN NUMBER,
274 oRETURN_CODE OUT NUMBER,
275 oRETURN_MSG OUT ERROR_MSG_BV.MSG_TEXT%TYPE,
276 iUSE_SQLERRM IN BOOLEAN DEFAULT TRUE) IS
277
278 vMSG_REC ERROR_MSG_BV%ROWTYPE := MSG_ROW_FNC (iERR_CODE); -- This Function selects 0 or 1 row based on passed Error code from Table of standard messages (just 33 rows)
279
280 BEGIN
281
282 IF vMSG_REC.MSG_TEXT IS NULL OR vMSG_REC.RETURN_CODE IS NULL THEN
283 vMSG_REC.RETURN_CODE := iERR_CODE;
284 vMSG_REC.MSG_TEXT := SQLERRM (iERR_CODE);
285 END IF;
286
287 oRETURN_CODE := vMSG_REC.RETURN_CODE;
288 oRETURN_MSG := vMSG_REC.MSG_TEXT;
289
290 EXCEPTION
291
292 WHEN OTHERS THEN
293
294 oRETURN_CODE := vMSG_REC.RETURN_CODE;
295 oRETURN_MSG := vMSG_REC.MSG_TEXT;
296
297 INSERT_ERROR_LOG_PRC ('CORE_PKG', 'ORACLE', SQLCODE, SQLERRM, 'ERR_HANDLER_PRC',
298 'Execution Block of ERR_HANDLER_PRC');
299
300 END ERR_HANDLER_PRC;
At line 295 - just a simple assignment of one field (which is VARCHAR2 (512) <- longest Oracle SQLERRM string) belonging to a ROWTYPE variable. But that's happening inside error handler which means that initial
error occur on Line 284 or 288. On those lines
also similar assignments. I checked all parameters, variables, %types and %rowtypes and they all
VARCHAR2(512) - exactly what are suppose to be. Longest string selected from Table of standard messages into %rowtype.msg_text is 97 characters (eventhough it can hold up to 512).
So my question is HOW in the world is possible that Buffer is too small If it's SAME length that variable ???
(and actual string less then 512)
Any Ideas anybody ?
Thanx ! ( Please let me know If anything is unclear )

Thanx, Rich. I understand what you're saying and I was able to re-create error in Anonymous block which calls
ERR_LOG_HANDLER_PRC and which call ERR_HANDLER_PRC that raises an Error.
DECLARE
STATUS ERROR_LOG_BV.ERROR_CODE%TYPE;
STATUS_MSG VARCHAR2(20); <-- this declaration causes 'Buffer too small' error
BEGIN
PENSKE_CORE_PKG.ERR_LOG_HANDLER_PRC (SQLCODE, SQLERRM, STATUS, STATUS_MSG, TRUE, 'ORACLE',
'ANONYMOUS_BLOCK', 'TEST_CALL');
END;
But this code executes fine:
DECLARE
STATUS ERROR_LOG_BV.ERROR_CODE%TYPE;
STATUS_MSG ERROR_LOG_BV.ERROR_DESC%TYPE;
BEGIN
PENSKE_CORE_PKG.ERR_LOG_HANDLER_PRC (SQLCODE, SQLERRM, STATUS, STATUS_MSG, TRUE, 'ORACLE',
'ANONYMOUS_BLOCK', 'TEST_CALL');
END;
But that's a testing code. In the real code I checked all Programs calling that routine, and all
OUT parameters and variables declared dynamically like :
vERR_CODE ERROR_LOG_BV.ERROR_CODE%TYPE;
vERR_MSG ERROR_LOG_BV.ERROR_DESC%TYPE;
So I don't know how is that possible ?

Similar Messages

  • How to pass simple parameter to XSLT from BPM 11g Data Association

    Is it possible to pass a simple parameter to an XSLT from a BPM 11g Data Association (11.1.1.6.0)?  Here is why I asked.  I have a transform that I want to reuse across two service activities in the same process.  The only difference is one integer ID value between the two activities.  (Happens to be running an IPM saved search, each with a different ID.)
    I tried mapping the ID value in the Data Association dialog, in addition to the XSLT mapping, but didn't work.  Or is there another method I could use to reuse this transform (besides just copying it as I've done for now)?  Thanks.

    If I understood your scenario, the point is: you always have to pass the same dataObjects as parameters to the XSL, but you can change the values of them in an association step before the transformation.
    Lets see if the following can fit your needs:
    1) your project has three BusinessObjects: "SearchParam", "CommonData" and "Result"; and five process dataObjects:
    - "search1", "search2" and "search" of type "SearchParam";
    - "commonData" of type "CommonData";
    - "result" of type "Result"
    2) your XSL has "result" as target and two sources: "search" and "commonData"
    3) In some part of the process flow you have a scriptTask with:
    - a data association from "search1" to "search";
    - a transformation with "search" and "commonData" as parameters
    4) In other part of the process flow you can use the same transformation, but using the data from "search2" as parameter, adding a scriptTask with:
    - a data association from "search2" to "search";
    - the same transformation with "search" and "commonData" as parameters
    In this scenario you are reusing the same XSL file only changing the values for one parameter.

  • Using a Simple Parameter Form Portlet with a Report Portlet to Search DB

    My organization registers clients for workshops in iLearning.We use iPortal for our web site. I would like to use a Simple Parameter Form Portlet for clients to conduct a search on the data that is in iLearning and have it displayed in a Report Portlet on a separate page. I have been able to bring the iLearning data into the Report Portlet but I have not been successful in setting up the Simple Parameter Form Portlet to do a search on the data and then have it displayed. Any suggestions.

    hi,
    i just tested this in portal 10.1.4 and it works fine. you can fire an event and pass a parameter from a simple parameter form portlet and consume this page parameter in a portlet builder reports component. there is some documented behavior in bug 3321558 that has to do with personaliziation (customization in older releases). if you enter some personalization the page parameter gets ignored. for more information on this please contact oracle support services.
    regards,
    christian

  • b Simple Parameter Form & Page Parameter /b

    Hello,
    <br>
    i have a problem with a simple Parameter Form:
    I have one page; on this page i have a simple Parameter Form and an OmniPortlet (the pageParameter is 'Field1' and is mapped to both portlets!)
    <br>
    now my problem: when i type my parameter in the simple param form it is displayed in the url (http://mypage<b>&Field1=10000</b>).<br> the omniportlet displays the right data. all right so far!
    <br>
    but now i type a new parameter in the simple parameter form and now the url looks like this: http://mypage&Field1=10000<b>&Field1=20000</b><br>The parameter shouldn't be added to the old url, but a new url should be created with <i>one</i> new parameter.
    <br>
    Where is the problem? i cant find any solution?
    <br>
    Thanks for your help!

    Hi,
    There is a step you are missing.
    Open the page properties for the page where the Simple Parameter form and the Omniportlet resides.
    Go to the Events Tab.
    Here you will see "Portlet Events". There will be a list of portlets that are added on this page. Click on the "Simple Parameter Form".
    Under this you will find a link called "Submit". When you click on this link, it opens options on the right hand side of the page.
    Here, under the heading "When this event is raised:" Click the Radio Button "Go to page:" and then click on the button for the LOV on the right side of the box, a pop-up opens, select this page itself. (For Example, if the name of the page is PAGE01 (where we have added this Simple Parameter Form and the OmniPortlet), under the Page Group PG01, then click on the link called Return Object for PAGE01 under PG01 from the pop-up).
    After doing the above step do this:
    Right Below this, you will find another heading called "Page Input" which will have the list of page parameters. From the first drop down list select "Event Output" and from the second drop down list select "Parameter 1" (If there is only one parameter. But if you have more than one parameter, select the "Event Output" & "Parameter 2" respectively, and so on). Make sure that you match the correct page parameter with the Parameter drop down otherwise your results will vastly vary or there might be no result.
    We are pretty much done.
    Now just click on the buttons "Apply" then "Ok"
    Test your page. It will not add &Field1=<value>&Field1=<value>...... any number of times you run this.
    I hope I was of some help to you.
    Regards,
    Saabir.

  • Creating a Simple Parameter Form in Portal

    I am trying to create a simple parameter form in Oracle Portal 10.1.2. to be able to allow users to enter a parameter on the dashboard that will be passed to discoverer worksheets. However, I can't seem to find any information as to how to do this. All I find is information stating that it can be done.
    Can anyone explain this to me or send me a link that explains this?
    Many thanks.
    Dino

    hi
    You could look at http://www.oracle.com/technology/products/discoverer/files/viewlets/1012_dashboard.html
    I don´t remember if here you create the simple parameter form. But there is a portlet called "Simple Parameter Form", you can find it at Portlet Builders. You can reach this link in your Oracle portal in the Edit link, in the add portlet link.
    then you can follow the wizard to create your parameter portlet
    After this step you should link the parameters you send through this portlet with the page and the other portlets.
    I hope this help

  • Weird case!

    Weird case!
    Desktop publishing with InDesign (CS5) is something else then Quark.
    I work with documents from customers that would have used Plug-ins but sometimes, let’s make a book, InDesign will not ad any pages.
    I think it’s strange for a publisher packet that let third party Plug-ins make a mess of such a nice peace of software.
    Or am I thinking wrong here?
    PS: forgive my bad English because it’s not my mothers languages.

    The version of InDesign is CS5 but for now, not on the job, I don’t know any other number, build, series or whatever.
    One of the problems is making a book.
    Start InDesign, make Book, and add just InDesign files, NOT.
    The only message is that InDesign can not add pages to the book because of a Plug-In.
    When I load the org. document I can read, change, delete but can not make a packet or make a book.
    The customer has used a Plug-in and forces me (or/and InDesign?) to buy that Plug-in!
    That’s weird, or…

  • Valuated GR not allowed in case of multiple account assignment

    Hi Friends,
    While creating Asset PO with multiple account assignment categories from SC
    i received the following error message in RZ20.
    PO 0030065837: No instance of object type PurchaseOrder has been created. External reference:
    PurchOrder 0030065837: Purchase order still contains faulty items
    PO 0030065837: Valuated GR not allowed in case of multiple accoun t assignment
    PurchOrder 0030065837: Transfer failed
    Now the PO status is error in process
    Can any one help on this issue...
    Thank You
    Shrinivas

    Hi shrinivas,
    When you are having the multiple account assignment, then the system will force you to have GR-non valuated indicator being flagged which results in the fact there is not any FI document at GR posting stage and this is the standard feature of SAP
    can you tell me whether you have that option of selecting or deselecting the GR nonvaluated in PO creation(EBP).If it is there falg it and reprocess the Sc
    hope this will help
    regards
    subbu

  • Display all record in case of null parameter OR selecting "ALL"

    hi all,
    I want to show the all records in the report in case the user give empty parameter Or "ALL" from the parameter list.
    I used such the way in the query:
    select item
    from item_master
    where ITEM_ID = NVL(:P_ITEM,ITEM_ID);
    its working good but now I want to give the "ALL" in the list of parameter form. so when the user select the "ALL" then the all items to be displayed.
    thanks
    Muhammad Nadeem
    [email protected]

    Hello,
    You can use the following SQL Query :
    select item
    from item_master
    where (:P_ITEM='ALL' or ITEM_ID = NVL(:P_ITEM,ITEM_ID);)
    as long as :P_ITEM has a "type" compatible with a string ...
    Regards

  • Very simple Parameter question in Eclipse

    I simply want to create a report where a user can pick a date range at runtime.  I designed a simple report, added parameter fields and ran it in the designer.  It prompted me for dates and I filled them in.  The report ran in the designer just fine.  When I publish the report to the Apache Tomcat web site, I want the prompts to pop up for the user so they can pick the date range.  There are no parameters that pop up and the parameter panel shows NO parameters.  Can someone point me to a document or process that will allow me to prompt the user for these dates?  I am invoking the report from the JSP that is generated by the plugin.

    Are you passing paramete values in your code? If you do not then it will automatically asks for parameters.
    Regards,
    Tejaswini

  • Workflow - Parameter Assignment Question

    I have this workflow where i have defined the input parameter in the "start" activity. and, have directly binded that parameter into the input parameter in the "mapping" activity.
    is this the right way to do? or do i need to assign the parameter (from "start" activity) first into a variable, and then assign it into the input parameter in the "mapping" activity?
    ~Prabha

    never mind, i got it :-)

  • Simple parameter question ie db_name and usage in an expression

    Hi,
    I just started with SSIS with an example containing a flat xls file with 5 columns and a source table in sql.
    The example works fine no parameters etc.
    What I want to try out is to make an exception that if a certain db_name = X then the flow should be redirected to another table.
    Basicly I need help how to define a parameter to read from the source database like "select db_name as db_name" and use this in the package flow. When db_name=X then flow A ELSE flow B
    Any help is very appreciated.
    -Miracles are easy, the impossible takes a bit longer-

    Hi Paul,
    Create an object variable with name varObj and create a string variable with name as varDBName
    Use this as source query in execute sql tasK: Select <DBNamefield> from Table. In execute sql task do the following:
    On General tab: set Result set as Full Result Set
    On Result Set tab: Click Add and set Result Name as 0 and select varObj as Variable Name. This variable will capture the value returned from the select statement.
    Take a for each loop container and configure it as:
    On Collection tab: Enumerator: for each ado enumerator; ADO Object source variable: varObj; Enumeration Mode: Rows in first table.
    On Variable Mappings tab: Select varDBName as variable and set Index as 0.
    Inside the for each loop put the data flow task. Configure the data flow task and use a conditional split to redirect the rows based on varDBName as : @[User::varDBName]=="x" and so on for different outputs
    Nitesh Rai- Please mark the post as answered if it answers your question

  • MIGO in case of multiple account assignment.

    Hi,
    I have created PO with multiple account assignment. AAC is P.
    While doing MIGO, FI document is not getting generated.
    Can anyone plz explain how multiple account assignment functionality works?
    Regards
    Nilesh

    Hi
    Its a standard practice that if there is multiple account assignment, the proportion will not be appearing at the time of MIGO. It will get updated only at the time of Invoice verification.
    Regards,
    Lakshmanan Krishnan

  • ORA-31011 : Weird case of parsing/validation failure...

    Hello all,
    It seems that when trying to insert into an XMLTYPE schema-bound column I am hitting a validation error that I cannot replicate with either XMLSpy os Stylus Studio.
    Here follow the schemas that are used, and the offending XML :
    envelope-consult.xsd
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:publicid:-:DGTAXUD:GENERAL:ENVELOPE:1.0" xmlns:xml="http://www.w3.org/XML/1998/namespace" targetNamespace="urn:publicid:-:DGTAXUD:GENERAL:ENVELOPE:1.0" elementFormDefault="qualified" attributeFormDefault="unqualified" version="EORI-CONSULT-ENVELOPE-1.0">
         <xs:annotation>
              <xs:documentation>
                   This XML schema can be used by a national application to
                   validate consultation envelopes sent to the EORI
                   CDCO application. It can also be used to validate
                   consultation responses and acknowledgement envelopes
                   sent back by the EORI CDCO application. The number of
                   transactions in an envelope is 5.
                   For a request envelope, each transaction
                   contains a single app.message.
                   For a response envelope, each transaction contains
                   a single status element and a single app.message
                   element.
              </xs:documentation>
         </xs:annotation>
      <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="xml.xsd"/>
         <xs:element name="envelope">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="header" type="Header" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="transaction" type="Transaction" maxOccurs="5"/>
                   </xs:sequence>
                   <xs:attribute name="id" type="xs:string" use="required"/>
                   <xs:attribute ref="xml:lang" default="en-GB"/>
              </xs:complexType>
         </xs:element>
         <xs:complexType name="AppMessage">
              <xs:sequence>
                   <xs:element ref="abstract.message"/>
              </xs:sequence>
              <xs:attribute name="id" type="xs:string" use="required"/>
         </xs:complexType>
         <xs:complexType name="Binary">
              <xs:simpleContent>
                   <xs:extension base="xs:base64Binary">
                        <xs:attribute name="mime.type" type="xs:string" default="application/octet-stream"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="BusinessRef">
              <xs:sequence>
                   <xs:element ref="abstract.ref"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="Header">
              <xs:attribute name="name" type="xs:string" use="required"/>
              <xs:attribute name="value" type="xs:string" use="required"/>
         </xs:complexType>
         <xs:complexType name="MMIMessageType">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute ref="xml:lang" default="en-GB"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="Status">
              <xs:sequence>
                   <xs:element name="mmi.message" type="MMIMessageType" minOccurs="0"/>
                   <xs:element name="status.detail" type="StatusDetail" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
              <xs:attribute name="category" type="StatusCategory" use="required"/>
              <xs:attribute name="location" type="xs:string" use="required"/>
         </xs:complexType>
         <xs:simpleType name="StatusCategory">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="ok"/>
                   <xs:enumeration value="error"/>
                   <xs:enumeration value="rejected"/>
                   <xs:enumeration value="warning"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="StatusDetail">
              <xs:sequence>
                   <xs:element name="business.ref" type="BusinessRef" minOccurs="0"/>
                   <xs:element name="binary" type="Binary" minOccurs="0"/>
                   <xs:element name="mmi.message" type="MMIMessageType" minOccurs="0"/>
              </xs:sequence>
              <xs:attribute name="category" type="StatusDetailCategory" use="required"/>
              <xs:attribute name="location" type="xs:string" use="required"/>
              <xs:attribute name="code" type="xs:NMTOKEN" use="required"/>
         </xs:complexType>
         <xs:simpleType name="StatusDetailCategory">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="error"/>
                   <xs:enumeration value="info"/>
                   <xs:enumeration value="warning"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="Transaction">
              <xs:sequence>
                   <xs:element name="header" type="Header" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element name="status" type="Status" minOccurs="0"/>
                   <xs:element name="app.message" type="AppMessage"/>
              </xs:sequence>
              <xs:attribute name="id" type="xs:string" use="required"/>
         </xs:complexType>
         <xs:element name="abstract.message" abstract="true"/>
         <xs:element name="abstract.ref" abstract="true"/>
    </xs:schema>EORI-consult.xsd
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:envelope="urn:publicid:-:DGTAXUD:GENERAL:ENVELOPE:1.0" xmlns="urn:publicid:-:DGTAXUD:EORI:CONSULT:1.0" targetNamespace="urn:publicid:-:DGTAXUD:EORI:CONSULT:1.0" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
         <xs:annotation>
              <xs:documentation>
                   This XML schema contains the definitions of data
                   elements and messages specific to the EORI consult
                   functionality.
              </xs:documentation>
         </xs:annotation>
         <xs:import namespace="urn:publicid:-:DGTAXUD:GENERAL:ENVELOPE:1.0" schemaLocation="envelope-consult.xsd"/>
         <xs:include schemaLocation="EORI-data.xsd"/>
         <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="xml.xsd"/>
         <!-- Base types -->
      <xs:simpleType name="Date">
              <xs:annotation>
                   <xs:documentation>Date format</xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="\d{4}\d{2}\d{2}"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="EoriRecord">
              <xs:sequence>
                   <xs:element name="eori.record.ref" type="EoriNumberRef"/>
                   <xs:element name="tc.number.list" type="TcNumberList"/>
                   <xs:element name="economic.operator.details" type="EconomicOperatorDetails"/>
                   <xs:element name="legal.status.list" type="LegalStatusPeriodList"/>
                   <xs:element name="establishment.address.list" type="EstablishmentAddressPeriodList"/>
                   <xs:element name="vat.list" type="VatList"/>
                   <xs:element name="contact.list" type="ContactPeriodList"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="EconomicOperatorDetails">
              <xs:sequence>
                   <xs:element name="full.name" type="EOFullName"/>
                   <xs:element name="short.name" type="EOShortName"/>
                   <xs:element name="establishment.date" type="Date" minOccurs="0"/>
                   <xs:element name="person.type.code" type="TypePerson" minOccurs="0"/>
                   <xs:element name="economic.activity.code" type="ActivityCode" minOccurs="0"/>
                   <xs:element name="start.date" type="Date"/>
                   <xs:element name="expiry.date" type="Date" minOccurs="0"/>
                   <xs:element name="publication.ind" type="xs:boolean" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>     
      <xs:complexType name="ValidityPeriod">
              <xs:sequence>
                   <xs:element name="start.date" type="Date"/>
                   <xs:element name="end.date" type="Date" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="ContactPeriod">
              <xs:sequence>
                   <xs:element name="contact" type="Contact"/>
                   <xs:element name="validity.period" type="ValidityPeriod"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="ContactPeriodList">
              <xs:sequence>
                   <xs:element name="contact" type="ContactPeriod" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>          
         </xs:complexType>
         <xs:complexType name="EstablishmentAddressPeriod">
              <xs:sequence>
                   <xs:element name="establishment.address" type="EstablishmentAddress"/>
                   <xs:element name="validity.period" type="ValidityPeriod"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="EstablishmentAddressPeriodList">
              <xs:sequence>
                   <xs:element name="establishment.address" type="EstablishmentAddressPeriod" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="LegalStatusPeriod">
              <xs:sequence>
                   <xs:element name="legal.status" type="LegalStatus"/>
                   <xs:element name="validity.period" type="ValidityPeriod"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="LegalStatusPeriodList">
              <xs:sequence>
                   <xs:element name="legal.status" type="LegalStatusPeriod" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="EoriRecordFull">
              <xs:complexContent>
                   <xs:extension base="EoriRecord">
                        <xs:sequence>
                             <xs:element name="aeo.certificate.lifecycle.list" type="AeoCertificateLifecycleList" minOccurs="0"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="AeoCertificateLifecycleList">
              <xs:sequence>
                   <xs:element name="aeo.certificate.lifecycle" type="AeoCertificateLifecycle" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>     
         <xs:complexType name="AeoCertificateLifecycle">
              <xs:sequence>
                   <xs:element name="start.date" type="Date"/>
                   <xs:element name="end.date" type="Date" minOccurs="0"/>
                   <xs:element name="aeo.certificate.ref" type="AeoCertificateNumber" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>          
         <!-- Consultation messages -->
         <xs:element name="eori.record.snapshot.consultation.request" substitutionGroup="envelope:abstract.message">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="snapshot.request.list" type="EoriRecordSnapshotRequestList"/>
                   </xs:sequence>
                <xs:attribute ref="xml:lang" default="en-GB"/>                              
              </xs:complexType>
         </xs:element>
         <xs:element name="eori.record.full.consultation.request" substitutionGroup="envelope:abstract.message">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="full.request.list" type="EoriRecordFullRequestList"/>
                   </xs:sequence>
                   <xs:attribute ref="xml:lang" default="en-GB"/>               
              </xs:complexType>
         </xs:element>
         <xs:element name="eori.record.snapshot.consultation.response" substitutionGroup="envelope:abstract.message">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="snapshot.response.list" type="EoriRecordSnapshotResponseList"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="eori.record.full.consultation.response" substitutionGroup="envelope:abstract.message">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="full.response.list" type="EoriRecordFullResponseList"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Acknowledgement business references -->
         <xs:element name="full.request" type="EoriRecordFullRequest" substitutionGroup="envelope:abstract.ref"/>
         <xs:element name="snapshot.request" type="EoriRecordSnapshotRequest" substitutionGroup="envelope:abstract.ref"/>
         <!-- Snapshot: Consultation messages -->
         <xs:complexType name="SnapshotConsultationRequest">
              <xs:sequence>
                   <xs:element name="snapshot.request.list" type="EoriRecordSnapshotRequestList"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="SnapshotConsultationResponse">
              <xs:sequence>
                   <xs:element name="snapshot.response.list" type="EoriRecordSnapshotResponseList"/>
              </xs:sequence>
         </xs:complexType>
         <!-- Full: Consultation messages -->
         <xs:complexType name="FullConsultationRequest">
              <xs:sequence>
                   <xs:element name="full.request.list" type="EoriRecordFullRequestList"/>                              
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="FullConsultationResponse">
              <xs:sequence>
                   <xs:element name="full.response.list" type="EoriRecordFullResponseList"/>
              </xs:sequence>
         </xs:complexType>
         <!-- Snapshot: Message structures -->
         <xs:complexType name="EoriRecordSnapshot">
              <xs:sequence>
                   <xs:element name="eori.record.ref" type="EoriNumberRef"/>
                   <xs:element name="tc.number.list" type="TcNumberList" minOccurs="0"/>
                   <xs:element name="economic.operator.details" type="EconomicOperatorDetails"/>
                   <xs:element name="legal.status" type="LegalStatus" minOccurs="0"/>
                   <xs:element name="establishment.address" type="EstablishmentAddress"/>
                   <xs:element name="vat.list" type="VatList" minOccurs="0"/>
                   <xs:element name="contact" type="Contact" minOccurs="0"/>
                   <xs:element name="aeo.certificate.ref" type="AeoCertificateNumber" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordSnapshotRequestList">
              <xs:sequence>
                   <xs:element name="snapshot.request" type="EoriRecordSnapshotRequest" maxOccurs="20"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordSnapshotRequest">
              <xs:sequence>
                   <xs:element name="eori.record.ref" type="EoriNumberRef"/>
                   <xs:element name="applicable.date" type="Date"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordFullRequestList">
              <xs:sequence>
                   <xs:element name="full.request" type="EoriRecordFullRequest" maxOccurs="20"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordFullRequest">
              <xs:sequence>
                   <xs:element name="eori.record.ref" type="EoriNumberRef"/>
                   <xs:element name="consultation.purpose.code" type="ConsultationPurpose" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordSnapshotResponseList">
              <xs:sequence>
                   <xs:element name="snapshot.response" type="EoriRecordSnapshotResponse" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordSnapshotResponse">
              <xs:sequence>
                   <xs:element name="eori.record.snapshot" type="EoriRecordSnapshot"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordFullResponseList">
              <xs:sequence>
                   <xs:element name="full.response" type="EoriRecordFullResponse" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EoriRecordFullResponse">
              <xs:sequence>
                   <xs:element name="eori.record.full" type="EoriRecordFull"/>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>EORI-data.xsd
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
         <xs:annotation>
              <xs:documentation>
                   This XML schema contains the definitions of data
                   elements common to the messages exchanged in the
                   EORI download, upload and consultation
                   functionalities.
              </xs:documentation>
         </xs:annotation>
         <!-- List types -->
         <xs:complexType name="CountryList">
              <xs:sequence>
                   <xs:element name="country" type="Country" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="LegalStatusList">
              <xs:sequence>
                   <xs:element name="legal.status" type="LegalStatus" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="TcNumberList">
              <xs:sequence>
                   <xs:element name="tc.number" type="TcNumberRef" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="VatList">
              <xs:sequence>
                   <xs:element name="vat" type="Vat" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="CertificateInfoList">
              <xs:sequence>
                   <xs:element name="certificate.info" type="CertificateInfo" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>          
         </xs:complexType>     
         <xs:complexType name="ApplicationInfoList">
              <xs:sequence>
                   <xs:element name="application.info" type="ApplicationInfo" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>          
         </xs:complexType>     
         <!-- Complex types -->
         <xs:complexType name="CertificateInfo">
              <xs:sequence>
                   <xs:element name="aeo.certificate.ref" type="AeoCertificateNumber"/>
              </xs:sequence>          
         </xs:complexType>     
         <xs:complexType name="ApplicationInfo">
              <xs:sequence>
                   <xs:element name="aeo.application.ref" type="AeoApplicationNumber"/>
              </xs:sequence>          
         </xs:complexType>     
         <xs:complexType name="AeoCertificateNumber">
              <xs:sequence>
                   <xs:element name="country.code" type="CountryCode"/>
                   <xs:element name="aeo.certificate.type.code" type="AeoCertificateTypeCode"/>
                   <xs:element name="national.number" type="NationalAuthorisationNumber"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="AeoApplicationNumber">
        <xs:sequence>
          <xs:element name="country.code" type="CountryCode"/>
          <xs:element name="national.number" type="ApplicationNumber"/>
        </xs:sequence>
      </xs:complexType>
         <xs:complexType name="Contact">
              <xs:sequence>
                   <xs:element name="phone" type="PhoneNumber" minOccurs="0"/>
                   <xs:element name="fax" type="PhoneNumber" minOccurs="0"/>
                   <xs:element name="email" type="Email" minOccurs="0"/>
                   <xs:element name="name.address" type="NameAddress"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="Country">
              <xs:choice>
                   <xs:element name="country.code" type="CountryCode"/>
                   <xs:element name="country.name" type="CountryName"/>
              </xs:choice>
         </xs:complexType>
         <xs:complexType name="EoriNumberRef">
              <xs:sequence>
                   <xs:element name="country.code" type="CountryCode"/>
                   <xs:element name="national.number" type="EoNationalNumber"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="TcNumberRef">
              <xs:sequence>
                   <xs:element name="country" type="Country"/>
                   <xs:element name="national.number" type="TcNationalNumber"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="EstablishmentAddress">
              <xs:sequence>
                   <xs:element name="language.code" type="LanguageCode"/>
                   <xs:element name="name" type="Name" minOccurs="0"/>
                   <xs:element name="street" type="Street"/>
                   <xs:element name="postcode" type="Postcode" minOccurs="0"/>
                   <xs:element name="city" type="City"/>
                   <xs:element name="country" type="Country"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="LegalStatus">
              <xs:sequence>
                   <xs:element name="language.code" type="LanguageCode"/>
                   <xs:element name="legal.status.description" type="LegalStatusDescription"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="NameAddress">
              <xs:sequence>
                   <xs:element name="language.code" type="LanguageCode"/>
                   <xs:element name="full.name" type="FullName"/>
                   <xs:element name="short.name" type="Name" minOccurs="0"/>
                   <xs:element name="street" type="Street"/>
                   <xs:element name="postcode" type="Postcode" minOccurs="0"/>
                   <xs:element name="city" type="City"/>
                   <xs:element name="country" type="Country"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="Vat">
              <xs:sequence>
                   <xs:element name="country.code" type="CountryCode"/>
                   <xs:element name="number" type="VATNationalNumber"/>
              </xs:sequence>
         </xs:complexType>
         <!-- Simple types -->
         <xs:simpleType name="Accepted">
              <xs:restriction base="xs:int">
                   <xs:pattern value="0|1"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ActivityCode">
              <xs:restriction base="SingleLineString">
          <xs:length value="4"/>
          <xs:pattern value="[0-9]+"/>   
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="NationalAuthorisationNumber">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="29"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="AeoCertificateTypeCode">
              <xs:restriction base="SingleLineString">
                   <xs:length value="4"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ApplicationNumber">
             <xs:restriction base="SingleLineString">
               <xs:minLength value="1"/>
               <xs:maxLength value="29"/>
             </xs:restriction>
           </xs:simpleType>
         <xs:simpleType name="City">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="35"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ConsultationPurpose">
              <xs:restriction base="xs:string">
                   <xs:length value="1"/>
                   <xs:enumeration value="C"/>
                   <xs:enumeration value="Q"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="CountryCode">
              <xs:annotation>
                   <xs:documentation>
                        Country code format
                   </xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="[A-Z][A-Z]"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="CountryName">
              <xs:annotation>
                   <xs:documentation>Country name</xs:documentation>
              </xs:annotation>
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="30"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="Email">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="70"/>
                   <xs:pattern value="\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="EoNationalNumber">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="15"/>
                   <xs:pattern value="\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="TcNationalNumber">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="15"/>
                   <xs:pattern value="\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="LanguageCode">
              <xs:annotation>
                   <xs:documentation>
                        Language code format
                   </xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="[a-z][a-z]"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="LegalStatusDescription">
              <xs:annotation>
                   <xs:documentation>
                        Legal status value
                   </xs:documentation>
              </xs:annotation>
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="50"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="EOFullName">
              <xs:restriction base="xs:string">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="300"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="EOShortName">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="35"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="PhoneNumber">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="2"/>
                   <xs:maxLength value="35"/>
                   <xs:pattern value="\+\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="Postcode">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="9"/>
                   <xs:pattern value="\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="SingleLineString">
              <xs:annotation>
                   <xs:documentation>
                        Single line string: Avoid presence of \n (new
                        line) and \r (return) characters in the string.
                        Note that pattern ".*" is equivalent.
                   </xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="[^\n\r]*"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="FullName">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="100"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="Name">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="35"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="Street">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="35"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="TypePerson">
              <xs:annotation>
                   <xs:documentation>
                        Type of person values as follows: 1-Natural
                        person, 2-Legal person and 3-Association of
                        persons. Values can be updated and retrieved by the CS/RD.
                   </xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:unsignedInt">
                   <xs:totalDigits value="1"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="VATNationalNumber">
              <xs:restriction base="SingleLineString">
                   <xs:minLength value="1"/>
                   <xs:maxLength value="15"/>
                   <xs:pattern value="\p{IsBasicLatin}+"/>
              </xs:restriction>
         </xs:simpleType>
    </xs:schema>xml.xsd
    <?xml version='1.0'?>
    <xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="en">
    <xs:attribute name="lang" type="xs:language"/>
    <xs:attribute name="space" default="preserve">
      <xs:simpleType>
       <xs:restriction base="xs:NCName">
        <xs:enumeration value="default"/>
        <xs:enumeration value="preserve"/>
       </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="base" type="xs:anyURI"/>
    <xs:attributeGroup name="specialAttrs">
      <xs:attribute ref="xml:base"/>
      <xs:attribute ref="xml:lang"/>
      <xs:attribute ref="xml:space"/>
    </xs:attributeGroup>
    </xs:schema>(second part follows...)

    (continuing from above post ...)
    TestXML.xml
    <?xml version="1.0" encoding="utf-8"?>
    <env:envelope id="5555" xmlns="urn:publicid:-:DGTAXUD:EORI:CONSULT:1.0" xmlns:env="urn:publicid:-:DGTAXUD:GENERAL:ENVELOPE:1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <env:header name="Version" value="1.0"/>
      <env:header name="From" value="EOS-CDCO"/>
      <env:header name="Originator" value="BE-EORI"/>
      <env:header name="InReplyTo" value="5554"/>
      <env:transaction id="1">
        <env:header name="InReplyTo" value="1"/>
        <env:status category="ok" location="/envelope[@id=&apos;5554&apos;]/transaction[@id=&apos;1&apos;]">
          <env:status.detail category="info" code="100" location="/envelope[@id=&apos;5554&apos;]/transaction[@id=&apos;1&apos;]/app.message[@id=&apos;1&apos;]">
            <env:business.ref>
              <full.request>
                <eori.record.ref>
                  <country.code>BE</country.code>
                  <national.number>123</national.number>
                </eori.record.ref>
                <consultation.purpose.code>C</consultation.purpose.code>
              </full.request>
            </env:business.ref>
            <env:mmi.message>Ok</env:mmi.message>
          </env:status.detail>
        </env:status>
        <env:app.message id="1">
          <eori.record.full.consultation.response>
            <full.response.list>
              <full.response>
                <eori.record.full>
                  <eori.record.ref>
                    <country.code>FR</country.code>
                    <national.number>123</national.number>
                  </eori.record.ref>
                  <tc.number.list>
                    <tc.number>
                      <country>
                        <country.code>AA</country.code>
                      </country>
                      <national.number>465466</national.number>
                    </tc.number>
                  </tc.number.list>
                  <economic.operator.details>
                    <full.name>a</full.name>
                    <short.name>a</short.name>
                    <establishment.date>19670813</establishment.date>
                    <person.type.code>1</person.type.code>
                    <economic.activity.code>1234</economic.activity.code>
                    <start.date>19670813</start.date>
                    <expiry.date>19670813</expiry.date>
                    <publication.ind>0</publication.ind>
                  </economic.operator.details>
                  <legal.status.list>
                    <legal.status>
                      <legal.status>
                        <language.code>aa</language.code>
                        <legal.status.description>status</legal.status.description>
                      </legal.status>
                      <validity.period>
                        <start.date>19670813</start.date>
                        <end.date>19670813</end.date>
                      </validity.period>
                    </legal.status>
                  </legal.status.list>
                  <establishment.address.list>
                    <establishment.address>
                      <establishment.address>
                        <language.code>aa</language.code>
                        <name>a</name>
                        <street>s</street>
                        <postcode>p</postcode>
                        <city>c</city>
                        <country>
                          <country.code>AA</country.code>
                        </country>
                      </establishment.address>
                      <validity.period>
                        <start.date>19670813</start.date>
                        <end.date>19670813</end.date>
                      </validity.period>
                    </establishment.address>
                  </establishment.address.list>
                  <vat.list>
                    <vat>
                      <country.code>AA</country.code>
                      <number>74455</number>
                    </vat>
                  </vat.list>
                  <contact.list>
                    <contact>
                      <contact>
                        <phone>+ 123</phone>
                        <fax>+ 123</fax>
                        <name.address>
                          <language.code>aa</language.code>
                          <full.name>a</full.name>
                          <short.name>a</short.name>
                          <street>s</street>
                          <postcode>p</postcode>
                          <city>c</city>
                          <country>
                            <country.code>AA</country.code>
                          </country>
                        </name.address>
                      </contact>
                      <validity.period>
                        <start.date>19670813</start.date>
                        <end.date>19670813</end.date>
                      </validity.period>
                    </contact>
                  </contact.list>
                  <aeo.certificate.lifecycle.list>
                    <aeo.certificate.lifecycle>
                      <start.date>19670813</start.date>
                      <end.date>19670813</end.date>
                    </aeo.certificate.lifecycle>
                  </aeo.certificate.lifecycle.list>
                </eori.record.full>
              </full.response>
            </full.response.list>
          </eori.record.full.consultation.response>
        </env:app.message>
      </env:transaction>
    </env:envelope>Here is the script that created the table and registered the schemas
    BEGIN     
       DBMS_XMLSCHEMA.REGISTERSCHEMA(
         SCHEMAURL => 'envelope-consult.xsd',
         SCHEMADOC => XDBURITYPE('/public/xsdfiles/EORI/envelope-consult.xsd').getBlob(),
         LOCAL     => TRUE,
         GENTYPES  => FALSE,
         GENBEAN   => FALSE,
         GENTABLES => FALSE,
         FORCE     => FALSE,
         CSID      => NLS_CHARSET_ID('AL32UTF8'),
         OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML);
    END;
    BEGIN     
       DBMS_XMLSCHEMA.REGISTERSCHEMA(
         SCHEMAURL => 'EORI-consult.xsd',
         SCHEMADOC => XDBURITYPE('/public/xsdfiles/EORI/EORI-consult.xsd').getBlob(),
         LOCAL     => TRUE,
         GENTYPES  => FALSE,
         GENBEAN   => FALSE,
         GENTABLES => FALSE,
         FORCE     => FALSE,
         CSID      => NLS_CHARSET_ID('AL32UTF8'),
         OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML);
    END;
    CREATE TABLE TEST_XML_TABLE
      ENV_CONSULT  SYS.XMLTYPE,
      MSG_TSTAMP   TIMESTAMP(6) WITH TIME ZONE      DEFAULT SYSTIMESTAMP          NOT NULL
    XMLTYPE COLUMN ENV_CONSULT STORE AS SECUREFILE BINARY XML
    (       TABLESPACE PARTYMS10_DATA
      INDEX(TABLESPACE PARTYMS10_INDEX)
    XMLSCHEMA "envelope-consult.xsd" ELEMENT "envelope"
       DISALLOW NONSCHEMA
    TABLESPACE PARTYMS10_DATA
    LOGGING
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    MONITORING
    /And here is the offending statement, together with the reported error
    INSERT
      INTO TEST_XML_TABLE
    VALUES (XDBURITYPE('/public/xmlfiles/EORI/TestXML.xml').getXML(), SYSTIMESTAMP)
    COMMIT
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LSX-00213: only 0 occurrences of particle "abstract.ref", minimum is 1
    Details:
    INSERT
      INTO TEST_XML_TABLE
    VALUES (XDBURITYPE('/public/xmlfiles/EORI/TestXML.xml').getXML(), SYSTIMESTAMP)
    Error at line 1
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LSX-00213: only 0 occurrences of particle "abstract.ref", minimum is 1I am using 11.1.0.7.0, as seen on
    select * from v$version;
    BANNER                                                                         
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production         
    PL/SQL Release 11.1.0.7.0 - Production                                         
    CORE   11.1.0.7.0   Production                                                     
    TNS for 32-bit Windows: Version 11.1.0.7.0 - Production                        
    NLSRTL Version 11.1.0.7.0 - Production                                         
    5 rows selected.Any ideas ? I cannot understand it at all... It seems to relate to the substitutionGroup entries in general, but I can't for the life of me see why :(
    Best Regards
    Philip

  • Weird case involving NTLM, Windows XP and the portal

    I have a very peculiar case here for a few users.
    The users have in common that they are all using windows xp (and just migrated), though most other person (even ones using windows XP do not have the problem).
    We have implemented SSO to the portal, and done this using IIS on the portal servers. In front of that we are using IBM edge loadbalancers.
    From a troubled user perspective, when the he opens the browser against the portal, he gets the portal logon page with a message saying user authentication failed.
    I've found out what happens behind the scene and why the portal fails, but I can't explain it thoroughly.
    The user's browser reaches the portal.company.com address. IIS requests NTLM login and after a few packets, the browser sends the user's userprincipalname ([email protected]) via the NTLM login (i've documented this in the network traces from ethereal). That the browser sends the userprincipalname is the core of the problems, all other user's send the SAMaccountname. The portal reads the NTLM information and parses the userinformation (here the userprincipalname) However, we have configured our portal to use the SAMaccountname when authentication against AD, and therefore the login fails.
    If I use an DNS alias for the portal.company.com addresse, say aliasportal.company.com (actually portal.company.com is an alias for aliasportal.company.com, but don't let that confuse you), the same client that sent userprincipalname earlier, now sends the SAMaccountname and therefore gets SSO (and goes through the loadbalancer). And if I try to access one of the portal servers directly (without going through the load balancer), it also sends SAMaccountname. So basically, there has to be something with the address portal.company.com that makes the user's browser to send the userprincipalname.
    Also, this problem is not tied to the user's profile, because if he uses another pc, it works like a charm.
    <b>If you have any idea at all what could have caused this, please do contribute.. No answers are stupid (in this case). I am especially looking for details to what causes IE to send userprincipalnames, and what causes it to send SAMaccountname.</b>
    Network sniffing(some minor changes to hide information):
    This is the NTLM packet which "wrongly" contains the userprincipalname.
    No.     Time        Source                Destination           Protocol Info
         17 0.107258    xxxxx        xxxxxx        HTTP     GET /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default HTTP/1.1, NTLMSSP_AUTH
    Frame 17 (792 bytes on wire, 792 bytes captured)
    Ethernet II, Src: 00:11:43:7d:52:94, Dst: 00:d0:05:04:8f:fc
    Internet Protocol, Src Addr: xxxxxxxxx , Dst Addr: xxxxxxx
    Transmission Control Protocol, Src Port: 2201 (2201), Dst Port: http (80), Seq: 403, Ack: 741, Len: 738
    Hypertext Transfer Protocol
        GET /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default HTTP/1.1\r\n
        Accept: /\r\n
        Accept-Language: da\r\n
        Accept-Encoding: gzip, deflate\r\n
        User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)\r\n
        Host: portal.company.com\r\n
        Connection: Keep-Alive\r\n
        Authorization: NTLM TlRMTVNTUAADAAAAGAAYAHoAAACkAKQAkgAAAAAAAABIAAAAIAAgAEgAAAASABIAaAAAAAAAAAA2AQAABYKIogUBKAoAAAAPZABqAHcAbABAAHMAdABhAHQAbwBpAGwALgBjAG8AbQBQAEMALQAzADkAMwA3ADEANAAjkf2i0gE5YfLWa6LaFWq/QOJVBMBK+X/0eZk41NRM7wDew37l6/jmAQE
            NTLMSSP
                NTLMSSP identifier: NTLMSSP
                NTLM Message Type: NTLMSSP_AUTH (0x00000003)
                Lan Manager Response: 2391FDA2D2013961F2D66BA2DA156ABF40E25504C04AF97F
                NTLM Response: F4799938D4D44CEF00DEC37EE5EBF8E60101000000000000...
                Domain name: NULL
                User name: [email protected]
                Host name: PC-393714
                Session Key: Empty
                Flags: 0xa2888205
        \r\n
    And this is the packet against the dns alias which works
    No.     Time        Source                Destination           Protocol Info
         17 0.103528    xxxxx          xxxxx         HTTP     GET /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default HTTP/1.1, NTLMSSP_AUTH
    Frame 17 (788 bytes on wire, 788 bytes captured)
    Ethernet II, Src: 00:11:43:7d:52:94, Dst: 00:d0:05:04:8f:fc
    Internet Protocol, Src Addr: xxxx, Dst Addr: xxxx
    Transmission Control Protocol, Src Port: 1825 (1825), Dst Port: http (80), Seq: 403, Ack: 741, Len: 734
    Hypertext Transfer Protocol
        GET /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default HTTP/1.1\r\n
        Accept: /\r\n
        Accept-Language: da\r\n
        Accept-Encoding: gzip, deflate\r\n
        User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)\r\n
        Host: aliasportal.company.com\r\n
        Connection: Keep-Alive\r\n
        Authorization: NTLM TlRMTVNTUAADAAAAGAAYAHgAAACkAKQAkAAAABYAFgBIAAAACAAIAF4AAAASABIAZgAAAAAAAAA0AQAABYKIogUBKAoAAAAPUwBUAEEAVABPAEkATAAtAE4ARQBUAEQASgBXAEwAUABDAC0AMwA5ADMANwAxADQAyhO3U1uCz0jn55samc+TUJmnyefvp0tXQN0VMytYEG3YDADHwRicxwEBAAA
            NTLMSSP
                NTLMSSP identifier: NTLMSSP
                NTLM Message Type: NTLMSSP_AUTH (0x00000003)
                Lan Manager Response: CA13B7535B82CF48E7E79B1A99CF935099A7C9E7EFA74B57
                NTLM Response: 40DD15332B58106DD80C00C7C1189CC70101000000000000...
                Domain name: COMPANY-NET
                User name: DAPA
                Host name: PC-393714
                Session Key: Empty
                Flags: 0xa2888205
        \r\n
    I'll be truely impressed if anyone solves this one!

    Hi Dagfinn,
    There are a few things I would check in the Internet explorer settings on the client, namely :
    -The security zones (which addresses are in Intranet, Trusted sites, etc.)
    -Check in the security settings if automatic logon with current username is enabled.
    -Look if "Enable integrated Windows authentication" is enabled in the advanced settings.
    Are you using Kerberos authentication? There's a long article on Microsoft's website about troubleshooting Kerberos errors which might give a few clues :
    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

  • Sql case statement for parametes

    I am using sort parameters in the stored procedure
    the following is my case statment
    CASE When @SORT_1 = 'CUSTOMER'
                     Then ar_ivhdr_tbl.EN_CUST_KEY
                     When @SORT_1 = 'BILLTO'
                    Then ar_bill_tbl.ar_bill_name
                     Else ' ' END SORTKEY
    what i would like to do is
    have the sort key sort by 2 fields so instead of just the customer sort sorting the customer field
    i would like it to sort customer and bill to
    this is the syntax i tried but sql doesnt like it
    CASE When @SORT_1 = 'CUSTOMER'
    Then ar_ivhdr_tbl.EN_CUST_KEY,ar_bill_tbl.ar_bill_key
    When @SORT_1 = 'BILLTO'
    Then ar_bill_tbl.ar_bill_name, date
    Else ' ' END SORTKEY
    syntax issues, any ideas?

    Hi Sharon,
    Your syntax is off.  Not sure what database you are using by it should look something like:
    CASE @SORT_1
    When 'CUSTOMER' Then ar_ivhdr_tbl.EN_CUST_KEY,ar_bill_tbl.ar_bill_key
    When 'BILLTO' Then ar_bill_tbl.ar_bill_name, date
    Else ' '
    END
    Good luck,
    Brian

Maybe you are looking for