Skip to Content
0

SAP system stating and stopping history

Apr 05, 2017 at 07:17 AM

89

avatar image
Former Member

Dear Support

its urgent

I want to ask you that how we identify about sap system when its stop or started

and I want to get list of 60 days logs in which its shows how many times system restarted sap database system

thank you

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

avatar image
Former Member Apr 05, 2017 at 12:55 PM
0

There are many manual and automatic ways of tracking this, but one of the simplest, yet most accurate, for an SAP system is the available.log.

available.log is stored in the work directory (/usr/sap/<sid>/work).

The information is checked and updated every 60 sec and at instance startup and shutdown. The default threshold for a “good” dialog time is 5.0 sec. You can adjust this threshold with the profile parameter max_dia_queue_time in the default or start profile (service must be restarted after changing it).

Share
10 |10000 characters needed characters left characters exceeded
Raquel Gomez
Apr 12, 2017 at 03:38 PM
0

Hi Syed,

You can use dispatcher trace file (dev_disp) to check server availability. It's located also under work directory (/usr/sap/<SID>/work).

On the trace file, you will see timestamp at the begining when aaplication server was last started:

Day Month <nr> xx:xx:xx 2017
........
***LOG Q00=> DpSapEnvInit, DPStart (xx xxxx) [dpInit.c 548]

Old dispatcher trace file (dev_disp.old) will show previous application server start and stop.


You can also check on transaction ST02 when was last application server restart.
Startup: xx.xx.2017 xx:xx:xx


Regarding SystemLog entries (transaction SM21) this also gives you a general overview of the server status each moment.
There, you can also find when aaplication server was stopped/started.

You can see how work processes are stopped, disconnection to Message Server done, and server stopped:
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DIA |<nr> | | | |Q02 Stop Workp. <nr>, PID 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DIA |<nr> | | | |Q02 Stop Workp. <nr>, PID 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DIA |<nr> | | | |Q02 Stop Workp. <nr>, PID 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DP |000 | | | |Q0M Message server disconnected
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DP |000 | | | |Q05 Stop SAP System, Dispatcher Pid 1234

Afterwards, you should be able to see how work processes are started, connection to Message Server stablished again and server started (steps performed in the opposite way):

|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DP |000 | | | |Q00 Start SAP System, SAPSYSTEM <nr>, Dispatcher Pid 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|DP |000 | | | |Q0K Connection to message server (on <hostname>) established
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|WRK |<nr> | | | |Q0Q Start Workp. <nr>, PID 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|WRK |<nr> | | | |Q0Q Start Workp. <nr>, PID 1234
|xx.xx.2017|xx:xx:xx|<server>_<SID>_<nr>|WRK |<nr> | | | |Q0Q Start Workp. <nr>, PID 1234

Regards,
Raquel

Share
10 |10000 characters needed characters left characters exceeded