Sap Hana Mini Check

Check ID Area Validity Description Analysis SQL statement (SAP Note 1969700)
M0012 GENERAL global Revision level SQL:

"HANA_Configuration_PatchL
evel"
M0110 GENERAL global Everything started SQL:

“HANA_Services_Overview”
M0111 GENERAL scale-out Host startup time variation (s) SQL:
“HANA_Startup_StartupTimes
”
M0115 GENERAL global Service startup time variation (s) SQL:

“HANA_Startup_StartupTimes
”
M0120 GENERAL global Services not started SQL:

"HANA_Services_Overview"
M0207 OPERATIN Power Recommended bigmem kernel SQL:

G SYSTEM flavor not used "HANA_Hosts_Overview"
M0208 OPERATIN global Supported operating system SQL:

G SYSTEM "HANA_Hosts_Overview"
M0209 OPERATIN global Recommended operating system SQL:

G SYSTEM kernel version "HANA_Hosts_Overview"
M0210 OPERATIN global Minimum CPU rate (MHz) SQL:
M0211 OPERATIN scale-out Hosts with varying CPU rates SQL:

M0215 OPERATIN global Hosts with outdated CPU type SQL:
M0220 OPERATIN global Current CPU utilization (%) SQL:

G SYSTEM "HANA_Resources_CPUAnd
Memory_History"
M0221 OPERATIN global Peak CPU utilization (%, last day) SQL:
Memory_History"
M0222 OPERATIN global Time since CPU utilization > 95 % SQL:

G SYSTEM (h) "HANA_Resources_CPUAnd
Memory_History"
M0226 OPERATIN global Peak system CPU utilization (%, SQL:
G SYSTEM last day) "HANA_Resources_CPUAnd
Memory_History"
M0227 OPERATIN global External CPU utilization (%, last

G SYSTEM hour)
SQL:
"HANA_LoadHistory_Hosts"
SQL:
"HANA_LoadHistory_Services
"
M0228 OPERATIN global Erroneous system CPU calculation SQL:
G SYSTEM "HANA_LoadHistory_Services
"
M0229 OPERATIN global Discrepancy between NUMA nodes SQL:

G SYSTEM and sockets “HANA_Hosts_Overview”
SQL: “HANA_NUMA_Nodes”
M0230 OPERATIN global Current memory utilization (%) SQL:
Memory_History"
M0231 OPERATIN global Time since memory utilization > 95 SQL:

G SYSTEM % (h) "HANA_Resources_CPUAnd
Memory_History"
M0232 OPERATIN global Hyperthreading active in critical SQL:

G_SYSTE contexts "HANA_Hosts_Overview"
M
M0233 OPERATIN >= NUMA nodes with high CPU SQL:
G_SYSTE 2.00.020 utilization "HANA_CPU_UtilizationPerCo
M re"
M0234 OPERATIN >= CPU steal share (%) SQL:

G_SYSTE 2.00.020 "HANA_Resources_CPUAnd
M Memory_CurrentDetails"
M0235 OPERATIN scale-out Hosts with varying physical memory SQL:

G SYSTEM size "HANA_Hosts_Overview"
M0240 OPERATIN global Current swap utilization (GB) SQL:
Memory_History"
M0241 OPERATIN global Time since swap utilization > 1 GB SQL:

G SYSTEM (h) "HANA_Resources_CPUAnd
Memory_History"
M0242 OPERATIN global Swap out (GB, last week) SQL:
G SYSTEM "HANA_LoadHistory_Hosts"
M0245 OPERATIN global Swap space size (GB) SQL:

M0250 OPERATIN global Max. used disk size (%) SQL: "HANA_Hosts_Disks"
G SYSTEM
SQL:
"HANA_Hosts_FileSystems" (
SAP HANA >= 2.00.020)
M0260 OPERATIN global Open files limit configured SQL:
G "HANA_Hosts_Overview"
SYSTEM
M0261 OPERATIN global Open files limit used (%, current) SQL:
G SYSTEM "HANA_Services_Statistics"
M0262 OPERATIN global Max. open files limit used (%, SQL:
G SYSTEM history) "HANA_LoadHistory_Services
"
M0263 OPERATIN global Asynchronous I/O queue size limit SQL:

G SYSTEM "HANA_Configuration_Infrastr
ucture"
M0264 OPERATIN global Virtual memory map count limit SQL:
ucture"
M0265 OPERATIN global Network socket backlog limit SQL:

ucture"
M0266 OPERATIN global Non-acknowledged requests limit SQL:

ucture"
M0267 OPERATIN global Ephemeral port limit SQL:

ucture"
M0270 OPERATIN global Unknown hardware components SQL:
M0280 OPERATIN scale-out Maximum time variation between SQL: "HANA_Hosts_Time"

G SYSTEM hosts (s)
M0310 DISK global I/O read throughput data min. SQL:

