Enterprise Portal 7.0 Stack Upgrade 21 to 27 using SUM error

[former_member196664]

Hi All,

I got an error while stack upgrading Enterprise Portal 7.0 from SPS 21 to 27 using SUM in the execution phase.

An error has occurred during the execution of the Deploy SDM step.

Could not update components. Deployment of queue Queue_2014.11.05 at 13:36:56 completed with error Deployment completed with error. See status messages for individual components. 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.

You can find more information in the files E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_10.LOG and ProcessOverview.html.

To troubleshoot the problem use the provided information. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following keywords:

SUM  execute  pre-component-deploy  deploy-sdm  com.sap.sdt.jspm.service.JspmService  class com.sap.sdt.jspm.service.JspmServiceException

Below is from OPERATESDM.OUT and OPERATESDM.ERR logs.

Do not check version of installed SDM

Initializing SDM for update

Caught OutOfMemoryError

java.lang.OutOfMemoryError

Severe (internal) error. Return code: 16

Below is from deply_SDM log.

Nov 17, 2014 10:58:55 AM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_29.OUT
Nov 17, 2014 10:58:55 AM [Info  ]: Process ID 8 has been started.
Nov 17, 2014 10:58:55 AM [Info  ]: Waiting for process ID 8, name java.exe to finish.
Nov 17, 2014 10:59:00 AM [Info  ]: Process ID 8, name java.exe has been finished, exit code 0.
Nov 17, 2014 10:59:00 AM [Info  ]: Process ID 8, name java.exe has been terminated.
Nov 17, 2014 10:59:00 AM [Info  ]: SDM server has been set to standalone mode.
Nov 17, 2014 10:59:00 AM [Info  ]: Auto-updating SDM server...
Nov 17, 2014 10:59:00 AM [Info  ]: AS Java process ID 9 has been started.
Nov 17, 2014 10:59:00 AM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Djava.ext.dir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\/libs -cp . -jar E:\SUM\SUM\sdt\tmp\unpack_SDMKit\SDM.jar autoupdate sdmHome=e:/usr/sap/EPQ/JC00/SDM/program ignoreversion=true popDir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\
Nov 17, 2014 10:59:00 AM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_30.OUT
Nov 17, 2014 10:59:00 AM [Info  ]: Process ID 9 has been started.
Nov 17, 2014 10:59:00 AM [Info  ]: Waiting for process ID 9, name java.exe to finish.
Nov 17, 2014 10:59:11 AM [Info  ]: Process ID 9, name java.exe has been finished, exit code 16.
Nov 17, 2014 10:59:11 AM [Info  ]: Process ID 9, name java.exe has been terminated.
Nov 17, 2014 10:59:11 AM [Error ]: Return code condition success evaluated to false for process java.exe for action ACTION_AUTO_UDPATE.
Nov 17, 2014 10:59:11 AM [Error ]: Cannot execute Java process for autoUpdate.
Nov 17, 2014 10:59:11 AM [Error ]: Could not auto-update SDM server.
Nov 17, 2014 10:59:11 AM [Error ]: Cannot update SDM tool.
Nov 17, 2014 10:59:11 AM [Info  ]: Deployment message for component 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.

Nov 17, 2014 10:59:11 AM [Info  ]: Overal deployment message : Deployment completed with error. See status messages for individual components.
Nov 17, 2014 10:59:11 AM [Info  ]: Saving data model Jump.JSPM.DataModel.xml ...
Nov 17, 2014 10:59:11 AM [Info  ]: Data model Jump.JSPM.DataModel.xml saved.
Nov 17, 2014 10:59:11 AM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...
Nov 17, 2014 10:59:14 AM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.
Nov 17, 2014 10:59:14 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.
Deployment of queue Queue_2014.11.05 at 13:36:56 completed with error Deployment completed with error. See status messages for individual components.
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.

I have a SAP ticket open for more than 10 days and no response. I found Note 1249354 - SDM autoupdate fails because of OutOfMemoryError is not clear exactly what I have to perform. Please help ASAP.

Thanks,

Kavitha Rajan.

[srinivasan_vinayagam · Accepted solution]

Hi Kavitha,

set below parameter in windows system environment variable

JAVA_OPTS="-Xms128m -Xmx4096m -XX:MaxPermSize=512m"

and start the SUM again.

if not work try below in windows environment

Set JAVA_OPTS="$JAVA_OPTS -Xmx1024m -XX:MaxPermSize=256m"

[former_member196664 · Accepted solution]

Srinivasan,

I have set set JAVA_OPTS=-Xmx2048m -XX:MaxPermSize=512m in DSUService.bat as you advised, do I have to set in Environment variable as well?

[srinivasan_vinayagam · Accepted solution]

Hi Kavitha,

Yes. Set it and try.

You said...one of your previous message the value 512M is back to 256M.. So you can set in system environment variable

[former_member196664 · Accepted solution]

Yes, Pls note it is happening (switching automatically to 256) only in SUM directory E:\SUM\SUM\sdt\tmp\unpack_SDMKit SDM memory parameters. Not under SDM home.

[former_member196664 · Accepted solution]

Hi All,

I have fixed the issue with config tool. Removed sys admin role from SAPEQDB user. I m fine with this issue now. I will attempt changing JDK as per ur advise.

Thank you all again.

[former_member196664 · Accepted solution]

I think I replied to the wrong thread.

[hemanth2 · Accepted solution]

Great news Kavitha.

Below will help with the JVM switch:

SAP Note No. 1367498 - SAP JVM installation prerequisites

SAP Note No. 1442124 How to download a SAP JVM patch from the SMP

SAP Note No. 1133020 How to import a SAP JVM patch into an AS Java

SAP Note No. 1603093- SAP JVM 4.1 parameters NetWeaver 2004 and 7.0

SAPJVM 4.1 Switch Procedure Including Screenshots:

<http://scn.sap.com/docs/DOC-33488>

Kind regards,
Hemanth

[former_member196664 · Accepted solution]

Thank you so much. Appreciate all the help. Do I have to remove JAVA_HOME from environment variables?

[former_member196664 · Accepted solution]

Hemanth,

Asking for JCE, for this, can I use the old JCE files from oracle? Or should I look for files in SAP.  Pls advise.

"Specify the location of the Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy File for JDK vendor Sun Microsystems Inc. and JDK version 1.4. Enter the absolute path to the archive. Note that you must not unzip the archive."

Thanks,

Kavitha

[hemanth2 · Accepted solution]

Kavitha, the JVM switch tool will tae care of this. The JAVA_HOME will now point to the sapjvm bin directory.

Kind regards,
Hemanth

[former_member196664 · Accepted solution]

I used Oracle JCE and completed SAP JVM switch in SBX. I will continue in DEV and QAS and will start Upgrade again.

Hemanth,

After cwitching to SAP JVM, do I have to change anthing with respect to upgrade in SUM? Can I just start from point of failure. Does it pick up SAP JVM from SAP automatically? Pls advise. Also do I need to remove old java_home from environment variable? Or change it?

Thanks,

Kavitha Rajan.

[hemanth2 · Accepted solution]

Hi Kavitha,

Note 1240081  - Java Cryptography Extension (JCE) Jurisdiction Policy Files            

has all the details in this regard.

"

"Unlimited" policy files need to be obtained from Oracle:

• http://www.oracle.com/technetwork/java/javase/downloads/index.html
• SAP JVM 4.1, 5.1 and 6.1
  • go to above mentioned URL
  • click "Previous Releases" > "Java Platform Technologies"
  • select the policy files according to your Java version:
    
    Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2
    
    Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0
    
    Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6
    
    

"

These files should be enough.

Regards,
Hemanth

[hemanth2 · Accepted solution]

All you need to make sure is that the SAP APPLICATION SERVER JAVA takes the new JDK (the jvm switch tool shuld take care of this).

Else:

Edit the instance profile and change the profile parameter

    SAPJVM_VERSION. Enter the new version of the SAP JVM e.g.:

    SAPJVM_VERSION = 4.1.028

    and

    jstartup/vm/home = <location of the new jdk>

    for example:

    jstartup/vm/home = /usr/sap/<SID>/SYS/exe/jvm/hpia64/

                       sapjvm_4.1.028

Regards,
Hemanth

[hemanth2 · Accepted solution]

HI Kavitha,

The best option would be restart SUM. The steps would be:

1) Stop SUM tool and make sure there are no leftover processes;
2) Set com.sap.sdt.severity to DEBUG in:
    -SUM\sdt\param\logging.properties
    -SUM\sdt\prop\logging.properties
    -SUM\java\param\logging.properties
3) Start SUM tool again and repeat the failing phase.
    Logs required for analysis:
    -SUM\java\log
    -SUM\java\trc
    -SUM\sdt\log
    -SUM\sdt\trc

Regards,
Hemanth

[former_member196664 · Accepted solution]

Hi All,

After SAP JVM switch. I am still getting getting error with upgrade using SUM. Pls help.

