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

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects. Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...

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...

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...

Deploying SAP on Google Cloud : Part 1

Connect to Google Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...

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...

EIENTRA

Search This Blog