(MB/s, last day) "HANA_IO_KeyFigures_Total_
History"
SQL:
"HANA_IO_KeyFigures_Detail
_History"
M0311 DISK global I/O read throughput data avg. SQL:
History"
SQL:
_History"
M0312 DISK global I/O read latency data max. (ms, last SQL:
day) "HANA_IO_KeyFigures_Total_
History"
SQL:
_History"
M0313 DISK global I/O read latency data avg. (ms, last SQL:
History"
SQL:
_History"
M0314 DISK global I/O read reload throughput avg.
(MB/s)
SQL:
"HANA_IO_KeyFigures_Total_
History"
SQL:
_History"
M0315 DISK global I/O write throughput data min. SQL:

History"
SQL:
_History"
M0316 DISK global I/O write throughput data avg. SQL:
History"
SQL:
_History"
M0317 DISK global I/O read activity data avg. (%, last SQL:
History"
SQL:
_History"
M0318 DISK global I/O write activity data avg. (%, last SQL:
History"
M0318 DISK global I/O write activity data avg. (%, last
day)
SQL:
_History"
M0320 DISK global I/O read throughput log min. (MB/s, SQL:
last day) "HANA_IO_KeyFigures_Total_
History"
SQL:
_History"
M0321 DISK global I/O read throughput log avg. (MB/s, SQL:
History"
SQL:
_History"
M0324 DISK global I/O write activity log avg. (%, last SQL:
History"
SQL:
_History"
M0325 DISK global I/O write throughput log min. (MB/s, SQL:
History"
SQL:
_History"
M0326 DISK global I/O write throughput log avg. (MB/s, SQL:
History"
SQL:
_History"
M0327 DISK global I/O write latency log max. (ms, last SQL:
History"
SQL:
_History"
M0328 DISK global 4 KB write duration log avg. (ms)
SQL:
_History"
M0329 DISK global I/O write latency log avg. (ms, last SQL:
History"
SQL:
_History"
M0330 DISK global Max. trigger read ratio (data) SQL:
“HANA_IO_KeyFigures_Total”
M0331 DISK global Max. trigger write ratio (data, log) SQL:
“HANA_IO_KeyFigures_Total”
M0340 DISK global Log switch wait count ratio (%) SQL: “HANA_Log_LogBuffers”
M0341 DISK global Log switch race count ratio (%) SQL: “HANA_Log_LogBuffers”
M0346 DISK global Long waitForLock savepoint phases SQL: “HANA_IO_Savepoints”
(last day)
M0348 DISK global Long critical savepoint phases (last SQL: “HANA_IO_Savepoints”
day)
M0350 DISK global Blocking savepoint phases > 10 s SQL: “HANA_IO_Savepoints”

(last day)
M0351 DISK global Blocking savepoint phase avg. (s, SQL: “HANA_IO_Savepoints”
last day)
M0352 DISK global Blocking savepoint phase max. (s, SQL: “HANA_IO_Savepoints”
last day)
M0355 DISK global Time since last savepoint (s) SQL: "HANA_IO_Savepoints"
M0356 DISK global Savepoint crit. phase write SQL: "HANA_IO_Savepoints"

throughput (MB/s)
M0357 DISK global Savepoint write throughput (MB/s) SQL: "HANA_IO_Savepoints"

M0358 DISK global Savepoints taking longer than 900 s SQL: "HANA_IO_Savepoints"
(last day)
M0360 DISK global Number of failed I/O reads
SQL:
"HANA_IO_KeyFigures_Total"
SQL:
History"
M0361 DISK global Number of failed I/O writes
SQL:
SQL:
History"
M0363 DISK global Redo log generation (TB / day, last

week)
SQL:
"HANA_Backup_BackupRuns"
M0364 DISK global Redo log per day vs. data (%, last
week)
SQL:
"HANA_Backup_BackupRuns"
M0365 DISK Rev. >= Wrong SAP HANA I/O parameter

122.04 settings
SQL:
SQL:
M0367 DISK global Filesystems with unsupported types
SQL: "HANA_Hosts_Disk"
M0370 DISK global Unused space in data files (%) SQL:

"HANA_Disks_Overview"
M0372 DISK global Unused space in classic disk LOBs SQL:

vs. data (%) "HANA_LOBs_LOBFiles"
M0373 DISK global Tables with many small disk LOBs SQL:
"HANA_LOBs_LOBFiles"
M0374 DISK global Tables with many disk LOBs SQL:
"HANA_LOBs_LOBFiles"
M0375 DISK global Data disk vs. memory ratio SQL:

"HANA_Configuration_Overvie
w"
M0380 DISK global Age of oldest backup snapshot SQL: "HANA_IO_Snapshots"

(days)
M0381 DISK >= Age of oldest fallback snapshot SQL: "HANA_IO_Snapshots"
2.00.030 (days)
M0383 DISK global Max. size of shadow pages (GB, SQL:

last day) "HANA_Disks_Data_Pages"
M0385 DISK global Savepoint vol. per day vs. data (%, SQL: "HANA_IO_Savepoints"
last week)
M0386 DISK global Max. savepoint prepare flush retries SQL: "HANA_IO_Savepoints"
(current)
M0387 DISK global Avg. savepoint prepare flush retries SQL: "HANA_IO_Savepoints"
(current)
M0410 MEMORY global Allocation limit used (%) SQL:
"HANA_Memory_Overview"
M0411 MEMORY global Current allocation limit used by SQL:

tables (%) "HANA_Memory_Overview"
M0413 MEMORY global Time since allocation limit used > SQL:
80 % (h) "HANA_Resource_CPUAndM
emory_History"
M0415 MEMORY global Curr. max. service allocation limit SQL:

used (%) "HANA_Services_Memory"
M0417 MEMORY global Time since service alloc. limit used SQL:
> 80 % (h) "HANA_Services_Memory"
M0420 MEMORY global Heap areas currently larger than 50 SQL:

GB "HANA_Memory_TopConsum
ers"
M0421 MEMORY global Heap areas larger than 100 GB SQL:

(last day) "HANA_Memory_TopConsum
ers_TimeSlices"
M0422 MEMORY global Heap areas larger than 200 GB SQL:

(history) "HANA_Memory_TopConsum
ers_TimeSlices"
M0423 MEMORY global Heap areas with potential memory SQL:

leak "HANA_Memory_TopConsum
ers_TimeSlices"
M0425 MEMORY global Pool/RowEngine/CpbTree leak size SQL:
(GB) "HANA_RowStore_TotalIndex
Size"
M0426 MEMORY global Row store table leak size (GB) SQL:
"HANA_Memory_Overview"
M0430 MEMORY global Number of low memory column SQL:

unloads (last day) "HANA_Tables_ColumnStore_
UnloadsAndLoads"
M0431 MEMORY global Time since last low memory column SQL:
unload (days) "HANA_Tables_ColumnStore_
UnloadsAndLoads"
M0435 MEMORY global Number of shrink column unloads SQL:

(last day) "HANA_Tables_ColumnStore_
UnloadsAndLoads"
M0437 MEMORY global Size of unloaded columns (GB, last SQL:

day) "HANA_Tables_ColumnStore_
UnloadsAndLoads"
M0438 MEMORY global Memory reclaim activity (s / day) SQL:

"HANA_Memory_Reclaims"
M0439 MEMORY global Memory reclaim maximum duration SQL:

(s) "HANA_Memory_Reclaims"
M0440 MEMORY global Shared memory utilization of SQL:
nameserver (%) "HANA_Memory_SharedMem
ory"
M0445 MEMORY global Number of OOM events (last hour) SQL:

"HANA_Memory_OutOfMemor
yEvents"
M0450 MEMORY Rev. >= Tables with memory LOBs > 2 GB SQL:
1.00.70 "HANA_LOBs_HybridLOBActi
vation_CommandGenerator"
M0453 MEMORY Rev. >= Size of non-unique concat attributes SQL:
1.00.70 (GB) "HANA_Tables_ColumnStore_
Columns"
M0454 MEMORY global Size of non-unique concat attributes SQL:

(%) "HANA_Tables_ColumnStore_
Columns"
M0455 MEMORY global Unused large non-unique concat SQL:

attributes "HANA_Tables_ColumnStore_
Columns_Statistics"
M0456 MEMORY Rev. >= Unused large non-unique row store SQL:
2.00.040 indexes "HANA_Indexes_RowStore_In
dexSearches"
M0460 MEMORY global Calculation engine cache utilization SQL:
(%) "HANA_CalculationEngine_Ca
lculationScenarios"
M0462 MEMORY global Caches with large size SQL:

"HANA_Memory_Caches_Ove
rview"
M0470 MEMORY global Frequent allocators SQL:

"HANA_Memory_TopConsum
ers"
M0472 MEMORY global Booked vs. allocated memory (%) SQL:
"HANA_Memory_ContextMem
ory"
M0480 MEMORY global Address space utilization (%) SQL:

"HANA_Memory_TopConsum
ers"
M0510 TABLES global Tables with > 100 partitions SQL:

"HANA_Tables_ColumnStore_
PartitionedTables"
M0511 TABLES global Tables with many columns SQL: "HANA_Columns"

M0512 TABLES global Hash partitioning on multiple SQL:
columns "HANA_Tables_ColumnStore_
PartitionedTables"
M0515 TABLES global Partitioned tables with inverted SQL: "HANA_Indexes"

hash indexes
M0516 TABLES global Existing inverted hash indexes SQL: "HANA_Indexes"

M0519 TABLES global Tables with large overflow partition SQL:
"HANA_ColumnStore_Partitio
ns"
M0520 TABLES global Tables / partitions > 1.5 billion rows SQL:
Records"
M0521 TABLES global Table histories > 1.5 billion rows SQL:
Records"
M0522 TABLES global Tables / partitions > 1.5 billion UDIV SQL:
rows "HANA_Tables_ColumnStore_
Records"
M0523 TABLES global Columns with many distinct text SQL:

tokens "HANA_Tables_ColumnStore_
Columns"
M0525 TABLES global Tables / partitions with large SQL:
memory size "HANA_Tables_TableSize"
M0526 TABLES global Tables / partitions with large SQL:

memory share "HANA_Tables_TableSize"
M0530 TABLES global Row store size (GB) SQL:

"HANA_RowStore_Overview"
M0533 TABLES global Row store tables with more than 1 SQL:
container "HANA_Tables_RowStore_Ta
blesWithMultipleContainers"
M0535 TABLES global Row store fragmentation (%) SQL:
"HANA_RowStore_Overview"
M0538 TABLES global Delta merges > 900 s (last day) SQL:
Merges"
M0539 TABLES global Critical merge share (%, last week) SQL:
Merges"
M0540 TABLES global Failing delta merges (info SQL:
messages, last day) "HANA_Tables_ColumnStore_
Merges"
M0541 TABLES global Failing delta merges (error SQL:

messages, last day) "HANA_Tables_ColumnStore_
Merges"
M0542 TABLES global Auto merge tables with delta SQL:

storage > 5 GB "HANA_Tables_ColumnStore_
DeltaStorage"
M0543 TABLES global Auto merge tables with many delta SQL:
records "HANA_Tables_ColumnStore_
DeltaStorage"
M0544 TABLES global Non-auto merge tables with delta SQL:
storage > 5 GB "HANA_Tables_ColumnStore_
DeltaStorage"
M0545 TABLES global Non-auto merge tables with many SQL:

delta records "HANA_Tables_ColumnStore_
DeltaStorage"
M0546 TABLES global Sum of delta size of small tables SQL:

(GB) "HANA_Tables_ColumnStore_
DeltaStorage"
M0547 TABLES global Non BW tables with disabled auto SQL:

merge “HANA_Tables_ColumnStore_
AutoMergeDisabled”
AutoMergeDisabled”
M0548 TABLES global Tables with disabled persistent SQL:

merge “HANA_Tables_ColumnStore_
PersistentMergeDisabled”
M0549 TABLES global Non BW tables with disabled auto SQL:

compression "HANA_Tables_ColumnStore_
AutoCompressionDisabled"
M0550 TABLES global Row store tables with ST_POINT SQL: "HANA_Columns"
columns
M0551 TABLES global Proper setup of timezone table SQL:
TTZZ "HANA_Configuration_Timezo
nes"
M0552 TABLES global Number of current timezone alerts SQL:

"HANA_Configuration_Timezo
nes"
M0555 TABLES Rev. <= Tables / partitions moved only SQL:

1.00.82 logically “HANA_Tables_ColumnStore_
TablesMovedLogically”
M0560 TABLES global Tables > 10 Mio. rows not SQL:
compressed "HANA_Tables_ColumnStore_
TablesWithoutCompressionOp
M0561 TABLES global Columns > 10 Mio. rows not SQL:
compressed "HANA_Tables_ColumnStore_
ColumnsWithoutCompression
Optimization"
M0562 TABLES global Columns with missing inverted SQL:

indexes "HANA_Indexes_ColumnStore
_MissingSingleColumnIndexes
"
M0563 TABLES global Indexes on large SPARSE / SQL:

PREFIXED columns "HANA_Indexes_ColumnStore
_MissingSingleColumnIndexes
"
"
M0565 TABLES global Tables > 10 Mio. rows and > 200 % SQL:
UDIV rows "HANA_Tables_ColumnStore_
Records"
M0566 TABLES global Tables with fragmented $trex_udiv$ SQL:

column "HANA_Tables_ColumnStore_
Compression"
M0567 TABLES Rev. >= Tables with MVCC timestamps > 5 SQL:
1.00.90 GB "HANA_GarbageCollection_C
olumnStore"
M0570 TABLES global Number of temporary tables SQL:
"HANA_Tables_TemporaryTab
les"
M0572 TABLES global Number of NO LOGGING tables SQL: "HANA_Tables"
M0574 TABLES global Tables with small unused retention SQL:
period "HANA_Tables_ColumnStore_
TableSize"
M0580 TABLES global Tables assigned to wrong service

M0582 TABLES global Tables with empty table location SQL:
"HANA_Tables_TableLocation
s"
Check ID Area Validity Description Analysis SQL statement (SAP Note 1969700)
M0610 TRACES, Rev. >= Kernel profiler active SQL:

DUMPS 1.00.70 "HANA_Traces_ActivatedAnd
AND LOGS Modified Traces"
M0612 TRACES, global Performance trace enabled SQL:

DUMPS "HANA_Traces_ActivatedAnd
M0613 TRACES, global Function profiler enabled SQL:

and LOGS Modified Traces"
M0614 TRACES, global SQL trace enabled SQL:

M0616 TRACES, global Indexserver python trace enabled SQL:

M0617 TRACES, global Executor python trace enabled SQL:

M0618 TRACES, global SQL client network trace enabled SQL:

M0620 TRACES, global Minimum expensive SQL trace SQL:
DUMPS threshold (ms) "HANA_Traces_ActivatedAnd
M0623 TRACES, global Traced expensive SQL statements SQL:

DUMPS (last day) "HANA_SQL_ExpensiveState
AND LOGS ments"
M0624 TRACES, global Expensive statements trace SQL:

DUMPS retention (days) "HANA_SQL_ExpensiveState
AND LOGS ments"
M0630 TRACES, global Existence of database trace SQL:
DUMPS settings "HANA_Traces_ActivatedAnd
M0635 TRACES, global Existence of user-specific trace SQL:

M0637 TRACES, global Existence of end-to-end trace SQL:

M0638 TRACES, global Number of backup log files SQL:

DUMPS "HANA_TraceFiles_Overview"
AND LOGS
M0639 TRACES, global Number of trace entries (last hour) SQL:

DUMPS "HANA_TraceFiles_Content"
and LOGS
M0640 TRACES, global Number of trace files (total) SQL:

AND LOGS
M0641 TRACES, global Number of trace files (last day) SQL:

AND LOGS
M0642 TRACES, global Size of trace files (GB, total) SQL:

AND LOGS
M0643 TRACES, global Size of trace files (GB, last day) SQL:
AND LOGS
M0644 TRACES, global Size of largest trace file (MB) SQL:

AND LOGS
M0645 TRACES, global Number of OOM trace files (last SQL:

DUMPS day) "HANA_TraceFiles_Overview"
AND LOGS
M0646 TRACES, global Number of statement OOM trace SQL:

DUMPS files (last day) "HANA_TraceFiles_Overview"
AND LOGS
M0650 TRACES, global Number of crash dumps (last day) SQL:

AND LOGS
M0652 TRACES, global Number of page dumps (last day) SQL:

AND LOGS
M0655 TRACES, global Number of RTE dumps (last day) SQL:

AND LOGS
M0658 TRACES, global Time since last dump (days) SQL:

AND LOGS
M0660 TRACES, global CPU time measurement enabled SQL:
DUMPS "HANA_Configuration_Param
AND LOGS eters"
M0661 TRACES, global Heap allocators with allocation SQL: "HANA_Heap_Flags"

DUMPS AN stack trace
D LOGS
M0662 TRACES, global Heap allocators with other activated SQL: "HANA_Heap_Flags"
DUMPS AN traces
D LOGS
M0663 TRACES, global Time since active heap allocator SQL: "HANA_Heap_Flags"
DUMPS AN trace (days)
D LOGS
M0670 TRACES, global Time since last trace file SQL:

DUMPS modification (s) "HANA_TraceFiles_Overview"
AND LOGS
M0710 STATISTIC global Open alerts (high priority) SQL:

S SERVER "HANA_StatisticsServer_Alert
s_Current"
M0711 STATISTIC global Open alerts (error state) SQL:

S SERVER "HANA_StatisticsServer_Alert
s_Current"
M0712 STATISTIC global Internal statistics server errors (last SQL:
S SERVER day) "HANA_StatisticsServer_Alert
s_History"
M0715 STATISTIC global Number of actions not executed as SQL:

S SERVER expected "HANA_StatisticsServer_Sche
dule"
M0716 STATISTIC ESS Number of statistics server worker SQL:

S SERVER threads "HANA_Threads_CurrentThre
ads"
M0717 STATISTIC ESS Number of disabled actions SQL:

S SERVER "HANA_StatisticsServer_Sche
dule"
M0718 STATISTIC ESS Number of relevant inactive actions SQL:
dule"
M0719 STATISTIC ESS Number of actions with unknown SQL:

S SERVER state "HANA_StatisticsServer_Sche
dule"
M0720 STATISTIC global Events not acknowledged since >= SQL: "HANA_Events"
S SERVER 1800 s
M0730 STATISTIC ESS Pending e-mails older than 3 days SQL:
S SERVER "HANA_StatisticsServer_Mail
Notifications"
M0735 STATISTIC ESS Alerts older than 42 days SQL:

S SERVER "HANA_Data_ColumnValueCo
unter_CommandGenerator"
M0736 STATISTIC ESS Alerts reported frequently SQL:

S SERVER "HANA_Data_ColumnValueCo
M0740 STATISTIC global Time since statistics server run (s) SQL:
dule"
M0744 STATISTIC global Total SQL cache share of statistics SQL:

S SERVER server (%) "HANA_Memory_SQLCache_
TopConsumers"
M0745 STATISTIC global Total size of statistics server tables SQL:

S SERVER (GB) "HANA_Tables_LargestTables
"
M0746 STATISTIC global Total memory share of statistics SQL:
S SERVER server (%) "HANA_Tables_LargestTables
"
M0747 STATISTIC SSS Number of zero entries in SQL:

S SERVER HOST_SQL_PLAN_CACHE "HANA_Data_ColumnValueCo
M0748 STATISTIC global History of M_CS_UNLOADS SQL:

S SERVER collected "HANA_StatisticsServer_Sche
dule"
M0749 STATISTIC ESS HISTORY of M_RECORD_LOCKS SQL:
S SERVER collected "HANA_StatisticsServer_Sche
dule"
M0750 STATISTIC global Stat. server tables with retention < SQL:
S SERVER 42 days "HANA_StatisticsServer_Histo
ries_RetentionTime"
M0751 STATISTIC global Historic thread samples save SQL:

S SERVER interval (s) "HANA_StatisticsServer_Sche
dule"
M0755 STATISTIC Rev. >= Embedded statistics server used SQL:
S SERVER 1.00.74 "HANA_Configuration_Param
eters"
M0760 STATISTIC ESS Status of embedded statistics SQL:

S SERVER server migration "HANA_StatisticsServer_Prop
erties"
M0765 STATISTIC SSS Log segment size of statisticsserver SQL:

S SERVER (MB) "HANA_Logs_LogBuffers"
M0770 STATISTIC ESS Number of stat. server tables not on SQL:

S SERVER master "HANA_Tables_LargestTables
"
M0780 STATISTIC ESS Unknown entries in SQL:
S SERVER HOST_OBJECT_LOCK_STATISTI "HANA_Data_ColumnValueCo
CS unter_CommandGenerator"
M0781 STATISTIC ESS, Orphan entry for alert 32
S SERVER Rev. >=
2.00.040
M0810 TRANSACT global Current MVCC versions in row SQL:

IONS AND store "HANA_GarbageCollection_O
THREADS verview"
M0811 TRANSACT Rev. >= Max. MVCC versions in row store SQL:
IONS AND 1.00.90 (last day) "HANA_LoadHistory_Services
THREADS "
M0812 TRANSACT global Max. versions per record in row
IONS AND store
THREADS
SQL:
"HANA_GarbageCollection_O
verview"
M0813 TRANSACT global Max. versions per table in row store

IONS AND
THREADS
SQL:
verview"
M0815 TRANSACT global Age of transaction blocking row SQL:

IONS AND store MVCC (s) "HANA_GarbageCollection_O
THREADS verview"
M0830 TRANSACT global Active commit ID range

IONS AND SQL:
THREADS "HANA_GarbageCollection_O
verview"
M0832 TRANSACT Rev. >= Max. active commit ID range (last

IONS AND 1.00.90 day) SQL:
THREADS "HANA_LoadHistory_Services
"
M0840 TRANSACT Rev. < Active update transaction ID range

IONS AND 1.00.100
THREADS
SQL:
verview"
M0841 TRANSACT global Oldest active update transaction SQL:
IONS AND current (h) "HANA_GarbageCollection_O
THREADS verview"
M0842 TRANSACT Rev. >= Oldest active update transaction in SQL:

IONS AND 1.00.90 history (h) "HANA_GarbageCollection_Bl
THREADS ockers_History"
M0843 TRANSACT global Longest running statement current SQL:

IONS AND (h) "HANA_SQL_ActiveStatement
THREADS s"
M0844 TRANSACT Rev. >= Longest running statement in SQL:

IONS AND 1.00.90 history (h) "HANA_GarbageCollection_Bl
THREADS ockers_History"
M0845 TRANSACT Rev. Maximum update transaction ID

IONS AND 1.00.64 -
THREADS 1.00.69.0
4 SQL:
verview"
M0846 TRANSACT global Table MVCC snapshot range

ION AND
THREADS
SQL:
verview"
M0848 TRANSACT Current update transaction ID SQL:

ION AND 1.00.122. "HANA_GarbageCollection_O
THREADS 16 verview"
<= SQL:
2.00.024. "HANA_GarbageCollection_L
01 OBs"
2.00.030
M0849 TRANSACT global Orphan LOBs
ION AND
THREADS
SQL:
"HANA_GarbageCollection_L
OBs"
M0850 TRANSACT global Persistence garbage collection SQL:

IONS AND history count "HANA_GarbageCollection_P
THREADS ersistence"
M0851 TRANSACT global Time since last CS LOB garb. coll. SQL:
IONS AND (days) "HANA_LOBs_ColumnStore_
THREADS Reclaims"
M0852 TRANSACT global Undo and cleanup files SQL:

IONS AND "HANA_Transactions_UndoCl
THREADS eanupFiles"
M0854 TRANSACT global Undo and cleanup file size (GB) SQL:
IONS AND "HANA_Transactions_UndoCl
THREADS eanupFiles"
M0856 TRANSACT global Max. undo size of current SQL:

IONS AND transaction (MB) "HANA_Transactions_UndoAn
THREADS dRedoLog"
M0857 TRANSACT global Max. redo size of current SQL:
IONS AND transaction (MB) "HANA_Transactions_UndoAn
THREADS dRedoLog"
M0858 TRANSACT global Rollbacks per second (last week) SQL: "HANA_Workload"
IONS AND
THREADS
M0860 TRANSACT Rev. >= Current pending sessions SQL:

IONS AND 1.00.90 "HANA_LoadHistory_Services
THREADS "
M0863 TRANSACT Rev. >= Avg. pending sessions (last day) SQL:
THREADS "
M0864 TRANSACT Rev. >= Admission control events (last day) SQL:
IONS AND 2.00.010 "HANA_Workload_Admission
THREADS ControlEvents"
M0865 TRANSACT Rev. >= Admission control rejections SQL:

THREADS "
M0866 TRANSACT Rev. >= Admission control max. queue size SQL:
THREADS "
M0870 TRANSACT global SelfWatchDog activity time (%, last SQL:

IONS AND hour) "HANA_Threads_ThreadSam
THREADS ples_FilterAndAggregation"
M0871 TRANSACT Rev. >= Max. load history gap (s, last week) SQL:
IONS AND 1.00.90 "HANA_Global_CriticalTimeFr
THREADS ames"
M0878 TRANSACT global Connections in CANCEL SQL:

IONS AND REQUESTED state "HANA_Connections_Overvie
THREADS w"
M0880 TRANSACT global Open connections (%) SQL:
IONS AND "HANA_Connections_Overvie
THREADS w"
M0882 TRANSACT global Max. parked job worker ratio SQL:

IONS AND "HANA_Jobs_Executors"
THREADS
M0883 TRANSACT global Queued job workers SQL:
IONS AND "HANA_Jobs_Executors"
THREADS
M0884 TRANSACT Rev. < Deviating max_concurrency used SQL:

IONS AND 2.00.030 internally "HANA_Jobs_Executors"
THREADS
M0885 TRANSACT global Current threads with significant SQL:
IONS AND duration "HANA_Threads_CurrentThre
THREADS ads"
M0887 TRANSACT global Application users with significant SQL:
IONS AND threads "HANA_Threads_CurrentThre
THREADS ads"
M0890 TRANSACT global Unusual frequent thread methods SQL:

IONS AND (last hour) "HANA_Threads_ThreadSam
M0892 TRANSACT global Unusual frequent thread methods SQL:
IONS AND (last week) "HANA_Threads_ThreadSam
M0910 BACKUP global Age of last data backup (days) SQL:

"HANA_Backups_BackupRun
s"
M0911 BACKUP global Age of last data backup error (days) SQL:
s"
M0915 BACKUP global Min. data backup throughput (GB/h, SQL:

last week) "HANA_Backups_BackupRun
s"
M0916 BACKUP global Avg. data backup throughput (GB/h, SQL:

last week) "HANA_Backups_BackupRun
s"
M0920 BACKUP global Age of last log backup (hours) SQL:

s"
M0921 BACKUP global Age of last log backup error (days) SQL:
s"
M0922 BACKUP global Maximum log backup duration (s, SQL:

last day) "HANA_Backups_BackupRun
s"
M0923 BACKUP global Log backup errors (last month) SQL:

s"
M0930 BACKUP global Automatic log backup SQL:

"HANA_Configuration_Param
eters"
M0935 BACKUP global Database log mode SQL:
"HANA_Configuration_Param
eters"
M0940 BACKUP global Size of backup catalog (MB) SQL:

"HANA_Backups_CatalogSize
"
M0942 BACKUP global Catalog size share (last day, %) SQL:
s"
M0945 BACKUP global Age of oldest backup in catalog SQL:

(days) "HANA_Backups_CatalogSize
"
M0950 BACKUP global Log segments not free for reuse SQL:
"HANA_Logs_LogSegments"
M0952 BACKUP global Log segments free for reuse SQL:

"HANA_Logs_LogSegments"
M0955 BACKUP global Max. number of log backups / SQL:

service (last day) "HANA_Backups_BackupRun
s"
M1010 LOCKS global Age of oldest active trans. lock wait SQL:
(s) "HANA_Locks_Transactional_
LockWaits"
M1011 LOCKS global Trans. lock wait durations > 600 s SQL:
(last day) "HANA_Locks_Transactional_
LockWaits"
M1020 LOCKS global Threads currently waiting for locks SQL:
"HANA_Threads_CurrentThre
ads"
M1021 LOCKS global Maximum threads waiting for locks SQL:

(last day) "HANA_Threads_ThreadSam
ples_AggregationPerTimeSlic
e"
M1030 LOCKS Rev. >= Concurrently blocked transactions SQL:

1.00.90 (last hour) "HANA_LoadHistory_Services
"
SQL:
"HANA_Locks_Transactional_
LockWaits"
M1031 LOCKS Rev. >= Concurrently blocked transactions SQL:
1.00.90 (last day) "HANA_LoadHistory_Services
"
SQL:
LockWaits"
M1040 LOCKS general Total current transactional locks
SQL:
LockWaits"
M1045 LOCKS general Transactional locks older than 1 day

SQL:
LockWaits"
M1050 LOCKS general Significant internal lock waits (last

hour) SQL:
"HANA_Threads_ThreadSam
ples_FilterAndAggregation"
M1052 LOCKS general Significant internal lock waits (last

day) SQL:
M1055 LOCKS general Locks with repeated wait spikes
SQL:
M1110 SQL global SQL using in average > 1 SQL:

connection (last day) "HANA_SQL_SQLCache"
M1112 SQL global SQL using in average > 1 thread SQL:

(last hour) "HANA_Threads_ThreadSam
M1113 SQL ESS SQL using in average > 1 thread SQL:

(last day) "HANA_Threads_ThreadSam
M1115 SQL global Longest running current SQL SQL:

statement (h) "HANA_SQL_ActiveStatement
s"
M1118 SQL global Longest running current job (s) SQL:

"HANA_Jobs_JobProgress"
M1120 SQL global Exp. stmt. trace: SQL running > 1 h SQL:
(last day) "HANA_SQL_ExpensiveState
ments"
M1125 SQL >= 2.0 Columns with many scanned SQL:

SPS 03 records "HANA_Tables_ColumnStore_
Columns_Statistics"
M1126 SQL >= 2.0 Row tables with many scanned SQL:
SPS 04 records "HANA_Tables_RowStore_Ta
ble_Size"
M1129 SQL global SQL cach evictions / h (last day) SQL:

"HANA_SQL_SQLCache_Ove
rview"
M1130 SQL global SQL cache evictions / h SQL:

"HANA_SQL_SQLCache_Ove
rview"
M1131 SQL global SQL cache hit ratio of indexserver SQL:

(%) "HANA_SQL_SQLCache_Ove
rview"
M1132 SQL ABAP, SQL cache size per SQL SQL:
SPS <= connection (MB) "HANA_SQL_SQLCache_Ove
1.00.08 rview"
M1140 SQL global SQL preparation runtime share (%) SQL:

"HANA_SQL_SQLCache_Pre
paration"
M1142 SQL global Table(s) using > 10 % of SQL cache SQL:

"HANA_Memory_SQLCache_
TopConsumers"
M1145 SQL ABAP SQL cache used by IN lists >= 100 SQL:
elements (%) "HANA_Memory_SQLCache_
TopConsumers"
M1147 SQL global Duplicate statement hashes in SQL SQL:
cache (%) "HANA_Memory_SQLCache_
TopConsumers"
M1148 SQL global Statements existing > 100 times in SQL:

SQL cache "HANA_SQL_SQLCache"
M1149 SQL global Statements with SESSION LOCAL SQL:

sharing type (%) "HANA_Memory_SQLCache_
TopConsumers"
M1150 SQL global Referenced statements in SQL SQL:

cache (%) "HANA_SQL_SQLCache"
M1152 SQL global Max. SQL contexts per connection SQL:

"HANA_Memory_ContextMem
ory"
M1159 SQL 2.0 SPS Hourly maximum commit I/O time SQL: "HANA_IO_Commits"
>= 04 average (ms)
M1160 SQL 1.0 SPS Average commit time (ms) SQL:

>= 11 "HANA_Connections_Statistic
s"
M1161 SQL 1.0 SPS Maximum commit I/O time (s) SQL: "HANA_IO_Commits"
>= 07
M1162 SQL 1.0 SPS Average commit I/O time (ms) SQL: "HANA_IO_Commits"
>= 07
M1163 SQL commit vs. execution ratio (%, last SQL: "HANA_Workload"
week)
M1164 SQL scale-out Unexpected distributed executions SQL:

"HANA_SQL_SQLCache"
M1165 SQL global Internal executions (%) SQL:
"HANA_SQL_SQLCache"
M1168 SQL >= Delivered statement hints SQL:

1.00.122. implemented "HANA_SQL_StatementHints"
03
M1169 SQL >= Total number of implemented SQL:

1.00.122. statement hints "HANA_SQL_StatementHints"
03
M1170 SQL global Average database request time SQL:

(ms) "HANA_SQL_SQLCache"
M1180 SQL ABAP Avg. ABAP buffer loading sessions SQL:
(last day) "HANA_SQL_SQLCache"
M1181 SQL ABAP Avg. FDA write sessions (last day) SQL:
"HANA_SQL_SQLCache"
M1182 SQL ABAP Avg. compatibility view sessions SQL:

(last day) "HANA_SQL_SQLCache_Spe
cialStatements"
M1210 APPLICATI ABAP DDLOG sequence cache size SQL:

ON "HANA_Configuration_Sequen
ces"
M1220 APPLICATI ABAP QCM conversion tables SQL:
ON client "HANA_Tables_SpecialTables"
M1230 APPLICATI ABAP ABAP row store tables on slave SQL:
ON node "HANA_Tables_RowStore_Ta
bleSize"
M1240 APPLICATI Connections without application SQL:

ON information (%) "HANA_Connections_Overvie
w"
M1250 APPLICATI BPC Physical BPC tables SQL:
ON "HANA_Tables_SpecialTables"
M1252 APPLICATI ABAP Physical ABAP pool and cluster SQL:

ON tables "HANA_Tables_SpecialTables"
M1260 APPLICATI ABAP QIWKTAB update rate (updates / h) SQL:

ON "HANA_SQL_SQLCache"
M1270 APPLICATI ABAP Two-column indexes including client SQL:
ON column "HANA_Indexes_MultiColumnI
ndexesWithClient"
M1280 APPLICATI ABAP Growth of short dump table SNAP SQL:

ON (GB, last day) "HANA_Tables_IOStatistics"
M1285 APPLICATI ABAP Number of update records in error SQL:
ON state "HANA_ABAP_UpdateErrors"
M1310 SECURITY global Secure store (SSFS) status

M1312 SECURITY global Inconsistent secure store SQL:
"HANA_Security_SecureStore
"
M1330 SECURITY global Number of users with expiration SQL: "HANA_Security_Users"

date
M1331 SECURITY global Connection user with (password) SQL: "HANA_Security_Users"

expiration
M1333 SECURITY >= Rev. Certificates with previous or SQL:

1.00.100 upcoming expiry "HANA_Security_Certificates"
M1335 SECURITY global Number of SAP users with SQL: "HANA_Security_Users"

password expiration
M1340 SECURITY global CATALOG READ privilege granted SQL:

to current user "HANA_Security_GrantedRole
sAndPrivileges"
M1360 SECURITY global Size of audit log table (GB) SQL:

"HANA_Tables_LargestTables
"
M1362 SECURITY global Active DML audit policies SQL:
"HANA_Security_AuditPolicies
"
M1410 LICENSE global License usage (%) SQL:

"HANA_License_LicenseUsag
e"
M1415 LICENSE global License expiration (days) SQL:

"HANA_License_Overview"
M1420 LICENSE global Permanent license SQL:

"HANA_License_Overview"
M1510 NETWORK global Avg. intra node send throughput SQL:
(MB/s) "HANA_Network_Services"
M1512 NETWORK scale-out Avg. inter node send throughput SQL:

(MB/s) "HANA_Network_Services"
M1520 NETWORK Rev. >= Retransmitted TCP segments (%) SQL:
1.00.100 "HANA_Network_Statistics"
M1522 NETWORK Rev. >= Bad TCP segments (%) SQL:

1.00.100 "HANA_Network_Statistics"
M1524 NETWORK Rev. >= Current network collision share (%) SQL:
2.00.020 "HANA_Network_Statistics_C
urrentDetails"
M1525 NETWORK Rev. >= Current send error share (%) SQL:
urrentDetails"
M1526 NETWORK Rev. >= Current receive error share (%) SQL:
urrentDetails"
M1530 NETWORK global Avg. intra node communication SQL:

volume (MB/s) "HANA_Network_Services"
M1532 NETWORK scale-out Avg. inter node communication SQL:
volume (MB/s) "HANA_Network_Services"
M1540 NETWORK global Host name resolution for non IP SQL:

addresses "HANA_Configuration_Infrastr
ucture"
M1550 NETWORK global Network Poll thread state share (%, SQL:
last day) "HANA_Threads_ThreadSam
M1551 NETWORK global Network Read thread state share SQL:

(%, last day) "HANA_Threads_ThreadSam
M1552 NETWORK global Network Write thread state share SQL:
(%, last day) "HANA_Threads_ThreadSam
M1610 XS global Log segment size of xsengine (MB) SQL:

ENGINE "HANA_Logs_LogBuffers"
M1710 NAMESER Rev. >= Avg. load history ping time (ms, last SQL:
VER 1.00.90 hour) "HANA_LoadHistory_Services
"
M1712 NAMESER Rev. >= Avg. load history ping time (ms, last SQL:
VER 1.00.90 day) "HANA_LoadHistory_Services
"
M1720 NAMESER Rev. >= Supported nameserver lock file SQL:

VER 1.00.91 location "HANA_TraceFiles_Content"
M1810 SYSTEM SR Services with replication error SQL:

REPLICATI "HANA_Replication_SystemR
ON eplication_Status"
M1811 SYSTEM SR Service with unknown replication SQL:

REPLICATI state "HANA_Replication_SystemR
M1813 SYSTEM SR, Rev. Replication connection closed (last SQL:
REPLICATI >= day) "HANA_StatisticsServer_Alert
ON 1.00.90 s_Reported"
M1814 SYSTEM SR Log position gap (MB) SQL:

ON eplication_KeyFigures"
M1815 SYSTEM SR Current log shipping delay (s) SQL:

M1816 SYSTEM SR Filling level of async shipping buffer SQL:

REPLICATI (%) "HANA_Replication_SystemR
M1818 SYSTEM SR Async log shipping buffer full (last SQL:
REPLICATI day) "HANA_Replication_SystemR
M1820 SYSTEM SR Parameter deviations primary vs. SQL:

REPLICATI secondary site "HANA_Replication_SystemR
ON eplication_ParameterDeviation
s"
M1830 SYSTEM SR Age of oldest replication snapshot SQL: "HANA_IO_Snapshots"
REPLICATI (h)
ON
M1835 SYSTEM SR Max. initial data shipping time (h) SQL:

ON eplication_Overview"
M1840 SYSTEM Avg. sync log shipping time SQL:
REPLICATI (ms/req, last hour) "HANA_Replication_SystemR
SR
M1843 SYSTEM Avg. sync log shipping time SQL:

REPLICATI (ms/req, last day) "HANA_Replication_SystemR
SR
M1846 SYSTEM Max. sync log shipping time SQL:

REPLICATI (ms/req, history) "HANA_Replication_SystemR
SR
M1850 SYSTEM System replication op. mode SQL:
REPLICATI logreplay used "HANA_Replication_SystemR
SR
M1852 SYSTEM Current log replay backlog (GB) SQL:

SR
M1853 SYSTEM Current log replay delay (s) SQL:
SR
M1854 SYSTEM Max. log replay backlog (GB, last SQL:

REPLICATI week) "HANA_Replication_SystemR
SR
M1855 SYSTEM Max. log replay delay (s, last week) SQL:
SR
M1860 SYSTEM Datashipping combined with log SQL:

REPLICATI retention "HANA_Configuration_Param
ON eters_Values"
SR
M1861 SYSTEM Both delta_datashipping and SQL:
REPLICATI logreplay used "HANA_Replication_SystemR
SR
M1865 SYSTEM System replication savepoint delay SQL:

REPLICATI (h) "HANA_Replication_SystemR
SR
M1910 OBJECTS Rev. <= Maximum object ID SQL:
1.00.85.0 "HANA_Objects_Overview"
3,
Rev.
1.00.90 -
1.00.95
M1920 OBJECTS Number of invalid procedures SQL:
"HANA_Objects_Procedures"
global
M1930 OBJECTS Synonyms with names identical to SQL:
table name "HANA_Synonyms_IdenticalT
ableNames"
ABAP
M1940 OBJECTS Sequences with insufficient caching SQL:

"HANA_Configuration_Sequen
ces"
global
M1945 OBJECTS Cross node triggers SQL:
"HANA_Configuration_Trigger
s_CrossNodeTriggers"
global
M1950 OBJECTS Columns with significant text SQL:

indexing errors "HANA_Indexes_TextIndexes_
IndexingQueues"
global
M1952 OBJECTS Documents queued for fulltext SQL:
indexing "HANA_Indexes_TextIndexes_
IndexingQueues"
global
M2010 BW Empty TABLE_PLACEMENT table

in BW scale-out
BW,
scale-out
M2020 BW Partitioned SID tables SQL:

BW PartitionedTables"
M2022 BW SID tables > 1.5 billion rows SQL:

Records"
BW
M2025 BW Partitioned special BW tables < 1.5 SQL:
bill. rows "HANA_Tables_ColumnStore_
PartitionedTables"
BW
M2027 BW Tables with high sub-partition SQL:

PARTNO "HANA_Tables_TablePartition
s"
BW
M2030 BW BW scale-out installation on 2 SQL:

nodes "HANA_Configuration_Overvie
w"
BW,
scale-out
M2040 BW Temporary BW tables SQL:

"HANA_Tables_SpecialTables"
BW
M2042 BW BW aggregate tables SQL:
"HANA_Tables_SpecialTables"
BW
M2044 BW Old temporary calculation scenarios SQL:

"HANA_CalculationEngine_Ca
lculationScenarios"
BW
M2050 BW BW tables with inverted hash SQL:

indexes "HANA_Indexes_Columns"
BW
M2110 CONSISTE CHECK_TABLE_CONSISTENCY SQL:

NCY Rev. >= errors (last month) "HANA_Consistency_CheckTa
1.00.100 bleConsistency_Results"
M2112 CONSISTE Last consistency check via stat. SQL:

NCY server (days) "HANA_StatisticsServer_Sche
dule"
Rev. >=
1.00.100
M2113 CONSISTE Last global table consistency check SQL:
NCY (days) "HANA_Threads_ThreadSam
global
M2115 CONSISTE Tables without recent consistency SQL:

NCY check "HANA_Consistency_CheckTa
bleConsistency_Tables"
Rev. >=
2.00.010
M2116 CONSISTE Tables with consistency check SQL:

NCY errors "HANA_Consistency_CheckTa
bleConsistency_Tables"
Rev. >=
2.00.010
M2120 CONSISTE Large tables with risk of index SQL:
NCY corruption "HANA_Tables_ColumnStore_
Rev. <= Records"
1.00.102.
03,
1.00.110
M2130 CONSISTE Inconsistencies between topology SQL:

NCY and daemon "HANA_Services_Overview"
global
M2135 CONSISTE Inconsistent node role definition in SQL:

NCY topology "HANA_Hosts_LandscapeCon
figuration"
scale-out
M2140 CONSISTE Inconsistencies of metadata and SQL:

NCY dependencies "HANA_Consistency_ObjectD
ependency"
global
M2210 SMART SDA tables without statistics SQL:

DATA "HANA_SmartDataAccess_Ta
ACCESS / bles"
SMART
global
DATA
INTEGRATI
ON
M2220 SMART SDI remote subscription exceptions SQL:
DATA "HANA_SmartDataIntegration
ACCESS / _RemoteSubscriptionExceptio
SMART ns"
global
DATA
INTEGRATI
ON
M2222 SMART SDI max. remote subscription apply SQL:

DATA delay (s) "HANA_SmartDataIntegration
ACCESS / _RemoteSubscriptionStatistics
SMART "
DATA
INTEGRATI
ON
glob
M2230 SMART Slave nodes with dpserver SQL:

DATA processes "HANA_Services_Overview"
ACCESS /
SMART
DATA
INTEGRATI
ON
scale-out
M2310 ADMINIST SAP HANA Studio connections SQL:

RATION "HANA_Connections_Overvie
w"
global
global
M2315 ADMINIST Connections with old SAP HANA SQL:

RATION Studio versions "HANA_Connections_Overvie
w"
global
M2320 ADMINIST Time since last hdbcons execution SQL:

RATION (h) "HANA_Threads_ThreadSam
global
M2330 ADMINIST Parameters set on host level SQL:
RATION "HANA_Configuration_Param
eters_Values"
global
M2332 ADMINIST Parameter changes requiring a SQL:

RATION SAP HANA restart "HANA_Configuration_Param
eters_Values"
Rev. >=
2.00.040
M2334 ADMINIST Parameters with unsupported value SQL:
RATION "HANA_Configuration_Param
eters_Values"
Rev. >=
2.00.040
M2340 ADMINIST Deprecated features used (last 30 SQL:

RATION days) "HANA_Features_FeatureUsa
ge"
global
M2410 TABLE Inactive table replicas SQL:

REPLICATI "HANA_Replication_TableRepl
ON Rev. >= ication_Replicas"
1.00.120
M2415 TABLE Last table replication deactivation SQL:
REPLICATI dump (days) "HANA_TraceFiles_Overview"
ON Rev. >=
1.00.122.
17, >=
2.00.2
M2510 SLT Orphan SLT sequences SQL:

global "HANA_SLT_OrphanSequenc
es"
M2610 ENTERPRI Orphan calculated ESH columns SQL:
SE "HANA_Tables_ColumnStore_
SEARCH Columns"
Rev. >=
2.00.000
Potential impact SAP Details
Note
Performance
degradations,
terminations, wrong In general you should
results, unplanned make sure that you
downtime are on a rather recent
2021789 revision level,
optimally a
maintenance revision
or data center service
point.
2617548
SAP Note 2375691 describes a critical crash and corruption bug that impacts many SAP HAN
It is strongly recommended to use at least SAP HANA 1.0 SPS 12 (SAP Note 2617548).
Terminations, 2177064 If SAP HANA

unplanned downtime services are not
started, certain
functionalities may
not be available.
Therefore check the
related trace files and
make sure that all
services can be
started successfully.
Unplanned downtime 2177064 A varying host startup
time can indicate
problems on some
hosts. Make sure you
understand the
reason for the varying
start time and
eliminate potentically
critical root causes.
Unplanned downtime 2177064 A varying service

startup time can
indicate problems of
some services. Make
sure you understand
the reason for the
varying start time and
eliminate potentically
critical root causes.
Erroneous alerts, Check if there is an

unplanned downtime inconsistency
between nameserver
2222249 topology and daemon
configuration.
Risk of OOM and Make sure that on

memory corruptions SLES 11.x and Power
you implement the
bigmem flavor in
2240716 order to increase the
maximum address
space.
Lack of support Make sure that you

use an operating
system that is both
supported by the
operating system
partner and SAP.
Performance 2235581 Make sure that a

degradations 2812427 reasonably new
operating system
Performance
A low CPU frequency
degradations
is often the
consequence of a
CPU power-save
mode. Make sure on
OS side that no CPU
runs in power-save
mode.
2235581
Systems on RHEL >=

7 and SLES >= 12
are no longer
checked as the
intel_pstate driver
would result in wrong
alerts.
Performance
degradations A varying CPU
frequency is often the
consequence of a
CPU power-save
mode. Make sure on
OS side that no CPU
runs in power-save
mode and that the
nodes of a SAP
HANA scaleout
2235581 scenario use the
same type of CPUs.
Systems on RHEL >=

7 and SLES >= 12
are no longer
checked as the
intel_pstate driver
would result in wrong
alerts.
Performance
degradations For SAP HANA 2.0
certain CPU types
are strongly
recommended. Make
sure that you use
2399995 supported CPU types
or take into account
the risk of
performance
regressions using
earlier CPU types.
Performance Investigate in the

degradations current top
contributors to CPU
time (system vs. user
CPU, SAP HANA vs.
non SAP HANA CPU,
2100040 top HANA internal
CPU consumers) and
eliminate CPU
bottleneck situations.
Performance Investigate in
degradations the recent top
contributors to CPU
CPU, SAP HANA vs.
non SAP HANA CPU,
CPU consumers) and
eliminate CPU

degradations historic top
contributors to CPU
CPU, SAP HANA vs.
non SAP HANA CPU,
CPU consumers) and
eliminate CPU
Performance Check which
degradations processes are
responsible for the
high system CPU
consumption and
take appropriate
actions to reduce the
system CPU
2100040 consumption (e.g. by
optimizing the
operating system
configuration or by
avoiding active
waiting within SAP
HANA).
Performance
degradations
This check compares the host CPU consumption with all the service CPU consumptions meas
A SAP HANA service

that isn't covered by
2100040 the load history
Another SAP HANA

tenant
Another application
or operating system
process
Check if the external
CPU overhead can
be explained and
accepted (e.g.
because it is another
active tenant). If not,
take appropriate
external CPU
consumption.
reduced analysis Due to a Linux issue it can happen that the SAP HANA load history shows system CPU identic
capabilities
2222110
Risk of NUMA issues

The value for
cpu_sockets in
M_HOST_INFORMA
TION is different from
the number of NUMA
nodes shown in
M_NUMA_NODES
(for a particular host /
port). This can
indicate underlying
NUMA configuration
2470289 issues that should be
analyzed and
resolved.
You can use hdbcons (SAP Note 2222218) with command 'jexec info' in order to display NUM

degradations, current top
terminations contributors to
memory allocation
and take appropriate
1999997 actions to reduce the
memory
consumption.
Performance Investigate in
degradations, the historic top
terminations contributors to
memory allocation
and take appropriate
1999997 actions to reduce the
memory
consumption.
Performance In Intel contexts with more than 8 CPU sockets hyperthreading should usually not be activate
degradations
2711650
Performance A high CPU utilization
degradations of specific NUMA
nodes can indicate
problems with CPU
load distribution or
NUMA configuration.
An analysis is of
particular importance
when some NUMA
2470289 nodes are
permanently very
busy while others are
mainly idle.
Performance An increased CPU steal share indicates that CPU resources are used by different components
degradations
2100040
Performance 1999997 Check why the

degradations, amount of physical
terminations memory varies
between SAP HANA
hosts and use hosts
with an identical
amount of physical
memory unless there
is a very specific
reason for the
deviation.
Performance 1999997
degradations,
terminations Make sure that the
total memory
consumption of SAP
HANA and other
software components
doesn't exceed the
available physical
memory. Check on
operating system
level why a significant
amount of swap
space is used and
take appropriate
swap space
utilization.
Performance 1999997
degradations,
terminations Make sure that the
total memory
consumption of SAP
HANA and other
software components
doesn't exceed the
available physical
memory. Check on
operating system
level why a significant
amount of swap
space was used and
take appropriate
swap space
utilization.
Performance 1999997
degradations,
terminations
Make sure that the total memory consumption of SAP HANA and other software component
Performance 1999997
degradations in case
of swapping It is usually better if
an OOM is triggered
when the memory is
scarce on OS side,
because swapping
can reduce the
system performance
significantly.
Therefore it is
recommended to use
a rather small swap
space.
SAP Note 2661792 describes a bug that can result in a wrong SAP HANA swap space calculati
Stuck situations, Take appropriate
failing backups actions in order to
1870858 make sure that SAP
HANA file system
overflows will not
happen
Terminations Configure an open
files limit of at least
2600030 100,000 on operating
system side.

100,000 on operating
system side. Check
why a significant
2600030 amount of file
handles is opened
concurrently by SAP
HANA.

100,000 on operating
system side. Check
why a significant
2600030 amount of file
handles is opened
concurrently by SAP
HANA.
Terminations Set the Linux

parameter fs.aio-
max-nr to
18446744073709551
615.
1868829
Be aware that the
underlying data is
only available with
SAP HANA >=
2.00.040.
OOM
Make sure that the
Linux parameter
vm.max_map_count
is set to 2147483647
(or an individually
calculated sufficiently
1980196 large value).
Be aware that the

underlying data is
only available with
SAP HANA >=
2.00.040.
Terminations, Make sure that the
performance Linux parameter
net.core.somaxconn
is set to at least
4096.
2382421
Be aware that the
underlying data is
only available with
SAP HANA >=
2.00.040.
Terminations, Make sure that the
performance Linux parameter
net.ipv4.tcp_max_syn
_backlog is set to at
least 8192.
2382421
Be aware that the
underlying data is
only available with
SAP HANA >=
2.00.040.
Terminations,
Configure Linux
performance
parameter
net.ipv4.ip_local_port
_range in a way that
at least 30000
ephemeral ports are
available on Linux
level.
2382421
2382421
Be aware that the

underlying data is
only available with
SAP HANA >=
2.00.040 and only in
the system database.
Missing information Make sure that

properly named and
1828631 filled hardware
information files are
available.
Various risks in Make sure that the

areas like system clocks on the
supportability and hosts of a SAP HANA
recovery scale-out solution
provide a nearly
identical time.
Performance Check for bottlenecks

degradations and possible
optimizations in the
1999930 I/O stack related to
read accesses to the
data area (operating
system, file system,
the read accesses to
Increased startup
times
This check measures
the average data load
throughput after SAP
HANA restart, so
basically the column
store load. If the
throughput is too low,
the time to load the
column store can be
quite high.
1999930
Check for bottlenecks

and possible
I/O stack related
to read accesses to
the data area
(operating system,
file system, network
to I/O sub system,
I/O sub system).

1999930 I/O stack related
to write accesses to
the data area
(operating system,
the data area
(operating system,
Performance Check why reading
degradations from the data area
requires significant
1999930 absolute time (e.g.
due to high amount of
read activity or slow
I/O).
Performance Check why writing to
degradations the the data area
requires significant
Performance
degradations

due to high amount
of write activity or
slow I/O).
to read accesses to
the log area
(operating system,
to read accesses to
the log area
(operating system,
Performance Check why writing to
degradations the log area requires
significant absolute
1999930 time (e.g. due to high
amount of write
activity or slow I/O).

the log area
(operating system,
the log area
(operating system,
the log area
(operating system,
Performance
degradations Check for bottlenecks
and possible
I/O stack related
the log area
(operating system,
to I/O sub system,
1999930
I/O sub system).
I/O write performance

to the log area is
most important in
terms of commit
performance.
and possible
Performance optimizations in the
degradations I/O stack related
1999930 to write accesses to
the log area
(operating system,
to I/O sub system,
Performance Make sure that
degradations asynchronous
1930979 queuing of I/O
requests is activated.
Performance Make sure that

degradations asynchronous
1930979 queuing of I/O
requests is activated.
Performance 2215131 Increase the size and

degradations / or number of the log
buffers in order to
reduce the
contention.
Performance 2215131 Increase the size and

degradations / or number of the log
buffers in order to
reduce the
contention.
Performance Check and optimize SAP HANA internal lock contention (SAP Note 1999998) related to savep
degradations
2100009

I/O stack related
the data area
2100009 (operating system,
to I/O sub system,
I/O sub system).
Performance Check for reasons of

degradations long blocking
savepoint phases like
2100009 internal lock
contention or I/O
write bottlenecks and
optimize them.

contention or I/O
optimize them.

contention or I/O
optimize them.
Increased recovery
times Check for bottlenecks
and possible
I/O stack related
the data area
(operating system,
to I/O sub system,
2100009
I/O sub system).
Make sure that

global.ini ->
[persistence] ->
savepoint_interval_s
is not set to very high
values.
Performance
degradations Check for bottlenecks
and possible
I/O stack related
2100009 to write accesses to
the data area
(operating system,
to I/O sub system,
I/O sub system).

I/O stack related
the data area
to I/O sub system,
I/O sub system).
I/O stack related
the data area
to I/O sub system,
I/O sub system).
Terminations 1999930
Check when and on
which disk areas the
errors happened and
take appropriate
actions to avoid failed
reads in the future.
The check is based

on the RESET view.
In order to avoid that
historic and already
analyzed failures are
still reported, you can
reset the view:
ALTER SYSTEM
RESET MONITORING
VIEW
M_VOLUME_IO_TOTA
L_STATISTICS_RESET
Check when and on
which disk areas the
errors happened and
take appropriate
actions to avoid
failed writes in the
future.
The check is based
on the RESET view.
In order to avoid that
historic and already
analyzed failures are
still reported, you can
reset the view:
ALTER SYSTEM
RESET MONITORING
VIEW
M_VOLUME_IO_TOTA
L_STATISTICS_RESET
Performance 1999930 Check for the main

degradations contributors of the
high redo log volume
(e.g. large full loads,
modification
operations)
and reduce the
amount of database
changes if possible.
Performance 1999930 Check for the main

degradations contributors of the
high redo log volume
(e.g. large full loads,
modification
operations)
and reduce the
amount of database
changes if possible.
Performance 1930979 Make sure that the

degradations SAP HANA I/O
parameter settings
are in line with the
recommendations.
Be aware that SAP
HANA may display
wrong values up to
Rev. 122.03, so you
can't rely on the
output
of SQL: "HANA_IO_K
eyFigures_Total" on
these Revisions.
Risk of performance 1999930

degradations and
terminations
Make sure that you only use filesystem types that are supported for your SAP HANA environm
Increased data disk 1870858 Reorganize the disk

space requirements area using ALTER
SYSTEM RECLAIM
DATAVOLUME.
Increased data disk 2220627 Check if you can
space requirements reduce LOB internal
fragmentation, e.g. by
conversion of LOBs
with particularly small
values and high
fragmentation to
packed LOBs.
Increased startup 2220627 Check if you can perform housekeeping (SAP Note 2388483) or convert the LOBs of the men
times and disk space
requirements
Increased startup 2220627
times and disk space
requirements
Check if you can perform housekeeping (SAP Note 2388483) or convert the LOBs of the men
This check is similar

to check M0373
above, but it doesn't
focus on small LOBs
and uses a higher
LOB count threshold.
Risk of file system The SAP HANA disk

overflows and requirements can
system down increase significantly
situations within short times, so
it is useful to
configure the disk
size significantly
larger than usually
required to be
prepared for special
situations.
Increased data disk Database snapshots

space requirements can increase the data
disk space
requirements and so
you should delete
2100009 them when they are
no longer required for
a specific reason.
Increased data disk Database snapshots
space requirements can increase the data
disk space
requirements and so
you should delete
2100009 them when they are
no longer required for
a specific reason.
Increased data disk Check for reasons of

space requirements increased amounts of
shadow pages and
try to avoid massive
peaks by reasonable
savepoint
configuration,
balancing of change
2100009
load and minimizing
merges and
compressions of
large tables.
Risk of performance
issues Check why a
particularly high
amount of data is
written during
savepoints (e.g. due
to unnecessary
modifications from
application side,
inadequate table
optimization
configuration, SAP
2100009 HANA parameter
settings or known
bugs).
Tempporary
increased values can
be acceptable in
context of a high
amount of intended
modifications or table
optimizations.
Risk of performance
issues
Identify the root
cause of a
particularly high
number of savepoint
prepare flush retries
(e.g. due to due to
unnecessary
modifications from
application side,
inadequate table
optimization
2100009 configuration, SAP
HANA parameter
settings or known
bugs).
Temporary increased
values can be
acceptable in context
of a high amount of
intended
modifications.
Risk of performance
issues
Identify the root
cause of a
particularly high
number of savepoint
prepare flush retries
(e.g. due to due to
unnecessary
2100009 modifications from
application side,
inadequate table
optimization
configuration, SAP
HANA parameter
settings or known
bugs).
Unloads, out of 1999997 Check the current
memory, memory utilization
performance and identify and
degradations resolve reasons
which are responsible
for the used memory
coming close to the
allocation limit.
Unloads, out of 1999997 Check if the amount

memory, of memory allocated
performance by tables can be
degradations reduced and if the
system is properly
sized in terms of
memory.
Unloads, out of 1999997 Check the historic

memory, memory utilization
performance and identify and
degradations resolve reasons
for the used memory
coming close to the
allocation limit.
Unloads, out of 1999997 Check the current

memory, memory utilization of
performance the critical services
degradations and identify and
resolve reasons
for the used memory
coming close to the
allocation limit or
increase the service
specific allocation
limit.
Unloads, out of 1999997 Check the historic
memory, memory utilization of
performance the critical services
degradations and identify and
resolve reasons
for the used memory
coming close to the
allocation limit or
increase the service
specific allocation
limit.
Unloads, out of 1999997 Check if you can

memory, reduce the memory
performance allocation of the
degradations largest heap areas.
Unloads, out of 1999997 Check if you can
memory, reduce the memory
performance allocation of the
degradations largest heap areas.
Unloads, out of 1999997 Check why the heap
memory, allocators have
performance grown to significant
degradations sizes in the past and
if you can reduce the
memory allocation of
the largest heap
areas.
Unloads, out of 1999997 Check if there are known memory leak issues. Consider the creation of an allocator block list
memory,
performance
degradations
Unloads, out of 1999997
Monitor the growth
memory,
and restart SAP
performance
HANA if required.
degradations
Upgrade to revision
1.00.83 or higher in
order to eliminate a
related bug.
2169283
An increased leak size can also be the consequence of a blocked garbage collection (SAP Not
Unloads, out of 2362759

memory,
performance
degradations
A bug with SAP HANA Rev. 111 to 112.05 and 120 to 122.01 can result in row store memory
2169283
An increased leak size can also be the consequence of a blocked garbage collection (SAP Not
Performance 2127458 Check why unloads

degradations were triggered (e.g.
high memory
consumption or
inadequate
configuration of
unload_lower_bound)
high memory
consumption or
inadequate
configuration of
unload_lower_bound)
Performance 2127458 Make sure that "resman shrink" / unload_upper_bound is configured with a reasonably high
degradations

high memory
consumption or
inadequate
configuration of
unload_lower_bound)
Performance 1999997 Check why significant

degradations time is spent to
perform memory
defragmentation and
try to reduce it (e.g.
by optimizing the
memory utilization or
configuration).
Performance 1999997
degradations
Check why significant
time is spent to
perform memory
defragmentation and
try to reduce it (e.g.
by optimizing the
memory utilization or
configuration).
This check is based
on the RESET view
so you can manually
reset it if you want to
make sure that
previous long
runtimes are no
longer considered by
the next mini check
runs:
ALTER SYSTEM
RESET MONITORING
VIEW
M_MEMORY_RECLAIM
_STATISTICS_RESET
Terminations 1977101 Increase the

nameserver topology
size or reduce the
number of
(temporary) tables.
Terminations 1999997 Check memory

limitations (GAL, PAL,
statement memory
limit) and / or
optimize the memory
footpring of
expensive queries.
Increased memory 1994962 Make sure that large

consumption memory LOBs are
converted into hybrid
LOBs in order to
reduce the memory
footprint.
Increased memory 1986747 Check if the largest
consumption non-unique concat
attributes are really
required or if they can
be eliminated (e.g. by
switching to single
column indexes or by
dropping no longer
required relics).
Increased memory 1986747 Check if the largest

consumption non-unique concat
attributes are really
required or if they can
be eliminated (e.g. by
switching to single
column indexes or by
dropping no longer
required relics).
Increased memory 1986747

consumption Check for what
purpose the reported
concat attributes exist
and consider
dropping them in
case they exist for no
apparent reason.
Be aware that a SAP

HANA restart resets
this counter to 0 and
so it will take some
time until all
important concat
attribute utilizations
are properly tracked.

Check if the
consumption
mentioned indexes
are still required from
application
perspective and
consider to drop them
if possible.
Be aware that a SAP
HANA restart resets
this counter to 0 and
so it will take some
time until all
important index
utilizations are
properly tracked.
Performance
degradations
Increase the size of
the calculation engine
cache size, so that it
can concurrently
keep all required
calculation scenarios:
indexserver.ini ->
[calcengine] ->
max_cache_size_kb
= <size_kb>

consumption
Check if the
increased cache
sizes are expected
and reasonable. If
not, take appropriate
actions (adjustments
on application side,
implementation of
fixes, purging of
caches) to reduce the
size to normal levels.
Increased 1999997
Check why specific
nameserver ping allocators exist very
times, memory frequently and take
bottlenecks appropriate actions to
reduce them.
OOM terminations 1999997
If SAP HANA erroneously records higher memory allocations in M_CONTEXT_MEMORY than
OOM situations 1999997

Optimize the
available address
space and its
utilization, e.g. by
avoiding manual
memory garbage
collection activities,
reducing the SAP
HANA memory
footprint or using the
bigmem flavor on
IBM Power systems.
Performance 2044468 Check if the high

degradations, high amount of partitions
resource is really required.
consumption
Performance and 1999997
memory overhead Avoid tables with a
high amount of
columns because of
disadvantages like:
2000002
Increased runtime of
"SELECT *" in
column store tables
Increased size of
heap allocator
Pool/malloc/libhdbcs
md.so due to a high
amount of column
metadata
Performance 2044468 Check if it is possible

degradations to use hash
partitioning based on
a single, selective
column.
Risk of corruptions 2436619 Inverted hash

indexes can result in
corruptions when a
table is repartitioned
so you should avoid
to define inverted
hash indexes on
partitioned tables.
Risk of corruptions 2109355 Due to a SAP HANA

bug inverted hash
indexes can result in
corruptions with SAP
HANA 2.00.010 -
2.00.024.08 and
2.00.030 - 2.00.036
and so this index type
should be avoided
with these Revision
levels.
Risk of performance 2044468 The overflow
overhead partitions in context
of range partitioning
are meant to contain
records that don't
match any provided
partition value range
and usually the
amount of records in
these partitions
should be small.
Check for what
reason a siginficant
amount of records is
stored in the overflow
partition and consider
a repartitioning of the
table to reduce the
record share of the
overflow partition.
Activate or extend
partitioning in order to
keep the amount of
records per table
(partition)
permanently below
the two billion limit.
BW SID tables
(typically following
the naming
convention /B%/S%
are excluded from
this check, because
they can never grow
beyond two billion
records and
partitioning can be
critical. See Check ID
2022 instead.
Terminations 1921694 Activate or extend
partitioning in order to
keep the amount of
records per
table history (partition
) permanently below
the two billion limit.
Terminations 2112604 Force an optimize

compression run on
the impacted tables
in order to minimize
the amount of UDIV
rows.
Terminations 2154870 TEXT columns are

tokenized and so the
distinct tokens can be
significantly higher
than the actual
number of records. In
order to avoid
running into the 2^31
limit you need to
make sure that the
amount of distinct
tokens is limited.
Only use the TEXT
data type if it is really
useful. For example,
you should not store
compressed data in a
TEXT column
because some
characters in the
compressed data
(e.g. "/") may be
interpreted as token
separator.
High resource 2044468 Large table
consumption (partitions) can be
responsible for a high
resource
consumption in terms
of CPU, memory and
I/O, in particular
during table
optimizations like
merges or
compressions.
Therefore you should
check if you can
implement
partitioning in a way
that the partition are
kept at reasonable
sizes.
High resource 2044468 Large table

consumption (partitions) can be
responsible for a high
resource
consumption in terms
of CPU, memory and
I/O, in particular
during table
optimizations like
merges or
compressions.
check if you can
implement
partitioning in a way
that the partition are
kept at reasonable
sizes.
Increased startup 2050579 Check for largest

time, terminations 1963779 tables in row store
Risk of performance 2000002 whether data can be
regressions Reorganize the
mentioned tables
during a time of low
system load in order
to avoid overhead
and performance
regressions:
ALTER TABLE
"<table_name>"
RECLAIM DATA
SPACE
Increased memory 1813245 Reorganize the row

consumption store in order to
minimize
fragmentation.
Increased resource 2057046 Check if the long
consumption running merges are
normal or if they can
be avoided (e.g. by
using default merge
parameter settings or
by reducing the data
volume)
Increased resource 2057046

consumption
Check why a
significant amount of
critical merges is
executed. In case of
many static tables it
can happen that no
auto or smart merge
kicks in and after one
week the critical
merge is started
regardless of the
amount of table
changes. In this case
it can be useful to
adjust the critical
merge decision
function so that
critical merges are no
longer performed
unnecessarily.
Be aware that in
systems with low
workload there is a
higher probability of
an increased critical
merge share. This is
typically not critical in
context of low
workload.
Increased resource 2057046 Check if it is possible

consumption, to reduce the amount
terminations of terminations of
merges with
informational
messages.
Increased memory 2057046 Check the individual

consumption, error messages and
terminations take appropriate
actions to prevent
critical terminations.
Increased memory 1977314 Check if delta

consumption storages permanently
remain on a high
level. If yes, check
why no merge
happens and take
appropriate actions to
make sure that
merges are
performed.

remain on a high
why no merge
happens and take
make sure that
merges are
performed.
remain on a high
why no merge
happens and take
make sure that
merges are
performed.

remain on a high
why no merge
happens and take
make sure that
merges are
performed.
Increased memory 2057046 Consider adjusting the auto merge decision function so that smaller tables are merged more
consumption

Check if auto merge
consumption is disabled on
purpose and
reactivate it if
possible.
A typical reason for a disabled auto merge is described in SAP Note 2196615: A move of a tab
Increased memory 2057046 Check if persistent

consumption merge is disabled on
purpose and
reactivate it if
possible.
Increased memory
consumption Check if the auto
compression is
disabled on purpose
and reactivate it if
possible.
2112604
A typical reason for a disabled auto optimize compression attribute is described in SAP Note
Also an EXPORT /
IMPORT can result in
lost auto
compression.
Crashes, 2038897 Make sure that
terminations ST_POINT columns
don't exist for row
store tables.
Performance 2100040 For timezone operations without conversion overhead it is important that the timezone table
regressions
Performance 2100040 For timezone operations without conversion overhead it is important that the timezone table
regressions
Risk of corruptions 2066313 Make sure that tables

are moved physically.
Increased memory 2105761 Make sure that an
consumption 2112604 optimization of
compression
Increased memory Make sure that large
consumption columns are
compressed
efficiently.
Be aware that there

is a chance of false
positives, i.e.
columns that are
2112604
reported although a
new compression will
not be able to
compress them
efficiently. In this case
you can ignore the
related tables in the
future and don't start
more manual
compression runs.
Performance For some reasons single column index structures may be missing. See SAP Note 2160391 -> "
regressions
2160391
Performance Indexes can't be used

regressions on columns being
compressed with
SPARSE (Rev. <=
122.02) or
PREFIXED type.
2112604
2112604
Execute an optimize
compression run in
order to make sure
that indexed columns
are not compressed
with SPARSE or
PREFIXED.
Increased memory Force a compression

consumption optimization after
2112604 large deletions of
data if required.
Increased memory Force a compression

consumption optimization in order
to clean up
fragmentation in the
2112604 internal column store
version
administration.
Increased memory 2112604 Force a compression

consumption 2387064 optimization in order
Risk of 2593893 to clean up
administration and Keep the amount of
resource overhead temporary SAP
HANA tables at a
limited level and drop
temporary tables
when they are no
longer needed.
Temporary tables
with names following
the naming
convention
_SYS_PARAM_ITAB*
are typically linked to
FDA processing (SAP
Note 2399993). In
case of many ABAP
work processes it is
recommended to
reduce the size of the
ABAP statement
cache
(dbs/hdb/stmt_cache
_size, SAP
Note 2600030). This
will implicitly also
reduce the number of
FDA related
temporary tables.
Performance 2214569
regressions
If you face issues
related to a high
number of tables
defined with NO
LOGGING, you
should check why so
many NO LOGGING
tables exist
concurrently and
reduce their number.
In BW environments
the following cleanup
reports exist:
UJHANA_DELETE_B
PC_HC_TABLE:
Cleanup of temporary
BPC hierarchy tables
RSDDTMPTAB_DEL
ETE,
SAP_DROP_TMPTA
BLES: Cleanup of
temporary BW tables
As a workaround you
can increase the
following parameter
that defines the
maximum number of
NO LOGGING tables:
indexserver.ini ->
[catalog_watchdog]
->
max_nologging_table
_count_limit
Performance 2127458
regressions
Avoid to configure
small unused
retention periods on
table level in order to
eliminate the risk of
frequent reloads. In
general it is sufficient
to rely on the normal
SAP HANA resource
container
management that
kicks out the least
relevant content in
case a shrink is
required.
Risk of Make sure that all

inconsistencies and tables are assigned
terminations to proper services,
typically indexserver.
Risk of Investigate why
inconsistencies and tables without a
terminations properly assigned
location exist and
eliminate the
inconsistency.
Potential impact SAP Details

Note
Performance Disable the kernel
degradations profiler traces unless
1804811 really needed.
Performance 1787489 Disable the

degradations performance trace
unless really needed.
Performance 1787489 Disable the function

degradations profiler unless really
needed.
Be aware that this

check covers the
function profiler in the
context of the
performance trace.
Performance 2031647 Disable the SQL
degradations trace unless really
needed.
Performance Disable the

degradations indexserver python
1935113 trace unless really
needed.
Performance Disable the executor
degradations python trace unless
2020877 really needed.
Performance Disable the SQL

degradations client network trace
Performance 2180165 Don't use an
degradations expensive statement
trace threshold below
1000 ms unless really
needed.
Performance 2180165 Increase the

degradations expensive statement
trace threshold in
order to reduce the
amount of captured
SQL statements.
Analysis limitations 2180165

Check why there are
no older records
available in the
expensive statements
trace. Typical reasons
are:
Many statements are

captured so that the
available trace files
are overwritten within
less than a week
Trace files are

configured with
limited size or
number
Expensive
statements trace was
recently activated
and wasn't running
before
A system replication
takeover was done
so that older data
from primary site can
no longer be
accessed
Try to find capturing
thresholds so that the
expensive statements
trace data is
preserved for at least
7 days.
Performance 2380176 Don't configure
degradations special database
trace settings unless
really needed.
Performance 2119087 Don't configure user-

degradations specific trace settings
Performance 2119087 Don't configure end-

degradations to-end trace settings
Risk of tool 2797078 Avoid manually

terminations dropping backup logs
with SAP HANA >=
2.0 SPS 04 because
it may not be
automatically
recreated.
Increased disk space 2380176 Check for reasons of

requirements, the particularly high
performance amount of generated
degradations trace information
(activated traces,
misconfigurations,
errors) and reduce
the volume.
Increased disk space 2119087 Take appropriate

requirements actions to limit the
amount of existing
trace files.
amount of existing
trace files.
size of existing trace
files.
size of existing trace
files.
Increased disk space 2119087 Take appropriate actions to limit the size of existing trace files. For backup.log and backint.lo
requirements
Memory bottlenecks 1999997 Check the historic

memory utilization
and identify and
resolve reasons
for the out of memory
situations.
Terminations 1999997 Optimize SQL

statements with a
particularly high
memory
consumption.
Unplanned downtime 2177064 Check for reasons

responsible for
crashes and
eliminate them.
Corruptions 1977242 Analyze and repair
corruptions on
persistence level.
Increased system Check why the RTE

load dumps were
generated and make
sure that they are
only triggered
manually when really
required.
Various 2119087 Check why the dump

was created and
eliminate the root
cause.
Increased system 2100040 Disable the CPU time
load measurement unless
really needed.
Increased system 1999997 An activated allocation stack trace imposes some overhead in terms of CPU and performance
load
Increased system 1999997 Allocated memory

load traces (e.g. in context
of memory fencing,
SAP Note 2222276)
impose some
overhead in terms of
CPU and
performance (SAP
Note 2100040, call
stack module
MemoryManager::Ch
eckedBlockHandler::c
reateStacktrace).
Make sure that
memory traces traces
are only activated if
really required and
deactive them once
you have collected
sufficient data.
Increased system 1999997 Allocated memory
load traces (e.g. allocation
stack trace or
memory fencing, SAP
Note 2222276)
impose some
overhead in terms of
CPU and
performance (SAP
Note 2100040, call
stack module
MemoryManager::Ch
eckedBlockHandler::c
reateStacktrace).
Make sure that
memory traces traces
are only activated if
really required and
deactive them once
you have collected
sufficient data.
Performance and 2119087 Check if there are

infrastructure issues some general SAP
HANA issues (e.g.
resource bottleneck,
lock issues) or
infrastructure
problems (e.g. disk
I/O) and eliminate
these problems.
Various 2445867 Check the reported

alerts and resolve the
root cause or adjust
the alert thresholds.
Monitoring limitations 2445867 Check why retrieving

alerts runs into an
internal error and
eliminate the root
cause.
Monitoring limitations 2147247 Run SQL: "HANA_StatisticsServer_Alerts_History" with ALERT_ID = 0 and proceed as describe
Monitoring limitations 2147247 Check why alert

checks and / or
history collection
runs were not
executed with the
defined interval
frequency (e.g. high
system load, disabled
checks) and eliminate
the root cause.
Monitoring limitations 2147247 In rare cases no

statistics server
worker threads exist
although the statistics
server is supposed to
be active. In this case
you can only resolve
the problem by
restarting SAP
HANA. Additionally
you can open a SAP
incident in order to
identify the root
cause for the missing
worker threads.
Monitoring limitations 2113228 Check why the

actions are disabled
and activate them
again if possible.
actions are inactive
and activate them
again if possible.
Monitoring limitations 2147247
The STATE values in
the statistics server
control table
STATISTICS_SCHED
ULE must contain
one of the following
values:
Disabled
Idle
Inactive
Scheduled
If other values exist

(due to an earlier
faulty manual
update), the action
will never be
executed. Update the
values based on your
needs, e.g. to 'Idle'.

Check why the
events are not
acknowledged (e.g.
statistics server
problem) and take
make sure that an
acknowledgement
happens in time.
Often this problem is caused by the bug described in SAP Note 2126236 and it can be fixed b
Monitoring limitations 2133799 Check why sending
e-mails doesn't work,
clean up old mail
send requests and
take appropriate
actions to activate
sending e-mails.
Performance 2170779 Keep the amount of

regressions, alerts in table
increased memory STATISTICS_ALERT
consumption S_BASE at a
reasonable level.
Performance 2147247 Delete frequently

regressions, reported alerts and
increased memory make sure that the
consumption reporting frequency is
reduced.

statistics server isn't
active since a
significant time and
take appropriate
actions to activate it.
Performance 2124112 Proceed as described in SAP Note 2124112 -> "Which problems and solutions exist in the are
regressions
Increased memory 2147247 Make sure that data

consumption collection and
deletion is configured
optimally for the
statistics server
histories.
Increased memory 2147247 Make sure that data
consumption collection and
deletion is configured
optimally for the
statistics server
histories.
Increased memory 2084747 Delete records with

consumption EXECUTION_COUN
T = 0 from
HOST_SQL_PLAN_
CACHE and adjust
the data collection by
adding "WHERE
EXECUTION_COUN
T > 0" to the query
parameter.
Increased memory 2084747 Monitoring view

consumption M_CS_UNLOADS it
already a history,
because it is based
on load trace files. As
a consequence a
historization is not
useful and - even
worse - it can result
in a high memory
consumption of the
statistics server if
many unloads have
happened in the past.
disable the history
collection for
M_CS_UNLOADS.
Increased memory 2147247 The added value of
consumption, merge the
and lock issues HOST_RECORD_LO
CKS history is small
and at the same time
it can become huge
causing various
issues up to standstill
situations (e.g. due to
long running merge
blocking savepoint
and DML operations
with
ConsistentChangeLo
ck). Therefore it
should generally be
deactivated.
Monitoring limitations 2147247 Check to what

extent you can
increase the retention
times to 42 days
without suffering from
large table growth
and high memory
requirements.

Thread samples may
only be historicized
once an hour, so in
case of a crash or
shutdown up to 60
minutes of thread
samples are missing.
Make sure that

thread samples are
historicized at least
every 10 minutes:
UPDATE
_SYS_STATISTICS.STA
TISTICS_SCHEDULE
SET
INTERVALLENGTH =
600 WHERE ID =
5034
Monitoring limitations 2092033 Consider a migration

to the embedded
statistics server.
Monitoring 2092033 Complete a

limitations successful migration
to the embedded
statistics server.
Backup problems 2019148 Increase the log

segment size of the
statistics server to
1024 MB.
Monitoring limitations 2091256 Move all statistics
server tables to the
master node.
Increased memory 2147247 Entries with
consumption, merge OBJECT_NAME =
and lock issues '(unknown)' are
typically linked to
dropped temporary
tables and are
therefore of not much
use. You can delete
them in order to
reduce the size of the
history table.
An orphan entry for alert 32 in table STATISTICS_ALERT_INFORMATION of owner _SYS_STATI
DELETE FROM
_SYS_STATISTICS.STA
TISTICS_ALERT_INFO
RMATION
WHERE ALERT_ID =
32
Performance 2169283 Avoid long running

degradations transactions
responsible for a
MVCC versions.

responsible for a
MVCC versions.
responsible for a
MVCC versions.
Check why specific
records are modified
particularly frequently.

responsible for a
MVCC versions.
Check why
specific tables are
modified particularly
frequently.

responsible for a
MVCC versions.
Performance 2169283 Optimize particularly

degradations long running
transactions.

degradations long running
transactions.
Performance 2169283 Optimize particularly long running update transactions (i.e. transactions with change operati
degradations
degradations long running update
transactions (i.e.
transactions with
change operations).

degradations long running update
transactions (i.e.
transactions with
change operations).

degradations long running SQL
statements or idle
cursors.

degradations long running SQL
statements or idle
cursors.
Restart and recovery 2001840 Proceed according to

termination the steps in the
referenced SAP Note
in order to make sure
that you don't run into
restart and recovery
issues.
Performance 2169283 Check for long

degradations, running SQL
increased emory and statements, idle
disk space cursors and
requirements uncommitted update
transactions blocking
garbage collection.
Increased disk space 2633077 Due to a SAP HANA bug with Revisions 1.00.122.16, 2.00.024.00, 2.00.024.01 and 2.00.030 t
requirements
Increased disk space 2220627
requirements
See SAP Note 2220627 ("Can there be orphan disk LOBs?") and take appropriate actions to re
Increased memory 2169283 Avoid long running

and disk space transactions and
requirements open idle cursors
blocking garbage
collection.

and disk space
requirements
See SAP Note 2220627 ("Can there be orphan disk LOBs?") and check why the column store

blocking garbage
collection.

blocking garbage
collection.
Increased memory 2169283 Check if you can

and disk space reduce the amount of
requirements, performed change
increased I/O and operations or if you
system replication can reduce
load, longer restart the commit frequency
times in order to split the
change load into
several smaller
pieces.
Increased memory 2169283 Check if you can
and disk space reduce the amount of
requirements, performed change
increased I/O and operations or if you
system replication can reduce
load, longer restart the commit frequency
times in order to split the
change load into
several smaller
pieces.
Increased resource 2000000

consumption,
terminations
Check why a
rollbacks is executed,
e.g. by checking the
SAP HANA database
trace files (SAP
Note 2380176) and
client (e.g. ABAP)
traces for error and
eliminate reasons for
rollbacks. In case of
internal rollbacks it
may be required to
activate a SAP HANA
SQL trace (SAP
Note 2031647).
Typical reasons for
many rollbacks are:
SAP HANA <=

1.00.122.08, <=
2.00.002.00,
2.00.010:
ABAP_SYSTEM_TIM
EZONE calls
Performance 2000000 Check why sessions

regressions are currently pending
and eliminate SAP
HANA overload
situations.
Performance 2000000 Check why sessions
regressions were recently
pending and
eliminate SAP HANA
overload situations.
Performance 2222250 Check for reasons of

regressions queueing or
rejections of incoming
requests, e.g. high
load or inadequate
admission control
configuration.
Terminations 2222250 Check for reasons of

queueing or
requests, e.g. high
load or inadequate
admission control
configuration.
Performance 2222250 Check for reasons of

regressions queueing or
requests, e.g. high
load or inadequate
admission control
configuration.
Performance 1999998 A high activity time of

regressions the SelfWatchDog
thread can indicate
problems accessing
the lock file for
shared memory
accesses in the /tmp
directory. See SAP
Notes 1999998 and 2
100296 for more
information.
Hang scenarios 2222110 A gap in the load history data data collection often indicates a general issue of the database,
Risk of blocked 2092196

garbage collection
If a session
permanently remains
in a CANCEL
REQUESTED state
(e.g. "Running
(CANCEL
REQUESTED)"), it
can block garbage
collection (SAP
Note 2169283).
check if you can
successfully kill it. If
you don't succeed
and SAP
Note 2092196 doesn'
t indicate that it is an
already known bug,
open a SAP incident
to request
assistance.
Due to an
initialization bug it
can happen that a
connection related to
“Dynamic Range
Partitioning” is shown
with “Idle (CANCEL
REQUESTED)” with
SAP HANA <=
1.00.122.12. This can
be ignored and
doesn’t indicate a
problem.
This check compares the number of open connections with the maximum_connections limit
Performance 2256719
regressions
In rare situations a
bug with Rev. <=
102.02 and Rev. 110
can result in an
increased amount of
parked job workers.
As a consequence
the system
performance can
suffer and in the
worst case it comes
to standstill.
Consider an upgrade
to a more recent SAP
HANA Revision level
or alternatively restart
SAP HANA.
Performance 2222250
regressions
A repeatedly
increased number of
queued job workers
can indicate that the
job worker load (i.e.
parallelized activities)
is higher than the
available job workers.
See SAP
Note 2222250 for job
worker configuration
and SAP
Note 2000002 for
SQL statement
optimization.
Performance 2222250
regressions
The internally used
max_concurrency
limitation for job
workers can differ in
some cases
unintentionally from
the setting of the
related parameter,
e.g. because an
UNSET of the
parameter wasn't
properly considered
by the running
system. If the used
concurrency is much
smaller than the
intended one, the
number of job
workers is limited and
throughput can
reduce. In this case
you can as a
workaround manually
set max_concurrency
to a reasonably high
explicit value.
Starting with SAP
HANA 2.0 SPS 03
the max_concurrency
value is internally
adjusted in relation to
the new
max_concurrency_mi
n_pct setting and so
this check is
deactivated to avoid
false alerts.
Performance 2114710
regressions
Check for reasons why several currently active threads already run for a longer time (e.g. loc
Performance 2114710
regressions
Check if it is normal that the reported application users are responsible for a significant datab
Performance 2114710
regressions
A high amount of threads being active in an uncommon thread method can indicate issues a
Performance 2114710
regressions
A high amount of threads being active in an uncommon thread method can indicate issues a
Recoverability 1642148 Make sure that at

limitations least one successful
data backup is
created per day.
Recoverability 1642148 Identify and eliminate

limitations the root causes of the
backup failures and
make sure that at
least one successful
data backup is
created per day.
Disk I/O 1999930 Check and eliminate

performance bottlenecks in the
regressions disk I/O area to the
data files.
Disk I/O 1999930 Check and eliminate

performance bottlenecks in the
regressions disk I/O area to the
data files.
Recoverability 1642148 Make sure that

limitations regular successful log
backups are created.
backup failures.
Recoverability 1999930
limitations Check why the
runtime of the log
backups is increased
and eliminate
potential bottlenecks.
If global.ini ->
[backup] ->
max_log_backup_gro
up_size is set to a
value greater than 1,
multiple logs can be
bundled in one
backup. In this
context increased
times are okay with
SAP HANA 1.0,
because all individual
log backups will show
the overall backup
time for all logs. With
SAP HANA >= 2.0
the behavior changed
and you should no
longer see increased
backup times in case
of log backup groups.

backup failures.
Recoverability 1645183 Configure the

limitations automatic log backup
based on the SAP
recommendations.
Recoverability 1645183 Configure the
limitations log mode based on
the SAP
recommendations.
Increased I/O load, 2083715 Keep the backup
log full situations catalog at a
reasonable size.
Increased backup 2083715 Keep the backup
size and duration catalog at a
reasonable size so it
doesn't increase the
overall backup size
significantly.
Increased I/O load, 2083715 Regularly remove old

log full situations backups from the
catalog (but keep at
least backups of the
recent 28 days).
Log full situations 2083715 Take appropriate

actions to make sure
that log segments are
freed for reuse.
Log full situations 2083715 Consider reducing

the number of free
log segments using
ALTER SYSTEM
RECLAIM LOG.
Backup bottlenecks 2083715 Increase the log

and increased segment size of the
backup catalog sizes involved services in
order to keep the
amount of log
backups on a
reasonable level.
Performance 1999998 Analyze and

regressions and eliminate long
stuck situations running current
record or table lock
wait situations.

stuck situations running historic
record or table lock
wait situations.
regressions and eliminate current
stuck situations transactional and
internal lock wait
situations.

regressions and eliminate historic
stuck situations transactional and
internal lock wait
situations.

stuck situations running record or
table lock wait
situations.

stuck situations running record or
table lock wait
situations.
Garbage collection, 1999998 Check why so

locking and rollback many transactionsal
issues locks are used
concurrently and if it
is possible to reduce
it (e.g. by
increasing commit
frequency or reducing
package sizes).
Garbage collection, 1999998 Check why old

locking issues transactional locks
exist and make sure
that they are
committed in time.

regressions and waits for internal
stuck situations locks happened.

regressions and waits for internal
stuck situations locks happened.
Performance 1999998 Check why many
regressions and threads have to wait
stuck situations concurrently for the
same internal locks.
The numbers in
brackets indicate the
number of sampled
occurrences and the
average number of
waiters. For example,
"Acquire Index
Access (439 x 62)"
indicates that the
thread samples
contain 439 times of
"Acquire Index
Access" contention
where in average 62
threads have been
waiting.
Long runtimes, high 2000002 Analyze and SQL

CPU consumption statements with a
high total elapsed
time.
high total elapsed
time.
high total elapsed
time.
Long runtimes, high 2000002
CPU consumption Analyze and optimize
current long running
SQL statements and
the related business
logic.
Long runtimes, high 2000002

resource Analyze and optimize
consumption current long running
jobs and background
activities.
consumption
If very long running

jobs are reported that
are no longer active
in the system, there
may be an orphan
record in the
underlying monitoring
view
M_JOB_PROGRESS
. These orphan
records can be the
consequence of a
termination (e.g. due
to memory allocation
errors) and an
inadequate SAP
HANA exception
handling. In this case
you can ignore these
entries, and they will
disappear after the
next SAP HANA
startup.
Long runtimes, high 2000002 Analyze and optimize

CPU consumption long running SQL
statements.
Long runtimes, high 2000002 Check if database

CPU consumption accessed responsible
for the high amount
of scanned records
can be tuned or if an
index can be created
on the column to
reduce runtime and
resource
consumption.
Long runtimes, high 2000002 Check if database
CPU consumption accessed responsible
for the high amount
of scanned row table
records can be tuned
or if an index can be
created on selective
columns to reduce
runtime and resource
consumption.
SQL parse overhead 2124112 Check if more SQL

statements with bind
variables can be
used or if the SQL
plan cache can be
increased.
variables can be
used or if the SQL
plan cache can be
increased.
Be aware that this

value
is averaged over the
complete time frame
since the last service
startup.
variables can be
used or if the SQL
plan cache can be
increased.
SQL parse overhead 2124112 Make sure that at
least 15 MB of SQL
cache is available for
each ABAP SQL
connection, because
all statements in the
ABAP SQL statement
cache will be pinned
in the SQL cache of
SAP HANA up to
SAP HANA SPS 08.

variables can be
used or if the SQL
plan cache can be
increased.
SQL parse 2124112 Check which classes

overhead, increased of SQL statements
memory are responsible and
consumption eliminate the root
cause (e.g. by
introducing bind
variables or limiting
the mount of IN lists
with different
lengths).
SQL parse 2124112

overhead, increased
Consider
memory
reducing ABAP profile
consumption
parameter
rsdb/max_in_blocking
_factor, taking
advantage of the
dbsl_equi_join
approach or adjusting
the application in
order to reduce the
number of very long
IN lists.
SQL parse 2124112
Check why certain
overhead, increased SQL statement exist
memory multiple times in the
consumption SQL cache and
check for
optimizations.
SQL parse 2124112 Check if you can
overhead, increased reduce the amount of
memory instantiations of these
consumption, SQL statements in
increased translation the SQL cache, e.g.
table load by optimizing stacked
SQL statements.
SQL parse 2124112 Check why significant

overhead, increased amounts of SQL
memory plans exist with plan
consumption sharing type
SESSION LOCAL
(e.g. temporary table
accesses).
SQL parse 2124112 Check why a high

overhead, increased amount of SQL cache
memory entries is still
consumption referenced and as a
consequence pinned
in memory.

consumption A high number of
SQL contexts for
single connections
can result in a large
size of heap allocator
Pool/Statistics.
Known issues are:
Statements being kept open due to transactional LOBs and JDBC (SAP Note 2711824)
Performance 2000000
regressions Analyze the
temporarily
increased commit
times and put a
particular focus on
bottlenecks in the
disk I/O area (SAP
Note 1999930) and
system replication
area (SAP
Note 1999880).
Be aware that there

are some current
weaknesses in
measuring these
values, so that
increased values may
not only be linked to
local I/O issues, they
can also be caused
by system replication
overhead.
Performance 2000000 Analyze the

regressions increased commit
times and put a
particular focus on
bottlenecks in the
disk I/O area (SAP
Note 1999930) and
system replication
area (SAP
Note 1999880).
Performance 2000000 Check why the

regressions commit time is - at
least temporarily -
massively increased
and put a particular
focus on bottlenecks
in the disk I/O area
(SAP Note 1999930)
and system
replication area (SAP
Note 1999880).
Be aware that there
are some current
weaknesses in
measuring these
values, so that
can also be caused
overhead.
Performance 2000000
regressions Analyze the
increased commit
times and put a
particular focus on
bottlenecks in the
disk I/O area (SAP
Note 1999930) and
system replication
area (SAP
Note 1999880).
Be aware that there

are some current
weaknesses in
measuring these
values, so that
can also be caused
overhead.
Performance 2000000
regressions
A comparably high
number of commits
can be responsible
for performance and
space overhead (e.g.
due to transaction
management,
timestamp
synchronization and
persisting of redo
data to disk). Check
from application side
why many commits
are issued and check
if you can reduce the
amount of commits.
Performance 2000002
regressions Check for reasons
why database
requests are
executed in a
distributed way (i.e.
involving several
hosts / services)
although this is not
expected. Typical
reasons are:
Inadequate client distribution mode configuration (SAP Note 2200772)
Problems in network
between SAP HANA
client and server
You can activate a
client trace (e.g.
SQLDBC, JDBC) in
order to check if there
is a specific
connection issue to a
SAP HANA node.
The following trace
error e.g. indicates
that SAP HANA node
<host> can't be
accessed:
PHYSICAL
CONNECTION OPEN
2018-12-12
12:51:32.090164
FAILED -10709 /
Connection failed
(RTE:[89006] System
call 'connect' failed,
rc=113:No route to
host
(<host>:<port>))
As a fallback SAP HANA may then use a different scale-out node to access data on <host>, int
Performance 2000002
regressions
Check why a
particularly high
amount of internal
statement executions
are performed.
Among others
internal executions
are caused by
triggers. Try to
minimize the usage
of triggers in order to
reduce the overhead
introduced by internal
statement
executions.
Performance 2700051
regressions Make sure that the
delivered statement
hints are
implemented. This is
particularly useful in
ABAP environments.
Administrative 2400006
complexity
Avoid defining a
high number of
statement hints on a
permanent basis.
Instead the
underlying problem
should be changed in
different ways (e.g.
by changes to the
application design,
proper SAP HANA
configuration of a
SAP HANA bug fix).
Performance 2000002
regressions Analyze and optimize
expensive SQL
statements with a
particularly high
cumulated runtime.
Performance 2000002
Check and optimize
regressions the SAP ABAP table
buffer configuration
(transactions ST02,
ST10, AL12):
Sufficient buffer size
Limited number of
swaps and
invalidations
No unnecessary
buffering of large
tables
Performance 2399993
regressions
Disable FDA or update to a sufficiently new SAP HANA Revision level as suggested in SAP Not
Performance 2000002
regressions
See SAP Note 2000002 ("How can compatibility view accesses be tuned?") and check if you c
Memory and 2000002 Buffer the DDLOG

performance issues sequence.
Increased space 9385 Remove QCM

requirements, Issues tables that are no
during system copies longer needed.
Risk of unexpected 2222277 Make sure that ABAP
effects row store tables are
generally located on
the master node. This
can be achieved by a
proper table
placement configurati
on (SAP
Note 1908075) and
table redistribution
(SAP Note 2081591).
Supportability
restrictions From a support
perspective it is
important to map
connections (and
related activities like
database requests) to
client applications.
A client application
can register the
application for a
specific connection
via:
SET 'APPLICATION' =
‘<application_name
>'
The ABAP client for

example registers
itself as
'ABAP:<sid>'or
'dw.sap<sid>_<inst>'.
Check in
collaboration with the
client vendor if it is
possible to register
SAP HANA database
connections with a
useful application
name.
Increased 2445363 Remove BPC tables

nameserver topology that are no longer
size needed.
Check for data 1892354 Physical ABAP pool
consistency and and cluster tables like
conversion state CDCLS, EDI40,
KAPOL, KOCLU and
RFBLG are normally
converted into
transparent tables
when a system is
migrated to SAP
HANA. If the
conversion doesn't
happen properly, the
former pool and
cluster tables may
still be used and in
the worst case you
can even have data
inconsistency
because data is split
across the physical
and logical tables
over time. If physical
pool and cluster
tables are populated
with records, you
should check and
correct the setup,
taking also care for
data consistency.

Go to transaction
problems due to row
SMQ2 and check all
store version
clients for
consolidation
unnecessary entries
in STOP state and
process or remove
them.
consolidation
Implement SAP Note 2125972 in order to optimize the reprocessing logic of SMQ2.
Memory overhead 2160391
Column store indexes

on more than one
column result in a
significant memory
and maintenance
overhead, and in
some cases also a
significant
performance impact
is possible. The client
column typically
provides limited
benefit in terms of
selectivity. Therefore
you can redefine non-
unique indexes on
client and one other
columns typically in a
way that you remove
the client column
from the index.
ABAP terminations 2399990

Check why a
particular high
amount of SAP ABAP
short dumps have
happened. They
aren't necessarily
related to problems
on SAP HANA side,
but nevertheless they
should be analyzed
and reduced if
possible.
ABAP terminations
Check SAP ABAP

update records in
error states (e.g.
"Error" or "Error (no
retry)") in transaction
SM13 and clean up in
close interaction with
the related
application team. A
wrong handling of
terminated update
records can result in
inconsistencies, so a
cleanup needs to be
handled with care.
There are situations

where orphan error
records remain in
table VBERROR. In
this case transaction
SM13 doesn’t show
any real update error
and the scenario can
be ignored.
VBERROR will be
automatically purged
after a retention time
of 50 days.
Authentication 1977221 Make sure that the

issues secure store is
available and
consistent.
Startup issues 2097613 An inconsistent
secure store can
result in severe
problems including
the unability to start
SAP HANA. Make
sure that the secure
store is properly
configured to avoid
this kind of scenario.
Authentication 2159014 Make sure that

issues important users don't
expire.
Authentication 2159014 Make sure that for
issues central database
users with many
connections (e.g.
SAP schema user)
neither user nor
password expiration
is configured.
Authentication 2159014 Make sure that

issues important certificates
are renewed in time.
Authentication 1702224 Make sure that the

issues password of technical
SAP users don't
expire.
Analysis limitations, 1640741 Assign the CATALOG
performance READ role to all
overhead users required for
SAP HANA
monitoring and
analysis.
Increased memory 2388483 Implement the recommendations for the SAP HANA audit log table CS_AUDIT_LOG_ as desc
requirements
Performance 2159014 A high number of of activated audit policies for DML statements like SELECT, INSERT, UPDATE
regressions,
increased I/O
and commit load
License violation 1704499 Make sure that the

license usage doesn't
exceed 100 % by
adjusting the
licensing conditions
or reconfiguring SAP
HANA or the
application.
Risk of license 1644792 Extend the license

violation and system before it expires.
unavailability Consider a
permanent license.
Risk of license 1644792 Consider using a
violation and system permanent license
unavailability rather than a
temporary one.
Performance 2222200
degradations
Eliminate bottlenecks
impacting the
communication
between the
processes within one
SAP HANA node.
Be aware that lower

values are normal
and expected in
scenarios where
mainly very small
communication
packages are sent
(with sizes of byte to
a few KB). In this
case small values are
no indication for
network /
communication
issues.
Performance 2222200
degradations
Eliminate bottlenecks
impacting the
communication
between the
processes of different
SAP HANA nodes.
Be aware that lower

values are normal
and expected in
scenarios where
mainly very small
communication
packages are sent
(with sizes of byte to
a few KB). In this
case small values are
no indication for
network /
communication
issues.
Performance 2222200 Check from network
degradations perspective if you can
reduce the
retransmission rate of
TCP segments
related to the SAP
HANA nodes.

bad TCP segments
related to the SAP
HANA nodes.

collisions related to
the SAP HANA
nodes.

reduce the number
of send errors related
to the SAP HANA
nodes.

reduce the number
of receive
errors related to the
SAP HANA nodes.
Performance 2222200
degradations Check why a
particular high
amount of data is
transmitted between
services of the same
SAP HANA node and
try to reduce it.
Performance 2222200
degradations Check why a
particular high
amount of data is
transmitted between
different SAP HANA
scale-out nodes and
try to reduce it.
The internal SAP

HANA host name
resolution (parameter
section
internal_hostname_re
solution) is done with
a mapping from IP
address (parameter
name) to host name
(parameter value). If
the parameter name
is no IP address (e.g.
because you
swapped the order
and specify the host
name rather than the
IP address), it doesn't
work as expected.
Make sure that the
parameter names in
section
internal_hostname_re
solution are IP
addresses.
Performance 2222200
degradations
Check in which
context the network
requests are typically
send and optimize /
reduce it if possible.
For example,
metadata accesses
or joins of partitioned
tables can result in a
high amount of
network requests.
Inadequate network
parameters can result
in earlier contention.
Performance 2222200
degradations
Check in which
context the network
send and optimize /
For example,
metadata accesses
high amount of
network requests.
Inadequate network
Performance 2222200
degradations
Check in which
context the network
send and optimize /
For example,
metadata accesses
high amount of
network requests.
Inadequate network
Backup problems 2062080 Check if a high

number of small logs
is generated for the
XS engine. If yes,
increase the log
segment size of the
XS engine to at least
64 MB.
Performance 2000000 The measured ping

degradations times include the
communication
between nameserver
and indexserver and
KPI collection within
the indexserver.
Increased times can
be a symptom of an
underlying
performance issue.
Check for general
issues impacting the
performance (e.g.
resource
bottlenecks).
Performance 2000000 The measured ping
degradations times include the
communication
between nameserver
and indexserver and
KPI collection within
the indexserver.
Increased times can
be a symptom of an
underlying
performance
issue. Check for
general issues
impacting the
performance (e.g.
resource
bottlenecks).
Performance 2100296 Make sure that the

degradations nameserver lock file
is located on a
supported file system
as delays in
accessing this file
can heavily impact
the performance of
SAP HANA.
High availability 1999880 Analyze the related

limitations trace files in order to
understand the
reason for the
problems and make
sure that system
replication is again
established.
High availability 1999880

limitations Analyze the related
trace files in order to
understand the
reason for the
problems and make
sure that system
replication is again
established.
limitations Check why the
connection to the
secondary system
has been lost
(temporarily or
permanently) and
make sure that it
remains connected
permanently.

limitations Check if the system
replication actually
works and ships logs
to the secondary site
on a regular basis. If
not, the secondary
site may be
significantly outdated
and a proper system
replication needs to
be re-established.
High availability 1999880 Check for errors or

limitations, communication
performance issues that can be
degradations responsible for the
log shipping delays
and make sure that
log can be shipped in
time.

limitations, Check for errors or
performance communication
degradations issues that can be
responsible for the
log shipping delays
and make sure that
time. If required,
increase the
asynchronous log
shipping buffer:
global.ini ->
[system_replication]
->
logshipping_async_b
uffer_size
limitations, Check for errors or
peformance communication
degradations issues that can be
responsible for the
log shipping delays
and make sure that
time. If required,
increase the
asynchronous log
shipping buffer:
global.ini ->
->
logshipping_async_b
uffer_size
Risk of problems 1999880

during / after failover Make sure that in
system replication
environments all
relevant SAP HANA
parameters are
maintained
consistently on the
primary and
secondary system. If
parameters need to
deviate, you can
maintain them in the
exclusion list
parameters at:
global.ini ->
[inifile_checker]
Increased data disk 1999880
space requirements
Database snapshots
can increase the data
disk space
requirements and so
you should make
sure that system
replication related
snapshots are
not kept longer than
necessary. The
snapshot retention
time is controlled by
the following
parameter:
global.ini ->
->
datashipping_snapsh
ot_max_retention_ti
me

limitations
A particularly long
initial data shipping
time restricts the
takeover capabilities
because a takeover
can only take place
when initial data
shipping is finished
and the system
replication sites are in
sync. Check why
initial data shipping
takes so long and
eliminate bottlenecks,
e.g. on network or I/O
side.
Performance 1999880
regressions
In order to avoid
negative impact on
the performance on
primary system
replication side, the
average log buffer
shipping time
shouldn't exceed a
few milli seconds. If
you face higher
values, you should
analyze the network
between the primary
and secondary side.
Performance 1999880
regressions
In order to avoid
negative impact on
the performance on
primary system
average log buffer
shipping time
shouldn't exceed a
you face higher
values, you should
analyze the network
between the primary
and secondary side.
Performance 1999880
regressions
In order to avoid
negative impact on
the performance on
primary system
average log buffer
shipping time
shouldn't exceed a
you face higher
values, you should
analyze the network
between the primary
and secondary side.
Increased takeover 1999880
times Due to various
advantages it is
recommended to use
operation mode
logreplay (or
logreplay_readacces
s) instead of
delta_datashipping
when SAP HANA >=
1.00.122.17 is used
and there are no
good
individual reasons to
use
delta_datashipping.
HA limitations 2661878
Check why a significant backlog exists for the log replay on secondary site in the system repli
Risk of standstill 1999880
Activating log
retention
(enable_log_retention
= on) in combination
with the replication
mode delta data
shipping
(operation_mode =
delta_datashipping)
doesn't make sense
and can result in
standstill situations
due to retained log
files. Don't set the
enable_log_retention
parameter when delta
data shipping is used
as system replication
mode.
Unsupported 1999880
scenario
It is not supported to mix operation mode delta_datashipping with a logreplay operation mo

limitations If system replication
mode
delta_datashipping is
used, a long duration
since the last shipped
savepoint can impact
the takeover times.
You can check the
following:
If system replication
is actually configured
with mode logreplay,
no savepoints are
shipped and a huge
delay is harmless and
can be ignored.
Make sure that the

parameters global.ini
->
->
datashipping_min_ti
me_interval and
global.ini ->
->
datashipping_logsize
_threshold aren't
configured with very
large values on the
secondary node.
Otherwise it will take
a long time until a
savepoint shipping is
triggered.
Check the overall

system replication
sanity and the state
of the secondary site.
Risk of terminations 2155663 Upgrade to SPS 08

Rev. >= 85.04 or Rev.
>= 96 in order to
eliminate the risk of
terminations in case
of large object IDs for
sequences.
Risk of terminations Check for invalid
procedures and
recompile them:
ALTER PROCEDURE
"<procedure>"
RECOMPILE
If a recompilation isn't
possible consider
adjusting or dropping
them.
Risk of terminations 2401716
Avoid using synonym names that are identical to table names - particularly in SAP ABAP envi

regressions and In order to guarantee
terminations optimal performance
of sequences with
limited overhead it is
recommended to
activate caching for
the sequences, e.g.
with a size of 100:
ALTER SEQUENCE
"<sequence_name>
" CACHE 100
Be aware that in case

of a crash there will
be gaps in the
sequence numbers,
so you need to make
sure that this is okay
from application
perspective.
Sequences related to
ABAP table DDLOG
and to SLT triggers
can be cached
without restriction.
Risk of performance
regressions
Cross node triggers
are triggers where
the triggering table
and the target tables
are located on
different SAP HANA
nodes in scale-out
environments. This
can result in
unnecessary
communication
overhead and you
should check if
moving all involved
tables to the same
node is possible.
Reduced text 2160391

analysis quality Check for frequent
text indexing errors
and eliminate the root
cause. You can use
the following query to
determine indexing
errors for a specific
<column> of a
specific <table>:
SELECT
"<column>"

INDEXING_ERROR_C
ODE("<column>")
ERROR_CODE,

INDEXING_ERROR_M
ESSAGE("<column>"
) ERROR_MESSAGE
FROM
"<table>"
WHERE

INDEXING_ERROR_C
ODE("<column>") !
=0
See SAP Note 2396942 for a dedicated indexing issue (error 5438) in IBM on Power environm
Reduced text 2160391

analysis quality Check if the amount
of queued documents
remain high over
time, even at times of
rather low system
load. If yes, you have
to check for possible
bottlenecks and
issues in the text
indexing procedure.

Make sure that
overhead due to optimal table
inadequate table placement and
placement landscape
redistribution is
configured.
Risk of locks and 2044468
Avoid partitioning of
hang situations SID tables in order to
rule out risks related
to uniqueness
checks.
Make sure from BW
side that the SID
number range in a
single info object
doesn't exceed 2
billion.
Risk of locks and 2044468
performance
regressions
BW tables with H, I,
J, K, P, Q, T, X or Y
immediately after the
second slash (e.g.
/BIC/P...) shouldn't
be partitioned unless
really required,
because partitioning
typically causes more
trouble than having
benefits. If there is a
risk that the 2 billion
record limit is
reached, partitioning
should nevertheless
be considered.
Take appropriate
actions on BW side to
limit the PARTNO
partition numbers.
The maximum
permitted value from
BW side is 9999
and you should have
sufficient headroom
to be on the save
side.
Inefficient table 1702409

distribution Consider to use at
least three nodes in
BW scale-out
scenarios in order to
guarantee optimal
table distribution.
Memory and 2388483

Make sure that
administration temporary BW tables
overhead aren't kept for an
unnecessary long
time.
Memory overhead 2388483
BW aggregates are
usually not required
in SAP HANA
environments. Check
why still BW
aggregate tables
(/<bw_prefix>/E1%, /
<bw_prefix>/F1%)
exist and purge them
if possible.
Performance 2593719
regressions Remove old
temporary calculation
scenarios, e.g. via
report
RSDDTMPTAB_DEL
ETE.
Risk of malfunctions 2109355

Inverted hash
indexes aren't
supported for BW
tables and need to be
converted to inverted
value indexes.
Data inconsistencies 1977584 Analyze the reported

and terminations errors and repair
corruptions if
required.
Data inconsistencies 2116157
and terminations
Consider scheduling
a regular
CHECK_TABLE_CO
NSISTENCY run with
the statistics server.
Alternatively you can
also use other
scheduling tools like
transaction DB13 or
cron.
and terminations
Schedule a table
consistency check
based on
CHECK_TABLE_CO
NSISTENCY at least
once in a backup
cycle. Make sure that
the history of the
thread samples (SAP
Note 2114710) is kept
for at least 42 days,
otherwise information
about previous
consistency check
runs may not be
found, resulting in
false positives. Also
make sure that
thread details are
properly collected
(SAP Note 2524020)
to avoid false
positives.

Schedule a table
and terminations
consistency check
based on
CHECK_TABLE_CO
NSISTENCY at least
once in a backup
cycle.
and terminations Check the reported
errors and repair
existing corruptions.
Make sure that
CHECK_TABLE_CO
NSISTENCY can be
executed without
error.
Wrong results 2264778
Consider upgrading to a more recent Revision level or partitioning the potentially impacted t
Downtime and 2222249

Make sure
erroneous alerts that daemon and
topology are
configured
consistent.
Risk of various
issues, e.g. restore
or takeover problems The configured
number of standby
nodes must be
identical to the actual
number of standby
nodes. If there is a
deviation, it needs to
be corrected, e.g. by
adjusting the
topology
information, in order
to rule out
unpredictable issues.
Open a SAP incident
if you need
assistance from SAP
side.
Risk of corruptions 2498587

Open a SAP
incident on
component HAND-
DB in order to
analyze and repair
the inconsistency.
and resource See SAP
overhead Notes 1872652 and 1
926323 and create
optimizer statistics on
all smart data access
tables.
Check why remote
subscriptions failed
with error and
eliminate the root
cause.
Outdated data 2400022
Check why applying the SDI remote subscription changes is significantly behind and resolve e
Risk of various 2391341

issues, e.g. restore
or takeover problems
Configure the dpserver processes based on the instruction in the SAP HANA EIM Administrati
Risk of blocked 2073112

garbage collection Check why a high
number of SAP
HANA Studio
connections to the
database exist and
check if you can
reduce them. Among
others you can
consider the
following:
Avoid using outdated
SAP HANA Studio
versions.
Avoid adjusting
timeout settings.
Manually terminate
old and no longer
needed connections.
Risk of instabilities 2073112

Make sure that you
use a sufficiently new
SAP HANA Studio
Revision that should
at least match the
SPS level of SAP
HANA.
Risk of instabilities 2222218
The hdbcons tool isn't
officially supported by
SAP and so it should
be used with care
and only in situations
where it is really
required. Check for
what purpose
hdbcons was called
and avoid calling
hdbcons too
frequently (unless
instructed by SAP
support).
Increased complexity 2186744
Check for what

purpose parameters
are set on host level
and check if it is
possible to define
parameters globally
to simplify application
complexity. For
example, host
specific parameters
aren't automatically
taken over in case of
host auto-failover.
Outdated 2186744
configuration
settings used
If parameters are
modified that require
a SAP HANA restart
to take effect, you
may be in a situation
that the parameter
value displays a state
the is actually not
active. This can result
in misinterpretations
and unexpected
behavior of the SAP
HANA database.
Consider this
scenario and restart
SAP HANA when
possible to make
sure that the new
setting takes effect.
Various 2186744
Make sure that

section and
parameter names are
spelled correctly, that
the parameter value
matches to the
intended data type
and that the
parameter value is
within the accepted
range. If the
parameter is raised
although all details
are properly
considered, it may be
caused by a missing
entry in view
CONFIGURATION_P
ARAMETER_PROPE
RTIES. In this case
you can open a SAP
incident on
component HAN-DB
in order to request
the parameter to be
added into that view.
Risk of unforeseen 2425002

issues Check which
deprecated features
you still use and
consider to use a
different,
current approach for
the same purpose.
Risk of terminations, 2340450

performance Check if table
regressions replicas are disabled
unintentionally and
activate them.
Performance 2400007
overhead Check for the
reasons of automatic
table replication
deactivation and
resolve underlying
issues if required.
Overhead in 2600095 Drop sequences no

sequence longer required in
administration context of SLT.
consumption
With SAP HANA >=
2.0 the previously
created calculated
ESH columns starting
with '$esh:ca' are no
longer required and
can be dropped using
report
ESH_HDB_RESET_
CALC_ATTRIBUTES.

Sap Hana Mini Check

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sap Hana Mini Check

Загружено:

Авторское право:

Доступные форматы

Check ID Area Validity Description Analysis SQL statement (SAP Note 1969700)

M0012 GENERAL global Revision level SQL:

M0110 GENERAL global Everything started SQL:

M0115 GENERAL global Service startup time variation (s) SQL:

M0120 GENERAL global Services not started SQL:

M0207 OPERATIN Power Recommended bigmem kernel SQL:

M0208 OPERATIN global Supported operating system SQL:

M0209 OPERATIN global Recommended operating system SQL:

M0211 OPERATIN scale-out Hosts with varying CPU rates SQL:

M0220 OPERATIN global Current CPU utilization (%) SQL:

M0222 OPERATIN global Time since CPU utilization > 95 % SQL:

M0227 OPERATIN global External CPU utilization (%, last

M0229 OPERATIN global Discrepancy between NUMA nodes SQL:

M0231 OPERATIN global Time since memory utilization > 95 SQL:

M0232 OPERATIN global Hyperthreading active in critical SQL:

M0234 OPERATIN >= CPU steal share (%) SQL:

M0235 OPERATIN scale-out Hosts with varying physical memory SQL:

M0241 OPERATIN global Time since swap utilization > 1 GB SQL:

M0245 OPERATIN global Swap space size (GB) SQL:

M0263 OPERATIN global Asynchronous I/O queue size limit SQL:

M0265 OPERATIN global Network socket backlog limit SQL:

M0266 OPERATIN global Non-acknowledged requests limit SQL:

M0267 OPERATIN global Ephemeral port limit SQL:

M0280 OPERATIN scale-out Maximum time variation between SQL: "HANA_Hosts_Time"

M0310 DISK global I/O read throughput data min. SQL:

M0315 DISK global I/O write throughput data min. SQL:

M0350 DISK global Blocking savepoint phases > 10 s SQL: “HANA_IO_Savepoints”

M0356 DISK global Savepoint crit. phase write SQL: "HANA_IO_Savepoints"

M0357 DISK global Savepoint write throughput (MB/s) SQL: "HANA_IO_Savepoints"

M0360 DISK global Number of failed I/O reads

M0361 DISK global Number of failed I/O writes

M0363 DISK global Redo log generation (TB / day, last

M0365 DISK Rev. >= Wrong SAP HANA I/O parameter

M0367 DISK global Filesystems with unsupported types

M0370 DISK global Unused space in data files (%) SQL:

M0372 DISK global Unused space in classic disk LOBs SQL:

M0375 DISK global Data disk vs. memory ratio SQL:

M0380 DISK global Age of oldest backup snapshot SQL: "HANA_IO_Snapshots"

M0383 DISK global Max. size of shadow pages (GB, SQL:

M0411 MEMORY global Current allocation limit used by SQL:

M0415 MEMORY global Curr. max. service allocation limit SQL:

M0420 MEMORY global Heap areas currently larger than 50 SQL:

M0421 MEMORY global Heap areas larger than 100 GB SQL:

M0422 MEMORY global Heap areas larger than 200 GB SQL:

M0423 MEMORY global Heap areas with potential memory SQL:

M0430 MEMORY global Number of low memory column SQL:

M0435 MEMORY global Number of shrink column unloads SQL:

M0437 MEMORY global Size of unloaded columns (GB, last SQL:

M0438 MEMORY global Memory reclaim activity (s / day) SQL:

M0439 MEMORY global Memory reclaim maximum duration SQL:

M0445 MEMORY global Number of OOM events (last hour) SQL:

M0454 MEMORY global Size of non-unique concat attributes SQL:

M0455 MEMORY global Unused large non-unique concat SQL:

M0462 MEMORY global Caches with large size SQL:

M0470 MEMORY global Frequent allocators SQL:

M0480 MEMORY global Address space utilization (%) SQL:

M0510 TABLES global Tables with > 100 partitions SQL:

M0511 TABLES global Tables with many columns SQL: "HANA_Columns"

M0515 TABLES global Partitioned tables with inverted SQL: "HANA_Indexes"

M0516 TABLES global Existing inverted hash indexes SQL: "HANA_Indexes"

M0523 TABLES global Columns with many distinct text SQL:

M0526 TABLES global Tables / partitions with large SQL:

M0530 TABLES global Row store size (GB) SQL: