cancel
Showing results for 
Search instead for 
Did you mean: 

SUM upgrade error

Former Member
0 Kudos

Dear Experts,

We're struck with error during the Solution Manager SP upgrade (SP14) using SUM (Software Update Manager).

Error "java.lang.NullPointerException: while trying to invoke the method java.lang.Process.destroy() of a null object returned from com.sap.sdt.tools.proc.OsProcess.getProcessObject()." occurred during Execution phase step "Deploy SDM".

Please find below the Error log:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[F:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_12.LOG]/-->

<!--PATTERN[DEPLOY-SDM_12.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy version rule has been set to updateLowerOrChanged in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy error strategy has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deployment prerequisite check error strategy has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Undeploy error strategy has been set to skipDepending in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Undeploy dependency rule has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy timeout has been set to 7200 seconds in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Start parsing deployment order definition file F:\SUM\SUM\sdt\config\dodf.xml.

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\config\dodf.xml is parsed and relative deployment data model is extracted.

Dec 14, 2015 10:31:32 PM [Info  ]: Start parsing deployment order definition file F:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml.

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: Updating SDM...

Dec 14, 2015 10:31:32 PM [Info  ]: Unpacking F:/SUM/SolMan_Patches/SDMKIT17_0-10006657.JAR to folder F:/SUM/SUM/sdt/tmp/unpack_SDMKit...

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\tmp\unpack_SDMKit has been deleted.

Dec 14, 2015 10:31:32 PM [Info  ]: Directory F:\SUM\SUM\sdt\tmp\unpack_SDMKit has been created.

Dec 14, 2015 10:31:32 PM [Info  ]: Stopping SDM server...

Dec 14, 2015 10:31:32 PM [Info  ]: AS Java process ID 135 has been started.

Dec 14, 2015 10:31:32 PM [Info  ]:   Command line: F:\usr\sap\SID\DVEBMGS00\exe\sapjvm_5\bin\java.exe -Xmx900M -Djava.ext.dir=F:/usr/sap/SID/DVEBMGS00/SDM/program/lib;F:/usr/sap/SID/DVEBMGS00/exe/sapjvm_5/jre/lib/ext -cp . -jar F:\usr\sap\SID\DVEBMGS00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=F:/usr/sap/SID/DVEBMGS00/SDM/program logfile=F:\SUM\SUM\sdt\log\SUM\OperateSDM_23.LOG

Dec 14, 2015 10:31:32 PM [Info  ]:   Standard out: F:\SUM\SUM\sdt\log\SUM\OPERATESDM_12.OUT

Dec 14, 2015 10:31:32 PM [Info  ]: Deployment message for component SAP_JAVASL :

Dec 14, 2015 10:31:32 PM [Error ]: The following problem has occurred during step execution: java.lang.NullPointerException: while trying to invoke the method java.lang.Process.destroy() of a null object returned from com.sap.sdt.tools.proc.OsProcess.getProcessObject().

Any ideas, please?

Thanks & best regards,

Sreenu

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member185239
Active Contributor
0 Kudos

Dear Sreenivasa,

Kindly follow the sapnote http://service.sap.com/sap/support/notes/2179754

- Change the SDM mode from integration to standalone mode

- F:\SUM\SUM\sdt\tmp\unpack_SDMK

- Run the update.bat file

- After getting a success message.

- bring the SDM from standalone to integrated mode

- Start the SDM

- Retry the SUM phase again.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,

Also, this OSS note doesn't match to my current issue.

My issue is relating to SDM deployment. I applied the changes mentioned in OSS note: 2164752 but as mentioned in this note, I am not able to reset upgrade option as it is deactivated.

Once again, I am getting the same error message with JAVA stack even after applying the Note changes by stopping the upgrade or exiting the upgrade.

Any ideas, please?

With regards,

Sreenu

former_member185239
Active Contributor
0 Kudos

Dear Sreenivasa,

Kindly paste OperateSDM_23.LOG and OPERATESDM_12.OUT file.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Dear Ashutosh,

I don't find these files in SUM log directory.

Any ideas, please?

Best regards,

Sreenu

former_member185239
Active Contributor
0 Kudos

Hi Sreeni,

Kindly check the log files in below location



F:\SUM\SUM\sdt\log\SUM\OperateSDM_23.LOG




With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

check the solution provided in https://scn.sap.com/thread/3641457

Former Member
0 Kudos

Dear Sunil,

Provided solution does not match to my Issue.

Error message states that it is related to SDM deployment issue. OSS note: 2164752 (DEPLOY-SDM: NullPointerException error in SUM) seems to be correct solution for the issue but I am not able to reset the SUM upgrade after making the changes mentioned in this OSS note.

Any ideas, please? Do i have to perform the SUM upgrade once again from scratch?

Thanks & best regards,

Sreenu

Former Member
0 Kudos

Have you restarted the instance?

Former Member
0 Kudos

Yeah sunil, i already done as per the Note. But, same error result.