SAP Help Site


Re: [sap-basis] Sap Ides Import Abap error

Posted by draghu_prasad prasad
on 08/10/2008 04:34:00 PM


hi all
this error occurs only with the deficiancy of RAM. At least 5 gb of ram
should the in the server so that this error will come again.
there is one more solution for this. but before this solution try this and
let me know if it now working will proveide the other alternate.
regards
raghava

On 8/9/08, niroukas via sap-basis <sap-basis@groups.ittoolbox.com> wrote:
>
>
>
>
>
> Hi all,
> I am new to Sap and i am trying to install Ides. I have downloaded the
> files from service.sap.com three times and i get alway an error in the
> phase of Abap importing.
>
> ERROR 2008-08-09 14:02:35
> 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-08-09 14:02:35
> 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|10|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 .
>
> import_monitor.log
> INFO: 2008-08-09 14:02:05
> Import Monitor is started.
>
> CONFIG: 2008-08-09 14:02:05
> Application options:
> dbCodepage=4103
> dbType=ORA
> extFiles=yes
> importDirs=F:\IDES\SAP IDES EXPORT DVD1\EXP1;F:\IDES\SAP IDES EXPORT
> DVD2\EXP2;F:\IDES\SAP IDES EXPORT DVD3\EXP3;F:\IDES\SAP IDES EXPORT
> DVD4\EXP4;F:\IDES\SAP IDES EXPORT DVD5\EXP5;F:\IDES\SAP IDES EXPORT
> DVD6\EXP6;F:\IDES\SAP IDES EXPORT DVD6\EXP7;F:\IDES\SAP IDES EXPORT
> DVD6\EXP8;F:\IDES\SAP IDES EXPORT DVD6\EXP9;F:\IDES\SAP IDES EXPORT
> DVD6\EXP10;F:\IDES\SAP IDES EXPORT DVD6\EXP11
> installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
> jobNum=3
> loadArgs= -stop_on_error
> monitorTimeout=30
> orderByr3loadExe=F:\usr\sap\NIR\SYS\exe\uc\NTI386\R3load.exe
> sapinsttrace=all
> tskFiles=yes
>
> CONFIG: 2008-08-09 14:02:05
> List of packages with table structure: ‘SAP0000’.
>
> CONFIG: 2008-08-09 14:02:05
> List of packages with views: ‘SAPVIEW’.
>
> TRACE: 2008-08-09 14:02:05 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: 2008-08-09 14:02:05 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: 2008-08-09 14:02:05
> Data codepage 4103 is determined using TOC file ‘F:\IDES\SAP IDES EXPORT
> DVD1\EXP1\DATA\SAPAPPL0.TOC’ for package ‘SAPAPPL0’.
>
> TRACE: 2008-08-09 14:02:05 com.sap.inst.migmon.LoadTask run
> Loading of ‘SAPAPPL2’ import package is started.
>
> TRACE: 2008-08-09 14:02:05 com.sap.inst.migmon.LoadTask processPackage
> Loading of ‘SAPAPPL2’ import package into database:
> F:\usr\sap\NIR\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage
> 4103 -l SAPAPPL2.log -stop_on_error
>
> ERROR: 2008-08-09 14:02:10 com.sap.inst.migmon.LoadTask run
> Loading of ‘SAPAPPL2’ import package is interrupted with R3load error.
> Process ‘F:\usr\sap\NIR\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd
> -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error’ exited with return code 2.
> For mode details see ‘SAPAPPL2.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
>
> WARNING: 2008-08-09 14:02:35
> Cannot start import of packages with views because not all import packages
> with tables are loaded successfully.
>
> WARNING: 2008-08-09 14:02:35
> 1 error(s) during processing of packages.
>
> INFO: 2008-08-09 14:02:35
> Import Monitor is stopped.
__.____._

Copyright © 2008 ITtoolbox and message author.
No redistribution.

Related Content

White Papers


In the Spotlight

Effectively integrate reporting into your OEM applications. Learn how

_.____.__


Leave a Comment so far
Leave a comment



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s



%d bloggers like this: