on 05-03-2007 2:53 AM
Hi All
We are trying to upgrade our BW 3.5 system to BI 7.0. Currently we ahve an ABAP stack with a java add-on.
W have run ABAP PREPARE thru to Phase GETSYNC_PREUP_FINI_D. It has halted at a phase that now waits for the java side to be upgraded.
Our java version is:
java full version "J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build
caix64142ifx-20061222 (ifix 113727: SR7 + 112603)"
When we start JPREPARE to upgraed the java stack we get the following error:
Waiting for SDTServer to connect on hostname rhubwp01/10.15.10.5 socket
6240 ...Allocation request for 1195725880 bytes
at com.sap.sdt.util.net.AbstractCharacterCommLink.read
(AbstractCharacterCommLink.java:105)
at com.sap.sdt.util.net.AbstractCommLink.receive
(AbstractCommLink.java:173)
at com.sap.sdt.util.net.AbstractCharacterCommLink.receiveMsg
(AbstractCharacterCommLink.java:57)
at com.sap.sdt.ucp.dialog.SDTServerConnection.receivePacket
(SDTServerConnection.java:803)
at com.sap.sdt.ucp.dialog.SDTServerConnection.handshake
(SDTServerConnection.java:738)
at com.sap.sdt.ucp.dialog.SDTServerConnection.connect
(SDTServerConnection.java:887)
at com.sap.sdt.ucp.dialog.SDTServerConnection.doSend
(SDTServerConnection.java:901)
at com.sap.sdt.ucp.dialog.SDTServerConnection.send
(SDTServerConnection.java:196)
at com.sap.sdt.ucp.dialog.AbstractServerConnection.send
(AbstractServerConnection.java:325)
at com.sap.sdt.ucp.dialog.AbstractServerConnection.process
(AbstractServerConnection.java:336)
at com.sap.sdt.ucp.dialog.Dialog.process(Dialog.java:194)
at com.sap.sdt.ucp.dialog.Dialog.process(Dialog.java:156)
at com.sap.sdt.ucp.pce.ctrl.ExecutionDialog.showWelcomeDialog
(ExecutionDialog.java:449)
at com.sap.sdt.ucp.pce.ctrl.ExecutionDialog.showWelcomeDialog
(ExecutionDialog.java:381)
at com.sap.sdt.ucp.pce.ctrl.ExecutionDirector.executeAction
(ExecutionDirector.java:142)
at com.sap.sdt.ucp.admin.ContextExecutor.executePce
(ContextExecutor.java:148)
at com.sap.sdt.ucp.admin.ContextExecutor.execute
(ContextExecutor.java:85)
at com.sap.sdt.ucp.main.CmdExecutor.runContext
(CmdExecutor.java:174)
at com.sap.sdt.ucp.main.CmdExecutor.executeRun
(CmdExecutor.java:149)
at com.sap.sdt.ucp.main.CmdExecutor.execute
(CmdExecutor.java:122)
at com.sap.sdt.tools.main.MainProgram.execute
(MainProgram.java:477)
at com.sap.sdt.ucp.main.Jump.main(Jump.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.sdt.bootstrap.BootStrap.start(BootStrap.java:153)
at Jump.main(Jump.java:88)
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
JVMDG318: Heap dump file written
to /usr/sap/jupgrade/heapdump831500.1178114861.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written
to /usr/sap/jupgrade/javacore831500.1178114862.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
Execution failed: Program has finished with error. 1
java.lang.OutOfMemoryError: JVMXE006:OutOfMemoryError, stAllocArray for
executeJava failed
com.sap.sdt.tools.main.MainException: Program has finished with error.
1java.lang.OutOfMemoryError: JVMXE006:OutOfMemoryError, stAllocArray forexecuteJava failed
at com.sap.sdt.tools.main.MainProgram.execute
(MainProgram.java:482)
at com.sap.sdt.ucp.main.Jump.main(Jump.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.sdt.bootstrap.BootStrap.start(BootStrap.java:153)
at Jump.main(Jump.java:88)
Can anybody please help.
Thanks
Sam
Hi All
SAP have come back with a solution to this. The information below is a note, however, since the note has been archived you cannot access it via SAP Service Marketplace.
Symptom
You are upgrading to SAP NetWeaver 2004s (or Business Suite 2005)
lower than Support Release 1.
The Java upgrade process results in a java.lang.OutOfMemoryError. In the
trouble ticket of the phase and in the phase log files you can find the
error message: Error java.lang.OutOfMemoryError <null>
This exception can occur in different phases of the upgrade, but most
often it occurs in the DETECT_START_RELEASE_COMPONENTS phase.
Other terms
NetWeaver UPGRADE, Java Upgrade, OutOfMemoryError
Reason and Prerequisites
The reason of the error is that there is not enough memory for saving
the upgrade data into xml files. The upgrade saves its internal data in
xml files and the size of these files can become very large - bigger
then 10 MB. The XML Processor may run out of memory while it saves the
xml file, which causes the error.
Solution
The problem is solved with the upgrade to SAP NetWeaver 2004s Support
Release 1 and Business Suite 2005 Support Release 1.
If you are upgrading to SAP NetWeaver 2004s (or Business Suite 2005)
lower than Support Release 1, then increase the JVM used by the Java
upgrade:
1. Stop the upgrade tool
2. Modify jump or jump.bat script, which is located in <upgrade
dir>/exe directory
- -for windows open the file jump.bat and add the line
set JUMP_JAVA_OPTS="-Xmx512m",
after the line:
set
CLASS_PATH=%ROOTDIR%\lib\sdt_bootstrap.jar;%ROOTDIR%\lib\sdt_u
cp.jar
- -for unix/linux systems edit the file jump and add the line
JUMP_JAVA_OPTS="-Xmx512m"
after the line:
classpath="$rootdir/lib/sdt_bootstrap.jar:$rootdir/lib/sdt_ucp
.jar"
3. Restart the upgrade tool.
Thanks
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.