Wednesday, 8 November 2017

Error in SAP Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started within the instance


Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started in the instance

Symptom:

During the execution of Software Provisioning Manager tool (SWPM), the tool fails with the following error:

sapinst_dev.log
ERROR     

Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started within the instance.

Resolution:

1. Stop the SWPM tool;

2. Stop the instance (in case it is not stopped already);

3. Make sure sapstartsrv command is not running for the instance. It can be done by running the command:

Example: 

$ ps -ef | grep sapstartsrv
sapadm   4199       1  0 Jan27 ?   00:10:11 /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D

abcadm   5375       1  0 Apr29 ?   00:08:43 /usr/sap/ABC/DVEBMGS00/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_DVEBMGS00_host -D

abcadm  19285       1  0 Jun15 ?   00:01:19 /usr/sap/ABC/SCS02/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_SCS02_host -D

abcadm  23002       1  0 May25 ?   00:03:53 /usr/sap/ABC/ASCS01/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_ASCS01_host -D

abcadm  23005 23706 0 12:52 pts/0  00:00:00 grep sapstartsrv


The first and last lines can be ignored. The first one is the sapstartsrv for the hostctrl, which is not relevant for the issue. The last line is the output for grep command.
Then, there are 3 sapstartsrv running for each instance of the system. Manually stop the process of the instance with issues.

Check if the file /usr/sap/sapservices exists on your system, otherwise create it as described in SAP Note 823941;

Confirm if your system uses start profile or only instance profile;

If it has start profile, then make sure all sapstartsrv commands are pointing to the start profile. In addition, make sure all startup commands showed in the Cause section properly exist into start profile;

If the start profile does not exist on your SAP system, then make sure that all startup commands are properly set for instance profile.

Start the instance once again;

For a test purpose, run the command below. It must return the process below listed.

/usr/sap///exe/sapcontrol -prot NI_HTTP -nr -function GetProcessList

If the output lists the processes status (like example below), it means it has worked and now you can run SWPM tool once again to continue the process.

/usr/sap/ABC/ASCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function GetProcessList

GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GREEN, Running, 2015 06 04 21:01:45, 482:39:35, 8452
enserver, EnqueueServer, GREEN, Running, 2015 06 04 21:01:46, 482:39:34, 8488

In case the issue remains and you require further assistance from BC-INS experts, provide the following information:

output of command /usr/sap///exe/sapcontrol -prot NI_HTTP -nr -function GetProcessList in a text file;
/usr/sap/sapservices file;
output of command ps -ef | grep sapstartsrv in a text file;
sapinst_dev.log;
control.xml;
summary.html;
keydb.xml
entire /usr/sap//SYS/profile directory;
entire /usr/sap///work directory


OR

Clean the shared memory in instance

Run the Command

cleanipc  remove  

XX your instance number

both DB and APP instance now you can continue the installation.






EmoticonEmoticon

Note: only a member of this blog may post a comment.