cancel
Showing results for 
Search instead for 
Did you mean: 

getting"cjs-30022" error in import abap while installing sap server

Former Member
0 Kudos

hi all ,

i am learning basis while installing sap server i am getting cjs-30022 "program migration monitor exists with code 103 ....am not able to complete the installation...can u please help me on this

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi balakrishna,

may be export cd's are corrupted  Stop the installation. and try to download export cd's and start again.

Regards

K.Sandeep

Former Member
0 Kudos

Hi,

May Problem with Exports sometimes ie, download error's

please try to download Export again and retry installation.

Regards,

rajshekar

Former Member
0 Kudos

Hi,

Check if the following packages are correctly copied.

SAPAPPL2

SAPSDIC

I would ask you to copy/download these packages again and see if the size is the same as given.

AC

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Guthi,

Can you share the log files where we can see the error in details.

Meanwhile, refer http://service.sap.com/sap/support/notes/1689026

Regards

Former Member
0 Kudos

hi divyanshu,

please find the log details and help me out of this

ERROR 2009-09-10 23:48:14

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2009-09-10 23:48:14

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 .

java version "1.4.2_12"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)

Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)

Import Monitor jobs: running 1, waiting 2, completed 16, failed 0, total 19.

Loading of 'SAPAPPL2' import package: ERROR

Import Monitor jobs: running 0, waiting 2, completed 16, failed 1, total 19.

Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.

Loading of 'SAPSDIC' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 16, failed 2, total 19.

INFO: 2009-09-11 00:25:07

Import Monitor is started.

CONFIG: 2009-09-11 00:25:07

Application options:

dbCodepage=4103

dbType=ORA

extFiles=yes

importDirs=D:\export1\EXP1;D:\export2\EXP2;D:\export3\EXP3;D:\export4\EXP4;D:\export5\EXP5;D:\export6\EXP6;D:\export6\EXP7;D:\export6\EXP8;D:\export6\EXP9;D:\export6\EXP10;D:\export6\EXP11

installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS

jobNum=1

loadArgs= -stop_on_error

monitorTimeout=30

orderBy=

r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2009-09-11 00:25:07

List of packages with table structure: 'SAP0000'.

CONFIG: 2009-09-11 00:25:07

List of packages with views: 'SAPVIEW'.

TRACE: 2009-09-11 00:25:07 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: 2009-09-11 00:25:07 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: 2009-09-11 00:25:07

Data codepage 4103 is determined using TOC file 'D:\export1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

TRACE: 2009-09-11 00:25:07 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL2' import package is started.

TRACE: 2009-09-11 00:25:08 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL2' import package into database:

C:\usr\sap\ECC\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error

ERROR: 2009-09-11 00:25:13 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL2' import package is interrupted with R3load error.

Process 'C:\usr\sap\ECC\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

TRACE: 2009-09-11 00:25:37 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSDIC' import package is started.

TRACE: 2009-09-11 00:25:37 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPSDIC' import package into database:

C:\usr\sap\ECC\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error

ERROR: 2009-09-11 00:25:40 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSDIC' import package is interrupted with R3load error.

Process 'C:\usr\sap\ECC\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

WARNING: 2009-09-11 00:26:07

Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2009-09-11 00:26:07

2 error(s) during processing of packages.

INFO: 2009-09-11 00:26:07

Import Monitor is stopped.

thanks

balu

divyanshu_srivastava3
Active Contributor
0 Kudos

Please upload these 3 logs and don't paste in reply.

Sapsdic.log, import_monitor.log and import_monitor.java.log

Regards,

Sriram2009
Active Contributor
Former Member
0 Kudos

hi sreeram and divyanshu......this is the error am getting in log

ERROR 2014-11-09 16:33:02

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2014-11-09 16:33:03

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 .

Former Member
0 Kudos

Hello,

Kindly post SAPSSEXClog as well.

regsrds,

pavan

Reagan
Advisor
Advisor
0 Kudos

You should in fact check or supply the logs of the failed packages.

First try to merge the TSK files of the failed packages and import them.