(DI-2302) Messages when monitoring HANA Expensive statements

Owned by SNP
Feb 02, 2023
2 min read

In case you see any of the below-mentioned messages when monitoring HANA Expensive statements, the configuration properties in the global.ini file need to be set up. Otherwise, the following KPIs for HANA Expensive statements are not collected:

  • HDB_SQL_EXP_STMT_DUR_NUM - Number of expensive SQL statements exceeding the time limit

  • HDB_SQL_EXP_STMT_NUM - Number of expensive statements exceeding the memory limit

1) Expensive statement monitoring is not enabled in the HANA config file

Monitoring of expensive statements is not enabled in HANA global configuration file. The collector is not able to monitor expensive statements when this configuration property is not defined or disabled.

Setup procedure

  1. Execute transaction DB02.

  2. Navigate to 'Configuration->INI files'

  3. Expand the 'INIFILE PARAMETER LIST' node

  4. Navigate to the following path: global.ini->expensive_statement->enable.

  5. Double-click the' enable' node

  6. Set the value to 'true'.

2) Duration threshold for expensive statement is not set in HANA config file

Missing configuration property 'threshold_duration' in HANA global configuration file for expensive statements on the system. The collector is not able to calculate the KPI on memory-expensive statements when this configuration property is not defined.

Setup procedure

  1. Execute transaction DB02

  2. Navigate to 'Configuration->INI files'

  3. Expand the 'INIFILE PARAMETER LIST' node

  4. Navigate to the following path: global.ini->expensive_statement->threshold_duration

  5. Double-click 'threshold_duration' node

  6. Set a valid system value that is greater than zero.

03) Resource tracking is not set in the HANA config file

Property for tracking resources is switched off in HANA global configuration file or not defined. The collector is not able to monitor expensive statements when this configuration property is switched off or not defined.

Setup procedure

  1. Execute transaction DB02

  2. Navigate to 'Configuration->INI files'

  3. Expand the 'INIFILE PARAMETER LIST' node

  4. Navigate to the following path: global.ini->resource_tracking->enable_tracking

  5. Double-click 'enable_tracking' node

  6. Set the system value to 'on'.

04) Memory tracking is not set in the HANA config file

The property for tracking memory is switched off in HANA global configuration file or not defined. The collector is not able to monitor expensive statements when this configuration property is switched off or not defined.

Setup procedure

  1. Execute transaction DB02

  2. Navigate to 'Configuration->INI files'

  3. Expand the 'INIFILE PARAMETER LIST' node

  4. Navigate to the following path: global.ini->resource_tracking->memory_tracking

  5. Double-click 'memory_tracking' node

  6. Set the system value to 'on'.

05) Memory threshold for expensive statement is not set in HANA config file

This message is not raised anymore since 2211 release.

Missing configuration property 'threshold_memory' in HANA global configuration file for expensive statements on the system. The collector is not able to calculate the KPI on memory-expensive statements when this configuration property is not defined.

Setup procedure

  1. Execute transaction DB02

  2. Navigate to 'Configuration->INI files'

  3. Expand the 'INIFILE PARAMETER LIST' node

  4. Navigate to the following path: global.ini->expensive_statement->threshold_memory

  5. Double-click 'threshold_memory' node

  6. Set a valid system value that is greater than zero.