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

Similar Messages

  • Statistics gathered during import

    Does after IMP import the tables are analyzed automatically?
    When i done import process of TEST user
    imp system/manager file=/home/oracle/test.dmp FROMUSER=TEST TOUSER=TEST
    and when i execute following query
    SELECT table_name,last_analyzed FROM DBA_TABLES WHERE owner=TEST'
    I find that table/indexes are analyzed automatically.
    Does it means statistics are gathered automatically during import?
    Oracle 10.2.0.1

    Refer to this link please
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#i1020893
    It seems it takes statistics for tables during export
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com

  • SAP database tables - Column statistics not found for table in DB02 - During import, inconsistent tables were found - Some open conversion requests still exist in the ABAP dictionary.

    Hi Experts,
    I'm implementing SAP note 1990492 which requires manual implementation. Implementation includes modifying standard tables (i.e. append
    the structure FIEU_S_APP_H to table FIEUD_FIDOC_H). After this I've adjusted the table in SE14 (Database Utility). I've done checks in SE14 and it shows the table is consistent.
    But during DB02 -> Space folder -> Single table analysis -> Input table name -> Indexes tab -> Upon clicking statistics, there is a warning "Column statistics not found for table".
    Our basis team is implementing an Add-On in the development system related to RWD Context Sensitive Help. They cannot proceed due to the following inconsistencies found in the table.
    Screenshot error from the activity:
    Screenshot from DB02:
    I'm an ABAP developer and have no other ideas on what to do. Thanks in Advanced.

    Hi All,
    We were able to fix the issue through the following:
    1. Call transaction
    SE14.
    2. Enter the name of
    the table and choose "Edit".
    3. Choose
    "Indexes".
    4. Select the index
    and choose "Choose (F2)".
    5. If you choose
    "Activate and adjust", the system creates the index again and it is
    consistent.
    6. Check the object
    log of this activation.
    7. If an error
    occurs, eliminate the cause and reactivate the index.

  • 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

  • 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

  • Import Table Statistics to another table

    Hi,
    Just like to know if I can use dbms_stats.import_table_stats to import table statistics to another table?
    Scenario:
    I exported the table statistics of the table (T1) using the command below.
    exec dbms_stats.export_table_stats('<user>','T1',NULL,'<stat table>');
    PL/SQL procedure successfully completed.
    And then, I have another table named T2, T1 and T2 are identical tables. T2 does not have statistics (I intentionally did not run gather statistics). I am wondering
    if I can import table statistics from T1 to T2 using dbms_stats package?.
    For what I understand, statistics can be imported back at the same table which is T1 but not for another table using dbms_stat package. If I am wrong, anyone can correct me.
    Thanks

    hi
    just try ;-) you lose nothing probably,
    check afterwards last_analyzed value for that table in user_tables
    if something is wrong, run regular stats

  • ORA-02373 error on expdp, table failed to import!!

    Hi All,
    Would need a little help from you guys. I am trying to take export of an schema, and as the expdp continues, it throws error while exporting one of the tables. I tried looking over the net, but found nothing on this.
    I think it is high time to have a say from the pros :) !!
    Here goes the error:
    =========================================================================
    ORA-31693: Table data object "SCHEMA-NAME"."TABLE-NAME" failed to load/unload and is being skipped due to error:
    ORA-02354: error in exporting/importing data
    ORA-02373: Error parsing insert statement for table "SCHEMA-NAME"."TABLE-NAME".
    ORA-00904: : invalid identifier
    =========================================================================
    The DB Server is 11g.
    Any kind of help will be greatly appreciated!
    Thanks in Advance.
    Noman A.

    Hi Kumar,
    This is the description of the table:
    Name Null Type
    ID NOT NULL VARCHAR2(64)
    COL-1 VARCHAR2(128)
    COL-2 VARCHAR2(128)
    COL-3 NOT NULL VARCHAR2(64)
    COL-4 NOT NULL VARCHAR2(64)
    COL-5 NOT NULL VARCHAR2(64)
    COL-6 NOT NULL VARCHAR2(64)
    COL-7 VARCHAR2(64)
    COL-8 VARCHAR2(255)
    COL-9 NOT NULL VARCHAR2(64)
    COL-10 NOT NULL TIMESTAMP(6)
    COL-11 NOT NULL TIMESTAMP(6)
    COL-12 NOT NULL CHAR(1)
    COL-13 BLOB()
    COL-14 VARCHAR2(512)
    COL-15 CHAR(3)
    Thanks
    Noman A.

  • Creating record on second main table during import

    Hello all,
    I am importing data to a main table (materials), and I have a second main table linked to the materials main table to store supporting data.  Assuming I have a new record being imported that contains an entity that doesn't exist in that second main table, is it possible to create a record inside the second main table?  This functionality exists for lookup tables, if the lookup record doesn't exist you can configure the map to create the record in the lookup table.  Can the same thing be accomplished with multiple main tables?  I'm having trouble with this because I can't get any field aside from the primary key on the second main table to show up in the destination fields in the import manager.

    Hi,
    As you said, Assuming I have a new record being imported that contains an entity that doesn't exist in that second main table, is it possible to create a record inside the second main table?
    This scenario is quite possible.
    I have a Work Around and it should work according to me...
    See, In this case you have to create two maps, one for Main table (Primary) Import and another for Second Main table(Secondary).
    Before Importing Main table(Import) this file should be Imported to Second Main table import(Secondary) by putting that file to ready inbound port of Second Main table.
    So, Records entities that do not exist in secondary main table will get created and for existing records will get updated.
    Now when the same Source file import for Main table, that record entity would be already there in Secondary main table and as such you would not face any issue while importing through main table.
    Kindly let me know if you face any issue.
    Thanks and Regards,
    Mandeep Saini

  • Can R3load skip some tables during import?

    We use DB-independent method to export/import SAP DB.
    Now the export is done by R3load.
    We want to exclude some tables in the import.
    I know  that R3load has an option "-o  T"  to  skip tables.
    However, we need to know
    1)  the exact syntax to put into export_monitor_cmd.properties
    2) still need the table structures to be imported even no data is wanted.
    Thanks!

    Lee and Rob,
    Thank you both for your responses.
    Rob, thank you sir... I appreciate greatly some possible solutions to implement.  The CollectionPreseter sounds very interesting.  I am relatively new to Light Room 3 (working through Kelby's book at the moment tryng to learn), so please excuse any lightly thought out questions.
    You mentioned the idea of setting up multiple collections where each would have its own preset.  So lets talk about a possible workflow scenario in order to help me understand whether I comprehend the functionality of what this plugin could do.
    Lets say I have 3 Collections with each having one preset assigned.
    Is it possible ->
    Workflow A
    That after I import photos and then assign into Collection 1, CollectionPreseter will assign the defined preset on Collection 1.
    Once applied, does the ability exist to then move the pictures from Collection 1 into Collection 2 (while keeping Collection 1 preset) to apply it's preset and then lastly Moving the pictures from Collection 2 (while keeping Preset 1 and 2) into Collection 3 to apply its preset? with Final Export.
    OR
    Workflow B
    Would the flow have to be something like this based on above:
    Import and place into Collection 1 (preset 1 is applied).  Export and Save
    Reimport and place into Collection 2 (preset 2 is applied). Export and Save.
    Reimport and place into Collection 3 (preset 3 is applied). Export and Save Final.?
    The other that I have not raised is what about droplets (actions) with Photoshop CS?  Are multiple droplets able to be applied and ran in a batch if I integrated with CS that way?
    Thank you...
    Steven

  • 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

  • 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.

  • UNDOTBS - ERRORS DURING IMPORT

    Hi,
    I have an Oracle 9i database running on a Linux box. It was running out of disk space (only 2GB free). I decided to create a new undotbs (UNDOTBS2), on a separate Disk (/usr/oracle/local/), because the original undotbs (/usr/oracle/data/UNDOTBS1) was quite big 3.7 GB!
    I switched to the new undotbs(2), and Oracle was happy all day long. The thing is, I have a script that drops 2 schema during the night, recreates them and import data into these 2 schemas,from a dump file (another database).
    This morning I noticed that the import process aborted (see error messages below),complaining that the UNDOTBS1 tablespace "couldn't be read at this time'. What is that mean?
    The following are the steps I had to follow, to be able to import the data.
    1. Move /usr/oracle/dataUNDOTBS1 to /usr/oracle/local/
    (both TS are on the same directory).
    2. Both TS are online.
    3. Oracle is using UNDOTBS1.
    I would like to get rid of one of these TS, but I afraid that by doing so, the nightly script will abort again.
    Any ideas?! Thanks, Juvenal
    -----ERROR MESSAGE BEGINS--------------------------------
    Import: Release 9.2.0.3.0 - Production on Tue Feb 3 23:07:24 2004
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to: Oracle9i Release 9.2.0.3.0 - Production
    JServer Release 9.2.0.3.0 - Production
    Export file created by EXPORT:V09.02.00 via conventional path import done in US7ASCII character set and AL16UTF16 NCHAR character set import server uses WE8ISO8859P1 character set (possible charset conversion) . importing IBT's objects into IBT . importing IBT_SECURITY's objects into IBT_SECURITY . importing IBT's objects into IBT
    . . importing table "ACCOUNT" 68795 rows imported
    . . importing table "ACCOUNTING_BRANCH" 101 rows imported
    . . importing table "ACCOUNTING_COMPANY" 80 rows imported
    . . importing table "ADDRESS" 207761 rows imported
    IMP-00017: following statement failed with ORACLE error 604: "CREATE UNIQUE INDEX "PK_ADDRESS" ON "ADDRESS" ("ADDR_ID" ) PCTFREE 10 INIT" "RANS 2 MAXTRANS 255 STORAGE(INITIAL 245760 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "IBT_INDEX" NOLOGGING"
    IMP-00003: ORACLE error 604 encountered
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00376: file 2 cannot be read at this time
    ORA-01110: data file 2: '/usr/oracle/data/undotbs01.dbf'
    IMP-00017: following statement failed with ORACLE error 604: "CREATE INDEX "IND_ADDR_SUB_ID" ON "ADDRESS" ("ADDR_SUB_ID" ) PCTFREE 10 IN" "ITRANS 2 MAXTRANS 255 STORAGE(INITIAL 245760 FREELISTS 1 FREELIST GROUPS 1)" " TABLESPACE "IBT_INDEX" NOLOGGING"
    IMP-00003: ORACLE error 604 encountered
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00376: file 2 cannot be read at this time
    ORA-01110: data file 2: '/usr/oracle/data/undotbs01.dbf'
    -----ERROR MESSAGE ENDS--------------------------------

    I think the filesystem where the new datafile is does not have the correct permission to allow Oracle writes on it.
    apply this command and reply the result:
    ls -l /usr/oracle/data
    the group has be "dba"
    if you want to change the permission on that folder you have to do this connected as root:
    chown oracle.dba /usr/oracle/data
    Joel Pérez
    http://otn.oracle.com/experts

  • IMPDP take too much time at TABLE STATISTICS

    Hi experts.
    on of my database is taking taking to much time during IMPDP at TABLE STATISTICS. it take alomost 20 mints to import TABLE STATISTICS while on the other hand all other objects are imported within 5 to 7 minits.
    my database version is 10.2.0.1 and O/S Red Hat Enterprise Linux AS release 3 (Taroon Update 5)
    please guide how i can fix this issue
    thanx in Advance.
    regards

    please guide how i can fix this issueSeems to be a bug. Upgrade to 10.2.0.4.0 or 10.2.0.5.0 and check again.
    Ronny Egner
    My Blog: http://blog.ronnyegner-consulting.de

  • Microsoft Lync Server 2013, Backup Service user store backup module detected items having pool ownership conflict during import.

    Dear Team,
    I have two Enterprise lync 2013 pools, abcPool and abcpool1. abcPool1 has got two servers, Server1 and server2. and abcpool has one FE server named "Server 3". and they have pool pairing.
    Replication was fine between them when i had only one FE server in each pool, one day FE service broke on one of the FE server on abcpool1 and failed to start so i had to do failover to another pool, at that time i introduced one more FE in abcPool1, that
    why now 2 FEs in abcPool2. Server1 FE service was resolved by reinstalling the binaries. However after that im unable to get the backupservice state to normal, i tried the below articles with no luck,
    http://social.technet.microsoft.com/Forums/lync/en-US/0403621e-26b6-4cd0-bbca-8534a20de665/backup-service-pool-ownership-conflict-during-import?forum=lyncdeploy 
    http://msucmenow.blogspot.in/2013/05/troubleshooting-lync-2013-pool-pairing.html
    "Event on Server 1"
    Log Name:      Lync Server
    Source:        LS Backup Service
    Date:          1/21/2014 8:02:33 AM
    Event ID:      4073
    Task Category: (4000)
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      ABC.net
    Description:
    Microsoft Lync Server 2013, Backup Service user store backup module detected items having pool ownership conflict during import.
    Items having pool ownership conflict: 
    ItemId: 1b3be172-b121-43cf-bd4e-b3d368eae6a9, DocId: 7972, DocName: urn:hcd:[email protected]
    ItemId: 1b3be172-b121-43cf-bd4e-b3d368eae6a9, DocId: 7973, DocName: urn:lcd:[email protected]
    ItemId: 1b3be172-b121-43cf-bd4e-b3d368eae6a9, DocId: 7974, DocName: urn:upc:[email protected]
    PS C:\Users\lyncadmin> Get-CsBackupServiceStatus -PoolFqdn pool1.net | fl
    ActiveMachineFqdn   : abc1.net
    OverallExportStatus : SteadyState
    OverallImportStatus : ErrorState
    BackupModules       : {UserServices.PresenceFocus:[SteadyState,ErrorState],
                          ConfServices.DataConf:[FinalState,NormalState],
                          CentralMgmt.CMSMaster:[FinalState,NotInitialized]}
    Following error in "Lync Server" logs on server3 on abcPool.
    Log Name:      Lync Server
    Source:        LS Backup Service
    Date:          1/21/2014 9:37:47 AM
    Event ID:      4069
    Task Category: (4000)
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:     SQL1.net
    Description:
    Microsoft Lync Server 2013, Backup Service user store backup module encountered an exception that was handled gracefully when importing document batch.
    Batch file: UserServices\PresenceFocus\1-UserServices-8\Data\488bc218-9954-4caf-a5da-89efdb7b85a7_0_1562.xml.
     Exception: System.Data.SqlClient.SqlException (0x80131904): Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.Batch' directly or indirectly in database 'rtcxds' to update, delete, or
    insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.
    Log Name:      Lync Server
    Source:        LS Backup Service
    Date:          1/21/2014 9:52:45 AM
    Event ID:      4064
    Task Category: (4000)
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:     SQL1.net
    Description:
    Microsoft Lync Server 2013, Backup Service user store backup module encountered an exception that was handled gracefully during export.
    Additional Message: 
     Exception: System.IO.IOException: The process cannot access the file '\\SQl1.net\LyncShare\1-BackupService-10\BackupStore\UserServices\PresenceFocus\Cookie\Cookie.zip' because it is being used by another process.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath,
    Boolean checkHost)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
    Praveen | MCSE Messaging 2003

    When you add a new FE in pool acdpool1, please check you have run the following:
    <system drive>\Program Files\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
    For the details, check
    http://technet.microsoft.com/en-us/library/jj204773.aspx
    Lisa Zheng
    TechNet Community Support

Maybe you are looking for

  • ITunes 10 glitch on Macbook Pro (Snow Leopard)

    ..this happens whenever i press the plus sign for it to become the mini version, but when i maximize it again, a weird glitch occurs that won't go away until i perform a killall iTunes in Terminal. I dont know why it happens, it never did it before u

  • Keypad problem

    Dear All, I have problem with my keypad,some characters do not work for example: Number:7,9 and alphabet M,N.even the key pushing for a long time still not appear . Any one can help me? Best regards T.S.Pasaribu  T.S.Pasaribu

  • Creatinig an intranet wiki for an OS X and Windows enviroment.

    I have a question about putting together and implementing a single wiki site for a school district that uses mac and windows systems.  The issue I am having is I need them to be able to use one single site for this purpose.  However I am sure there i

  • SQL delete statement

    The common way to delete a specific row in a table is: DELETE FROM customerTable WHERE customerName =ABC AND customerID =123; However, are there any other alternative way to delete the specific row instead? Because my problem is i must link the name

  • Can i take a picture of a video in iPhoto?

    If it's possible, how is it?