Req import fails with POCIRM-24a: ORA-01400:

Req import fails with.
POCIRM-24a: ORA-01400: cannot insert NULL into ("PO"."PO_REQ_DISTRIBUTIONS_ALL"."D

Please post the details of the application release, database version and OS.
Req import fails with.
POCIRM-24a: ORA-01400: cannot insert NULL into ("PO"."PO_REQ_DISTRIBUTIONS_ALL"."DPlease follow the steps in these docs for details about the error.
Adding To Cart Delivers Error - ORA-01400: Cannot Insert NULL Into ("PO"."PO_REQUISITION_LINES_ALL"."DELIVER_TO_LOCATION_ID") [ID 580002.1]
FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1]
Thanks,
Hussein

Similar Messages

  • Open Item Import fails with a process_flag = -999 or -888

    Problem description
    ============
    The Open Item Import fails with a process_flag = -999 in
    mtl_system_items_interface. This keeps the item from being imported into
    mtl_system_items. The process_flag has to be set back to 1 to have the row(s)
    reprocessed.
    Solution
    ======
    UPDATE mtl_system_items_interface
    set transaction_type='CREATE'
    where transaction_type=<'>
    Commit;
    Re run the Item Import it should go fine.
    Regards,
    Mehboob

    Hi,
    It looks like you have posted the same in below thread.
    Item Import completed with Process_Flag = 31, 41 and 42
    Any way if you have problem you can refer to below metalink notes.
    NOTE:103869.1 - Item Attribute vs Template Attributes Using IOI
    NOTE:106812.1 - Instructions for Running Item Open Import (IOI) Including Historical Revision Da
    NOTE:109628.1 - FAQ for Item Import
    NOTE:268968.1 - Understanding Item Import and Debugging Problems with Item Import
    NOTE:458544.1 - Inventory Item Open Interface ITAR Template
    NOTE:52746.1 - A Guideline to IOI Error Messages and Solutions
    Thanks
    Vishalaksha

  • Import failing with no errors

    Import failing with no errors
    All it says in logs for each table is
    . . skipping table "<table_name>"
    It's a full import from a 10.2.03 db into a 10.2.0.3 db

    Hi,
    "INDEXFILE" , this is parameter is specified, index-creation statements for the requested mode are extracted and written to the specified file, rather than used to create indexes in the database. No database objects are imported.
    Due to that that Objects are skipping.
    The INDEXFILE parameter can be used only with the FULL=y, FROMUSER, TOUSER, or TABLES parameters.
    Else you can perform a two step process as stated by Amardeep.
    - Pavan Kumar N

  • MDL IMPORT FAILS WITH MDL1261

    Hi all,
    I am using the OWB Repository Version 10.2.0.4.0 in a AIX server and we face MDL IMPORT FAILS WITH MDL1261
    On Oracle Metalink we found the following information. The datatype and background both are set to 113.
    Does the suggestion to set the values to 10007 apply in this case?
    Thanks !
    Sebastian
    MDL IMPORT FAILS WITH MDL1261
    The upgrade to 11.1.0.7 creates a new property SAP_FTP in the repository. The DATATYPE of this property is incorrectly set to113. The value should be 10007. This wrong datatype causes the NullPointerException because it causes the type not be found when it is expected to be there.
    Solution
    1. Using SQL*Plus, connect to OWBSYS
    2. Check datatype of property SAP_FTP
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'SAP_FTP';
    NAME DATATYPE
    SAP_FTP 113
    3. Check datatype of property BACKGROUND
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'BACKGROUND';
    NAME DATATYPE
    BACKGROUND 10007
    The value of DATATYPE for the property SAP_FTP and property BACKGROUND should be the same (10007). If this is not the case, the DATATYPE of property BACKGROUND should be changed.
    Proceed to the next step to correct this.
    4. Update PROPERTYDEFINITION_V
    If the value of DATATYPE is not the same for property SAP_FTP and property BACKGROUND, then correct this as follows:
    SQL> update PROPERTYDEFINITION_V
    set DATATYPE = (select datatype from PROPERTYDEFINITION_V where name = 'BACKGROUND') where name = 'SAP_FTP';
    5. Verify updated correctly
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'SAP_FTP';
    NAME DATATYPE
    SAP_FTP 10007
    6. If everything looks correct, then commit.
    SQL> commit;
    Commit complete.

    Hi Detlef,
    This is the only error I got. Regards, Sebastian
    error at line 237,069: MDL1261: Error importing MAPPING GG_OPS.4_DWH.GG_MAP_D_OFFICE.
    Detailed Error Message:
    java.lang.NullPointerException
         at oracle.wh.repos.impl.foundation.CMPElement.setElement(CMPElement.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.WBProxy.uncached(WBProxy.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.StaticCache.uncache(StaticCache.java:120)
         at oracle.wh.repos.pdl.foundation.CacheMediator.uncacheComponent(CacheMediator.java:1435)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:495)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:346)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:640)
         at oracle.wh.repos.pdl.foundation.MemoryManagerImpl.uncache(MemoryManagerImpl.java:530)
         at oracle.wh.repos.pdl.foundation.MemoryManagerImpl.checkMemory(MemoryManagerImpl.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.CacheMediator.cache(CacheMediator.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.CacheMediator.cache(CacheMediator.java(Compiled Code))
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4482)
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4468)
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4463)
         at oracle.wh.repos.pdl.metadataloader.MDLImportCreateUtil.internalImportObject(MDLImportCreateUtil.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.MDLImportCreateUtil.importObject(MDLImportCreateUtil.java(Inlined Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElementCreateObj(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElement(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.processPendingFCOElements(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElementPendingFCOAssoc(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElement(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.run(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ConverterStateMachine.runAll(ConverterStateMachine.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML$ConvertHandlerBase.startElement(ProcessXML.java(Compiled Code))
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java(Compiled Code))
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:326)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:293)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:295)
         at oracle.wh.repos.pdl.metadataloader.converter.util.WBXMLSourceReader.parse(WBXMLSourceReader.java:59)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML.runConversion(ProcessXML.java:356)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML.run(ProcessXML.java:290)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.StateMachine.runAll(StateMachine.java:50)
         at oracle.wh.repos.pdl.metadataloader.converter.WBConverter.ConvertXML(WBConverter.java:568)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1859)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
         at oracle.owb.Import.ImportServiceManager.internalImportMetaData(ImportServiceManager.java:506)
         at oracle.owb.Import.ImportServiceManager.importMetaDataFromFile(ImportServiceManager.java:355)
         at oracle.owb.scripting.executers.ImportCmdExecuter.startMetaDataImportCommand(ImportCmdExecuter.java:708)
         at oracle.owb.scripting.executers.ImportCmdExecuter.importFromFile(ImportCmdExecuter.java:150)
         at oracle.owb.scripting.parsers.ImportCmdParser.mdlImportCommand(ImportCmdParser.java:302)
         at oracle.owb.scripting.parsers.ImportCmdParser.ImportCommand(ImportCmdParser.java:152)
         at oracle.owb.scripting.parsers.ImportCmdParser.parseCommand(ImportCmdParser.java:112)
         at oracle.owb.scripting.commands.OMBMetaDataImportCmd.executeCommand(OMBMetaDataImportCmd.java:77)
         at oracle.owb.scripting.commands.OMBCommand.cmdProc(OMBCommand.java:69)
         at tcl.lang.Parser.evalObjv(Parser.java:818)
         at tcl.lang.Parser.eval2(Parser.java:1221)
         at tcl.lang.Interp.eval(Interp.java:2189)
         at tcl.lang.Interp.evalFile(Interp.java:2368)
         at tcl.lang.TclShell.run(TclShell.java:124)
         at tcl.lang.TclShell.run(TclShell.java:68)
         at oracle.owb.scripting.OMBShell.main(OMBShell.java:38)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         at java.lang.reflect.Method.invoke(Method.java:391)
         at Launcher.main(Launcher.java:167)

  • Journal Import fails with EC12 issue

    Journal Import fails with EC12 issue, we knew the AR credit memo transactions causing this issue have distribution lines with accounted_dr value as zero and entered_dr as non zero, same is the case with accounted_cr and entered_cr.
    Issue is with the Credit memos generated out of iReceivables that are creating distributions with null amounts when applied on invoices with rules. Null amounts are on REV/UNEARN distribution lines. Applied patch# 12957348 as suggested in metalink and we noticed more number of such transactions after patch application.
    Any pointers are really appreciated. We have over 5000 such lines and is not possible to clear them manually and since these CM's are phased, we are sure to see them again with this issue till it is resolved. Note# 285995.1 didn't help either.
    We are on 11.5.10.2 and 10g database.
    K

    FOR l_rec IN (SELECT ledger_id,group_id from apps.gl_interface
    WHERE status='NEW'
    AND user_je_source_name='GIS_DATA_CONVERSION'
    GROUP BY ledger_id,group_id
    ORDER BY group_id
    LOOP
    apps.gl_journal_import_pkg.populate_interface_control (user_je_source_name => 'GIS_DATA_CONVERSION',
    GROUP_ID => l_rec.group_id,
    set_of_books_id => l_rec.ledger_id,
    interface_run_id =>vl_interface_id,
    table_name => 'GL_INTERFACE',
    processed_data_action=>'D'
    COMMIT;
    vl_request_id := apps.fnd_request.submit_request (application => 'SQLGL', -- application short name
    program => 'GLLEZLSRS', -- program short name
    description => NULL, -- program name
    start_time => NULL, -- start date
    sub_request => FALSE, -- sub-request
    argument1 => 2065, --Data access set id
    argument2 => 'GIS_DATA_CONVERSION', --Source
    argument3 => l_rec.ledger_id, -- set of books id
    argument4 => l_rec.group_id,
    argument5 => 'N', -- error to suspense flag
    argument6 => NULL, -- create summary flag
    argument7 => 'N' -- import desc flex flag
    COMMIT;
    IF ( vl_request_id = 0 ) THEN
    xxgis.gis_conv_util_pkg.debug_print_p(1,'FND_LOG','E001: Journal Import Submission Failed. ' || SQLERRM);
    retcode := 2;
    EXIT;
    ELSE
    xxgis.gis_conv_util_pkg.debug_print_p(1,'FND_LOG','P001: Submitted Journal Import Program for group id: ' || l_rec.group_id ||
    'and ledger :'||l_rec.ledger_id|| ', Request ID: ' || vl_request_id);
    END IF;
    END LOOP;

  • Import failing with ORA-20001: GET_BLOCK Error

    Hi All,
    I'm attempting to install an export of our Application into the LIVE environment (something I've done many times before), and it's failing with the following error message: -
    ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 698, column 1: PLS-00103: Encountered the symbol &amp;quot;,'#DD#','#EE#');&amp;quot; when expecting one of the following: ) , * &amp;amp; = - + &amp;lt; / &amp;gt; at in is mod remainder not rem &amp;lt;an exponent (**)&amp;gt; &amp;lt;&amp;gt; or != or ~= &amp;gt;= &amp;lt;= &amp;lt;&amp;gt; and or like LIKE2_ LIKE4_
    The only part of the message that makes any sense to me is the '#DD#','#EE#' which looks like part of a Javascript Passback Function from one of the pages.
    Can anyone throw any light on why I'm getting this error message?
    Thanks,
    Mike

    Scott,
    I managed to track down the error. A column link URL I'm using calls a Javascript Passback Function as follows: -
    javascript:passBack('#A#','#B#','#C#','#D#','#E#','#F#','#G#','#H#','#I#','#J#','#K#','#L#','#M#','#N#','#O#','#P#','#Q#','#R#','#S#','#T#','#U#','#W#','#X#','#Y#','#Z#','#AA#','#BB#','#CC#','#DD#','#EE#');
    By reducing the length of this the import now works. The confusing part is that this was working previously.
    Cheers,
    Mike

  • Import fails with unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 6999

    Hi,
    I have taken export backup of table from 9.2.0.4 on AIX & trying to import in 11.1.0.7.0 on AIX
    while importing im getting the following error.
    ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
    As the table size is 37G , total free space in tablespace is 40G,
    & no index on the table.
    following are sum lines from import file
    Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Export file created by EXPORT:V09.02.00 via direct path
    import done in US7ASCII character set and UTF8 NCHAR character set
    import server uses AL32UTF8 character set (possible charset conversion)
    export server uses AL16UTF16 NCHAR character set (possible ncharset conversion)
    . importing DATAMIG's objects into CUSTOM
    . . importing table "CASA_TRAN_HIST_UPLD"
    IMP-00058: ORACLE error 1653 encountered
    ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
    IMP-00028: partial import of previous table rolled back: 62844421 rows rolled back
    IMP-00017: following statement failed with ORACLE error 1917:
    "GRANT SELECT ON "CASA_TRAN_HIST_UPLD" TO "BSGUSER""
    IMP-00003: ORACLE error 1917 encountered
    ORA-01917: user or role 'BSGUSER' does not exist
    Import terminated successfully with warnings.
    is there any to resolve the issue.
    how to change NCHAR set for import.
    Thanks

    Hello,
    which & how i can set character set for import.About the Character Set, it's a setting at the Database creation. You may check it by using the following query on the Source and Target Databases:
    select * from v$nls_parameters; The NLS_CHARACTERSET will give you the Character set of the Database.
    It cannot be changed easily. It may imply a Database creation and export/import of data ( see Note *225912.1* ).
    Else, when you export (with the Original Export/Import utility) it's recommended to set the NLS_LANG parameter.
    The NLS_LANG parameter has 3 components:
    - Language
    - Territory
    - Client Character Set
    A wrong setting of the NLS_LANG may lead to conversion. However starting with *9i* most data is exported with the Character Set of the Database regardless the NLS_LANG setting. The following note may give you some details about it:
    Export/Import and NLS Considerations [ID 15095.1]Hope this help.
    Best regards,
    Jean-Valentin

  • Import fail with IMP00003

    hi i have a DB running on oracle 9.2.0.6 enterprise edt and i want to migrate it to 9.2.0.8 with standard edt. I have taken the schema exp from 9206-ent edt and when importing it to 9208-std edt getting below error:
    IMP-00017: following statement failed with ORACLE error 3113:
    "BEGIN "
    "SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_QUEUE_TABLE('SA_BATCH_Q',1,8,3,0,0,'Batch q"
    "ueue table');"
    "COMMIT; END;"
    IMP-00003: ORACLE error 3113 encountered
    ORA-03113: end-of-file on communication channel
    IMP-00000: Import terminated unsuccessfully

    Hi,
    Queue tables cannot be imported..
    You can manually create them ...before doing so...u should stop the queues u want to create..
    BEGIN
    sys.dbms_aqadm.stop_queue
    (queue_name => 'ABCDXYZ.BIP_MESSAGE_QUEUE');
    sys.dbms_aqadm.drop_queue
    (queue_name => 'ABCDXYZ.BIP_MESSAGE_QUEUE');
    END;
    BEGIN
    sys.dbms_aqadm.stop_queue
    (queue_name => 'ABCDXYZ.AQ$_BIP_MESSAGE_QUEUE_TABLE_E');
    sys.dbms_aqadm.drop_queue
    (queue_name => 'ABCDXYZ.AQ$_BIP_MESSAGE_QUEUE_TABLE_E');
    END;
    BEGIN
    sys.dbms_aqadm.drop_queue_table
    (queue_table => 'ABCDXYZ.BIP_MESSAGE_QUEUE_TABLE');
    END;
    CREATE OR REPLACE
    TYPE "ABCDXYZ"."BIP_HOTBILL_MESSAGE_T" AS OBJECT
    account_no NUMBER(10),
    payment_due_date DATE,
    interim_bill_date DATE,
    include_nrc NUMBER(1),
    include_rc NUMBER(1),
    include_adj NUMBER(1),
    include_usage NUMBER(1),
    include_bmf NUMBER(1),
    bip_mode NUMBER(10),
    account_key NUMBER(10),
    bill_order_number VARCHAR2(26),
    request_id vARCHAR2(64)
    BEGIN
    DBMS_AQADM.CREATE_QUEUE_TABLE
    QUEUE_TABLE => 'BIP_MESSAGE_QUEUE_TABLE'
    ,QUEUE_PAYLOAD_TYPE => 'BIP_HOTBILL_MESSAGE_T'
    ,COMPATIBLE => '8.1'
    ,STORAGE_CLAUSE => '
    TABLESPACE ARBOR_01_TBL
    PCTUSED 0
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    STORAGE (
    INITIAL 64K
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    PCTINCREASE 0
    BUFFER_POOL DEFAULT
    ,SORT_LIST => 'ENQ_TIME'
    ,MULTIPLE_CONSUMERS => FALSE
    ,MESSAGE_GROUPING => 0
    End;
    BEGIN
    SYS.DBMS_AQADM.CREATE_QUEUE
    QUEUE_NAME => 'ABCDXYZ.BIP_MESSAGE_QUEUE'
    ,QUEUE_TABLE => 'ABCDXYZ.BIP_MESSAGE_QUEUE_TABLE'
    ,QUEUE_TYPE => SYS.DBMS_AQADM.NORMAL_QUEUE
    ,MAX_RETRIES => 5
    ,RETRY_DELAY => 0
    ,RETENTION_TIME => 0
    END;
    BEGIN
    SYS.DBMS_AQADM.START_QUEUE
    QUEUE_NAME => 'ABCDXYZ.BIP_MESSAGE_QUEUE'
    ,ENQUEUE => TRUE
    ,DEQUEUE => TRUE
    END;
    Edited by: Serverprocess on Jun 6, 2011 2:56 PM

  • Import failed with canon 6d footage after latest update

    After I updated to Final Cut X 10.0.8, I've been getting "Import Failed" messages during the import process when taking in footage from my Canon 6D
    The import process also seems to be going very slow (slower than usual)
    I've tried duplicating the SD card locally on the hard drive and re-importing, but have gotten the same results.
    If I click OK on the error dialogue box, the import will continue. but another box will pop up every 5 to 10 minutes or so
    Any ideas?

    Hey Russ, it actually works fine for me too the few times I've used it but I point it out as a common denominator with people who have trouble importing that way. Separating the .mov files into their own folder eliminates the camera and card reader, both much slower than just transfering files from a connected drive. But I'm doing newspaper video with Canon DSLRs - including 5D3 video, similar to 6D - almost daily where speed is of the essence and this is by far the most foolproof method I've come across.

  • Logical standby failed with LOGSTDBY status: ORA-01281: SCN range specified

    My logical standby datbase on 11gR2 failed with the above message.
    A search on the error says
    Error: ORA-01281 (ORA-1281)
    Text: SCN range specified is invalid
    Cause: StartSCN may be greater than EndSCN, or the SCN specified may be
    invalid.
    Action: Specify a valid SCN range.
    does any one have an idea as to how to specify a Valid SCN Range
    appreciate you help.

    When you got to DBMS_LOGSTDBY
    http://www.morganslibrary.org/reference/pkgs/dbms_logstdby.html
    What did you do when you saw the procedure MAP_PRIMARY_SCN?

  • SC import fails with "import successfully" in log. How to perform import?

    Hello SDN!
    I can't import SC SAP-SHRWEB.sca from Development to Consolidation system. At firts import process was finished with 'import failed' state and with followed log:
    20080416094446 Info   :Starting Step Repository-import at 2008-04-16 09:44:46.0570 +6:00
    20080416094446 Info   :Component:sap.com/SAP-SHRWEB
    20080416094446 Info   :Version  :MAIN_CRM50VAL_C.20060914085157
    20080416094446 Info   :1. propagation request is of type TCSSoftwareComponent
    20080416094457 Info   :Propagatable:0af61b4e430511db8c9d0030057116fe exists allready in the repository. No import necessary.
    20080416193724 Fatal  :VcmFailure received
    20080416193724 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Not Ready [(pre||post)-condition failed: Not Ready]:Not Ready [(pre||post)-condition failed: Not Ready]
    com.tssap.dtr.client.lib.deltavlib.VcmFailure: Not Ready [(pre||post)-condition failed: Not Ready]
         at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1742)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1432)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2815)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:978)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    20080416193725 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Not Ready [(pre||post)-condition failed: Not Ready]:communication error: VcmFailure received: Not Ready [(pre||post)-condition failed: Not Ready]
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Not Ready [(pre||post)-condition failed: Not Ready]
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1742)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1432)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2815)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:978)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    20080416193725 Info   :Step Repository-import ended with result 'fatal error' ,stopping execution at 2008-04-16 19:37:25.0338 +6:00
    I applied note 989010 and reimport SC. File processed about 5 hours and after that it still have 'import failed' state but in the log there is a message:
    20080417124350 Info   :Starting Step Repository-import at 2008-04-17 12:43:50.0291 +6:00
    20080417124350 Info   :Component:sap.com/SAP-SHRWEB
    20080417124350 Info   :Version  :MAIN_CRM50VAL_C.20060914085157
    20080417124350 Info   :1. propagation request is of type TCSSoftwareComponent
    20080417124351 Info   :propagatable:0af62b4e430511db8c9d0030057116fe not known in repository:http://UIT-EP-01:51000/dtr
    20080417124351 Info   :Import propagatable:0af62b4e430511db8c9d0030057116fe from archive:SAP-SHRWEB into repository:http://UIT-EP-01:51000/dtr
    20080417124351 Detail :start of importing propagatable:0af62b4e430511db8c9d0030057116fe to repository:http://UIT-EP-01:51000/dtr
    20080417124359 Info   :Propagatable:0af61b4e430511db8c9d0030057116fe imported successfully.
    Please help me to import this SC or provide me a detail way how to clean DTR, my track and other that may be necessary to clean from SC and reimport all SCs again.
    Regards, Lev

    Hi Lev,
    To your question to clear the track
    You can delete your track as described in the below link, and then recreate the track and reimport.
    Link: [Deleting Track|http://help.sap.com/saphelp_nw70/helpdata/EN/33/71fe94e1834af8b5bd3c0e1de5ab41/frameset.htm]
    Do not forget to delete DTR workspace.
    Do reward points if you find the link useful.
    Cheers,
    Sandeep

  • Rman archivelog backup fails with rman-03002,ora-19563

    Hi,
    D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
    RMAN> backup archivelog all;
    RMAN-03002: Error with backup command on 06-25-2013
    ORA-19563: Header-Validation is not successful.
        fails with the given errors.
    11.2.0.2 PROD DB on Windows Server 2008  R2 Enterpriise.
    When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
    The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH  FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
    Please suggest.
    Thanks a lot.
    Best Regards,

    Hi,
    Thanks a lot.
    I don't think that archivelogs were relocated, except I changed the location yesterday.
    As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
    LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
    I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
    Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
    LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
    Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

  • Disco command line import fails with parser error 7

    Hi, we have discoverer version 10.1.2.48.18 installed to multiple environments.
    Developers have created eex-file and we try to import it to all the test environments, it goes through fine with some but with some it fails with parser error 7 :
    Here is the full error log:
    11/13/2008 7:30:22 AM
    D:\disco1012\BIToolsHome_1\bin\DIS51ADM.EXE /connect /import oudata_disco.eex /identifier /refresh /preserve_workbook_owner /show_progress /log import.log
    oudata_disco.eex:Could not locate the Folder with identifier 'INSTRUCTOR_ASSIGNMENTS1' in the target End User Layer
    oudata_disco.eex:An imported Folder had display name 'Dc transactional sales q2' renamed to 'Dc transactional sales q2 1'
    oudata_disco.eex:An imported Item Class had display name 'Eval_Delivery_Region' renamed to 'Eval_Delivery_Region 1'
    oudata_disco.eex:An imported Item Class had display name 'Quarter' renamed to 'Quarter 1'
    oudata_disco.eex:An imported Item Class had display name 'Track List with ALL' renamed to 'Track List with ALL 1'
    The Item Hierarchy with identifier 'INSTRUCTOR_ASSIGNMENTS_LAST_REFRESH_DATE_DEFAULT_DATE_HIERARCHY' has not been imported because: There are no items in this hierarchy node
    Import completed, but with warnings. Please check the result.
    File(s) imported partially :
    oudata_disco.eex
    11/13/2008 7:36:38 AM
    11/13/2008 7:37:29 AM
    D:\disco1012\BIToolsHome_1\bin\DIS51ADM.EXE /connect /import oudata_disco_workbooks_84.eex /identifier /refresh /preserve_workbook_owner /show_progress /log import.log
    oudata_disco_workbooks_84.eex:A parsing failure has occurred in file 'oudata_disco_workbooks_84.eex'.
    Parser error: '7'
    The import has failed (your End User Layer has not been modified) - oudata_disco_workbooks_84.eex:A parsing failure has occurred in file 'oudata_disco_workbooks_84.eex'.
    Parser error: '7'
    If anyone knows what can be teh cause of this please let me know.
    thanks,
    Nina

    Hi,
    The most likely cause is that the export file has become corrupted. Are there very big export files?
    Another possibility is that Discoverer Administrator has run out of memory while parsing the file.
    Rod West

  • JTECH import fails with error Dirty DC

    Hi guys,
    We are on NW2004 s SP 7. I am trying to import JTECH7P and the import is failing with error dirty Dcs.
    Can anyone tell me where the error is? Is it due to incompatible to JTECH patch with my NWDI and EP system.
    Can some one give me matrix of which SP and patch for source codes JTECH ESS MSS BUILD JEE are required for NW2004s J2EE SP 7.
    Can some one point me to a note similar to 761266. I think 761266 this note does not have NW2004s related etails
    appreciate any help.
    regards
    Sam

    Ufuk Altinkaynak schrieb:
    > Dave Parkes schrieb:
    >> Stored in an external storage area, or under the post office ?
    >>
    >
    > Hello Dave,
    >
    > when using post office storage error is C06A, when using an external
    > storage, the error is C06B.
    >
    > If you have any hints/ solution or can say something about the charge,
    > that would be a huge help
    >
    Updated Information,
    Just to be sure about the C06B error, i created an new Library with
    external storage, than i draged and droped an *.txt file into documents
    (no the funny part) imported without any erors into the default library
    (that one with post office storage, that had before C06A errors)
    No i can use the library (with postoffice storage) without any erros.
    The only change on that system, was to create an additional library with
    external storage
    As every good side has a bad side, this bad side is, that i cannot
    import any documents into the library with external storage, the error i
    receive is C06B
    I have no clue why creating an additional librarry has fixed the first
    error, but hopefully this makes sence for someone, and hopefully anyone
    can help on the second error / Problem:
    C06B Error while importing into a library with external storrage
    regards
    Ufuk Altinkaynak

  • Import fails with error unique constraint

    Hello,
    I try to import an APEX Application from Version 2.2 to APEX Version 2.0.
    I get the following error message:
    ORA-20001: GET_BLOCK-Fehler. ORA-20001: GET_STMT-Fehler. ORA-20001: Die Ausführung der Anweisung war nicht erfolgreich. ORA-00001: unique constraint (FLOWS_020000.WWV_FLOW_REGION_UPD_RPT_CI1) violated<pre>
    &lt;br&gt;begin&lt;br&gt; &lt;br&gt;---------------------------------------&lt;br&gt;-- ...updatable report columns for page 60&lt;br&gt;--&lt;br&gt; &lt;br&gt;begin&lt;b
    For the Import I chose the option "Auto Assign New Application ID".
    Has anyone an Idea, why the import fails?
    (Export from Version 2.2 and Import to a different Workspace in Version 2.2 is successful)
    Thank you for your responses,
    Carola

    Carola,
    I have no idea why this is happening. You may send the application export file (or the export file for page 60 only) to [email protected] and I will check it.
    Scott

Maybe you are looking for