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

Similar Messages

  • 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 standby: SQL Apply too slow

    Hi all,
    I have a question regarding SQL Apply performance in logical standby. There are two kind of operations that are remarkably slow when applying them on logical standby. These are "truncate table" and "delete from table" operations.
    When logical standby pick up one of mentioned statements from logs one of appliers start working whereas rest others are waiting. It looks like standby hang and very slow sql apply is moving on gradually and finally when operation completes standby is behind primary for 4 or 5 or even 8 hours.
    What can be done in this regard to speed up sql apply and alleviate this situation?
    Best Regards,
    Alex

    Are you absolutely sure that the truncate is the problem (and deletes). How did you check it?
    You can use LogMiner to check what are most of the commands in the log currently applied. I use this:
    BEGIN
    sys.DBMS_LOGMNR.ADD_LOGFILE( LOGFILENAME => '/home/oracle/arc_43547_1_595785865.arc', OPTIONS => sys.DBMS_LOGMNR.ADDFILE);
    END;
    BEGIN
    sys.DBMS_LOGMNR.START_LOGMNR( OPTIONS => sys.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG);
    END;
    SELECT seg_owner,seg_name,table_name,operation,COUNT(1) FROM V$LOGMNR_CONTENTS
    GROUP BY seg_owner,seg_name,table_name,operation
    ORDER BY COUNT(1) DESC
    BEGIN
    sys.DBMS_LOGMNR.END_LOGMNR();
    END;
    Most of the times in our cases when SQL Apply is slow is because of high activity on particular object. This can be detected by high number of DMLs for that object using LogMiner. If this object is not needed on the logical standby you can skip it and thus SQL Apply will be faster because it will not apply changes for this particular one. If it's needed and this is not a regular rate, then you can skip it temporarily, turn on SQL Apply , after problematic logs are applied, turn off SQL Apply, instantiate the object and unskip it, turn on sql apply again.
    Another thing that can drastically slowdown SQL Apply is the size of memory available for SQL Apply(Alert log shows that max is ~4.5GB or something like this, I'm not sure )
    You can increase it with something like this:
    ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    BEGIN
    DBMS_LOGSTDBY.APPLY_SET('MAX_SGA', 3000); -- set to 3000 MB
    END;
    ALTER DATABASE START LOGICAL STANDBY APPLY;
    You have to increase it if the following reports:
    SELECT NAME, VALUE FROM V$LOGSTDBY_STATS
    WHERE NAME LIKE '%page%' OR
    NAME LIKE '%uptime%' or name like '%idle%';
    that 'bytes paged out' increases if run every few seconds during slow SQL Apply.
    I hope that it's something that can be fixed using the above info. If no, please comment and share your investigations.
    Thanks

  • Logical Standby SQL Apply Using Incorrect Decode Statement

    We are seeing statements erroring out on our logical standby that have been rewritten (presumably by sql apply) with decode statements that don't appear to be correct. For example, here is one of the rewritten statements.
    update /*+ streams restrict_all_ref_cons */ "CADPROD"."OMS_SQL_STATEMENT" p
    set *"APPLICATION"=decode(:1,'N',"APPLICATION",:2)*,
    "STATEMENT"=dbms_reputil2.get_final_lob(:3,"STATEMENT",:4)
    where (:5='N' or(1=1 and (:6='N' or(dbms_lob.compare(:7,"STATEMENT")=0)or(:7 is null and "STATEMENT" is null)))) and(:8="APPLICATION")
    The problem comes in, we believe, with the attempt to write the value "APPLICATION" to the application column which is only a 10 character field. the value for the :1 bind variable is "N" and the value for :2 is null.
    We see the following error on the logical standby:
    ORA-00600: internal error code, arguments: [kgh_heap_sizes:ds], [0x01FCDBE60], [], [], [], [], [], []
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [kxtoedu+54] [PC:0x2542308] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ] []
    ORA-12899: value too large for column "CADPROD"."OMS_SQL_STATEMENT"."APPLICATION" (actual: 19576, maximum: 10)
    Is this a configuration issue or is it normal for SQL Apply to convert statements from logminer into decode statements?
    We have an Oracle 10.2.0.4 database running on windows 2003 R2 64-bit os. We have 3 physical and 2 logical standby's, no problems on the physical standbys.

    Hello;
    I noticed some of your parameters seem to be wrong.
    fal_client - This is Obsolete in 11.2
    You have db_name='test' on the Standby, it should be 'asadmin'
    fal_server=test is set like this on the standby, it should be 'asadmin'
    I might consider changing VALID_FOR to this :
    VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
    Document 278371.1 is showing its age in my humble opinion.
    -----Wait on this until you fix your parameters----------------------
    Try restarting the SQL Apply
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
    Use these statements to trouble shoot :
    SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
    SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
    SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
    TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
    mseberg
    Edited by: mseberg on Feb 14, 2012 7:37 AM

  • Import failed when Import a SBO Database in SAP Hana

    Hi all,
    When I try to import a SBO database Rev 69 to SAP Hana with Rev 74, I receive this error:
    SAP DBTech JDBC: [2048]: column store error: table import failed:  [30151] Object not found in the import directory;object=SBOCOMMON:ETL_Sen
    I guess that the error not have relationship with different Revs. I imported another DB with this Rev and this work.
    The import was done in 2 ways:
    Script:
    IMPORT DATABASE."*" FROM '<directory>' WITH REPLACE
    Click right in Database, Import, select directory, select tables, import...
    Does anyone know what can be or the solution??
    Thanks
    Best regards
    Marcos Taira

    Hello Marcos.
    You could check this note.
    1981315 - HANA import fails with error "not found in the import directory"
    Regards.
    Mario.

  • 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

  • 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

  • MAP 9.1 - Inventory is scanned but failed during Assessment, Duplicate Primary Key

    Hi MAP team, saw the similar thread but didn't want to hijack it if it's a different root cause.
    We have a client using MAP for data collection that is having failures with generating the assessment. In the MAPToolkitLog, we get this:
    “Microsoft.AssessmentPlatform.MapException: Caught SqlException running the stored procedure [WinClient_Assessment].[LicensingAssessmentProc]. ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'LicensingAssessment_pk'. Cannot
    insert duplicate key in object 'WinClient_Assessment.LicensingAssessment'. The duplicate key value is (4d74950a-3c31-4b7e-9464-12fd8ae03942).”
    Tracing it down it looks like there are two entries for a DeviceNumber under Win_Inventory.SoftwareLicensingProducts, with these two descriptions: “Windows Operating System - Windows(R) 7, RETAIL channel”, and “Windows Operating System - Windows(R) 7, OEM_SLP
    channel”. So two lines are trying to get created for an OEM and a RETAIL line in the LicensingAssessmentProc, causing a duplicate PRIMARY KEY and hence the issue with the assessment. Is this an existing bug and if so is there a quick way to resolve it so we
    can conduct the assessments? The issue is that we cannot run additional scans to improve coverage as it wants us to refresh the assessment before letting us run another scan.
    Thank you,
    Nick

    Following up on this, digging into the data it looks like "Windows(R) 7, OCUR add-on for Ultimate,HomePremium,Enterprise,Professional,ServerHomePremium,Embedded" is getting flagged as an OS and being included in the Win_Inventory.SoftwareLicensingProducts,
    conflicting with the actual OS line. When I deleted those rows the duplicate primary key issue was resolved and we were able to process assessments. Not sure if we can run additional scans on that database, will check soon.
    This is a pretty inconvenient way to get around this bug however, can this be addressed without having to delete SQL rows, or is this an edge case that needs to be caught in the filtering in the next release?

  • Errors ORA-39002,ORA-39070, ORA-29283, ORA-06512, ORA-29283 during import

    Hi all,
    I am getting errors during import to 10g database using impdp command.
    D:\>impdp nisa_lt/abc123@objtel1 directory=dtpump dumpfile=20120208_expobj.dmp full=y logfile=dbblog.log
    Import: Release 10.2.0.1.0 - Production on Monday, 13 February, 2012 17:16:05
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
    Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at "SYS.UTL_FILE", line 488
    ORA-29283: invalid file operation
    dmpfile history:
    Starting "NISA_LT"."SYS_EXPORT_SCHEMA_01": nisa_lt/********@OBJ schemas=nisa_lt directory=dtpump dumpfile=20120208_expobj.dmp logfile=20120208_expobj.log
    Master table "NISA_LT"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
    Dump file set for NISA_LT.SYS_EXPORT_SCHEMA_01 is:
    /oradb/OBJ/oraarch/20120208_expobj.dmp
    Job "NISA_LT"."SYS_EXPORT_SCHEMA_01" successfully completed at 15:04:36
    and the dump file was done ftp with bin mode set.
    It'll be really helpful if some one can guide me on this.

    Hi all,
    I was trying to import into a database which i have only the details, but i have no access to db machine, which i think was the problem.
    dmp file easily got imported to database present in the systems which i had access.
    Following are my conclusions based on the experiments, correct me if I'm wrong:
    1. Basically these are errors when db system cant read/write/access the directory structure pointed by directory in database.
    2. This can be achieved by mounting the directory in which dmp is present to the system where database is present.
    2. We cannot import using impdp just by having tns details of the db, we need to have access to db system.
    Thanks
    Avi :)

  • Manually Apply Archived log to stand by database

    Hi all,
    I'm using Oracle 10g. So, we need to apply the archived logs of Primary database to stand by database, but this process must be manually.
    A "robot" copy the archived logs to destination. I need to get these archived logs from destination and manually apply to stand by database.
    How can I do this?
    thank you very much!!!!

    How can I do this?First stop current recover process as
    alter database recover managed standby database cancel;Then transfer all need archive logs from primary to standby side and apply these manually using below command.
    recover standby database until cancel
    /*this command will ask full path of archive logs
    and give these then finally enter "CANCEL" word*/Finally you can continue normal/automatic state using
    alter database recover managed standby database ;

  • Logical standby stuck at initializing SQL apply only coordinator process up

    Hi
    OS: solaris 5.10
    Hardware: sun sparc
    Oracle database: 11.2.0.1.0
    Primary database name: asadmin
    Standby database name: test
    I had been trying to convert a physical standby to logical standby database. Both the primary and standby reside on the same machine.
    The physical standby was created with a hot backup of primary.
    I had been following document id 278371.1 to convert the physical to logical standby and used the following steps:
    Relevant init parameters on primary:
    *.db_name='asadmin'
    *.db_unique_name='asadmin'
    *.log_archive_config='dg_config=(asadmin,test)'
    *.log_archive_dest_1='location=/u01/asadmin/archive valid_for=(all_logfiles,all_roles) db_unique_name=asadmin'
    *.log_archive_dest_2='SERVICE=test async valid_for=(online_logfiles,primary_role) db_unique_name=test'
    *.log_archive_dest_state_1='enable'
    *.log_archive_dest_state_2='enable'
    *.fal_client='asadmin'
    *.fal_server='test'
    *.remote_login_passwordfile='EXCLUSIVE'
    Relevant init parameters on standby database:
    *.db_name='test' -- Was asadmin before I renamed the DB during conversion to logical standby
    *.db_unique_name='test'
    *.log_archive_dest_1='location=/u01/test/archive valid_for=(all_logfiles,all_roles) db_unique_name=test'
    *.log_archive_dest_2='service=asadmin async valid_for=(online_logfiles,primary_role) db_unique_name=asadmin'
    *.log_archive_dest_state_1=enable
    *.log_archive_dest_state_2=defer
    *.remote_login_passwordfile='EXCLUSIVE'*.fal_server=test
    *.fal_client=asadmin
    Steps on primary:
    1) alter system set log_archive_dest_state_2=defer;
    2) shutdown immediate;
    3) Made sure that the physical standby has applied all of the redo sent to it following the shutdown.
    4) startup mount;
    5) ALTER DATABASE BACKUP CONTROLFILE to '/home/oracle/control01.ctl';
    6) ALTER SYSTEM ENABLE RESTRICTED SESSION;
    7) ALTER DATABASE OPEN;
    8) Verified that the supplemental logging is on.
    9) ALTER SYSTEM ARCHIVE LOG CURRENT;
    10) Checked for the checkpoint change no. at this point which is 72403818 and is present in archive log file 1_62_775102253.dbf
    11) EXECUTE DBMS_LOGSTDBY.BUILD;
    12) ALTER SYSTEM ARCHIVE LOG CURRENT;
    13) Checked for the archive log containing dictionary build which is 1_64_775102253.dbf
    14) ALTER SYSTEM DISABLE RESTRICTED SESSION;
    Details of archive logs and related checkpoint change nos:
    NAME FIRST_CHANGE# NEXT_CHANGE#
    /u01/asadmin/archive/1_61_775102253.dbf 72402901 72403817
    /u01/asadmin/archive/1_62_775102253.dbf 72403817 72404069
    /u01/asadmin/archive/1_63_775102253.dbf 72404069 72404211
    /u01/asadmin/archive/1_64_775102253.dbf 72404211 72405700
    Steps on standby:
    1) shutdown immediate;
    2) Copy the archivelog file 61(was created at primary after apply stopped at standby), 62(contains checkpoint no. 72403818), 63 and 64(contains dictionary build). Copy the backup controlfile from step 5 above to the controlfile location in standby init.
    3) startup mount;
    4) Rename all datafiles and redo log files (including standby redo log files) to the correct path on standby.
    5) alter database recover automatic from '/u01/test/archive' until change 72405700 using backup controlfile; -- This completed error-free
    6) alter database guard all; -- this completed error free
    7) alter database open resetlogs; -- this completed error free.
    8) nid target=sys/oracle12 dbname=test
    9) Changed the db_name in init file to new name test.
    10) Added a tempfile to temp tablespaces.
    11) ALTER DATABASE REGISTER LOGICAL LOGFILE '/u01/test/archive/1_61_775102253.dbf'; -- ORA-16225: Missing LogMiner session name for Streams
    12) ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL 72405700; -- This completed error free.
    Also enabled the log_archive_dest_state_2 on primary.
    After this output from some views:
    SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
    SESSION_ID STATE
    1 INITIALIZING
    SQL> SELECT SID, SERIAL#, SPID, TYPE FROM V$LOGSTDBY_PROCESS;
    SID SERIAL# SPID TYPE
    587 22 15476 COORDINATOR
    SELECT PERCENT_DONE, COMMAND
    FROM V$LOGMNR_DICTIONARY_LOAD
    WHERE SESSION_ID = (SELECT SESSION_ID FROM V$LOGSTDBY_STATE);
    PERCENT_DONE
    COMMAND
    0
    SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
    TYPE HIGH_SCN STATUS
    COORDINATOR ORA-16111: log mining and apply setting up
    SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
    APPLIED_SCN NEWEST_SCN
    72405700 72411501
    SELECT THREAD#, SEQUENCE#, FILE_NAME FROM DBA_LOGSTDBY_LOG L
    WHERE NEXT_CHANGE# NOT IN
    (SELECT FIRST_CHANGE# FROM DBA_LOGSTDBY_LOG WHERE L.THREAD# = THREAD#)
    ORDER BY THREAD#,SEQUENCE#;
    no rows selected
    SQL> SELECT EVENT_TIME, STATUS, EVENT
    FROM DBA_LOGSTDBY_EVENTS
    ORDER BY EVENT_TIMESTAMP, COMMIT_SCN; 2 3
    EVENT_TIME STATUS EVENT
    14-FEB-12 02:00:50 ORA-16111: log mining and apply setting up
    14-FEB-12 02:00:50 Apply LWM 72405699, HWM 72405699, SCN 72405699
    14-FEB-12 02:20:11 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 02:20:39 ORA-16111: log mining and apply setting up
    14-FEB-12 02:20:39 Apply LWM 72405699, HWM 72405699, SCN 72405699
    14-FEB-12 02:54:15 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 02:57:38 ORA-16111: log mining and apply setting up
    EVENT_TIME STATUS EVENT
    14-FEB-12 02:57:38 Apply LWM 72405699, HWM 72405699, SCN 72405699
    14-FEB-12 03:01:36 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 03:13:44 ORA-16111: log mining and apply setting up
    14-FEB-12 03:13:44 Apply LWM 72405699, HWM 72405699, SCN 72405699
    14-FEB-12 04:32:23 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 04:34:17 ORA-16111: log mining and apply setting up
    14-FEB-12 04:34:17 Apply LWM 72405699, HWM 72405699, SCN 72405699
    EVENT_TIME STATUS EVENT
    14-FEB-12 04:36:16 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 04:36:21 ORA-16111: log mining and apply setting up
    14-FEB-12 04:36:21 Apply LWM 72405699, HWM 72405699, SCN 72405699
    14-FEB-12 05:15:22 ORA-16128: User initiated stop apply successfully
    completed
    14-FEB-12 05:15:29 ORA-16111: log mining and apply setting up
    14-FEB-12 05:15:29 Apply LWM 72405699, HWM 72405699, SCN 72405699
    I also greped for lsp and lcr processes and found that lsp is up but do not see any lcr.
    The logs are getting transported to the archive destination on standby whenever they are archived on primary but are not getting applied to standby.
    Also in case the standby is down while a log is generated on primary it is not automatically transported to standby once the standby is up, means gap resolution is also not working.
    I see the following in alert log every time I try to restart the log apply, everything seems to be stuck at initialization.
    ALTER DATABASE START LOGICAL STANDBY APPLY (test)
    with optional part
    IMMEDIATE
    Attempt to start background Logical Standby process
    Tue Feb 14 05:15:28 2012
    LSP0 started with pid=28, OS id=23391
    Completed: alter database start logical standby apply immediate
    LOGMINER: Parameters summary for session# = 1
    LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
    LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
    LOGMINER: SpillScn 0, ResetLogScn 0
    -- NOTHING AFTER THIS

    Hello;
    I noticed some of your parameters seem to be wrong.
    fal_client - This is Obsolete in 11.2
    You have db_name='test' on the Standby, it should be 'asadmin'
    fal_server=test is set like this on the standby, it should be 'asadmin'
    I might consider changing VALID_FOR to this :
    VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
    Document 278371.1 is showing its age in my humble opinion.
    -----Wait on this until you fix your parameters----------------------
    Try restarting the SQL Apply
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
    Use these statements to trouble shoot :
    SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
    SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
    SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
    TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
    mseberg
    Edited by: mseberg on Feb 14, 2012 7:37 AM

  • How to monitor SQL Apply for 10.2.0.3 logical standby database

    We have a logical standby database setup for reporting purposes. Users want to monitor whether sql apply is working or failed closely as it has reporting repercations.
    In case of 9i databases , there was "Data Not Applied (logs)" metric which we used for alerting and paging, in case a backlog of more than 5 log files developed.
    With 10.2.0.3 onwards, the metric no more exists.
    I would like to learn from other, how to monitor the setup, so that if the backlog in logs shipping or applying develops, we get page.
    Regards.

    regather the statistics on the table with method_opt=>for all columns or for all indexed columns or whatever size 1
    The 'size 1' directive will remove the histogram statistics.
    Sorry, didn't read ur post in a hurry. Below article (http://www.freelists.org/post/oracle-l/Any-quick-way-to-remove-histograms,13) removes histogram without re-analyzing the table. Hope that helps!!!
    On 3/16/07, Wolfgang Breitling <breitliw@xxxxxxxxxxxxx> wrote:
    I also did a quick check and just using
    exec
    dbms_stats.set_column_stats(user,'table_name',colname=>'column_name',d
    istcnt=>
    <num_distinct>);
    will remove the histogram without removing the low_value andhigh_value.
    At 01:40 PM 3/16/2007, Alberto Dell'Era wrote:
    On 3/16/07, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:
    Is there any faster way to remove histograms other than
    re-analyzing
    >
    the table? I want to keep the existing table, index & columnstats,
    >
    but with only 1 bucket (i.e. no histograms).You might try the attached script, that reads the stats using
    dbms_stats.get_column_stats and re-sets them, minus the histogram,
    using dbms_stats.set_column_stats.
    I haven't fully tested it - it's only 10 minutes old, even if Ihave
    slightly modified for you another script I've used for quite some
    time - and the spool on 10.2.0.3 seems to confirmthat the histogram
    is, indeed, removed, while all the other statistics are preserved.I
    have also reset density to 1/num_distinct, that is the value youget
    if no histogram is collected.regards,
    naren
    Edited by: fuzzydba on Oct 25, 2010 10:52 AM

  • Sql Apply issue in logical standby database--(10.2.0.5.0) x86 platform

    Hi Friends,
    I am getting the following exception in logical standby database at the time of Sql Apply.
    After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
    alter database start logical standby apply
    Tue May 17 06:42:00 2011
    No optional part
    Attempt to start background Logical Standby process
    LOGSTDBY Parameter: MAX_SERVERS = 20
    LOGSTDBY Parameter: MAX_SGA = 100
    LOGSTDBY Parameter: APPLY_SERVERS = 10
    LSP0 started with pid=30, OS id=4988
    Tue May 17 06:42:00 2011
    Completed: alter database start logical standby apply
    Tue May 17 06:42:00 2011
    LOGSTDBY status: ORA-16111: log mining and apply setting up
    Tue May 17 06:42:00 2011
    LOGMINER: Parameters summary for session# = 1
    LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
    LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
    Tue May 17 06:42:00 2011
    LOGMINER: krvxpsr summary for session# = 1
    LOGMINER: StartScn: 0 (0x0000.00000000)
    LOGMINER: EndScn: 0 (0x0000.00000000)
    LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
    LOGMINER: session_flag 0x1
    LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
    LOGSTDBY Apply process P014 started with pid=47 OS id=5456
    LOGSTDBY Apply process P010 started with pid=43 OS id=6484
    LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
    Tue May 17 06:42:01 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
    Tue May 17 06:42:01 2011
    LOGMINER: Turning ON Log Auto Delete
    Tue May 17 06:42:01 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
    Tue May 17 06:42:01 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
    LOGSTDBY Apply process P008 started with pid=41 OS id=4740
    LOGSTDBY Apply process P013 started with pid=46 OS id=7864
    LOGSTDBY Apply process P006 started with pid=39 OS id=5500
    LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
    Tue May 17 06:42:02 2011
    LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
    LOGMINER: op 4.1 (Control File)
    Tue May 17 06:42:02 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
    LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
    LOGSTDBY Apply process P007 started with pid=40 OS id=2760
    Tue May 17 06:42:03 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    LOGSTDBY Apply process P012 started with pid=45 OS id=7152
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
    LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
    Tue May 17 06:42:04 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
    LOGSTDBY Apply process P011 started with pid=44 OS id=6816
    LOGSTDBY Apply process P005 started with pid=38 OS id=5792
    LOGSTDBY Apply process P009 started with pid=42 OS id=752
    Tue May 17 06:42:05 2011
    krvxerpt: Errors detected in process 34, role builder.
    Tue May 17 06:42:05 2011
    krvxmrs: Leaving by exception: 600
    Tue May 17 06:42:05 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    Tue May 17 06:42:06 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
    ORA-12801: error signaled in parallel query server P001
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    Tue May 17 06:42:06 2011
    LogMiner process death detected
    Tue May 17 06:42:06 2011
    logminer process death detected, exiting logical standby
    LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
    LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
    LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
    LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
    LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
    LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
    LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
    LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
    LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
    Tue May 17 06:42:10 2011

    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
    refer these too
    *ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
    *Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY*

  • SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

    SQL Server 2012 Developer Edition will not install.  Setup files don't even get copied completely.  Win 8.1.  ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

    Hello,
    I am glad it worked.
    Thank you for visiting MSDN forums!
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Slow SQL Apply on Logical Standby Database in Oracle10g

    Hi,
    We are using Oracle 10g Logical Standby database in our production farm but whenever there is bulk data load (5-6 GB data) on the primary database, the logical standby seems to be hung. It takes days to apply the 5-6 GB data on the logical standby.
    Can anybody give me some pointers how can I make my SQL Apply fast on the logical standby for bulk data.
    Thanks
    Amit

    Hi there,
    I've a similar problem. I did an insert of 700k on a table. It takes me over 1 1/2 hours to see the data. Notice, I increased the "max_sga" to 300m and "max_servers" to 25" and didn't help the performance at all.
    My version is 10.2.0.3 with the patch 6081550.
    APPLIED_SCN APPLIED_TIME RESTART_SCN RESTART_TIME LATEST_SCN LATEST_TIME MINING_SCN MINING_TIME
    1015618 29-NOV-2007 18:28:51 1009600 29-NOV-2007 18:28:51 1017519 29-NOV-2007 19:54:07 1015656 29-NOV-2007 18:32:14

Maybe you are looking for