E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_36.LOG

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_36.LOG]/-->
<!--PATTERN[DEPLOY-SDM_36.LOG]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Nov 25, 2014 10:52:08 AM [Info  ]: Number of source deployed components detected from components provider: 0
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP_JTECHF
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCKITGP
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCBASE
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/RTC
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/JSPM
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/CAF-UM
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP_BUILDT
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/KM-KW_JIKS
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI_MMR
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/RTC-STREAM
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP-JEE
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/ADSSAP
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/NET-PDK
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/JLOGVIEW
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI-BASE-S
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/EPBC2
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/CAF
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP-JEECOR
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI-IBC
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCFLEX
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP_JTECHS
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/WDEXTENSIONS
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCFRAMEWORK
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/EPBC
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/KMC-BC
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/EP-WDC
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/KMC-COLL
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/EP_BUILDT
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/EP-PSERV
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/LM-TOOLS
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI_UDI
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/LM-PORTAL
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/CORE-TOOLS
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI-REPPLAN
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/CAF-KM
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BI-WDALV
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCKITBI
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/UMEADMIN
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BIWEBAPP
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/UWLJWF
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP-EU
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/KMC-CM
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/VCKITXX
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BASETABLES
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/CrestronLogonApp
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP KERNEL UNICODE WINDOWS_X86_64
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/BC-FES-IGS WINDOWS_X86_64
Nov 25, 2014 10:52:09 AM [Info  ]: Initialize map with source deployed component sap.com/SAP_JAVASL
Nov 25, 2014 10:52:09 AM [Info  ]: Number of source deployed components detected from components provider: 48
Nov 25, 2014 10:52:09 AM [Info  ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.
Nov 25, 2014 10:52:09 AM [Info  ]: Deploy version rule has been set to updateLowerOrChanged in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Deploy error strategy has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Deployment prerequisite check error strategy has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Undeploy error strategy has been set to skipDepending in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Undeploy dependency rule has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Deploy timeout has been set to 7200 seconds in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 25, 2014 10:52:09 AM [Info  ]: Start parsing deployment order definition file E:\SUM\SUM\sdt\config\dodf.xml.
Nov 25, 2014 10:52:09 AM [Info  ]: File E:\SUM\SUM\sdt\config\dodf.xml is parsed and relative deployment data model is extracted.
Nov 25, 2014 10:52:09 AM [Info  ]: Start parsing deployment order definition file E:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml.
Nov 25, 2014 10:52:09 AM [Info  ]: File E:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.
Nov 25, 2014 10:52:10 AM [Info  ]: Number of source deployed components detected from components provider: 48
Nov 25, 2014 10:52:10 AM [Info  ]: Updating SDM...
Nov 25, 2014 10:52:10 AM [Info  ]: Unpacking E:/SUM/SUM/EPQ/SDMKIT27_0-10003463.JAR to folder E:/SUM/SUM/sdt/tmp/unpack_SDMKit...
Nov 25, 2014 10:52:10 AM [Info  ]: File E:\SUM\SUM\sdt\tmp\unpack_SDMKit has been deleted.
Nov 25, 2014 10:52:10 AM [Info  ]: Directory E:\SUM\SUM\sdt\tmp\unpack_SDMKit has been created.
Nov 25, 2014 10:52:12 AM [Info  ]: Stopping SDM server...
Nov 25, 2014 10:52:12 AM [Info  ]: AS Java process ID 1 has been started.
Nov 25, 2014 10:52:12 AM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Xmx900M -Djava.ext.dir=e:/usr/sap/EPQ/JC00/SDM/program/lib;C:/j2sdk1.4.2_13-x64/jre/lib/ext -cp . -jar e:\usr\sap\EPQ\JC00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=e:/usr/sap/EPQ/JC00/SDM/program logfile=E:\SUM\SUM\sdt\log\SUM\OperateSDM_59.LOG
Nov 25, 2014 10:52:12 AM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_106.OUT
Nov 25, 2014 10:52:12 AM [Info  ]: Process ID 1 has been started.
Nov 25, 2014 10:52:12 AM [Info  ]: Waiting for process ID 1, name java.exe to finish.
Nov 25, 2014 10:52:23 AM [Info  ]: Process ID 1, name java.exe has been finished, exit code 0.
Nov 25, 2014 10:52:23 AM [Info  ]: Process ID 1, name java.exe has been terminated.
Nov 25, 2014 10:52:23 AM [Info  ]: SDM server has been stopped.
Nov 25, 2014 10:52:23 AM [Info  ]: Setting SDM server to standalone mode...
Nov 25, 2014 10:52:23 AM [Info  ]: AS Java process ID 2 has been started.
Nov 25, 2014 10:52:23 AM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Xmx900M -Djava.ext.dir=e:/usr/sap/EPQ/JC00/SDM/program/lib;C:/j2sdk1.4.2_13-x64/jre/lib/ext -cp . -jar e:\usr\sap\EPQ\JC00\SDM\program\bin\SDM.jar jstartup mode=standalone sdmHome=e:/usr/sap/EPQ/JC00/SDM/program logfile=E:\SUM\SUM\sdt\log\SUM\OperateSDM_59.LOG
Nov 25, 2014 10:52:23 AM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_107.OUT
Nov 25, 2014 10:52:23 AM [Info  ]: Process ID 2 has been started.
Nov 25, 2014 10:52:23 AM [Info  ]: Waiting for process ID 2, name java.exe to finish.
Nov 25, 2014 10:52:30 AM [Info  ]: Process ID 2, name java.exe has been finished, exit code 0.
Nov 25, 2014 10:52:30 AM [Info  ]: Process ID 2, name java.exe has been terminated.
Nov 25, 2014 10:52:30 AM [Info  ]: SDM server has been set to standalone mode.
Nov 25, 2014 10:52:31 AM [Info  ]: Auto-updating SDM server...
Nov 25, 2014 10:52:31 AM [Info  ]: AS Java process ID 3 has been started.
Nov 25, 2014 10:52:31 AM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Djava.ext.dir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\/libs -cp . -jar E:\SUM\SUM\sdt\tmp\unpack_SDMKit\SDM.jar autoupdate sdmHome=e:/usr/sap/EPQ/JC00/SDM/program ignoreversion=true popDir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\
Nov 25, 2014 10:52:31 AM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_108.OUT
Nov 25, 2014 10:52:31 AM [Info  ]: Process ID 3 has been started.
Nov 25, 2014 10:52:31 AM [Info  ]: Waiting for process ID 3, name java.exe to finish.
Nov 25, 2014 10:52:39 AM [Info  ]: Process ID 3, name java.exe has been finished, exit code 16.
Nov 25, 2014 10:52:39 AM [Info  ]: Process ID 3, name java.exe has been terminated.
Nov 25, 2014 10:52:39 AM [Error ]: Return code condition success evaluated to false for process java.exe for action ACTION_AUTO_UDPATE.
Nov 25, 2014 10:52:39 AM [Error ]: Cannot execute Java process for autoUpdate.
Nov 25, 2014 10:52:39 AM [Error ]: Could not auto-update SDM server.
Nov 25, 2014 10:52:39 AM [Error ]: Cannot update SDM tool.
Nov 25, 2014 10:52:39 AM [Info  ]: Deployment message for component 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.

Nov 25, 2014 10:52:39 AM [Info  ]: Overal deployment message : Deployment completed with error. See status messages for individual components.
Nov 25, 2014 10:52:39 AM [Info  ]: Saving data model Jump.JSPM.DataModel.xml ...
Nov 25, 2014 10:52:39 AM [Info  ]: Data model Jump.JSPM.DataModel.xml saved.
Nov 25, 2014 10:52:39 AM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...
Nov 25, 2014 10:52:43 AM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.
Nov 25, 2014 10:52:44 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.
Deployment of queue Queue_2014.11.05 at 13:36:56 completed with error Deployment completed with error. See status messages for individual components.
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.

Last few lines of UseCaseExec.log

Nov 25, 2014 10:52:07 AM [Info]: Skipping execution of Step with ID check-offline-components-slot as it has already been executed. Status ID SUM.execute.pre-component-deploy.1.check-offline-components-slot
Nov 25, 2014 10:52:07 AM [Info]: Skipping execution of Step with ID set-rfcengine-mode-manual as it has already been executed. Status ID SUM.execute.pre-component-deploy.1.set-rfcengine-mode-manual
Nov 25, 2014 10:52:07 AM [Info]: Skipping execution of Step with ID run-cleanipc as it has already been executed. Status ID SUM.execute.pre-component-deploy.1.run-cleanipc
Nov 25, 2014 10:52:07 AM [Info]: Skipping execution of Step with ID install-as-java-service as it has already been executed. Status ID SUM.execute.pre-component-deploy.1.install-as-java-service
Nov 25, 2014 10:52:07 AM [Info]: Evaluation pre-condition DplSlotJAVASLPresent == "true" of step deploy-sdm.
Nov 25, 2014 10:52:07 AM [Info]: Pre-condition DplSlotJAVASLPresent == "true" of step deploy-sdm resulted in true.
Nov 25, 2014 10:52:07 AM [Info]: Step Deploy SDM started.
Nov 25, 2014 10:52:07 AM [Info]:  Step type is com.sap.sdt.executor.step.StepExecutor.
Nov 25, 2014 10:52:07 AM [Info]: Changed the execution state of Step deploy-sdm from ABORTED to RUNNING.
Nov 25, 2014 10:52:07 AM [Info]: Service log file is E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_36.LOG
Nov 25, 2014 10:52:07 AM [Info]: Starting execution of Step Step ID: deploy-sdm
Service Ref: com.sap.sdt.jspm.service.JspmService
Operation: updateComponents
Can Revoke: true
Display Name: Deploy SDM
Can Reset: false
Step Parameters Map: {0=Parameter
Type: in
Index: 0
Reference: DplSlotJAVASLComponents
Value Type: list
Value: null
Is password: false
dataModelStorage: false
Entries: []
, 1=Parameter
Type: in
Index: 1
Reference: DeployUser
Value Type: string
Value: null
Is password: false
dataModelStorage: false
Entries: []
, 2=Parameter
Type: in
Index: 2
Reference: DeployUserPassword
Value Type: string
Value: null
Is password: false
dataModelStorage: false
Entries: []
, 3=Parameter
Type: in
Index: 3
Reference: null
Value Type: boolean
Value: true
Is password: false
dataModelStorage: false
Entries: []
}
.
Nov 25, 2014 10:52:08 AM [Info]: Loaded parameters for operation updateComponents.
Nov 25, 2014 10:52:44 AM [Info]: Changed the execution state of Step deploy-sdm from RUNNING to ABORTED.
Nov 25, 2014 10:52:44 AM [Error]: The following problem has occurred during step execution: java.lang.reflect.InvocationTargetException.
Nov 25, 2014 10:52:44 AM [Info]: Changed the execution state of Module pre-component-deploy from RUNNING to ABORTED.
Nov 25, 2014 10:52:44 AM [Error]: A problem has occurred: com.sap.sdt.executor.exception.StepExecutionException: Problem while trying to execute operation on service  deploy-sdm. The following problem has occurred java.lang.reflect.InvocationTargetException. CSN Component BC-UPG-TLS-TLJ.
Could not update components.
Deployment of queue Queue_2014.11.05 at 13:36:56 completed with error Deployment completed with error. See status messages for individual components.
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.

.
Nov 25, 2014 10:52:57 AM [Info]: Zip file E:\SUM\SUM\sdt\log\errorReport.zip with collected logs created succesfully.

Trouble Ticket Report

Update to SAP NETWEAVER 7.0

SID................: EPQ
Hostname...........: sapepqas
Install directory..: e:\usr\sap\EPQ
SUM directory......: E:\SUM\SUM\sdt
Database...........: MSS
Operating System...: WIN
JDK version........: 1.6.0_81 SAP AG
SUM version........: 1.0.11.7
Source release.....: n/a
Target release.....: 7.00
ABAP stack present.: false

An error has occurred during the execution of the Deploy SDM step with action execute. Service com.sap.sdt.jspm.service.JspmService failed with the following message:

Could not update components.

You can find more information in the files E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_36.LOG and ProcessOverview.html.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

SUM,execute,pre-component-deploy,deploy-sdm,com.sap.sdt.jspm.service.JspmService,class com.sap.sdt.jspm.service.JspmServiceException

Thanks,

Kavitha Rajan.

[hemanth2 · Accepted solution]

Hi Kavitha,

Why is SDM stil using the OLD JDK?

"

Nov 25, 2014 10:52:23 AM [Info  ]: Setting SDM server to standalone mode...

Nov 25, 2014 10:52:23 AM [Info  ]: AS Java process ID 2 has been started.

Nov 25, 2014 10:52:23 AM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Xmx900M -Djava.ext.dir=e:/usr/sap/EPQ/JC00/SDM/program/lib;C:/j2sdk1.4.2_13-x64/jre/lib/ext -cp . -jar e:\usr\sap\EPQ\JC00\SDM\program\bin\SDM.jar jstartup mode=standalone sdmHome=e:/usr/sap/EPQ/JC00/SDM/program
"

Before starting the upgrade, did you make sure that the source server was up and running and all applications including SDM is using the new JVM?

Check the instance profile in /usr/sap/<SID>/SYS/profile/<SID>_JC<num>_<host> and add

the following line

jstartup/vm/home = <location of the new jdk>

(If it is not present).

Kind regards,
Hemanth

[former_member196664 · Accepted solution]

Hemanth/All,

SAP asked to check Note 879377 

• Add the parameters to the value of sdm.JavaParameters property in /usr/sap/<SID>/<INSTANCE_ID>/SDM/program/config/sdm_jstartup.properties file
• Add the parameters to the value of sdm_java_paramsproperty in /usr/sap/<SID>/<INSTANCE_ID>/SDM/program/sdm_jdk.bat

Both parameters are blank. What do I need to fill in? Pls advise.

I am also checking the SDM jdk as per you advised. Which file do I have to modify? I see SAP is using SAP JVM. But how to check for SDM?

Thanks,

Kavitha Rajan.

[former_member196664 · Accepted solution]

Also, the only place I found old jdk is E:\usr\sap\EPQ\JC00\SDM\program\backup. I have modified sdm_jdk.bat to new SAP JVM.

[Reagan · Accepted solution]

Hello Kavitha

What is the value for the parameter sdm.JavaPath in the sdm_jstartup.properties file?

Also what is the value for the parameter sdm_java_home in the sdm_jdk.bat / sdm_jdk.sh files?

They should be pointing to the SAP JVM location.

Eg:

sdm_java_home=E:\usr\sap\EPQ\JC00\exe\sapjvm_4

sdm.JavaPath=E:\usr\sap\EPQ\JC00\exe\sapjvm_4

Reagan

[former_member196664 · Accepted solution]

Reagan,

sdm_jdk.bat was having sdm_java_home=E:/usr/sap/EPQ/JC00/exe/sapjvm_4

But sdm_jstartup.properties had the old path and just modified. I will restart SAP and try upgrade again. But SAP also asked about

• Add the parameters to the value of sdm.JavaParameters property in /usr/sap/<SID>/<INSTANCE_ID>/SDM/program/config/sdm_jstartup.properties file
• Add the parameters to the value of sdm_java_paramsproperty in /usr/sap/<SID>/<INSTANCE_ID>/SDM/program/sdm

Pls advise the value to fill in. both parameters are blank.

Thanks,

Kavitha Rajan.

[hemanth2 · Accepted solution]

I think the best option is that you remove the old JDK completely.
The version j2sdk1.4.2_13-x64 is very very old.

1)
Uninstall the old JDK. Then make sure that the instance profile has :

    SAPJVM_VERSION. Enter the new version of the SAP JVM e.g.:

    SAPJVM_VERSION = 6.1.048

    and

    jstartup/vm/home = <location of the new jdk>

    for example:

    jstartup/vm/home = /usr/sap/<SID>/SYS/exe/jvm/hpia64/

                       sapjvm_6.1.048

