Migration monitor - Reload DB problem

Hello everyone,
I just migrated an SAP system from linux platform to windows problem, everything went well, and now, I would like to overwrite the current database with a new EXPORT files.
I exported the source system again, file structures and its contents were created well, and then I would like to import the EXPORTS into the system again, without using sapinst tools but using sap migration monitor, with command : import_monitor.bat
during the import, I met difficulties, please refer to the pictures I attached.
Do I need to remove all database objects before I reload the db again.
Please share your experience. Thanks a lot
Fresh

Hello
You're true Distmon won't recreate the Oracle instance, database, datafiles & so on.
Distmon is only loading data in an existing DB.
You could reset all the already created/loaded objects using the drop user cascade command.
drop user sapsr3 cascade;
This will delete all the objects related to the SAP schema but will leave the DB, tablespace and datafiles
Regards
http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_9008.htm

Similar Messages

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.

Dual Monitor Causing System Problems?

Hi, I'm new to this site, so I hope this is where I ask this question! My design group switched to G5/Cinema Display screen from old g4 setups mid 2005. I retained my Mitsubishi Diamond Pro 2020u monitor to use as a secondary display for pallettes, extra files, etc. It's hooked up using a dvi-vga adapter.
My new G5 had hiccups from the start, but around March 2006 I started getting Kernel Panics almost every week, serious slow-downs, Adobe app crashes, etc. It got to the point that I was troubleshooting every week, but could never put a finger on exactly what was happening. IT archive-installed 10.4.4 after we discovered the system had been updated to 10.4.6 and we thought that would solve the problem. While that solved the issues that were relevant to 10.4.6 glitches, it didn't fix everything and little, persistent problems remained, including stalls, crashes and kernel panics. After removing suspect fonts, wallpaper, icons, updating software, repairing permissions, tossing preferences, and other troubleshooting over and over, we (I.T.) finally switched my cpu to another one in the department using data migration (just my user information, not software or other files). Still the same hiccups and even new glitches appeared (InDesign crashing on spellcheck, Photoshop not granting me access to save changes to files, etc.), including two more Kernel panics (within 5 minutes of each other) in the two weeks since we switched hardware. More troubleshooting fixed the app-specific problems, but there are still the persistent annoyances occurring.
I again did all the troubleshooting mentioned above and finally someone mentioned that I'm the only designer in our group using a dual display set-up. Could there be validity to the non-cinema display monitor causing these problems and if so, what is the solution? I've disconnected the second monitor for now, but would love to have it back. Also, we work with a server (for instance, the kernel panics only happen when I try to place a file from the server into InDesign CS2 using the place command, so there's another avenue to go down if the monitor isn't the issue.)Thanks!
G5 Mac OS X (10.4.4) graphic design applications
G5 Mac OS X (10.4.4) graphic design applications
G5 Mac OS X (10.4.4) graphic design applications

I only just disconnected the monitor, so it will take time to tell if that's a factor. As for the kernel panics, although it's always the same scenario (placing images from server through InDesign) they happen very randomly; it's not happening every single time I place a file. In fact, I just placed an image on the server into an ID doc I have on my desktop, no problem. So I can't say for sure that it has happened when working from my desktop or only when working on the server.
G5 Mac OS X (10.4.4) graphic design applications

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

Integration of migration monitor to R3SETUP

Hello,
I'm preparing heterogenenous migration of R/3 4.6C system, manually integrating migration monitor 7.0 to R3SETUP and I'm afraid, that pdf documentation attached to MIGMON.SAR package is somehow incomplete.
It's very specific in integrating migmon to import process, saying:
4. Modify the file control.xml / *.R3S.
R3SETUP
a) Add an exit step to the EXE section right before the section DBR3LOADEXECDUMMY*.
b) Remove the sections DBR3LOADEXECDUMMY* and DB3LOADEXEC_* from the EXE section.
But very brief when describing migmon integration to export process. It just says:
Export Monitor
1. If FTP access is used, verify that the required directories exist on the import server before the monitor is started. The import_dirs.sh shell script or the import_dirs.bat batch file can be used to create the correct directory structure.
2. Create or edit the export_monitor_cmd.properties file to specify the correct monitor options.
3. Start the Export Monitor as the <sapsid>adm user.
4. If any export errors occur, restart the monitor after the problem has been fixed.
Which is not enough information to integrate migmon to export process.
Am I correct in assumption that:
1. Exit step must be added in DBEXPORT.R3S in EXE section, right before DBR3LOADEXECDUMMY_IND_IND section?
2. Sections DBR3LOADEXECDUMMY_IND_IND and DBEXPR3LOADEXEC_IND_ORA must be removed as their tasks are performed by migration monitor?
Thanks and regards,
Michal Skrobak

