Error while validating flat file schema

Hi,
I have the flat file schema which is character delimited on '|'. It has Details and Tralier. Trailer starts with a "Tag Identifier" as 'T' and can have one value as "Total Records" i.e. T|3. Details is also delimited on the base of '|' and but has no "Tag Identifier".
Details have min occurs as 0.
Schema:
Eg of the valid values:
21788367|EN
21848269|EN
22004225|EN
T|3
This should also be the valid value (with no details and only trailer):
T|0
But, when I'm trying to validate this. I'm getting error:
Unexpected data found while looking for:
'\r\n'
The current definition being parsed is User_details. The stream offset where the error occurred is 2. The line number where the error occurred is 1. The column where the error occurred is 2.
I think it is trying to find Details record also. What setting I need to change?
Please help.
Kunal G

This is my schema:
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns="http://BTS_POC.Users" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" targetNamespace="http://BTS_POC.Users" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
<b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true" allow_early_termination="false" early_terminate_optional_fields="false" allow_message_breakup_of_infix_root="false" compile_parse_tables="false" root_reference="Users_Root" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Users_Root">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="hex" child_delimiter="0xD 0xA" child_order="infix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element minOccurs="0" maxOccurs="unbounded" name="Users_Detail">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="char" child_delimiter="|" child_order="infix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Name" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="Id" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="2" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Users_Trailer">
<xs:annotation>
<xs:appinfo>
<b:recordInfo tag_name="T" structure="delimited" child_delimiter_type="char" child_delimiter="|" child_order="prefix" sequence_number="2" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element name="TotalNumber" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Kunal G