2)

SDM parameters are right:

sdm_java_home=E:\usr\sap\EPQ\JC00\exe\sapjvm_4

sdm.JavaPath=E:\usr\sap\EPQ\JC00\exe\sapjvm_4

3)

Once this is done,

3.1)

Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of
the existing files. Do not rename the bootstrap folder as this is needed for the sync process.

3.2)

Change bootstrap.properties file to ensure it has element.resynch=force as per SAP
note 710663.

3.3)

Delete following files

/usr/sap/<SID>/<INSTANCE>/j2ee/cluster/instance.properties.vmprop

/usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdm_jstartup.properties.vmprop

3.4)

Restart the J2EE Engine. The new server folders should be created during the
bootstrapping and this is a time consuming process as all the contents of the
server nodes will be syched with the DB content.

3.5)

  Remove the element.resynch=force property or change it to element.resynch=detect which
is the default setting.

Let us know the outcome. The next time the dev_sdm should point to the right JVM.

Regards,
Hemanth

[former_member196664 · Accepted solution]

Hi All,

SUM was not picking SAP JVM despite SAP was using SAP JVM. After checking with SAP, I used JSPM and performed Stack Upgrade.

Thanks,

Kavitha Rajan.

[hemanth2]

Also try to increase the SDM heap to 1024 MB if you have enough RAM and try this as well.

