CJS-30022 Program 'Migration Monitor'

Hi Experts
I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
ERROR 2007-08-11 18:03:25
CJS-30022 Program 'Migration Monitor'
exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log.
C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
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 .
WARNING 2007-08-11 18:03:25
Execution of the command "C:\java\bin\java.exe -classpath migmon.
jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
"C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
"C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\SYS\exe\uc\NTI386\R3load.exe -tskFiles
yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
Any suggesstions/ideas for this error
Regards
Rahul

I just encountered this same error, except it was during an export of an ECC 6.0 Source system. I searched SDN for an answer and then worked my counterpart in Japan. My problem turned out to be the version of the R3Load.exe I was using. It was the latest available on Marketplace. I reverted back to the one that was delivered with kernel patch 102 and my export completed with no errors. I made sure to do the same on the Target system so I did not get the errors during the import.
Hope this helps...

Similar Messages

Solut Manager v4.0 install. error : CJS-30022 Program 'Migration Monitor

Hi Experts
I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
ERROR 2007-08-11 18:03:25
CJS-30022 Program 'Migration Monitor'
exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log.
C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
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 .
WARNING 2007-08-11 18:03:25
Execution of the command "C:\java\bin\java.exe -classpath migmon.
jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
"C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
"C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\SYS\exe\uc\NTI386\R3load.exe -tskFiles
yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
Any suggesstions/ideas for this error
Regards
Rahul

Check the logfile SAPAPPL0.log for errors...
Markus

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
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 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Migration Monitor error during Het. Sys Copy

We are doing an Het. Sys Copy from Aix-Orcle to Win IA64-Oracle using the standard indipendent procedure (export-import), on an Abap only instance.
During the import we got errors for the wrong migration key, despite it seemed well generated and we applied at the end the note 970518 point "D019527, 09/MAY/06".
Anyway after a bit the import process stopped due this error and we do not how what's went wrong:
" Execution of the command "C:\j2sdk1.4.2_04\bin\java.exe -classpath
migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType
ORA -importDirs E:\Iveco_export\TS1\ABAP -installDir "C:\Program
Files\sapinst_instdir\NW04S\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP" -
orderBy "" -r3loadExe E:\usr\sap\TS1\SYS\exe\uc\NTIA64\R3load.exe -
tskFiles yes -extFiles yes -migrationKey 1G5fdEM50T1IrBzjt6TE5Pae -
dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -
stop_on_error" -trace all -sapinst" finished with return code 128.
Output: java version "1.4.2_04"Java(TM) 2 Runtime Environment, Standard
Edition (build 1.4.2_04-b05)Java HotSpot(TM) 64-Bit Server VM (build
1.4.2_04-b05, mixed mode)
ERROR 2007-06-21 08:33:44
CJS-30022 Program 'Migration Monitor' exits with error code 128. For
details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-06-21 08:33:44
FCO-00011 The step runMigrationMonitor with step key
|NW_ABAP_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 .
bye

If you post logfiles, please put "code tags" around, this makes your logs readable.
If you read what you posted you will find:
> ERROR Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19. ERROR 2009-03-31 18:14:16 CJSlibModule::writeError_impl() CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
Do that.
Markus

Migration monitor error

Hi all,
I am installing IDES ECC, in abap import step i got this error, does any one knows
how to solve this error
ERROR 2007-10-04 00:54:00
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-10-04 00:54:00
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 .
WARNING 2007-10-04 00:54:00
Execution of the command "C:\j2sdk1.4.2_14\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP1;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP2;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP3;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP4;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP5;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\51032272_1\EXP6;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\IDESEXPCDS\01\51032413_6\EXP7;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\IDESEXPCDS\01\51032413_6\EXP8;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\IDESEXPCDS\01\51032413_6\EXP9;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\IDESEXPCDS\01\51032413_6\EXP10;C:\Documents and Settings\Administrator\downloads_sap\ERP 2006 my SAP\IDESEXPCDS\01\51032413_6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe J:\usr\sap\ECI\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output: java 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 3, completed 21, failed 0, total 25.Import Monitor jobs: running 2, waiting 2, completed 21, failed 0, total 25.Import Monitor jobs: running 3, waiting 1, completed 21, failed 0, total 25.Loading of 'SAPCLUST' import package: ERRORImport Monitor jobs: running 2, waiting 1, completed 21, failed 1, total 25.Loading of 'SAPSSEXC_4' import package: ERRORImport Monitor jobs: running 1, waiting 1, completed 21, failed 2, total 25.Loading of 'SAPPOOL' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 21, failed 3, total 25.
Thank you

