ECC 6.0 System copy export fail

Question

WARNING 2011-12-08 21:38:22.281
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.exp.ExportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Export Monitor jobs: running 1, waiting 0, completed 45, failed 0, total 46.
Unloading of 'SAPAPPL0_5' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 45, failed 1, total 46.
ERROR 2011-12-08 21:38:22.282
CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.
ERROR 2011-12-08 21:38:22.293
FCO-00011  The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|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 103. For details see log file(s) export_monitor.java.log, export_monitor.log.).
I am using SAP ECC 6.0 with Ms Sql 2005 on 64 bit windows 2008 R2 OS. During a system copy export i am getting this error.
Please help me.

Answer 1

Your main problem is not, that you don't see anything in MMC (the system can be added manually without much hazzle) - but is, that you database content of schema SAP<SID>DB does not match the data found on the filesystem.
If you copy the filesystem structure from production to test/qa, you need to make sure, the database and filesystem are in sync. You will have two problems if you "just copy them":
- They are out of sync because your production was going on running since you copied the backup files
- all configuration (all java property sheets) is/are set to point to the production system instead of the test/qa system
I doubt, that it will work if you copy it over. This also explains, why you can't even start configtool, because it points to the wrong system/schema. You MAY be able to fix all that manually, but you may encounter subsequent errors because not all configuration is documented, you would need to step into the whole j2ee tree and look at each and every propertysheet to find out, whether it's correct or not. Additionally, the database may have other information (see above) and all that may become overwritten during bootstrap.
So - the best way to get your system up and running quickly is to start sapinst on the source system, export your Java instance (not using ABAP but the Java dump) and re-importing that to your test/qa system.
Markus