[former_member196664]

Hemanth,

I increased heap still same. At the last option, I will re-install SDM.

Thanks,

Kavitha Rajan.

[srinivasan_vinayagam]

Hi Kavitha,

Do not replace the SUM, check the SDM version.

Regards,

V Srinivasan

[hemanth2]

Great, please keep us posted.
Please increase the SDM severity before starting SUM again.

[srinivasan_vinayagam]

Hi Kavitha,

Have you checked below three notes?

879377 - How to adjust the JVM parameters used by SDM?

1249354 - SDM autoupdate fails because of OutOfMemoryError

1264514 - OutOfMemoryError in SDM and hanging RemoteGUI, JSPM, EHPI

Regards,

V Srinivasan

[former_member196664]

Hi Srinivasan,

Yes I have updated SDM memory to 512M.

Thanks,

Kavitha Rajan.

[former_member196664]

Hi All,

Just figured out, after I update E:\SUM\SUM\sdt\tmp\unpack_SDMKit update.bat to 512M install.bat to 512M for the memory, it is still changing back to 256M once I executed the failed step in SUM. I tried command sdm.bat newjdk "memory=512 ", executed successfully. But not sure how the value is changing back to 256M. Please advise how to fix this.

Thanks,

Kavitha Rajan.

[former_member196664]