hi lakshmi,
on 4th oct you faced a problem related to IMPORT ABAP,
same problem i m facing when i m installing ECC6.0 , would u pl. tell me , how your problem has been sorted out
thanks in advanced
sanjay garg

CJS-30022 ECC6.0 SR3 installation error on SLES 10 SP2 DB2 9.5 64 bit

same post on linux forum:
error in ECC.ERP
Hello
I'm stuck with installation on newly build machine Intel Xeon and 5 GB RAM.
System SLES 10 SP2 and all patches applied. IBM Java 142 v 10 (latest from OSS note for x86_64) but tried also with SLES provided sun java (same error).
All steps from 958253 has been applied, 1125951 suggest installeion of "pdksh" shell but that is not available in SLES - ksh is installed, saplocales version 3 also.
sapinst.log
INFO 2008-06-25 10:14:13.955
Creating file /db2/IED/sapdata3/sapinstdir1/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/import_monitor.java.log.
INFO 2008-06-25 10:14:13.985
Output of /opt/IBMJava2-amd64-142/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2008-06-25 10:14:14.177
Execution of the command "/opt/IBMJava2-amd64-142/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 1. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20080130 (JIT enabled)
J9VM - 20071205_1933_LHdSMr
JIT - r7_level20071016_1845)
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor
WARNING[E] 2008-06-25 10:14:14.181
CJS-30022 Program 'Migration Monitor' exits with error code 1. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-06-25 10:14:14.279
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_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.java.log
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20080130 (JIT enabled)
J9VM - 20071205_1933_LHdSMr
JIT - r7_level20071016_1845)
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor
there is no import_monitor.log available.
I'm using ECC 6.0 SR3 fresh downloaded instalallation disks and DB6 9.5 from SAP service.sap.com.

Finally i've resolved this problem. You can't use /db2/SID/sapdata(n) directory as a your sapinst installation directory becouse sapinst is setting strange access rights to whole /db2/SID tree and sidadm user can't do any activity below.
It's my first SAP DB6 based instalallation (i've done dozen of times on Oracle and there it was possible) and this is new for me.
Note 967123 is describing this problem "ABAP: Error in step extractMigrationMonitorArchive
The installation aborts in step extractMigrationMonitorArchive.
Solution:
Download a patch of MIGMON.SAR from the SAP service marketplace
(for more information see SAP note 784118) and extract the archive as
user <sapsid>adm into the current installation directory
(using SAPCAR with the option '-xvf')
Then restart SAPinst or re-execute the step."
And it looks that user sidadm is unpacking MIGMON.SAR.
Thanks for hints.

Cjs-30022 and fco-00011 error in crm ,ep.xi installation can any one helpme

hi friends can any one help me
while installing crm i got this error on abap import
import moinitor job: running 0,waiting 1,completed 15 , failed 3 ,total 19 i can see in satus bar and it is throughing an error like
SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport    : 21212
guistart   : true
command    : "C:\j2sdk1.4.2_12/bin\javaw.exe" -cp "C:/WINDOWS/TEMP/sapinst_exe.3468.1197716131\jar\instgui.jar;C:/WINDOWS/TEMP/sapinst_exe.3468.1197716131\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
load resource pool G:\New Folder\instmaster\IM_WINDOWS_I386\resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host willsys, port 21200 to continue with the installation
guiengine: login in process.
IRunModeReceiver CChoiceDialogModifier::continuePreviousRun()
INFO       2007-12-15 02:56:07 [synxcfile.cpp:493]
           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.8.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.8.xml'.
INFO       2007-12-15 02:56:07 [synxcfile.cpp:493]
           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.9.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/inifile.9.xml'.
INFO       2007-12-15 02:56:15
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO       2007-12-15 02:56:31 [synxcfile.cpp:493]
           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/keydb.5.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/CRM05/SYSTEM/ORA/CENTRAL/AS/keydb.5.xml'.
