Transport fails during import

Hello                                                                               
While importing communication strcture & infosource ZMM_0CUST_SALES_ATTR
we got error 8 saying "There is no DataSource with these attributes     
Reference to transfer structure 80CUST_SALESM_AA not available.         
No activation possible."                                                
Then we have included the data source and again tried to import it      
but got the same error. Following are objects in transport.             
Communication structure : ZMM_0CUST_SALES_ATTR                          
InfoSource transaction data : ZMM_0CUST_SALES_ATTR                      
Transfer structure : 80CUST_SALESM_AA                                   
DataSource (Active Version) : 80CUST_SALESM                                                                               
Thanks                                                                  
Sundar

Hi,
Thanks for the prompt reply. Yes, I had successfully imported a request in BQ2 containing the characteristic 0Cust_sales. Only after importing this characteristic I tried the in problem request which was meant to Activate the the Transfer structure of the infoobject which uses 0cust_sales as datasource.
I found a SAP note suggesting a program which fixes the after import issues(RSDG_AFTER_IMPORT_FOR_CORR) but I am not sure it will work.
I dont want the request to fail again when I move it into production.
All your help is highly appreciated.
Many Thanks
Sundar

Similar Messages

  • Table Statistics failed during Import

    Hi All,
    I am trying to import an existing schema in Oracle 10g.
    I am using the impdp utility.
    The export dump consists of the complete schema (metadata and data).
    But it failed with the following logs.
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT []
    ORA-06502: PL/SQL: numeric or value error
    LPX-00007: unexpected end-of-file encountered
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 6235
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    1945A21C 14916 package body SYS.KUPW$WORKER
    1945A21C 6300 package body SYS.KUPW$WORKER
    1945A21C 12279 package body SYS.KUPW$WORKER
    1945A21C 3279 package body SYS.KUPW$WORKER
    1945A21C 6889 package body SYS.KUPW$WORKER
    1945A21C 1262 package body SYS.KUPW$WORKER
    1CD814AC 2 anonymous block
    Job "THHIS"."SYS_IMPORT_FULL_02" stopped due to fatal error at 11:47:38
    I had then used the parameter EXCLUDE=STATISTICS and then the import was successful.
    I would like to the significance of this STATISTICS.
    I mean would EXCLUDE=STATISTICS always be ok?
    I have exported and imported the scheme as a user and not as sysdba. Does this make any difference?
    any suggestion would be highly appreciated.
    Thanks,
    Tanuja

    Hi,
    See related threads here:
    ORA-39125 & DBMS_METADATA
    Error ORA-39125 and ORA-04063 during export for transportable tablespace
    ORA-39125: Worker unexpected fatal error in string while calling string [string]
    Cause: An unhandled exception was detected internally within the worker process for the Data Pump job while calling the specified external routine. This is an internal error. Additional information may be supplied.
    Action: If problem persists, contact Oracle Customer Support.
    Hope this helps . . .
    Donald K. Burleson
    Oracle Press author
    Author of "Oracle Tuning: The Definitive Reference"
    http://www.rampant-books.com/book_2005_1_awr_proactive_tuning.htm

  • ECC 6.0 Installation fails during Import ABAP Phase

    Hi,
    I am tryiing to install ECC 6.0 on windows 2003:Oracle and it is failing at phase 17 Import Abap with the following error:
    ERROR 2007-11-13 16:04:09
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2007-11-13 16:04:09
    FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    here is the import_monitor.java.log file:
    ava version "1.4.2_14"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)
    Java HotSpot(TM) Client VM (build 1.4.2_14-b05, mixed mode)
    Import Monitor jobs: running 1, waiting 37, completed 0, failed 0, total 38.
    Loading of 'SAPNTAB' import package: OK
    Import Monitor jobs: running 0, waiting 37, completed 1, failed 0, total 38.
    Import Monitor jobs: running 1, waiting 36, completed 1, failed 0, total 38.
    Import Monitor jobs: running 2, waiting 35, completed 1, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 34, completed 1, failed 0, total 38.
    Loading of 'SAPSSEXC_4' import package: OK
    Import Monitor jobs: running 2, waiting 34, completed 2, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 33, completed 2, failed 0, total 38.
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 33, completed 3, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 32, completed 3, failed 0, total 38.
    Loading of 'SAPAPPL2_1' import package: OK
    Import Monitor jobs: running 2, waiting 32, completed 4, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 31, completed 4, failed 0, total 38.
    Loading of 'SAPSSEXC_2' import package: OK
    Import Monitor jobs: running 2, waiting 31, completed 5, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 30, completed 5, failed 0, total 38.
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 30, completed 6, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 29, completed 6, failed 0, total 38.
    Loading of 'SAPAPPL1_1' import package: OK
    Import Monitor jobs: running 2, waiting 29, completed 7, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 28, completed 7, failed 0, total 38.
    Loading of 'SAPSSEXC_1' import package: OK
    Import Monitor jobs: running 2, waiting 28, completed 8, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 27, completed 8, failed 0, total 38.
    Loading of 'SAPAPPL0_3' import package: OK
    Import Monitor jobs: running 2, waiting 27, completed 9, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 26, completed 9, failed 0, total 38.
    Loading of 'SAPAPPL1_2' import package: OK
    Import Monitor jobs: running 2, waiting 26, completed 10, failed 0, total 38.
    Loading of 'SAPAPPL2_2' import package: OK
    Import Monitor jobs: running 1, waiting 26, completed 11, failed 0, total 38.
    Import Monitor jobs: running 2, waiting 25, completed 11, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 24, completed 11, failed 0, total 38.
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 12, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 23, completed 12, failed 0, total 38.
    Loading of 'SAPAPPL0_1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 13, failed 0, total 38.
    Import Monitor jobs: running 3, waiting 22, completed 13, failed 0, total 38.
    Loading of 'SAPAPPL2_3' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 13, failed 1, total 38.
    Loading of 'SAPSSEXC_3' import package: ERROR
    Import Monitor jobs: running 1, waiting 22, completed 13, failed 2, total 38.
    Import Monitor jobs: running 2, waiting 21, completed 13, failed 2, total 38.
    Import Monitor jobs: running 3, waiting 20, completed 13, failed 2, total 38.
    Loading of 'SAPSSEXC_5' import package: ERROR
    Import Monitor jobs: running 2, waiting 20, completed 13, failed 3, total 38.
    Loading of 'SAPAPPL0_2' import package: ERROR
    Import Monitor jobs: running 1, waiting 20, completed 13, failed 4, total 38.
    Import Monitor jobs: running 2, waiting 19, completed 13, failed 4, total 38.
    Import Monitor jobs: running 3, waiting 18, completed 13, failed 4, total 38.
    Loading of 'FUPARAREF' import package: ERROR
    Import Monitor jobs: running 2, waiting 18, completed 13, failed 5, total 38.
    Import Monitor jobs: running 3, waiting 17, completed 13, failed 5, total 38.
    Loading of 'TODIR' import package: ERROR
    Import Monitor jobs: running 2, waiting 17, completed 13, failed 6, total 38.
    Import Monitor jobs: running 3, waiting 16, completed 13, failed 6, total 38.
    Loading of 'SAPSDIC' import package: ERROR
    Import Monitor jobs: running 2, waiting 16, completed 13, failed 7, total 38.
    Import Monitor jobs: running 3, waiting 15, completed 13, failed 7, total 38.
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 14, failed 7, total 38.
    Loading of 'SAPSSRC' import package: ERROR
    Import Monitor jobs: running 1, waiting 15, completed 14, failed 8, total 38.
    Loading of 'E071K' import package: ERROR
    Import Monitor jobs: running 0, waiting 15, completed 14, failed 9, total 38.
    Import Monitor jobs: running 1, waiting 14, completed 14, failed 9, total 38.
    Import Monitor jobs: running 2, waiting 13, completed 14, failed 9, total 38.
    Import Monitor jobs: running 3, waiting 12, completed 14, failed 9, total 38.
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 15, failed 9, total 38.
    Import Monitor jobs: running 3, waiting 11, completed 15, failed 9, total 38.
    Loading of 'SAPPOOL' import package: ERROR
    Import Monitor jobs: running 2, waiting 11, completed 15, failed 10, total 38.
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 1, waiting 11, completed 16, failed 10, total 38.
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 0, waiting 11, completed 17, failed 10, total 38.
    Import Monitor jobs: running 1, waiting 10, completed 17, failed 10, total 38.
    Import Monitor jobs: running 2, waiting 9, completed 17, failed 10, total 38.
    Import Monitor jobs: running 3, waiting 8, completed 17, failed 10, total 38.
    Loading of 'SAPSLEXC' import package: ERROR
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 11, total 38.
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 1, waiting 8, completed 18, failed 11, total 38.
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 11, total 38.
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 11, total 38.
    Loading of 'SAPAPPL0_4' import package: ERROR
    Import Monitor jobs: running 2, waiting 6, completed 18, failed 12, total 38.
    Loading of 'SAPUSER' import package: ERROR
    Import Monitor jobs: running 1, waiting 6, completed 18, failed 13, total 38.
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 0, waiting 6, completed 19, failed 13, total 38.
    Import Monitor jobs: running 1, waiting 5, completed 19, failed 13, total 38.
    Import Monitor jobs: running 2, waiting 4, completed 19, failed 13, total 38.
    Import Monitor jobs: running 3, waiting 3, completed 19, failed 13, total 38.
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 20, failed 13, total 38.
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 1, waiting 3, completed 21, failed 13, total 38.
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 0, waiting 3, completed 22, failed 13, total 38.
    Import Monitor jobs: running 1, waiting 2, completed 22, failed 13, total 38.
    Import Monitor jobs: running 2, waiting 1, completed 22, failed 13, total 38.
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 23, failed 13, total 38.
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 24, failed 13, total 38.
    here is a copy of import_monitor.log
    INFO: 2007-11-13 14:02:09
    Import Monitor is started.
    CONFIG: 2007-11-13 14:02:09
    Application options:
    dbCodepage=4103
    dbType=ORA
    extFiles=yes
    importDirs=C:\sapcds\inst_exp\exp1\EXP1;C:\sapcds\inst_exp\exp1\EXP2;C:\sapcds\inst_exp\exp1\EXP3;C:\sapcds\inst_exp\exp1\EXP4;C:\sapcds\inst_exp\exp1\EXP5;C:\sapcds\inst_exp\exp1\EXP6;C:\sapcds\inst_exp\exp2\EXP7;C:\sapcds\inst_exp\exp2\EXP8;C:\sapcds\inst_exp\exp2\EXP9;C:\sapcds\inst_exp\exp2\EXP10;C:\sapcds\inst_exp\exp2\EXP11
    installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
    jobNum=3
    loadArgs= -stop_on_error
    monitorTimeout=30
    orderBy=
    r3loadExe=E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-11-13 14:02:09
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-11-13 14:02:09
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
    INFO: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2007-11-13 14:02:10
    Data codepage 1100 is determined using TOC file 'C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.TOC' for package 'SAPSSEXC_3'.
    INFO: 2007-11-13 14:02:12
    Version table 'SVERS' is found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2007-11-13 14:02:12
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is started.
    TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPNTAB' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPNTAB.TSK ORA -l SAPNTAB.log
    TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPNTAB' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error
    INFO: 2007-11-13 14:13:11 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is successfully completed.
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_3' import package is started.
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
    Loading of 'DOKCLU' import package is started.
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_4' import package is started.
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_3' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_3.TSK ORA -l SAPSSEXC_3.log
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_4' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_4.TSK ORA -l SAPSSEXC_4.log
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'DOKCLU' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP11\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DOKCLU.TSK ORA -l DOKCLU.log
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC_3' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC_4' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_4.cmd -dbcodepage 4103 -l SAPSSEXC_4.log -stop_on_error
    TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'DOKCLU' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -stop_on_error
    INFO: 2007-11-13 14:28:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_4' import package is successfully completed.
    TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_2' import package is started.
    TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_2' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_2.TSK ORA -l SAPSSEXC_2.log
    TRACE: 2007-11-13 14:29:10 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC_2' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -stop_on_error
    INFO: 2007-11-13 14:34:56 com.sap.inst.migmon.LoadTask run
    Loading of 'DOKCLU' import package is successfully completed.
    TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_1' import package is started.
    TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2_1' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_1.TSK ORA -l SAPAPPL2_1.log
    TRACE: 2007-11-13 14:35:12 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2_1' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_1.cmd -dbcodepage 4103 -l SAPAPPL2_1.log -stop_on_error
    INFO: 2007-11-13 15:02:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_1' import package is successfully completed.
    TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1_1' import package is started.
    TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1_1' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_1.TSK ORA -l SAPAPPL1_1.log
    TRACE: 2007-11-13 15:02:43 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1_1' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_1.cmd -dbcodepage 4103 -l SAPAPPL1_1.log -stop_on_error
    INFO: 2007-11-13 15:08:06 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_2' import package is successfully completed.
    TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask run
    Loading of 'DD03L' import package is started.
    TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'DD03L' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\DD03L.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DD03L.TSK ORA -l DD03L.log
    TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'DD03L' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
    INFO: 2007-11-13 15:19:29 com.sap.inst.migmon.LoadTask run
    Loading of 'DD03L' import package is successfully completed.
    TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_1' import package is started.
    TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_1' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_1.TSK ORA -l SAPSSEXC_1.log
    TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC_1' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -stop_on_error
    INFO: 2007-11-13 15:22:34 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1_1' import package is successfully completed.
    TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_2' import package is started.
    TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2_2' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_2.TSK ORA -l SAPAPPL2_2.log
    TRACE: 2007-11-13 15:22:42 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2_2' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_2.cmd -dbcodepage 4103 -l SAPAPPL2_2.log -stop_on_error
    INFO: 2007-11-13 15:24:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_1' import package is successfully completed.
    TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_3' import package is started.
    TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0_3' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_3.TSK ORA -l SAPAPPL0_3.log
    TRACE: 2007-11-13 15:24:40 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0_3' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_3.cmd -dbcodepage 4103 -l SAPAPPL0_3.log -stop_on_error
    INFO: 2007-11-13 15:34:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_3' import package is successfully completed.
    TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1_2' import package is started.
    TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1_2' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_2.TSK ORA -l SAPAPPL1_2.log
    TRACE: 2007-11-13 15:34:41 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1_2' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_2.cmd -dbcodepage 4103 -l SAPAPPL1_2.log -stop_on_error
    INFO: 2007-11-13 15:45:42 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1_2' import package is successfully completed.
    INFO: 2007-11-13 15:46:06 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_2' import package is successfully completed.
    TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_1' import package is started.
    TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SCPRSVALS' import package is started.
    TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0_1' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_1.TSK ORA -l SAPAPPL0_1.log
    TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SCPRSVALS' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRSVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRSVALS.TSK ORA -l SCPRSVALS.log
    TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SCPRSVALS' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRSVALS.cmd -dbcodepage 4103 -l SCPRSVALS.log -stop_on_error
    TRACE: 2007-11-13 15:46:10 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0_1' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_1.cmd -dbcodepage 4103 -l SAPAPPL0_1.log -stop_on_error
    INFO: 2007-11-13 15:51:35 com.sap.inst.migmon.LoadTask run
    Loading of 'SCPRSVALS' import package is successfully completed.
    TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_3' import package is started.
    TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2_3' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_3.TSK ORA -l SAPAPPL2_3.log
    TRACE: 2007-11-13 15:51:41 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2_3' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error
    INFO: 2007-11-13 15:56:27 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_1' import package is successfully completed.
    TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_2' import package is started.
    TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0_2' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_2.TSK ORA -l SAPAPPL0_2.log
    TRACE: 2007-11-13 15:56:43 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0_2' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    ERROR: 2007-11-13 15:56:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2_3' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPAPPL2_3.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-11-13 15:56:51 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_3' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSSEXC_3.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_5' import package is started.
    TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_5' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_5.TSK ORA -l SAPSSEXC_5.log
    TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
    TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC_5' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error
    TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
    ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_5' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSSEXC_5.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_2' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPAPPL0_2.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
    Loading of 'FUPARAREF' import package is started.
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
    Loading of 'TODIR' import package is started.
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'FUPARAREF' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\FUPARAREF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" FUPARAREF.TSK ORA -l FUPARAREF.log
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'TODIR' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\TODIR.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" TODIR.TSK ORA -l TODIR.log
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'TODIR' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
    TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'FUPARAREF' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error
    ERROR: 2007-11-13 15:57:40 com.sap.inst.migmon.LoadTask run
    Loading of 'FUPARAREF' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error' exited with return code 2.
    For mode details see 'FUPARAREF.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
    TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
    ERROR: 2007-11-13 15:58:10 com.sap.inst.migmon.LoadTask run
    Loading of 'TODIR' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error' exited with return code 2.
    For mode details see 'TODIR.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SEOSUBCODF' import package is started.
    TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SEOSUBCODF' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SEOSUBCODF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SEOSUBCODF.TSK ORA -l SEOSUBCODF.log
    TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SEOSUBCODF' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -stop_on_error
    ERROR: 2007-11-13 15:58:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSDIC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask run
    Loading of 'E071K' import package is started.
    TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'E071K' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\E071K.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" E071K.TSK ORA -l E071K.log
    TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'E071K' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error
    INFO: 2007-11-13 16:00:13 com.sap.inst.migmon.LoadTask run
    Loading of 'SEOSUBCODF' import package is successfully completed.
    ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSSRC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
    Loading of 'E071K' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error' exited with return code 2.
    For mode details see 'E071K.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SCPRVALS' import package is started.
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SCPRVALS' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRVALS.TSK ORA -l SCPRVALS.log
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP5\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SCPRVALS' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRVALS.cmd -dbcodepage 4103 -l SCPRVALS.log -stop_on_error
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
    TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
    INFO: 2007-11-13 16:01:20 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is successfully completed.
    TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP4\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
    TRACE: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
    ERROR: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPPOOL.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2007-11-13 16:01:57 com.sap.inst.migmon.LoadTask run
    Loading of 'SCPRVALS' import package is successfully completed.
    INFO: 2007-11-13 16:02:01 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is successfully completed.
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_4' import package is started.
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0_4' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_4.TSK ORA -l SAPAPPL0_4.log
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
    TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
    TRACE: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0_4' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error
    ERROR: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSLEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2007-11-13 16:02:23 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is successfully completed.
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
    TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
    ERROR: 2007-11-13 16:02:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0_4' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPAPPL0_4.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-11-13 16:02:41 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is interrupted with R3load error.
    Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPUSER.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2007-11-13 16:02:42 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is successfully completed.
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
    TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
    INFO: 2007-11-13 16:03:10 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is successfully completed.
    INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is successfully completed.
    INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is successfully completed.
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is started.
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER1' import package:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER1.TSK ORA -l SAPUSER1.log
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
    TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER1' import package into database:
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -stop_on_error
    INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is successfully completed.
    INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    WARNING: 2007-11-13 16:04:09
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-11-13 16:04:09
    13 error(s) during processing of packages.
    INFO: 2007-11-13 16:04:09
    Import Monitor is stopped.
    how can i resolve these errors?

    Hi,
    Here are the logs of the jobs that are failing to complete. i am selecting the recommended which is unicode
    SAPALLP2_3.log
    DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
    (DB) ERROR: DDL statement failed
    (CREATE TABLE "TN02Q" ( "MANDT" VARCHAR2(9) DEFAULT '000' NOT NULL , "EINRI" VARCHAR2(12) DEFAULT ' ' NOT NULL , "ANWEN" VARCHAR2(12) DEFAULT ' ' NOT NULL , "PARNA" VARCHAR2(30) DEFAULT ' ' NOT NULL , "PARWE" VARCHAR2(45) DEFAULT ' ' NOT NULL , "COMMT" VARCHAR2(90) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 604)
      error message returned by DbSl:
    ORA-00604: error occurred at recursive SQL level 2
    ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
    (DB) INFO: disconnected from DB
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155648
    SAPSSEXC_3.log
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: REPOSRC created #20071113141340
    DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
    (IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "REPOSRC"
      (SQL error 604)
      error message returned by DbSl:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
    (DB) INFO: disconnected from DB
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155650
    SAPSSEXC_5.log
    DbSl Trace: Failed to register client info: orc=604
    DbSl Trace: ORA-604 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
    (DB) ERROR: DDL statement failed
    (CREATE TABLE "TFTIT" ( "SPRAS" VARCHAR2(3) DEFAULT ' ' NOT NULL , "FUNCNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "STEXT" VARCHAR2(222) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 34164981 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 604)
      error message returned by DbSl:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select name,password,datats#...","Typecheck","kgghtInit")
    (DB) INFO: disconnected from DB
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711
    SAPAPPL0_2.log
    DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=41)
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "ECRM_REPL_KEY~0" ON "ECRM_REPL_KEY" ( "MANDT", "ISUPRODLOG", "OBJNUM" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 604)
      error message returned by DbSl:
    ORA-00604: error occurred at recursive SQL level 2
    ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select con#,obj#,rcon#,enabl...","Typecheck","kgghteInit")
    (DB) INFO: disconnected from DB
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711

  • Logical dataguard SQL apply fails during import on primary database

    I have created logical dataguard using GRID, initially every things works fine.
    One time we had to do import of new data on primary database, that is where the problem started.
    log apply is lagging big time, and i got this error
    StatusRedo apply services stopped due to failed transaction (1,33,8478)
    ReasonORA-16227: DDL skipped due to missing object
    Failed SQLDROP TABLE "USA"."SYS_IMPORT_SCHEMA_01" PURGE
    This table exists on logical dataguard...
    How do we deal with import on logical dataguard, since import generates a lot of redlogs

    Hello;
    These Oracle notes might help :
    Slow Performance In Logical Standby Database Due To Lots Of Activity On Sys.Aud$ [ID 862173.1]
    Oracle10g Data Guard SQL Apply Troubleshooting [ID 312434.1]
    Developer and DBA Tips to Optimize SQL Apply [ID 603361.1]
    Best Regards
    mseberg

  • Problem during import of 121 transport requests to productive system

    Hello
    We have problem during import of transport requests to productive system. Import of 121 transport requests stopped very soon in phase "N" (in TRBAT I have only one entry and in  TRJOB  as well).
    In sm50 there is an BGD running under user DDIC in client 000 now for 14453 seconds (program SAPLSDB2). This should be import.
    In SM37 I can see it as  job "RDDGEN0L" with  repport"RDDGENBB". Based on some literature it should perform "Converting all structure changes generated by the import and recorded in table TBATG, other than the structure changes to matchcode objects." Very interesting  that TBATG has only four entries related to 2 indexes in table "DFKKOPK" , one in table "DFKKREP06" and one" ENQU" for EFKKEXC". (only this last one has not status error)
    For fist two indexes I know they are not present  as objects "LIMU""INDX" in any transport request beeing imported.
    Also on productive system there is no"VOL" and "ZOL"indexes for table "DFKKOPK"(instead they are created on test system ie. not transported from development to test system)
    Last command for that process is "CREATE INDEX "DFKKOPK~HKO" ON "DFKKOPK" ("MANDT", "HKONT", "OPBEL") PCTFREE 10 INITRANS 002 TABLESPACE PSA
    PTR3 STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREAS"
    There is enaught space on disk and in tablespaces (it is an oracle/HPux server).
    Does anyone knows workaroun to solve production

    are you importing these transport requests simultaneously into production?
    I would suggest you try doing in smaller groups of 5 or 10 and then see whether you are able to import the requests
    Rohit

  • Transport Fail -com.sap.aii.utilxi.misc.api.ResourceException:Import

    Hi Experts,
    My Transports through Solution Manager is failing in Production PI. Transports are imported, deployed successfully in Test and Regression environments and working fine. Transport requests are of type Workbench and we are attaching '.tpz' files as Non abap objects. All contain ESR objects, no ID components. Import and Check version steps are good but failing at Deployment step in Production PI.
    Please find the log which I can see in SE10. All the transports failed with the same below error description.
    CTS Import Service - Version 0.94 04.04.2008
    ==============================================================
    Deploy Web service destination = CTSDEPLOY
    Directory = /usr/sap/trans/data
    SDM Deploy URL =
    SLD Deploy URL =
    XI Deploy URL = http://ABC2159161:50000
    Start import with id:4E8B872CA9F100F2E10080000A32109F
    DeployProxy (patch level:0) called with followingparameters:
    Deployable(0)
    Deployable-Type:1
    Deployable-Id:4E6E38F506B601AAE10080000A321063
    Deployable-TransportContainerId:DI1K900677
    Deployable-ContentLocator:/usr/sap/trans/data/DI1K900677/XI7_1
    >>>63.tpz
    Property(0)
    Property-key:TARGETSYSTEMID Property-value:PI1
    Begin CommunicationData-Type[0]:1
    CommunicationData-Address:http://ABC2159161:50000/rep
    CommunicationData-Host:ABC2159161
    CommunicationData-Port:50000
    CommunicationData-User:'filled'
    CommunicationData-Password:'filled'
    Importing archive:XI7_1_A_SAPPI_CM_1.0_of_ABC.com-objs_6
    com.sap.aii.ibtransportclient.XiTransportException: caused by:
    >>>rt failed: Internal error when importing object [Lcom.sap.a
    >>>aused by: com.sap.aii.utilxi.misc.api.ResourceException: Im
    >>>g object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d
    >>>ethodFault: caused by: ClientServerException exception:Impo
    >>>object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d c
    >>>sourceException: Import failed: Internal error when importi
    >>>IWorkspace;@7ffc92d
    End CommunicationData-Type[0]:1
    End import with returncode:'8'
    Deployment
    End date and time : 20111009003401
    Ended with return code:  ===> 8 <===
    Thanks,
    Nabendu.

    Hi,
    I have already informed Basis about these. But do we have any way to check the exact reason for this failure?
    All the above points can ensure the successful transport to Production or not, I am not sure.
    Thanks,
    Nabendu.

  • Error in phase: ADD_TO_BUFFER in SPAM during import of SAPKB70017 and 18

    Hello
    What is problem in this case? During import of SAPKB70017 and SAPKB70018 I get following error(there is no SLOG file in /usr/sap/trans/log):
    The import was stopped, since an error occurred during the phase
    ADD_TO_BUFFER, which the Support Package Manager is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Support Package -> Import queue from the initial
    screen of the Support Package Manager.
    The following details help you to analyze the problem:
        -   Error in phase: ADD_TO_BUFFER
        -   Reason for error:
        -   Return code: 0211
        -   Error message:
    Notes on phase ADD_TO_BUFFER
    In this phase the queue is placed in the transport buffer of your
    system. This phases can terminate due to the following reasons:
    o   TP_INTERFACE_FAILURE: The tp interface could not be called. There is
         an RFC error.
    o   CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included
         in the transport buffer. The program tp is trying to open a file in
         the file system. For more information, refer to the SLOG log file in
         the directory /usr/sap/trans/log.
    A prerequisite of the Support Package Manager is that the Change and
    Transport System (CTS) is configured correctly. For more detailed
    information, read the online documentation available from Help -> SAP
    Library -> mySAP Technology Components -> SAP Web Application Server ->
    Change and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.

    Hi Jan,
    First, check whether your STMS is configured properly. Next check the transport directory and the transport tool from within STMS (system -> check in menu options).
    If these 2 are ok, then you might check from within the OS layer by manually adding to buffer (tp add to buffer <Request No> <SID>).
    Also, I am assuming you are doing this from client 000 with a non-standard user having proper authorizations.
    I believe this to be an issue of permissions at the OS layer.
    Regards
    Siva

  • IDES ECC 6.0 Installation failed at IMPORT ABAP -- Urgent pls....

    Hi Gurus,
    ecc6 installation failed at IMPORT ABAP step (to be precise - 16th step out of 19 steps) while importing  'SAPSSEXC' package .....
    snippets of following logs are below
    1> IMPORT_MONITOR.LOG
    2> SAPINST.LOG
    3> SAPSSEXC.LOG
    <h2>IMPORT_MONITOR.LOG</h2>
    ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l
    SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
    For mode details see 'SAPSSEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2008-01-08 02:42:17
    Cannot start import of packages with views because not all import packages with tables are loaded
    successfully.
    WARNING: 2008-01-08 02:42:17
    1 error(s) during processing of packages.
    INFO: 2008-01-08 02:42:17
    Import Monitor is stopped.
    <h2>SAPINST.LOG</h2>
    WARNING 2008-01-08 02:42:21
    Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion
    com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs
    F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:
    \ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F
    :\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11 -installDir
    C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS -orderBy "" -r3loadExe
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3
    -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code
    103. Output:
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
    Loading of 'SAPAPPL2' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
    ERROR 2008-01-08 02:42:23
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s)
    import_monitor.java.log, import_monitor.log.
    ERROR 2008-01-08 02:42:24
    FCO-00011  The step runMigrationMonitor with step key
    |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|in
    d|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio
    nMonitor was executed with status ERROR .
    <h2>SAPSSEXC.LOG</h2>
    (DB) INFO: D301T~A created
    (DB) INFO: D345T created
    (DB) INFO: D345T~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of D345T completed (6585 rows) #20080107180224
    (DB) INFO: DSYST created
    (DB) INFO: DSYST~0 created
    (IMP) INFO: import of DSYST completed (54353 rows) #20080107194721
    (DB) INFO: DYNPSOURCE created
    (DB) INFO: DYNPSOURCE~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of DYNPSOURCE completed (190478 rows) #20080107205002
    (DB) INFO: ENHSPOTCONTRACT~1 created
    (DB) INFO: ENHSPOTHEADER created
    (DB) INFO: ENHSPOTHEADER~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of ENHSPOTHEADER completed (4078 rows) #20080107205109
    (DB) INFO: INDTEXT created
    (DB) INFO: INDTEXT~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (DB) INFO: PERMISSION created
    (DB) INFO: PERMISSION~0 created
    (IMP) INFO: import of PERMISSION completed (112356 rows) #20080107214109
    (DB) INFO: PERMISSION~IF created
    (DB) INFO: REPOSRC created
    (DB) INFO: REPOSRC~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    ANY POINTERS WILL BE HIGHLY APPRECIATED
    THANKS IN ADVANCE

    no...loading was not finished....it aborted with 'Retry', 'View Log', & Stop options...i retried with no luck...
    this is 'Central system ' installation btw....
    it failed with below error
    ERROR 2008-01-08 02:42:23
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    <h2>IMPORT_MONITOR.LOG</h2>
    INFO: 2008-01-07 16:33:26
    Import Monitor is started.
    CONFIG: 2008-01-07 16:33:26
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11
    installDir=C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2008-01-07 16:33:26
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2008-01-07 16:33:26
    List of packages with views: 'SAPVIEW'.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2008-01-07 16:33:26
    Data codepage 4103 is determined using TOC file 'F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
    TRACE: 2008-01-07 16:33:28 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    INFO: 2008-01-08 00:15:00 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is successfully completed.
    TRACE: 2008-01-08 00:15:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2008-01-08 00:15:27 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
    INFO: 2008-01-08 00:15:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
    TRACE: 2008-01-08 00:15:58 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
    TRACE: 2008-01-08 00:16:02 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
    INFO: 2008-01-08 00:49:00 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is successfully completed.
    TRACE: 2008-01-08 00:49:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2008-01-08 00:49:40 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
    TRACE: 2008-01-08 00:50:11 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
    INFO: 2008-01-08 00:53:51 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is successfully completed.
    TRACE: 2008-01-08 00:54:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2008-01-08 00:54:40 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport3\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
    TRACE: 2008-01-08 00:54:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
    INFO: 2008-01-08 01:02:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is successfully completed.
    TRACE: 2008-01-08 01:02:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2008-01-08 01:02:50 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
    TRACE: 2008-01-08 01:03:11 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
    INFO: 2008-01-08 01:09:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is successfully completed.
    TRACE: 2008-01-08 01:09:46 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2008-01-08 01:09:51 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
    TRACE: 2008-01-08 01:09:55 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
    INFO: 2008-01-08 01:14:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is successfully completed.
    TRACE: 2008-01-08 01:14:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2008-01-08 01:14:18 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
    TRACE: 2008-01-08 01:14:21 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
    INFO: 2008-01-08 01:15:50 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is successfully completed.
    TRACE: 2008-01-08 01:16:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2008-01-08 01:16:19 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
    TRACE: 2008-01-08 01:16:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
    INFO: 2008-01-08 01:17:55 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is successfully completed.
    TRACE: 2008-01-08 01:18:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2008-01-08 01:18:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
    TRACE: 2008-01-08 01:18:31 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
    INFO: 2008-01-08 01:18:43 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is successfully completed.
    TRACE: 2008-01-08 01:18:46 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2008-01-08 01:18:48 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
    TRACE: 2008-01-08 01:18:50 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
    INFO: 2008-01-08 01:20:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is successfully completed.
    TRACE: 2008-01-08 01:20:15 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
    TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
    INFO: 2008-01-08 01:20:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is successfully completed.
    TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
    TRACE: 2008-01-08 01:20:46 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
    INFO: 2008-01-08 01:20:51 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is successfully completed.
    TRACE: 2008-01-08 01:21:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2008-01-08 01:21:22 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
    TRACE: 2008-01-08 01:21:23 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
    INFO: 2008-01-08 01:21:25 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is successfully completed.
    TRACE: 2008-01-08 01:21:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is started.
    TRACE: 2008-01-08 01:21:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER1' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER1.TSK MSS -l SAPUSER1.log
    TRACE: 2008-01-08 01:21:52 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER1' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -loadprocedure fast
    INFO: 2008-01-08 01:21:53 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is successfully completed.
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
    INFO: 2008-01-08 01:22:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
    For mode details see 'SAPSSEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2008-01-08 02:42:17
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2008-01-08 02:42:17
    1 error(s) during processing of packages.
    INFO: 2008-01-08 02:42:17
    Import Monitor is stopped.

  • Variable not set (error 91)/Error during import (error 102)/execut bat file

    We are on BO 11.5.0.0 and using the COM SDK with Visual Basic to run multiple reports (sometimes multiple flavors of the same report) through a bat file.
    If we run the reports single-threaded through the bat file, the reports run fine.  However, if multiple versions of the bat file start at approximately the same time, we get one of two errors:
    91 Object variable or With block variable not set
    102 Error during import document -
    Here's the part of the code with the problem:
    Dim BOapp As busobj.Application
    Dim receiveDoc As busobj.Document
    Set BOapp = New busobj.Application
    BOapp.Interactive = False
    BOapp.Logon strUser, strPass, strFromSystem, "Enterprise", False, False
    BOapp.Visible = False
    Set receiveDoc = BOapp.Documents.OpenFromEnterprise(strFromRep, strFromFolder, boFolder)
    receiveDoc.SaveAs (strDocumentPath & strFromRep & ".REP")
    Values for the following variables are passed in from the bat file:
    strUser
    strPass
    strFromSystem
    strFromRep
    strFromFolder
    strDocumentPath
    If it fails on the OpenFromEnterprise statement, we get the 102 error.
    If it fails on the SaveAs statement, we get the 91 error.
    Running it through debug hasn't helped, since we are running only one report.
    Any thoughts on what could be going wrong?
    Thanks in advance

    I have tried this running the VB code on my desktop (outside of the bat file) and nothing out of the ordinary occurs.  The VB code runs fine with only one occurrence.
    I had seen on other posts "ThisDocument" and didn't know if it would be applicable in this situation.  I also wasn't sure how it should be used based on the rest of my code.  Would "ThisDocument" make a difference?
    Thanks again

  • Dev Workplace install failing on "import java dump"

    Trying to install the developer NW workplace(2004s) with maxdb(7.60) on windows XP pro (32 bits).
    I am using The following SAP dvd's: 51031374_dev_ws_04s,
    51031391_2004s_kernel7_lin_win and 51031410_maxdb_760.
    Installation is failing while importing the java dump (step 21).
    The relevant error is:
    SEVERE: DB Error during import of BC_SL_ACTIVE_PARTS
    Feb 21, 2006 4:08:55 PM com.sap.inst.jload.Jload printSQLException
    SEVERE: Message: The object of type java.sql.Date with the value
    '2005-10-06 15:00:00.0' assigned to host variable 5 is not normalized. It
    must not contain time components in the time zone running the virtual
    machine.
    Feb 21, 2006 4:08:55 PM com.sap.inst.jload.Jload printSQLException
    SEVERE: SQLState: SAP06
    Feb 21, 2006 4:08:55 PM com.sap.inst.jload.Jload printSQLException
    SEVERE: ErrorCode: 1001124
    I aslo tried upgrading maxdb to 7.60-21 (from the default -9) but that did not help.
    It seem like the dump is trying to import an improperly formatted timestamp inside a date field in maxdb (or something of that sort)
    I was thinkign of tryimg to fix the dump, but it's a 800MB binary dump so i guess that's out.
    Anyhow, anybody as a clue of what's going on ?? (ie: db setting or something).
    Thank you.

    Hello folks,
    Today I also tried to install SAP Netweaver 7.0 SR3 Developer Workplace on Windows Vista. But Installation process has stop at phace 20 ( Import Java dump) line. Even I already changed the timezone according to some of yours advice, but still the problem is same. I tried it 2nd time. I uninstalled MaxDb and uninstall SAP NW and restart system and resinstall it.
    Here is log view for reference:
    INFO 2008-03-25 01:42:43.963
    Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/launcher.jar" -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sql.connect.OpenSQLConnectInfo "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/tc_sec_secstorefs.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/jdbc20.jar" create_dr jdbc/pool/NW4 com.sap.dbtech.jdbc.DriverSapDB jdbc:sapdb://Obaid-PC/SNW?timeout=0&spaceoption=true&unicode=true SAPNW4DB XXXXXX NW4
    Obaid-PC/sapmnt/NW4/SYS/global/security/data/SecStore.properties
    Obaid-PC/sapmnt/NW4/SYS/global/security/data/SecStore.key" finished with return code 0. Output: Driver successfully created
    INFO 2008-03-25 01:42:44.494
    Execute step requestJavaDumpInStepPhase of component |NW_Workplace|ind|ind|ind|ind|0|0|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Jload|ind|ind|ind|ind|9|0
    INFO 2008-03-25 01:42:44.991
    Execute step exitStepIfParallelABAPImport of component |NW_Workplace|ind|ind|ind|ind|0|0|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_JExecute step exitStepIfParallelABAPImport of component |NW_Workplace|ind|ind|ind|ind|0|0|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_J
    Please help me what could be other reason, how can i resolve this issue. I need to install it.
    thanks
    Obaid.

  • Mail fails to import messages after 10.8.5 update

    After the update Mail fails to import my messages and then quits.
    First screen says: Welcome to Mail. To use the new features your existing Mail messages need to be imported....
    Then when I click continue it says: The import failed. An error occurred during the import. Make sure you have available space in your home folder and try again.
    I run mail from inside the container (MacOS folder) and here's what it reads:
    Last login: Mon Oct 21 22:39:50 on ttys001
    /Applications/Mail.app/Contents/MacOS/Mail ; exit;
    Gustavos-MacBook-Air:~ calazans$ /Applications/Mail.app/Contents/MacOS/Mail ; exit;
    2013-10-21 23:03:45.907 Mail[778:707] Using V2 Layout
    2013-10-21 23:04:43.483 Mail[778:9617] Copy from /Users/calazans/Library/Mail/V2/MailData/Envelope Index to /Users/calazans/Library/Mail/V2/MailData/Envelope Index-26 failed with 10: not an error
    logout
    [Process completed]
    I have already reinstalled combo 10.8.5
    I have already booted on recovery console and repaired permissions
    I have already installed the Supplemental update 10.8.5
    I have created another standard user and inside this new account Mail will work perfectly.
    Nothing worked so far. Cherry on the cake : I have a message saying I have a recall on my MBAir SSD drive.
    Please advise on how to solve this issue !
    Cheers,
    ZChef

    Intermediate answer: The app launched correctly and the import process has started.
    It is taking ages though. Over 3 hours for around 30K messages.
    The message count sometimes gets stuck for 20-30 minutes or so and then starts counting again...
    There are ~5K messages left to be imported. I'll let you know if it goes ok.
    Stay tuned for the next and hopefully last episode.
    Cheers,
    ZChef

  • Mail failed to import after Mavericks upgrade

    Just upgraded to Mavericks and have all current updates - went to open mail and got the following message:
    Mail failed to import.
    An error occurred during the import. Make sure you have available space in your home folder and try again.
    I have a pretty "clean" Macbook Air - not much on it so can't imagine I'm anywhere close to not having available space. Help!

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Transport failed in PRD Server ECC 6.0

    Hi to all,
    I have one issue in my PRD system. The transport system somehow working and sometimes failed to import. I need to retry several times before it can be transported. I check the log file the same message occurred.:-
    <i>Log File:                /usr/sap/trans/log/DEVR904107.PRD
               Execution of programs after import (XPRA)
               Transport request   : DEVK904107
               System              : PRD
               tp path             : tp
               Version and release: 372.03.35 700
               Temporary log /usr/sap/trans/tmp/DEVR904107.PRD not found
               Execution of programs after import (XPRA)
               End date and time : 20071203141456
               Ended with return code:  ===> 12 <===
               ######################################</i>
    Eventhough I copy the file from /usr/sap/trans/log to /usr/sap/trans/tmp sometimes it still failed to transport. I check the TP setting in my DEV, TST and PRD it shows no error. I even check file permission in usr/sap/trans and it is already given to full permission. In fact this only happens in my PRD system. I check on OSS no answers found.
    By the way my PRD system is running on SUSE10 Ent. Linux with MaxDB 7.6. Need your help guys.
    Thanks in advance.

    Sorry for the late reply. But i just faced a similar issue and want to make sure i inform future users about it.
    Please check that the /usr/sap/trans has been mounted on the application servers as well as the CI/DB instance.
    Once this was done on my end the issue got resolved.

  • When transporting multiproviders and cubes transport failed.

    HI Experts,
    When transporting cubes and multiproviders in a request the transport failed with return code 8.
    The described below as:
    Start of the after-import method RS_CUBE_AFTER_IMPORT for obje
    Error/warning in dict. activator, detailed log    > Detail   
    /BIC/L101078 (specify a primary key)                         
    Table /BIC/L101078 could not be activated                    
    Return code..............: 8                                 
    DDIC Object TABL /BIC/L101078 has not been activated         
    Error when activating InfoCube 101078                        
    Error/warning in dict. activator, detailed log    > Detail   
    /BIC/L101077 (specify a primary key)                         
    Table /BIC/L101077 could not be activated                    
    Return code..............: 8                                 
    DDIC Object TABL /BIC/L101077 has not been activated         
    Error when activating InfoCube 101077                        
    Error/warning in dict. activator, detailed log    > Detail   
    /BIC/L101078 (specify a primary key)                         
    Table /BIC/L101078 could not be activated                    
    Return code..............: 8                                 
    DDIC Object TABL /BIC/L101078 has not been activated         
    Error when activating InfoCube 101078                        
    Error/warning in dict. activator, detailed log    > Detail   
    /BIC/L101077 (specify a primary key)                         
    Table /BIC/L101077 could not be activated                    
    Return code..............: 8                                 
    DDIC Object TABL /BIC/L101077 has not been activated         
    Error when activating InfoCube 101077                        
    Error/warning in dict. activator, detailed log    > Detail   
    /BIC/L101078 (specify a primary key)                         
    Table /BIC/L101078 could not be activated                    
    Please let us know if anyone has come across similar kind of issue.
    Regards,
    Monalisa Mohanty

    Issue seems to be with the aggregates maintained in the cube.
    Is your aggregates were properly maintained in your Dev system when you have collected it in your transport?
    Check the same and also use overwrite option when you are trying to import the transport in the target systems.
    If the aggregates are properly maintained then check the import once again and see if that works fine with the overwrite mode. If not then you need to collect your objects again in a new transport.
    Hope this helps.
    Murali

  • BW 7.0: several ORA-01408 during import

    Hi,
    I'm copying my BW system with export/import procedure from prd to dev. During import, and I think only on fact-tables, there are several ORA-01408 such as:
    DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-1408 occurred when executing SQL stmt (parse error offset=57)
    (DB) ERROR: DDL statement failed
    (CREATE  INDEX "/BIC/EAV_FAORDT~P" ON "/BIC/EAV_FAORDT" ( "KEY_AV_FAORDTP" , "KEY_AV_FAORDTT" , "KEY_AV_FAORDTU" , "KEY_AV_FAORDT1" , "KEY_AV_FAORDT2" , "KEY_AV_FAORDT3" , "KEY_AV_FAORDT4" , "KEY_AV_FAORDT5" , "KEY_AV_FAORDT6" , "KEY_AV_FAORDT7" , "KEY_AV_FAORDT8"  ) TABLESPACE PSAPNBDFACT STORAGE (INITIAL 188743680 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 1408)
      error message returned by DbSl:
    ORA-01408: such column list already indexed
    (DB) INFO: disconnected from DB
    Note 885441 describe to igonere this indexes error... is it ok for me?
    Source system has got:
    SAP_ABA     700     0018     SAPKA70018
    SAP_BASIS     700     0018     SAPKB70018
    PI_BASIS     2006_1_700     0008     SAPKIPYM08
    ST-PI     2008_1_700     0000     -
    SAP_BW     700     0020     SAPKW70020
    FINBASIS     600     0015     SAPK-60015INFINBASIS
    SEM-BW     600     0015     SAPKGS6015
    BI_CONT     703     0012     SAPKIBIIQ2
    ST-A/PI     01L_BCO700     0000     -
    So... it should enough updated to exclude note 925309.
    Regards.
    Thankyou....

    Also several ORA-01452... have you got any idea?
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "/BIC/FACC_PCO1~0" ON "/BIC/FACC_PCO1" ( "KEY_ACC_PCO1P", "KEY_ACC_PCO1T", "KEY_ACC_PCO1U", "KEY_ACC_PCO11", "KEY_ACC_PCO12", "KEY_ACC_PCO13", "KEY_ACC_PCO17" ) TABLESPACE PSAPNBDFACT STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 1452)
      error message returned by DbSl:
    ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
    (DB) INFO: disconnected from DB

Maybe you are looking for

  • My iphone 4 is not charging and when I connect it on the pc it says device not recognized!!pls help!!

    Hello guys!!Pls help me if someone knows what should I do.my iphone was working perfectly so far but a couple of days ago it stopped charging.its not charging neither with the a/c adaptre nor with the usb through my pc.it says device not recognized..

  • greater than symbol inserted at bottom of php pages in all pages

    I've coded for years and never seen this.  At the bottom of all of my pages, no matter what I do, the following gets added in "<html>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>"  obviously these symbols show up and make all my webpages look awful.  I de

  • My MBP with OS 10.6.8, MRT & Syslogd are earting up processor

    Hi There, I have recently observed the slow in my MBP and found that they are 2 processes which are most of the time eating up processor. Which are Syslogd and MRT.  I really don't know about MRT process but i have searched the cause of syslogd. In m

  • Hyperion Reports Batch Email Issue

    Hi All, I am having trouble getting Hyperion Reports (v11) to send emails after running a batch. We have gotten it to work with Taskflows in the Hyperion Workspace but not in Hyperion Reports. Does Reports use the same email address as Taskflows? [em

  • Batch reservation & Allocation in process order

    I am allocating batch to process order components(for active ingridient)While I am allocating the batch I am able to select the batch which has all of its quantity reserved,which is not desireble.Any solutions please??/ Eg.In MMBE my batch stock(say