Also,

I have below values set.

E:\usr\sap\EPQ\JC00\SDM\program sdm_jdk.bat is 512

E:\usr\sap\EPQ\JC00\SDM\program\instfiles update.bat is 512

E:\usr\sap\EPQ\JC00\SDM\program\config sdm_jstartup.properties sdm.MaxHeapSize=1024

[hemanth2]

Hi Kavitha,

is the command sdm.bat newjdk "memory=512 " working? This will make sure that at runtime, this is the memory assigned.

Kind regards,
Hemanth

[former_member196664]

SDM.properties SDM version = 1.0

Thanks,

Kavitha

[former_member196664]

Hemanth,

When I execute the command, below are the results.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\epqadm>E:

E:\>cd usr\sap\EPQ\JC00\SDM\program

E:\usr\sap\EPQ\JC00\SDM\program>sdm.bat newjdk "memory=512"

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_java_home=C:/j2sdk1.4.2_13-x64

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_64bit_switch=

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_heap_size=512

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_java_params=

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_memory_switch=-Xmx512M

E:\usr\sap\EPQ\JC00\SDM\program>set sdm_com="C:/j2sdk1.4.2_13-x64\bin\java"   -X
mx512M  -jar "E:/usr/sap/EPQ/JC00/SDM/program\bin\SDM.jar"

E:\usr\sap\EPQ\JC00\SDM\program>"C:/j2sdk1.4.2_13-x64\bin\java"   -Xmx512M  -jar
"E:/usr/sap/EPQ/JC00/SDM/program\bin\SDM.jar" newjdk "sdmhome=E:/usr/sap/EPQ/JC
00/SDM/program" "memory=512"
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addI
viewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBased
SecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator g
enerateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem
startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConf
igurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHiera
rchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNo
de getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView
PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder en
code
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObject
s
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Inst
anceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Inst
anceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Type
MappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Gene
ratedComplexType _loadInto
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/7.0015.20080123135023.0000
Initializing Network Manager (50017)
Checking if another SDM is running on port 50018
modify file: 'E:/usr/sap/EPQ/JC00/SDM/program/config/sdm_jstartup.properties'
  set property: 'sdm.MaxHeapSize=512'
  Create file 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties.ne
w'
    out of 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties'
    while setting property 'sdm.MaxHeapSize=' to '512'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties'
    to 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties.bak'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties.new'

    to 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties'.
  Remove file 'E:\usr\sap\EPQ\JC00\SDM\program\config\sdm_jstartup.properties.ne
w'
modify file: 'E:/usr/sap/EPQ/JC00/SDM/program/sdm_jdk.bat'
  set property: 'set sdm_heap_size=512'
  Create file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat.new'
    out of 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat'
    while setting property 'set sdm_heap_size=' to '512'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat'
    to 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat.bak'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat.new'
    to 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat'.
  Remove file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.bat.new'
modify file: 'E:/usr/sap/EPQ/JC00/SDM/program/sdm_jdk.sh'
  set property: 'sdm_heap_size=512'
  Create file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh.new'
    out of 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh'
    while setting property 'sdm_heap_size=' to '512'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh'
    to 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh.bak'.
  Copy file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh.new'
    to 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh'.
  Remove file 'E:\usr\sap\EPQ\JC00\SDM\program\sdm_jdk.sh.new'
Successfully executed. Return code: 0

E:\usr\sap\EPQ\JC00\SDM\program>

[former_member196664]

Hemanth,

These are not getting updated in SUM directory. 😞

[srinivasan_vinayagam]

Hello Kavitha,

Follow this Note once again with double the memory what recommended below note

1249354 - SDM autoupdate fails because of OutOfMemoryError

If not worked try below.

Remove JAVA_HOME = C:\j2sdk1.4.2_13-x64\  from your environment and set JAVA_HOME from SUM directory SAPJVM will be there.

Or

Download latest SUM SP level and replace the SDM.jar  file.

Regards,

V Srinivasan

[former_member196664]

I am in the execution phase, at this time, can I replace entire SUM directory and start upgrade again? Please let me know.

Thanks,

Kavitha Rajan.

[former_member196664]

I extracted SUM10SP11_8, did not find tmp folder is empty to get new SDM.jar

[srinivasan_vinayagam]

Hi Kavitha,

You can try this.