INFO       2007-12-15 02:56:32
Execute step runMigrationMonitor of component |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.
INFO       2007-12-15 02:56:32 [synxcpath.cpp:776]
           CSyPath::createFile()
Creating file C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.
INFO       2007-12-15 02:56:32 [syxxccuren.cpp:105]
           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(iastring)
Working directory changed to C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS.
INFO       2007-12-15 02:56:32
           CJSlibModule::writeInfo_impl()
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "G:\New Folder\exp\export1\EXP1;G:\New Folder\exp\export2\EXP2;G:\New Folder\exp\export2\EXP3;G:\New Folder\exp\export2\EXP4" -installDir "C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING    2007-12-15 02:57:02
           CJSlibModule::writeWarning_impl()
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "G:\New Folder\exp\export1\EXP1;G:\New Folder\exp\export2\EXP2;G:\New Folder\exp\export2\EXP3;G:\New Folder\exp\export2\EXP4" -installDir "C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
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 3, completed 15, failed 0, total 19.
Import Monitor jobs: running 2, waiting 2, completed 15, failed 0, total 19.
Import Monitor jobs: running 3, waiting 1, completed 15, failed 0, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 15, failed 1, total 19.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 15, failed 2, total 19.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 15, failed 3, total 19.
ERROR      2007-12-15 02:57:02
           CJSlibModule::writeError_impl()
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-12-15 02:57:02
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 .
INFO       2007-12-15 02:57:06 [iaxxgenimp.cpp:774]
           showDialog()
An error occured and the user decided to retry the current step: "|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".
INFO       2007-12-15 02:57:06 [synxcpath.cpp:776]
           CSyPath::createFile()
Creating file C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.
INFO       2007-12-15 02:57:06 [syxxccuren.cpp:105]
           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(iastring)
Working directory changed to C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS.
INFO       2007-12-15 02:57:06
           CJSlibModule::writeInfo_impl()
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "G:\New Folder\exp\export1\EXP1;G:\New Folder\exp\export2\EXP2;G:\New Folder\exp\export2\EXP3;G:\New Folder\exp\export2\EXP4" -installDir "C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING    2007-12-15 02:57:37
           CJSlibModule::writeWarning_impl()
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "G:\New Folder\exp\export1\EXP1;G:\New Folder\exp\export2\EXP2;G:\New Folder\exp\export2\EXP3;G:\New Folder\exp\export2\EXP4" -installDir "C:\Program Files\sapinst_instdir\CRM05\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
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 3, completed 15, failed 0, total 19.
Import Monitor jobs: running 2, waiting 2, completed 15, failed 0, total 19.
Import Monitor jobs: running 3, waiting 1, completed 15, failed 0, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 15, failed 1, total 19.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 15, failed 3, total 19.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 15, failed 3, total 19.
ERROR      2007-12-15 02:57:37
           CJSlibModule::writeError_impl()
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-12-15 02:57:37 [iaxxgenimp.cpp:731]
           showDialog()
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 .
plz help me i am trying disperatly
thnk
ravi

Hi Ravulapalli,
>G:\New Folder\exp\export1\EXP1
please check import_monitor.java.log, import_monitor.log
Please rename "New Folder" to New_Folder. Restart the central instance installation.
Regards,
Jeff

I need your help(sap installation error : CJS-30022)

Hello My friends,
I meet so difficult problems.
- SAP NetWeaver Application Server ABAP 7.02 SP6 32-bit Developer Edition
- SAP NetWeaver Application Server ABAP 7.02 SP6 64-bit Developer Edition
In setting up above two version, it was interrupted on the menu during the installation.
I want to solve this problem.
To request help to solve this problem.
I searched "google" and " sdn.sap.com" but I didn't solve.
I installed the hardware OS xp 32bit cpu 2.4 ram 1 gb hdd 160 gb With OS windows7 64bit cpu 2.0 ram 3 gb hdd 80 gb ---
I installed as follows order
1.os xp pro, windows7 installation.
2.installing iis
3.As hdwwiz.exe MS Loopback Adapter network / ip: 10.10.0.10, 255.255.255.0
4.c: \ windows \ system32 \ drive \ etc \ host add to the 10.10.0.10 netweaver
5.The latest version of jre, java.com download at the click of a button installed in    path: JAVA_HOME setting
6.Computer swap size: 4096 - 4096
7. Turn off the firewall settings
The default setting is
run
D:\Setup\SAPNW7.01ABAPTrial.part1\SAPNWABAP701SR1_TRIAL\SAP_NetWeaver701SR1_2008_Installation_Master\IM_WINDOWS_I386
\sapinst.exe
should install, run
During the installation, it is interrupted from "Import abap menu".
I need your help.
--------- error log ---------
WARNING    2012-07-13 17:13:12.859
           CJSlibModule::writeWarning_impl()
