Skip to main content

Must to do before restart after HANA Crash


Full System Information Dump refers to a practice in which, when a critical system is down, instead of immediately restarting it, you first gather and save essential log and trace files. This precaution is taken because restarting a system can overwrite crucial low-level logs or traces, making it harder to analyze the root cause of the issue later on.


SAP HANA supports this process by offering a feature called a full system information dump. With this dump, you can select and save specific logs, allowing you to preserve important information for later troubleshooting. By doing this, you ensure that you have the necessary data to investigate and address the problem effectively after restarting the SAP HANA database.


Additionally, in the Database Directory, you have the option to specify the credentials of the database user needed to access detailed information about an individual database. This step is essential unless a single sign-on mechanism is in place for that particular database.



Steps to do for collecting Full System information dump 


  • Start by locating the Alerts and Diagnostics card.

  • Click on the "Manage full system information dumps" link.

  • Select "Collect Diagnostics" and pick either 


Collect from Existing Files:


Purpose: This option is chosen when you want to gather diagnostic information for specific file types over a defined time period, typically the last seven days by default.

Include System Views: If you wish to include information from system views, you can select the option. However, note that if connected to the system database of a multiple-container system, only information from the system views of the system database is collected. Information from the system views of tenant databases is not collected.

Performance Impact: Collecting information from system views involves executing SQL statements, which might impact system performance. This option is not available in diagnosis mode, and the database must be online for its utilization.


Create from Runtime Environment:


Purpose: This option is selected when you want to limit the information collection to runtime environment (RTE) dump files.

Additional Configuration: You can configure the collection of dump files by specifying the number of sets to be collected, the interval at which RTE dump files are collected, the host(s), service(s), and section(s) from each selected service.

Processing Time: The system collects the relevant information and saves it to a ZIP file. This process may take some time, and it can be allowed to run in the background.

Multiple-Container System: If connected to the system database of a multiple-container system, information from all tenant databases is collected and saved to separate ZIP files.


 

  • In the pop-up window, choose the specific information items you wish to collect. Then, at the bottom-right corner, click on "Start Collecting."

  • Once all the data is gathered, you'll see the "fullsysteminfodump_<SID><DBNAME><HOST>_<timestamp>.zip" file in the collections table.


The other way to collect diagnostic information from command line 


fullSystemInfoDump.py is present in the python support file , We need to add these details when we are asking for support from SAP . The script is part of the SAP HANA server installation and can be executed directly from the command line. 


Command : python  fullSystemInfoDump.py –tenant <SID>


Other options to check :  


→    - - nosql : Excludes  collection of system view

→    - - days=DAYS : Collect trace files from these number of past days 

→    - - help


If the SQL-accessible option is available (with no --nosql specified), the script initiates the gathering of diagnostic information. In cases where SQL access is not possible, the script proceeds to collect support information without exporting data from system views.


Unless the --rtedump option is specified, the script collects all the mentioned file types; otherwise, it exclusively generates and gathers runtime environment (RTE) dump files.


Collecting Diagnostic file : https://me.sap.com/notes/1732157


Information that is collected in fullSystemInfoDump.py :  


Information is saved here : $DIR_GLOBAL/sapcontrol/snapshots. $DIR_GLOBAL typically points to /usr/sap/ /SYS/global.


Log file 

All information about what has been collected is shown as console output, and is written to a

file named log.txt, which is stored in the ZIP file.

Trace file 

Trace file for each host in the landscape $DIR_INSTANCE/<SAPLOCALHOST>/trace/


compileserver_alert_<SAPLOCALHOST>.trc

compileserver_<SAPLOCALHOST>.<...>.trc

daemon_<SAPLOCALHOST>.<...>.trc

indexserver_alert_<SAPLOCALHOST>.trc

indexserver_<SAPLOCALHOST>.<...>.trc

nameserver_alert_<SAPLOCALHOST>.trc

nameserver_history.trc

nameserver_<SAPLOCALHOST>.<...>.trc

preprocessor_alert_<SAPLOCALHOST>.trc

preprocessor_<SAPLOCALHOST>.<...>.trc

statisticsserver_alert_<SAPLOCALHOST>.trc

statisticsserver_<SAPLOCALHOST>.<...>.trc

xsengine_alert_<SAPLOCALHOST>.trc

xsengine_<SAPLOCALHOST>.<...>.trc


Database System Log File 

$DIR_INSTANCE/<SAPLOCALHOST>/trace/backup.log

$DIR_INSTANCE/<SAPLOCALHOST>/trace/backint.log


Database Configuration File

$DIR_INSTANCE/<SAPLOCALHOST>/exe/config/


compileserver.ini

daemon.ini

executor.ini

extensions.ini

filter.ini

global.ini

indexserver.ini

inifiles.ini

localclient.ini

mimetypemapping.ini

nameserver.ini

preprocessor.ini

scriptserver.ini

statisticsserver.ini

validmimetypes.ini

xsengine.ini

crashdump file , record performance trace file 

Crashdump files for services are collected unabridged.


Performance trace files with the suffix *.tpt are collected unabridged.

Runtime dump for each index server 

For each index server, an RTE dump file containing information about threads, stack contexts,

and so on is created and stored in the file

indexserver_<SAPLOCALHOST>_<PORT>_runtimedump.trc.


Performance Trace Files

Performance trace files with the suffix *.tpt are collected unabridged

Kerberos Files



/etc/krb5.conf

/etc/krb5.keytab


System Views

Only the first 2,000 rows are exported.


SYS.M_CE_CALCSCENARIOS WHERE SCENARIO_NAME LIKE '%_SYS_PLE%'

SYS.M_CONNECTIONS with CONNECTION_ID > 0

SYS.M_DATABASE_HISTORY

SYS.M_DEV_ALL_LICENSES

SYS.M_DEV_PLE_SESSIONS_

SYS.M_DEV_PLE_RUNTIME_OBJECTS_

SYS.M_EPM_SESSIONS

SYS.M_INIFILE_CONTENTS

SYS.M_LANDSCAPE_HOST_CONFIGURATION

SYS.M_RECORD_LOCKS

SYS.M_SERVICE_STATISTICS

SYS.M_SERVICE_THREADS

SYS.M_SYSTEM_OVERVIEW

SYS.M_TABLE_LOCATIONS

SYS.M_TABLE_LOCKS

SYS.M_TABLE_TRANSACTIONS

_SYS_EPM.VERSIONS

_SYS_EPM.TEMPORARY_CONTAINERS

_SYS_EPM.SAVED_CONTAINERS

_SYS_STATISTICS.STATISTICS_ALERT_INFORMATION

_SYS_STATISTICS.STATISTICS_ALERT_LAST_CHECK_INFORMATION

_SYS_STATISTICS.STATISTICS_ALERTS

_SYS_STATISTICS.STATISTICS_INTERVAL_INFORMATION

_SYS_STATISTICS.STATISTICS_LASTVALUES

_SYS_STATISTICS.STATISTICS_STATE

_SYS_STATISTICS.STATISTICS_VERSION




topology.txt

All available topology information is exported to a file named topology.txt. It contains

information about the host topology in a tree-like structure.


Contains following information : nameserver role , Available database , Host , HANA build time and version , Number of CPUs and CPU type , Used Crypto library , Hardware Manufacturer , Amount of memory and swap , Network information , Important Linux parameter , OS provider , SAP HANA SID and instance number , Timezone 





When connected to the system database of a multiple-container system, the script exclusively collects information from the system views of the system database. Irrespective of the option setting, no information from the system views of tenant databases is gathered.


After collecting the dumps then only restart the Hana Database 


Comments

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set