header
stringlengths 12
160
| content
stringlengths 15
265k
|
|---|---|
## 1 SAP HANA Troubleshooting and Performance Analysis Guide
|
## 1 SAP HANA Troubleshooting and Performance Analysis Guide
With SAP HANA, you can analyze data at incredible speeds, for example, with scans of 1 billion rows per second per core and join performance of 10 million rows per second. However, such results are only possible if the system is monitored and performance issues are kept to a minimum.
This guide describes the measures you can take to identify and resolve specific issues and shows you how to enhance the performance of your SAP HANA database in the following areas:
- Host resources (CPU, memory, disk)
- Size and growth of data structures
- Transactional problems
- SQL statement performance
- Security, authorization, and licensing
- Configuration.
A separate guide aimed at developers is available, focusing on performance issues and steps you can take to enhance the performance of your SAP HANA database: SAP HANA Performance Guide for Developers.
## Prerequisites
- This guide assumes knowledge of the relevant functionality of the SAP HANA database (knowledge which can be gained from HANA training courses such as HA100, HA200).
- Access to the administration tool SAP HANA cockpit (or alternatively SAP HANA studio) is required.
## Overview
## Analyzing Generic Symptoms
This section of the troubleshooting guide helps you to find out about causes of generic problems such as:
- slow system-wide performance
- slow individual SQL statements
- frequent out-of-memory (OOM) situations
Furthermore, you are directed to sections of this guide that contain more specific root causes.
SAP Note references lead you to possible solutions.
Analyzing Generic Symptoms [page 8]
## Root Causes & Solutions
In this section of the troubleshooting guide you find concrete root causes for problems together with possible solutions. Some of the areas covered are:
- Memory Problems
- CPU Related Root Causes and Solutions
- License Issues
- Statement Performance Analysis
You may find the SAP Notes very useful for solving your issue as they contain detailed explanations and step-by-step instructions, for example.
Root Causes and Solutions [page 65]
## Tools and Tracing
This section of the troubleshooting guide presents monitoring tools which can be used for analyzing and tracing certain issues.
## Tools and Tracing [page 237]
Apart from those more specific monitoring tools discussed here, there are important tools for administrators and developers in general:
- SAP HANA cockpit
Tip
For the documentation of the latest SAP HANA cockpit support package (SP), see https:// help.sap.com/viewer/p/SAP_HANA_COCKPIT
- SAP HANA database explorer SAP HANA Database Explorer
- SQL analyzer Analyzing Statement Performance
- Support Log Assistant
The Support Log Assistant is a tool that allows you to automatically scan and analyze text files such as logs, configuration files or traces. The tool will then suggest solutions to known issues found in the files and highlight important details that it finds. The tool is integrated into the incident logging procedure and is also available as a standalone tool; the following link is to a Support Portal getting started page which also gives direct access to the Support Log Assistant.
Support Log Assistant
## Alerts
Alert checkers run in the background and you are notified in case of potentially critical situations arising in your system. In the SAP HANA cockpit, you can easily see in which areas you might need to take some action.
Alerts Reference [page 302]
## SAP Notes
SAP Notes are used to give detailed supplementary customer support information in addition to the formal set of published documents. This troubleshooting guide includes many references to relevant SAP Notes. The
Alerts reference section, for example, gives links to corresponding notes for each system alert. Some other FAQ-format SAP Notes which you may find useful are listed here:
- SAP Note 2000003 - FAQ: SAP HANA
- SAP Note 1999997 - FAQ: SAP HANA Memory
- SAP Note 2186744 - FAQ: SAP HANA Parameters
## Guided Answers
Guided Answers is an interactive online support tool to help users to diagnose and solve problems using decision trees. It covers many SAP products including SAP HANA and offers a set of step-by-step problemsolving online documents each one designed to address a specific topic. Guided Answers is available in the SAP Support portal at the following address:
https://ga.support.sap.com/dtp/viewer/
This troubleshooting guide includes links to specific trees where relevant. The following tree is a general high-level troubleshooting tree for SAP HANA:
https://gad5158842f.us2.hana.ondemand.com/dtp/viewer/#/tree/1623/actions/21021
## Further Resources
The following SAP HANA documents are important resources for working with SAP HANA and are often referred to in this guide:
- SAP HANA Administration Guide
- SAP HANA SQL and System Views Reference
In particular, the SAP HANA Administration Guide gives general details on using the administration tools SAP HANA cockpit and SAP HANA studio.
There is a central online portal for a variety of support resources for SAP products which is available from the SAP ONE Support Launchpad Software Downloads : https://launchpad.support.sap.com/#/ softwarecenter
In the SAP Community Network (SCN) you can find many support resources online including wikis, blogs, reference materials and so on. This SCN wiki page, for example, provides links to many specialist topics: SAP HANA In-Memory Troubleshooting Guide .
Both SAP HANA Academy and SAP Support offer Y ouT ube channels with a wide range of support materials in video format:
- https://www.youtube.com/user/saphanaacademy
- http://www.youtube.com/user/SAPSupportInfo
|
## 2 Analyzing Generic Symptoms
|
## 2 Analyzing Generic Symptoms
The purpose of this section of the document is to help you to find the probable root cause of some generic problems and refer you to more detailed sections of the SAP HANA Troubleshooting and Performance Analysis Guide to proceed with your analysis.
Performance issues may be difficult to diagnose; problems may be rooted in a number of seemingly unrelated components. Checking for system alerts is a good starting point if you experience any trouble with your SAP HANA system. If the system issues an alert, refer to the Reference: Alerts section to find the part of this guide, an SAP Note or Knowledge Base Article which addresses the problem.
However, alerts are configurable (see Memory Problems for information on configuring alerts) and do not cover all aspects of the system, problems can still occur without triggering an alert. This section therefore describes some generic symptoms which you may observe and helps you to analyze the underlying problem.
## Related Information
Memory Problems [page 65] Alerts Reference [page 302]
|
## 2.1 Using the SQL Statement Collection for Analysis and Health Checks
|
## 2.1 Using the SQL Statement Collection for Analysis and Health Checks
A collection of predefined customizable statements is available for checking the database.
An extensive SQL statement collection is available for analyzing the SAP HANA database, this can be used to examine specific problems or for routine monitoring. The script collection is available in a zip file attached to the SAP Note 1969700 SQL Statement Collection for SAP HANA . Several scripts are referred to in this Troubleshooting Guide but a general starting point for system analysis is to check the overall health of the SAP HANA database by running the script HANA_Configuration_MiniChecks as illustrated below.
## Identify the Correct Version of a Script
Many of the statements are version specific, you must therefore choose the correct version of the script for the version and database revision of SAP HANA you are running. For example, if you are on SAP HANA 2.00.023 and script versions 2.00.000+, 2.00.010+, and 2.00.030+ are available, you should use the 2.00.010+ version. Script versions for earlier releases than your database release are expected to work, but you should avoid using script version for SAP HANA releases later than the release you are using. They may describe monitoring views or columns not yet available with your SAP HANA version.
## Modify a Script
Where relevant, the SQL support scripts contain sections which can be customized to enter your own parameter values, these are marked with the comment ' /* Modification section */ '. For example:
```
( SELECT /* Modification section */ '%' HOST, '%' PORT, '%' OBJECT_TYPE, ... )
```
If you want to analyze a specific time range, you can modify the time parameters using the codes described in the comment block of the script, in the section INPUT_PARAMETERS . Y ou can use 'C-H12' BEGIN_TIME , or you can enter a specific date and time.
To do this, in place of 'C-H12' BEGIN_TIME and 'C' END_TIME , enter the date and time you want to analyze, in the format 'YYY/MM/DD HH24:MI:SS' .
Example: To check for transaction lock waits that happened between 19/08/2022 at 2pm and 20/08/2022 at 2pm, the modification part of the script would look like this:
```
SELECT Modification section 2022/08/19 2022/08/20 SERVER, UTC SITE_Id, HOST , SERVICE_NAME ,
```
## Script HANA_Configuration_MiniChecks
The output of the HANA_Configuration_MiniChecks script is illustrated here; the output report gives an overview of the overall health of the SAP HANA database. The report covers various aspects of the system including Memory, CPU, I/O, locks and other issues that may cause a performance problem. If a potentially critical issue is found the column 'C' is marked with an 'X' . The last column of the report references relevant SAP notes or Knowledge Base Articles that will help you to resolve the issues.
Example Output of the Configuration_MiniChecks Script
## Related Information
SAP Note 1969700
|
## 2.2 Handling SQL Errors
|
## 2.2 Handling SQL Errors
Errors generated when executing SQL statements are identified by a code number which may be helpful to find an explanation and solution to the problem.
This section gives some recommended solutions to help solve problems related to SQL errors. The topic which follows 'SQL Error Reference' is a table of error codes which includes links to other sources of information for many of the most frequently occurring errors.
Error messages returned when executing SQL statements are identified by a number, type and description, for example:
ERROR [SQL-608] exceed maximum number of prepared statements
There are currently over 5700 SQL errors; all error codes and types are listed in the monitoring view m_ERROR_CODES. To get a complete list of errors and their descriptions you can execute the following query:
```
SELECT * FROM M_ERROR_CODES ORDER BY CODE ASC;
```
All SQL error messages are also listed in the help topic 'SQL Error Codes' in the SAP HANA SQL Reference Guide for SAP HANA Platform (link in Related Information below).
## Knowledge Base Search
You can search for existing support documentation on a specific error in the SAP HANA Support Knowledge Base and the SAP Support community (see links in Related Information below). For example, the search results for the description of the SQL-608 error given above includes references to many HAN-DB (SAP HANA Database) knowledge base articles such as:
- 2464140 - Longer running realtime replication may provide errors like "exceed maximum number of prepared statements"
- 2154870 - How-To: Understanding and defining SAP HANA Limitations
SQL errors may also be related to third party SAP tools, middleware or application clients that use HANA, and information may therefore be available under other component IDs (not only 'HAN-DB*'). The following error, for example, may occur in the context of 'SAP Access Control 12.0' between SPRO and HANA:
```
ERROR_CODE : 4.229 - ERR_PROVIDER_INVALID_PROVIDER_NAME - 'Invalid provider name'
```
The following KBA (under the component Access Request GRC-SAC-ARQ ) may be relevant but may not be immediately visible in the search results:
- 3002042 - Invalid provider name: 'SAP_PI_GRC'.'Create_User': line xx col xx (at pos xx): line x col xx (at pos xx)
If no solution can be found you may need to open a support ticket under the HAN-DB* component with the example system trace files, logs and screenshots of the error(s) for further analysis.
## Search Trace Files
You can also search the HANA service trace and service alert files (see also 'Analyzing SQL Traces') for example: 'indexserver_saphana01.30003.024.trc', 'indexserver_alert_saphana01.trc'.
For errors in BW on HANA, the values of the following transaction codes may also be helpful:
- The ABAP Dumps in transaction code ST22
- The work process trace entry from transaction code ST11
The following articles may also be helpful when analyzing trace files:
- 2194685 - How to find work process trace for SM21 System Log or ST22 dump
- 2380176 - FAQ: SAP HANA Database Trace
- 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANA Environments
## Related Information
SQL Error Codes (SAP HANA SQL Reference Guide)
SQL Error Reference [page 12] Analyzing SQL Traces [page 238] SAP HANA Support Knowledge Base
## Links to Knowledge Base Articles :
SAP Note 2194685
SAP Note 2380176
SAP Note 2399990
SAP Note 2464140
SAP Note 2154870
SAP Note 3002042
|
## 2.2.1 SQL Error Reference
|
## 2.2.1 SQL Error Reference
The following reference table provides links to sources of troubleshooting information for many frequently occurring SQL errors.
SQL Error Codes
| Code | Type | Description | More information |
|--------|---------------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 4 | FATAL_OUT_OF_MEMORY | Cannot allocate enough memory | This error indicates an out-of-memory (OOM) situation. - KBA 1999997 - FAQ:SAPHANA Memory |
| 7 | ERR_FEATURE_NOT_SUPPORTED | Feature not supported | Commonpreamble to a more detailed error. Please review the error detail following the pre- amble "feature not supported: ...." and search the SAP HANAKnowledge base for existing Knowledge based articles and SAP Notes. Some examples: 2970997 - feature not supported: Invalid op- tions 2804287 - feature not supported: Create da- tabase command on SYSTEMDB only 2870701 - Error "feature not supported: global temporary table must be empty to drop" 2661916 - feature not supported: Snapshot backup not supported on a tenant database 2710915 - feature not supported: move with- out partition not allowed on partitioned table |
| 8 | ERR_INV_ARGUMENT | Invalid argument | 3104969 - DBSQL_SEMREQ_ERROR. 22 In- valid argument. (Internal KBA) |
| 10 | ERR_AUTHENTICATION_FAILED | Authentication failed | This error indicates a failure during user authen- tication - (See KBA 2399990 ) See section '11. How can tracing be activated for security topics like authorization, authentication and login?' - 2159014 - FAQ: SAP HANASe- curity |
| 11 | ERR_INV_STATE | Invalid state | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments. |
| 12 | ERR_FILE_OPEN_FAILED | Cannot open file | Issue with a backup file in the backup catlog or a data / redo log file in the persistence directory on the HANAdata and log volumes. Check the underlying HANAservices that use persistence and their trace files for more information on the error. |
| 15 | ERR_FILE_NOT_FOUND | Cannot find file | Typically an issue with a third party backint tool: 2801380 - ERROR: [110063] The backup destination header is corrupt 2541007 - Not able to restore database from Symantec NetBackup if the backup file name contains square brackets |
| 18 | ERR_SERVICE_SHUTDOWN | Service shutting down | Indicates that a HANAservice has been sent a shutdown command either manually from <sid>adm, or a parent process like the sap- start service, daemon or nameserver. Check the HANAservice trace files for the events leading up to the error. |
| 19 | ERR_INV_LICENSE | Invalid license | 19: invalid license' is described in more detail in SAP KBA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 20 | ERR_CON_OUTSIDE_VALID- ITY_PERIOD | Connect attempt out- side user's validity pe- riod | Connect attempt outside user's validity peri- od' is described in more detail in SAP KBA 2380176 - FAQ: SAP HANADatabase Trace |
| 21 | ERR_PERSISTENCE | Persistence error | Persistence error' is described in more detail in SAP KBA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 128 | ERR_TX | Transaction error | SQL error 128: transaction error: exceed maxi- mumnumberof transactions' is described in further detail in KBA 2154870 - How-To: Un- derstanding and defining SAP HANALimitations |
| 129 | ERR_TX_ROLLBACK | Transaction rolled back by an internal error | This is a quite generic message that something went wrong and the transaction had to be rolled back. Check the HANAservice trace files for related detailed error messages. |
| 131 | ERR_TX_ROLLBACK_LOCK_TIME- OUT | Transaction rolled back by lock wait timeout | SAP KBAs: 3066406 - SQL code: 131" occurred while accessing table 1999998 - FAQ: SAP HANALock Analysis 2380176 - FAQ: SAP HANADatabase Trace |
| 132 | ERR_TX_ROLLBACK_RESOURCE | Transaction rolled back due to unavailable re- source | SAP KBAs: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2154870 - How-To: Understanding and defin- ing SAP HANALimitations |
| 133 | ERR_TX_ROLLBACK_DEADLOCK | Transaction rolled back by detected deadlock | This type of short dump indicates a deadlock, so a cross-wise transactional lock. In most cases deadlocks are caused by inadequate application coding that results in risk of cross-wise locking of different transactions. See 1999998 - FAQ: SAP HANALock Analy- sis |
| 138 | ERR_TX_SERIALIZATION | Transaction serializa- tion failure | This error indicates that a retry for a database request was triggered, but the request is not retriable. This trace error can be linked to "138: trans- action serialization failure: Serialization failure" errors observed on client side (SAP KBA 2399990 ) |
| 139 | ERR_TX_ROLLBACK_QUERY_CAN- CEL | Current operation can- celed by request and transaction rolled back | SAP Note 2931813 - Memory Related Error or Warning Trace Messages when Cancelling a Query |
| 142 | ERR_TX_EXCEED_MAX_TX_NUM | Exceedmaxnum of concurrent transac- tions | This error is generated if the limit of configured external connections is reached. See SAP KBAs: 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 1910159 - How to handle HANAAlert 25: 'Check number of connections' |
| 144 | ERR_TX_ROLLBACK_UNIQUE_VIO- LATED | Transaction rollback unique constraint vio- lated | See '19. Which error messages exist in the con- text of indexes?' - 2160391 - FAQ:SAPHANA Indexes |
| 145 | ERR_TX_DIST_FAILURE | Transaction distribu- tion work failure | Multiple , generic causes. See KBAs: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 146 | ERR_TX_LOCK_ACQUISITION_FAIL | Resource busy and NOWAIT specified | This error indicates that an operation is per- formed with a NOWAIT option and so it termi- nates immediately in case the transactional ob- ject or record lock can't be acquired. See KBAs for more information: 1999998 - FAQ: SAP HANALock Analysis 2380176 - FAQ: SAP HANADatabase Trace |
| 149 | ERR_TX_DIST_2PC_FAILURE | Distributed transaction commit failure | This error indicates major problems on server side, so the SAP HANAdatabase should be in- vestigated. |
| 154 | ERR_TX_INDEX_HANDLE_AC- QUISITION_FAIL | failure in acquiring in- dex handle | This error indicates an index handle contention issue (SAP Note 1999998 ) accessing a mon- itoring view like M_CS_NSE_ADVISOR. SAP Note - 3125519 - Querying M_CS_NSE_ADVISOR Might Fail and Not Pro- duce Any Recommendation |
| 256 | ERR_SQL | sql processing error | [256]: sql processing error:' is a generic error and needs further investigation via theHANA service traces. 2073630 - DBIF_RSQL_SQL_ERROR SQL er- ror 256 when access table 2380176 - FAQ: SAP HANADatabase Trace |
| 257 | ERR_SQL_PARSE | sql syntax error | This error indicates a wrong syntax and you need to check the related SQL statement for correctness. In rare cases the issue can also be a conse- quence of problems on lower layers (infrastruc- ture / hardware) erroneously modifying SQL statement strings. SAP KBA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 258 | ERR_SQL_INSUFF_PRIV | insufficient privilege | Authorization / permission problems. This ter- mination indicates missing privileges. Make sure that proper roles and privileges are assigned. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2159014 - FAQ: SAP HANASecurity |
| 259 | ERR_SQL_INV_TABLE | invalid table name | This error indicates that the table or view <ob- ject> isn't found. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 260 | ERR_SQL_INV_COLUMN | invalid column name | This error indicates that column <column> doesn't exist in table <table> and so the da- tabase operation <op> (e.g. 'INS' for INSERT) fails. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 261 | ERR_SQL_INV_INDEX | invalid index name | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2142945 - FAQ: SAP HANAHints 2800008 - FAQ: SAP HANAFulltext Indexes |
| 262 | ERR_SQL_INV_QUERY | invalid query name | ODBC_SQL* queries are built-in database quer- ies (installed when the SAP HANAdatabase is created) that are used for certain ODBCdriver related actions, e.g. ODBC_SQL_COLUMNS for retrieving column metadata. The error indicates that the query isn't available. Check why it is missing or not properly accessible. |
| 264 | ERR_SQL_INV_DATATYPE | invalid datatype | 21. Are there restrictions in processing LOB col- umns?' - 2220627 - FAQ:SAPHANALOBs 2222219 - SAP HANAErrors and different Results due to Design Changes 2765864 - Update Statement Fails With Er- ror "invalid datatype: $rowid$ of invalid data types" |
| 266 | ERR_SQL_INCNST_DATATYPE | inconsistent datatype | 2486755 - "inconsistent datatype: lob type comparison" when selecting from a column with typeTEXT-HANADB 2222219 - SAP HANAErrors and different Results due to Design Changes |
| 268 | ERR_SQL_AMBG_COLUMN | column ambiguously defined | 2695943 - SQL failed with error "column am- biguously defined" 2552712 - The Error "column ambiguously defined" May Occur When a Statement is Exe- cuted |
| 269 | ERR_SQL_MANY_VALUES | too many values | This error indicates that a database operation is executed with a wrong number of arguments, e.g.: SAP KBA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 270 | ERR_SQL_FEW_VALUES | not enough values | This error indicates that a database operation is executed with a wrong number of arguments, e.g.: SAP KBA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 272 | ERR_SQL_DPLC_COLUMN | duplicate column name | Column name already exists in the table |
| 274 | ERR_SQL_INS_LARGE_VALUE | inserted value too large for column | This error indicates that a value was inserted in a column that is larger than the maximum column value size, e.g.: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2222219 - SAP HANAErrors and different Results due to Design Changes 3018823 - Inserted Value Too Large For Col- umn 2725050 - SqlScript Execution Fails With "[274]: inserted value too large for column" |
| 286 | ERR_SQL_LONG_IDENTIFIER | identifier is too long | Identifier are names for SAP HANAobjects like table, column or user. 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2170441 - Query on SDA object fails with Er- ror "ORA-00972: identifier is too long" |
| 287 | ERR_SQL_NOT_NULL | cannot insert NULL or update to NULL | This error happens when a NULL value is in- serted into a column that doesn't allow NULL values, e.g. because of a NOTNULLor primary key constraint. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 288 | ERR_SQL_EXST_TABLE | cannot use duplicate table name | 2800007 - FAQ: SAP HANATemporary Ta- bles 2562930 - SAP HANALocal Temporary Ta- ble existence boundaries |
| 292 | ERR_SQL_FEW_ARGUMENT | wrong number of argu- ments | This error indicates that a database operation is executed with a wrong number of arguments, e.g.: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 293 | ERR_SQL_INV_ARGUMENT | argument type mis- match | Can occur during catalog consistency checks and during HANservice removal from the topol- ogy: 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions 2342394 - Unable to remove additional index server 2504698 - Removing additional indexserver services fails with error on a SAP HANAsystem |
| 301 | ERR_SQL_UNIQUE_VIOLATED | unique constraint vio- lated | This error indicates that a modification isn't possible because the key already exists. Check the existing unique and primary keys and make sure that duplicates aren't processed. 2380176 - FAQ: SAP HANADatabase Trace 2572224 - How-To: Repairing SAP HANATa- bles 2160391 - FAQ: SAP HANAIndexes |
| 302 | ERR_SQL_INV_CHAR_VAL | invalid CHARor VAR- CHARvalue | This error indicates a wrong character encoding and is typically caused by a data corruption. See SAP Note 2116157 in order to check the consistency of the database (with a particular focus on the table returning the error) and take appropriate actions to repair inconsistencies. |
| 303 | ERR_SQL_INV_DATETIME_VAL | "invalid DATE TIME or TIMESTAMP value" | This error indicates that a value <value> can't be parsed as date, time or timestamp. This problem can be caused by wrong data in under- lying tables or inadequate application design. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2361364 - [303]: invalid DATE, TIME or TIMESTAMP value: search table error: [6931] at- tribute value is not a date or wrong syntax |
| 304 | ERR_SQL_DIV_BY_ZERO | division by zero unde- fined | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2945199 - search table error: [6859] Attribu- teEngine: divide by zero 2548692 - Alert in HANAStudio '[3] 304 division by zero undefined: search table error: [6859] AttributeEngine: divide by zero' |
| 305 | ERR_SQL_SINGLE_ROW | single-row query re- turns more than one row | This termination indicates that more than 1 re- cord is returned although only a single row can be used. It is typically caused by a coding error on application side. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 306 | ERR_SQL_INV_CURSOR | invalid cursor | These termination indicates a lack of memory on SAP HANAserver side. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 307 | ERR_SQL_NUM_OUT_OF_RANGE | numeric value out of range | This termination indicates an overflow while processing decimal numbers. Adjust the appli- cation, data or column precision in order to make sure that overflows no longer happen. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 308 | ERR_SQL_EXST_COLUMN | column name already exists | A CREATE or ALTER statement processing an existing table column may encounter this during a DDL operation. |
| 310 | ERR_SQL_IN_PROC | sql error in procedure | 2647960 - Checks after phase MAIN_NEW- BAS/JOB_RS_DMO_HDB_CONTENT_ACTIVATE were negative for Delivery Unit A2EESNHI_DE- LIVERY_UNIT |
| 311 | ERR_SQL_DROP_ALL_COLUMNS | cannot drop all col- umns in a table | Restriction for issuing a DROPcommandfor all columns in a database table |
| 313 | ERR_SQL_INV_SEQ | invalid sequence | 6. Which problems exist in context of sequen- ces?' - 2600095 - FAQ: SAP HANASequen- ces |
| 314 | ERR_SQL_OVERFLOW_NUMERIC | numeric overflow | This error is returned if you use a higher number precision than defined for the column. Either reduce the precision on application side or in- crease the precision in the database. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 320 | ERR_SQL_LOB_INDEX | cannot create index on expression with data- type LOB | 21. Are there restrictions in processing LOB col- umns?' - 2220627 - FAQ:SAPHANALOBs |
| 324 | ERR_SQL_EXST_SEQ | cannot use duplicate sequence name | 2134323 - Nesting error in SQLRUN_ISU_TRIGGERS: maximum depth 8 |
| 325 | ERR_SQL_ESC_SEQ | invalid escape se- quence | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 328 | ERR_SQL_INV_FUNC_PROC | invalid name of func- tion or procedure | This error indicates that an object (e.g. table) accessed in a database request doesn't exist. Make sure that the application only accesses objects that exist on SAP HANAlevel. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 332 | ERR_SQL_INV_USER | invalid user name | 2433879 - Restricted User getting "Invalid User Name/Password" 2354866 - "Could Not Save the Connection Data; Invalid User Nameor Password" 2506777 - Unable to login after resetting the SYSTEM user's password forHANA 2538907 - Error "Logon to SAP System Host failed" when using updated password to log on HANAsystem 2764976 - 10: authentication failed: ERR_AU- THENTICATION_FAILED SQLSTATE: 28000 |
| 338 | ERR_SQL_ZERO_LEN_NOT_AL- LOWED | zero-length columns are not allowed | HANAdoes not support zero-length columns. 2674281 - Error "SAP DBTech JDBC: [338]: zero-length columns are not allowed:" |
| 339 | ERR_SQL_INV_NUMBER | invalid number | This termination indicates that a number was expected but something else was found. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2972659 - Reason for error "339: invalid number" |
| 340 | ERR_SQL_VAR_NOT_BOUND | not all variables bound | This termination indicates an issue with bind variable processing. See SAP Note 2380176 -> "unbound parameter: <cnt> of <total>, <cnt> out of <total_batch> batches" for more details. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 348 | ERR_SQL_INV_DATETIME_FOR- MAT | invalid datetime format | 2271717 - SAP HANASDA: Error executing query [Oracle][ODBC]Invalid datetime format. 2933606 - SDA Oracle Remote Query Fails With [Oracle][ODBC]Invalid datetime format |
| 349 | ERR_SQL_CREATE_UNIQUE_IN- DEX | cannot CREATE UNIQUE INDEX; dupli- cate key found | 2838779 - Error "duplicate key found" when trying to recreate a missing primary index |
| 359 | ERR_SQL_STR_LENGTH_TOO_LAR GE | string is too long | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2222219 - SAP HANAErrors and different Results due to Design Changes |
| 361 | ERR_SQL_VIEW_UPDATE_VIOLA- TION | data manipulation op- eration not legal on this view | 2738610 - How to truncate or delete rows from sys.table_placement-SAPHANA 2638028 - Behavior Correction of Invalid Up- datable View Creation |
| 362 | ERR_SQL_INV_SCHEMA | invalid schema name | This error indicates that the specified schema name is invalid. Make sure that you specify an existing schema name and that you are author- ized to access the schema. 2535951 - FAQ: SAP HANAUsers and Sche- mas 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 378 | ERR_SQL_INV_COLUMN_VIEW | invalid column view | This error is known in the context of BWtables: 2134076 - Report RS_BW_POST_MIGRA- TION failing after migrating to theSAPHANA database 2315758 - Error 2048 creation of column view failed when executing report RSDDB_LOGI- NDEX_CREATE 2114556 - Error 2999 has occurred in the BWA/SAP HANAserver |
| 382 | ERR_SQL_COLLECT_ALL_VER- SIONS | fail to collect all version garbage | Indicates blcoked garbage collection issues. See KBA 2169283 - FAQ: SAP HANAGarbage Collection |
| 383 | ERR_SQL_INV_IDENTIFIER | invalid identifier | This error indicates that a wrong identifier was used. Check the related SQL statement for cor- rectness. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2572224 - How-To: Repairing SAP HANATa- bles 2160391 - FAQ: SAP HANAIndexes 2606638 - How to deal with error "invalid identifier: _sys_ prefix not allowed" 2728304 - "ALTER SEQUENCE" command fails with error: "invalid identifier: _sys_ prefix not allowed" |
| 384 | ERR_SQL_TOO_LONG_CONSTANT | string is too long | 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2222219 - SAP HANAErrors and different Results due to Design Changes |
| 391 | ERR_SQL_INV_USABLE_VIEW | invalidated view | This error indicates that the view <view> is in- valid. This can e.g. happen if the definition of an underlying object changed or an object was dropped. You have to make sure that the view is consistent and valid or avoid accesses / drop the view. 2985592 - Database returned the SQL code 391. Error text: invalidated view |
| 396 | ERR_SQL_EXST_USER_DE- FINED_TYPE | cannot use duplicate user-defined type name | 2223237 - Troubleshooting HANAEmbed- ded Statistics Server Migration - decision tree 2122188 - ESS disabled due to duplicate cre- ation of TT_MAIL_COLLECTOR |
| 397 | ERR_SQL_INV_OBJ_NAME | invalid object name | This error indicates that an object isn't found with the specified name (and schema). 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 398 | ERR_SQL_MANY_ORDER_BY | cannot have more than one order by | Only one ORDER BY clause is allowed in a state- ment |
| 402 | ERR_SQL_DROPPED_USER | the user was already dropped before query execution | 2819401 - Errors Related to the _SYS_XB User and Schema When Running theSAPHANA System Migration Tool to Migrate From SAP HANA1.0 to SAP HANA2.0 on IBM Power |
| 403 | ERR_SQL_INTERNAL_ERROR | internal error | Generic preamble. Check the HANAservice traces and ABAP dump traces for further infor- mation on the error. |
| 406 | ERR_SQL_CANT_UP- DATE_GEN_COL | "INSERT UPDATE and UPSERT are disallowed on the generated field" | 3070791 - INSERT, UPDATE and UPSERT are disallowed on the generated field |
| 410 | ERR_SQL_INV_PRIVILEGE_NAME- SPACE | invalid privilege name- space | 2428863 - Unable to view any package in- side Content Folder of HANAStudio |
| 411 | ERR_SQL_INV_TABLE_TYPE | invalid table type | 2280915 - CREATE procedure gives error "258 - insufficient privilege: Not authorized er- ror". |
| 412 | ERR_SQL_INV_PASSWORD_LAY- OUT | invalid password layout | 2895515 - Mismatch password_layout error occurred in HANA. |
| 414 | ERR_SQL_ALTER_PASS- WORD_NEEDED | user is forced to change password | Provide a new password for <user> or disable the password life time if it isn't required (e.g. because it is a pure technical user): 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2137351 - Error: 414 user is forced to change password for SAPDBCTRL (or SAPHA- NADBSHD) 2386570 - SAP DBTech JDBC: [591]: internal error: internal error: user is forced to change password 2136604 - Error InstallingPOonaSAP HANAMulti-tenant Database |
| 415 | ERR_SQL_USER_DEACTIVATED | user is deactivated | 2574644 - SAP HANAdatabase user is deac- tivated 2452650 - User password expired with max- imum_unused_initial_password_lifetime set at shot time 2681997 - You have reached maximum num- ber of invalid password entry attempts. User is locked until ... 3066561 - Parameter detailed_er- ror_on_connect controls what messages are re- turned during error connect attempt |
| 416 | ERR_SQL_USER_LOCKED | user is locked; try again later | This error is typically caused because the max- imum number of invalid connect attempts has been reached. It is controlled by the following SAP HANAparameter: indexserver.ini -> [password policy] -> maxi- mum_invalid_connect_attempts (default: 6) 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 420 | ERR_SQL_ALTER_PASS- WORD_NOT_ALLOWED | password change cur- rently not allowed | 2765239 - Password change currently not allowed: minimal password lifetime is x days. |
| 423 | ERR_SQL_LVC | AFL error | Multiple causes, review KBA 2399990 - How- To: Analyzing ABAP Short Dumps inSAPHANA Environments |
| 424 | ERR_SQL_INV_PACKAGE | invalid name of pack- age | 1891017 - Grant Repository Access to Root Package in SAP HANAStudio |
| 430 | ERR_SQL_INV_USABLE_PROC | invalidated procedure | 2935599 - SQL error 430 (invalidated proce- dure) 2196359 - Limitations for cross-database ac- cess in an SAP HANAMDCenvironment |
| 431 | WRN_SQL_NEARLY_EX- PIRED_PASSWORD | user's password will expire within few days | 1752349 - DBconnection fails with SQL error 431 - user's password will expire within few days 1702224 - Disable password lifetime for technical users |
| 435 | ERR_SQL_INV_EXP | invalid expression | 2222219 - SAP HANAErrors and different Results due to Design Changes 2044468 - FAQ: SAP HANAPartitioning |
| 436 | ERR_SQL_SET_SYSTEM_LICENSE | could not set system li- cense | 2263579 - "could not set system license: 5503: nameserver failed to process the request" error during HANAlicense key installation 2311999 - Permanent license import failed via HDBSQL 2772760 - Unable to apply the permanent license to SYSTEMDB |
| 437 | ERR_SQL_ONLY_LICENSE_HAN- DLING | only commands for li- cense handling are al- lowed in current state | 2728984 - System Has No Valid License. Ex- ecute failed (437) - Instance is registered with permanent license 2781578 - "License Expired" error when ena- bling HDI container in MDCHANAenvironments 2670267 - Error: Get server node failed on connection 0: rc=437 |
| 440 | ERR_SQL_TABLE_TYPE_CONVER- SION_ERROR | table type conversion error | 2397189 - SAP DBTech JDBC: [440]: Table Type Conversion Error During SUMUpgrade in The Phase MAIN_SHDIMP/PARMVNT_SHD |
| 442 | ERR_SQL_MAX_NUM_COLUMN | number of columns ex- ceeds its maximum | 2154870 - How-To: Understanding and defin- ing SAP HANALimitations |
| 444 | ERR_SQL_PACKMAN | package manager er- ror | 2936298 - SAP HANAExternal Machine Learning Library 2.0 requires libssl 1.0.x |
| 446 | ERR_SQL_EXST_TRIGGER | cannot use duplicate trigger name | 2911708 - ERROR [SQL-301] unique con- straint violated: Table(STATISTICS_PROPER- TIES) |
| 447 | ERR_SQL_BACKUP_FAILED | backup could not be completed | backup could not be completed:' is a preamble to the actual root cause for the error. Please check the HANAservice trace files for more in- formation on the error. Example scenarios: 2472144 - HANABackup Using Backint fails with the error: [447] backup could not be com- pleted, [110203] Not all data could be written 2500531 - Error "ERROR BACKUP SAVE DATA terminated with error: [447] backup could not be completed, [2000004 ] Can not open file" when doing a backup 2399786 - Backup could not be completed: Error calling io_setup 2623425 - Backup could not be completed 2310262 - Error [110026] - Backup could not be completedonHANA 2723171 - [447] backup could not be com- pleted, [3000116 ] Could not acquire save- point lock |
| 448 | ERR_SQL_RECOVERY_FAILED | recovery could not be completed | recovery could not be completed:' is a preamble to the actual root cause for the error. Please check the HANAservice trace files for more in- formation on the error. Example scenarios: 2728068 - HANAPoint in time recovery fails - [448] recovery could not be completed 2688972 - Recovery Error: [448] recovery could not be completed, [110021] Object 0 with the value 1024 does not exist-SAPHANA |
| 449 | ERR_SQL_RECOVERY_STRATEGY | recovery strategy could not be deter- mined | recovery strategy could not be determined: ' is a preamble to the actual root cause for the error. Please check the HANAservice trace files for more information on the error. Example scenarios: 2123153 - [449] recovery strategy could not be determined [110512] Backint duringHANA Recovery 2610577 - Backup destination header is cor- rupt [110063] 2736164 - recovery strategy could not be de- termined - BKI1214E: TSMError for session to |
| 451 | ERR_SQL_NOT_AL- LOWED_SUBJ_TAB_AC- CESS_TRIGGER | modification of subject table in trigger not al- lowed | 2800020 - FAQ: SAP HANATriggers 2222219 - SAP HANAErrors and different Results due to Design Changes 2170927 - Create trigger fails with error JDBC: [451]: modification of subject table in trigger not allowed: maximum nesting depth |
| 452 | ERR_SQL_INV_BACKUPID | invalid backup id | 2962261 - Backup catalog housekeeping: in- valid backup id 'xxxxxxxxxxx' |
| 454 | WRN_SQL_WRONG_HINT_SYN- TAX | wrong hint syntax | 2939423 - Getting Error while creating View with HINT - incorrect syntax near "HINT" |
| 455 | ERR_SQL_READ_ONLY_SES- SION_VARIABLE | the predefined session variable cannot be set via SET command | 2470084 - XSUAA metadata for XS_APPLI- CATIONUSER trust creation |
| 459 | ERR_SQL_INV_USABLE_FUNC | invalidated function | This termination indicates thataSAPHANA function was accessed that is invalidated. You can use SQL: "HANA_Objects_Functions" (ONLY_INVALID_FUNCTIONS = 'X') available via SAP Note 1969700 to list invalid functions in the system. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 461 | ERR_SQL_FK_NOT_FOUND | foreign key constraint violation | This error indicates that a change failed due to a foreign key constraint violation. 2160391 - FAQ: SAP HANAIndexes 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 462 | ERR_SQL_FK_ON_UPDATE_DE- LETE_FAILED | failed on update or de- lete by foreign key con- straint violation | This error indicates that a change failed due to a foreign key constraint violation. 2160391 - FAQ: SAP HANAIndexes 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 463 | ERR_SQL_MAX_NUM_TABLE | number of tables ex- ceeds its maximum | 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2968736 - HANASQLError 463 - number of tables exceeds its maximum |
| 464 | ERR_SQL_MAX_PARSE_TREE_DEP TH | SQL internal parse tree depth exceeds its max- imum | 2385634 - TREX_EXT_SEARCH_CELL_TA- BLE Leads to SQL Error "parse tree depth ex- ceeds its maximum:255" 2332054 - TREX_EXT_LIST_INDEXES fails with "SQL internal parse tree depth exceeds its maximum: parse tree depth exceeds its maxi- mum:255" |
| 465 | ERR_SQL_INV_USABLE_TRIGGER | "Cannot execute trig- ger was invalidated by object change" | This error is caused by an invalidated trigger (SAP Note 2800020 ) on the underlying ta- ble. 2800020 - FAQ: SAP HANATriggers 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 468 | ERR_SQL_HINT | hint error | Generic preamble to a more detailed error. 2142945 - FAQ: SAP HANAHints 2400006 - FAQ: SAP HANAStatement Hints 2938007 - Query on SAP HANAfails with error 468: hint error 2916954 - Normalization of Whitespaces and Comments of SQL statements in Statement Hints 2570351 - Error 468/ "hint error: invalid hint" From TREX_EXT_SEARCH_CELL_TABLE or TREX_EXT_AGGREGATE |
| 472 | ERR_SQL_EXST_DATA_SOURCE | cannot use duplicate data source name | 2408262 - SAP DBTech JDBC: [472]: cannot use duplicate data source name: __esstore$ |
| 474 | ERR_SQL_INV_ADAPTER | invalid adapter name | 2552938 - Error when altering HANARe- mote Source connection adapter type from SDA to SDI: invalid adapter name - SAP HANA1.0 smart data integration 2440935 - SAP DBTech JDBC: [474] (at 21): invalid adapter name: mii: line 1 col 22 (at pos 21) |
| 476 | ERR_SQL_INV_REMOTE_OBJECT | invalid remote object name | Preamble to a more detailed error: 2262782 - Unable to export or import SAP HANAvirtual tables 2033611 - Limitation of export / import for virtual tables 2775477 - SAP DBTech JDBC: [476]: invalid remote object name: IMPORT_TABLE can't be used for functions. 2607873 - Error when creating file adapter virtual table using SQL - SAP HANASmart Data Integration 2554385 - ODBCError during Import of a HANASchema / Table(s) |
| 478 | ERR_SQL_UDF_RUNTIME | user defined function runtime error | 2945199 - search table error: [6859] Attribu- teEngine: divide by zero 2401963 - Invalid table name exception when calling UDF 2792149 - currency/unit conversion error: conversion type '<conversion type>' has unsup- ported 'BKUZU' or 'GKUZU' type set |
| 485 | ERR_SQL_INV_STRUC- TURED_PRIVILEGE_DEFINITION | invalid definition of structured privilege | 2250455 - SAP DBTech JDBC 485 - Invalid definition of structured privilege: Invalid filter condition 2762943 - ERROR [SQL-485] invalid defini- tion of structured privilege: Condition 1 = 1 can- not be used for <viewname> 2608634 - Invalid definition of structured privilege when use HANAexternal view for modified composite provider 2563281 - Error message "invalid definition of structured privilege: Complex condition [...] cannot be used for view [...]" |
| 488 | ERR_SQL_INV_DATABASE | invalid database name | HANATenant or SYSTEMDB System ID (SID) not recognised |
| 494 | ERR_SQL_INV_EPMQUERY- SOURCE_DEF | invalid EPMQuery Source definition | 2481228 - dberror(PreparedStatement.exe- cuteUpdate): 494 - invalid EPMQuery Source definition: no valid EPMlicense available error in SAP Analytics Cloud (BOC) |
| 500 | ERR_SQL_REQUIRE_PREDICATE | predicates are required in a where clause | 2748386 - Error "SAP DBTech JDBC: [500]: predicates are required in a where clause" When Running Select * From User Authorization Views 2795522 - Querying EFFEC- TIVE_ROLE_GRANTEES fails with error un- known role_name 2088971 - How-To: Controlling the Amount of Records in SAP HANAMonitoring Views 2564718 - Authorization replication termi- nates with SQL error message "predicates are required in a where clause: unknown user_name" 2541080 - Predicates are required in a where clause in SAP Analytics Cloud (BOC) |
| 503 | ERR_SQL_EXST_TASK | cannot use duplicate name of task | 2695441 - Unable to activate flow graph within the import package - SAP HANASmart Data Integration |
| 512 | ERR_REP | replication error | Generic preamble to a more detailed error: 2852687 - HANAREPLICATION ERROR 2754755 - HANAsystem replication error oc- curred 2712064 - SAP HANASystem Replication Er- ror port 4####already in use 2680982 - Error "site to unregister is still online, cannot proceed" When Unregistering the Secondary System in System Replication Envi- ronment 2813089 - Replication mode/status is UN- KNOWNinMDCscenario 2695510 - With Table Replication, Error Mes- sage Flooding in Worker Node Indexserver After Coordinator Node Failed-over 2796783 - Copying/Moving a Tenant Data- base From a System Replication Primary Sys- tem to Another HANASystem Fails When Se- cure Network Communication is Disabled 1999880 - FAQ: SAP HANASystem Replica- tion |
| 513 | ERR_SQL_REP_ALREADY_ACTIVE | cannot execute DDL statement on replica- tion table while repli- cating | DDL like CREATE/ALTER/DROP etc not possi- ble during replication operation |
| 544 | ERR_RS_PARTITION | partition error | 2930379 - How to increase the total number of partitions for CDPOStable |
| 576 | ERR_API | api error | 2618451 - SSL API error happened when copy or move tenant database betweenHANA systems 2650994 - SAP HANASystem Replication does not work with DBisolation set to HIGH 2771017 - Replication does not complete due to nameserver error 2561693 - HANADatabase fails to start due to SSL error 2862268 - BI Commentary Guidelines for HANASSLConnections |
| 578 | ERR_API_INV_STATEMENT | invalid statement | The issue can be a consequence of problems on lower layers (infrastructure / hardware) result- ing in a malformed statement ID. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 589 | ERR_API_TOO_MANY_PARAME- TERS | too many parameters are set | 3040627 - Error 589 - too many parameters are set: number of parameters xxxxx exceeds maximum number of parameters, 32767 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2380176 - FAQ: SAP HANADatabase Trace |
| 592 | ERR_API_NOT_SUP- PORTED_TYPECONV | not supported type conversion | 2962294 - HANAAlert 27 is disabled and will not be called. Reason: timeout SNAPSHOT_ID: <timestamp> 2380176 - FAQ: SAP HANADatabase Trace |
| 597 | ERR_API_SESSION_CONTEXT_ER- ROR | session context error | Preamble to more detailed error described fur- ther in: 2380176 - FAQ: SAP HANADatabase Trace 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 598 | ERR_API_EXTERNAL_EXECU- TION_FAILURE | Failed to execute the external statement | This is a common preamble to a more detailed error. It can have multiple causes. Please review the error detail from the index- server traces and search the SAP HANAKnowl- edge base for existing Knowledge based articles and SAP Notes. 2776953 -Query Fails With Error "failed to execute the external statement: no such data type:.." in HANAScale-out System |
| 600 | ERR_API_CALL_ROUTING_FAIL- URE | failed routed execution | Preamble to more detailed error described fur- ther in: 2380176 - FAQ: SAP HANADatabase Trace 2200772 - FAQ: SAP HANAStatement Rout- ing and Client Distribution Mode 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2090424 - Error -10108 (Session has been reconnected) after failover of coordina- tor/worker node 2591281 - Blocked Transactions fromHANA JDBC Client Call - Session Will be Closed due to the Error: [600] failed routed execution 2691896 - Distributed Query Fails With "StatementRouting Connection.cc(xxxxx): failed to join XA session due to active user transac- tion" |
| 603 | ERR_API_INV_LOB | invalid LOB | 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions 2690991 - Error 5400 Invalid type 64 in column of type 32 at udiv during consistency check 2408032 - Reading From LOB Binary Stream After Closing the ResultSet via JDBC Fails With Error "invalid lob locator id (piecewise lob read- ing)" 3017449 - Indexserver Crash in TRexCom- monObjects::writeRow When Executing an UP- DATE Statement on a Partitioned Table |
| 606 | ERR_API_EXCEED_MAX_LOB_SIZE | exceed maximum LOB size | See 2154870 - How-To: Understanding and defining SAP HANALimitations |
| 608 | ERR_API_EXCEED_MAX_PRE- PARED_STATEMENT | exceed maximum number of prepared statements | System limitation. Described further in: 3031816 - "ERROR [SQL-608] exceed maxi- mumnumberof prepared statements" and "the number of prepared statements per connection cannot exceed <number>" 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace |
| 613 | ERR_API_TIMEOUT | execution aborted by timeout | This error indicates that a database request hit the timeout (in seconds) 2000003 - FAQ:SAPHANA 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 3116306 - [Error] execution aborted by time- out while partitioning |
| 640 | ERR_SQL_2 | sql processing error | Starting with SAP HANARev. 122.03 the THROW_ERROR hint is available (SAP Note 2436893 ) that terminates the execution of the underlying database request 2380176 FAQ: SAP HANADatabase Trace 2073630 - DBIF_RSQL_SQL_ERROR SQL er- ror 256 when access table 2142945 FAQ: SAP HANAHints |
| 648 | ERR_SQL_TRIG- GER_AND_PROC_NEST- ING_DEPTH_EXCEEDED | nesting depth of trig- ger and procedure is exceeded | System limitation: 2134323 - Nesting error in SQLRUN_ISU_TRIGGERS: maximum depth 8 2977828 - Trigger Creation Fails With 'nest- ing depth of trigger and procedure is exceeded' 2130431 - 'Nesting depth of trigger and pro- cedure is exceeded' error is raised when SQL trigger with procedure call is created |
| 651 | ERR_SQL_EXST_OBJECT | cannot use duplicate object name | 2572224 - How-To: Repairing SAP HANATa- bles |
| 663 | ERR_SQL_CONNECT_NOT_AL- LOWED | user not allowed to connect from client | 3171342 - ERROR [SQL-663] user not al- lowed to connect from client |
| 684 | ERR_SQL_PLANSTABIL- IZER_STORED_HINT_RECORD_AL- READY_EXISTS | plan stabilizer stored hint error - statement hint record already ex- ists | 2700051 - Delivery of Statement Hints (SAP HANA>=1.00.122.03) 2400006 - FAQ: SAP HANAStatement Hints |
| 685 | ERR_SQL_PLANSTABIL- IZER_STORED_HINT_RE- CORD_DOES_NOT_EXIST | plan stabilizer stored hint error - statement hint record does not exist | 2700051 - Delivery of Statement Hints (SAP HANA>=1.00.122.03) 2400006 - FAQ: SAP HANAStatement Hints |
| 1024 | ERR_SES | session error | Preamble to more detailed error: 2303494 - Importing Delivery Unit fails with "Session error: Repository: Activation failed for at least one object" 2280915 - CREATE procedure gives error "258 - insufficient privilege: Not authorized er- ror". 2775970 - The re-import of a delivery unit fails after an upgrade |
| 1025 | ERR_COM | communication error | Network or communication related problem 2222200 - FAQ: SAP HANANetwork 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2000003 - FAQ:SAPHANA |
| 1026 | ERR_COM_LISTEN | cannot bind a commu- nication port | 2261671 - "cannot bind to the local port" when start HANAservices |
| 1033 | ERR_SES_INV_PROTOCOL | error while parsing protocol | These terminations indicate a severe prob- lem during parsing the communication pro- tocol. Check the database trace (SAP Note 2380176 ) for more details. Typically you will find an error "failed to encode cursor: error while parsing protocol" with further accompany- ing details. 2380176 - FAQ: SAP HANADatabase Trace 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 1037 | ERR_COM_UNKNOWN_HOST | unknown hostname | 2941074 - SAP HANAserver rebooted 2936450 - SAP HANAis down without crash or shutdown |
| 1038 | ERR_SES_SERVER_BUSY | rejected as server is temporarily over- loaded | 2908549 - SAP HANADatabase requests fail with error code 1038 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2222250 - FAQ: SAP HANAWorkload Man- agement 3061965 - Unexpected Error "rejected as server is temporarily overloaded" |
| 1335 | ERR_SQLSCRIPT_RUNTIME_CY- CLIC_DEPENDENCY | Cyclic dependency found in a runtime pro- cedure | 3032114 - Cyclic Dependency Error When Revoking Role From User Through GRCin SPS05 3018242 - Removing Role From User via HANAor GRCCanCause Cyclic Dependency Error |
| 1793 | ERR_SHM_CREATE_INVALID | invalid key or invalid size | This issue can arise due to wrong configuration of shared memory setting on OSlevel. 2827664 - NameServer persistence initiali- zation failed |
| 2048 | ERR_CS | Column store error | Generic preamble to a more detailed error de- scription: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 1999997 - FAQ:SAPHANAMemory 2222200 - FAQ: SAP HANANetwork 2044468 - FAQ: SAP HANAPartitioning 2380176 - FAQ: SAP HANADatabase Trace |
| 2054 | ERR_CS_DELTA_LOG_RE- PLAY_FAILED | Redo log replay failed | Check HANAservice traces for more detail on the error cause |
| 2055 | ERR_CS_MAXIMUM_ROW | Maximum number of rows per table or parti- tion reached | System limitation: 2212518 - HANAerror maximum number of rows per partition reached 2154870 - How-To: Understanding and defin- ing SAP HANALimitations 2964715 - Maximum number of rows per table or partition reached: '_SYS_AUDIT:CS_AU- DIT_LOG_' 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 2560 | ERR_METADATA | Metadata error | Preamble to more detailed error: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2380176 - FAQ: SAP HANADatabase Trace 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions |
| 2561 | ERR_DIST_METADATA | Distributed metadata error | 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions 2245772 - distributed metadata error: Failed to get table location during table lock - Error during BWupgrade or migration |
| 2566 | ERR_DIST_META- DATA_TNSCLIENT_FAILURE | Distributed environ- ment error | 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions 2240241 - Failed to update dependency: dis- tributed environment error 2447887 - Removing Multiple Services from HANAScale Out Environment Can Lead to Data Loss 2062308 - Deadlock Between Worker and Coordinator Node During Worker Startup 2433918 - Execution of a Stored Procedure Fails With the Message "distributed environ- ment error: table already exists;newIndex(..): catalog creation failed" |
| 2567 | ERR_DIST_METADATA_NET- WORK_FAILURE | Network error | Generic preamble to a more detailed descrip- tion: 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 1999880 - FAQ: SAP HANASystem Replica- tion 2057046 - FAQ: SAP HANADelta Merges 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions |
| 3584 | ERR_DIST_SQL | Distributed SQL error | Generic preamble to a more detailed descrip- tion: 1999997 - FAQ:SAPHANAMemory 1999998 - FAQ: SAP HANALock Analysis 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions 2380176 - FAQ: SAP HANADatabase Trace 2901387 - Unable to run HANA_Configura- tion_MiniChecks_2.00.040+ 3105683 - A Query Fails With an Error "dis- tributed SQL error: [18] A received argument has an invalid value" 3121246 - SQL error "SAP DBTech JDBC: [3584]: distributed SQL error: [18] A received argument has an invalid value" 1969700 - SQL Statement Collection for SAP HANA |
| 3587 | ERR_DIST_SQL_INVALID_PROTO- COL | Invalid protocol or service shutdown dur- ing distributed query execution | The following error messages can indicateOOM situations. Be aware that some of the errors can also be issued in other scenarios. To make sure that they are really memory related, you have to check the related trace file. 1999997 - FAQ:SAPHANAMemory |
| 3589 | ERR_DIST_SQL_REMOTE_EXECU- TION_FAILURE | Remote query execu- tion failure | 2439128 - Error 3589 - "remote query execu- tion failure" When Opening XS Applications |
| 3841 | ERR_AUDITING_NO_PRIV_NAME | Invalid privilege | 2428863 - Unable to view any package in- side Content Folder of HANAStudio |
| 3843 | ERR_AUDITING_POLICY_AL- READY_EXISTS | Audit policy with cur- rent name already ex- ists | Policy name already created as per "CREATE AUDIT POLICY ... " |
| 3844 | ERR_AUDITING_INV_POL- ICY_TYPE | Invalid combination of audit actions | Check auditing configuration and setup: Auditing Activity inSAPHANA Audit Policies Audit Trails Auditing Configuration and Audit Policy Man- agement Best Practices and Recommendations for Cre- ating Audit Policies Configuring Database Auditing |
| 3846 | ERR_AUDITING_INV_LEVEL | Invalid auditing level | Check auditing configuration and setup: Auditing Activity inSAPHANA Audit Policies Audit Trails Auditing Configuration and Audit Policy Man- agement Best Practices and Recommendations for Cre- ating Audit Policies Configuring Database Auditing |
| 3847 | ERR_AUDITING_INV_POL- ICY_NAME | Invalid policy name | Check auditing configuration and setup: Auditing Activity inSAPHANA Audit Policies Audit Trails Auditing Configuration and Audit Policy Man- agement Best Practices and Recommendations for Cre- ating Audit Policies Configuring Database Auditing |
| 3848 | ERR_AUDITING_INV_ACTION_OB- JECT_TYPE | Invalid combination of audit action and object type | Check auditing configuration and setup: Auditing Activity inSAPHANA Audit Policies Audit Trails Auditing Configuration and Audit Policy Man- agement Best Practices and Recommendations for Cre- ating Audit Policies Configuring Database Auditing |
| 3849 | ERR_AUDITING_INV_OB- JECT_TYPE | Audit policy for this object type not sup- ported | Check auditing configuration and setup: Auditing Activity inSAPHANA Audit Policies Audit Trails Auditing Configuration and Audit Policy Man- agement Best Practices and Recommendations for Cre- ating Audit Policies Configuring Database Auditing |
| 4096 | ERR_PLANVIZ_GENERAL | [PlanViz] general error | 2275905 - How to disallow the Usage of PlanViz in a SAP HANASystem 2825090 - PlanViz for a DMLStatement on Row Store Table Fails in Scale-Out System 2337716 - SAP DBTech JDBC: [4096]: [Plan- Viz] general error: Not supported yet; Please update your server instance |
| 4098 | ERR_PLANVIZ_INVA- LID_PLAN_GENERAL | [PlanViz] invalid plan | 2781336 - PlanViz Execution Fails With "inva- lid plan -- try preparing statement again" |
| 4104 | ERR_PLANVIZ_PLAN_NOT_FOUND | [PlanViz] plan not found | 2337716 - SAP DBTech JDBC: [4096]: [Plan- Viz] general error: Not supported yet; Please update your server instance |
| 4105 | ERR_PLANVIZ_UNSUP- PORTED_STMT_TYPE | [PlanViz] unsupported statement type | 2822978 - Statement Execution Fails In SAP HANAStudio after PlanViz Generation Failed |
| 4109 | ERR_PLAN- VIZ_TRACE_ONLY_GENERAL | [PlanViz] error in trace-only mode | Due to a SAP HANAbug this error can happen when plan trace is activated with a statement hash filter on SAP HANA<=2.00.046. Make sure that the plan trace is only activated when really required and optimally in non-production systems. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments 2781336 - PlanViz Execution Fails With "inva- lid plan -- try preparing statement again" |
| 4249 | ERR_USER_PARAM_DUPLI- CATE_EMAIL_ADDRESS | Same email address cannot be used for dif- ferent users | 2845742 - SAP HANACockpit user deletion after failed logon attempts with wrong password |
| 4251 | ERR_USER_PARAM_INVA- LID_STATEMENT_MEMORY_LIMIT | Invalid statement memory limit | Setting User Parameters for Workload 2222250 - FAQ: SAP HANAWorkload Man- agement |
| 4252 | ERR_USER_PARAM_INVA- LID_STATEMENT_THREAD_LIMIT | Invalid statement thread limit | Setting User Parameters for Workload 2222250 - FAQ: SAP HANAWorkload Man- agement |
| 4274 | ERR_KERBEROS_DUPLI- CATE_PROVIDER | Duplicate specification of identity for KER- BEROS | 2921965 - Duplicate specification of identity for KERBEROS |
| 4280 | ERR_TICKET | General ticket error | 2872841 - Cannot Load Tile Error on Fiori Launchpad |
| 4321 | ERR_SSL_ENFORCE | Only secure connec- tions are allowed | Preamble to more detailed error: 2999904 - hdbsql failed with error "4321: only secure connections are allowed SQLSTATE: HY000". 2475246 - How to configure HANADBcon- nections using SSL from ABAP instance 2572975 - Solman monitoring of only spe- cific HANADBsusing SSL 3168368 - After setting sslenforce as true in HANAdatabase, the R3trans, transport in ABAP are failing 2818623 - Enabled SSL DBCOconnection SolMan to HANAresult in sql error 4321 3028338 - "Only secure connections are al- lowed" in HDB_CHK_PRIVILEGES phase with SUM1.0 2420711 - FAQ: SAP HANAXimoStudio 2795610 - Enabling SSO in HANACockpit Manager of SAP HANACockpit 2 Fails When sslEnforce=true on the Remote SAP HANASys- tem 3083365 - User Provided Service connec- tions with SSL functionality is not available in SAP HANAWebIDEfor HANA(On-Premise) |
| 5136 | ERR_TEXT_COMMON_ALLOCA- TION_FAILED | Allocation failed. | Memory allocation failure. Preamble to more de- tailed error: See '1. Which indications exist forSAPHANA memory problems?' - 1999997 - FAQ: SAP HANAMemory |
| 5170 | ERR_TEXT_COM- MON_FILE_NOT_FOUND | File not found. | This a generic error where an expected system, library (dll) file or third party client driver file cannot be found at the expected or configured directory location. Some example scenarios: 2349144 - HANAinstance does not stop - kill.sap file not found 2981347 - Failed to create an SDA connec- tion between HANAand DB2 - Can't open lib '/ opt/IBM/db2/dsdriver/lib/libdb2o.so.1': file not found 2928047 - libsqora.so.11.1': file not found |
| 5172 | ERR_TEXT_COMMON_INVA- LID_LENGTH | Invalid length. | Table column inconsistency. 2905396 - Error 5995 reported by check_ta- ble_consistency 2116157 - FAQ: SAP HANAConsistency Checks and Corruptions |
| 5533 | ERR_TEXT_PREPROCES- SOR_FAILED | Preprocessor: failed | This error indicates a problem when communi- cating with the preprocessor service, e.g. in con- text of text searches. You can check the prepro- cessor database trace (SAP Note 2380176 ) for further details. 2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANAEnvironments |
| 5634 | ERR_CERTADM_INVA- LID_CERT_DEFINITION | Certificate definition inconsistent | 2975450 - Error: "5634: Certificate definition inconsistent" when import Trusted Certificate via SQL |
| 5637 | ERR_CERTADM_CERTIFI- CATE_IN_USE | Certificate could not be dropped because it is still in use by at least one PSE | 3169349 - Certificate could not be dropped because it is still in use by at least one pse |
| 5736 | ERR_MASKING_INVALID_COL- UMN_DATATYPE | Masking: not sup- ported data type | 2669149 - Masking: not supported data type: exception 4075007 : column col- umn_name does not have a character string data type and cannot be masked |
|
## 2.3 Performance and High Resource Utilization
|
## 2.3 Performance and High Resource Utilization
By observing the general symptoms shown by the system such as poor performance, high memory usage, paging or column store unloads we can start to narrow down the possible causes as a first step in analyzing the issue.
## High Memory Consumption
You observe that the amount of memory allocated by the SAP HANA database is higher than expected. The following alerts indicate issues with high memory usage:
- Memory usage of name server (Alert 12)
- Total memory usage of Column Store tables (Alert 40)
- Memory usage of services (Alert 43)
- Memory usage of main storage of Column Store tables (Alert 45)
- Runtime dump files (Alert 46)
See the section Memory Problems for information on analyzing the root cause.
## Out-of-Memory Situations
You observe trace files or error messages indicating an Out-of-Memory (OOM) situation.
See the section Memory Problems for information on analyzing the root cause.
## Paging on Operating System Level
You observe that paging is reported on operating system level.
See the section Memory Problems for information on analyzing the root cause.
## Column Store Unloads
You observe unloads in the column store. The following alerts indicate issues with high memory usage:
- Column store unloads (Alert 55)
See the section Memory Problems for information on analyzing the root cause.
## Permanently Slow System
Issues with overall system performance can be caused by a number of very different root causes. Typical reasons for a slow system are resource shortages of CPU, memory, disk I/O and, for distributed systems, network performance.
Check Overview Monitoring and Administration Performance Monitor for either Memory , CPU or Disk Usage . If you see a constant high usage of memory or CPU, proceed with the linked sections Memory Problems or CPU Related Root Causes and Solutions respectively. I/O Related Root Causes and Solutions provides ways to check for disk I/O related problems. In case of network performance issues, have a look at the Monitor Network page accessible from the Monitoring group in the SAP HANA cockpit.
Note that operating system tools can also provide valuable information on disk I/O load. Basic network I/O data is included in the Load graph and in the m_SERVICE_NETWORK_IO system view, but standard network analysis tools can also be helpful to determine whether the network is the main bottleneck. If performance issues only appear sporadically, the problem may be related to other tasks running on the database at the same time.
These include not only maintenance related tasks such as savepoints (disk I/O, see I/O Related Root Causes and Solutions ) or remote replication (network I/O), but also SQL statements dispatched by other users, which can block a lot of resources. In the case of memory, this can lead to unloads of tables, which affects future SQL statements, when a table has to be reloaded into memory. In this case, see Memory Problems as well. Another reason for poor performance, which in many cases cannot be detected by the SAP HANA instance itself, are other processes running on the same host that are not related to SAP HANA. You can use the operating system tools to check for such processes. Note that SAP only supports production systems running on validated hardware.
## Slow Individual SQL Statements or with Increasingly Long Runtimes
Issues with the performance of a particular statement can be caused by a number of very different root causes. In principle, a statement can trigger all the resource problems that also lead to an overall slowdown of the system, so most of the previous information also applies to statement performance. In addition, statement performance can suffer from transactional problems, that is, blocked transactions. Blocked transactions can be checked in the Threads tile or on the Blocked Transactions page accessible from the Monitoring group. For troubleshooting, proceed with Transaction Problems .
If the runtime of a statement increases steadily over time, there could be an issue with the delta merge operation. Alerts should be issued for most problems occurring with the delta merge, but since they depend on configurable thresholds, this is not always the case. For troubleshooting, proceed with Delta Merge . If you have none of the above problems, but the statement is still too slow, a detailed Statement Performance Analysis might reveal ways to optimize the statement. However, some queries are inherently complex and require a lot of computational resources and time.
## Related Information
Memory Problems [page 65]
CPU Related Root Causes and Solutions [page 82] Disk Related Root Causes and Solutions [page 106] I/O Related Root Causes and Solutions [page 114] m_SERVICE_NETWORK_IO Transactional Problems [page 167] Delta Merge [page 129] Statement Performance Analysis [page 180]
|
## 2.4 Common Symptoms and Troubleshooting
|
## 2.4 Common Symptoms and Troubleshooting
Typical symptoms and the related troubleshooting information are described in this section.
System-side slow performance, slow individual statement performance, and OOM problems are issues that you might experience while using the SAP HANA database. For each section, this document will cover the known symptoms and the corresponding troubleshooting steps to follow depending on the causes.
|
## 2.4.1 Slow System-wide Performance
|
## 2.4.1 Slow System-wide Performance
Slow system-wide performance issues are problems that could be caused by excessive use of CPU, database resource locks or incorrect configuration of OS parameters.
Generally, when you encounter a performance issue, you may see these symptoms in SAP HANA cockpit:
- Continually high CPU usage according to OS commands or load graph (visible from CPU Usage tile Performance Monitor )
- Many pending or waiting threads in the thread view (details visible from the Threads tile).
To look for the cause at the operating system level refer to the topic System Appears to Hang with High System CPU Usage .
If the performance issue persists or if it recurs sporadically you may need to contact Support to analyze the root cause. In this case please generate at least two runtime dumps at 3 minute intervals while the system performance is slow for further investigation. For details refer to SAP Note 1813020 - How to generate a runtime dump on SAP HANA or the Guided Answer How to generate a runtime dump .
## Related Information
System Appears to Hang with High System CPU Usage [page 54]
SAP Note 1813020
How to generate a runtime dump (Guided Answer)
|
## 2.4.1.1 HANA System-wide Performance Analysis
|
## 2.4.1.1 HANA System-wide Performance Analysis
This topic describes solutions for both current and former system performance problems.
## Analysis of Current Performance Problems
Before taking any other action while the problem is present it is of utmost importance to capture a few HANA runtime environment (RTE) dump files and a Kernel Profiler Trace to collect information about the database's internal processes. Proceed as follows:
## Generating a Runtime Dump
Capture a number (3-5) of RTE dumps. There are several options for recording runtime dumps as described in the KBA 1813020 - How to generate a runtime dump on SAP HANA .
If the problem occurs randomly and you cannot predict when it will happen you can automate the collection of the runtime dumps with the SAP HANASitter tool which can be used, for example, to trigger methods such as the creation of traces and dumps when specific conditions are met. Refer to KBA 2399979 - How-To: Configuring automatic SAP HANA Data Collection with SAP HANASitter .
## Kernel Profiler Trace
Create a Kernel Profiler Trace, either:
- via the SQL console (see ALTER SYSTEM START KERNEL PROFILER statement)
- in hdbcons as described in KBA 1804811 SAP HANA Database: Kernel Profiler Trace .
## Analysis
Once the RTE Dumps are ready use an automated analysis tool such as the HANA Dump Analyzer to spot obvious problems. Refer to SAP Note 2498739 - How-To: Analyzing Runtime Dumps with SAP HANA Dump Analyzer . Most known problem situations are recognizable by the tool and you should then be able to take the first mitigation steps. Using the 'Auto Analyzer' option in the HANA Dump Analyzer the following summaries might be shown in the result:
- High Workload
- High CPU
- Waitgraph detected
Each of the identified issues require specific steps to perform an in-depth analysis and gain further insight on what potential culprits are.
## High workload / High CPU
This indicates that most of the active / running threads are in ownership of one specific application workload; if the HANA instance is configured according to official SAP guidance this should not happen under normal circumstances. It is important to understand which application user is responsible for the workload. If the situation is disruptive, ask the user to refrain form any further actions until the exact root cause is identified to avoid worsening the situation.
As a second step, check whether HANA Workload Management is configured according to SAP recommendations. Refer to KBA 2222250 - FAQ: HANA Workload Management . Pay particular attention to the appropriate configuration of the following workload related parameters:
- default_statement_concurrency_limit
- max_concurrency*
- max_concurrency_hint*
- num_cores*
(*not necessarily required as of HANA SPS3) Refer to KBA 2600030 - Parameter Recommendations in SAP HANA Environments .
## Waitgraph detected
This situation indicates that threads are not able to efficiently acquire locks on objects as they are already held by other threads (see Thread investigation below). The waitgraph is a directed graph depicting which threads are waiting for which locks and in turn which threads are holding the locks to be acquired. It is a good practice here to investigate what exactly the lock-holding threads (not the lock acquiring threads) are busy with. If no insights can be gained during this analysis and the problem requires an immediate mitigation, consider canceling the session responsible for the lock-holding threads by:
1. Identifying the corresponding connection ID of the problematic thread by examining the runtime dump; search the file for the thread ID identified, for example:
2. Cancel the session with:
```
1348967027[thr=<thread_id>]: SqlExecutor, TID: 34, UTID: 364438059, CID: <conn_id>,….
```
```
ALTER SYSTEM CANCEL SESSION '<conn_id>';
```
## Threads
A next step is to check what threads are currently running on the database while the performance issue exists. Y ou can check this in SAP HANA cockpit from the Threads card of the System Overview or from the Performance tab in SAP HANA Studio which is illustrated here:
Threads Overview
Refer to KBA 2114710 - FAQ: SAP HANA Threads and Thread Samples for tips on how to identify and solve problems with running and blocked threads. The information given for the following frequently-asked questions, for example, will be helpful:
- What kind of information is available for the SAP HANA threads?
- How can I interpret the thread state?
- What are the main thread types, methods and details?
## HANA Database Parameters
Check that the database parameters are configured as recommended. You can do this by running the script HANA_Configuration_Parameters_1.00.90+ , or HANA_Configuration_Parameters_Values_1.00.90+_MDC attached to the KBA 1969700 SQL Statement Collection for SAP HANA . The script can be executed in the system database as well as at the tenant database level. Recommended parameter values are discussed in more detail in the KBA 2600030 Parameter Recommendations in SAP HANA Environments .
Example Output of the HANA_Configuration_Parameters_1.00.90+ Script
## Analysis of Former Performance Problems
You can also analyze system-wide performance problems that occurred in the past using the methods described here.
## Thread Sample Analysis
When the issue is no longer present, a HANA Thread Sample analysis can be conducted to identify potential culprits. Proceed as follows using the scripts in the SQL Statement Collection for SAP HANA (attached to SAP Note 1969700 - see link in Further Information below):
1. Define a problematic time-period: be as accurate as possible here to avoid distortion of the statistical data by workloads not directly related. Use scripts TimeFrameReport (HANA_Global_TimeFrameReport_2.00.043+.txt) and LoadHistory (HANA_LoadHistory_Services_2.00.030+.txt) to do the following:
- Evaluate CPU / Memory / Disk
- Check Running vs. Waiting Threads
- Check on MVCC Versions
- Check Blocked Transactions / Locking Issues
2. Use the above information to identify the most active application workload for a defined time-period using the script HANA_Threads_ThreadSamples_FilterAndAggregation_*.
If you had a high CPU utilization in the past, use the script HANA_LoadHistory_Services_2.00.*.txt (or HANA_LoadHistory_Services_1.00.120+.txt for HANA 1) to find a time-period where the CPU was high. If a problematic time-period is identified run the HANA_Threads_ThreadSamples_FilterAndAggregation_* script
for this specific period. For example, if you have identified the period 10:00-11:00 a.m. on the 25th April, go to the modification section of the script and enter the following values:
```
'2021/04/07 10:00:00' BEGIN_TIME, '2021/04/07 11:00:00' END_TIME,
```
If the issue lies further in the past (older than few hours), you have to switch the DATA_SOURCE to 'HISTORY':
```
'HISTORY' DATA_SOURCE,
```
You can use the AGGREGATE_BY filter, for example, to see which threads have been consuming most of the CPU time:
```
'HASH, THREAD_STATE, THREAD_DETAIL, THREAD_METHOD' AGGREGATE_BY
```
Use the AGGREGATE_BY filter with the following values if you want to see which application user and component was actively consuming most of the CPU time:
```
'HASH, THREAD_STATE, APP_SOURCE, APP_USER' AGGREGATE_BY
```
Additionally, if you are only looking for the threads actively consuming CPU, you can set a filter in the modification section for THREAD_STATE:
```
'RUNNING' THREAD_STATE,
```
For further information refer to KBA 2114710 - FAQ: SAP HANA Threads and Thread Samples .
## Log Files for OS and Network
If the steps already described do not help to identify the performance problem, then it may be that the issue is not related to the SAP HANA database but could be an operating system, hardware, or network-related problem. In this case you can check the messages file for the time of the performance issue from the directory VAR/LOG for the HANA nodes. Check the messages for any indication of OS, hardware or network-related problems.
If necessary you can collect a runtime dump when the performance issue happens again and is live on the system as described above.
## Known Performance issues and How to Resolve Them
The following table identifies some specific known problems with links to KBAs which give technical details about how to resolve them.
| Symptom | Solution |
|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| After migration to HANADBfor ECC or Suite on HANAsystem reports and transactions are slow. | Check that you are using HANAoptimized transactions and applications, some optimizations may need to be explicitly switched on via the switch framework (transaction SFW5). Refer to SAP Note 1761546 - SAP ERP poweredbySAPHANA - Optimizations and the attached document (Suite on HANAOptimizations) which lists optimized objects (reports and transactions). 1761546 SAP ERP powered by SAP HANA- Optimizations |
| Symptom | Solution |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| After migration to HANADBcustom transactions or ABAP programs are slow. | You may need to optimize custom programs and transactions by using the code inspector tool and SQL monitor. Refer to the note 1912445 - ABAP custom code migration for SAP HANA- recommendations and Code Inspector variants for SAP HANAmigration . See also the blog post 'ABAP on HANA- from analysis to optimization' which includes, for example, a section on The Golden Rules: Five performance guidelines for ABAP database operations . |
| The system is slow with a lot of state- ments running. Statements of the type SELECT TOP X cause a performance problem on SAP HANA. | Refer to the SAP Note 2238679 - High CPU Consumption Caused by UnifiedTa- ble::MVCCObject::generateOLAPBitmapMVCC . |
| After a HANAupgrade the performance of calculation views is poor. | Refer to the following SAP Notes: • 2441054 - High query compilation times and absence of plan cache entries for queries against calculation views • 2291812 SAP HANADB: Disable/Enable CalculationEngine Feature - Calc- View Unfolding . |
| In an ABAP environment you are using the fast data access (FDA) protocol and the performance of queries is poor. | Refer to the KBA 2399993 - FAQ: SAP HANAFast Data Access . Question 6 identifies a list of possible problems which may occur with FDA. |
| Using fast data access the HANAsys- tem has poor performance. In the HANAtrace files you see entries like: Destroying allocator 'Connection/xxxxx/ Pool/RowEngine/Session' with x blocks and x bytes still allocated' . | This known issue is related to memory management of FDA queries and is descri- bed in SAP Note 2580435 - Memory Leak in Pool/RowEngine/Session . This may be solved by upgrading to a higher version of SAP HANA: HANA01SPS12 Revision 122.15 or higher, or, HANA02SPS01 Revision 012.04 or higher. |
## Further Information
Links to KBAs and SAP Notes which may be helpful :
- 1969700 - SAP HANA Statement Collection
- 1813020 - How to generate a runtime dump on SAP HANA
- 2399979 - How-To: Configuring automatic SAP HANA Data Collection with SAP HANASitter
- 2498739 - How-To: Analyzing Runtime Dumps with SAP HANA Dump Analyzer.
- 2000000 - FAQ: SAP HANA Performance Optimization
- 2222217 - How-To: Troubleshooting SAP HANA Startup Times
- 2222250 - FAQ: HANA Workload Management
- 2600030 - Parameter Recommendations in SAP HANA Environments
- 2114710 - FAQ: SAP HANA Threads and Thread Samples
You can also use Guided Answers to analyze performance problems. The following Guided Answer trees are focused on the SAP NetWeaver product:
- Master Guided Answer: Performance issues
- How to perform a Network analysis (Using Operation System Monitor - ST06)
- Analysis of Hardware Bottlenecks for Performance (Using Operation System Monitor - ST06)
- Performance Analysis Procedure for an ABAP Program (Using SAP Workload Monitor - ST03)
## Related Information
ALTER SYSTEM {START | STOP | SAVE | CLEAR} KERNEL PROFILER Statement (System Management)
|
## 2.4.1.2 System Appears to Hang with no new Connections and no Response from the SAP HANA Database
|
## 2.4.1.2 System Appears to Hang with no new Connections and no Response from the SAP HANA Database
In cases where logs cannot be written, all DML statement will fall into wait status. This can lead to a failure of opening new connections because the system internally executes DML statements during the process. Typically, a full log volume is the cause for this.
## Basic System Checks
In cases where the SAP HANA database is no longer responding to any requests it is advisable to follow a bottom up approach to quickly identify the root cause of the problem. The following system checks will eliminate common operating system related problems which often lead to system hanging situations:
Firstly, check the system resources at the operating system level, by using the TOP command:
Check the values for CPU and MEM to make sure that these resources are not exhausted.
Secondly, check the disk utilization by running the disk free command: df -h and verify that no volume has reached 100% utilization (see example below).
Check whether you are able to connect to the indexserver process locally by using hdbsql to run a test-query, for example:
```
SELECT CURRENT_TIMESTAMP FROM DUMMY;
```
If this is successful then check the network stability between the clients facing the issue and the SAP HANA database host.
## Possible Root Causes
Some common situations which cause a system to freeze are given here with remedial actions to take:
Root cause: Log volume full either caused by disk full or quota setting
## Required action:
1. Check for the DISKFULL event in the indexserver trace or
2. Run the disk free command: df -h in the OS shell (the -h option is more readable and displays the output in units of 1024). A result such as the following with a value of 100% will immediately identify the culprit as a full log area:
3. Check the quota setting in the file system.
4. If you have verified that the log volume is full then follow the procedure described in SAP Note 1679938 Log Volume is full .
```
/dev/mapper/vg_hana-log 102G 102G 0G 100% /hana/log
```
You can find additional information in SAP Note 2083715 - Analyzing log volume full situations .
Root cause: Log volume full caused by failure of log backup
## Required action:
1. Check backup.log (located at /usr/sap/<SID>=/HDB<Instance#>=/<Host>=/trace ) to see whether it includes ERROR in log backup. Check m_BACKUP_CATALOG, m_LOG_SEGMENTS.
2. If log backup uses backint, please check backint.log (located at /usr/sap/<SID>=/HDB<Instance#>=/ <Host>=/trace ) to see whether it includes ERROR information, and contact backint vendor support.
## Admission Control
Note that if statements are rejected with SQL Error 1038 this is related to the Admission Control feature which is designed to prevent the system from being overloaded by defining thresholds and either queuing or rejecting statements when necessary. You can check whether admission control is preventing new sessions from being established due to low system resources by querying the monitoring view m_ADMISSION_CONTROL_EVENTS:
```
SELECT * FROM M_ADMISSION_CONTROL_EVENTS;
```
If many events are raised during the problematic time-period you should investigate which SAP HANA resources were exhausted making it necessary for admission control to intervene. For more information about Admission Control see the KBA 2222250 FAQ: SAP HANA Workload Management
Before SAP HANA 2 SPS05 Revision 056 there is a known coding issue where the Admission Control feature could generate the SQL Error 1038 when there is no overloading of resources. For more information about this issue see the KBA 3061965 - Unexpected Error "rejected as server is temporarily overloaded" .
## Configuration Parameters for Admission Control
You should apply the recommended settings for all admission control configuration parameters located under indexserver.ini [admission_control] . Y ou can check the parameter settings using the script 'HANA_Configuration_Parameters_2.00.040+' from the SAP Note 1969700 SQL Statement Collection for SAP HANA . The example output below from this script shows a discrepancy for the setting queue_memory_threshold which is set to a value of 90 when on a SAP HANA Database with Revision <= 2.00.053 it should be zero. The explanation for this setting is to avoid queuing in case of high memory consumption that is often harmless (e.g. caused by a large page cache). The latest information about recommended configuration parameter settings is maintained in SAP note 2600030 Parameter Recommendations in SAP HANA Environments .
Where Admission Control is functioning correctly the root cause for the Admission Control event(s) is often high CPU, this can be confirmed for current Admission Control events using the script 'HANA_Workload_AdmissionControlEvents' or for historic Admission Control events using the script 'HANA_LoadHistory_Services' from the SAP Note 1969700 SQL Statement Collection for SAP HANA .
For troubleshooting steps for high CPU analysis please see Analysis of CPU Related Issues .
## Related Information
|
## 2.4.1.3 System Appears to Hang with High System CPU Usage
|
## 2.4.1.3 System Appears to Hang with High System CPU Usage
The SAP HANA database is an in-memory database and by its nature it consumes large amounts of memory. Some performance issues of SAP HANA can be caused by the operating system's memory management features.
For this case, you can see high usage of SYSTEM CPU that can be monitored in the Performance Monitor , available from SAP HANA cockpit Monitoring and Administration CPU Usage .
You can begin an analysis of CPU related problems by running a Kernel Profile trace either:
- via the SQL console (see ALTER SYSTEM START KERNEL PROFILER statement)
- in hdbcons as described in KBA 1804811 SAP HANA Database: Kernel Profiler Trace .
The kernel profiler trace is required for analysis by SAP Support. Refer to the topic HANA System-wide Performance Analysis for how to analyze the kernel profiler trace. Refer to KBA 2222250 - FAQ: HANA Workload Management which gives guidance on CPU-related configuration settings.
Root cause: Problem caused by the configuration of transparent huge page
## Required action:
1. Check Transparent Huge Page whether it is set to [never] by running the command cat /sys/ kernel/mm/transparent_hugepage/enabled .
2. Apply KBA 2031375 - SAP HANA: Transparent HugePages (THP) setting on Linux .
Root cause: Problem caused by the configuration of OS page cache
## Required action:
1. Check sar file ( /var/log/sa ) whether kbcached usage ( sar -r ) is higher than 10% of physical memory and high page in/out occurred.
2. Check and apply SAP Note 1557506 - Linux paging improvements .
Root cause: Problem caused by translation lookaside buffer (TLB) shootdown
## Required action:
1. Check plan trace.
Root cause : Due to high context switches (High SYS CPU) by many SqlExecutor threads
## Required action:
1. Check Performance Monitor and indexserver.ini ->= sql ->= sql_executors / max_sql_executors and refer to Controlling Parallelism of SQL Statement Execution .
## Related Information
Transparent Huge Pages on Linux [page 204]
System Hanging Situations [page 204] HANA System-wide Performance Analysis [page 46] Controlling Parallel Execution of SQL Statements [page 87]
```
SAP Note 2031375 SAP Note 1557506 SAP Note 2222250 SAP Note 1804811
```
|
## 2.4.1.4 Slower Response with High User CPU Usage
|
## 2.4.1.4 Slower Response with High User CPU Usage
The performance may degrade with increased usage of the CPU and applications.
Root cause: Not many executor threads but high CPU in a few nodes and a few tables accessed
Required Action: In an SAP Business Warehouse system, check for non-even partitioning of huge column tables. For more information, see SAP Note 1819123 - BW on SAP HANA SP5: landscape redistribution and Indicator for Large Delta Storage of Column Store Tables .
Root Cause: Performance degradation by huge MVCC versions
Required Action: Check for KPI Active Version in the Performance Monitor to find the MVCC garbage blocker, then kill it via the Threads tile on the Overview page. For more information, see Troubleshooting Blocked Transactions .
Refer also to the section 'Analysis of Former Performance Problems' in the topic HANA System-wide Performance Analysis.
## Related Information
Indicator for Large Delta Storage of Column Store Tables [page 131]
Blocked Transactions [page 167]
HANA System-wide Performance Analysis [page 46]
SAP Note 1819123
|
## 2.4.2 Slow Individual SQL Statements
|
## 2.4.2 Slow Individual SQL Statements
This section looks at the causes of slow individual SQL statements although there is no significant performance issue on system level and the associated troubleshooting steps.
If the following doesn't help to resolve the problem, see Getting Support . In this case, to analyze further, collect the explain plan, plan visualizer file, performance trace and catalog export. Also refer to SQL Statement Analysis and Query Plan Analysis for more information. SAP KBA 2000002 - FAQ: SAP HANA SQL Optimization explains general information about SQL optimization.
## Related Information
```
SQL Statement Analysis [page 238] Query Plan Analysis [page 248] SAP Note 2000002 Getting Support
```
|
## 2.4.2.1 A Statement is Sometimes Slow and Sometimes Fast
|
## 2.4.2.1 A Statement is Sometimes Slow and Sometimes Fast
There are a number of things to check when you experience inconsistent query execution time.
Check the following possibilities:
Root Cause: Same query shows different execution plans according to the HANA SQL Plan Cache.
Required Action: Analyze the difference in the execution plan by using the Explain Plan tool as outlined in SAP Note 2410208 Collect Explain Plan of a Prepared Statement .
Once you have found the corresponding statement hash for a problematic query, you can check how many different plans are stored in the Plan Cache by running the following query:
```
SELECT PLAN_ID, STATEMENT_HASH FROM M_SQL_PLAN_CACHE WHERE STATEMENT_HASH = '<statement_hash>'
```
Typically, the result will show multiple rows for a single statement hash value each with a different PLAN_ID value. Using the Plan IDs listed in the result you can execute the statements given in SAP Note 2410208 to display the execution plan and identify the differences there.
Additionally, you can check why a new execution plan was generated by selecting the column LAST_INVALIDATION_REASON. The reasons mentioned there are discussed in SAP KBA 2124112 FAQ: SAP HANA Parsing ('How can I determine the reason for a statement recompilation?')
If you want to prevent this from happening consider using the Plan Stability feature which captures the execution plans of the SQL statements and applies them later when the statements are compiled again. In this way Plan Stability can provide consistent performance across different revisions. You can use Plan Stability in SAP HANA Cockpit or from the command line as described in the SQL Plan Stability section of this guide. The following SAP Note gives additional information: 2639193 SAP HANA SQL Plan Stability .
Root Cause: If a related table was unloaded, it takes some time to load tables
Required Action: Check unload trace and execute after table loaded fully. You can refer to LOADED column of m_CS_TABLES.
Root Cause: Query compilation time is long.
Required Action: Check the execution time after adding 'with hint (ignore_plan_cache)' at the end of query. This hint will always cause the query to be compiled. If a long running compiled query plan has been evicted frequently from the plan cache, increase the query cache size. For more information, see SQL Plan Cache Analysis .
Root Cause: Merge status of column table can affect query plan
Required Action: Check MEMORY_SIZE_IN_DELTA, RAW_RECORD_COUNT_IN_DELTA, and LAST_MERGE_TIME columns of m_CS_TABLES whether there is large amount of data in delta. Check m_DELTA_MERGE_STATISTICS to see when the last merge occurred. For more information, see Delta Merge .
## Related Information
SQL Plan Cache Analysis [page 185]
```
Delta Merge [page 129] SQL Plan Stability [page 284] SQL Plan Stability (SAP HANA Cockpit) SAP Note 2410208 SAP Note 2124112 SAP Note 2639193
```
|
## 2.4.2.2 A Statement is Slower After an Upgrade
|
## 2.4.2.2 A Statement is Slower After an Upgrade
After upgrade, the query execution time can be different because of changes in the query execution plan.
Root cause: After an upgrade, a query can have a different plan, which leads to a different execution time.
Required Action: If you have an instance running on an older revision, compare the plan and collect the plan visualizer file. See Getting Support for further help.
Refer also to the SQL Plan Stability section of this guide; this feature offers the option to preserve a query's execution plan by capturing an abstraction of the plan and reusing it after the upgrade to regenerate the original plan and retain the original performance.
For more information, see Expensive SQL Statements .
## Related Information
Expensive SQL Statements [page 77]
```
Analyzing SQL Execution with the Plan Visualizer [page 253] SQL Plan Stability [page 284] Getting Support
```
|
## 2.4.2.3 A Query on Multiple Nodes Can Be Slower
|
## 2.4.2.3 A Query on Multiple Nodes Can Be Slower
In distributed systems, query execution can be routed to other nodes for better performance. However, there is a chance of having slow performance in the case where the network used for transferring intermediate results generated during query execution is slow or where there is an inefficient network configuration.
Root cause: A misconfigured network can lead to slow queries.
Required Action: Check your network configuration and its bandwidth/latency among SAP HANA servers. For more information see Network View and SAP Note 2183363 - Configuration of SAP HANA internal network .
Root cause: Statement routing and huge data transfer among distributed nodes can cause differences of query execution times due to the difference of anchor nodes.
Required Action: Check how much data is transferred among distributed nodes and the network performance. You can use the PlanViz Tool to check which nodes in the network are involved during the execution of the query and how much data is transferred (see Overview Page, Plan Viz). The KPI values for the distribution show:
- Number of nodes
- Number of network transfers
- Network traffic
Consider the locations of joined tables to reduce transferred intermediate result size.
## Related Information
Network View [page 261]
Performance Trace [page 289]
Overview Page [page 256]
SAP Note 2183363
|
## 2.4.2.4 Slow Select for all Entries (FAE) Query
|
## 2.4.2.4 Slow Select for all Entries (FAE) Query
There are a number of points to check if you have performance issues with SELECT FOR ALL ENTRIES (FAE) from an ABAP query.
For FAE on SAP HANA, please generally refer to SAP Note 1662726 - Optimization of select with FOR ALL ENTRIES on SAP HANA database .
Root cause: Indexes are missing.
Required Action: Check WHERE clause and check concat indexes for all fields used in WHERE clause.
Root cause: Due to DBSL behavior, slower operator can be chosen.
Required Actions: Apply parameters for ABAP optimization. For more information, see SAP Note 1987132 SAP HANA: Parameter setting for SELECT FOR ALL ENTRIES .
Root cause: When using less than or greater than ('<' or '>=') filters in FAE query, it can be slower than having no filter.
Required Actions: Do not use less than or greater than ('<' or '>=') filters in an FAE query.
## Related Information
```
SAP Note 1662726 SAP Note 1987132
```
|
## 2.4.2.5 All Statements Accessing a Specific Table are Slow
|
## 2.4.2.5 All Statements Accessing a Specific Table are Slow
In case queries run on specific tables are slow, check if there are too many versions.
Root cause: If there are too many versions of single records, accessing the table can be slow. In this case, the number of system-wide MVCC versions is in acceptable range. To verify further whether there are too many versions for a specific table, check the result of this query:
```
SELECT * FROM M_RS_TABLE_VERSION_STATISTICS where table_name='mytable';
```
This can be caused by a cursor unnecessarily being held on a query result or a long-lived transaction without a commit/rollback.
Required Action: Applications should commit as early as possible or close any cursors that are not needed. Check the application logic to see whether it really needs to update single records frequently.
|
## 2.4.3 Frequent Out of Memory (OOM)
|
## 2.4.3 Frequent Out of Memory (OOM)
If Out Of Memory situations happen frequently, it can also lead to performance drop by unloading tables or shrinking memory jobs.
First check Memory Problems and SAP KBA 1999997 - FAQ: SAP HANA Memory as they provide information on SAP HANA memory and its problems.
This section introduces common problems and their troubleshooting steps.
## Related Information
Memory Problems [page 65] SAP Note 1999997
|
## 2.4.3.1 Out of Memory Caused by Sudden Increased Memory Usage
|
## 2.4.3.1 Out of Memory Caused by Sudden Increased Memory Usage
Check the memory consumption of statements in the event of OOMs caused by suddenly increased memory usage.
Root cause : Huge intermediate results during query processing.
Required Actions: Enable memory tracking by setting the following parameters to on in the global.ini file resource_tracking section.
- enable_tracking = on
- memory_tracking = on
Enable the Expensive Statement Trace by setting the status to Active .
Then, check the memory consumption of statements using m_EXPENSIVE_STATEMENTS.MEMORY_SIZE. After your analysis you can optimize any problematic queries that were found.
|
## 2.4.3.2 Out of Memory Caused by Continuously Increased Memory Usage
|
## 2.4.3.2 Out of Memory Caused by Continuously Increased Memory Usage
Check if many statements trigger an Out Of Memory in a system where used memory is continuously increased.
Root cause: Commit/rollback within stored procedure can lead to memory leakages. Do not use exec('commit') or exec('rollback') within a stored procedure. If this syntax is used, the system cannot reclaim the memory used for query execution because its related transactions are left hanging.
Required Actions: Remove exec('commit') or exec('rollback'). If you would like to use commit/rollback within stored procedure, see SAP HANA SQLScript Reference for more information.
Root cause: Due to memory leakage caused by a programming error
Required Action: Check the Performance Monitor in SAP HANA cockpit Overview Memory Usage to determine whether used memory continuously increases without a significant increase in data size. If you find a suspicious component which keeps allocating memory, create a support ticket attaching a full system dump, mm trace, and the output of _SYS_STATISTICS.HOST_HEAP_ALLOCATORS_BASE.
## Related Information
SAP HANA SQLScript Reference
|
## 2.4.3.3 Out of Memory While High Usage Of Column Store Components' Allocators
|
## 2.4.3.3 Out of Memory While High Usage Of Column Store Components' Allocators
If a system is undersized, Out Of Memory (OOM) can happen frequently.
Root cause:
Undersized memory
## Required Action:
1. Check top allocators in [MEMORY_OOM] section of OOM dump to see whether they are for column store components as described in section 13 of KBA 1999997 - FAQ: SAP HANA Memory .
2. Check the unload trace whether frequent unloading of tables took place.
3. Reduce the amount of data in column store or increase physical memory.
## Related Information
SAP Note 1999997
|
## 2.4.3.4 Out of Memory Caused by Large Memory Usage of Statistics Server
|
## 2.4.3.4 Out of Memory Caused by Large Memory Usage of Statistics Server
This case can happen if the majority of memory used by the statisticsserver is due to many alerts or undersized memory.
Root cause: Due to big STATISTICS_ALERTS_BASE table size, an OOM can occur.
Required Action: Check table size of _SYS_STATISTICS.STATISTICS_ALERTS_BASE and truncate STATISTICS_ALERTS_BASE from hdbsql based on solution from SAP Note 2170779 - SAP HANA DB: Big statistics server table leads to performance impact on the system .
Root cause: Big Pool/Statistics allocator size
Required Action: Check SAP Note 2147247 - FAQ: SAP HANA Statistics Server first.
## Related Information
SAP Note 2170779
SAP Note 2147247
|
## 2.4.3.5 Out of Memory Occurs due to High Usage of Shared Memory
|
## 2.4.3.5 Out of Memory Occurs due to High Usage of Shared Memory
Shared memory is space where system information and row store tables are stored.
Check the following if the used amount of shared memory is high.
Root cause: Severely fragmented row store tables
## Required action:
1. Check whether SHARED_MEMORY in [MEMORY_OOM] ->= IPMM short info of OOM dump is unusally high.
2. Apply SAP Note 1813245 - SAP HANA DB: Row store reorganization .
Root cause: Memory shortage is caused by high usage of memory of row store tables in an SAP Business Warehouse (BW) system
Required action: In an SAP Business Warehouse system the used amount of shared memory is high and SAP Note 1813245 doesn't recommend row store reorganization, first apply SAP Note 706478 - Preventing Basis tables from increasing considerably , then apply SAP Note 1813245 - SAP HANA DB: Row store reorganization again.
Root cause: Memory shortage is caused by high usage of memory of row store tables in non-SAP Business Warehouse (BW) systems
Required Action: Check if you can convert some row store tables into column store tables or archive old data to reduce the memory size, or else increase the system memory.
## Related Information
SAP Note 1813245
SAP Note 706478
|
## 2.4.4 Table Consistency Check
|
## 2.4.4 Table Consistency Check
This section gives basic information for solving problems related to the Table Consistency Check.
The table consistency check is a procedure available in the SAP HANA database that performs a range of consistency check actions on database tables. It can be run from the command line or scheduled within the statistics service. Alert #83 Table Consistency is generated if the consistency check detects a given number of errors.
## Monitoring Views
Results of all consistency checks, whether executed manually or scheduled in the statistics service, are available in two monitoring views:
- m_CONSISTENCY_CHECK_HISTORY
- m_CONSISTENCY_CHECK_HISTORY_ERRORS
The first view gives high level information about parameters used for the check, runtime duration and the total number of tables with errors; each run is identified by a CHECK_EXECUTION_ID value. The errors table lists and gives details of all errors found within each check run.
Additionally, the monitoring view m_CS_TABLES, holds values for: LAST_CONSISTENCY_CHECK_TIME, LAST_CONSISTENCY_CHECK_ERROR_COUNT.
## Common Errors
If you encounter errors when running the table consistency check you should first try to rerun the check as some errors may only be due to timing issues related to the current workload and would not occur again if the table consistency check is repeated.
If the same error does recur check the following trace files:
- Database trace file available in SAP HANA Studio or Database Explorer: <service>=_<host>=.<port>=.<counter>=.trc
- Dedicated trace file: <service>=_<host>=.<port>=.table_consistency_check.<timestamp>=.trc. For this trace file the parameter enable_table_consistency_check_trace must be enabled.
If necessary, increase the trace level to debug to get sufficient diagnostic information:
```
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('trace', 'table_consistency_check') = 'debug'
```
Search the trace file for any errors and make a note of the error code. This information will be helpful if it is finally necessary to contact SAP Support for assistance.
## More Information
For background information see Table Consistency Check in the SAP HANA Administration Guide . Refer also to the following SAP Notes:
- 2116157 FAQ: SAP HANA Consistency Checks and Corruptions
- 1977584 Technical Consistency Checks for SAP HANA Databases
## Related Information
SAP Note 2116157
SAP Note 1977584
|
## 3 Root Causes and Solutions
|
## 3 Root Causes and Solutions
This section provides detailed information on the root causes of problems and their solutions.
System alerts are a good indicator for the underlying problem. The SAP Notes you will be directed to are a source of background information, explanations, alternative options, FAQs or useful SQL statements, for example. Detailed monitoring and administration of the SAP HANA databases is possible via the SAP HANA cockpit and the SAP HANA database explorer.
|
## 3.1 Memory Problems
|
## 3.1 Memory Problems
This section discusses the analysis steps that are required to identify and resolve memory related issues in the SAP HANA database.
For general information on SAP HANA memory management see the SAP HANA Academy video SAP HANA Memory Management which discusses the memory concept and comments on the difference between used, allocated, and resident Memory.
Alerts related to memory problems and corresponding SAP Notes are documented in the Alerts reference table (see category 'Memory'). SAP Note 1840954 - Alerts related to HANA memory consumption includes information on how to analyze out-of-memory (OOM) dump files.
The SAP HANA Administration Guide gives details on using the tool SAP HANA cockpit to analyze memory problems.
In order to understand the current and historic SAP HANA memory consumption you can use the following tools and approaches:
- Memory information in SAP HANA cockpit
- Memory information from logs and traces
- Memory information from SQL commands
- Memory information from other tools (see the tools overview in the SAP HANA Administration Guide ).
## Related Information
SAP Note 1840954
Alerts Reference [page 302]
SAP HANA Administration Guide
Video HANA Academy: SAP HANA Memory Management
|
## 3.1.1 Memory Information in SAP HANA Cockpit
|
## 3.1.1 Memory Information in SAP HANA Cockpit
There are a number of sources of information in SAP HANA cockpit that can assist you in understanding memory utilization.
- Open the Manage Services page from the Overall Database Status tile for high-level information about physical memory, allocation limit, and used memory for each service.
- To get a graphical overview about physical memory, allocation limit, used memory, and resident memory open the Performance Monitor from the Memory Usage tile.
- Open the Memory Analysis app from the Memory Usage tile for details about memory utilization as well as history information. For example, click the Components tab in the Memory Analysis app to view the used memory grouped by different components like "Statement Execution & Intermediate Results" or "Column Store Tables". When you choose a component, the corresponding historic information of memory usage is displayed by a graph.
|
## 3.1.2 Memory Information from Logs and Traces
|
## 3.1.2 Memory Information from Logs and Traces
In case of critical memory issues you can often find more detailed information in logs and trace files.
- Try to identify memory-related errors in the alert trace files in the SAP HANA database explorer (accessible via the View trace and diagnostic files link). Search for the strings 'memory' , 'allocat' , or 'OOM' (caseinsensitive).
- Check if an out-of-memory (OOM) trace file was created (users of SAP HANA Studio may need to view some trace files at the operating system level - see SAP Note 2573851 OOM rtedump file missing in HANA Studio ).
- Investigate error messages seen on the application side that occurred at times of high memory usage. If the application is an SAP NetWeaver system, good starting points for analysis are System Log (SM21), ABAP Runtime Error (ST22), and Job Selection (SM37).
If help from SAP Customer Support is needed to perform an in-depth analysis, the following information is valuable and should be added to the ticket:
- Diagnosis information (full system info dump). To collect this information, see section Diagnosis Information .
- Performance trace provides detail information on the system behavior, including statement execution details. The trace output is written to a trace file perftrace.tpt, which must be sent to SAP Customer Support. Please note that the trace must be captured while the issue is present or while reproducing the issue. To enable this trace, see section Performance Trace under Additional Analysis Tools for Support.
If specific SAP HANA system components need deeper investigation, SAP Customer Support can ask you to raise the corresponding trace levels to INFO or DEBUG, rerun the query and then send the indexserver trace files to SAP Customer Support.
To do so choose Trace Configuration in the SAP HANA database explorer and launch the Database Trace wizard. The following illustration shows the example of enabling the join engine trace (join_eval). You can enter a search string and then select the component in the indexserver.ini file and change the System Trace Level to the appropriate value. Some trace components (such as debug trace details for join engine) can create many megabytes of trace information and may also require an increase of the values maxfiles and
maxfilesize in the [trace] section of the global.ini file (see also SAP Note 2629103 SQL Traces Stop Writing When it Exceeds the Maximum Filesize ).
Internal details about SQL statement execution can be collected by enabling the Executor Trace; this provides the highest level of detail and should only be activated for the short time of query execution. After capturing the trace details you can upload the trace file (extrace.py) to SAP Customer Support. This trace is enabled by activating a configuration parameter as described and illustrated here.
Open the Configuration of System Properties view, edit the parameter trace in the [pythontrace] section of the executor.ini file, and change its value to on . When you change the default value, you have the option to set
values at each specific layer. The trace parameter is off by default. Click Change Layer to turn the parameter on. You can then change the configuration value for a selected database and for a selected layer:
## Related Information
Diagnosis Information [page 293]
Performance Trace [page 289]
SAP Note 2629103
SAP Note 2573851
|
## 3.1.3 Memory Information from SQL Commands
|
## 3.1.3 Memory Information from SQL Commands
There are a number of ways to analyze memory usage based on pre-defined and modifiable SQL queries.
The Statement Library of SAP HANA database explorer provides a set of tabular views to display the memory consumption of loaded tables based on pre-defined SQL queries:
- The view Component Memory Usage shows the aggregated memory consumption in bytes for different heap memory service components, services, and ports. Order by the used memory size column and find the largest consumers. The following heap memory service components are available: 1) Column Store Tables, 2) Row Store Tables, 3) Statement Execution & Intermediate Results, 4) Monitoring & Statistical Data, 5) Caches, 6) System, 7) Code Size, 8) Stack Size.
- The view Schema Size of Loaded Tables displays the aggregated memory consumption of loaded tables in MB for different database schemas. The aggregation comprises both column store and row store tables. Order by the schema size column and find the largest consumers.
- The view Used Memory by Tables shows two values: the total memory consumption of all column store tables in MB and the total memory consumption of all row store tables in MB.
## Note
You can find this and other information in the Memory Analysis app of the SAP HANA cockpit. For more information, see Analyze Memory Statistics in the SAP HANA Administration Guide .
## SQL Statement Collection
SAP Note 1969700 - SQL Statement Collection for SAP HANA contains several commands that are useful to analyze memory-related issues. Based on your needs you can configure restrictions and parameters in the sections marked with /* Modification section */ .
Some of the memory-related statements which you may find useful are described here:
- HANA_Memory_Overview
- HANA_Memory_TopConsumers* - available in two versions depending on the release. The output of the statement is the same in both cases:
- HANA_Memory_TopConsumers_History (available in older versions of the statement collection)
- HANA_Memory_TopConsumers_TimeSlices (supersedes 'Consumers History' in versions SPS 04 and above)
- HANA_Tables_LargestTables
- HANA_Memory_SharedMemory
## HANA_Memory_Overview
This query gives an overview of current memory information showing key values in the following columns:
- NAME: Description
- TOTAL_GB: Total size (GB)
- DETAIL_GB: Size on detail level (GB) - this is shown at two levels with a breakdown at a second level - see the following table:
| NAME | TOTAL_GB | DETAIL_GB | DETAIL2_GB |
|--------------------------------------|------------|-----------------------------|---------------------------------|
| User-defined global allocation limit | not set | | |
| License memory limit | 256 | | |
| License usage | 143 | 124 (2014/03/01-2014/03/31) | |
| | | 143 (2014/04/01-2014/04/30) | |
| | | 113 (2014/05/01-2014/05/09) | |
| Physical memory | 256 | 256 (vhbshk0sdb) | |
| HANAinstance memory (allocated) | 113 | 113 (vhbshk0sdb) | |
| HANAinstance memory (used) | 85 | 85 (vhbshk0sdb) | |
| HANAshared memory | 23 | 23 (vhbshk0sdb) | |
| HANAheap memory (used) | 52 | 52 (vhbshk0sdb) | 10 (Pool/NameIdMapping/ RoDict) |
## HANA_Memory_TopConsumers_History / HANA_Memory_TopConsumers_TimeSlices
The output shows the areas in history with the highest memory requirements (column store and row store tables, heap, code, stack). The following columns contain the key values:
- SAMPLE_TIME: Timestamp
- KEY_FIGURE: Memory key figure
- VALUE_TOTAL: Total value of memory key figure
- DETAIL_<n>=: Top <n>= detail area related to memory key figure
- VALUE_<n>=: Memory key figure value of top <n>= detail area
- PCT_<n>=: Fraction of overall value occupied by top <n>= detail area (%)
VALUE_TOT
| SAMPLE_TIME | KEY_FIGURE | AL | DETAIL_1 | VALUE_1 | PCT_1 |
|-----------------|-----------------|---------|-------------------------------------------------------------|-----------|---------|
| 2014/04/22(TUE) | Space used (GB) | 408.55 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 85.94 | 21 |
| 2014/04/21(MON) | Space used (GB) | 382.82 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 90.44 | 24 |
| 2014/04/20(SUN) | Space used (GB) | 437.76 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 126.2 | 29 |
| 2014/04/19(SAT) | Space used (GB) | 513.7 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 133.29 | 26 |
| 2014/04/18(FRI) | Space used (GB) | 445.53 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 112.35 | 25 |
| 2014/04/17(THU) | Space used (GB) | 363.3 | Pool/RowEngine/QueryExecution | 72.54 | 20 |
| 2014/04/16(WED) | Space used (GB) | 487.59 | Pool/RowEngine/QueryExecution | 104.39 | 21 |
| 2014/04/15(TUE) | Space used (GB) | 588.56 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 168.21 | 29 |
| 2014/04/14(MON) | Space used (GB) | 3484.97 | Pool/JoinEvaluator/ JERequestedAttributes/Results | 2795.2 | 80 |
| 2014/04/13(SUN) | Space used (GB) | 572.9 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 175.6 | 31 |
| 2014/04/12(SAT) | Space used (GB) | 477.98 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 111.76 | 23 |
| 2014/04/11(FRI) | Space used (GB) | 491.72 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 119.74 | 24 |
| 2014/04/10(THU) | Space used (GB) | 463.47 | Pool/PersistenceManager/ PersistentSpace(0)/DefaultLPA/Page | 100.82 | 22 |
## HANA_Tables_LargestTables
This query provides an overview of current memory allocation by tables. The following list explains the columns displayed in the table:
- OWNER: Name of the table owner
- TABLE_NAME: Name of the table
- S: Table store ('R' for row store, 'C' for column store)
- HOST: Host name ('various' in case of partitions on multiple hosts)
- U: 'X' if at least one unique index exists for the table
- POS: Position of table in top list
- COLS: Number of table columns
- RECORDS: Number of table records
- SUm_DISK_GB: Total size on disk (in GB, table + indexes + LOB segments)
- SUm_MEm_GB: Total potential maximum size in memory (in GB, table + indexes + LOB segments)
| OWNER | TABLE_NAME | S | HOST | U | POS | COLS | RECORDS | SUM_DIS K_GB | SUM_ME M_GB |
|---------|------------------|-----|----------|-----|-------|--------|------------|----------------|---------------|
| SAPSR3 | /BIC/AZOCEUO0500 | C | various | X | 1 | 16 | 877829360 | 63.9 | 76.15 |
| SAPSR3 | /BIC/AZOCZZO0400 | C | various | X | 2 | 33 | 965035392 | 63.45 | 70.1 |
| SAPSR3 | RSMONMESS | R | erslha33 | X | 3 | 19 | 170801504 | 27.92 | 54.21 |
| SAPSR3 | /BIC/AZFIGLO1300 | C | various | X | 4 | 60 | 652633189 | 47.2 | 53.23 |
| SAPSR3 | /BIC/AZSCXXO4400 | C | various | X | 5 | 26 | 1251448665 | 47.78 | 53.04 |
| SAPSR3 | /BIC/AZOCEUO0800 | C | various | X | 6 | 17 | 911830438 | 37.86 | 52.42 |
| SAPSR3 | /BIC/AZOCZZO2000 | C | various | X | 7 | 34 | 1200422292 | 46.5 | 50.08 |
| SAPSR3 | RSWR_DATA | R | erslha33 | X | 8 | 10 | 20471 | 36.88 | 36.88 |
| SAPSR3 | RSRWBSTORE | C | erslha33 | X | 9 | 5 | 14483956 | 36.18 | 36.2 |
| SAPSR3 | /BIC/AZMIEUO0200 | C | various | X | 10 | 52 | 403915330 | 28.58 | 33.05 |
| SAPSR3 | /BIC/AZSCXXO2900 | C | various | X | 11 | 275 | 183029330 | 30.82 | 29.26 |
| SAPSR3 | /BIC/AZSCXXO4700 | C | various | X | 12 | 42 | 648103462 | 27.38 | 28.83 |
| SAPSR3 | /BIC/FZRREUC16B | C | erslha35 | | 13 | 122 | 258261262 | 26.43 | 24.99 |
| SAPSR3 | /BIC/AZOCEUO9000 | C | various | X | 14 | 16 | 251896248 | 20.53 | 23.71 |
| SAPSR3 | RSBMNODES | R | erslha33 | X | 15 | 12 | 130344869 | 13.67 | 20.25 |
| SAPSR3 | /BIC/AZSCXXO1400 | C | various | X | 16 | 279 | 164509638 | 18.49 | 19.82 |
| SAPSR3 | /BIC/AZOCEUO0300 | C | various | X | 17 | 27 | 577787981 | 17.95 | 19.6 |
| OWNER | TABLE_NAME | S | HOST | U | POS | COLS | RECORDS | SUM_DIS K_GB | SUM_ME M_GB |
|---------|------------------|-----|----------|-----|-------|--------|------------|----------------|---------------|
| SAPSR3 | EDI40 | R | erslha33 | X | 18 | 7 | 5733625 | 18.26 | 18.4 |
| SAPSR3 | /BIC/FZOCZZC20 | C | various | | 19 | 34 | 1427403108 | 18.97 | 17.8 |
| SAPSR3 | /BIC/AZSCXXO2600 | C | various | X | 20 | 306 | 95251083 | 16.65 | 16.97 |
| SAPSR3 | /BIC/AZSCXXO0800 | C | various | X | 21 | 266 | 120598787 | 18.76 | 15.62 |
| SAPSR3 | /BIC/AZSPXXO0200 | C | various | X | 22 | 48 | 270975902 | 12.63 | 15.3 |
| SAPSR3 | /BIC/AZOCZZO5000 | C | various | X | 23 | 33 | 215732874 | 14.16 | 14.92 |
| SAPSR3 | /BIC/AZSPXXO0300 | C | various | X | 24 | 56 | 275036362 | 13.09 | 14.77 |
| SAPSR3 | /BIC/AZOCEUO0600 | C | various | X | 25 | 16 | 663581081 | 12.29 | 14.34 |
| SAPSR3 | /BIC/AZOCZZO0700 | C | various | X | 26 | 41 | 350819182 | 15 | 14.32 |
| SAPSR3 | /BIC/FZRREUC16D | C | erslha40 | | 27 | 122 | 146620284 | 15.39 | 14.06 |
| SAPSR3 | /BIC/AZMDEUO0800 | C | various | X | 28 | 246 | 151145647 | 15.39 | 14 |
| SAPSR3 | /BIC/AZMIEUO1300 | C | various | X | 29 | 16 | 406548712 | 11.52 | 13.35 |
| SAPSR3 | /BIC/AZRREUO0100 | C | various | X | 30 | 167 | 202422848 | 15.36 | 13.24 |
## HANA_Memory_SharedMemory
This query shows currently used and allocated shared memory per host and service. The following list explains the columns displayed in the table:
- HOST: Host name
- PORT: Port name
- SERVICE_NAME: Service name
- SHm_ALLOC_GB: Allocated shared memory (GB)
- SHm_USED_GB: Used shared memory (GB)
- SHm_USED_PCT: Percentage of allocated memory used
| HOST | PORT | SERVICE_NAME | SHM_ALLOC_GB | SHM_USED_GB | SHM_USED_PCT |
|----------|--------|------------------|----------------|---------------|----------------|
| MyHost01 | 31001 | nameserver | 0.13 | 0.02 | 18.64 |
| MyHost01 | 31002 | preprocessor | 0 | 0 | 0 |
| MyHost01 | 31003 | indexserver | 24.5 | 11.21 | 45.76 |
| MyHost01 | 31005 | statisticsserver | 0.14 | 0.03 | 22.98 |
| HOST | PORT | SERVICE_NAME | SHM_ALLOC_GB | SHM_USED_GB | SHM_USED_PCT |
|----------|--------|----------------|----------------|---------------|----------------|
| MyHost01 | 31006 | webdispatcher | 0 | 0 | 0 |
| MyHost01 | 31007 | xsengine | 0.14 | 0.03 | 22.96 |
| MyHost01 | 31010 | compileserver | 0 | 0 | 0 |
## Related Information
SAP Note 1969700
Memory Analysis Using the SQL Statement Collection for Analysis and Health Checks [page 8]
|
## 3.1.4 Memory Information from Other Tools
|
## 3.1.4 Memory Information from Other Tools
Other tools are also available to analyze high memory consumption and out-of-memory situations.
A number of SAP Notes and 'How-to' documents are available to provide help with some of the most common questions and difficulties related to memory. The tool hdbcons provides expert functionality to analyze memory issues. You can use this tool (typically with guidance from the SAP Product Support team) to create runtime dump files and analyze the details of memory consumption. If necessary, dump files can be sent to Product Support for further analysis.
The following SAP Notes may be helpful in solving some problems and when analyzing memory issues with hdbcons .
- 1999997 FAQ: SAP HANA Memory
- 2400007 FAQ: SAP HANA Runtime Dumps
- 2222218 FAQ: SAP HANA Database Server Management Console (hdbcons)
- 1786918 Required information to investigate high memory consumption (hdbcons)
- 1813020 How to generate a runtime dump on SAP HANA
- 1984422 How-To: Analyzing SAP HANA Out-of-memory (OOM) Dumps
- How to troubleshoot HANA High Memory Consumption (Guided Answer)
## Tip
Guided Answers is a support tool for troubleshooting problems using decision trees. A guided answer is available for How to troubleshoot HANA High Memory Consumption .
## Related Information
```
SAP Note 2400007 SAP Note 2222218 SAP Note 1786918 SAP Note 1813020 SAP Note 1984422 How to troubleshoot HANA High Memory Consumption (Guided Answer)
```
|
## 3.1.5 Root Causes of Memory Problems
|
## 3.1.5 Root Causes of Memory Problems
Once you have completed your initial analysis, you have the information required to start the next phase of your analysis.
Based on the results from the analysis approaches you are now able to answer the following questions:
- Is it a permanent or a sporadic problem?
- Is the memory consumption steadily growing over time?
- Are there areas with critical memory consumption in heap, row store or column store?
- Is there a big difference between used memory and allocated memory?
In the following you can find typical root causes and possible solutions for the different scenarios.
A valuable tool for analyzing memory problems is the Expensive Statements Trace which is useful in cases where individual statements seem to exhaust the system's memory. This is described separately in the Tools and Tracing section: Analyzing Expensive Statements Traces.
## Related Information
Analyzing Expensive Statements Traces [page 243]
|
## 3.1.5.1 Significant External Memory Consumption
|
## 3.1.5.1 Significant External Memory Consumption
If the database resident memory of all SAP HANA databases on the same host is significantly smaller than the total resident memory, you have to check which processes outside of the SAP HANA databases are responsible for the additional memory requirements.
Typical memory consumers are:
- Operating system (for example, caches, mapping structures)
- Third party tools (for example, backup, virus scanner)
How to identify top memory consumers from non-SAP HANA processes is out of scope of this guide. However, when you are able to identify the reason for the increased memory consumption of the external program, you can check if it is possible to optimize its configuration.
|
## 3.1.5.2 Space Consumed by Large Tables
|
## 3.1.5.2 Space Consumed by Large Tables
If particularly large tables consume significant amounts of space in the row store or column store, you should check if the amount of data can be reduced.
The following references will be helpful:
- SAP Note 2388483 - How To: Data Management for Technical Tables describes archiving and deletion strategies for typical SAP tables with a technical background; for example, tables required for communication, logging or administration.
- General recommendations for managing data can be found on the Information Lifecycle Management page.
For more information on memory management for resident table data, see Managing Tables in the SAP HANA Administration Guide and the following SAP Notes:
- SAP Note 2222277 - FAQ: SAP HANA Column Store and Row Store
- SAP Note 2220627 - FAQ: SAP HANA LOBs
- SAP Note 2388483 - How-To: Data Management for Technical Tables
## Related Information
```
https://www.sap.com/products/information-lifecycle-management.html Managing Tables SAP Note 2222277 SAP Note 2220627 SAP Note 2388483
```
|
## 3.1.5.3 Internal Columns in the Column Store
|
## 3.1.5.3 Internal Columns in the Column Store
For several reasons, SAP HANA creates internal columns in the column store. Some column store tables are automatically loaded into memory.
## Internal Columns
You may be able to optimize or remove internal columns in order to reduce memory usage. In some situations a cleanup is possible, for example, in the case of CONCAT attribute columns that were created in order to support joins. For more information see SAP Note 1986747: How-To: Analyzing Internal Columns in SAP HANA Column Store .
## Column Store Table Loads and Unloads
The SAP HANA system dynamically loads column store tables into memory during system restart and when required by the application. You may be able to optimize the number of pre-loaded tables. For more information, see SAP Note 2127458: FAQ: SAP HANA Loads and Unloads .
## Related Information
```
SAP Note 2127458 SAP Note 1986747
```
|
## 3.1.5.4 Memory Leaks
|
## 3.1.5.4 Memory Leaks
A memory leak is a memory area (typically a heap allocator) that grows over time without any apparent reason.
If you have identified a suspicious area, proceed as follows:
- Check for SAP Notes that describe the memory leak and provide a solution.
- Check if the problem is reproducible with a recent SAP HANA revision.
- If you can't resolve the problem yourself, open an SAP customer message and use the component HANDB.
Before you open a Support incident refer to SAP Note 1786918 Required information to investigate high memory consumption .
Information about a specific memory area can be obtained from the output of the following hdbcons command giving the name of the heap allocator as a parameter. This information is also particularly helpful to the Support team when analyzing memory problems.
```
hdbcons "mm -bl <allocator_name>"
```
## Related Information
```
SAP Note 1786918 Problem Analysis Using hdbcons
```
|
## 3.1.5.5 Large Heap Areas
|
## 3.1.5.5 Large Heap Areas
Some heap areas can be larger than necessary without being a memory leak.
SAP Note 1840954 - Alerts Related to HANA Memory Consumption contains an overview of heap allocators with a potentially large memory consumption and possible resolutions.
Refer also to SAP Note 1999997 - FAQ: SAP HANA Memory .
## Related Information
SAP Note 1840954
|
## 3.1.5.6 Expensive SQL Statements
|
## 3.1.5.6 Expensive SQL Statements
SQL statements processing a high amount of data or using inefficient processing strategies can be responsible for increased memory requirements.
See SQL Statement Analysis for information on how to analyze expensive SQL statements during times of peak memory requirements.
## Related Information
SQL Statement Analysis [page 238]
Setting a Memory Limit for SQL Statements [page 79] Analyzing Expensive Statements Traces [page 243]
|
## 3.1.5.7 Memory Consumption Related to Transactional Problems
|
## 3.1.5.7 Memory Consumption Related to Transactional Problems
High memory consumption can be caused by problems with transactions.
In some cases, high memory consumption is caused by wait situations, which can have different reasons:
- Long-running or unclosed cursors,
- Blocked transactions,
- Hanging threads.
As one of the negative impacts, used memory is not released any more. In particular, the number of table versions can grow up to more than 8,000,000 which is considered the amount where an action is required.
For more information, see the separate section Transactional Problems .
## Related Information
Transactional Problems [page 167]
|
## 3.1.5.8 Used Space Much Smaller than Allocated Space
|
## 3.1.5.8 Used Space Much Smaller than Allocated Space
In order to optimize performance by minimizing the memory management overhead or due to fragmentation, SAP HANA may allocate additional memory rather than reusing free space within the already allocated memory.
This can lead to undesired effects that the SAP HANA memory footprint increases without apparent need.
The SAP HANA license checks against allocated space, so from a licensing perspective it is important to keep the allocated space below the license limit.
In order to limit the amount of allocated space, you can set the parameter global_allocation_limit to a value not larger than the maximum memory that should be allocated.
See Set the global_allocation_limit Parameter in the SAP HANA Administration Guide .
## Related Information
Change the Global Memory Allocation Limit
|
## 3.1.5.9 Fragmentation
|
## 3.1.5.9 Fragmentation
Fragmentation effects are responsible for inefficiently used memory. They can occur in different areas.
In order to minimize fragmentation of row store tables you can proceed as follows:
- If the fragmentation of row store tables in the shared memory segments of indexserver processes reaches 30% and the allocated memory size is greater than 10GB, a table redistribution operation is needed.
SAP Note 1813245 - SAP HANA DB: Row Store reorganization describes how to determine fragmentation and perform a table redistribution.
## Related Information
SAP Note 1813245
|
## 3.1.5.10 Large Memory LOBs
|
## 3.1.5.10 Large Memory LOBs
LOB (Large Object) columns can be responsible for significant memory allocation in the row store and column store if they are defined as memory LOBs.
To check for memory LOBs and switch to hybrid LOBs see SAP Note 1994962 - Activation of Hybrid LOBs in SAP HANA .
## Related Information
```
SAP Note 1994962
```
|
## 3.1.5.11 Large Delta Store
|
## 3.1.5.11 Large Delta Store
The delta store can allocate a significant portion of the column store memory.
You can identify the current size of the delta store by running the SQL command: HANA_Tables_ColumnStore_Overview ( SAP Note 1969700 - SQL Statement Collection for SAP HANA ). If the delta store size is larger than expected, proceed as described in the section Delta Merge .
## Related Information
```
SAP Note 1969700 Delta Merge [page 129]
```
|
## 3.1.5.12 Undersized SAP HANA Memory
|
## 3.1.5.12 Undersized SAP HANA Memory
If a detailed analysis of the SAP HANA memory consumption didn't reveal any root cause of increased memory requirements, it is possible that the available memory is not sufficient for the current utilization of the SAP HANA database.
In this case you should perform a sizing verification and make sure that sufficient memory is installed on the SAP HANA hosts.
|
## 3.1.5.13 Setting a Memory Limit for SQL Statements
|
## 3.1.5.13 Setting a Memory Limit for SQL Statements
You can set a statement memory limit to prevent single statements from consuming too much memory.
## Prerequisites
To apply these settings you must have the system privilege INIFILE ADMIN.
For these options, enable_tracking and memory_tracking must first be enabled in the global.ini file. Additionally, resource_tracking must be enabled in this file if you wish to apply different settings for individual users (see Procedure below).
## Context
You can protect an SAP HANA system from uncontrolled queries consuming excessive memory by limiting the amount of memory used by single statement executions per host. By default, there is no limit set on statement memory usage, but if a limit is applied, statement executions that require more memory will be aborted when they reach the limit. To avoid canceling statements unnecessarily you can also apply a percentage threshold value which considers the current statement allocation as a proportion of the global memory currently available. Using this parameter, statements which have exceeded the hard-coded limit may still be executed if the memory allocated for the statement is within the percentage threshold. The percentage threshold setting is also effective for workload classes where a statement memory limit can also be defined.
You can also create exceptions to these limits for individual users (for example, to ensure an administrator is not prevented from doing a backup) by setting a different statement memory limit for each individual.
These limits only apply to single SQL statements, not the system as a whole. Tables which require much more memory than the limit applied here may be loaded into memory. The parameter global_allocation_limit limits the maximum memory allocation limit for the system as a whole.
You can view the (peak) memory consumption of a statement in m_EXPENSIVE_STATEMENTS.MEMORY_SIZE.
## Procedure
1. Enable statement memory tracking.
In the global.ini file, expand the resource_tracking section and set the following parameters to on :
- enable_tracking = on
- memory_tracking = on
2. statement_memory_limit - defines the maximum memory allocation per statement in GB. The parameter is not set by default.
- In the global.ini file, expand the memorymanager section and locate the parameter. Set an integer value in GB between 0 (no limit) and the value of the global allocation limit. Values that are too small can block the system from performing critical tasks.
- An option is also available to apply a limit in relation to the system's effective allocation limit. To do this, set the parameter to a value of '-1'. In this case a memory limit is applied calculated as 25% of the smaller of the global_allocation_limit and the process_allocation_limit.
- A value for this parameter may also be set during installation or upgrade by hdblcm.
- The value defined for this parameter can be overridden by the corresponding workload class property STATEMENT_MEMORY_LIMIT.
- When the statement memory limit is reached, a dump file is created with 'compositelimit_oom' in the name. The statement is aborted, but otherwise the system is not affected. By default only one dump file is written every 24 hours. If a second limit hits in that interval, no dump file is written. The interval can be configured in the memorymanager section of the global.ini file using the oom_dump_time_delta parameter, which sets the minimum time difference (in seconds) between two dumps of the same kind (and the same process).
After setting this parameter, statements that exceed the limit you have set on a host are stopped by running out of memory.
3. statement_memory_limit_threshold - defines a percentage of the global allocation limit. Parameter statement_memory_limit is respected only if total used memory exceeds this threshold. The default value is 0% (of the global_allocation_limit) so statement_memory_limit is always respected.
- In the global.ini file, expand the memorymanager section and set the parameter as a percentage of the global allocation limit.
- This parameter provides a means of controlling when the statement_memory_limit is applied. If this parameter is set, when a statement is issued the system will determine if the amount of memory it consumes exceeds the defined percentage value of the overall global_allocation_limit parameter setting. The statement memory limit is only applied if the current SAP HANA memory consumption exceeds this statement memory limit threshold as a percentage of the global allocation limit.
- This is a way of determining if a particular statement consumes an inordinate amount of memory compared to the overall system memory available. If so, to preserve memory for other tasks, the statement memory limit is applied and the statement fails with an exception.
- Note that the value defined for this parameter also applies to the workload class property STATEMENT_MEMORY_LIMIT.
4. total_statement_memory_limit - a value in gigabytes to define the maximum memory available to all statements running on the system. The default value is 0 (no limit).
- This limit does not apply to users with the administrator role SESSION ADMIN or WORKLOAD ADMIN who need unrestricted access to the system. However, a check of the user's privileges allowing the administrator to by-pass the limit is only made for the first request when a connection is made. The privileged user would have to reconnect to be able to bypass the statement memory limit again (see also Admission Control).
- The value defined for this parameter cannot be overridden by the corresponding workload class property TOTAL_STATEMENT_MEMORY_LIMIT.
- There is a corresponding parameter for use with system replication on an Active/Active (read enabled) secondary server. This is required to ensure that enough memory is always available for essential log shipping activity. See also sr_total_statement_memory_limit in section Memory Management .
5. User parameters can limit memory for statements. For further information, refer to Setting User Parameters for Workload .
## Results
The following example and scenarios show the effect of applying these settings:
Example showing statement memory parameters
| Parameter | Value |
|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Physical memory | 128GB |
| global_allocation_limit | The unit used by this parameter is MB. The default value is: 90%of the first 64 GBof available physical memory on the host plus 97%of each further GB; or, in the case of small physical memory, physical memory minus 1 GB. |
| Parameter | Value |
|----------------------------------|----------------------------------------------|
| statement_memory_limit | 1 GB(the unit used by this parameter is GB.) |
| statement_memory_limit_threshold | 60% |
## Scenario 1 :
A statement allocates 2GB of memory and the current used memory size in SAP HANA is 50GB.
- 0,9 * 128GB = 115,2 (global allocation limit)
- 0,6 * 115,2 = 69,12 (threshold in GB)
- 50 GB < 69,12 GB (threshold not reached)
The statement is executed, even though it exceeds the 1GB statement_memory_limit .
## Scenario 2 :
A statement allocates 2GB and the current used memory size in SAP HANA is 70GB
- 70 GB >= 69,12 GB (threshold is exceeded)
The statement is cancelled, as the threshold is exceeded, the statement_memory_limit is applied.
## Related Information
Change the Global Memory Allocation Limit
Memory Management Setting User Parameters for Workload Managing Peak Load (Admission Control)
|
## 3.2 CPU Related Root Causes and Solutions
|
## 3.2 CPU Related Root Causes and Solutions
This section covers the troubleshooting of high CPU consumption on the system.
A constantly high CPU consumption will lead to a considerably slower system as no more requests can be processed. From an end user perspective, the application behaves slowly, is unresponsive or can even seem to hang.
Note that a proper CPU utilization is actually desired behavior for SAP HANA, so this should be nothing to worry about unless the CPU becomes the bottleneck. SAP HANA is optimized to consume all memory and CPU available. More concretely, the software will parallelize queries as much as possible in order to provide optimal performance. So if the CPU usage is near 100% for a query execution, it does not always mean there is an issue. It also does not automatically indicate a performance issue.
|
## 3.2.1 Indicators of CPU Related Issues
|
## 3.2.1 Indicators of CPU Related Issues
CPU related issues are indicated by alerts issued or in views in the SAP HANA cockpit.
The following alerts may indicate CPU resource problems:
- Host CPU Usage (Alert 5)
- Most recent savepoint operation (Alert 28)
- Savepoint duration (Alert 54)
You notice very high CPU consumption on your SAP HANA database from one of the following:
- Alert 5 (Host CPU Usage) is raised for current or past CPU usage
- The CPU usage displayed in the CPU Usage tile on the Overview screen
- The Performance Monitor shows high current or past CPU consumption. Furthermore, the CPU usage of the host as well as the individual servers is displayed.
|
## 3.2.2 Analysis of CPU Related Issues
|
## 3.2.2 Analysis of CPU Related Issues
This section describes how to analyze high CPU consumption using tools in the SAP HANA cockpit and the command line.
When analyzing high CPU consumption, you need to distinguish between the CPU resources consumed by HANA itself and by other, non-SAP HANA processes on the host. While the CPU consumption of SAP HANA will be addressed here in detail, the CPU consumption of other processes running on the same host is not covered. Such situations are often caused by additional programs running concurrently on the SAP HANA appliance such as anti-virus and backup software. For more information see SAP Note 1730928 - Using external software in a HANA appliance .
## Analyzing CPU Consumption in Cockpit
A good starting point for the analysis is the Overview page in the SAP HANA cockpit. It contains a tile that displays CPU usage. If you click on that tile, the Performance Monitor opens and you can view the SAP HANA CPU usage versus total CPU usage. If SAP HANA CPU usage is low while total CPU usage is high, the issue is most likely related to a non-SAP HANA process.
To find out what is happening in more detail, open the Threads tile (see Thread Monitoring ). In order to prepare it for CPU time analysis, perform the following steps:
- To switch on resource tracking open the Configuration of System Properties monitor and in the resource_tracking section of the global.ini file set the enable_tracking parameter to on . See Memory Information from Logs and Traces .
- Display the CPU Time column in the Thread Monitor.
The Thread Monitor shows the CPU time of each thread running in SAP HANA in microseconds. A high CPU time of related threads is an indicator that an operation is causing the increased CPU consumption.
In order to identify expensive statements causing high resource consumption, turn on the Expensive Statement Trace and specify a reasonable runtime (see Expensive Statements Trace ). If possible, add further restrictive
criteria such as database user or application user to narrow down the amount of information traced. Note that the CPU time for each statement is shown in the column CPU_TIME if resource_tracking is activated.
## General Analysis Resources
The topic 'HANA System-wide Performance Analysis' describes a general approach which can also be applied for CPU related issues. This includes the following actions:
- Generating a runtime dump
- Creating a kernel profiler trace
- Using the HANA Dump Analyzer tool
You can enable and configure the kernel profiler in the SAP HANA Database Explorer (Trace Configuration) or you can manage the kernel profiler from the SQL command line using the ALTER SYSTEM command. In both cases RESOURCE ADMIN or TRACE ADMIN privileges are required. Note that setting a maximum duration or memory limit for profiling is good practice and should be used if appropriate values can be estimated. More information about this tool can be found in Kernel Profiler .
In addition to the runtime dump it may be possible to capture the current state of the system in a full system information dump for later analysis. However, this in itself requires resources and may therefore worsen the situation. To get a Full System Info Dump using SAP HANA cockpit, open Diagnosis Files via the link Manage full system information dumps under Alerting & Diagnostics and choose either a zip file from the list or create a new one via Collect Diagnostics . See also the topic 'Diagnosis Information' in the Tools and Tracing section.
## Tip
Guided Answers is a support tool for troubleshooting problems using decision trees. A guided answer is available for How to troubleshoot HANA High CPU Utilization .
## Related Information
SAP Note 1730928
Thread Monitoring
Memory Information from Logs and Traces [page 66]
Expensive Statements Trace [page 243]
HANA System-wide Performance Analysis [page 46]
Kernel Profiler [page 291]
Collect and Download Diagnosis Information
Diagnosis Information [page 293]
How to troubleshoot HANA High CPU Utilization (Guided Answer)
|
End of preview. Expand
in Data Studio
Please like my profile if you use this dataset 🥰
- Downloads last month
- 38