Execution of the command ""C:\Program Files\Java\j2re1.4.2_19\bin\java.exe" -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 2. Output:
java version "1.4.2_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_19-b04)
Java HotSpot(TM) Client VM (build 1.4.2_19-b04, mixed mode)
Required system resources are missing or not available:
Import directory 'C:\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP2' does not have valid structure of subdirectories;
Import directory 'C:\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP3' does not have valid structure of subdirectories.
ERROR      2012-07-13 17:13:12.859
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2012-07-13 17:13:12.875 [sixxcstepexecute.cpp:988]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO       2012-07-13 17:13:13.562 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\__instana_tmp.xml.
WARNING    2012-07-13 17:13:15.0 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2012-07-13 17:13:15.0 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .

Hello,
Which system are you getting the error, XP / Win 7 ?
Please find the minimum H/W requirement (Source Inst Guide)
Minimum RAM :- 4GB
Paging file size :- 1 times RAM plus 8 GB
If you are trying for win 7, then I would recommend you to
increase the swap space and give it a try.
It looks like it is not getting the required system
resources (RAM).
Thanks,
Vishal

CJS-30022 ECC6.0 installation error on SLES 10 SP2 DB2 9.5 64 bit

Hello
I'm stuck with installation on newly build machine Intel Xeon and 5 GB RAM.
System SLES 10 SP2 and all patches applied. IBM Java 142 v 10 (latest from OSS note for x86_64) but tried also with SLES provided sun java (same error).
All steps from 958253 has been applied, 1125951 suggest installeion of "pdksh" shell but that is not available in SLES - ksh is installed, saplocales version 3 also.
sapinst.log
INFO 2008-06-25 10:14:13.955
Creating file /db2/IED/sapdata3/sapinstdir1/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/import_monitor.java.log.
INFO 2008-06-25 10:14:13.985
Output of /opt/IBMJava2-amd64-142/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2008-06-25 10:14:14.177
Execution of the command "/opt/IBMJava2-amd64-142/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 1. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20080130 (JIT enabled)
J9VM - 20071205_1933_LHdSMr
JIT - r7_level20071016_1845)
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor
WARNING[E] 2008-06-25 10:14:14.181
CJS-30022 Program 'Migration Monitor' exits with error code 1. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-06-25 10:14:14.279
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|
NW_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.java.log
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20080130 (JIT enabled)
J9VM - 20071205_1933_LHdSMr
JIT - r7_level20071016_1845)
there is no import_monitor.log available.
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor

Finally i've resolved this problem. You can't use /db2/SID/sapdata(n) directory as a your sapinst installation directory becouse sapinst is setting strange access rights to whole /db2/SID tree and sidadm user can't do any activity below.
It's my first SAP DB6 based instalallation (i've done dozen of times on Oracle and there it was possible) and this is new for me.
Note 967123 is describing this problem "ABAP: Error in step extractMigrationMonitorArchive
The installation aborts in step extractMigrationMonitorArchive.
Solution:
Download a patch of MIGMON.SAR from the SAP service marketplace
(for more information see SAP note 784118) and extract the archive as
user <sapsid>adm into the current installation directory
(using SAPCAR with the option '-xvf')
Then restart SAPinst or re-execute the step."
And it looks that user sidadm is unpacking MIGMON.SAR.
Thanks for hints.

ECC v6.0 installation error : CJS-30022 and FCO-00011

Hi All,
I enconter the while installing ECC 6.0 in windows 2003 server and MSSQL 2005 as the database. The error occurs during import ABAP phase ( exactly the Job name was SAPSDIC and this is the first job out of 19)
The same issue has been discussed in this forum but for oracle( Please find the link below for it)Kindly let me know how to fix it and since the database i am using it is SQL 2005 i am really confused on what should i change exactly.
Re: Solution Manager v4.0 installation error : CJS-30022 and FCO-00011
regards,
Anandha Krishnan.R

