Error while import schema in HANA DB

Hi...
I am trying to perform an export-import of a HANA DB user instance at schema level including all objects (in my case tables and synonyms) and data.
Export and Import works very well except importing a schema which contains a synonym referred to other existing schema .
Here is a test case
- Schema A with a Table and Schema B to contain a synonym for schema A's table.
- Exported both schemas to CSV which is done successfully and everything looked ok in export location.
- Imported Schema A and then Schema B with the following command.
Command:
IMPORT "<bkup_schema>"."*" FROM '<bkp_location>' WITH RENAME SCHEMA <bkup_schema> TO <brand_new_schema>;
The schema A (with table) imported fine.  Schema B (with synonym) gives the below error :
"SAP DBTech JDBC: [2048]: column store error: table import failed:  [2003] An index already exists with the same name "
When trying to use "REPLACE" clause in the command the error changes as below:
SAP DBTech JDBC: [2048]: column store error: table import failed:  [30117] Binary import failed (cannot execute drop statement)
Has anybody faced this type of error before??

Folks, I am running into the same issue. What I figure out was the following:
1) I turn off the autocommit
2) I run the import for the first time
import "<SCHEMA_NAME>"."*" as binary from '<location>' with replace;
rollback;
3) I get the error as described
SAP DBTech JDBC: [2048]: column store error: table import failed:  [30117] Binary import failed (cannot execute drop statement)
4) I run this import once again and commit and surprisingly the error is gone and the import is successful.
import "<SCHEMA_NAME>"."*" as binary from '<location>' with replace;
commit;