1. Exit the SUM Tool and Open for edit SUM/sdt/exe/DSUService.bat to fine below line.

set JAVA_OPTS=-Xmx1024m --XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError

-Djava.system.class.loader=com.sap.sdt.bootstrap.SystemClassLoader

To increase the values as below

Change Xmx1024m to Xmx2048m and -XX:MaxPermSize=256m to

-XX:MaxPermSize=512m

Now start the SUM Tool and continue the update.

Regards,

V Srinivasan

[former_member196664]

Hi Reagan and Srinivasan,

I tried both of your suggestions. And I am getting the same error.OPERATESDM_54.OUT

Do not check version of installed SDM

Initializing SDM for update

Caught OutOfMemoryError

DEPLOY-SDM_18.log

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[E:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_18.LOG]/-->
<!--PATTERN[DEPLOY-SDM_18.LOG]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Nov 18, 2014 1:24:45 PM [Info  ]: Number of source deployed components detected from components provider: 48
Nov 18, 2014 1:24:45 PM [Info  ]: Number of source deployed components detected from components provider: 48
Nov 18, 2014 1:24:45 PM [Info  ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.
Nov 18, 2014 1:24:45 PM [Info  ]: Deploy version rule has been set to updateLowerOrChanged in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Deploy error strategy has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Deployment prerequisite check error strategy has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Undeploy error strategy has been set to skipDepending in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Undeploy dependency rule has been set to stop in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Deploy timeout has been set to 7200 seconds in file E:\SUM\SUM\sdt\param\jspm_config.txt.
Nov 18, 2014 1:24:45 PM [Info  ]: Start parsing deployment order definition file E:\SUM\SUM\sdt\config\dodf.xml.
Nov 18, 2014 1:24:45 PM [Info  ]: File E:\SUM\SUM\sdt\config\dodf.xml is parsed and relative deployment data model is extracted.
Nov 18, 2014 1:24:45 PM [Info  ]: Start parsing deployment order definition file E:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml.
Nov 18, 2014 1:24:45 PM [Info  ]: File E:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.
Nov 18, 2014 1:24:45 PM [Info  ]: Number of source deployed components detected from components provider: 48
Nov 18, 2014 1:24:45 PM [Info  ]: Updating SDM...
Nov 18, 2014 1:24:45 PM [Info  ]: Unpacking E:/SUM/SUM/EPQ/SDMKIT27_0-10003463.JAR to folder E:/SUM/SUM/sdt/tmp/unpack_SDMKit...
Nov 18, 2014 1:24:45 PM [Info  ]: File E:\SUM\SUM\sdt\tmp\unpack_SDMKit has been deleted.
Nov 18, 2014 1:24:45 PM [Info  ]: Directory E:\SUM\SUM\sdt\tmp\unpack_SDMKit has been created.
Nov 18, 2014 1:24:47 PM [Info  ]: Stopping SDM server...
Nov 18, 2014 1:24:47 PM [Info  ]: AS Java process ID 4 has been started.
Nov 18, 2014 1:24:47 PM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Xmx900M -Djava.ext.dir=e:/usr/sap/EPQ/JC00/SDM/program/lib;C:/j2sdk1.4.2_13-x64/jre/lib/ext -cp . -jar e:\usr\sap\EPQ\JC00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=e:/usr/sap/EPQ/JC00/SDM/program logfile=E:\SUM\SUM\sdt\log\SUM\OperateSDM_28.LOG
Nov 18, 2014 1:24:47 PM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_52.OUT
Nov 18, 2014 1:24:47 PM [Info  ]: Process ID 4 has been started.
Nov 18, 2014 1:24:47 PM [Info  ]: Waiting for process ID 4, name java.exe to finish.
Nov 18, 2014 1:24:48 PM [Info  ]: Process ID 4, name java.exe has been finished, exit code 104.
Nov 18, 2014 1:24:48 PM [Info  ]: Process ID 4, name java.exe has been terminated.
Nov 18, 2014 1:24:48 PM [Info  ]: SDM server has been stopped.
Nov 18, 2014 1:24:48 PM [Info  ]: Setting SDM server to standalone mode...
Nov 18, 2014 1:24:48 PM [Info  ]: AS Java process ID 5 has been started.
Nov 18, 2014 1:24:48 PM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Xmx900M -Djava.ext.dir=e:/usr/sap/EPQ/JC00/SDM/program/lib;C:/j2sdk1.4.2_13-x64/jre/lib/ext -cp . -jar e:\usr\sap\EPQ\JC00\SDM\program\bin\SDM.jar jstartup mode=standalone sdmHome=e:/usr/sap/EPQ/JC00/SDM/program logfile=E:\SUM\SUM\sdt\log\SUM\OperateSDM_28.LOG
Nov 18, 2014 1:24:48 PM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_53.OUT
Nov 18, 2014 1:24:48 PM [Info  ]: Process ID 5 has been started.
Nov 18, 2014 1:24:48 PM [Info  ]: Waiting for process ID 5, name java.exe to finish.
Nov 18, 2014 1:24:53 PM [Info  ]: Process ID 5, name java.exe has been finished, exit code 0.
Nov 18, 2014 1:24:53 PM [Info  ]: Process ID 5, name java.exe has been terminated.
Nov 18, 2014 1:24:53 PM [Info  ]: SDM server has been set to standalone mode.
Nov 18, 2014 1:24:53 PM [Info  ]: Auto-updating SDM server...
Nov 18, 2014 1:24:53 PM [Info  ]: AS Java process ID 6 has been started.
Nov 18, 2014 1:24:53 PM [Info  ]:   Command line: C:\j2sdk1.4.2_13-x64\bin\java.exe -Djava.ext.dir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\/libs -cp . -jar E:\SUM\SUM\sdt\tmp\unpack_SDMKit\SDM.jar autoupdate sdmHome=e:/usr/sap/EPQ/JC00/SDM/program ignoreversion=true popDir=E:/SUM/SUM/sdt/tmp\unpack_SDMKit\
Nov 18, 2014 1:24:53 PM [Info  ]:   Standard out: E:\SUM\SUM\sdt\log\SUM\OPERATESDM_54.OUT
Nov 18, 2014 1:24:53 PM [Info  ]: Process ID 6 has been started.
Nov 18, 2014 1:24:53 PM [Info  ]: Waiting for process ID 6, name java.exe to finish.
Nov 18, 2014 1:25:03 PM [Info  ]: Process ID 6, name java.exe has been finished, exit code 16.
Nov 18, 2014 1:25:03 PM [Info  ]: Process ID 6, name java.exe has been terminated.
Nov 18, 2014 1:25:03 PM [Error ]: Return code condition success evaluated to false for process java.exe for action ACTION_AUTO_UDPATE.
Nov 18, 2014 1:25:03 PM [Error ]: Cannot execute Java process for autoUpdate.
Nov 18, 2014 1:25:03 PM [Error ]: Could not auto-update SDM server.
Nov 18, 2014 1:25:03 PM [Error ]: Cannot update SDM tool.
Nov 18, 2014 1:25:03 PM [Info  ]: Deployment message for component 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.

Nov 18, 2014 1:25:03 PM [Info  ]: Overal deployment message : Deployment completed with error. See status messages for individual components.
Nov 18, 2014 1:25:03 PM [Info  ]: Saving data model Jump.JSPM.DataModel.xml ...
Nov 18, 2014 1:25:03 PM [Info  ]: Data model Jump.JSPM.DataModel.xml saved.
Nov 18, 2014 1:25:03 PM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...
Nov 18, 2014 1:25:06 PM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.
Nov 18, 2014 1:25:07 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.
Deployment of queue Queue_2014.11.05 at 13:36:56 completed with error Deployment completed with error. See status messages for individual components.
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.

I changed SDM update.bat and other heap as per the note 879377 to 512 in all the places. But again getting same error during EXECUTION phase and step "delete previous SUM configurations". Please help.

Thanks,

Kavitha Rajan.

.

[hemanth2]

Hi Kavitha,

Hope you are doing good.

Nice to hear from you again.

It is strange that the workaround wasn't successful. In such cases, please can you reinstall SDM as mentioned in SAP Note No. 860939: Initial installation/Update of SDM.
If the issue persists, detailed SDM logs will be helpful. Setup the logging severity to debug mode on SDM server:

open file /usr/sap/<SID>/JC<nr>/SDM/program/logging.properties and add the following lines:

com.sap.sdm.persistency.severity = ALL

com.sap.sdm.app.cvers.deplobs.severity = ALL

com.sap.sdm.app.cvers.deplobs.impl.severity = ALL

now open file /usr/sap/<SID>/JC<nr>/SDM/program/saplogging.config and change the last line

com.sap.sl.util.severity = ALL

Now the sdm logs should have more details.

Thank you!

____________

Kind Regards,

Hemanth

SAP AGS

[Reagan]

Good Evening Kavitha

Have you tried restarting the server and see if that helps ?

Another option is to update the JRE on the system and see if fixed this issues.

Do not change/replace the SUM directory with a new one as this is not recommended.

Reagan

[former_member196664]

Reagan,

I restarted server and again failing at same step.

[Reagan]

Hello Kavitha

I believe you are still using SUN Java on the machine. Could you update the JRE on the system or switch to SAP JVM and see if it helps?

Reagan

[hemanth2]

Hi Kavitha,

I completely agree with Reagan. I did mention this to you the last time as well .

Such "unusual " issues can be caused due to this unsupported JVMs.

regards,

hemanth

[Reagan]

Hello Kavitha

The note 1249354 - SDM autoupdate fails because of OutOfMemoryError is suggesting to set the heap value of 256M for the SDM.

Open a command prompt and put the SDM into standalone mode.

cd e:\usr\sap\EPQ\JC00\SDM\program

StopServer.bat

sdm.bat jstartup "mode=standalone"

Modify the update.bat file located at e:\usr\sap\EPQ\JC00\SDM\program\instfiles as suggested in the note. As a good practice backup the original update.bat file.

If the value of 256M is already set then increase it to 512M and see if it helps.

Also what does the log fle E:\SUM\SUM\sdt\log\SUM\OPERATESDM_29.OUT contain ?

Additionally check the SAP note 879377 - How to adjust the JVM parameters used by SDM? to set the heap value for SDM.

Reagan

[former_member196664]

Hi All,

I reverted back the kernel. But the problem still exists connecting to config tool. I am going to change JAVA as well. But looking to connect this DB connection issue first. Pls help. Below is the error I am getting while trying to connect to config tool.

"Error occurred while working with Configuration (Scanning). Msg:Erro while connecting to DB"

Thanks,
Kavitha Rajan.