on 04-27-2016 3:10 PM
Hi experts,
we try to export a NW 7.0 instance from oracle 11 db with R3load.
Environment information:
OS info:
Nodename: <hostname>
Release: HP-UX B.11.31
Version: U (unlimited-user license)
Machine: ia64
DB info:
Oracle 11.2.0.2
Software:
SWPM 1.0 SP 10 (actual version)
While starting the export of the NW stack in phase "Run migration monitor" the export stops and creates an dump.
sapinst_dev.log:
----------------------------------------------------------------------------------------
ERROR 2016-04-27 16:07:34.181 (root/sapinst) [CSiStepExecute.cpp:1106] id=controller.step
Executed errno=FCO-00011
The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialo
g|ind|ind|ind|ind|abapUnload|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was exec
uted with status ERROR ( Last error reported by the step: Program 'Migration Monitor' exits wi
th error code 101. For details see log file(s) export_monitor.java.log, export_monitor.log.).
----------------------------------------------------------------------------------------
export_monitor.log:
----------------------------------------------------------------------------------------
ERROR: 2016-04-26 16:11:00 com.sap.inst.migmon.exp.ExportStandardTask run
Fatal exception during execution of the Export Monitor.
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:145)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:619)
at java.lang.StringBuffer.append(StringBuffer.java:340)
at java.io.BufferedReader.readLine(BufferedReader.java:345)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at com.sap.inst.migmon.imp.StrFileUtils.findPredefinedTableNames(StrFileUtils.java:54)
at com.sap.inst.migmon.MigrationTask.collectConversionPackageNames(MigrationTask.java:1206)
at com.sap.inst.migmon.exp.ExportStandardTask.createPredefinedPackageGroups(ExportStandardTask.java:26
4)
at com.sap.inst.migmon.exp.ExportTask.assignGroupPackages(ExportTask.java:255)
at com.sap.inst.migmon.exp.ExportStandardTask.doRun(ExportStandardTask.java:101)
at com.sap.inst.migmon.MigrationTask.run(MigrationTask.java:455)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPool
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoo
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecuto
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:763)
INFO: 2016-04-26 16:11:00
Export Monitor is stopped.
----------------------------------------------------------------------------------------
We already searched in the following SAP notes and tried the solutions without positive results :
The MIGMON.SAR file on SWPM 1.0 SP10 is modified on 16.04.2016. We also tried to replace the MIGMON.SAR file on the SWPM ISO. But all MIGMON.SAR files on service marketplace are older.
Also this did´t work.
Any suggestions?
Kind regards
Thorsten
We identified the problem was related to the package splitter.
While package splitter run he create a temporary file unter /tmp for package SAPNTAB.STR file and move this temporary file afterwards under <DUMPDIR>/ABAP/DATA
The SAPNTAB.STR has been created everytime with a size of +4GB and wasn´t a ASCII file.
SAP Support provided an alternative SPLIT.SAR file. We replaced the SPLIT.SAR file on the SWPM ISO. That works.
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.
Hi Cristiano,
yes we restarted completely. We followed the instructions from SAP Note 1420809
Kind regards,
Thorsten
Hi Cristiano,
yes, the first line is different. How much memory failed to allocate:
Standard:
java.lang.OutOfMemoryError: Java heap space (failed to allocate 537002000 bytes) (max heap: 1024 MB)
With 2048m:
java.lang.OutOfMemoryError: Java heap space (failed to allocate 1074003984 bytes) (max heap: 2048 MB)
With 4096m:
java.lang.OutOfMemoryError: Java heap space (failed to allocate 2148007964 bytes) (max heap: 2048 MB)
with 512m:
java.lang.OutOfMemoryError: Java heap space (failed to allocate 268509860 bytes) (max heap: 2048 MB)
We have tried a lot of variants 😉
We also tried to start the SAPINST manual as user <SID>adm with cshell from the SAPINST installations directory with:
/oracle/T11/oraarch/P11_sapinst_instdir/sapinst_exe.5770.1461925432/jre/bin/java -classpath migmon.jar:migmonctrl.jar:createorderby.jar -showversion -Xmx2048m -d64 com.sap.inst.migmon.exp.ExportMonitor -sapinst
We get exactly the same OOM exception.
We also opened a SAP call because of this issue.
Kind regards
Thorsten
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.