Symptom
During upgrade of a Java system using the SUM tool, you face the below error in phase START-SHADOW-INSTANCE-DM.
Sum reports the below error :
The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 0.
Could not check if the instance number 0 on host XXXXXXX is started.
Sapcontrol client could not perform action wait for started on instance 0
Return code condition success evaluated to false for process sapcontrol for action wait for started.
For more details, you can refer to the respective upgrade logs as described below :
./SUM/sdt/log/SUMTroubleTicket.Log
An error has occurred during the execution of the Start java shadow instance step with action pre-execute. Service com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService failed with the following message:
Could not start SAP instance with number 14.
You can find more information in the files /usr/sap/<SID>/SUM/sdt/log/SWITCH/START-SHADOW-INSTANCE-DM_##.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:
SWITCH,pre-execute,deploy-shadow,start-shadow-instance-dm,com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService,class com.sap.sdt.util.diag.DiagException
./SUM/sdt/log/SUM/START-SHADOW-INSTANCE-DM_03.LOG
Sep 22, 2015 12:07:44 AM [Info ]: Command line: usr/sap/<sid>/SUM/sdt/data/kernel/sapcontrol -nr 14 -host xxxxx-prot NI_HTTP -function WaitforStarted 7200 5
Sep 22, 2015 12:07:44 AM [Info ]: Standard out: usr/sap/<sid>/SUM/sdt/tmp/SAPCONTROL_WAITFORSTARTED_14_03.OUT
Sep 22, 2015 12:07:44 AM [Info ]: Process ID 14 has been started.
Sep 22, 2015 12:07:44 AM [Info ]: Waiting for process ID 14, name sapcontrol to finish.
Sep 22, 2015 12:09:50 AM [Info ]: Process ID 14, name sapcontrol has been finished, exit code 2.
Sep 22, 2015 12:09:50 AM [Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started.
Sep 22, 2015 12:09:50 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 14.
Could not check if the instance number 14 on host saphcps is started.
Sapcontrol client could not perform action wait for started on instance 14
Return code condition success evaluated to false for process sapcontrol for action wait for started.
./SUM/sdt/log/SWITCH/SAPCONTROL_WAITFORSTARTED_14_03.OUT
22.09.2015 00:09:50
WaitforStarted
FAIL: process jstart J2EE Server not running
./usr/sap/<SID>/<instance Name>/work/ jvm_bootstrap.out:
Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: Database index
contains file
[/ext/bi~mmr~api/lib/sap.com~bi~mmr~coremodels_api_full.jar] that
cannot
be found in
[bin\runtime/ext/bi~mmr~api/lib/sap.com~bi~mmr~coremodels_api_full.jar]
/usr/sap/<SID>/<instance name>/work/ log_bootstartp.0.log:
Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: Database index
contains file
[/ext/bi~mmr~api/lib/sap.com~bi~mmr~coremodels_api_full.jar] that
cannot
be found in
[bin\runtime/ext/bi~mmr~api/lib/sap.com~bi~mmr~coremodels_api_full.jar]
Read more...
Environment
JAVA release upgrade using SUM tool
Product
Keywords
SWITCH,pre-execute,deploy-shadow,start-shadow-instance-dm,com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService,class com.sap.sdt.util.diag.DiagException, START-SHADOW-INSTANCE-DM BootStrap failed JLoad error , KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.