Skip to end of metadata
Go to start of metadata

How to check the sapstartsrv release and patch level?

There are different ways to get the kernel release and patch level of sapstartsrv:

sapcontrol web method "GetVersionInfo"

110> sapcontrol -nr <instance number> -function GetVersionInfo

06.08.2015 15:09:33
GetVersionInfo
OK
Filename, VersionInfo, Time
/usr/sap/<SID>/ASCS01/exe/sapstartsrv, 742, patch 101, changelist 1567027, RKS compatibility level 0, optU (Mar 24 2015, 16:19:18), linuxx86_64, 2015 03 24 16:01:42

Strings command

Windows

C:\>strings sapstartsrv.exe | findstr changelist

#[%]SAPProductVersion: 741, patch 201, changelist 1568441

UNIX

> strings sapstartsrv | grep changelist

#[%]SAPProductVersion: 742, patch 101, changelist 1567027

getsapversion command

getsapversion sapstartsrv  

#File Version: 7770, 200, 30, 36697
Product Version: 777, patch 200, changelist 2002777
Platform: linuxx86_64
Special Build Description: optU (Jun 12 2020, 21:24:47)
Compatibility Level: 0

What it the goal of history.glf log file?

This file belongs to the sapstartsrv service. It is possible to find it over DIR_HOME folder. The goal of the file is to record the history events of some specific sapstartsrv methods.

The execution of following methods are currently rocorded into the history.glf file:

Start

Stop2

RestartInstance

RestartService

StopService

StartSystem

StopSystem

RestartSystem

UpdateSystem

UpdateSCSInstance

If the log file does not exist, the sapstartsrv create it during the startup. If the file exist, however header is corrupted or in a non-recognized way, the file is recreated by sapstartsrv. Otherwise the old file remains.

The content of the file is something similar to:

> cat history.glf

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

ENCODING:UTF8

RECORD_SEPARATOR:10

COLUMN_SEPARATOR:9

ESC_CHARACTER:0

COLUMNS:Severity|Time|Text

SEVERITY_MAP:Info|Information|Warning|Warning|Error|Error

HEADER_END

Info 2015 09 14 23:13:26 Logfile created

Info 2015 09 14 23:13:26 SAP-StartService started

Info 2015 09 14 23:16:27 Restart service by user "<user who trigger the method>" from "<IP> / <hostname>"

Info 2015 09 14 23:16:30 SAP-StartService started

How to add a new system on SAP MMC?

The SAP Snap-In for Microsoft Management Console (MMC) provides a graphical user interface to administer SAP systems from Windows PCs. It is installed with any SAP application server on Windows by default.
The default configuration allows you to administer any locally installed SAP application server. See fully details on this wiki page: SAP MMC Snap-In


In case you want to add a new system to monitor with SAP MMC, follow these steps:
- Open the SAPMMC window:

- Select ‘SAP System’, click on right button and Press ‘Properties’:

- Go to tab ‘Fixed’ and fill areas.
System: you should enter here SystemID (SID) from the system you want to add to SAPMMC
Instance: Enter here application server hostname (<hostname>) and instance number (<$$>) for that system.
Afterwards, press ‘>> Add >>’ and you should see that system under Fixed instance list white box.

Then, click OK.
- Finally, you should be able to see SAP system on SAPMMC window:


Under "Options" in the "General" tab there are "Always show local SAP instnaces" and "Always show all SAP insnaces of SAP systems", both are enabled by default. They make it easier to use SAP MMC:

1."Always show local SAP instances" automatically add all instances running of the server where you start SAP MMC
2."Always show all SAP instances of SAP systems" will query sapstartsrv of one of the instances via "GetSystemInstanceList" for a complete list of instances of the systems
This make it easier to administer huge systems or systems with varying number of instances.


The entries under a System id are the result of running : "sapcontrol -nr <instance number> -function GetSystemInstanceList"

When running this command the output is taken from file "$(DIR_GLOBAL)\sapcontrol"
Every sapstartsrv registers with its instance name in $(DIR_GLOBAL)/sapcontrol and updates its information every 60 seconds

SAP MMC can be used to perform many different administration actions over SAP system, such as Start or Stop it (click on <SID> with right button > All Tasks).
You can also Create a Snapshot, this will collect system information and developer traces. Fully details on Note 1786182 - CreateSnapshot: Collecting developer traces using sapcontrol 

See also:
2010805 - SAP MMC common issues
2624443 - [WEBINAR] Understanding SAP Startup Framework
1788704 - sapstartsrv registration in $(DIR_GLOBAL)

How to read Snapshots using SAPMMC or SAP MC

The SAP Microsoft Management Console (MMC) Snap-In gives you the option to create snapshots (ZIP archive with Web service responses) for support purposes that
can later be opened again "offline" using the SAP MMC.

Snapshots are packed as zip archives in the directory:
  $(DIR_GLOBAL)/sapcontrol/snapshots
They can be extracted to a local directory and read into a graphic user interface of SAPMMC and SAP-MC using the following menu path:
  Context menu "SAP Systems" -> "All Tasks" -> "Open Snapshot”


This will take us to the directory where we saved the snapshots:

Then, a new “SAP Systems” tree is created with all the information from the loaded snapshot:


SNAPSHOT viewer can be found on transaction SNAPSHOTS, which contains a list of all the snapshots taken by all the application servers.
They are created under specific circumstances that may need analysis afterwards; such as work process crash, critical resources on the Dispatcher, Queue standstill, or memory shortage situations, for instance.
You can see roughly what was happening in the system, which were the problems at a particular time.


  • No labels