This page is to explain the steps on how to perform checks if the SAP HANA instance is not starting. At the end of this guide, there will be frequently asked questions and common problems that are encountered.
Transparent Huge Page:
1890444 - Slow HANA system due to CPU power save mode
Extremely High Memory consumption
When you run into system hang Situation please do not restart the Database.
Instead please take a look into SAP Note: 1813020 - How to generate a runtime dump on SAP HANA
Generate 3 to 5 dumps on about 30 seconds part.
Take a look into these dumps to find out which allocator is taking up the most memory.
Look at SAP Note 1999997 - FAQ: SAP HANA Memory under Q13 for a list of allocator list and their purpose.
CPU maxed out
ISSUE: All CPU cores are completely used system wide
1. Check to see if it's HANA process that is consuming most of the CPU.
2. If it is, trigger runtime dump from hdbcons, or use OS tool gstack to trigger thread dump.
3. If it is not, consult with customer DB admin to see if that process can be terminated or restarted.
File System errors
HANA internal thread deadlock
It is possible due to programming error, that HANA's internal threads deadlocked (request handlers), which makes the system appear to hanging and not receiving any request.
This is not the deadlock situation caused by transactions locks, which can be resolved automatically by the database.
Run Time Dumps needs to be collect for fix identification.
Related SAP Notes/KBAs
SAP Note 1732157 - Collecting diagnosis information for SAP HANA
SAP Note 2083715 - Analyzing log volume full situations
SAP Note 1788692 - Index Server crash due to missing LogSegment file