13 Replies Latest reply: May 14, 2012 1:14 AM by Emerson Nei de Paula RSS

SAPINST running out of memory in the middle of import process

Venu Katamneni
Currently Being Moderated

Hi,

 

We are running import process in the target systems as part of the unicode conversion. The import had been running for almost 50+ hours when suddenly the SAPINST GUI stopped with the following error. Did some body encounter this? If so, could you please respond? Thanks in advance..

 

******************************************************************************************************************************

 

WARNING    2009-07-02 20:57:04.906

           CJSlibModule::writeWarning_impl()

Execution of the command "/oracle/X02/j2sdk1.4.2_20/bin/java -classpath migcheck.jar -showversion -d64 com.sap.inst.migcheck.MigrationChecker -checkObjects -dbType ORA -tskDir /tmp/sapinst_instdir/NW701/LM/COPY/ORA/SYSTEM/DISTRIBUTED/AS-ABAP/DB -strDirs /oracle/dbexport/ABAP/DATA -trace all" finished with return code 101. Output:

java version "1.4.2_20-rev"

Java(TM) Platform, Standard Edition for Business (build 1.4.2_20-rev-b04)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_20-rev-b04, mixed mode)

 

java.lang.OutOfMemoryError

 

WARNING[E] 2009-07-02 20:57:04.910

           CJSlibModule::writeError_impl()

CJS-30022  Program 'Object Checker' exits with error code 101. For details see log file(s) object_checker.java.log, object_checker.log.

 

ERROR      2009-07-02 20:57:05.143 [sixxcstepexecute.cpp:950]

FCO-00011  The step runObjectChecker with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runObjectChecker was executed with status ERROR .

Actions