Cannot auto update SDM during EHP upgrade using SUM

[Former Member]

Hi Gurus,

Currently we are upgrading our NW7.0 BW Usage type system to NW 7.02

OS - Windows 2008R2 and DB - SQL 2008 R2

Using latest version of SUM tool available in SMP. It is ABAP+ Java stack.

We are stuck in the Execution phase: Deploy SDM

The error says :

sap.com/SAP_JAVASL: Cannot update SDM tool.

Could not auto-update SDM server.

Cannot execute Java process for autoUpdate.

Return code condition success evaluated to false for process java.exe

for action ACTION_AUTO_UDPATE.

Please see the attached error logs - DEPLOY_SDM.LOG, OPERATESDM.ERR,
OPERATESDM.OUT for details.

I have checked various forums and note 1249354 but none is able to resolve this.

The update.bat file already has -Xmx=256M.

I tried to perform the update of SDM manually and there was no error using below command

Java -jar <tmp_dir>/bin/SDM.jar autoupdate

But now when we continue the upgrade using SUM from the point where it was
stopped, it again fails and cannot proceed further.

Kindly suggest your valuable inputs.

Cheers
SG

DEPLOY-SDM_39.TXT.zip

[AtulKumarJain · Accepted solution]

Hi Team,

could you please

-Xmx=512M and try this .

Please check

1249354 - SDM autoupdate fails because of OutOfMemoryError

BR

Atul

[Former Member · Accepted solution]

Hi Atul,

I did said that I tried note 1249354 already but its not helping.

Where shall I update this parameter -Xmx=512M in update.bat or Java parameters ?

I tried updating in update.bat, but as soon as SUM toll is rerun it rewrites update.bat file with -256M parameter.

Any other suggestions guys ?

Cheers,

SG

[AtulKumarJain · Accepted solution]

1)  Exit the SUM tool
2)  Open for edit SUM/sdt/exe/DSUService.bat
3)  Find following line:
set JAVA_OPTS=-Xmx1024m -XX:MaxPermSize=256m
-XX:+HeapDumpOnOutOfMemoryError
-Djava.system.class.loader=com.sap.sdt.bootstrap.SystemClassLoader

4)  Change Xmx1024m to Xmx2048m and -XX:MaxPermSize=256m to
-XX:MaxPermSize=512m
5)  Start the Sum tool and try to repeat the failed phase

[Former Member · Accepted solution]

Thanks Atul for taking interest in  my issue.

But somehow this workaround didn't helped

I have got same errors in log file again:

1.Cannot delete file M:\bwupgrade\SUM\sdt\tmp\unpack_SDMKit

2.java.lang.OutOfMemoryError

3.Processing error . Return code 104

Now regarding error 1, I tried to manually delete the file "unpack_SDMKit"

But it gave a popup, this file is in use by another process.

I am planning to take server REBOOT now and then start SUM tool again.

Can you please suggest if after rebooting server, SUM tool will continue from this step only ?

Kindly share if you have any other sugestions for me to try to... I am simply running out of ideas at this moment. Seems SDM is always having some issues.

Cheers,

SG

[AtulKumarJain · Accepted solution]

HI SG,

It is better to kill the process  if it still show the same issue you can reboot the server .

SUM tool will continue from where it stop.

Best Regadrs,

Atul

[Former Member · Accepted solution]

OK Atul, done that.

Still facing OutOfMemory issue

This is simply killing me.

1.java.lang.OutOfMemoryError

2.Processing error . Return code 104

Error is -

May 7, 2013 5:27:56 PM [Info  ]:   Command line: H:\j2sdk1.4.2_38-x64\bin\java.exe -Xmx900M -Djava.ext.dir=h:/usr/sap/BIP/DVEBMGS00/SDM/program/lib;H:/j2sdk1.4.2_38-x64/jre/lib/ext -cp . -jar h:\usr\sap\BIP\DVEBMGS00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=h:/usr/sap/BIP/DVEBMGS00/SDM/program logfile=M:\bwupgrade\SUM\sdt\log\SUM\OperateSDM_77.LOG

May 7, 2013 5:27:56 PM [Info  ]:   Standard out: M:\bwupgrade\SUM\sdt\log\SUM\OPERATESDM_110.OUT

May 7, 2013 5:27:56 PM [Info  ]: Process ID 338 has been started.

May 7, 2013 5:27:56 PM [Info  ]: Waiting for process ID 338, name java.exe to finish.

May 7, 2013 5:28:01 PM [Info  ]: Process ID 338, name java.exe has been finished, exit code 104

Cheers,

SG

[AtulKumarJain · Accepted solution]

Hi SG,

It will be good if you raise a meesage to sap.

Best Regards,

Atul

[Former Member · Accepted solution]

Raised the same with SAPOSS team, waiting for their reply.

Meanwhile, if anyone of you can suggest a solution here, that will be highly appreciated !

Cheers,

SG

[Former Member · Accepted solution]

HI All,

This SDM issue seemed a bit tricky and even SAP decided to skip this step after asking us to manually upgrade SDM component.

I have manually upgraded SDM and Skipped this step by keying in the password provided by SAP. ( Cannot share the password because of security reasons )

Finally our upgrade was completed successfully.

Cheers,

SG