Dear Michal,
the removing of the phases DBR3LOADEXECDUMMY* and DBEXPR3LOADEXEC* from .R3S
files is valid for export and for import too:
1. set exit in DBEXPORT.R3S before DBR3LOADEXECDUMMY
2. then remove DBR3LOADEXECDUMMY* and DBEXPR3LOADEXEC* from DBEXPORT.R3S
All further steps can be leaved unchanged in the .R3S template file for the export.
Kind regards
Sandor

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

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

Dual monitor screen refresh problem

We have a GUI application that runs on a dual monitor setup and are experiencing strange behaviour. The application is started on one monitor (the left hand one), but at times a window which has been dragged to the right hand monitor stops getting screen updates (e.g. typing show nothing on screen, but the characters are in fact in the field). If a window is positioned so that it overlaps both screens and the problem occurs, what we observe is the portion of the window on the left monitor (where the application was started) is redrawn successfully, but the portion of the window on the right hand monitor is not drawn at all - half the window shows correct detail, half the window is a grey rectangle.
This issue is not experienced when we run the application on a single monitor. The problem is intermittent, and is not due to idle time in the application (it can occur which an operator is working with the GUI).
We are running 1.5.0 update 5.

We noticed the same problem.
We've got JSE 1.5.0_06 and a swing GUI. For me it looks like this: Only the bigger part of the application is refreshed. So if the application starts at the secondary monitor and is dragged so that a small part of the GUI is displayed on the primary monitor only the bigger part of the GUI (so that one on the secondary monitor) gets refreshed. So scrolling leads to graphic mistakes in the smaller GUI part.
If the main part of the application runs on the primary monitor and only a small part is on the secondary one we observe the same problem: Only the part on the primary monitor gets refreshed.
We also observed this grey rectangle paulch already mentioned.
Minimizing and refitting forces the repainting so then everything is fine.
Is was trying to find something in the bug database but I wasn't successful although I found several descriptions like this in this forum.
Can anybody present some work-around for this?
Thanks
Inga

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.

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

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 in TDMS shell creation

Hi,
I am working on a TDMS shell creation for ECC system, I have few question..
1) Is it mandatory to run migration monitor manually while in both exporting and importing database with R3load option in tdms shell creation or only while running R3load export?
2) How to run export monitor activity in background?
3) How to parallel R3load processes to export a single package instead running one r3load for each package?
OS: AIX
DB: DB2
SAp ECC 6
Thanks
Praveen

Answers to your questions are below -
1) It is mandatory during the exports of data from the source system.
2) It should not be run in background
3) Use table splitting using R3TA, but that should be done before exports.

After Effects CS6: Cache and Reload Footage Problem

After Effects CS6: Cache and Reload Footage Problem
I am having trouble getting my footage to update in an AE project.
In an existing project, there is an image sequence in a composition. I have saved and closed AE, modified the footage (same dimensions and qty. of frames, only the pixel data changes), and then re-launched AE and opened the project. Though I have changed the footage, the old content still appears.
To resolve this, I have done the following:
Edit>Purge>All Memory
Edit>Purge>Image Cache Memory
Edit>Preferences>Media & Disk Cache>Empty Disk Cache
Edit>Preferences>Media & Disk Cache>Clean Database & Cache
From the Project window I've selected all footage and selected Reload
None of these got the footage to update. I could double-click on the footage in the project bin and scrub the play head and the old footage was still displayed.
Finally I had to replace the footage with itself and that resolved the issue.
If this is operator error, lack of understanding the cache functions, or something else, I'd appreciate some assistance. I don't recall this behavior in CS 5.5, so I am guessing this is a change in CS 6.
Win 7 Pro 64bit Service Pack 1
Intel Xeon CPU X5450 @ 3.00 GHz 2.99 GHz
RAM 20 GB

about Illustrator and Photoshop files in CS6 especially - you should work with Ctrl/Cmd+E (Edit Original).
when in Ae and you want to change a source file, use this command on one of the layers
from the source file you wish to change (doesn't matter if its in the timeline or project window) and
your original software linked to that file will open.
when you work this way you make AE reload that file and any change after that will be seen back in AE immediately.
it is also very convenient way to work because there can be no confusion on which file you are on
if you work with multiple source files for example.
even if you made the change with your Photoshop/Illustrator opened file and got back to Ae
and didn't see any change - press on one of the layers Ctrl/Cmd+E and this will refresh it immediately.
This is the case in CS6.
in CC I have noticed that any change I make is refreshed immediately in Ae as if it rechecks the changes all the time,
and didn't even need to use Ctrl/Cmd+E but it's a good habit all the same.
didn't come across a case where that didn't work for be but
if all fails you could always change the folder location of the file, let Ae lose it, then replace footage of the file,
and thus let Ae re-link it back.

Migration monitor - Reload DB problem

Similar Messages

Maybe you are looking for