Similar Messages

  • Getting error while importing schema with ORACLE TEXT

    IMP-00003: ORACLE error 20000 encountered
    ORA-20000: Oracle Text error:
    DRG-52204: error while registering index
    DRG-10507: duplicate index name: WORKORDER_Q, owner: SYS
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.DRIIMP", line 115
    ORA-06512: at line 2
    IMP-00088: Problem importing metadata for index WORKORDER_Q. Index creation will be skipped
    Database version - Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Os version - Linux nlxs1012.slb.atosorigin-asp.com 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
    We have take export of schema from production db now importing data to qa environment..
    In import facing above error..

    I am importing objects from P20_MAXIMO to Q25_MAXIMO to another database..
    Below is import par file..
    USERID='/ as sysdba'
    FILE=exp_P20_MAXIMO_C2364781.dmp
    LOG=imp_P20_MAXIMO__Q25_MAXIMO_C2364781_1.log
    FROMUSER=P20_MAXIMO
    TOUSER=Q25_MAXIMO
    buffer=1000000
    feedback=100000
    Export parfile
    userid='/ as sysdba'
    owner=P20_MAXIMO
    FILE=exp_P20_MAXIMO_C2364781.dmp
    LOG=exp_P20_MAXIMO_C2364781.log
    buffer=10000000
    feedback=100000
    statistics=none

  • Error while importing schemas using datapump

    Hi,
    I am trying to import schema from qc to development. after importing i got the following error attached below:
    Processing object type SCHEMA_EXPORT/TABLE/GRANT/WITH_GRANT_OPTION/OBJECT_GRANT
    Processing object type SCHEMA_EXPORT/TABLE/GRANT/CROSS_SCHEMA/OBJECT_GRANT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    ORA-39065: unexpected master process exception in RECEIVE
    ORA-39078: unable to dequeue message for agent MCP from queue "KUPC$C_2_20090421161917"
    Job "SYS"."uat.210409" stopped due to fatal error at 20:15:13
    ORA-39014: One or more workers have prematurely exited.
    ORA-39029: worker 2 with process name "DW02" prematurely terminated
    ORA-31671: Worker process DW02 had an unhandled exception.
    ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421161934 from queue "KUPC$C_2_20090421161917"
    ORA-06512: at "SYS.KUPW$WORKER", line 1397
    ORA-06512: at line 2
    ORA-39029: worker 3 with process name "DW03" prematurely terminated
    ORA-31671: Worker process DW03 had an unhandled exception.
    ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421162030 from queue "KUPC$C_2_20090421161917"
    ORA-06512: at "SYS.KUPW$WORKER", line 1397
    ORA-06512: at line 2
    ORA-39029: worker 4 with process name "DW04" prematurely terminated
    ORA-31671: Worker process DW04 had an unhandled exception.
    ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421162031 from queue "KUPC$C_2_20090421161917"
    ORA-06512: at "SYS.KUPW$WORKER", line 1397
    ORA-06512: at line 2
    Is my import completed successfully or not??. please help...

    When a datapump job runs, it creates a table called the master table. It has the same name as the job name. This is used to keep track of where all of the information in the dumpfile is located. It is also used when restarting a job. For some reason, this table got dropped. I'm not sure why, but in most cases, datapump jobs are restartable. I don't know why the original message was reported, but I was hoping the job woudl be restartable. You could always just rerun the job. Since the job that failed already created tables and indexes, if you restart the job, all of the objects that are dependent on those objects will not be created by default.
    Let's say you have table tab1 with an index ind1 and both table and index are anaylized. Since tab1 is already created, the datapump job will mark all of the objects dependent on tab1 to skip. This includes the index, table_statistics, and index_statistics. To get around this, you could say
    table_exists_action=replace
    but this will replace all tables that are in the dumpfile. Your other options are:
    table_exists_action=
    truncate -- to truncate the data in the table and then just reload the data, but not the dependent objects
    append -- to append the data from the dumpfile to the existing table, but do not import the dependent objects
    skip -- skip the data and dependent objects from the dumpfile.
    Hope this helps.
    Dean

  • Error while importing RFC schema

    Hello Friends,
    I am getting the following error while importing the RFC schema in Integration repository from SAP which is on ECC version.
    The error I am getting is:
    Unable to establish connection to R/3 system 10.238.52.79 (system=03, client=250) Troubleshooting tips:
    Is the target system online?
    Check the connection data (note that server names and groups are case-sensitive)
    Tips for administrators (see the configuration guide for more details):
    Does the user have the required authorizations in the target system?
    Is the target system configured correctly in "etc/services"?
    I checked the target system configuraion as well as user authorization. All the connection parameters are also correct.
    Does anybody have idea about the solution to this problem?
    Regards,
    Nitin.

    I had this problem before. I had to make an entry with SAPGW03 in my services file on the XI server. the entry should look like
    sapgw03     3303
    That resolved my problem. If you are working with a XI server on Windowns the file is located in <WINDOWS_DIR>\system32\driver\etc\ directory.
    Thanks,
    Kalyan Musunuri
    OBT Global Inc.
    Message was edited by: Kalyan Tej Musunuri

  • Error in trigger while importing schema

    I am getting the below error while importing a schema back to a database..
    ORA-39083: Object type TRIGGER failed to create with error:
    ORA-04072: invalid trigger type
    Failing sql is:
    BEGIN DBMS_DDL.SET_TRIGGER_FIRING_PROPERTY('"pula"','"Trigger1"',FALSE) ; END;
    ORA-39083: Object type TRIGGER failed to create with error:
    I have checked the status of the trigger and everything id fine...
    Please help..!!

    Rajesh,
    Please go through this Wiki chapter on CoA import using DTW and you should be able to understand this better
    https://wiki.sdn.sap.com/wiki/display/B1/SAPBusinessOne...ToGo-10.DataTransfer+Workbench
    Suda

  • Error while importing 10.2.0.3 dumpfile on 11.2.0.1Database

    Hi All,
    I am getting the below error while importing an 10g dump on an 11g Database.
    The command which i am executing is
    C:\Users>impdp directory=TEST_DIR parallel=4 dumpfile=TEST_%U.dmp logfile=TEST.log schemas=TEST
    The Error is :
    ORA-39002: invalid operation
    ORA-31694: master table "SYS"."SYS_IMPORT_SCHEMA_01" failed to load/unload
    ORA-02354: error in exporting/importing data
    ORA-02368: the following file is not valid for this load operation
    ORA-02369: internal number in header in file H:\TEST\TEST_03.dmp is not valid
    Which means TEST_03.dmp is not valid but when i am executing the same Import by using the below command
    C:\Users>impdp directory=TEST_DIR parallel=4 dumpfile=TEST_01.dmp,TEST_02.dmp,TEST_03.dmp,TEST_04.dmp logfile=TEST.log schemas=TEST
    Is Throwing an error as
    ORA-39001: invalid argument value
    ORA-39000: bad dump file specification
    ORA-31619: invalid dump file "H:\TEST\TEST_04.dmp"
    So i am confused that in previous command it was stating TEST_03.dmp is not valid and in above command it throwing error as TEST_04.dmp is valid.
    Can anyone help me why there is such discrepencies in it while i am running the same commands.
    Thanks
    Snehasis.

    Hi,
    I would think that all the files are 'bad' in some way but the command is just accessing the files in a different order when run in the two different ways. All the files have to be read at the initial phase of the import.
    I think you'll likely find that if you change the order of the files in your second command the bad file will be reported as a different file - oracle often validates things from right to left.
    The % option is probably ordering the files in some random sequence and it just so happened that TEST03.dmp was checked first.
    The most likely cause of the error is that the files were transferred to the server in the correct ftp mode.
    Cheers,
    Harry

  • Error while importing data into Oracle 11gr2 with arcsde 9.3.1

    I am getting error while importing the data into oracle 11g r2. We are using arcsde 9.3.1
    It seems to be having some problem with spatial index creation.
    kindly help
    IMP-00017: following statement failed with ORACLE error 29855:
    "CREATE INDEX "A3032_IX1" ON "DGN_POLYLINE_2D" ("SHAPE" ) INDEXTYPE IS "MDS"
    "YS"."SPATIAL_INDEX""
    IMP-00003: ORACLE error 29855 encountered
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: [mdidxrbd]
    ORA-13249: Error in Spatial index: index build failed
    ORA-13249: Error in spatial index: [mdrcrtxfergm]
    ORA-13249: Error in spatial index: [mdpridxtxfergm]
    ORA-13200: internal error [ROWID:AAAT5pAA9AACIy5AAQ] in spatial indexing.
    ORA-13206: internal error [] while creating the spatial index
    ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
    ORA-06512: at "MDSYS

    Guys,
    I am also getting the same error and also my issue is like I am not even to analyze for which indexes I am getting error. It does not hve any indx name before error.
    Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX
    ORA-39083: Object type INDEX failed to create with error:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: [mdidxrbd]
    ORA-13249: Error in Spatial index: index build failed
    ORA-13249: Error in spatial index: [mdrcrtxfergm]
    ORA-13249: Error in spatial index: [mdpridxtxfer]
    ORA-29400: data cartridge error
    ORA-12801: error signaled in parallel query server P000
    ORA-13249: Error in spatial index: [mdpridxtxfergm]
    ORA-13200: internal error [ROWID:AA
    ORA-39083: Object type INDEX failed to create with error:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: [mdidxrbd]
    ORA-13249: Error in Spatial index: index build failed
    ORA-13249: Error in spatial index: [mdrcrtxfergm]
    ORA-13249: Error in spatial index: [mdpridxtxfer]
    ORA-29400: data cartridge error
    ORA-12801: error signaled in parallel query server P002
    ORA-13249: Error in spatial index: [mdpridxtxfergm]
    ORA-13200: internal error [ROWID:AA
    ORA-39083: Object type INDEX failed to create with error:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: [mdidxrbd]
    ORA-13249: Error in Spatial index: index build failed
    ORA-13249: Error in spatial index: [mdrcrtxfergm]
    ORA-13249: Error in spatial index: [mdpridxtxfer]
    ORA-29400: data cartridge error
    stack cnt....
    How can I find for which indexes it is failing?
    Thank you,
    Myra

  • Error while importing WSDL file created in JDeveloper inside BS

    Hi All,
    I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
    The error in OSB is 'The Resource Mapped Does not exist'

    Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
    Regards,
    Anuj

  • 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 importing MS project into cProject

    Hi
    I am getting the below error while importing MS project client file or XML file into cProjects.
    dpr_shared087
    Logon language becomes original language
    Message no. DPR_SHARED087
    Diagnosis
    The logon language is defined as a possible text language in Customizing for Collaboration Projects under Specify Text Languages. Therefore, it is valid.
    System Response
    The logon language becomes the original language of the new object that was created.
    Kindly suggest what configuration data if any is missing.
    Regards
    Srikrishna

    Hi
    I am getting the below error while importing MS project into cProject.
    Error occurred when importing from Microsoft Project
    Message no. DPR_UI_BSP116
    Diagnosis
    When a project is imported from Microsoft Project, the system generates an XML string during internal processing. A project is then created in cProjects from this string.
    The XML string contains errors because the values from Microsoft Project were transferred without verification.
    Procedure for System Administration
    Notify SAP or call the cProjects application with the "DebugMode=X" query string and carry out the import again.
    The XML string that was generated temporarily is then validated against the cProjects XML schema. The error message from the XML parser is then displayed in the popup.
    Kindly suggest, if the below steps for importing MS project is ok or not?
    step 1: Create project in MS project with tasks.
    step 2: Maintain maping fields of MSP in cProject configurat
    step 3: Import MPP file into cProject using "Import" button.
    step 4: I am getting the above error while importing the MPP file.
    Regards
    Srikrishna

  • Errors While import-IMPDP

    Hi Team,
    Getting below errors while import Please suggest.
    Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
    ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
    ORA-31625: Schema ASID is needed to import this object, but is unaccessible
    ORA-28031: maximum of 148 enabled roles exceeded
    Failing sql is:
    BEGIN
    sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'PAC', inst_scn=>'21502808296');COMMIT; END;
    ORA-39014: One or more workers have prematurely exited.
    ORA-39029: worker 1 with process name "DW01" prematurely terminated
    ORA-31671: Worker process DW01 had an unhandled exception.
    ORA-01031: insufficient privileges
    ORA-06512: at "SYS.KUPW$WORKER", line 13249
    ORA-06512: at "SYS.KUPW$WORKER", line 14900
    ORA-06512: at "SYS.KUPW$WORKER", line 6293
    ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling KUPP$PROC.CHANGE_USER [PROCACT_SCHEMA:"ASI"]
    ORA-06512: at "SYS.KUPW$WORKER", line 12280
    ORA-01031: insufficient privileges
    ORA-06512: at "SYS.KUPW$WORKER", line 5288
    ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
    ORA-31625: Schema ASIF is needed to import this object, but is unaccessible
    ORA-28031: maximum of 148 enabled roles exceeded
    Failing sql is:
    BEGIN
    sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'PAC', inst_scn=>'21502808296');COMMIT; END;
    ORA-06512: at "SYS.KUPW$WORKER", line 1342
    ORA-06512: at line 2
    Job "SYS"."SYS_IMPORT_FULL_01" stopped due to fatal error at 17:13:38
    Thanks In advance.

    ORA-28031: maximum of 148 enabled roles exceeded28031, 00000, "maximum of %s enabled roles exceeded"
    // *Cause:  The user attempted to enable too many roles.
    // *Action: Enable fewer roles.                                                                                                                                                                                                                                                                                                                                                                                                           

  • JAXB Bindings - error while compiling Schema(s)

    Hello, I want to create Java classes from a XML Schema by using JAXB Binding. However, when I do that a message error appears: "Error while compiling Schema" and then it says:
    "C:\...\NetBeansProjects\myproject\build.xml:12: Problem: failed to create task or type import
    Cause: The name is undefined.
    Action: Check the spelling.
    Action: Check that any custom tasks/types have been declared.
    Action: Check that any <presetdef>/<macrodef> declarations have taken place."
    Does anybody know what it's happening? It could be that there is a .jar missing?
    Thank you very much

    The document build.xml at line 12 says <import file="nbproject/build-impl.xml"/>. The file nbproject / build-impl.xml exists. If you want I could send it to you.You could post it here (the build-impl.xml, I mean).
    I have a working example, we could compare.
    I have included all the .jar you mentioned (excep the jaxb1-imp.jar).?
    If you added this JAXB compiling target via NB's wizard, as you describe below, you shouldn't have to "include" whatever jars wich are already in the JDK. That is, if you're using JDK6 - JAXB was not (or not so much) included in the JDK prior to 1.6.
    If the JDK is 1.5, I have no idea where you have to add these jars, possibly you're not add them in the correct classpath. Presumably Ant itself would need them in its classpath to be able to define the task.
    And I have not touched anythingThey all say that... :o)
    the only thing I did was to add other .jars (for other purposes).See?
    Is it possible that you removed one of the important jars when doing back-and-forth tries?
    But anyway I went back to remove this new .jars and the JAXB Binding still doesn't work .
    Should I uninstall the IDE and re-install? I do not know what else to do ...Do you have any reason to believe you did corrupt the JDK or NetBeans's installation? For example, when you write about adding/removing the mentioned jars, did you do that somewhere in the JDK or NB installation?
    Other than that, I don't see what reinstalling NB would do.
    Without going to such extremes, have you tried simply to remove the JAXBBinding, and add it again in the NetBeans project, using the wizard?

  • Error while importing WSDL

    Hi,
    I am getting following error while importing a WSDL file to siebel tool. It seems that
    WSDL wizard is treating the XSD schema namespsace declaration as a schema import, and is trying to connect to the w3.org URL.
    (Also this problem seems to be WindowsXp specific..as I am able to import the same WSDL file to other machine (having WindowsNT)
    Can somebody help me on this.
    ===============Error Message=================================
    Errors during processing:
    There are no web service definitions to be generated.(SBL-EAI-04340)
    Following are warnings generated in the process:
    Service 'FormsServiceService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
    Port 'FormsService' can not be imported. PortType 'FormsService' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'renderHTMLForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderHTMLForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
    The http://schemas.xmlsoap.org/wsdl/:operation 'renderPDFForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderPDFForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
    The http://schemas.xmlsoap.org/wsdl/:operation 'renderForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
    The http://schemas.xmlsoap.org/wsdl/:operation 'renderPDFFormWithUsageRights' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderPDFFormWithUsageRightsResponse' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
    The http://schemas.xmlsoap.org/wsdl/:operation 'processFormSubmission' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'processFormSubmission' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
    The http://schemas.xmlsoap.org/wsdl/:operation 'renderFormGuide' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderFormGuideResponse' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
    XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
    Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)

    Hi,
    I think, This is a late answer but I want to reply to help other persons who can get this error. I copied from metalink.
    The reason for the error is using of a proxy server (check Explorer > Tools > Internet Options > Connections, and click LAN Setting). One suggestion was to configure the settings to bypass the proxy server for the www.w3.org urls. r Instead used a dial up connection to avoid the proxy server, and was able to import the wsdl ok.
    Regards.

  • Error while importing music in iMovie 11 From itunes 10

    Error while importing music in iMovie 11
    I have the same error explained in a other post which was still left unanswered
    I have this sound problem after reorganising folders by itunes, i tried to delete al files in itunes and also
    deleted the xml file in the itunes dir, created new playlists, but still i have no music sound in imovie timeline
    after dragging a mp3 into it. When i preview the file in imovie it souds ok.
    Also i see the red dot with the number 1 in the itunes logo while dragging the mp3.
    Is there a solution for this problem?
    Former post;
    Re: Error while importing music in iMovie 09 from iTunes 09
    Posted: Jul 24, 2010 8:08 AM   in response to: vincentplaces  
    I'm having the exact same issue, but still haven't figured out what it is. I note that at the top of this thread it indicates that there are two "helpful" entries and one "solved" entry, but I can't find the solved one, so maybe someone will repost it here or kindly link to it.
    There is one icon missing though.
    As I read through the excellent tutorial at http://www.kenstone.net/fcphomepage/imovie_09stone.html I scroll down to the point where he talks about dragging music in from iTunes, which is what I'm trying to do. I can see, in his screen shot, the extra little icon that is a red oval and a white "1" in it. I don't get that icon when I am trying to drag my music into the video. I do get the green and white plus icon when I try to drag my music in. Also I DO get BOTH the red 1 and the green plus when I try dragging in a sound effect, which I can do with no problem. But why not the music?
    I've been able to drag in music with no problem in other productions, so I can't figure out what is going on with this one. I'm sure there is a setting somewhere that got flipped, but I can't figure out where.
    In desperation I also tried adding an extra title slide at the end of my video just to make sure there is more video time than music time in the production, but that didn't help at all.
    Any help guys?
    iMac 27"   Mac OS X (10.6.4)    

    Hi
    Due to some kind of copy protection in iTunes - I don't copy directly from this in iMovie
    to my projects. (Most often the result of doing it in iMovie is a DVD without any sound)
    I do
    • In iTunes - collect needed audio into a new Playlist
    • then burn this out as an Audio-CD .aiff (NOT .mp3)
    • This CD I copy into a folder on my Mac (often containing other material that's connected to the project)
    • And then I drag and drop these .aiff files into my movie project in iMovie.
    This works Greatly and even more so when I do my DVD.
    Yours Bengt W

  • Error while importing a new CERT in oracle 10G B2B

    Hi All,
    I am trying to upload a new certificate in 10 G B2B server, its not updating a certificate, I am facing the below error while importing
    Error
    An error occurred when updating the certificate.
    Error -: AIP-16001: The model validation engine failed due to an internal system error.
    Error -: AIP-11052: Writing following objects: Certificate failed due to following constraint violation: CERTIFICATE. CAN NOT UPDATE UNVERSIONABLE OBJECT IN A VALIDATED CONFIGURATION.
    Note: Please help me in resolving this ASAP.
    Regards
    Sai

    Hi Sai,
    It seems you are updating certificate in a delivery channel which is being used in a validated (or may be deployed) agreement. Please retire/purge any deployed configuration which is using that delivery channel and also make sure no such agreement is in valid state(which is using this delivery channel).
    Regards,
    Anuj

Maybe you are looking for

  • Executable JAR file: Could not find the main class.

    Hello, I have a problem with making an executable JAR file. I have written a JAVA program that consists of five different classes of which User.java is the main class and I have saved a text document with Main-Class: User and a blank line after that.

  • What Presets for This Avi File?

    I have a couple of .avi files of musical movies (from tv) that I would like to edit in Premiere (which I've virtually never used before, only some intermittent stuff with my little digital camera... no real knowledge ). What I want to do is simply ex

  • Question about capturing from FX1000

    Hello everyone. This is my first post here tho I have been searching these forums for some time now. I looked for my question but i could not find one that helped me. Anyway. So I just got a HDR-FX1000 and I love it! I just filmed my last show and wh

  • Height of new 27" iMac?

    Hi, I'm looking to upgrade but I've got height restrictions on my desk due to shelving... the spec page says 20.4 for the body, but does anyone have the TOTAL height of the 27", with the stand?? Thanks.

  • Confused with as2 vs as3

    hi i am new at flash and have been following training i purchased from total training and have been building my website in flash using the action script 2 setting with some degree of success. i have now however hit a brick wall. i am trying to make s