on 06-25-2008 10:08 AM
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
Dear Marcin,
It may be that some files of the Migration Monitor are missing or corrupt. In that case you may simply apply the latest patch of Migmon as per note 784118 - archive 'MIGMON.SAR' - simply download and extract the archive to your installation directory.
[784118 - System Copy Java Tools|https://service.sap.com/sap/support/notes/784118]
Thanks,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thats right, but i suppose that sapinst should uncar this archive during installation and migmon.jar is started by java exec, So where is this temp directory where sapinst should unpack MIGMON.SAR archive ?
yes - right - it should be placed in your installation directory...
(I think in your case it´s /db2/IED/sapdata3/sapinstdir1/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/)
Markus
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.
I'm using ECC 6.0 SR3 fresh downloaded instalallation disks and DB6 9.5 from SAP service.sap.com.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.