Similar Messages

  • Getting error while loading Flat File

    Hello All,
    I am getting error while loading flat file. Flat file is a CSV file.
    Value ',,,,,,,,' of characteristic 0DATE is not a number with 000008 spaces
    Data seprator  |
    Escape sign    ;
    It has 23708 entries , it s loading successfully till 23 665 entries
    Besides when checked in PSA
    for record having entries >23667 has calender day as ,,,,,, where as rest entries are  having date
    Besides when i checked in Flat file ,the total number of rows is 23,667 is there but i wonder why it has got 23,708 in
    RSMO
    Could you please let me know how to correct.
    regards
    path

    Hi,
    For date column you should maintain YYYYMMDD formate Eg: 20090601, kepp cursor on date column and right click and Formate >Custome>make it 00000000 then save teh file as .CSV . First type values on column and do like this formate and save it and without opening it load it. Once you open it you losw 00000000 formate you need to give again the same formate.
    Settings in Infopackage:
    Data Format  = CSV
    Data Separator = ,
    Escape Sign = ;
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/01ed2fe3811a77e10000000a422035/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6567e07211d2acb80000e829fbfe/content.htm
    Thanks
    Reddy

  • Error while loading flat file into DSO

    Hi
    I am loading data from a flat file into a DSO. My fields in the flat file are Trans_Dt, (CHAR) Particulars (CHAR), Card_Name, (CHAR) Exps_Type, (CHAR)
    Debit_Amount,Credit_Amount,***._Amt,Open_Bal_Check_Acnt, (CURR)
    0Currency (CHAR)
    In the proposal tab apart from the above mentioned fields 3 additional fields viz, field 10, field 11, and field 12 have come. How did these 3 additional fields come when I don't have any additional fields in my flat file? I've deleted these extra 3 fields though.
    When I activate the DataSource it is getting activated but then I get the message 'Data structures were changed. Start transactions before hand'. What does this message mean?
    When I hit the 'Read preview data' button it doesn't show me any data and gives me the error Missing reference to currency field / unit field for the fields Debit_Amount,Credit_Amount,***._Amt,Open_Bal_Check_Acnt
    How do I create a reference field to the above mentioned fields?
    Earlier I didn't have the 0Currency field in the flat file. But in my DSO while creating the key figures by default the 0Currency field also got created which is quite obvious. Now while activating the transformations I was getting a message that 'No source field for the field 0Currency'. Hence I had to create a new field in my flat file called 0Currency and load it with USD in all rows.
    Please help me in loading this flat file into the DSO.
    Thank you.
    TR.

    Hi guys,
    Thanks a lot for your answers. with your help I could see the data in the 'Read preview data' and schedule the load. I did use all the Info objects in the info objects column of the data source to load the flat file.
    The data is in PSA successfully without any issues. but when I executed the DTP it failed with errors.
    Earlier there was no mapping from Currency field in source to the all the key figure fields in the target in the transformation. The mapping was only from Currency to 0CURRENCY but still the transformation got activated. As per your advise I mapped Currency field to the remaining Key Figure fields but then I am getting the error
    'Source parameter CURRENCY is not being used'
    Why is that so?
    list of Errors after executing the DTP:
    1. 'Record filtered because records with the same key contain errors'
    Message:
    Diagnosis: The data record was filtered out becoz data records with the same key have already been filtered out in the current step for other reasons and the current update is non-commutative (for example, MOVE). This means that data records cannot be exchanged on the basis of the semantic key.
    System Response: The data record is filtered out; further processing is performed in accordance with the settings chosen for error handling.
    Procedure: Check these data records and data records with the same key for errors and then update them.
    Procedure for System administration
    Can you please explain this error and how should I fix this error.
    2. Exception input_not_numeric; see long text - ID RSTRAN
    Diagnosis: An exception input_not_numeric was raised while executing function module RST_TOBJ_TO_DERIVED_TOBJ.
    System Response
    Processing the corresponding record has been terminated.
    Procedure
    To analyse the cause, set a break point in the program of the transformation at the call point of function module RST_TOBJ_TO_DERIVED_TOBJ. Simulate the data transfer process to investigate the cause.
    Procedure for System Administration
    What does this error mean? How do I set a breakpoint in the program to fix this error inorder to load the data?
    What does Procedure for System Administration mean?
    Please advise.
    Thank you.
    TR.

  • Error while loading Flat file to the table (ORA-00936: missing expression)

    lat file Hi Gurus
    Receiving the following error while trying to load of flat file to the database :
    ODI-1228: Task test_file_load (Integration) fails on the target ORACLE connection DEMO_STAGE.
    Caused By: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1079)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3937)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
         at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:163)
         at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:102)
         at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:1)
         at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:662)
    The file which I have tried to load is : SRC_SALES_PERSON and teh table structure is
    CREATE table "TRG_SALES_PERSON"(
    "SALES_PERSON_ID" NUMBER(8,0) NOT NULL,
    "FIRST_NAME" VARCHAR2(80),
    "LAST_NAME" VARCHAR2(80),
    "DATE_HIRED" VARCHAR2(80),
    "DATE_UPDATED" DATE NOT NULL)
    Knowledge module used are
    LKM File to SQL
    IKM SQL Incremental Update
    We rae using ODI 11g R2 ...
    Thanks and reallty appreciate any help in thsi regard.

    HI there,
    I am facing the same issue while loading data from SRC_SALES_PERSON(flat file) to TRG_CUSTOMER.
    I dont see any errors in the steps however the data is not laoded finally. Here are the sql commands
    **On source**
    select     ID     C11_ID,
         LASTNAME     C9_LASTNAME
    from      TABLE
    /*$$SNPS_START_KEYSNP$CRDWG_TABLESNP$CRTABLE_NAME=SRC_SALES_PERSONSNP$CRLOAD_FILE=D:\Pratima\Softwares\ODI\ofm_odi_companion_generic_11.1.1.5.1_disk1_1of1[1]\demo\oracledi-demo\oracledi\demo\file/SRC_SALES_PERSON.txtSNP$CRFILE_FORMAT=FSNP$CRFILE_SEP_FIELD=0x0009SNP$CRFILE_SEP_LINE=0x000D0x000ASNP$CRFILE_FIRST_ROW=0SNP$CRFILE_ENC_FIELD=SNP$CRFILE_DEC_SEP=SNP$CRSNP$CRDWG_COLSNP$CRCOL_NAME=IDSNP$CRTYPE_NAME=STRINGSNP$CRORDER=1SNP$CRLINE_OFFSET=1SNP$CRLENGTH=11SNP$CRPRECISION=11SNP$CRACTION_ON_ERROR=0SNP$CRSNP$CRDWG_COLSNP$CRCOL_NAME=FIRSTNAMESNP$CRTYPE_NAME=STRINGSNP$CRLINE_OFFSET=12SNP$CRLENGTH=50SNP$CRPRECISION=50SNP$CRSNP$CRDWG_COLSNP$CRCOL_NAME=LASTNAMESNP$CRTYPE_NAME=STRINGSNP$CRLINE_OFFSET=62SNP$CRLENGTH=50SNP$CRPRECISION=50SNP$CRSNP$CRDWG_COLSNP$CRCOL_NAME=DATE1SNP$CRTYPE_NAME=STRINGSNP$CRLINE_OFFSET=112SNP$CRLENGTH=20SNP$CRPRECISION=20SNP$CR$$SNPS_END_KEY*/
    On Target
    insert into STAGING.C$_0TRG_CUSTOMER
         C11_ID,
         C9_LASTNAME
    values
         :C11_ID,
         :C9_LASTNAME
    The actual code at source fails however the step is in green.
    Thanks in Advance,
    Pratima

  • Error while uploading flat file

    Hello
    My flat file(.csv) has 3 columns.But when i am uploading and when i check Master data, it just shows me the first column.Why is it so?
    When i maintain Master data, do i have to maintan attr, text and hierarchies?In mapping and transfer rules?What should I map, Attr or text or hierarchies or all the 3?
    Thanks

    Hi,
    Let me make some guesses about your situation.
    You use an IS with Direct Update for text master data upload. In this case in Master Data maintenance you'll see the IO's code and its attributes. To see IO's texts you need to click on a 'Text' icon, with a pencil or glasses.
    For direct update of master data you need to create an IS with direct update (the last radio button in the 'Create Infosource' screen).
    Then right click on an IS - Assign Datasource, choose flat file source system, confirm all system 'Save changes' proposals.
    In Infosource change screen press 'Activate'.
    Number of datasources for a master data will depend on the settings for the IO. If this IO has master data, texts and hierarchies, then you'll have 3 DSs.
    In the 'Datasource' field of the screen you can see what is this DS for. Click on this field and choose another DS. Press 'Activate'. Do it the 3rd time if you have 3 DSs.
    Then during an infopackage creation you'll be able to choose an option (Master data attributes, texts, hierarchies) and upload the appropriate data.
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov

  • Getting error while loading flat file into table.

    I am using ODI 11 and i am trying to load data in oracle database table using source as flat .txt file .
    When i execute the interface , i am getting below errors.
    ODI-1217: Session INF_FILE2TAB (31022) fails with return code 7000.
    ODI-1226: Step INF_FILE2TAB fails after 1 attempt(s).
    ODI-1240: Flow INF_FILE2TAB fails while performing a Loading operation. This flow loads target table PARTNER.
    Caused By: org.apache.bsf.BSFException: exception from Jython:
    Traceback (most recent call last):
    File "<string>", line 44, in <module>
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
         at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1074)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2224)
         at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2168)
         at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:333)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
    java.sql.SQLException: java.sql.SQLException: ORA-06564: object DAT_DIR does not exist
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2458)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
         at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:540)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
         at java.lang.Thread.run(Thread.java:662)
    Please let me know pointers on this.

    Yes,after your sugestion i have created ODI agent and tested the file system connection in topology. It was connected successfully.
    but when i tried again for file to table load. Again got below error.
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (most recent call last):
    File "<string>", line 44, in <module>
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
         at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1074)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2224)
         at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2168)
         at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:333)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
    java.sql.SQLException: java.sql.SQLException: ORA-06564: object DAT_DIR does not exist
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2458)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
         at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:540)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
         at java.lang.Thread.run(Thread.java:662)
    Please suggest.

  • Error while Creating Flat file Source System

    Hi Friends,
    The message "No entry for BW_USER in table RSADMIN available" is shown when I try to create a Source System for File System(Manual Metadata, Data using File Interface). Could somebody help me please.
    Thanks in advance.
    Hanuma Reddy

    Hi,
    I have solved this problem from SDN by seeing below reply to some others question. Thanks Ajay.
    I think this problem comes if you have used more than one client in BW (for example if you logged on to 000 and ran admin workbench initially after installation, and then if you prepared another client for use as BW client).
    Look at OSS note 410952, it mentions of the same error. The fix as mentioned in the note is as follows
    Symptom
    You receive the error message when trying to connect a source system to the Admininistrator Workbench:
    "No entry for BW_USER in table RSADMIN exists" (message number RSAR 059).
    Additional key words
    RSAR059, APO, RSADMINA
    Cause and prerequisites
    In table RSADMINA, the BW user is not maintained for ALE.
    Solution
    Maintain the entry using the following path:
    Call Administrator workbench (transaction RSA1).
    From the 'Settings' menu, select Global Settings'.
    If an entry already exists in the field "BW user for ALE", delete this.
    Enter the correct names for the BW users in this field.
    Save the entry.
    You must restart the Administrator Workbench (RSA1) now.
    The source system can now be linked without errors.

  • Runtime Error while loading Flat file in to ODS

    Hi Friends,
    I have 11 records in flatfile and I am loading it from PC. when I see in preview I can see.
    But when I load it ,it gives me short dump. request status is in amber..
    Please help me as this is urgent support issue.
    The ABAP Runtime Error is
    Runtime Error          CALL_FUNCTION_CONFLICT_TYPE
    Except.                CX_SY_DYN_CALL_ILLEGAL_TYPE
    Date and Time          02.01.2008 13:55:38       
    What happened?                                                                   
        Error in ABAP application program.                                                                               
    The current ABAP program "GP44UKXZB8WE74CAKI38CZ0B586" had to be terminated  
         because one of the                                                          
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    A function module was called incorrectly.                                                                               
    What can you do?                                                                 
        Print out the error message (using the "Print" function)                     
        and make a note of the actions and input that caused the                     
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.               
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer     
         termination messages, especially those beyond their normal deletion         
        date.                                                                               
    is especially useful if you want to keep a particular message.

    Hi Sudhakar,
    This seems to be a type conflict error. It occurs when you assign for example a char field to a numc field. So, I suggest you check your mappings and see if there is any type mismatch in the info objects. Hope it helps.
    Thanks and Regards
    Subray Hegde

  • Error in validating XML against schema

    Hi am getting some critical errors while Validating XML against schema
    error is:
    cvc-elt.1: Cannot find the declaration of element 'position' , here <position> is my root element.
    my code is as follows:
    package com.glemser.xmLabeling.library.component.spl;
    import com.documentum.com.DfClientX;
    import com.documentum.com.IDfClientX;
    import com.documentum.fc.client.IDfClient;
    import com.documentum.fc.client.IDfSession;
    import com.documentum.fc.client.IDfSessionManager;
    import com.glemser.common.helper.OperationHelper;
    import org.xml.sax.*;
    import org.xml.sax.helpers.DefaultHandler;
    import javax.xml.parsers.ParserConfigurationException;
    import javax.xml.parsers.SAXParserFactory;
    import java.io.CharArrayWriter;
    import java.io.IOException;
    import java.io.InputStream;
    public class Test {
    static IDfSession m_session;
    public static void main(String[] args) {
    try {
         new Test().validate();
    } catch (Exception e) {
    e.printStackTrace();
    private XMLReader xmlReader;
    private DefaultHandler handler; // Defines the handler for this parser
    private boolean valid = true;
    public void validate() {
    try {
    SetXML setXML = new SetXML();
    OperationHelper operation = new OperationHelper();
    String splObjPath = "C://Documents and Settings/dparikh/My Documents/xmLabelingStage/Test.xml";//operation.executeExportOperation(m_session, new DfId(m_objectId), true);
    SAXParserFactory spf = SAXParserFactory.newInstance();
    spf.setNamespaceAware(false);
    spf.setValidating(true);
    spf.setFeature("http://xml.org/sax/features/validation", true);
    spf.setFeature("http://apache.org/xml/features/validation/schema", true);
    spf.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
    if (spf.isValidating()) {
    System.out.println("The parser is validating");
    javax.xml.parsers.SAXParser sp = spf.newSAXParser();
    sp.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");
    sp.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation", "file://C:/Documents and Settings/dparikh/My Documents/xmLabelingStage/Test.xsd");
    System.out.println("The parser is validating1");
    //Create XMLReader
    xmlReader = sp.getXMLReader();
    xmlReader.setFeature("http://apache.org/xml/features/validation/schema", true);
    xmlReader.setEntityResolver(new SchemaLoader());
    ContentHandler cHandler = new MyDefaultHandler();
    ErrorHandler eHandler = new MyDefaultHandler();
    xmlReader.setContentHandler(cHandler);
    xmlReader.setErrorHandler(eHandler);
    System.out.println("The parser is validating2");
    parseDocument(splObjPath);
    } catch (SAXException se) {
    se.printStackTrace();
    } catch (ParserConfigurationException e) {
    e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates.
    public void parseDocument(String xmlFile) {
    try {
    xmlReader.parse(xmlFile);
    if (valid) {
    System.out.println("Document is valid!");
    } catch (SAXException e) {
    e.printStackTrace();
    } catch (IOException e) {
    e.printStackTrace();
    } catch (Exception e) {
    e.printStackTrace();
    class MyDefaultHandler extends DefaultHandler {
    private CharArrayWriter buff = new CharArrayWriter();
    private String errMessage = "";
    /* With a handler class, just override the methods you need to use
    // Start Error Handler code here
    public void warning(SAXParseException e) {
    System.out.println("Warning Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
    public void error(SAXParseException e) {
    errMessage = new String("Error Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
    System.out.println(errMessage);
    valid = false;
    public void fatalError(SAXParseException e) {
    errMessage = new String("Error Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
    System.out.println(errMessage);
    valid = false;
    public class SchemaLoader implements EntityResolver {
    public static final String FILE_SCHEME = "file://";
    public InputSource resolveEntity(String publicId, String systemId) throws SAXException {
    if (systemId.startsWith(FILE_SCHEME)) {
    String filename = systemId.substring(FILE_SCHEME.length());
    InputStream stream = SchemaLoader.class.getClassLoader().getResourceAsStream(filename);
    return new InputSource(stream);
    } else {
    return null;
    My XML and XSD are as below:
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="position" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="position_number" type="xsd:string"/>
    <xsd:element name="position_title" type="xsd:string"/>
    <xsd:element name="report_to_position" type="xsd:string"/>
    <xsd:element name="incumbent" type="xsd:string"/>
    <xsd:element name="operation" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <position xsi:schemaLocation="Test.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <position_number>12345</position_number>
    <position_title>Sr. Engr</position_title>
    <report_to_position>23456</report_to_position>
    <incumbent>23456</incumbent>
    <operation>INSERT</operation>
    </position
    Please help me out

    --> Could not find cached enumeration value Custom.CI.Enum.PeripheralDevice.Printer for property Type, class BMC.Custom.CI.PeripheralDevice in enumeration cache.
    You must specify either the Name or Guid of an enumeration of type Custom.CI.Enum.PeripheralDevice.Type.
    Be sure that you are specifying the Name property of the enumeration value you want to set, and not the DisplayName; the Internal Name is something like "IncidentCategoryEnum.Category" for out of the box enumerations, or ENUM.210ADA2282FDABC3210ADA2282FDABC
    for enumerations created in the console.
    you can check this by finding the enumeration in the XML or by using the the
    SMLets commandlet
    Get-SCSMEnumeration | ?{$_.DisplayName –eq “Printer”}
    and then checking your value with
    Get-SCSMEnumeration -Name "ENUM.210ADA2282FDABC3210ADA2282FDABC"
    and see if you get the right displayname back

  • Error while buliding biztalk flat file schema

    Hi Everyone,
    am using a flat file schema i had imported a schemas.
    but when i bulit schemas solution am getting this error.
    Only one SchemaInfo, GroupInfo, RecordInfo or FieldInfo is allowed in the appInfo block

    Hi Rajiv,
    Your error is related is much more related to your own flat file where there is some restriction over grouping the record . 
    I would suggest to go through your Flat File Schema Wizard again to see is there inconsistency you have done while generating schema .
    I would also suggest you to look over below MSDN Articles
    Walkthrough: Creating a Flat File Schema From a Document Instance
    Creating Schemas Using BizTalk Flat File Schema Wizard
    BizTalk Server: Transform text files (Flat Files) into XML – by @Sandro
    Thanks
    Abhishek

  • Object reference not set to an instance of an object error when generating a schema using flat file schema wizard.

    I have a csv file that I need to generate a schema for. I am trying to generate a schema using flat file schema wizard but I keep getting "Object reference not set to an instance of an object." error when I am clicking on the Next button after
    specifying properties of the child elements on the wizard. At the end I get schema file generated but it contains an empty root record with no child elements.
    I thought may be this is because I didn't have my project checked out from the Visual SourceSafe db first but I tried again with the project checked out and got the same error.
    I also tried creating a brand new project and generating a schema for it but got the same error.
    I am not sure what is causing Null Reference exception to be thrown and there is nothing in the Windows event log that would tell me more about the problem.
    I am using Visual Studio 2008 for my BizTalk development.
    I would appreciate if some has any insides on this issue.

    Hi,
    To test your environment, create a new BizTalk project outside of source control.
    Create a simple csv file on the file system.
    Name,City,State
    Bob,New York,NY
    Use the Flat file schema Wizard to create the flat file schema from your simple csv instance.
    Validate the schema.
    Test the schema using your csv instance.
    This will help you determine if everything is ok with you environment.
    Thanks,
    William

  • Running reports on Flat file schemas when OBIEE server is on Unix

    Hello
    we would like to know how Unix OBIEE work with flat file. Currently, in our environment our Development and Production OBIEE are running on Unix AIX machine while our local OBIEE environment is on Windows.
    As our devolepment and configuration goes, we have encounter situations where the flat file schema that were working well on Windows OBIEE server will not run on Unix. The flat files are located on a windows file directory and could be successfully imported into OBIEE throu Admin Tool.
    However, when updating rowcounts or running reports on answers in Unix OBIEE it would return errors:
    State: HY000. Code: 472983136. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 16023] The ODBC function has returned an error. The database may not be available, or the network may be down. (HY000)
    The same activity is working fine on our local machine when OBIEE is on windows..
    We would like to get some help on how to work with flat files when OBIEE is runing on Unix..

    is this the same question as [this one|http://forums.oracle.com/forums/message.jspa?messageID=4018049#4018049] ?

  • Error while reading wsdl file

    I created and deployed a BPEL process with a JMS adapter and DB adapter.
    I have tested this and it works fine.
    After a few days, I try to open the project and the BPEL process, and click on the DB
    adapter and it throws an exception on the designer :
    "Error while reading wsdl file ... (wsdl file name) NULL Exception"
    This is hard to debug as the exception does not provide any info, NULL.
    This has happened several times for my project. The next time the JMS adapter hit the
    same exception while opening on designer. This one I notice happened after I imported
    a new schema file (xsd) into the BPEL process.
    Only way around that I have for this currently is to delete and recreate the adapters, which as time
    consuming as I have to re-create and re-assign a lot of the activities.
    Has anyone encountered this and is there a way to fix this without deleting/recreating the adapters ?
    Thanks.

    I experienced the same issue and found the cause and a workaround;
    "Error while reading wsdl file …. Exception: null"
    http://www.petervannes.nl/files/b7c08911ce3cde3677e2182bbc5f032a-47.php
    Edited by: 944333 on Jul 3, 2012 10:24 PM

  • Error while importing .xml file in Datatype

    Hi SDN,
    I am getting this error while importing .xml file in Datatype.
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
    Actually I have created datatype in my development box..
    but my client doesn't want to develop in development box.
    so i have exported that datatype as xsd from datatype editor.
    and while importing into sandbox datatype editor i am getting this error..
    Any help please......

    Hi Rajeev,
    now i have an .xml file its not importing into datatype...
    error is
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
      <?xml version="1.0" encoding="UTF-8" ?>
      <xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:complexType name="DT_PLANNINGSCHEDULE">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
      </xsd:annotation>
      <xsd:sequence>
      <xsd:element name="PlanningSchedule_Output">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PlanningScheduleHeader">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleIssueDate" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="SchedulePurpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Purpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PurposeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleTypeCoded" type="xsd:string">
    <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="SellerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipFromParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipToParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Language">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LanguageCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationGroupedPlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Location">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BasePlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LineItemNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerLineItemNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemIdentifiers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNumbers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="StandardPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ProductIdentifier" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemDescription" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfItemReferences">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceTypeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="PrimaryReference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Reference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="RefNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ForecastFrequencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="CommitmentLevelCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleDates">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfDateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Date">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="DateQualifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleQuantities">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfQuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityValue" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="UnitOfMeasurement">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="UOMCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>

  • Error while retreiving xml file from database

    Hi-
    I am trying to configure Planning and getting the following error message at instance configuration step:
    "Error while retreiving xml file from database"
    We looked at PlanningSystemDB.properties, changes server name to its ip, reinstalled planning, made sure both auth methods are selected (sql server and windows), created new relational repository.. still the same error.
    Here is the contents of the configtool error file:
    (Dec 11, 2008, 04:36:44 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:37:09 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:38:41 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:07 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:12 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:22 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:40:46 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
    (Dec 11, 2008, 04:41:05 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
    (Dec 11, 2008, 04:48:28 PM), com.hyperion.cis.DBConfigurator, ERROR, Invalid SQL statement: begin transaction IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PROPERTIES]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PROPERTIES IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APP_CLUSTER_DTL]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APP_CLUSTER_DTL IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APPLICATION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APPLICATION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_DATASOURCE]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_DATASOURCE IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_CLUSTER]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_CLUSTER IF EXISTS (select * from sysobjects where id = object_id(N'[HSP_ACTION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSP_ACTION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PI_INFO]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PI_INFO commit begin transaction CREATE TABLE HSP_ACTION ( ID INTEGER NOT NULL IDENTITY, CONSTRAINT PK_HSP_ACTION PRIMARY KEY(ID) , FROM_ID INTEGER, TO_ID INTEGER, ACTION_ID INTEGER, OBJECT_TYPE INTEGER, PRIMARY_KEY VARCHAR(255), ACTION_TIME DATETIME ); CREATE TABLE HSPSYS_CLUSTER ( CLUSTER_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), CONSTRAINT PK_HSPCLUSTER PRIMARY KEY(CLUSTER_ID) ); CREATE TABLE HSPSYS_DATASOURCE ( DATASOURCE_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), APP_ID INTEGER, RDB_SERVER_URL VARCHAR(255), RDB_TYPE VARCHAR(255) NOT NULL, RDB_CATALOG_NAME VARCHAR(255) NOT NULL, RDB_USER VARCHAR(255) NOT NULL, RDB_PASSWORD VARCHAR(255), RDB_DRIVER VARCHAR(255) NOT NULL, ESS_SERVER VARCHAR(255) NOT NULL, ESS_USER VARCHAR(255) NOT NULL, ESS_PASSWORD VARCHAR(255), CONSTRAINT PK_HSPDTASRC PRIMARY KEY(DATASOURCE_ID) ); CREATE TABLE HSPSYS_APPLICATION ( APP_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), DATASOURCE_ID INTEGER NOT NULL, CONSTRAINT FK_HSPAPP_DSID FOREIGN KEY(DATASOURCE_ID) REFERENCES HSPSYS_DATASOURCE, VERSION VARCHAR(255) NOT NULL, CONSTRAINT PK_HSPAPP PRIMARY KEY(APP_ID) ); CREATE TABLE HSPSYS_APP_CLUSTER_DTL ( APP_ID INTEGER NOT NULL , CONSTRAINT FK_HSP_APP_ID FOREIGN KEY (APP_ID) REFERENCES HSPSYS_APPLICATION , CLUSTER_ID INTEGER NOT NULL, CONSTRAINT FK_HSPCS_CLID FOREIGN KEY(CLUSTER_ID) REFERENCES HSPSYS_CLUSTER, CONSTRAINT PK_APP_CLSTR_DTL PRIMARY KEY(CLUSTER_ID, APP_ID) ); CREATE TABLE HSPSYS_PROPERTIES ( PROPERTY_ID INTEGER NOT NULL, OBJECT_ID INTEGER NOT NULL, PROPERTY_NAME VARCHAR(255) NOT NULL, PROPERTY_VALUE VARCHAR(255), CONSTRAINT PK_HSPPROP PRIMARY KEY(PROPERTY_ID, OBJECT_ID, PROPERTY_NAME) ); CREATE TABLE HSPSYS_PI_INFO ( XML_FILE NTEXT NOT NULL ); commit
    (Dec 11, 2008, 04:50:32 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    Thanks for any help.

    After spending 2+ hrs with Hyperion Support nothing got resolved.. Just to give more background on this problem, we originally reconfigured all Hyperion components to use different SQL server, that is when the problem started happening as soon as we got to Planning Instance Configuration. Could this be the situations when old server name is still somewhere in the system?.. Could this be Shared Services problem.
    Here is another quote from SharedServices_Security.log
    2008-12-12 15:08:48,249 [http-58080-Processor1] WARN com.hyperion.css.spi.impl.nv.NativeProvider.getHierarchicalRoleTree(Unknown Source) - Exception getting Child Roles in hierarchy due to Illegal or invalid id.dflt passed in. Please check the argument.
    2008-12-12 15:31:18,121 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
    2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
    2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 1016
    2008-12-12 15:31:30,823 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
    2008-12-12 15:31:41,229 [http-58080-Processor4] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:31:41,229 [http-58080-Processor4] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
    2008-12-12 15:38:01,938 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
    2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
    2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 813
    2008-12-12 15:38:35,453 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
    2008-12-12 15:42:09,776 [http-58080-Processor3] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:42:09,776 [http-58080-Processor3] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
    2008-12-12 15:42:09,776 [http-58080-Processor2] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:42:09,776 [http-58080-Processor2] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.

Maybe you are looking for

  • Replication of Item Categories from R/3 to CRM

    Hi, How can we replicate Item Categories and Item Category Determination from R/3 to CRM. Could you please let me know detail steps as I am new to middleware. Thanks in advance. Sai

  • Retrieve Client IP Address in a Oracle WebServices Manager Custom Policy

    Hi everybody, For some reasons i had to implement a custom policy in the OWSM, to restrict the access to webservices by Client IP Addresses. I´ve been following the examples for custom policies mentioned in the books: "Oracle Web Services Manager, Or

  • Sub-Contracting Challan Posting Date

    Dear Experts, We have a business requirement to prevent users from changing the 57F4 Challan Posting date while creation of Challan in J1IF01Transaction. Is it possible through configuration or should we go in for an user exit? Thanks, Srinath

  • IPOD AS HARD DRIVE FOR CONTACTS & CALENDER

    I am trying to set my IPOD as a hard drive for my contacts and calender but it doesn't work. I have clicked on the enable key after pluging in the IPOD but nothing happens. The only time i see the IPOD contacts folder is when i click on the e:drive.

  • Landscape Problems with Crystal Reports 2008 SP3

    My initial install of Crystal Reports 2008 was SP2 (12.2.0.290).  After installing SP3 and Fix Pack 3.3, I started to experience problems with reports in landscape orientation. The reports are set up as 11x8.5 in landscape.  They are loaded into a th