Sunil,
The log file is pasted.
===== Log file of import.monitor.log =============
TRACE: 2007-04-18 18:45:15 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -ctf I "E:\SAP ERP 2005 IDES\51032413_4_IDES SAP ERP 2005 SR2 Inst. Export\EXP4\DATA\SAPSDIC.STR" "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-04-18 18:45:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast
ERROR: 2007-04-18 19:00:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast' 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: 2007-04-18 19:01:00
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2007-04-18 19:01:00
1 error(s) during processing of packages.
INFO: 2007-04-18 19:01:00
Import Monitor is stopped.
===== Log file of import.monitor.java.log =============
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
===== Log file of SAPSDIC.TSK =============
T F4TMP C ok
P F4TMP~0 C ok
D F4TMP I ok
T F4UHLP C ok
P F4UHLP~0 C ok
D F4UHLP I err
Note : Other than the last task all the other tasks were found to be ok
===== Log file of SAPSDIC.log =============
(DB) INFO: ENHA_TMDIR~CMP created
(DB) INFO: ENHA_TMDIR~ENH created
(DB) INFO: ENHA_TMDIR~MTD created
(DB) INFO: F4TMP created
(DB) INFO: F4TMP~0 created
(IMP) INFO: import of F4TMP completed (1404 rows) #20070418185312
(DB) INFO: F4UHLP created
(DB) INFO: F4UHLP~0 created
(CNV) WARNING: code page conversion problem
Number of substitutions: 5
(row 3322 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 22 04 3e 04 47 04 3a 04 38 04 20 00 20 00 20 00 |".>.G.:.8. . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 9
(row 3323 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 23 04 41 04 3a 04 3e 04 40 04 35 04 3d 04 38 04 |#.A.:.>[email protected].=.8.|
VALUE 35 04 20 00 20 00 20 00 20 00 20 00 20 00 20 00 |5. . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 4
(row 3324 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 26 04 38 04 3a 04 3b 04 20 00 20 00 20 00 20 00 |&.8.:.;. . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 7
(row 3325 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 27 04 30 04 41 04 42 04 3e 04 42 04 30 04 20 00 |'.0.A.B.>.B.0. .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 13
(row 3326 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 15 04 3c 04 |-.;.5.:.B.@...<.|
VALUE 3a 04 3e 04 41 04 42 04 4c 04 20 00 20 00 20 00 |:.>.A.B.L. . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 19
(row 3327 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 21 04 3e 04 |-.;.5.:.B.@.!.>.|
VALUE 3f 04 40 04 3e 04 42 04 38 04 32 04 3b 04 35 04 |?.@.>.B.8.2.;.5.|
VALUE 3d 04 38 04 35 04 20 00 20 00 20 00 20 00 20 00 |=.8.5. . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 18
(row 3328 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 38 04 47 04 |-.;.5.:[email protected].|
VALUE 1d 04 30 04 3f 04 40 04 4f 04 36 04 35 04 3d 04 |[email protected].=.|
VALUE 38 04 35 04 20 00 20 00 20 00 20 00 20 00 20 00 |8.5. . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 16
(row 3329 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 38 04 47 04 |-.;.5.:[email protected].|
VALUE 35 04 41 04 3a 04 38 04 39 04 20 00 42 04 3e 04 |5.A.:.8.9. .B.>.|
VALUE 3a 04 20 00 20 00 20 00 20 00 20 00 20 00 20 00 |:. . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 7
(row 3330 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3d 04 35 04 40 04 33 04 38 04 4f 04 20 00 |[email protected]. .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed>
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: F4UHLP~1 created
(DB) INFO: GCTAB created
(DB) INFO: GCTAB~0 created
(IMP) INFO: import of GCTAB completed (0 rows) #20070418185312
(DB) INFO: GUI_FKEY created
(DB) INFO: GUI_FKEY~0 created
(IMP) INFO: import of GUI_FKEY completed (335 rows) #20070418185312
(DB) INFO: VRSX4~1 created
(DB) INFO: disconnected from DB
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe: END OF LOG: 20070418190034
regards,
Anandha Krishnan.R

Help need on Migration Monitor during the OS migration

Dear Guru,
I need some helps to start the export with migration monitor tools.
First I want to start the export on the source system and then move the file by myself to the source system.
I can start the export in client mode? (I try already but it is just hang there)
Then, I try to start the export with server mode, but I got the error below:
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: Export without hintfile
Alternate NameTab for type "BAPIPAREX_HELP" was missing and has been simulated.
(GSI) INFO: dbname = "BWT20030708040756 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "HSEA-PDC-S015 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "HSEA-PDC-S015"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 6)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
my export properties are as below:
Export Monitor options
Server operating mode
server
Client operating mode
#client
Exchange mode: ftp | net
#ftp
net
Common options
List of export directories, separator on Windows ; on UNIX :
exportDirs=V:\sap_inst_temp\export
Installation directory
installDir=C:\Program Files\sapinst_instdir\NW04\COPY\EXPORT\ABAP\COPY\NUC\DBEXP
Package order: name | file with package names
orderBy=name
DDL control file, default is DDL<DB_TYPE>.TPL
ddlFile=
File with mapping between DDL files and package names
ddlMap=
Monitor timeout in seconds
monitorTimeout=30
R3load options
Optional path of R3load executable
r3loadExe=
Generation of task files: yes | no
tskFiles=yes
Code page for data files
dataCodepage=
Additional R3load arguments for TASK phase
taskArgs=yes
Additional R3load arguments for LOAD phase
loadArgs=
Number of parallel export jobs
jobNum=3
Network options
Network exchange directory
netExchangeDir=V:\sap_inst_temp\export\netExchange
FTP options
Remote FTP host
ftpHost=
Name of remote FTP user
ftpUser=
Password of remote FTP user
ftpPassword=
List of remote FTP directories for export dump, separator : or ;
ftpExportDirs=
Remote FTP exchange directory
ftpExchangeDir=
Number of parallel FTP jobs
ftpJobNum=3
Socket options
#socket
Server hostname
host=
Server port number
port=
Trace option
Trace level
trace=all
E-mail options
SMTP server
mailServer=
"From" email address
mailFrom=
"To" email address
mailTo=
If anyone can share the document base on the migration monitor, It will be helpful.
Thank you and Best Regards,
Rapheephan

> Then, I try to start the export with server mode, but I got the error below:
>
> (DB) INFO: connected to DB
> (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
> (DB) INFO: Export without hintfile
> Alternate NameTab for type "BAPIPAREX_HELP" was missing and has been simulated.
> (GSI) INFO: dbname = "BWT20030708040756 "
> (GSI) INFO: vname = "ORACLE "
> (GSI) INFO: hostname = "HSEA-PDC-S015 "
> (GSI) INFO: sysname = "Windows NT"
> (GSI) INFO: nodename = "HSEA-PDC-S015"
> (GSI) INFO: release = "5.2"
> (GSI) INFO: version = "3790 Service Pack 2"
> (GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 6)"
> (BEK) ERROR: SAPSYSTEMNAME not in environment
Did you execute it as <sid>adm user?
Markus

Migration monitor (migmon.jar) not found when installing Solman 4.0

Hi again all,
I am doing the installation of the database instance for Solution Manager 4.0 and at the Import ABAP step, it ends with the following error:
WARNING 2007-09-20 17:22:32
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath migmon.jar
-showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /u02
/sap/EXP1:/u02/sap/EXP2:/u02/sap/EXP3:/u02/sap/EXP4 -installDir /tmp/sapinst_ins
tdir/SOLMAN/SYSTEM/ORA/DISTRIBUTED/AS/DB -orderBy "" -r3loadExe /usr/sap/SMD/SYS
/exe/run/R3load -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorT
imeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return
code 1. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-200703
28 (JIT enabled)
J9VM - 20070327_1654_LHdSMr
JIT - r7_level20061020_1803ifx1)
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor
The migmon.jar file is not present anywhere on the server. It appears that this is needed for doing system copies but why is it looking for it here since this is just a fresh installation and not a system copy? And more importantly, how do I resolve this?
Steve

Read the first sentence of my first reply to your question
The tool to import data is called "Migration Monitor" because it was initially developed assisting on migrations of systems. Since the process itself is the same (R3load export/import), it was integrated in the installer. Don't let the name confuse you.
Markus

Migration Monitor question

Suppose there are 50 dedicated packages for top 50 table and 25 SAPXXXX package in total. I want to:
Load them order by size (seems this is the default setting in migtion monitor)
For those 50 tables, I need specify both DDL file and loadArgs
8 parallel processor used.
My questions:
1) ddlFile & ddlMap parameters can be used to specify the non standard DDL control file. I must set both those 50 & 25 packages into 2 group sections in ddlmap file? Or I can simply set 25 of them into ddlMap.txt and let sapinst use default value (set in import property file) for other 50 packages?
2) ddlMap file can be used to specify the additional loadArgs, such as "-loadprocedure fast LOAD" etc...?
3) If loadArgs must be used in orderby.txt (this is suggested in migration monitor guide), sapinst will not use order by size option, instead, it uses the line order, right?
4) Same as question 1, I must set both those 50 & 25 package into 2 group sections in orderby.txt?
5) If I need set those 50 & 25 packages. I want to know how to defined "package". Every file with STR extension in <exportdir>/DATA stands for a package, am i right? How about SAPVIEW.STR, it can be loaded before all packages are loaded completely?
The migration monitor guidd is really hard to fully understand. I can not find answer for about questions.
Thanks for you comment,
James

Neel,
Yes, you are right.
My test shows:
ddlMap control file just read group and ddlFile parameter information.
orderby control file does NOT recogonize ddlFile parameter, but loadArgs , no. of jobs are OK.
So you recommend to use same orderby.lst as both ddlMap & orderby control file, and put all parameters into the same orderby.lst. That is a good idea.
My test also shows:
We do NOT have to list all packages in orderby.lst. Packaged are not listed in orderby.lst will be assinged to a "default group" and use the default ddlFile, loadArgs parameters in property file. SAPNTAB will be checked at the first to identify the codepage. SAPVIEW will be loaded after all other packages are loaded successfully.
*Below is suitable for Ver640:
If we use group concept in orderby.lst, than each group (include "default group") get its own no. of jobs and orderby property. I do NOT find a way to specify individual loadArgs to each group but use a system wide orderby (order by size of all packages is a good suggestion during import) and no. of jobs parameter. In traditionaly sapinst mode, if we do not select "Use Migration Monitor" and select "Individual Configuration for Data Load" option, then we can specify ddlFile & loadArgs, and use a system wide orderby and no. of jobs parameter. So if there is loading conflict (example, you do not want to load 2 big packages at the same time), use Migration Monitor. If there is no loading conflict and more than 1 loadArgs, use "Individual Configuration for Data Load" option.
As for 700, I do not test this point. It works as ver640, I think.
James

Migration Monitor - How Are You Using It?

Hello!
In this short discussion, you can help us to better understand how you are using the Migration Monitor – this better understanding would help the team responsible for this tool to adapt their automated tests accordingly and would also influence the future development decisions in this area.
What is the Migration Monitor?
The Migration Monitor is part of the software provisioning manager as of SAP NetWeaver 2004 SR1, but can also be executed manually. It uses the EXT, WHR, STR, TPL files to control the unload and load, to accelerate the load by automatic parallelization, and to generate the R3load task and command files (TSK and CMD files).The Migration Monitor does the following:
Creates R3load command files
Creates R3load task files if required
Starts R3load processes to unload the data
Transfers packages from source to target host if required
Starts R3load processes to load data as soon as a package is available
Informs the person performing the system copy in case of errors
How Do You Use the Migration Monitor?
Only for sequential unload and load - that is, you first unload to a local system, transfer the export directory to the target host, and then load using this directory.
For parallel unload and load:
a) Unload and load using a shared network directory
b) Unload and load using transfer by FTP
c) Unload and load using sockets
In your reply, please just name your preferred option (1, 2a, 2b, or 2c) – and why you prefer it.
Thanks a lot for your support!
Boris

Boris,
Options - All three but mainly Option # 2.
Option # 1 - To dynamically increase the number of parallel process from Source system. But in case of homogeneous system copies with massive database sizes, the database proprietary methods comes in handy than the R3load procedures.
Option # 2 - To reduce downtime in migrations (hetero combinations) thru parallel export/import of data loads.
Hope it helps.
Regards,
Srinivas K.

CJS-30022 Program 'Migration Monitor'

Similar Messages

Maybe you are looking for