2019-08-27 1999993

1999993 - How-To: Interpreting SAP HANA Mini Check

Results
Version 409 Type SAP Knowledge Base Article
Language English Master Language English
Release Status Released to Customer Category How To
Component HAN-DB (SAP HANA Database) Released On 29.07.2019

Please find the original document at https://launchpad.support.sap.com/#/notes/1999993

Symptom

You want to perform a technical SAP HANA health check.

You are interested to understand the output of SQL: "HANA_Configuration_MiniChecks" (SAP Note 1969700
).

Environment

SAP HANA

Cause

You want to check for potentially critical technical issues in the SAP HANA database. Usually these issues
are raised and processed via SAP HANA alerts. This SAP Note describes a different approach via SQL:
"HANA_MiniChecks" provided in SAP Note 1969700 that is available for the following reasons:

• Ad-hoc execution possible

• Execution in different environments possible (SAP HANA Studio, DBACOCKPIT, other SQL interfaces
to SAP HANA)
• Flexible adjustments and delivery possible
• Tailored checks for SAP support services

Attention: Text-based "copy and paste" can result in unforeseen issues, so you should either download the
file directly to the database server or make sure that you use a file-based copy approach that doesn't modify
the file content.

Like the complete SQL statement collection of SAP Note 1969700 the mini checks command is mainly
intended for use by SAP support. Deviations from the results of the SAP HANA alerts are possible and
sometimes intended.

In case of multitenant databases (MDC, SAP Note 2101244) the mini checks should be executed individually
in the system DB and in all tenants, because the majority of the mini checks is database specific and has no
system-wide scope.

It is possible to implement SAP Solution Manager metrics based on mini checks using custom metrics. See
Custom Metrics for HANA Monitoring for details.

Here you find the SAP HANAChecker Python script including a documentation that can be used to run the
mini checks and send automatic e-mails in case of potentially critical issues.

For feedback and suggestions you can contact Christian Hansen after reading the disclaimer obtained by

© 2019 SAP SE or an SAP affiliate company. All rights reserved 1 of 109

2019-08-27 1999993
python hanachecker.py --disclaimer

Resolution

The command SQL: "HANA_Configuration_MiniChecks" (SAP Note 1969700) performs several mini checks
and returns C = 'X' if a potentially critical situation is found. You can then perform a more detailed analysis to
check if there is a real issue or if the 'X' can be ignored. This SAP Note provides details that can help you to
analyze and judge potentially critical situations.

In order to understand the mini checks and the possible analysis steps in detail, you can consider a SAP
HANA Technical Performance Optimization (TPO) service (SAP Note 2177604) including empowering. In this
onsite service the mini checks are performed for a customer system (which is typically already in production)
and a comprehensive analysis is performed together with SAP HANA experts of the customer in order to
illustrate typical problem resolution steps.

Be aware that multiple versions of SQL: "HANA_Configuration_MiniChecks" may exist. See naming
convention details in SAP Note 1969700 and make sure that you use the most appropriate command version
in order to use the most comprehensive list of checks. Be aware that versions tagged with "Internal"
exclusively contain internal checks and aren't available for customers.

You can restrict the output of the mini checks to the potentially critical results (C = 'X') by setting
ONLY_POTENTIALLY_CRITICAL_RESULTS = 'X' in the "Modification section" of the mini checks command.

These mini checks can only be evaluated on SAP HANA databases. Oracle mini checks can be found in SAP
Note 1615380.

Checks with a pure security focus are available in a dedicated SQL statement: SQL:
"HANA_Security_MiniChecks" (SAP Note 1969700).

Checks for critical trace file records are available in a dedicated SQL statement: SQL:
"HANA_TraceFiles_MiniChecks" (SAP Note 1969700).

ESS is an abbreviation for the embedded statistics server, SSS is the shortcut for the standalone statistics
server. SR represents system replication environments.

When checks are related to "last day", the last 86400 seconds before the analysis time are considered, not
the last calendar day. If no time restriction like "last day" or "last hour" is specified for a cumulating key figure,
the complete interval since the last startup is considered.

Analysis SQL
Check Potential SAP
Area Validity Description statement (SAP Details
ID impact Note
Note 1969700)
In general you
should make sure
Performance that you are on a
degradations rather recent
SQL: , revision level,
"HANA_Config terminations 2021789 optimally a
M0012 GENERAL global Revision level
uration_Patc , wrong 2617548 maintenance
hLevel" results, revision or data
unplanned center service
downtime point. SAP Note
2375691 describes
a critical crash and

© 2019 SAP SE or an SAP affiliate company. All rights reserved 2 of 109

2019-08-27 1999993
corruption bug that
impacts many SAP
HANA SPS 11 and
12 Revisions. It is
strongly
recommended to
use at least SAP
HANA 1.0 SPS 12
(SAP Note
2617548).
If SAP HANA
services are not
started, certain
functionalit
ies may not be
available.
SQL: Terminations
Everything Therefore check
M0110 GENERAL global “HANA_Service , unplanned 2177064
started the related trace
s_Overview” downtime
files and make
sure that all
services can be
started
successfully
.
A varying host
startup time can
indicate problems
on some hosts.
SQL: Make sure you
Host startup
scale- “HANA_Startup Unplanned understand the
M0111 GENERAL time variation 2177064
out _StartupTime downtime reason for the
(s)
s” varying start time
and eliminate
potentically
critical root
causes.
A varying service
startup time can
indicate problems
of some services.
SQL: Make sure you
Service startup
“HANA_Startup Unplanned understand the
M0115 GENERAL global time variation 2177064
_StartupTime downtime reason for the
(s)
s” varying start time
and eliminate
potentically
critical root
causes.
SQL: Erroneous Check if there is
Services not
M0120 GENERAL global "HANA_Servic alerts, 2222249 an inconsistenc
started
es_Overview" unplanned y between

© 2019 SAP SE or an SAP affiliate company. All rights reserved 3 of 109

2019-08-27 1999993
downtime nameserver
topology and
daemon
configuratio
n.
Make sure that on
SLES 11.x and
Power you
Recommended SQL: Risk of OOM
OPERATING implement the
M0207 Power bigmem kernel "HANA_Hosts_ and memory 2240716
SYSTEM bigmem flavor in
flavor not used Overview" corruptions
order to increase
the maximum
address space.
Make sure that you
use an operating
Supported SQL:
OPERATING Lack of system that is both
M0208 global operating "HANA_Hosts_
SYSTEM support supported by the
system Overview"
operating system
partner and SAP.
Make sure that a
reasonably new
operating system
Recommended
SQL: kernel is
OPERATING operating Performance 2235581
M0209 global "HANA_Hosts_ implemented in
SYSTEM system kernel degradations 2812427
Overview" order to avoid
version
running into
already fixed,
critical issues.
A low CPU
frequency is often
the consequence
of a CPU power-
save mode. Make
sure on OS side
SQL: that no CPU runs
OPERATING Minimum CPU Performance
M0210 global "HANA_Hosts_ 2235581 in power-save
SYSTEM rate (MHz) degradations
Overview" mode. Systems on
RHEL >= 7 and
SLES >= 12 are no
longer checked as
the intel_pstate
driver would result
in wrong alerts.
A varying CPU
frequency is often
the consequence
Hosts with SQL:
OPERATING scale- Performance of a CPU power-
M0211 varying CPU "HANA_Hosts_ 2235581
SYSTEM out degradations save mode. Make
rates Overview"
sure on OS side
that no CPU runs
in power-save

© 2019 SAP SE or an SAP affiliate company. All rights reserved 4 of 109

2019-08-27 1999993
mode and that the
nodes of a SAP
HANA scaleout
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.
For SAP HANA 2.0
certain CPU types
are strongly
recommended.
Make sure that you
Hosts with SQL:
OPERATING Performance use supported
M0215 global outdated CPU "HANA_Hosts_ 2399995
SYSTEM degradations CPU types or take
type Overview"
into account the
risk of
performance
regressions using
earlier CPU types.
Investigate in the
current top
contributors
to CPU time
SQL: (system vs. user
"HANA_Resour CPU, SAP HANA
OPERATING Current CPU Performance
M0220 global ces_CPUAndMe 2100040 vs. non SAP
SYSTEM utilization (%) degradations
mory_History HANA CPU, top
" HANA internal
CPU consumers)
and eliminate CPU
bottleneck
situations.
Investigate in the
recent top
contributors
to CPU time
SQL: (system vs. user
Peak CPU "HANA_Resour CPU, SAP HANA
OPERATING Performance
M0221 global utilization (%, ces_CPUAndMe 2100040 vs. non SAP
SYSTEM degradations
last day) mory_History HANA CPU, top
" HANA internal
CPU consumers)
and eliminate CPU
bottleneck
situations.
M0222 OPERATING global Time since SQL: Performance 2100040 Investigate in the

© 2019 SAP SE or an SAP affiliate company. All rights reserved 5 of 109

2019-08-27 1999993
SYSTEM CPU utilization "HANA_Resour degradations historic top
> 95 % (h) ces_CPUAndMe contributors
mory_History to CPU time
" (system vs. user
CPU, SAP HANA
vs. non SAP
HANA CPU, top
HANA internal
CPU consumers)
and eliminate CPU
bottleneck
situations.
Check which
processes are
responsible for the
high system CPU
consumption and
SQL: take appropriate
Peak system "HANA_Resour actions to reduce
OPERATING Performance
M0226 global CPU utilization ces_CPUAndMe 2100040 the system CPU
SYSTEM degradations
(%, last day) mory_History consumption (e.g.
" by optimizing the
operating system
configuratio
n or by avoiding
active waiting
within SAP HANA).
This check
compares the host
CPU consumption
with all the service
CPU
consumptions
measured via load
history (SAP Note
2222110). If the
SQL: host CPU
"HANA_LoadHi consumption is
External CPU story_Hosts" significantl
OPERATING Performance
M0227 global utilization (%, SQL: 2100040 y higher, it can be
SYSTEM degradations
last hour) "HANA_LoadHi caused by different
story_Servic factors: A SAP
es" HANA service that
isn't covered by
the load history
Another SAP
HANA tenant
Another
application or
operating system
process Check if
the external CPU

© 2019 SAP SE or an SAP affiliate company. All rights reserved 6 of 109

2019-08-27 1999993
overhead can be
explained and
accepted (e.g.
because it is
another active
tenant). If not, take
appropriate actions
to reduce the
external CPU
consumption.
Due to a Linux
issue it can
happen that the
SAP HANA load
history shows
SQL:
Erroneous reduced system CPU
OPERATING "HANA_LoadHi
M0228 global system CPU analysis 2222110 identical to user
SYSTEM story_Servic
calculation capabilities CPU. This problem
es"
is fixed with recent
Linux kernel
versions, see SAP
Note 2555398 for
more details.
The value for
cpu_sockets in
M_HOST_INFOR
MATION is
different from the
number of NUMA
nodes shown in
M_NUMA_NODES
(for a particular
SQL: host / port). This
Discrepancy
“HANA_Hosts_O Risk of can indicate
OPERATING between
M0229 global verview” SQL: NUMA 2470289 underlying NUMA
SYSTEM NUMA nodes
“HANA_NUMA_No issues configuratio
and sockets
des” n issues that
should be
analyzed and
resolved. You can
use hdbcons (SAP
Note 2222218)
with command
'jexec info' in order
to display NUMA
related details.
Investigate in the
SQL:
Performance current top
Current "HANA_Resour
OPERATING degradations contributors
M0230 global memory ces_CPUAndMe 1999997
SYSTEM , to memory
utilization (%) mory_History
terminations allocation and take
"
appropriate actions
© 2019 SAP SE or an SAP affiliate company. All rights reserved 7 of 109
2019-08-27 1999993
to reduce the
memory
consumption.
Investigate in the
historic top
SQL: contributors
Time since Performance
"HANA_Resour to memory
OPERATING memory degradations
M0231 global ces_CPUAndMe 1999997 allocation and take
SYSTEM utilization > 95 ,
mory_History appropriate actions
% (h) terminations
" to reduce the
memory
consumption.
In Intel contexts
with more than 8
CPU sockets
Hyperthreadi
SQL: hyperthreadi
OPERATING_SY ng active in Performance
M0232 global "HANA_Hosts_ 2711650 ng should usually
STEM critical degradations
Overview" not be activated
contexts
(unless explicitly
mentioned in SAP
Note 2711650).
A high CPU
utilization of
specific NUMA
nodes can indicate
problems with
CPU load
distribution
SQL:
NUMA nodes or NUMA
OPERATING_SY >= "HANA_CPU_Ut Performance
M0233 with high CPU 2470289 configuratio
STEM 2.00.020 ilizationPer degradations
utilization n. An analysis is of
Core"
particular
importance when
some NUMA
nodes are
permanently very
busy while others
are mainly idle.
An increased CPU
steal share
indicates that CPU
resources are
SQL: used by different
"HANA_Resour components in a
OPERATING_SY >= CPU steal Performance
M0234 ces_CPUAndMe 2100040 virtualized
STEM 2.00.020 share (%) degradations
mory_Current environment.
Details" You need to make
sure (e.g. by
proper workload
settings, SAP Note
2222250) that

© 2019 SAP SE or an SAP affiliate company. All rights reserved 8 of 109

2019-08-27 1999993
contention for CPU
resources is
limited in
virtualized
environments
so that different
systems don't
interfere to much
with each other.
Check why the
amount of physical
memory varies
between SAP
Hosts with Performance HANA hosts and
SQL:
OPERATING scale- varying degradations use hosts with an
M0235 "HANA_Hosts_ 1999997
SYSTEM out physical , identical amount of
Overview"
memory size terminations physical memory
unless there is a
very specific
reason for the
deviation.
Make sure that the
total memory
consumption of
SAP HANA and
other software
components
SQL: doesn't exceed the
Performance
"HANA_Resour available physical
OPERATING Current swap degradations
M0240 global ces_CPUAndMe 1999997 memory. Check on
SYSTEM utilization (GB) ,
mory_History operating system
terminations
" level why a
significant amount
of swap space is
used and take
appropriate actions
to reduce the swap
space utilization.
Make sure that the
total memory
consumption of
SAP HANA and
other software
SQL:
Performance components
Time since "HANA_Resour
OPERATING degradations doesn't exceed the
M0241 global swap utilization ces_CPUAndMe 1999997
SYSTEM , available physical
> 1 GB (h) mory_History
terminations memory. Check on
"
operating system
level why a
significant amount
of swap space was
used and take
© 2019 SAP SE or an SAP affiliate company. All rights reserved 9 of 109
2019-08-27 1999993
appropriate actions
to reduce the swap
space utilization.
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
Performance
SQL: level why a
OPERATING Swap out (GB, degradations
M0242 global "HANA_LoadHi 1999997 significant amount
SYSTEM last week) ,
story_Hosts" of swap space was
terminations
used and take
appropriate actions
to reduce the swap
space utilization.
See SAP Note
2779331 for
reasons why the
swap spae
utilization is higher
than expected.
It is usually better
if an OOM is
triggered when the
memory is scarce
on OS side,
because swapping
can reduce the
system
performance
Performance significantl
SQL:
OPERATING Swap space degradations y. Therefore it is
M0245 global "HANA_Hosts_ 1999997
SYSTEM size (GB) in case of recommended to
Overview"
swapping use a rather small
swap space. SAP
Note 2661792
describes a bug
that can result in a
wrong SAP HANA
swap space
calculation with
erroneous very
high values.
SQL: Stuck Take appropriate
OPERATING Max. used disk "HANA_Hosts_ situations, actions in order to
M0250 global 1870858
SYSTEM size (%) Disks" SQL: failing make sure that
"HANA_Hosts_ backups SAP HANA file
© 2019 SAP SE or an SAP affiliate company. All rights reserved 10 of 109
2019-08-27 1999993
FileSystems" system overflows
(SAP HANA >= will not happen
2.00.020)
Configure an open
SQL: files limit of at least
OPERATING Open files limit
M0260 global "HANA_Hosts_ Terminations 2600030 100,000 on
SYSTEM configured
Overview" operating system
side.
Configure an open
files limit of at least
100,000 on
SQL: operating system
Open files limit
OPERATING "HANA_Servic side. Check why a
M0261 global used (%, Terminations 2600030
SYSTEM es_Statistic significant amount
current)
s" of file handles is
opened
concurrently
by SAP HANA.
Configure an open
files limit of at least
100,000 on
SQL: operating system
Max. open files
OPERATING "HANA_LoadHi side. Check why a
M0262 global limit used (%, Terminations 2600030
SYSTEM story_Servic significant amount
history)
es" of file handles is
opened
concurrently
by SAP HANA.
Set the Linux
parameter fs.aio-
max-n
SQL: r to 184467440737
Asynchronous
OPERATING "HANA_Config 09551615. Be
M0263 global I/O queue size Terminations 1868829
SYSTEM uration_Infr aware that the
limit
astructure" underlying data is
only available with
SAP HANA >=
2.00.040.
Make sure that the
Linux parameter
vm.max_map_c
ount is set to
2147483647 (or an
SQL:
individually
OPERATING Virtual memory "HANA_Config
M0264 global OOM 1980196 calculated
SYSTEM map count limit uration_Infr
sufficiently
astructure"
large value). Be
aware that the
underlying data is
only available with
SAP HANA >=

© 2019 SAP SE or an SAP affiliate company. All rights reserved 11 of 109

2019-08-27 1999993
2.00.040.
Make sure that the
Linux parameter
net.core.som
SQL: axconn is set to at
Network Terminations
OPERATING "HANA_Config least 4096. Be
M0265 global socket backlog , 2382421
SYSTEM uration_Infr aware that the
limit performance
astructure" underlying data is
only available with
SAP HANA >=
2.00.040.
Make sure that the
Linux parameter
net.ipv4.tcp
_max_syn_bac
SQL:
Non-acknowle Terminations klog is set to at
OPERATING "HANA_Config
M0266 global dged requests , 2382421 least 8192. Be
SYSTEM uration_Infr
limit performance aware that the
astructure"
underlying data is
only available with
SAP HANA >=
2.00.040.
Configure Linux
parameter
net.ipv4.ip_
local_port_r
ange in a way that
at least 30000
SQL: ephemeral ports
Terminations
OPERATING Ephemeral "HANA_Config are available on
M0267 global , 2382421
SYSTEM port limit uration_Infr Linux level. Be
performance
astructure" aware that the
underlying data is
only available with
SAP HANA >=
2.00.040 and only
in the system
database.
Make sure that
Unknown SQL: properly named
OPERATING Missing
M0270 global hardware "HANA_Hosts_ 1828631 and filled hardware
SYSTEM information
components Overview" information files
are available.
Make sure that the
Various risks system clocks on
Maximum time
SQL: in areas like the hosts of a SAP
OPERATING scale- variation
M0280 "HANA_Hosts_ supportabili HANA scale-out
SYSTEM out between hosts
Time" ty and solution provide a
(s)
recovery nearly identical
time.
M0310 DISK global I/O read SQL: Performance 1999930 Check for
© 2019 SAP SE or an SAP affiliate company. All rights reserved 12 of 109
2019-08-27 1999993
throughput "HANA_IO_Key degradations bottlenecks and
data min. Figures_Tota possible
(MB/s, last l_History" SQL: optimization
day) "HANA_IO_Key s in the I/O stack
Figures_Deta related to read
il_History" accesses to the
data area
(operating system,
file system,
network to I/O sub
system, I/O sub
system).
Check for
bottlenecks and
possible
SQL:
optimization
I/O read "HANA_IO_Key
s in the I/O stack
throughput Figures_Tota
Performance related to the read
M0311 DISK global data avg. l_History" SQL: 1999930
degradations accesses to data
(MB/s, last "HANA_IO_Key
area (operating
day) Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O read s in the I/O stack
Figures_Tota
latency data Performance related to the read
M0312 DISK global l_History" SQL: 1999930
max. (ms, last degradations accesses to data
"HANA_IO_Key
day) area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O read s in the I/O stack
Figures_Tota
latency data Performance related to the read
M0313 DISK global l_History" SQL: 1999930
avg. (ms, last degradations accesses to data
"HANA_IO_Key
day) area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
I/O read reload SQL: This check
Increased
M0314 DISK global throughput "HANA_IO_Key 1999930 measures the
startup times
avg. (MB/s) Figures_Tota average data load

© 2019 SAP SE or an SAP affiliate company. All rights reserved 13 of 109

2019-08-27 1999993
l_History" SQL: throughput after
"HANA_IO_Key SAP HANA restart,
Figures_Deta so basically the
il_History" column store load.
If the throughput is
too low, the time to
load the column
store can be quite
high. Check for
bottlenecks and
possible
optimization
s in the 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).
Check for
bottlenecks and
possible
SQL: optimization
I/O write "HANA_IO_Key s in the I/O stack
throughput Figures_Tota related to write
Performance
M0315 DISK global data min. l_History" SQL: 1999930 accesses to the
degradations
(MB/s, last "HANA_IO_Key data area
day) Figures_Deta (operating system,
il_History" file system,
network to I/O sub
system, I/O sub
system).
Check for
bottlenecks and
possible
SQL: optimization
I/O write "HANA_IO_Key s in the I/O stack
throughput Figures_Tota related to write
Performance
M0316 DISK global data avg. l_History" SQL: 1999930 accesses to the
degradations
(MB/s, last "HANA_IO_Key data area
day) Figures_Deta (operating system,
il_History" file system,
network to I/O sub
system, I/O sub
system).
SQL: Check why reading
I/O read
"HANA_IO_Key from the data area
activity data Performance
M0317 DISK global Figures_Tota 1999930 requires significant
avg. (%, last degradations
l_History" SQL: absolute time (e.g.
day)
"HANA_IO_Key due to high
© 2019 SAP SE or an SAP affiliate company. All rights reserved 14 of 109
2019-08-27 1999993
Figures_Deta amount of read
il_History" activity or slow
I/O).
Check why writing
SQL:
to the the data
"HANA_IO_Key
I/O write area requires
Figures_Tota
activity data Performance significant absolute
M0318 DISK global l_History" SQL: 1999930
avg. (%, last degradations time (e.g. due to
"HANA_IO_Key
day) high amount of
Figures_Deta
write activity or
il_History"
slow I/O).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O read s in the I/O stack
Figures_Tota
throughput log Performance related to read
M0320 DISK global l_History" SQL: 1999930
min. (MB/s, degradations accesses to the
"HANA_IO_Key
last day) log area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O read s in the I/O stack
Figures_Tota
throughput log Performance related to read
M0321 DISK global l_History" SQL: 1999930
avg. (MB/s, degradations accesses to the
"HANA_IO_Key
last day) log area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check why writing
SQL:
to the log area
"HANA_IO_Key
I/O write requires significant
Figures_Tota
activity log Performance absolute time (e.g.
M0324 DISK global l_History" SQL: 1999930
avg. (%, last degradations due to high
"HANA_IO_Key
day) amount of write
Figures_Deta
activity or slow
il_History"
I/O).
Check for
SQL:
bottlenecks and
"HANA_IO_Key
I/O write possible
Figures_Tota
throughput log Performance optimization
M0325 DISK global l_History" SQL: 1999930
min. (MB/s, degradations s in the I/O stack
"HANA_IO_Key
last day) related to write
Figures_Deta
accesses to the
il_History"
log area (operating

© 2019 SAP SE or an SAP affiliate company. All rights reserved 15 of 109

2019-08-27 1999993
system, file
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O write s in the I/O stack
Figures_Tota
throughput log Performance related to write
M0326 DISK global l_History" SQL: 1999930
avg. (MB/s, degradations accesses to the
"HANA_IO_Key
last day) log area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
SQL:
optimization
"HANA_IO_Key
I/O write s in the I/O stack
Figures_Tota
latency log Performance related to write
M0327 DISK global l_History" SQL: 1999930
max. (ms, last degradations accesses to the
"HANA_IO_Key
day) log area (operating
Figures_Deta
system, file
il_History"
system, network to
I/O sub system,
I/O sub system).
Check for
bottlenecks and
possible
optimization
s in the I/O stack
related to write
accesses to the
SQL: log area (operating
4 KB write
"HANA_IO_Key Performance system, file
M0328 DISK global duration log 1999930
Figures_Deta degradations system, network to
avg. (ms)
il_History" I/O sub system,
I/O sub system).
I/O write
performance to the
log area is most
important in terms
of commit
performance.
SQL: Check for
I/O write
"HANA_IO_Key bottlenecks and
latency log Performance
M0329 DISK global Figures_Tota 1999930 possible
avg. (ms, last degradations
l_History" SQL: optimization
day)
"HANA_IO_Key s in the I/O stack

© 2019 SAP SE or an SAP affiliate company. All rights reserved 16 of 109

2019-08-27 1999993
Figures_Deta related to write
il_History" accesses to the
log area (operating
system, file
system, network to
I/O sub system,
I/O sub system).
Make sure that
SQL:
Max. trigger asynchronous
“HANA_IO_KeyF Performance
M0330 DISK global read ratio 1930979 queuing of I/O
igures_Total degradations
(data) requests is
”
activated.
Make sure that
SQL:
Max. trigger asynchronous
“HANA_IO_KeyF Performance
M0331 DISK global write ratio 1930979 queuing of I/O
igures_Total degradations
(data, log) requests is
”
activated.
Increase the size
SQL: and / or number of
Log switch wait Performance
M0340 DISK global “HANA_Log_Log 2215131 the log buffers in
count ratio (%) degradations
Buffers” order to reduce the
contention.
Increase the size
Log switch SQL: and / or number of
Performance
M0341 DISK global race count “HANA_Log_Log 2215131 the log buffers in
degradations
ratio (%) Buffers” order to reduce the
contention.
Check and
optimize SAP
HANA internal lock
Long
contention (SAP
waitForLock SQL:
Performance Note 1999998)
M0346 DISK global savepoint “HANA_IO_Save 2100009
degradations related to
phases (last points”
savepoints
day)
(typically on
ConsistentCh
angeLock).
Check for
bottlenecks and
possible
optimization
s in the I/O stack
Long critical
SQL: related to write
savepoint Performance
M0348 DISK global “HANA_IO_Save 2100009 accesses to the
phases (last degradations
points” data area
day)
(operating system,
file system,
network to I/O sub
system, I/O sub
system).

© 2019 SAP SE or an SAP affiliate company. All rights reserved 17 of 109

2019-08-27 1999993
Check for reasons
of long blocking
Blocking
SQL: savepoint phases
savepoint Performance
M0350 DISK global “HANA_IO_Save 2100009 like internal lock
phases > 10 s degradations
points” contention or I/O
(last day)
write bottlenecks
and optimize them.
Check for reasons
of long blocking
Blocking
SQL: savepoint phases
savepoint Performance
M0351 DISK global “HANA_IO_Save 2100009 like internal lock
phase avg. (s, degradations
points” contention or I/O
last day)
write bottlenecks
and optimize them.
Check for reasons
of long blocking
Blocking
SQL: savepoint phases
savepoint Performance
M0352 DISK global “HANA_IO_Save 2100009 like internal lock
phase max. (s, degradations
points” contention or I/O
last day)
write bottlenecks
and optimize them.
Check for
bottlenecks and
possible
optimization
s in the I/O stack
related to write
accesses to the
data area
SQL: Increased (operating system,
Time since last
M0355 DISK global "HANA_IO_Sav recovery 2100009 file system,
savepoint (s)
epoints" times network to I/O sub
system, I/O sub
system). Make
sure that global.ini
-> [persistence
] -> savepoint_in
terval_s is not set
to very high
values.
Check for
bottlenecks and
possible
optimization
Savepoint crit.
SQL: s in the I/O stack
phase write Performance
M0356 DISK global "HANA_IO_Sav 2100009 related to write
throughput degradations
epoints" accesses to the
(MB/s)
data area
(operating system,
file system,
network to I/O sub

© 2019 SAP SE or an SAP affiliate company. All rights reserved 18 of 109

2019-08-27 1999993
system, I/O sub
system).
Check for
bottlenecks and
possible
optimization
s in the I/O stack
Savepoint
SQL: related to write
write Performance
M0357 DISK global "HANA_IO_Sav 2100009 accesses to the
throughput degradations
epoints" data area
(MB/s)
(operating system,
file system,
network to I/O sub
system, I/O sub
system).
Check for
bottlenecks and
possible
optimization
s in the I/O stack
Savepoints
SQL: related to write
taking longer Performance
M0358 DISK global "HANA_IO_Sav 2100009 accesses to the
than 900 s degradations
epoints" data area
(last day)
(operating system,
file system,
network to I/O sub
system, I/O sub
system).
Check when and
on which disk
areas the errors
happened and
take appropriate
actions to avoid
failed reads in the
future. The check
SQL: is based on the
"HANA_IO_Key RESET view. In
Number of Figures_Tota order to avoid that
M0360 DISK global failed I/O l" SQL: Terminations 1999930 historic and
reads "HANA_IO_Key already analyzed
Figures_Tota failures are still
l_History" reported, you can
reset the view:
ALTER SYSTEM
RESET
MONITORING
VIEW
M_VOLUME_IO_
TOTAL_STATIS
TICS_RESET

© 2019 SAP SE or an SAP affiliate company. All rights reserved 19 of 109

2019-08-27 1999993
Check when and
on which disk
areas the errors
happened and
take appropriate
actions to avoid
failed writes in the
future. The check
SQL: is based on the
"HANA_IO_Key RESET view. In
Number of Figures_Tota order to avoid that
M0361 DISK global failed I/O l" SQL: Terminations 1999930 historic and
writes "HANA_IO_Key already analyzed
Figures_Tota failures are still
l_History" reported, you can
reset the view:
ALTER SYSTEM
RESET
MONITORING
VIEW
M_VOLUME_IO_
TOTAL_STATIS
TICS_RESET
Check for the main
contributors
of the high redo
log volume (e.g.
Redo log
SQL: large full loads,
generation (TB Performance
M0363 DISK global "HANA_Backup 1999930 modification
/ day, last degradations
_BackupRuns" operations) and
week)
reduce the amount
of database
changes if
possible.
Check for the main
contributors
of the high redo
log volume (e.g.
Redo log per SQL: large full loads,
Performance
M0364 DISK global day vs. data "HANA_Backup 1999930 modification
degradations
(%, last week) _BackupRuns" operations) and
reduce the amount
of database
changes if
possible.
Make sure that the
SAP HANA I/O
Wrong SAP SQL:
parameter settings
Rev. >= HANA I/O "HANA_IO_Key Performance
M0365 DISK 1930979 are in line with the
122.04 parameter Figures_Tota degradations
recommendati
settings l"
ons. Be aware that
SAP HANA may
© 2019 SAP SE or an SAP affiliate company. All rights reserved 20 of 109
2019-08-27 1999993
display wrong
values up to Rev.
122.03, so you
can't rely on the
output of SQL:
"HANA_IO_Key
Figures_Tota
l" on these
Revisions.
Make sure that you
only use filesystem
types that are
Risk of
Filesystems supported for your
SQL: performance
with SAP HANA
M0367 DISK global "HANA_Hosts_ degradations 1999930
unsupported environment.
Disk" and
types Check the SAP
terminations
hardware directory
for further support
details.
Reorganize the
Increased
Unused space SQL: disk area using
data disk
M0370 DISK global in data files "HANA_Disks_ 1870858 ALTER SYSTEM
space
(%) Overview" RECLAIM
requirements
DATAVOLUME.
Check if you can
reduce LOB
internal
fragmentatio
Unused space Increased
SQL: n, e.g. by
in classic disk data disk
M0372 DISK global "HANA_LOBs_L 2220627 conversion of
LOBs vs. data space
OBFiles" LOBs with
(%) requirements
particularly
small values and
high fragmentatio
n to packed LOBs.
Check if you can
perform
housekeeping
(SAP Note
Increased 2388483) or
Tables with SQL: startup times convert the LOBs
M0373 DISK global many small "HANA_LOBs_L and disk 2220627 of the mentioned
disk LOBs OBFiles" space tables to packed
requirements LOBs in order to
improve startup
times and reduce
disk space
consumption.
Tables with SQL: Increased Check if you can
M0374 DISK global many disk "HANA_LOBs_L startup times 2220627 perform
LOBs OBFiles" and disk housekeeping

© 2019 SAP SE or an SAP affiliate company. All rights reserved 21 of 109

2019-08-27 1999993
space (SAP Note
requirements 2388483) or
convert the LOBs
of the mentioned
tables to packed
LOBs in order to
improve startup
times and reduce
disk space
consumption.
This check is
similar to check
M0373 above, but
it doesn't focus on
small LOBs and
uses a higher LOB
count threshold.
The SAP HANA
disk requirements
can increase
significantl
Risk of file
y within short
SQL: system
times, so it is
Data disk vs. "HANA_Config overflows
M0375 DISK global useful to configure
memory ratio uration_Over and system
the disk size
view" down
significantl
situations
y larger than
usually required to
be prepared for
special situations.
Database
snapshots can
increase the data
Age of oldest Increased disk space
SQL:
backup data disk requirements
M0380 DISK global "HANA_IO_Sna 2100009
snapshot space and so you should
pshots"
(days) requirements delete them when
they are no longer
required for a
specific reason.
Database
snapshots can
increase the data
Age of oldest Increased disk space
SQL:
>= fallback data disk requirements
M0381 DISK "HANA_IO_Sna 2100009
2.00.030 snapshot space and so you should
pshots"
(days) requirements delete them when
they are no longer
required for a
specific reason.
M0383 DISK global Max. size of SQL: Increased 2100009 Check for reasons

© 2019 SAP SE or an SAP affiliate company. All rights reserved 22 of 109

2019-08-27 1999993
shadow pages "HANA_Disks_ data disk of increased
(GB, last day) Data_Pages" space amounts of
requirements shadow pages and
try to avoid
massive peaks by
reasonable
savepoint
configuratio
n, balancing of
change load and
minimizing merges
and compressions
of large tables.
Check why a
particularly
high amount of
data is written
during savepoints
(e.g. due to
unnecessary
modification
s from application
side, inadequate
table optimization
Savepoint vol.
SQL: Risk of configuratio
per day vs.
M0385 DISK global "HANA_IO_Sav performance 2100009 n, SAP HANA
data (%, last
epoints" issues parameter settings
week)
or known bugs).
Tempporary
increased values
can be acceptable
in context of a high
amount of
intended
modification
s or table
optimization
s.
Identify the root
cause of a
particularly
high number of
savepoint prepare
Max. savepoint flush retries (e.g.
SQL: Risk of
prepare flush due to due to
M0386 DISK global "HANA_IO_Sav performance 2100009
retries unnecessary
epoints" issues
(current) modification
s from application
side, inadequate
table optimization
configuratio
n, SAP HANA

© 2019 SAP SE or an SAP affiliate company. All rights reserved 23 of 109

2019-08-27 1999993
parameter settings
or known bugs).
Temporary
increased values
can be acceptable
in context of a high
amount of
intended
modification
s.
Identify the root
cause of a
particularly
high number of
savepoint prepare
flush retries (e.g.
Avg. savepoint due to due to
SQL: Risk of
prepare flush unnecessary
M0387 DISK global "HANA_IO_Sav performance 2100009
retries modification
epoints" issues
(current) s from application
side, inadequate
table optimization
configuratio
n, SAP HANA
parameter settings
or known bugs).
Check the current
memory utilization
and identify and
Unloads, out
SQL: resolve reasons
Allocation limit of memory,
M0410 MEMORY global "HANA_Memory 1999997 which are
used (%) performance
_Overview" responsible for the
degradations
used memory
coming close to
the allocation limit.
Check if the
amount of memory
Current Unloads, out
SQL: allocated by tables
allocation limit of memory,
M0411 MEMORY global "HANA_Memory 1999997 can be reduced
used by tables performance
_Overview" and if the system
(%) degradations
is properly sized in
terms of memory.
Check the historic
memory utilization
and identify and
Time since SQL: Unloads, out
resolve reasons
allocation limit "HANA_Resour of memory,
M0413 MEMORY global 1999997 which are
used > 80 % ce_CPUAndMem performance
responsible for the
(h) ory_History" degradations
used memory
coming close to
the allocation limit.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 24 of 109

2019-08-27 1999993
Check the current
memory utilization
of the critical
services and
identify and
Curr. max. Unloads, out resolve reasons
SQL:
service of memory, which are
M0415 MEMORY global "HANA_Servic 1999997
allocation limit performance responsible for the
es_Memory"
used (%) degradations used memory
coming close to
the allocation limit
or increase the
service specific
allocation limit.
Check the historic
memory utilization
of the critical
services and
identify and
Time since Unloads, out resolve reasons
SQL:
service alloc. of memory, which are
M0417 MEMORY global "HANA_Servic 1999997
limit used > 80 performance responsible for the
es_Memory"
% (h) degradations used memory
coming close to
the allocation limit
or increase the
service specific
allocation limit.
Check if you can
SQL: Unloads, out
Heap areas reduce the
"HANA_Memory of memory,
M0420 MEMORY global currently larger 1999997 memory allocation
_TopConsumer performance
than 50 GB of the largest heap
s" degradations
areas.
SQL: Check if you can
Unloads, out
Heap areas "HANA_Memory reduce the
of memory,
M0421 MEMORY global larger than 100 _TopConsumer 1999997 memory allocation
performance
GB (last day) s_TimeSlices of the largest heap
degradations
" areas.
Check why the
heap allocators
SQL: have grown to
Unloads, out
Heap areas "HANA_Memory significant sizes in
of memory,
M0422 MEMORY global larger than 200 _TopConsumer 1999997 the past and if you
performance
GB (history) s_TimeSlices can reduce the
degradations
" memory allocation
of the largest heap
areas.
SQL: Unloads, out Check if there are
Heap areas
"HANA_Memory of memory, known memory
M0423 MEMORY global with potential 1999997
_TopConsumer performance leak issues.
memory leak
s_TimeSlices degradations Consider the

© 2019 SAP SE or an SAP affiliate company. All rights reserved 25 of 109

2019-08-27 1999993
" creation of an
allocator block list
or an allocation
stack trace in order
to understand the
leaking allocations
in a better way
(SAP Note
2222218). In case
of an unknown
issue open a SAP
incident on
component HAN-
DB.
Monitor the growth
and restart SAP
HANA if required.
Upgrade to
revision 1.00.83 or
SQL: Unloads, out higher in order to
Pool/RowEngi
"HANA_RowSto of memory, 1999997 eliminate a related
M0425 MEMORY global ne/CpbTree
re_TotalInde performance 2169283 bug. An increased
leak size (GB)
xSize" degradations leak size can also
be the
consequence of a
blocked garbage
collection (SAP
Note 2169283).
A bug with SAP
HANA Rev. 111 to
112.05 and 120 to
122.01 can result
in row store
memory growth
because space
freed by delete
Unloads, out operations isn't
Row store SQL:
of memory, 2362759 considered for re-
M0426 MEMORY global table leak size "HANA_Memory
performance 2169283 use. See SAP
(GB) _Overview"
degradations Note 2362759 for
more information.
An increased leak
size can also be
the consequence
of a blocked
garbage collection
(SAP Note
2169283).
Number of low SQL: Check why
memory "HANA_Tables Performance unloads were
M0430 MEMORY global 2127458
column _ColumnStore degradations triggered (e.g. high
unloads (last _UnloadsAndL memory
© 2019 SAP SE or an SAP affiliate company. All rights reserved 26 of 109
2019-08-27 1999993
day) oads" consumption or
inadequate
configuratio
n of unload_lower
_bound)
Check why
unloads were
SQL: triggered (e.g. high
Time since last
"HANA_Tables memory
low memory Performance
M0431 MEMORY global _ColumnStore 2127458 consumption or
column unload degradations
_UnloadsAndL inadequate
(days)
oads" configuratio
n of unload_lower
_bound)
Make sure that
"resman shrink" /
unload_upper
_bound is
SQL:
Number of configured with a
"HANA_Tables
shrink column Performance reasonably high
M0435 MEMORY global _ColumnStore 2127458
unloads (last degradations limit (SAP Note
_UnloadsAndL
day) 2301382) or
oads"
consider to disable
a shrink
configuratio
n completely.
Check why
unloads were
SQL: triggered (e.g. high
Size of
"HANA_Tables memory
unloaded Performance
M0437 MEMORY global _ColumnStore 2127458 consumption or
columns (GB, degradations
_UnloadsAndL inadequate
last day)
oads" configuratio
n of unload_lower
_bound)
Check why
significant time is
spent to perform
memory
Memory SQL: defragmentat
Performance
M0438 MEMORY global reclaim activity "HANA_Memory 1999997 ion and try to
degradations
(s / day) _Reclaims" reduce it (e.g. by
optimizing the
memory utilization
or configuratio
n).
Check why
Memory
SQL: significant time is
reclaim Performance
M0439 MEMORY global "HANA_Memory 1999997 spent to perform
maximum degradations
_Reclaims" memory
duration (s)
defragmentat

© 2019 SAP SE or an SAP affiliate company. All rights reserved 27 of 109

2019-08-27 1999993
ion and try to
reduce it (e.g. by
optimizing the
memory utilization
or configuratio
n). 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_REC
LAIM_STATIST
ICS_RESET
Increase the
Shared
SQL: nameserver
memory
"HANA_Memory topology size or
M0440 MEMORY global utilization of Terminations 1977101
_SharedMemor reduce the number
nameserver
y" of (temporary)
(%)
tables.
Check memory
limitations (GAL,
SQL: PAL, statement
Number of
"HANA_Memory memory limit) and /
M0445 MEMORY global OOM events Terminations 1999997
_OutOfMemory or optimize the
(last hour)
Events" memory footpring
of expensive
queries.
Make sure that
SQL: large memory
Tables with "HANA_LOBs_H Increased LOBs are
Rev. >=
M0450 MEMORY memory LOBs ybridLOBActi memory 1994962 converted into
1.00.70
> 2 GB vation_Comma consumption hybrid LOBs in
ndGenerator" order to reduce the
memory footprint.
Check if the
largest non-unique
SQL:
Size of non- Increased concat attributes
Rev. >= "HANA_Tables
M0453 MEMORY unique concat memory 1986747 are really required
1.00.70 _ColumnStore
attributes (GB) consumption or if they can be
_Columns"
eliminated (e.g. by
switching to single

© 2019 SAP SE or an SAP affiliate company. All rights reserved 28 of 109

2019-08-27 1999993
column indexes or
by dropping no
longer required
relics).
Check if the
largest non-unique
concat attributes
are really required
SQL:
Size of non- Increased or if they can be
"HANA_Tables
M0454 MEMORY global unique concat memory 1986747 eliminated (e.g. by
_ColumnStore
attributes (%) consumption switching to single
_Columns"
column indexes or
by dropping no
longer required
relics).
Check for what
purpose the
reported concat
attributes exist and
consider dropping
them in case they
exist for no
SQL:
Unused large apparent reason.
"HANA_Tables Increased
non-unique Be aware that a
M0455 MEMORY global _ColumnStore memory 1986747
concat SAP HANA restart
_Columns_Sta consumption
attributes resets this counter
tistics"
to 0 and so it will
take some time
until all important
concat attribute
utilizations
are properly
tracked.
Check if the
mentioned indexes
are still required
from application
perspective and
consider to drop
SQL:
Unused large them if possible.
"HANA_Indexe Increased
Rev. >= non-unique Be aware that a
M0456 MEMORY s_RowStore_I memory 2160391
2.00.040 row store SAP HANA restart
ndexSearches consumption
indexes resets this counter
"
to 0 and so it will
take some time
until all important
index utilizations
are properly
tracked.
Calculation SQL: Performance Increase the size
M0460 MEMORY global
engine cache "HANA_Calcul degradations of the calculation

© 2019 SAP SE or an SAP affiliate company. All rights reserved 29 of 109

2019-08-27 1999993
utilization (%) ationEngine_ engine cache size,
CalculationS so that it can
cenarios" concurrently
keep all required
calculation
scenarios:
indexserver.
ini -> [calcengine]
-> max_cache_si
ze_kb = <size_kb>
Check if the
increased cache
sizes are expected
and reasonable. If
not, take
SQL:
Increased appropriate actions
Caches with "HANA_Memory
M0462 MEMORY global memory 2502256 (adjustments
large size _Caches_Over
consumption on application
view"
side, implementati
on of fixes, purging
of caches) to
reduce the size to
normal levels.
Check why specific
Increased
SQL: allocators exist
nameserver
Frequent "HANA_Memory very frequently and
M0470 MEMORY global ping times, 1999997
allocators _TopConsumer take appropriate
memory
s" actions to reduce
bottlenecks
them.
If SAP HANA
erroneously
records higher
memory
allocations in
M_CONTEXT_ME
MORY than
actually allocated,
it is possible that
database requests
SQL:
Booked vs. are terminated with
"HANA_Memory OOM
M0472 MEMORY global allocated 1999997 unjustified
_ContextMemo terminations
memory (%) composite limit
ry"
OOM dumps. See
SAP Note
1999997 ("Is the
SAP HANA
memory
information always
correct?" ->
M_CONTEXT_ME
MORY) for known
scenarios and
© 2019 SAP SE or an SAP affiliate company. All rights reserved 30 of 109
2019-08-27 1999993
solutions.
Optimize the
available address
space and its
utilization, e.g. by
avoiding manual
SQL: memory garbage
Address space "HANA_Memory OOM collection
M0480 MEMORY global 1999997
utilization (%) _TopConsumer situations activities, reducing
s" the SAP HANA
memory footprint
or using the
bigmem flavor on
IBM Power
systems.
SQL: Performance
Check if the high
"HANA_Tables degradations
Tables with > amount of
M0510 TABLES global _ColumnStore , high 2044468
100 partitions partitions is really
_Partitioned resource
required.
Tables" consumption
Avoid tables with a
high amount of
columns because
of disadvantage
s like: Increased
runtime of
"SELECT *" in
SQL: Performance
Tables with 1999997 column store
M0511 TABLES global "HANA_Column and memory
many columns 2000002 tables Increased
s" overhead
size of heap
allocator
Pool/malloc/
libhdbcsmd.s
o due to a high
amount of column
metadata
SQL: Check if it is
Hash
"HANA_Tables possible to use
partitioning Performance
M0512 TABLES global _ColumnStore 2044468 hash partitioning
on multiple degradations
_Partitioned based on a single,
columns
Tables" selective column.
Inverted hash
indexes can result
in corruptions
Partitioned when a table is
SQL:
tables with Risk of repartitione
M0515 TABLES global "HANA_Indexe 2436619
inverted hash corruptions d so you should
s"
indexes avoid to define
inverted hash
indexes on
partitioned tables.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 31 of 109

2019-08-27 1999993
Due to a SAP
HANA bug
inverted hash
indexes can result
in corruptions with
SAP HANA
Existing SQL:
Risk of 2.00.010 -
M0516 TABLES global inverted hash "HANA_Indexe 2109355
corruptions 2.00.024.08 and
indexes s"
2.00.030 -
2.00.036 and so
this index type
should be avoided
with these
Revision levels.
The overflow
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
SQL:
Tables with Risk of records in these
"HANA_Column
M0519 TABLES global large overflow performance 2044468 partitions should
Store_Partit
partition overhead be small. Check
ions"
for what reason a
siginficant amount
of records is stored
in the overflow
partition and
consider a
repartitioni
ng 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
SQL:
Tables / (partition)
"HANA_Tables
M0520 TABLES global partitions > 1.5 Terminations 1921694 permanently below
_ColumnStore
billion rows the two billion limit.
_Records"
BW SID tables
(typically following
the naming
convention
/B%/S% are

© 2019 SAP SE or an SAP affiliate company. All rights reserved 32 of 109

2019-08-27 1999993
excluded from this
check, because
they can never
grow beyond two
billion records and
partitioning
can be critical. See
Check ID 2022
instead.
Activate or extend
partitioning
SQL: in order to keep
Table histories
"HANA_Tables the amount of
M0521 TABLES global > 1.5 billion Terminations 1921694
_ColumnStore records per table
rows
_Records" history (partition)
permanently below
the two billion limit.
Force an optimize
compression run
Tables / SQL:
on the impacted
partitions > 1.5 "HANA_Tables
M0522 TABLES global Terminations 2112604 tables in order to
billion UDIV _ColumnStore
minimize the
rows _Records"
amount of UDIV
rows.
TEXT columns are
tokenized and so
the distinct tokens
can be significantl
y 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
SQL: distinct tokens is
Columns with
"HANA_Tables limited. Only use
M0523 TABLES global many distinct Terminations 2154870
_ColumnStore the TEXT data
text tokens
_Columns" 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.
M0525 TABLES global Tables / SQL: High 2044468 Large table

© 2019 SAP SE or an SAP affiliate company. All rights reserved 33 of 109

2019-08-27 1999993
partitions with "HANA_Tables resource (partitions)
large memory _TableSize" consumption can be responsible
size for a high resource
consumption in
terms of CPU,
memory and I/O, in
particular during
table optimization
s like merges or
compressions
. Therefore you
should check if you
can implement
partitioning
in a way that the
partition are kept
at reasonable
sizes.
Large table
(partitions)
can be responsible
for a high resource
consumption in
terms of CPU,
memory and I/O, in
particular during
Tables /
SQL: High table optimization
partitions with
M0526 TABLES global "HANA_Tables resource 2044468 s like merges or
large memory
_TableSize" consumption compressions
share
. Therefore you
should check if you
can implement
partitioning
in a way that the
partition are kept
at reasonable
sizes.
Check for largest
tables in row store
SQL: Increased whether data can
Row store size 2050579
M0530 TABLES global "HANA_RowSto startup time, be cleaned or
(GB) 1963779
re_Overview" terminations tables can be
moved to column
store.
Reorganize the
SQL: mentioned tables
Row store "HANA_Tables during a time of
Risk of
tables with _RowStore_Ta low system load in
M0533 TABLES global performance 2000002
more than 1 blesWithMult order to avoid
regressions
container ipleContaine overhead and
rs" performance
regressions:
© 2019 SAP SE or an SAP affiliate company. All rights reserved 34 of 109
2019-08-27 1999993
ALTER TABLE
"<table_name
>" RECLAIM
DATA SPACE
Reorganize the
Row store SQL: Increased row store in order
M0535 TABLES global fragmentatio "HANA_RowSto memory 1813245 to minimize
n (%) re_Overview" consumption fragmentatio
n.
Check if the long
running merges
are normal or if
SQL: they can be
Delta merges Increased
"HANA_Tables avoided (e.g. by
M0538 TABLES global > 900 s (last resource 2057046
_ColumnStore using default
day) consumption
_Merges" merge parameter
settings or by
reducing the data
volume)
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
SQL: this case it can be
Critical merge Increased
"HANA_Tables useful to adjust the
M0539 TABLES global share (%, last resource 2057046
_ColumnStore critical merge
week) consumption
_Merges" decision function
so that critical
merges are no
longer performed
unnecessaril
y. 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.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 35 of 109

2019-08-27 1999993
Check if it is
possible to reduce
Failing delta SQL: Increased
the amount of
merges (info "HANA_Tables resource
M0540 TABLES global 2057046 terminations
messages, last _ColumnStore consumption,
of merges with
day) _Merges" terminations
informationa
l messages.
Check the
individual error
Failing delta SQL: Increased messages and
merges (error "HANA_Tables memory take appropriate
M0541 TABLES global 2057046
messages, last _ColumnStore consumption, actions to prevent
day) _Merges" terminations critical
terminations
.
Check if delta
storages
permanently
SQL: remain on a high
Auto merge
"HANA_Tables Increased level. If yes, check
tables with
M0542 TABLES global _ColumnStore memory 1977314 why no merge
delta storage >
_DeltaStorag consumption happens and take
5 GB
e" appropriate actions
to make sure that
merges are
performed.
Check if delta
storages
permanently
SQL: remain on a high
Auto merge
"HANA_Tables Increased level. If yes, check
tables with
M0543 TABLES global _ColumnStore memory 1909742 why no merge
many delta
_DeltaStorag consumption happens and take
records
e" appropriate actions
to make sure that
merges are
performed.
Check if delta
storages
permanently
SQL: remain on a high
Non-auto
"HANA_Tables Increased level. If yes, check
merge tables
M0544 TABLES global _ColumnStore memory 1977314 why no merge
with delta
_DeltaStorag consumption happens and take
storage > 5 GB
e" appropriate actions
to make sure that
merges are
performed.
Non-auto SQL: Increased Check if delta
M0545 TABLES global merge tables "HANA_Tables memory 1909742 storages
with many _ColumnStore consumption permanently

© 2019 SAP SE or an SAP affiliate company. All rights reserved 36 of 109

2019-08-27 1999993
delta records _DeltaStorag remain on a high
e" level. If yes, check
why no merge
happens and take
appropriate actions
to make sure that
merges are
performed.
Consider adjusting
the auto merge
decision function
so that smaller
SQL: tables are merged
Sum of delta "HANA_Tables Increased more frequently.
M0546 TABLES global size of small _ColumnStore memory 2057046 See "Is the default
tables (GB) _DeltaStorag consumption auto merge
e" decision function
already optimal?"
in SAP Note
2057046 for more
details.
Check if auto
merge is disabled
on purpose and
reactivate it if
possible. A typical
SQL:
reason for a
Non BW tables “HANA_Tables_ Increased
disabled auto
M0547 TABLES global with disabled ColumnStore_ memory 1977314
merge is described
auto merge AutoMergeDis consumption
in SAP Note
abled”
2196615: A move
of a table from row
store to column
store using ABAP
tools.
SQL: Check if persistent
Tables with
“HANA_Tables_ Increased merge is disabled
disabled
M0548 TABLES global ColumnStore_ memory 2057046 on purpose and
persistent
PersistentMe consumption reactivate it if
merge
rgeDisabled” possible.
Check if the auto
compression is
disabled on
SQL:
purpose and
Non BW tables "HANA_Tables
Increased reactivate it if
with disabled _ColumnStore
M0549 TABLES global memory 2112604 possible. A typical
auto _AutoCompres
consumption reason for a
compression sionDisabled
disabled auto
"
optimize
compression
attribute is

© 2019 SAP SE or an SAP affiliate company. All rights reserved 37 of 109

2019-08-27 1999993
described in SAP
Note 2196615: A
move of a table
from row store to
column store using
ABAP tools. Also
an EXPORT /
IMPORT can result
in lost auto
compression.
Make sure that
Row store
SQL: ST_POINT
tables with Crashes,
M0550 TABLES global "HANA_Column 2038897 columns don't exist
ST_POINT terminations
s" for row store
columns
tables.
For timezone
operations without
conversion
overhead it is
important that the
timezone table
TTZZ is properly in
place and that the
operating system
environment
SQL:
Proper setup variable TZ isn't
"HANA_Config Performance
M0551 TABLES global of timezone 2100040 set to a wrong
uration_Time regressions
table TTZZ value.. See SAP
zones"
Note 2100040 ->
"How can CPU
intensive
operations in SAP
HANA be identified
and optimized?" ->
"__tz_conver
t" for the required
configuratio
ns.
For timezone
operations without
conversion
overhead it is
important that the
SQL: timezone table
Number of
"HANA_Config Performance TTZZ is properly in
M0552 TABLES global current 2100040
uration_Time regressions place and that the
timezone alerts
zones" operating system
environment
variable TZ isn't
set to a wrong
value.. See SAP
Note 2100040 ->
© 2019 SAP SE or an SAP affiliate company. All rights reserved 38 of 109
2019-08-27 1999993
"How can CPU
intensive
operations in SAP
HANA be identified
and optimized?" ->
"__tz_conver
t" for the required
configuratio
ns.
SQL:
Tables /
“HANA_Tables_ Make sure that
Rev. <= partitions Risk of
M0555 TABLES ColumnStore_ 2066313 tables are moved
1.00.82 moved only corruptions
TablesMovedL physically.
logically
ogically”
SQL:
"HANA_Tables Make sure that an
Tables > 10 _ColumnStore Increased optimization
2105761
M0560 TABLES global Mio. rows not _TablesWitho memory of compression
2112604
compressed utCompressio consumption happens for large
nOptimizatio tables.
n"
Make sure that
large columns are
compressed
efficiently.
Be aware that
there is a chance
of false positives,
SQL: i.e. columns that
"HANA_Tables are reported
Columns > 10 _ColumnStore Increased although a new
M0561 TABLES global Mio. rows not _ColumnsWith memory 2112604 compression will
compressed outCompressi consumption not be able to
onOptimizati compress them
on" efficiently.
In this case you
can ignore the
related tables in
the future and
don't start more
manual
compression runs.
For some reasons
single column
SQL:
index structures
Columns with "HANA_Indexe
may be missing.
missing s_ColumnStor Performance
M0562 TABLES global 2160391 See SAP Note
inverted e_MissingSin regressions
2160391 -> "What
indexes gleColumnInd
are BLOCK and
exes"
FULL indexes?" ->
Index type =

© 2019 SAP SE or an SAP affiliate company. All rights reserved 39 of 109

2019-08-27 1999993
'NONE' -> Column
indexed = 'X' for
more information
and solutions.
Indexes can't be
used on columns
being compressed
with SPARSE
(Rev. <= 122.02)
SQL:
or PREFIXED
Indexes on "HANA_Indexe
type. Execute an
large SPARSE s_ColumnStor Performance
M0563 TABLES global 2112604 optimize
/ PREFIXED e_MissingSin regressions
compression run in
columns gleColumnInd
order to make sure
exes"
that indexed
columns are not
compressed with
SPARSE or
PREFIXED.
Force a
Tables > 10 SQL: compression
Increased
Mio. rows and "HANA_Tables optimization
M0565 TABLES global memory 2112604
> 200 % UDIV _ColumnStore after large
consumption
rows _Records" deletions of data if
required.
Force a
compression
optimization
SQL:
Tables with in order to clean
"HANA_Tables Increased
fragmented up fragmentatio
M0566 TABLES global _ColumnStore memory 2112604
$trex_udiv$ n in the internal
_Compression consumption
column column store
"
version
administrati
on.
Force a
compression
Tables with SQL: optimization
Increased
Rev. >= MVCC "HANA_Garbag 2112604 in order to clean
M0567 TABLES memory
1.00.90 timestamps > eCollection_ 2387064 up fragmentatio
consumption
5 GB ColumnStore" n in the column
store MVCC
timestamps.
Keep the amount
of temporary SAP
Risk of
SQL: HANA tables at a
Number of administrati
"HANA_Tables limited level and
M0570 TABLES global temporary on and 2593893
_TemporaryTa drop temporary
tables resource
bles" tables when they
overhead
are no longer
needed.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 40 of 109

2019-08-27 1999993
Temporary tables
with names
following the
naming convention
_SYS_PARAM_I
TAB* 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/stm
t_cache_size
, SAP Note
2600030). This will
implicitly also
reduce the number
of FDA related
temporary tables.
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
Number of NO SQL:
Performance cleanup reports
M0572 TABLES global LOGGING "HANA_Tables 2214569
regressions exist:
tables "
UJHANA_DELET
E_BPC_HC_TAB
LE: Cleanup of
temporary BPC
hierarchy tables
RSDDTMPTAB_D
ELETE,
SAP_DROP_TMP
TABLES: Cleanup
of temporary BW
tables As a
workaround you
can increase the

© 2019 SAP SE or an SAP affiliate company. All rights reserved 41 of 109

2019-08-27 1999993
following
parameter that
defines the
maximum number
of NO LOGGING
tables:
indexserver.
ini -> [catalog_wat
chdog] ->
max_nologgin
g_table_coun
t_limit
Avoid to configure
small unused
retention periods
on table level in
order to eliminate
the risk of frequent
Tables with SQL: reloads. In general
small unused "HANA_Tables Performance it is sufficient to
M0574 TABLES global 2127458
retention _ColumnStore regressions rely on the normal
period _TableSize" SAP HANA
resource container
management that
kicks out the least
relevant content in
case a shrink is
required.
Make sure that all
Risk of
Tables tables are
inconsistenc
M0580 TABLES global assigned to assigned to proper
ies and
wrong service services, typically
terminations
indexserver.
Investigate why
tables without a
SQL: Risk of
Tables with properly assigned
"HANA_Tables inconsistenc
M0582 TABLES global empty table location exist and
_TableLocati ies and
location eliminate the
ons" terminations
inconsistenc
y.

Analysis SQL
Check Potential SAP
Area Validity Description statement (SAP Details
ID impact Note
Note 1969700)
SQL:
Disable the k
TRACES, "HANA_Traces
Rev. >= Kernel profiler Performance profiler traces
M0610 DUMPS AND _ActivatedAn 1804811
1.00.70 active degradations unless really
LOGS dModified
needed.
Traces"
TRACES, Performance trace SQL: Performance Disable the
M0612 global 1787489
DUMPS AND enabled "HANA_Traces degradations performance
© 2019 SAP SE or an SAP affiliate company. All rights reserved 42 of 109
2019-08-27 1999993
LOGS _ActivatedAn unless really
dModified needed.
Traces"
Disable the
function profil
SQL: unless really
TRACES, "HANA_Traces needed. Be a
Function profiler Performance
M0613 DUMPS and global _ActivatedAn 1787489 that this chec
enabled degradations
LOGS dModified covers the fun
Traces" profiler in the
context of the
performance
SQL:
TRACES, "HANA_Traces Disable the S
SQL trace Performance
M0614 DUMPS AND global _ActivatedAn 2031647 trace unless r
enabled degradations
LOGS dModified needed.
Traces"
SQL: Disable the
TRACES, Indexserver "HANA_Traces indexserver
Performance
M0616 DUMPS AND global python trace _ActivatedAn 1935113 python trace
degradations
LOGS enabled dModified unless really
Traces" needed.
SQL:
Disable the
TRACES, "HANA_Traces
Executor python Performance executor pyth
M0617 DUMPS AND global _ActivatedAn 2020877
trace enabled degradations trace unless r
LOGS dModified
needed.
Traces"
SQL:
Disable the S
TRACES, SQL client "HANA_Traces
Performance client network
M0618 DUMPS AND global network trace _ActivatedAn
degradations trace unless r
LOGS enabled dModified
needed.
Traces"
Don't use an
SQL:
Minimum expensive
TRACES, "HANA_Traces
expensive SQL Performance statement tra
M0620 DUMPS AND global _ActivatedAn 2180165
trace threshold degradations threshold belo
LOGS dModified
(ms) 1000 ms unle
Traces"
really needed
Increase the
expensive
SQL: statement tra
TRACES, Traced expensive
"HANA_SQL_Ex Performance threshold in o
M0623 DUMPS AND global SQL statements 2180165
pensiveState degradations to reduce the
LOGS (last day)
ments" amount of
captured SQL
statements.
SQL: Check why th
TRACES, Expensive
"HANA_SQL_Ex Analysis are no older
M0624 DUMPS AND global statements trace 2180165
pensiveState limitations records availa
LOGS retention (days)
ments" in the expens

© 2019 SAP SE or an SAP affiliate company. All rights reserved 43 of 109

2019-08-27 1999993
statements tr
Typical reaso
are: Many
statements ar
captured so t
the available
files are
overwritten w
less than a w
Trace files ar
configured wi
limited size o
number Expe
statements tr
was recently
activated and
wasn't runnin
before A syst
replication
takeover was
so that older
from primary
can no longer
accessed Try
find capturing
thresholds so
the expensive
statements tr
data is preser
for at least 7
SQL: Don't configu
TRACES, Existence of "HANA_Traces special datab
Performance
M0630 DUMPS AND global database trace _ActivatedAn 2380176 trace settings
degradations
LOGS settings dModified unless really
Traces" needed.
SQL: Don't configu
TRACES, Existence of user- "HANA_Traces user-specifi
Performance
M0635 DUMPS AND global specifi _ActivatedAn 2119087 c trace setting
degradations
LOGS c trace settings dModified unless really
Traces" needed.
SQL:
Don't configu
TRACES, Existence of end- "HANA_Traces
Performance end-to-end tra
M0637 DUMPS AND global to-end trace _ActivatedAn 2119087
degradations settings unles
LOGS settings dModified
really needed
Traces"
Avoid manua
SQL: dropping bac
TRACES,
Number of backup "HANA_TraceF Risk of tool logs with SAP
M0638 DUMPS AND global 2797078
log files iles_Overvie terminations HANA >= 2.0
LOGS
w" 04 because it
not be autom

© 2019 SAP SE or an SAP affiliate company. All rights reserved 44 of 109

2019-08-27 1999993
y recreated.
Check for rea
of the particu
Increased high amount
SQL: disk space generated tra
TRACES,
Number of trace "HANA_TraceF requirements information
M0639 DUMPS and global 2380176
entries (last hour) iles_Content , (activated tra
LOGS
" performance misconfigura
degradations tions, errors)
reduce the
volume.
SQL: Take appropr
TRACES, Increased
Number of trace "HANA_TraceF actions to lim
M0640 DUMPS AND global disk space 2119087
files (total) iles_Overvie amount of ex
LOGS requirements
w" trace files.
SQL: Take appropr
TRACES, Increased
Number of trace "HANA_TraceF actions to lim
M0641 DUMPS AND global disk space 2119087
files (last day) iles_Overvie amount of ex
LOGS requirements
w" trace files.
SQL: Take appropr
TRACES, Increased
Size of trace files "HANA_TraceF actions to lim
M0642 DUMPS AND global disk space 2119087
(GB, total) iles_Overvie size of existin
LOGS requirements
w" trace files.
SQL: Take appropr
TRACES, Increased
Size of trace files "HANA_TraceF actions to lim
M0643 DUMPS AND global disk space 2119087
(GB, last day) iles_Overvie size of existin
LOGS requirements
w" trace files.
Take appropr
actions to lim
size of existin
trace files. Fo
SQL: backup.log an
TRACES, Increased
Size of largest "HANA_TraceF backint.log an
M0644 DUMPS AND global disk space 2119087
trace file (MB) iles_Overvie SAP HANA >
LOGS requirements
w" SPS 04 cons
trace file rota
as suggested
SAP Note
2797078.
Check the his
memory utiliz
SQL: and identify a
TRACES, Number of OOM
"HANA_TraceF Memory resolve reaso
M0645 DUMPS AND global trace files (last 1999997
iles_Overvie bottlenecks which are
LOGS day)
w" responsible fo
out of memor
situations.
TRACES, Number of SQL: Optimize SQL
M0646 DUMPS AND global statement OOM "HANA_TraceF Terminations 1999997 statements w
LOGS trace files (last iles_Overvie particularly

© 2019 SAP SE or an SAP affiliate company. All rights reserved 45 of 109

2019-08-27 1999993
day) w" high memory
consumption.
SQL: Check for rea
TRACES,
Number of crash "HANA_TraceF Unplanned responsible fo
M0650 DUMPS AND global 2177064
dumps (last day) iles_Overvie downtime crashes and
LOGS
w" eliminate them
SQL:
TRACES, Analyze and
Number of page "HANA_TraceF
M0652 DUMPS AND global Corruptions 1977242 corruptions o
dumps (last day) iles_Overvie
LOGS persistence le
w"
Check why th
RTE dumps w
SQL: generated an
TRACES,
Number of RTE "HANA_TraceF Increased make sure th
M0655 DUMPS AND global
dumps (last day) iles_Overvie system load they are only
LOGS
w" triggered man
when really
required.
SQL: Check why th
TRACES,
Time since last "HANA_TraceF dump was cre
M0658 DUMPS AND global Various 2119087
dump (days) iles_Overvie and eliminate
LOGS
w" root cause.
SQL: Disable the C
TRACES, CPU time
"HANA_Config Increased time measure
M0660 DUMPS AND global measurement 2100040
uration_Para system load unless really
LOGS enabled
meters" needed.
An activated
allocation sta
trace imposes
some overhe
terms of CPU
performance
Note 2100040
stack module
MemoryMana
TRACES, Heap allocators SQL: r::CheckedBl
Increased
M0661 DUMPS AND global with allocation "HANA_Heap_F 1999997 ockHandler::
system load
LOGS stack trace lags" createStackt
race). Make s
that allocation
stack traces a
only activated
really require
deactive them
once you hav
collected suff
data.
TRACES, Heap allocators SQL: Allocated me
Increased
M0662 DUMPS AND global with other "HANA_Heap_F 1999997 traces (e.g. in
system load
LOGS activated traces lags" context of me

© 2019 SAP SE or an SAP affiliate company. All rights reserved 46 of 109

2019-08-27 1999993
fencing, SAP
2222276) imp
some overhe
terms of CPU
performance
Note 2100040
stack module
MemoryMana
r::CheckedBl
ockHandler::
createStackt
race). Make s
that memory
traces traces
only activated
really require
deactive them
once you hav
collected suff
data.
Allocated me
traces (e.g.
allocation sta
trace or mem
fencing, SAP
2222276) imp
some overhe
terms of CPU
performance
Note 2100040
stack module
TRACES, Time since active SQL:
Increased MemoryMana
M0663 DUMPS AND global heap allocator "HANA_Heap_F 1999997
system load r::CheckedBl
LOGS trace (days) lags"
ockHandler::
createStackt
race). Make s
that memory
traces traces
only activated
really require
deactive them
once you hav
collected suff
data.
Check if there
some genera
Time since last SQL: Performance HANA issues
TRACES,
trace file "HANA_TraceF and resource
M0670 DUMPS AND global 2119087
modification iles_Overvie infrastructu bottleneck, lo
LOGS
(s) w" re issues issues) or
infrastructu
re problems (

© 2019 SAP SE or an SAP affiliate company. All rights reserved 47 of 109

2019-08-27 1999993
disk I/O) and
eliminate thes
problems.
Check the
SQL:
reported alert
"HANA_Statis
STATISTICS Open alerts (high resolve the ro
M0710 global ticsServer_A Various 2445867
SERVER priority) cause or adju
lerts_Curren
the alert
t"
thresholds.
Check why
SQL:
retrieving aler
"HANA_Statis
STATISTICS Open alerts (error Monitoring runs into an
M0711 global ticsServer_A 2445867
SERVER state) limitations internal error
lerts_Curren
eliminate the
t"
cause.
Run SQL:
"HANA_Statis
ticsServer_A
lerts_Histor
y" with ALER
= 0 and proce
SQL:
as described
Internal statistics "HANA_Statis
STATISTICS Monitoring SAP Note
M0712 global server errors (last ticsServer_A 2147247
SERVER limitations 2147247 ("Ho
day) lerts_Histor
can internal
y"
statistics serv
errors be
analyzed?") in
order to resol
the underlying
problems.
Check why al
checks and /
history collec
runs were no
SQL:
Number of actions executed with
STATISTICS "HANA_Statis Monitoring
M0715 global not executed as 2147247 defined interv
SERVER ticsServer_S limitations
expected frequency (e.
chedule"
high system l
disabled chec
and eliminate
root cause.
In rare cases
statistics serv
worker thread
SQL:
Number of exist although
STATISTICS "HANA_Thread Monitoring
M0716 ESS statistics server 2147247 statistics serv
SERVER s_CurrentThr limitations
worker threads supposed to b
eads"
active. In this
you can only
resolve the

© 2019 SAP SE or an SAP affiliate company. All rights reserved 48 of 109

2019-08-27 1999993
problem by
restarting SA
HANA.
Additionally
you can open
SAP incident
order to ident
the root caus
the missing w
threads.
Check why th
SQL:
actions are
STATISTICS Number of "HANA_Statis Monitoring
M0717 ESS 2113228 disabled and
SERVER disabled actions ticsServer_S limitations
activate them
chedule"
again if possi
Check why th
SQL:
Number of actions are
STATISTICS "HANA_Statis Monitoring
M0718 ESS relevant inactive 2147247 inactive and
SERVER ticsServer_S limitations
actions activate them
chedule"
again if possi
The STATE v
in the statistic
server contro
table
STATISTICS
CHEDULE m
contain one o
following valu
SQL: Disabled Idle
Number of actions
STATISTICS "HANA_Statis Monitoring Inactive
M0719 ESS with unknown 2147247
SERVER ticsServer_S limitations Scheduled If
state
chedule" values exist (
to an earlier f
manual upda
the action wil
never be
executed. Up
the values ba
on your need
e.g. to 'Idle'.
Check why th
events are no
acknowledge
(e.g. statistics
Events not SQL: server proble
STATISTICS Monitoring
M0720 global acknowledged "HANA_Events 2126236 and take
SERVER limitations
since >= 1800 s " appropriate
actions to ma
sure that an
acknowledge
ent happens

© 2019 SAP SE or an SAP affiliate company. All rights reserved 49 of 109

2019-08-27 1999993
time. Often th
problem is ca
by the bug
described in S
Note 2126236
it can be fixed
implementing
patch_check_
21_add_info_
events.sql.
Check why
sending e-ma
SQL:
doesn't work,
"HANA_Statis
STATISTICS Pending e-mails Monitoring clean up old m
M0730 ESS ticsServer_M 2133799
SERVER older than 3 days limitations send request
ailNotificat
take appropri
ions"
actions to act
sending e-ma
SQL: Performance Keep the amo
"HANA_Data_C regressions, of alerts in tab
STATISTICS Alerts older than
M0735 ESS olumnValueCo increased 2170779 STATISTICS
SERVER 42 days
unter_Comman memory LERTS_BAS
dGenerator" consumption reasonable le
Delete freque
SQL: Performance
reported alert
"HANA_Data_C regressions,
STATISTICS Alerts reported make sure th
M0736 ESS olumnValueCo increased 2147247
SERVER frequently reporting
unter_Comman memory
frequency is
dGenerator" consumption
reduced.
Check why th
statistics serv
SQL: isn't active sin
Time since
STATISTICS "HANA_Statis Monitoring significant tim
M0740 global statistics server 2147247
SERVER ticsServer_S limitations and take
run (s)
chedule" appropriate
actions to act
it.
Proceed as
described in S
Note 2124112
"Which proble
SQL:
Total SQL cache and solutions
STATISTICS "HANA_Memory Performance
M0744 global share of statistics 2124112 in the area of
SERVER _SQLCache_To regressions
server (%) parsing?" -> "
pConsumers"
SQL cache
occupation by
_SYS_STATI
ICS requests
Total size of SQL: Increased Make sure th
STATISTICS
M0745 global statistics server "HANA_Tables memory 2147247 data collectio
SERVER
tables (GB) _LargestTabl consumption deletion is
© 2019 SAP SE or an SAP affiliate company. All rights reserved 50 of 109
2019-08-27 1999993
es" configured
optimally for t
statistics serv
histories.
Make sure th
data collectio
SQL:
Total memory Increased deletion is
STATISTICS "HANA_Tables
M0746 global share of statistics memory 2147247 configured
SERVER _LargestTabl
server (%) consumption optimally for t
es"
statistics serv
histories.
Delete record
with
EXECUTION
UNT = 0 from
SQL:
Number of zero HOST_SQL_
"HANA_Data_C Increased
STATISTICS entries in N_CACHE an
M0747 SSS olumnValueCo memory 2084747
SERVER HOST_SQL_PLA adjust the dat
unter_Comman consumption
N_CACHE collection by
dGenerator"
adding "WHE
EXECUTION
UNT > 0" to t
query parame
Monitoring vie
M_CS_UNLO
it already a hi
because it is
based on load
trace files. As
consequence
historizatio
n is not usefu
- even worse
SQL:
History of Increased can result in a
STATISTICS "HANA_Statis
M0748 global M_CS_UNLOADS memory 2084747 memory
SERVER ticsServer_S
collected consumption consumption
chedule"
the statistics
server if man
unloads have
happened in
past. Therefo
you should di
the history
collection for
M_CS_UNLO
.
Increased The added va
SQL:
HISTORY of memory of the
STATISTICS "HANA_Statis
M0749 ESS M_RECORD_LOC consumption, 2147247 HOST_RECO
SERVER ticsServer_S
KS collected merge and LOCKS histo
chedule"
lock issues small and at t

© 2019 SAP SE or an SAP affiliate company. All rights reserved 51 of 109

2019-08-27 1999993
same time it c
become huge
causing vario
issues up to
standstill situa
(e.g. due to lo
running merg
blocking save
and DML
operations wi
ConsistentCh
angeLock).
Therefore it s
generally be
deactivated.
Check to wha
extent you ca
increase the
SQL:
retention time
Stat. server tables "HANA_Statis
STATISTICS Monitoring 42 days witho
M0750 global with retention < 42 ticsServer_H 2147247
SERVER limitations suffering from
days istories_Ret
large table gr
entionTime"
and high mem
requirements
.
Thread samp
may only be
historicized
once an hour
in case of a c
or shutdown u
60 minutes of
thread sampl
are missing. M
SQL:
Historic thread sure that thre
STATISTICS "HANA_Statis Monitoring
M0751 global samples save 2147247 samples are
SERVER ticsServer_S limitations
interval (s) historicized
chedule"
at least every
minutes: UPD
_SYS_STATI
ICS.STATIST
CS_SCHEDU
SET
INTERVALLE
TH = 600 WH
ID = 5034
SQL: Consider a
Embedded
STATISTICS Rev. >= "HANA_Config Monitoring migration to t
M0755 statistics server 2092033
SERVER 1.00.74 uration_Para limitations embedded
used
meters" statistics serv
M0760 STATISTICS ESS Status of SQL: Monitoring 2092033 Complete a

© 2019 SAP SE or an SAP affiliate company. All rights reserved 52 of 109

2019-08-27 1999993
SERVER embedded "HANA_Statis limitations successful
statistics server ticsServer_P migration to t
migration roperties" embedded
statistics serv
Increase the
Log segment size SQL: segment size
STATISTICS Backup
M0765 SSS of statisticsse "HANA_Logs_L 2019148 the statistics
SERVER problems
rver (MB) ogBuffers" server to 102
MB.
SQL:
Number of stat. Move all stati
STATISTICS "HANA_Tables Monitoring
M0770 ESS server tables not 2091256 server tables
SERVER _LargestTabl limitations
on master the master no
es"
Entries with
OBJECT_NA
'(unknown)' a
typically linke
Unknown entries SQL: Increased
dropped
in "HANA_Data_C memory
STATISTICS temporary tab
M0780 ESS HOST_OBJECT_ olumnValueCo consumption, 2147247
SERVER and are there
LOCK_STATIST unter_Comman merge and
of not much u
ICS dGenerator" lock issues
You can dele
them in order
reduce the siz
the history tab
An orphan en
for alert 32 in
STATISTICS
LERT_INFOR
TION of owne
_SYS_STATI
ICS can resu
terminations
when opening
Overview tab
the Administr
on Console o
STATISTICS ESS, Rev. Orphan entry for Monitoring SAP HANA S
M0781 2803904
SERVER >= 2.00.040 alert 32 limitations (SAP Note
2073112) in c
SAP HANA >
2.00.040 is us
Delete this en
eliminate the
inconsistenc
y and resolve
problem: DEL
FROM
_SYS_STATI
ICS.STATIST
CS_ALERT_I

© 2019 SAP SE or an SAP affiliate company. All rights reserved 53 of 109

2019-08-27 1999993
ORMATION
WHERE
ALERT_ID =
Avoid long ru
SQL:
Current MVCC transactions
TRANSACTIONS "HANA_Garbag Performance
M0810 global versions in row 2169283 responsible fo
AND THREADS eCollection_ degradations
store significant am
Overview"
of MVCC vers
Avoid long ru
SQL:
Max. MVCC transactions
TRANSACTIONS Rev. >= "HANA_LoadHi Performance
M0811 versions in row 2169283 responsible fo
AND THREADS 1.00.90 story_Servic degradations
store (last day) significant am
es"
of MVCC vers
Avoid long ru
transactions
responsible fo
SQL: significant am
TRANSACTIONS Max. versions per "HANA_Garbag Performance of MVCC vers
M0812 global 2169283
AND THREADS record in row store eCollection_ degradations Check why
Overview" specific recor
are modified
particularly
frequently.
Avoid long ru
transactions
responsible fo
SQL: significant am
TRANSACTIONS Max. versions per "HANA_Garbag Performance of MVCC vers
M0813 global 2169283
AND THREADS table in row store eCollection_ degradations Check why
Overview" specific table
modified
particularly
frequently.
Avoid long ru
SQL:
Age of transaction transactions
TRANSACTIONS "HANA_Garbag Performance
M0815 global blocking row store 2169283 responsible fo
AND THREADS eCollection_ degradations
MVCC (s) significant am
Overview"
of MVCC vers
Optimize
SQL:
particularly
TRANSACTIONS Active commit ID "HANA_Garbag Performance
M0830 global 2169283 long running
AND THREADS range eCollection_ degradations
transactions
Overview"
.
Optimize
SQL:
Max. active particularly
TRANSACTIONS Rev. >= "HANA_LoadHi Performance
M0832 commit ID range 2169283 long running
AND THREADS 1.00.90 story_Servic degradations
(last day) transactions
es"
.
TRANSACTIONS Rev. < Active update SQL: Performance Optimize
M0840 2169283
AND THREADS 1.00.100 transaction ID "HANA_Garbag degradations particularly

© 2019 SAP SE or an SAP affiliate company. All rights reserved 54 of 109

2019-08-27 1999993
range eCollection_ long running
Overview" update
transactions
(i.e. transactio
with change
operations).
Starting with
HANA SPS 1
value is no lo
used for garb
collection
purposes (se
SAP Note
2322024).
Optimize
particularly
SQL: long running
Oldest active
TRANSACTIONS "HANA_Garbag Performance update
M0841 global update transaction 2169283
AND THREADS eCollection_ degradations transactions
current (h)
Overview" (i.e. transactio
with change
operations).
Optimize
particularly
SQL:
long running
Oldest active "HANA_Garbag
TRANSACTIONS Rev. >= Performance update
M0842 update transaction eCollection_ 2169283
AND THREADS 1.00.90 degradations transactions
in history (h) Blockers_His
(i.e. transactio
tory"
with change
operations).
Optimize
SQL:
Longest running particularly
TRANSACTIONS "HANA_SQL_Ac Performance
M0843 global statement current 2169283 long running
AND THREADS tiveStatemen degradations
(h) statements or
ts"
cursors.
SQL: Optimize
Longest running "HANA_Garbag particularly
TRANSACTIONS Rev. >= Performance
M0844 statement in eCollection_ 2169283 long running
AND THREADS 1.00.90 degradations
history (h) Blockers_His statements or
tory" cursors.
Proceed acco
to the steps in
SQL: referenced SA
Rev. Restart and
TRANSACTIONS Maximum update "HANA_Garbag Note in order
M0845 1.00.64 - recovery 2001840
AND THREADS transaction ID eCollection_ make sure th
1.00.69.04 termination
Overview" you don't run
restart and
recovery issu
SQL: Performance Check for lon
TRANSACTION Table MVCC
M0846 global "HANA_Garbag degradations 2169283 running SQL
AND THREADS snapshot range
eCollection_ , increased statements, id
© 2019 SAP SE or an SAP affiliate company. All rights reserved 55 of 109
2019-08-27 1999993
Overview" emory and cursors and
disk space uncommitted
requirements update
transactions
blocking garb
collection.
Due to a SAP
HANA bug wi
Revisions
1.00.122.16,
2.00.024.00,
2.00.024.01 a
2.00.030 the
store LOB
garbage colle
SQL: fails when the
"HANA_Garbag update transa
1.00.122.16
eCollection_ Increased ID has excee
TRANSACTION <= Current update
M0848 Overview" SQL: disk space 2633077 value of 4 bill
AND THREADS 2.00.024.01 transaction ID
"HANA_Garbag requirements Avoid upgrad
2.00.030
eCollection_ one of these
LOBs" Revisions in c
you already h
a high update
transaction ID
value. Procee
according to S
Note 2633077
you already u
one of these
Revisions.
See SAP Not
2220627 ("Ca
SQL: there be orph
Increased
TRANSACTION "HANA_Garbag disk LOBs?")
M0849 global Orphan LOBs disk space 2220627
AND THREADS eCollection_ take appropri
requirements
LOBs" actions to red
the amount o
orphan disk L
Avoid long ru
SQL: Increased
Persistence transactions
TRANSACTIONS "HANA_Garbag memory and
M0850 global garbage collection 2169283 and open idle
AND THREADS eCollection_ disk space
history count cursors block
Persistence" requirements
garbage colle
See SAP Not
2220627 ("Ca
SQL: Increased
Time since last there be orph
TRANSACTIONS "HANA_LOBs_C memory and
M0851 global CS LOB garb. coll. 2220627 disk LOBs?")
AND THREADS olumnStore_R disk space
(days) check why th
eclaims" requirements
column store
garbage colle

© 2019 SAP SE or an SAP affiliate company. All rights reserved 56 of 109

2019-08-27 1999993
is stopped sin
significant tim
Avoid long ru
SQL: Increased
transactions
TRANSACTIONS Undo and cleanup "HANA_Transa memory and
M0852 global 2169283 and open idle
AND THREADS files ctions_UndoC disk space
cursors block
leanupFiles" requirements
garbage colle
Avoid long ru
SQL: Increased
transactions
TRANSACTIONS Undo and cleanup "HANA_Transa memory and
M0854 global 2169283 and open idle
AND THREADS file size (GB) ctions_UndoC disk space
cursors block
leanupFiles" requirements
garbage colle
Increased Check if you
memory and reduce the am
disk space of performed
SQL: requirements change opera
Max. undo size of
TRANSACTIONS "HANA_Transa , increased or if you can
M0856 global current transaction 2169283
AND THREADS ctions_UndoA I/O and reduce the co
(MB)
ndRedoLog" system frequency in o
replication to split the ch
load, longer load into seve
restart times smaller piece
Increased Check if you
memory and reduce the am
disk space of performed
SQL: requirements change opera
Max. redo size of
TRANSACTIONS "HANA_Transa , increased or if you can
M0857 global current transaction 2169283
AND THREADS ctions_UndoA I/O and reduce the co
(MB)
ndRedoLog" system frequency in o
replication to split the ch
load, longer load into seve
restart times smaller piece
Check why a
significant am
of rollbacks is
executed, e.g
checking the
HANA databa
trace files (SA
Note 2380176
Increased
Rollbacks per SQL: and client (e.g
TRANSACTIONS resource
M0858 global second (last "HANA_Worklo 2000000 ABAP) traces
AND THREADS consumption,
week) ad" error and elim
terminations
reasons for
rollbacks. In c
of internal
rollbacks it m
required to
activate a SA
HANA SQL tr
(SAP Note

© 2019 SAP SE or an SAP affiliate company. All rights reserved 57 of 109

2019-08-27 1999993
2031647). Ty
reasons for m
rollbacks are:
HANA <=
1.00.122.08,
2.00.002.00,
2.00.010:
ABAP_SYST
TIMEZONE c
Check why
SQL: sessions are
TRANSACTIONS Rev. >= Current pending "HANA_LoadHi Performance currently pen
M0860 2000000
AND THREADS 1.00.90 sessions story_Servic regressions and eliminate
es" HANA overlo
situations.
Check why
SQL: sessions wer
TRANSACTIONS Rev. >= Avg. pending "HANA_LoadHi Performance recently pend
M0863 2000000
AND THREADS 1.00.90 sessions (last day) story_Servic regressions and eliminate
es" HANA overlo
situations.
Check for rea
of queueing o
SQL: rejections of
"HANA_Worklo incoming requ
TRANSACTIONS Rev. >= Admission control Performance
M0864 ad_Admission 2222250 e.g. high load
AND THREADS 2.00.010 events (last day) regressions
ControlEvent inadequate
s" admission co
configuratio
n.
Check for rea
of queueing o
rejections of
SQL:
incoming requ
TRANSACTIONS Rev. >= Admission control "HANA_LoadHi
M0865 Terminations 2222250 e.g. high load
AND THREADS 2.00.010 rejections story_Servic
inadequate
es"
admission co
configuratio
n.
Check for rea
of queueing o
rejections of
SQL:
incoming requ
TRANSACTIONS Rev. >= Admission control "HANA_LoadHi Performance
M0866 2222250 e.g. high load
AND THREADS 2.00.010 max. queue size story_Servic regressions
inadequate
es"
admission co
configuratio
n.
SelfWatchDog SQL: A high activity
TRANSACTIONS Performance
M0870 global activity time (%, "HANA_Thread 1999998 of the
AND THREADS regressions
last hour) s_ThreadSamp SelfWatchDo
© 2019 SAP SE or an SAP affiliate company. All rights reserved 58 of 109
2019-08-27 1999993
les_FilterAn thread can
dAggregation indicate probl
" accessing the
file for shared
memory acce
in the /tmp
directory. See
SAP Notes
1999998 and
2100296 for m
information.
A gap in the l
history data d
collection ofte
indicates a ge
issue of the
database, ho
SQL:
service. Chec
TRANSACTIONS Rev. >= Max. load history "HANA_Global Hang
M0871 2222110 time frames w
AND THREADS 1.00.90 gap (s, last week) _CriticalTim scenarios
the highest ga
eFrames"
and optimize
performance,
locking and
resource utiliz
(SAP Note
2000000).
If a session
permanently
remains in a
CANCEL
REQUESTED
state (e.g.
"Running
(CANCEL
REQUESTED
, it can block
garbage colle
Connections in SQL: Risk of (SAP Note
TRANSACTIONS CANCEL "HANA_Connec blocked 2169283).
M0878 global 2092196
AND THREADS REQUESTED tions_Overvi garbage Therefore you
state ew" collection should check
you can
successfully
kill it. If you d
succeed and
Note 2092196
doesn't indica
that it is an al
known bug, o
a SAP inciden
request
assistance. D

© 2019 SAP SE or an SAP affiliate company. All rights reserved 59 of 109

2019-08-27 1999993
an initializati
on bug it can
happen that a
connection re
to “Dynamic
Range Partiti
” is shown wit
“Idle (CANCE
REQUESTED
with SAP HAN
<= 1.00.122.1
This can be
ignored and
doesn’t indica
problem.
This check
compares the
number of op
connections w
the
maximum_co
ections limita
SQL:
(see SAP No
TRANSACTIONS Open connections "HANA_Connec
M0880 global Terminations 1910159 2154870). Ch
AND THREADS (%) tions_Overvi
it is possible t
ew"
reduce the nu
of open
connections o
consider
increasing the
maximum_co
ections param
In rare situati
bug with Rev
102.02 and R
110 can resu
an increased
amount of pa
job workers. A
consequence
system
SQL:
TRANSACTIONS Max. parked job Performance performance
M0882 global "HANA_Jobs_E 2256719
AND THREADS worker ratio regressions suffer and in
xecutors"
worst case it
comes to
standstill.
Consider an
upgrade to a
recent SAP H
Revision leve
alternativel
y restart SAP

© 2019 SAP SE or an SAP affiliate company. All rights reserved 60 of 109

2019-08-27 1999993
HANA.
A repeatedly
increased num
of queued job
workers can
indicate that t
job worker loa
(i.e. paralleliz
activities) is h
SQL: than the avail
TRANSACTIONS Queued job Performance
M0883 global "HANA_Jobs_E 2222250 job workers. S
AND THREADS workers regressions
xecutors" SAP Note
2222250 for j
worker
configuratio
n and SAP N
2000002 for S
statement
optimization
.
The internally
used
max_concurr
ncy limitation
job workers c
differ in some
cases uninten
lly from the se
of the related
parameter, e.
because an
UNSET of the
parameter wa
properly
considered by
Deviating SQL:
TRANSACTIONS Rev. < Performance running syste
M0884 max_concurre "HANA_Jobs_E 2222250
AND THREADS 2.00.030 regressions the used
ncy used internally xecutors"
concurrency i
much smaller
the intended
the number o
workers is lim
and throughp
can reduce. I
case you can
workaround
manually set
max_concurr
ncy to a
reasonably hi
explicit value.
Starting with

© 2019 SAP SE or an SAP affiliate company. All rights reserved 61 of 109

2019-08-27 1999993
HANA 2.0 SP
the max_conc
ncy value is
internally adju
in relation to t
new
max_concurr
ncy_min_pct
setting and so
check is
deactivated to
avoid false al
Check for rea
why several
currently activ
threads alrea
run for a long
time (e.g. lock
SQL: resource limit
Current threads
TRANSACTIONS "HANA_Thread Performance expensive SQ
M0885 global with significant 2114710
AND THREADS s_CurrentThr regressions statements).
duration
eads" See SAP Not
2000000 for m
information re
to SAP HANA
performance
optimization
.
Check if it is
normal that th
reported
application us
are responsib
a significant
database acti
(e.g. because
are central jo
users or the
SQL: application on
Application users
TRANSACTIONS "HANA_Thread Performance connects with
M0887 global with significant 2114710
AND THREADS s_CurrentThr regressions single applica
threads
eads" user to the SA
HANA databa
or if you can
reduce the lo
the applicatio
users. See SA
Note 2000000
more informa
related to SA
HANA
performance

© 2019 SAP SE or an SAP affiliate company. All rights reserved 62 of 109

2019-08-27 1999993
optimization
.
A high amoun
threads being
active in an
uncommon th
method can
indicate issue
SQL: and so it shou
"HANA_Thread checked if the
Unusual frequent
TRANSACTIONS s_ThreadSamp Performance activities are
M0890 global thread methods 2114710
AND THREADS les_FilterAn regressions justified or if t
(last hour)
dAggregation is possible. S
" SAP Note
2000000 for m
information re
to SAP HANA
performance
optimization
.
A high amoun
threads being
active in an
uncommon th
method can
indicate issue
SQL: and so it shou
"HANA_Thread checked if the
Unusual frequent
TRANSACTIONS s_ThreadSamp Performance activities are
M0892 global thread methods 2114710
AND THREADS les_FilterAn regressions justified or if t
(last week)
dAggregation is possible. S
" SAP Note
2000000 for m
information re
to SAP HANA
performance
optimization
.
Make sure th
SQL:
least one
Age of last data "HANA_Backup Recoverabili
M0910 BACKUP global 1642148 successful da
backup (days) s_BackupRuns ty limitations
backup is cre
"
per day.
Identify and
eliminate the
SQL: causes of the
Age of last data
"HANA_Backup Recoverabili backup failure
M0911 BACKUP global backup error 1642148
s_BackupRuns ty limitations and make sur
(days)
" that at least o
successful da
backup is cre

© 2019 SAP SE or an SAP affiliate company. All rights reserved 63 of 109

2019-08-27 1999993
per day.
Check and
SQL:
Min. data backup Disk I/O eliminate
"HANA_Backup
M0915 BACKUP global throughput (GB/h, performance 1999930 bottlenecks in
s_BackupRuns
last week) regressions disk I/O area
"
the data files.
Check and
SQL:
Avg. data backup Disk I/O eliminate
"HANA_Backup
M0916 BACKUP global throughput (GB/h, performance 1999930 bottlenecks in
s_BackupRuns
last week) regressions disk I/O area
"
the data files.
SQL: Make sure th
Age of last log "HANA_Backup Recoverabili regular succe
M0920 BACKUP global 1642148
backup (hours) s_BackupRuns ty limitations log backups a
" created.
SQL: Identify and
Age of last log
"HANA_Backup Recoverabili eliminate the
M0921 BACKUP global backup error 1642148
s_BackupRuns ty limitations causes of the
(days)
" backup failure
Check why th
runtime of the
backups is
increased and
eliminate pote
bottlenecks.
If global.ini ->
[backup] ->
max_log_bac
up_group_siz
e is set to a v
greater than 1
multiple logs
be bundled in
SQL: backup. In thi
Maximum log
"HANA_Backup Recoverabili context increa
M0922 BACKUP global backup duration 1999930
s_BackupRuns ty limitations times are oka
(s, last day)
" with SAP HAN
1.0, because
individual log
backups will s
the overall ba
time for all log
With SAP HA
>= 2.0 the
behavior chan
and you shou
longer see
increased bac
times in case
log backup
groups.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 64 of 109

2019-08-27 1999993
SQL: Identify and
Log backup errors "HANA_Backup Recoverabili eliminate the
M0923 BACKUP global 1642148
(last month) s_BackupRuns ty limitations causes of the
" backup failure
Configure the
SQL: automatic log
Automatic log "HANA_Config Recoverabili backup based
M0930 BACKUP global 1645183
backup uration_Para ty limitations the SAP
meters" recommenda
ons.
Configure the
SQL:
mode based
Database log "HANA_Config Recoverabili
M0935 BACKUP global 1645183 the SAP
mode uration_Para ty limitations
recommenda
meters"
ons.
SQL:
Increased Keep the bac
Size of backup "HANA_Backup
M0940 BACKUP global I/O load, log 2083715 catalog at a
catalog (MB) s_CatalogSiz
full situations reasonable si
e"
Keep the bac
catalog at a
SQL:
Increased reasonable si
Catalog size share "HANA_Backup
M0942 BACKUP global backup size 2083715 it doesn't incr
(last day, %) s_BackupRuns
and duration the overall ba
"
size significan
y.
Regularly rem
SQL: old backups f
Age of oldest Increased
"HANA_Backup the catalog (b
M0945 BACKUP global backup in catalog I/O load, log 2083715
s_CatalogSiz keep at least
(days) full situations
e" backups of th
recent 28 day
Take appropr
SQL: actions to ma
Log segments not Log full
M0950 BACKUP global "HANA_Logs_L 2083715 sure that log
free for reuse situations
ogSegments" segments are
freed for reus
Consider redu
the number o
SQL:
Log segments free Log full log segments
M0952 BACKUP global "HANA_Logs_L 2083715
for reuse situations using ALTER
ogSegments"
SYSTEM
RECLAIM LO
Increase the
Backup
segment size
SQL: bottlenecks
Max. number of the involved
"HANA_Backup and
M0955 BACKUP global log backups / 2083715 services in or
s_BackupRuns increased
service (last day) to keep the
" backup
amount of log
catalog sizes
backups on a

© 2019 SAP SE or an SAP affiliate company. All rights reserved 65 of 109

2019-08-27 1999993
reasonable le
Analyze and
SQL: Performance eliminate long
Age of oldest
"HANA_Locks_ regressions running curre
M1010 LOCKS global active trans. lock 1999998
Transactiona and stuck record or tabl
wait (s)
l_LockWaits" situations lock wait
situations.
Analyze and
SQL: Performance eliminate long
Trans. lock wait
"HANA_Locks_ regressions running histor
M1011 LOCKS global durations > 600 s 1999998
Transactiona and stuck record or tabl
(last day)
l_LockWaits" situations lock wait
situations.
Analyze and
SQL: Performance
eliminate curr
Threads currently "HANA_Thread regressions
M1020 LOCKS global 1999998 transactiona
waiting for locks s_CurrentThr and stuck
l and internal
eads" situations
wait situation
SQL:
Analyze and
"HANA_Thread Performance
Maximum threads eliminate hist
s_ThreadSamp regressions
M1021 LOCKS global waiting for locks 1999998 transactiona
les_Aggregat and stuck
(last day) l and internal
ionPerTimeSl situations
wait situation
ice"
SQL:
"HANA_LoadHi Analyze and
Concurrently Performance
story_Servic eliminate long
Rev. >= blocked regressions
M1030 LOCKS es" SQL: 1999998 running recor
1.00.90 transactions and stuck
"HANA_Locks_ table lock wa
(last hour) situations
Transactiona situations.
l_LockWaits"
SQL:
"HANA_LoadHi Analyze and
Concurrently Performance
story_Servic eliminate long
Rev. >= blocked regressions
M1031 LOCKS es" SQL: 1999998 running recor
1.00.90 transactions and stuck
"HANA_Locks_ table lock wa
(last day) situations
Transactiona situations.
l_LockWaits"
Check why so
many transac
al locks are u
Garbage
SQL: concurrently
Total current collection,
"HANA_Locks_ and if it is pos
M1040 LOCKS general transactiona locking and 1999998
Transactiona to reduce it (e
l locks rollback
l_LockWaits" by increasing
issues
commit frequ
or reducing
package size
Transactiona SQL: Garbage Check why ol
M1045 LOCKS general 1999998
l locks older than "HANA_Locks_ collection, transactiona

© 2019 SAP SE or an SAP affiliate company. All rights reserved 66 of 109

2019-08-27 1999993
1 day Transactiona locking l locks exist a
l_LockWaits" issues make sure th
they are
committed in
SQL:
"HANA_Thread Performance Check why
Significant internal
s_ThreadSamp regressions significant wa
M1050 LOCKS general lock waits (last 1999998
les_FilterAn and stuck for internal lo
hour)
dAggregation situations happened.
"
SQL:
"HANA_Thread Performance Check why
Significant internal
s_ThreadSamp regressions significant wa
M1052 LOCKS general lock waits (last 1999998
les_FilterAn and stuck for internal lo
day)
dAggregation situations happened.
"
Check why m
threads have
wait concurre
for the same
internal locks
numbers in
brackets indic
the number o
sampled
SQL: occurrences a
"HANA_Thread Performance the average
Locks with
s_ThreadSamp regressions number of wa
M1055 LOCKS general repeated wait 1999998
les_FilterAn and stuck For example,
spikes
dAggregation situations "Acquire Inde
" Access (439
indicates that
thread sampl
contain 439 ti
of "Acquire In
Access"
contention wh
in average 62
threads have
waiting.
SQL using in Long Analyze and
SQL:
average > 1 runtimes, statements w
M1110 SQL global "HANA_SQL_SQ 2000002
connection (last high CPU high total elap
LCache"
day) consumption time.
SQL:
"HANA_Thread Long Analyze and
SQL using in
s_ThreadSamp runtimes, statements w
M1112 SQL global average > 1 2000002
les_FilterAn high CPU high total elap
thread (last hour)
dAggregation consumption time.
"
M1113 SQL ESS SQL using in SQL: Long 2000002 Analyze and
© 2019 SAP SE or an SAP affiliate company. All rights reserved 67 of 109
2019-08-27 1999993
average > 1 "HANA_Thread runtimes, statements w
thread (last day) s_ThreadSamp high CPU high total elap
les_FilterAn consumption time.
dAggregation
"
Analyze and
SQL: Long optimize curre
Longest running
"HANA_SQL_Ac runtimes, long running
M1115 SQL global current SQL 2000002
tiveStatemen high CPU statements an
statement (h)
ts" consumption the related
business logi
Analyze and
optimize curre
long running
and backgrou
activities. If ve
long running
are reported t
are no longer
active in the
system, there
be an orphan
record in the
underlying
Long monitoring vie
SQL: runtimes, M_JOB_PRO
Longest running
M1118 SQL global "HANA_Jobs_J high 2000002 SS. These or
current job (s)
obProgress" resource records can b
consumption consequence
termination (e
due to memo
allocation erro
and an inade
SAP HANA
exception
handling. In th
case you can
ignore these
entries, and t
will disappear
the next SAP
HANA startup
SQL: Long Analyze and
Exp. stmt. trace:
"HANA_SQL_Ex runtimes, optimize long
M1120 SQL global SQL running > 1 h 2000002
pensiveState high CPU running SQL
(last day)
ments" consumption statements.
SQL: Check if data
Long
Columns with "HANA_Tables accessed
>= 2.0 SPS runtimes,
M1125 SQL many scanned _ColumnStore 2000002 responsible fo
03 high CPU
records _Columns_Sta high amount
consumption
tistics" scanned reco

© 2019 SAP SE or an SAP affiliate company. All rights reserved 68 of 109

2019-08-27 1999993
can be tuned
an index can
created on th
column to red
runtime and
resource
consumption.
Check if data
accessed
responsible fo
high amount
scanned row
SQL: Long
Row tables with records can b
>= 2.0 SPS "HANA_Tables runtimes,
M1126 SQL many scanned 2000002 tuned or if an
04 _RowStore_Ta high CPU
records index can be
ble_Size" consumption
created on
selective colu
to reduce run
and resource
consumption.
Check if more
SQL stateme
SQL:
SQL cach with bind vari
"HANA_SQL_SQ SQL parse
M1129 SQL global evictions / h (last 2124112 can be used o
LCache_Overv overhead
day) the SQL plan
iew"
cache can be
increased.
Check if more
SQL stateme
with bind vari
can be used o
the SQL plan
SQL:
cache can be
SQL cache "HANA_SQL_SQ SQL parse
M1130 SQL global 2124112 increased. Be
evictions / h LCache_Overv overhead
aware that th
iew"
value is avera
over the com
time frame sin
the last servic
startup.
Check if more
SQL stateme
SQL:
SQL cache hit with bind vari
"HANA_SQL_SQ SQL parse
M1131 SQL global ratio of 2124112 can be used o
LCache_Overv overhead
indexserver (%) the SQL plan
iew"
cache can be
increased.
SQL: Make sure th
SQL cache size
ABAP, SPS "HANA_SQL_SQ SQL parse least 15 MB o
M1132 SQL per SQL 2124112
<= 1.00.08 LCache_Overv overhead SQL cache is
connection (MB)
iew" available for e

© 2019 SAP SE or an SAP affiliate company. All rights reserved 69 of 109

2019-08-27 1999993
ABAP SQL
connection,
because all
statements in
ABAP SQL
statement cac
will be pinned
the SQL cach
SAP HANA u
SAP HANA S
08.
Check if more
SQL stateme
SQL:
with bind vari
SQL preparation "HANA_SQL_SQ SQL parse
M1140 SQL global 2124112 can be used o
runtime share (%) LCache_Prepa overhead
the SQL plan
ration"
cache can be
increased.
Check which
classes of SQ
statements ar
SQL parse responsible a
SQL:
Table(s) using > overhead, eliminate the
"HANA_Memory
M1142 SQL global 10 % of SQL increased 2124112 cause (e.g. b
_SQLCache_To
cache memory introducing bi
pConsumers"
consumption variables or
limiting the m
of IN lists with
different leng
Consider redu
ABAP profile
parameter
rsdb/max_in_
blocking_fac
SQL parse
SQL: tor, taking
SQL cache used overhead,
"HANA_Memory advantage of
M1145 SQL ABAP by IN lists >= 100 increased 2124112
_SQLCache_To dbsl_equi_jo
elements (%) memory
pConsumers" in approach o
consumption
adjusting the
application in
order to reduc
the number o
long IN lists.
Check why ce
SQL parse SQL stateme
SQL:
Duplicate overhead, exist multiple
"HANA_Memory
M1147 SQL global statement hashes increased 2124112 in the SQL ca
_SQLCache_To
in SQL cache (%) memory and check for
pConsumers"
consumption optimization
s.
M1148 SQL global Statements SQL: SQL parse 2124112 Check if you

© 2019 SAP SE or an SAP affiliate company. All rights reserved 70 of 109

2019-08-27 1999993
existing > 100 "HANA_SQL_SQ overhead, reduce the am
times in SQL LCache" increased of instantiatio
cache memory ns of these S
consumption, statements in
increased SQL cache, e
translation by optimizing
table load stacked SQL
statements.
Check why
significant
SQL parse
SQL: amounts of S
Statements with overhead,
"HANA_Memory plans exist wi
M1149 SQL global SESSION LOCAL increased 2124112
_SQLCache_To plan sharing t
sharing type (%) memory
pConsumers" SESSION LO
consumption
(e.g. tempora
table accesse
Check why a
SQL parse amount of SQ
Referenced SQL: overhead, cache entries
M1150 SQL global statements in SQL "HANA_SQL_SQ increased 2124112 still reference
cache (%) LCache" memory and as a
consumption consequence
pinned in mem
A high numbe
SQL contexts
single connec
can result in a
large size of h
allocator
SQL:
Max. SQL Increased Pool/Statist
"HANA_Memory
M1152 SQL global contexts per memory 1999997 ics. Known is
_ContextMemo
connection consumption are: Statemen
ry"
being kept op
due to
transactiona
l LOBs and JD
(SAP Note
2711824)
Analyze the
temporarily
increased com
times and put
particular focu
Hourly maximum SQL: bottlenecks in
2.0 SPS >= Performance
M1159 SQL commit I/O time "HANA_IO_Com 2000000 disk I/O area
04 regressions
average (ms) mits" Note 1999930
and system
replication are
(SAP Note
1999880). Be
aware that th

© 2019 SAP SE or an SAP affiliate company. All rights reserved 71 of 109

2019-08-27 1999993
are some cur
weaknesses
measuring th
values, so tha
increased val
may not only
linked to loca
issues, they c
also be cause
system replic
overhead.
Analyze the
increased com
times and put
particular focu
SQL:
bottlenecks in
1.0 SPS >= Average commit "HANA_Connec Performance
M1160 SQL 2000000 disk I/O area
11 time (ms) tions_Statis regressions
Note 1999930
tics"
and system
replication are
(SAP Note
1999880).
Check why th
commit time i
least tempora
massively
increased and
a particular fo
on bottleneck
the disk I/O a
(SAP Note
1999930) and
system replic
SQL: area (SAP No
1.0 SPS >= Maximum commit Performance
M1161 SQL "HANA_IO_Com 2000000 1999880). Be
07 I/O time (s) regressions
mits" aware that th
are some cur
weaknesses
measuring th
values, so tha
increased val
may not only
linked to loca
issues, they c
also be cause
system replic
overhead.
Analyze the
SQL: increased com
1.0 SPS >= Average commit Performance
M1162 SQL "HANA_IO_Com 2000000 times and put
07 I/O time (ms) regressions
mits" particular focu
bottlenecks in
© 2019 SAP SE or an SAP affiliate company. All rights reserved 72 of 109
2019-08-27 1999993
disk I/O area
Note 1999930
and system
replication are
(SAP Note
1999880). Be
aware that th
are some cur
weaknesses
measuring th
values, so tha
increased val
may not only
linked to loca
issues, they c
also be cause
system replic
overhead.
A comparably
number of
commits can
responsible fo
performance
space overhe
(e.g. due to
transaction
management
commit vs. SQL: timestamp
Performance
M1163 SQL execution ratio (%, "HANA_Worklo 2000000 synchronizat
regressions
last week) ad" ion and persis
of redo data t
disk). Check
application si
why many
commits are
issued and ch
if you can red
the amount o
commits.
Check for rea
why database
requests are
executed in a
distributed wa
Unexpected SQL: (i.e. involving
Performance
M1164 SQL scale-out distributed "HANA_SQL_SQ 2000002 several hosts
regressions
executions LCache" services) alth
this is not
expected. Typ
reasons are:
Inadequate c
distribution

© 2019 SAP SE or an SAP affiliate company. All rights reserved 73 of 109

2019-08-27 1999993
mode configu
n (SAP Note
2200772)
Problems in
network betw
SAP HANA c
and server Yo
can activate a
client trace (e
SQLDBC, JD
in order to ch
there is a spe
connection is
to a SAP HAN
node. The
following trac
error e.g. indi
that SAP HAN
node <host>
be accessed:
PHYSICAL
CONNECTIO
OPEN 2018-1
12:51:32.090
164 FAILED -
10709 /
Connection fa
(RTE:[89006]
System call
'connect' faile
rc=113:No ro
host (<host>:
t>)) As a fallb
SAP HANA m
then use a
different scale
node to acces
data on <hos
introducing so
unexpected
overhead. It i
crucial to elim
communicatio
n problems b
setting up a p
network
configuratio
n (SAP Note
2222200).
SQL: Check why a
Internal Performance
M1165 SQL global "HANA_SQL_SQ 2000002 particularly
executions (%) regressions
LCache" high amount

© 2019 SAP SE or an SAP affiliate company. All rights reserved 74 of 109

2019-08-27 1999993
internal statem
executions ar
performed. A
others interna
executions ar
caused by
triggers. Try t
minimize the
usage of trigg
in order to red
the overhead
introduced by
internal statem
executions.
Make sure th
delivered
SQL: statement hin
Delivered
>= "HANA_SQL_St Performance are implemen
M1168 SQL statement hints 2700051
1.00.122.03 atementHints regressions This is particu
implemented
" useful in ABA
environments
.
Avoid defining
high number
statement hin
a permanent
basis. Instead
underlying
SQL: problem shou
Total number of Administrati
>= "HANA_SQL_St changed in
M1169 SQL implemented ve 2400006
1.00.122.03 atementHints different ways
statement hints complexity
" (e.g. by chan
to the applica
design, prope
SAP HANA
configuratio
n of a SAP H
bug fix).
Analyze and
optimize
SQL: expensive SQ
Average database Performance
M1170 SQL global "HANA_SQL_SQ 2000002 statements w
request time (ms) regressions
LCache" particularly
high cumulate
runtime.
Check and
optimize the S
Avg. ABAP buffer SQL:
Performance ABAP table b
M1180 SQL ABAP loading sessions "HANA_SQL_SQ 2000002
regressions configuratio
(last day) LCache"
n (transaction
s ST02, ST10

© 2019 SAP SE or an SAP affiliate company. All rights reserved 75 of 109

2019-08-27 1999993
AL12): Suffici
buffer size Lim
number of sw
and invalidati
s No unneces
buffering of la
tables
Disable FDA
update to a
sufficiently
new SAP HA
Revision leve
suggested in
SQL:
Avg. FDA write Performance Note 2000002
M1181 SQL ABAP "HANA_SQL_SQ 2399993
sessions (last day) regressions “What are typ
LCache"
approaches t
tune expensiv
SQL stateme
-> “High runti
when using fa
data access”.
See SAP Not
2000002 ("Ho
can compatib
SQL:
y view access
Avg. compatibilit "HANA_SQL_SQ
Performance be tuned?") a
M1182 SQL ABAP y view sessions LCache_Speci 2000002
regressions check if you c
(last day) alStatements
eliminate or
"
optimize the
compatibilit
y view access
SQL:
Memory and
DDLOG sequence "HANA_Config Buffer the DD
M1210 APPLICATION ABAP performance 2000002
cache size uration_Sequ sequence.
issues
ences"
Increased
space
SQL:
requirements Remove QCM
QCM conversion "HANA_Tables
M1220 APPLICATION ABAP client , Issues 9385 tables that ar
tables _SpecialTabl
during longer neede
es"
system
copies
Make sure th
ABAP row sto
tables are
SQL:
ABAP row store Risk of generally loca
"HANA_Tables
M1230 APPLICATION ABAP tables on slave unexpected 2222277 on the maste
_RowStore_Ta
node effects node. This ca
bleSize"
achieved by a
proper table
placement

© 2019 SAP SE or an SAP affiliate company. All rights reserved 76 of 109

2019-08-27 1999993
configuratio
n (SAP Note
1908075) and
table redistrib
on (SAP Note
2081591).
From a suppo
perspective it
important to m
connections (
related activit
like database
requests) to c
applications
. A client
application ca
register the
application fo
specific
connection vi
SET
SQL:
Connections 'APPLICATIO
"HANA_Connec Supportabili
M1240 APPLICATION without application ' = ‘<applicati
tions_Overvi ty restrictions
information (%) _name>' The
ew"
ABAP client f
example regis
itself as
'ABAP:<sid>'
or 'dw.sap<si
_<inst>'. Che
collaboratio
n with the clie
vendor if it is
possible to re
SAP HANA
database
connections w
useful applica
name.
SQL:
Increased Remove BPC
Physical BPC "HANA_Tables
M1250 APPLICATION BPC nameserver 2445363 tables that ar
tables _SpecialTabl
topology size longer neede
es"
Physical ABA
pool and clus
Check for
tables like CD
SQL: data
Physical ABAP EDI40, KAPO
"HANA_Tables consistency
M1252 APPLICATION ABAP pool and cluster 1892354 KOCLU and
_SpecialTabl and
tables RFBLG are
es" conversion
normally
state
converted into
transparent ta
© 2019 SAP SE or an SAP affiliate company. All rights reserved 77 of 109
2019-08-27 1999993
when a syste
migrated to S
HANA. If the
conversion do
happen prope
the former po
and cluster ta
may still be u
and in the wo
case you can
have data
inconsistenc
y because da
split across th
physical and
logical tables
time. If physic
pool and clus
tables are
populated wit
records, you
should check
correct the se
taking also ca
for data
consistency.
Go to transac
SMQ2 and ch
all clients for
Risk of
unnecessary
performance
entries in STO
SQL: problems
QIWKTAB update state and pro
M1260 APPLICATION ABAP "HANA_SQL_SQ due to row 2000002
rate (updates / h) or remove the
LCache" store version
Implement SA
consolidatio
Note 2125972
n
order to optim
the reprocess
logic of SMQ2
Column store
indexes on m
than one colu
result in a
significant me
SQL:
and maintena
Two-column "HANA_Indexe
Memory overhead, an
M1270 APPLICATION ABAP indexes including s_MultiColum 2160391
overhead some cases a
client column nIndexesWith
significant
Client"
performance
impact is pos
The client col
typically prov
limited benefi

© 2019 SAP SE or an SAP affiliate company. All rights reserved 78 of 109

2019-08-27 1999993
terms of
selectivity.
Therefore you
redefine non-
unique indexe
client and one
other column
typically in a w
that you remo
the client colu
from the inde
Check why a
particular high
amount of SA
ABAP short
dumps have
happened. Th
SQL:
Growth of short aren't necess
"HANA_Tables ABAP
M1280 APPLICATION ABAP dump table SNAP 2399990 related to
_IOStatistic terminations
(GB, last day) problems on
s"
HANA side, b
nevertheless
they should b
analyzed and
reduced if
possible.
Check SAP A
update record
error states (e
"Error" or "Err
(no retry)") in
transaction S
and clean up
close interact
with the relate
application te
A wrong hand
of terminated
Number of update SQL:
ABAP update record
M1285 APPLICATION ABAP records in error "HANA_ABAP_U
terminations can result in
state pdateErrors"
inconsistenc
ies, so a clea
needs to be
handled with
There are
situations wh
orphan error
records rema
table VBERR
In this case
transaction S
doesn’t show

© 2019 SAP SE or an SAP affiliate company. All rights reserved 79 of 109

2019-08-27 1999993
real update e
and the scena
can be ignore
VBERROR w
automaticall
y purged afte
retention time
50 days.
Make sure th
Secure store Authenticati secure store
M1310 SECURITY global 1977221
(SSFS) status on issues available and
consistent.
An inconsiste
secure store
result in seve
problems incl
SQL: the unability t
Inconsistent "HANA_Securi Startup start SAP HA
M1312 SECURITY global 2097613
secure store ty_SecureSto issues Make sure th
re" secure store
properly
configured to
avoid this kin
scenario.
Number of users SQL: Make sure th
Authenticati
M1330 SECURITY global with expiration "HANA_Securi 2159014 important use
on issues
date ty_Users" don't expire.
Make sure th
central datab
users with ma
Connection user SQL: connections (
Authenticati
M1331 SECURITY global with (password) "HANA_Securi 2159014 SAP schema
on issues
expiration ty_Users" neither user n
password
expiration is
configured.
Make sure th
SQL:
Certificates important
>= Rev. "HANA_Securi Authenticati
M1333 SECURITY with previous or 2159014 certificates
1.00.100 ty_Certifica on issues
upcoming expiry are renewed
tes"
time.
Number of SAP Make sure th
SQL:
users with Authenticati password of
M1335 SECURITY global "HANA_Securi 1702224
password on issues technical SAP
ty_Users"
expiration users don't ex
SQL: Assign the
Analysis
CATALOG READ "HANA_Securi CATALOG R
limitations,
M1340 SECURITY global privilege granted ty_GrantedRo 1640741 role to all use
performance
to current user lesAndPrivil required for S
overhead
eges" HANA monito

© 2019 SAP SE or an SAP affiliate company. All rights reserved 80 of 109

2019-08-27 1999993
and analysis.
Implement th
recommenda
ons for the SA
SQL:
Increased HANA audit lo
Size of audit log "HANA_Tables
M1360 SECURITY global memory 2388483 table
table (GB) _LargestTabl
requirements CS_AUDIT_L
es"
_ as describe
SAP Note
2388483.
A high numbe
of activated a
policies for D
statements lik
SELECT, INS
UPDATE or
DELETE can
responsible fo
increased SA
HANA chang
load, perform
issues,
POSTCOMM
INISH_SMP w
(SAP Note
1999930), ma
Performance threads worki
SQL:
regressions, module
Active DML audit "HANA_Securi
M1362 SECURITY global increased I/O 2159014 Auditing::CS
policies ty_AuditPoli
and commit TableAuditTr
cies"
load ailWriter::e
xecutePrepar
edStatement
or a growing
of the audit lo
table
CS_AUDIT_L
_. If you face
these sympto
you can doub
check
if you can find
good compro
between secu
requirements
and SAP HAN
overhead.
Make sure th
SQL:
license usage
"HANA_Licens License
M1410 LICENSE global License usage (%) 1704499 doesn't excee
e_LicenseUsa violation
100 % by
ge"
adjusting the
© 2019 SAP SE or an SAP affiliate company. All rights reserved 81 of 109
2019-08-27 1999993
licensing
conditions or
reconfigurin
g SAP HANA
the applicatio
Risk of
Extend the lic
license
SQL: before it expir
License expiration violation and
M1415 LICENSE global "HANA_Licens 1644792 Consider a
(days) system
e_Overview" permanent
unavailabili
license.
ty
Risk of
license Consider usin
SQL:
violation and permanent lic
M1420 LICENSE global Permanent license "HANA_Licens 1644792
system rather than a
e_Overview"
unavailabili temporary on
ty
Eliminate
bottlenecks
impacting the
communicatio
n between the
processes wi
one SAP HAN
node. Be awa
that lower val
are normal an
Avg. intra node SQL: expected in
Performance
M1510 NETWORK global send throughput "HANA_Networ 2222200 scenarios wh
degradations
(MB/s) k_Services" mainly very s
communicatio
n packages a
sent (with siz
byte to a few
In this case s
values are no
indication for
network /
communicatio
n issues.
Eliminate
bottlenecks
impacting the
communicatio
Avg. inter node SQL: n between the
Performance
M1512 NETWORK scale-out send throughput "HANA_Networ 2222200 processes of
degradations
(MB/s) k_Services" different SAP
HANA nodes
aware that low
values are no
and expected

© 2019 SAP SE or an SAP affiliate company. All rights reserved 82 of 109

2019-08-27 1999993
scenarios wh
mainly very s
communicatio
n packages a
sent (with siz
byte to a few
In this case s
values are no
indication for
network /
communicatio
n issues.
Check from
network
perspective if
SQL:
Retransmitte can reduce th
Rev. >= "HANA_Networ Performance
M1520 NETWORK d TCP segments 2222200 retransmissi
1.00.100 k_Statistics degradations
(%) on rate of TC
"
segments rela
to the SAP H
nodes.
Check from
network
SQL: perspective if
Rev. >= Bad TCP "HANA_Networ Performance can reduce th
M1522 NETWORK 2222200
1.00.100 segments (%) k_Statistics degradations number of ba
" TCP segmen
related to the
HANA nodes
Check from
network
SQL:
perspective if
"HANA_Networ
Rev. >= Current network Performance can reduce th
M1524 NETWORK k_Statistics 2222200
2.00.020 collision share (%) degradations number of
_CurrentDeta
collisions rela
ils"
to the SAP H
nodes.
Check from
network
SQL:
perspective if
"HANA_Networ
Rev. >= Current send error Performance can reduce th
M1525 NETWORK k_Statistics 2222200
2.00.020 share (%) degradations number of se
_CurrentDeta
errors related
ils"
the SAP HAN
nodes.
Check from
SQL:
network
"HANA_Networ
Rev. >= Current receive Performance perspective if
M1526 NETWORK k_Statistics 2222200
2.00.020 error share (%) degradations can reduce th
_CurrentDeta
number of rec
ils"
errors related

© 2019 SAP SE or an SAP affiliate company. All rights reserved 83 of 109

2019-08-27 1999993
the SAP HAN
nodes.
Check why a
particular high
amount of da
Avg. intra node SQL:
Performance transmitted
M1530 NETWORK global communicatio "HANA_Networ 2222200
degradations between serv
n volume (MB/s) k_Services"
of the same S
HANA node a
try to reduce
Check why a
particular high
amount of da
Avg. inter node SQL:
Performance transmitted
M1532 NETWORK scale-out communicatio "HANA_Networ 2222200
degradations between diffe
n volume (MB/s) k_Services"
SAP HANA s
out nodes an
to reduce it.
The internal S
HANA host n
resolution
(parameter se
internal_hos
tname_resolu
tion) is done w
mapping from
address
(parameter na
to host name
(parameter va
If the parame
SQL:
Host name name is no IP
"HANA_Config
M1540 NETWORK global resolution for non Terminations 2222200 address (e.g.
uration_Infr
IP addresses because you
astructure"
swapped the
and specify th
host name ra
than the IP
address), it d
work as expe
Make sure th
parameter na
in section
internal_hos
tname_resolu
tion are IP
addresses.
SQL: Check in whic
Network Poll
"HANA_Thread Performance context the
M1550 NETWORK global thread state share 2222200
s_ThreadSamp degradations network requ
(%, last day)
les_FilterAn are typically s

© 2019 SAP SE or an SAP affiliate company. All rights reserved 84 of 109

2019-08-27 1999993
dAggregation and optimize
" reduce it if
possible. For
example,
metadata
accesses or j
of partitioned
tables can res
a high amoun
network requ
Inadequate
network
parameters c
result in earlie
contention.
Check in whic
context the
network requ
are typically s
and optimize
reduce it if
possible. For
SQL:
example,
"HANA_Thread
Network Read metadata
s_ThreadSamp Performance
M1551 NETWORK global thread state share 2222200 accesses or j
les_FilterAn degradations
(%, last day) of partitioned
dAggregation
tables can res
"
a high amoun
network requ
Inadequate
network
parameters c
result in earlie
contention.
Check in whic
context the
network requ
are typically s
and optimize
reduce it if
SQL: possible. For
"HANA_Thread example,
Network Write
s_ThreadSamp Performance metadata
M1552 NETWORK global thread state share 2222200
les_FilterAn degradations accesses or j
(%, last day)
dAggregation of partitioned
" tables can res
a high amoun
network requ
Inadequate
network
parameters c
result in earlie

© 2019 SAP SE or an SAP affiliate company. All rights reserved 85 of 109

2019-08-27 1999993
contention.
Check if a hig
number of sm
logs is genera
SQL:
Log segment size Backup for the XS en
M1610 XS ENGINE global "HANA_Logs_L 2062080
of xsengine (MB) problems If yes, increas
ogBuffers"
log segment s
of the XS eng
to at least 64
The measure
ping times inc
the communic
n between
nameserver a
indexserver a
KPI collection
within the
SQL: indexserver.
Avg. load history
Rev. >= "HANA_LoadHi Performance Increased tim
M1710 NAMESERVER ping time (ms, last 2000000
1.00.90 story_Servic degradations can be a sym
hour)
es" of an underly
performance
issue. Check
general issue
impacting the
performance
resource
bottlenecks)
.
The measure
ping times inc
the communic
n between
nameserver a
indexserver a
KPI collection
within the
SQL: indexserver.
Avg. load history
Rev. >= "HANA_LoadHi Performance Increased tim
M1712 NAMESERVER ping time (ms, last 2000000
1.00.90 story_Servic degradations can be a sym
day)
es" of an underly
performance
issue. Check
general issue
impacting the
performance
resource
bottlenecks)
.
Rev. >= Supported SQL: Performance Make sure th
M1720 NAMESERVER 2100296
1.00.91 nameserver lock "HANA_TraceF degradations nameserver l

© 2019 SAP SE or an SAP affiliate company. All rights reserved 86 of 109

2019-08-27 1999993
file location iles_Content file is located
" supported file
system as de
in accessing
file can heavi
impact the
performance
SAP HANA.
Analyze the
related trace
in order to
SQL:
understand th
"HANA_Replic High
SYSTEM Services with reason for the
M1810 SR ation_System availability 1999880
REPLICATION replication error problems and
Replication_ limitations
make sure th
Status"
system replic
is again
established.
Analyze the
related trace
in order to
SQL:
understand th
Service with "HANA_Replic High
SYSTEM reason for the
M1811 SR unknown ation_System availability 1999880
REPLICATION problems and
replication state Replication_ limitations
make sure th
Status"
system replic
is again
established.
Check why th
connection to
secondary sy
SQL:
has been lost
Replication "HANA_Statis High
SYSTEM SR, Rev. >= (temporarily
M1813 connection closed ticsServer_A availability 1999880
REPLICATION 1.00.90 or permanent
(last day) lerts_Report limitations
and make sur
ed"
that it remain
connected
permanently.
Check if the
system replic
actually work
ships logs to
SQL: secondary sit
"HANA_Replic High a regular bas
SYSTEM Log position gap
M1814 SR ation_System availability 1999880 not, the secon
REPLICATION (MB)
Replication_ limitations site may be
KeyFigures" significantl
y outdated an
proper system
replication ne
to be re-estab

© 2019 SAP SE or an SAP affiliate company. All rights reserved 87 of 109

2019-08-27 1999993
ed.
Check for err
communicatio
SQL: High
n issues that
"HANA_Replic availability
SYSTEM Current log be responsibl
M1815 SR ation_System limitations, 1999880
REPLICATION shipping delay (s) the log shippi
Replication_ performance
delays and m
Status" degradations
sure that log
be shipped in
Check for err
communicatio
n issues that
be responsibl
the log shippi
delays and m
sure that log
SQL: High
be shipped in
Filling level of "HANA_Replic availability
SYSTEM If required,
M1816 SR async shipping ation_System limitations, 1999880
REPLICATION increase the
buffer (%) Replication_ performance
asynchronous
Status" degradations
log shipping
buffer: global
[system_repl
ication] ->
logshipping_
async_buffer
_size
Check for err
communicatio
n issues that
be responsibl
the log shippi
delays and m
sure that log
SQL: High
be shipped in
Async log "HANA_Replic availability
SYSTEM If required,
M1818 SR shipping buffer full ation_System limitations, 1999880
REPLICATION increase the
(last day) Replication_ peformance
asynchronous
KeyFigures" degradations
log shipping
buffer: global
[system_repl
ication] ->
logshipping_
async_buffer
_size
SQL: Make sure th
"HANA_Replic Risk of system replic
Parameter
SYSTEM ation_System problems environments
M1820 SR deviations primary 1999880
REPLICATION Replication_ during / after all relevant S
vs. secondary site
ParameterDev failover HANA param
iations" are maintaine

© 2019 SAP SE or an SAP affiliate company. All rights reserved 88 of 109

2019-08-27 1999993
consistently
on the primar
secondary sy
If parameters
to deviate, yo
maintain them
the exclusion
parameters a
global.ini ->
[inifile_che
cker]
Database
snapshots ca
increase the d
disk space
requirements
and so you sh
make sure th
system replic
related snaps
are not kept l
Increased
Age of oldest SQL: than necessa
SYSTEM data disk
M1830 SR replication "HANA_IO_Sna 1999880 The snapsho
REPLICATION space
snapshot (h) pshots" retention time
requirements
controlled by
following
parameter:
global.ini ->
[system_repl
ication] ->
datashipping
_snapshot_m
x_retention_
time
A particularly
long initial da
shipping time
restricts the
takeover
capabilities
because a
SQL:
takeover can
"HANA_Replic High
SYSTEM Max. initial data take place wh
M1835 SR ation_System availability 1999880
REPLICATION shipping time (h) initial data
Replication_ limitations
shipping is
Overview"
finished and t
system replic
sites are in sy
Check why in
data shipping
takes so long
eliminate

© 2019 SAP SE or an SAP affiliate company. All rights reserved 89 of 109

2019-08-27 1999993
bottlenecks, e
on network or
side.
In order to av
negative impa
the performan
on primary sy
replication sid
the average l
SQL:
buffer shippin
Avg. sync log "HANA_Replic
SYSTEM Performance time shouldn'
M1840 SR shipping time ation_System 1999880
REPLICATION regressions exceed a few
(ms/req, last hour) Replication_
seconds. If yo
KeyFigures"
face higher va
you should
analyze the
network betw
the primary a
secondary sid
In order to av
negative impa
the performan
on primary sy
replication sid
the average l
SQL:
buffer shippin
Avg. sync log "HANA_Replic
SYSTEM Performance time shouldn'
M1843 SR shipping time ation_System 1999880
REPLICATION regressions exceed a few
(ms/req, last day) Replication_
seconds. If yo
KeyFigures"
face higher va
you should
analyze the
network betw
the primary a
secondary sid
In order to av
negative impa
the performan
on primary sy
replication sid
the average l
SQL:
buffer shippin
Max. sync log "HANA_Replic
SYSTEM Performance time shouldn'
M1846 SR shipping time ation_System 1999880
REPLICATION regressions exceed a few
(ms/req, history) Replication_
seconds. If yo
KeyFigures"
face higher va
you should
analyze the
network betw
the primary a
secondary sid

© 2019 SAP SE or an SAP affiliate company. All rights reserved 90 of 109

2019-08-27 1999993
Due to variou
advantages it
recommende
use operation
mode logrepl
logreplay_re
SQL:
adaccess) ins
System replication "HANA_Replic Increased
SYSTEM of delta_data
M1850 SR op. mode ation_System takeover 1999880
REPLICATION ipping when S
logreplay used Replication_ times
HANA >=
Overview"
1.00.122.17 i
used and the
no good indiv
reasons to us
delta_datash
ipping.
Check why a
significant ba
exists for the
replay on
secondary sit
the system
replication
scenario. In c
SQL:
of tables /
"HANA_Replic
SYSTEM Current log replay HA partitions with
M1852 SR ation_System 2661878
REPLICATION backlog (GB) limitations high change l
Replication_
you can cons
KeyFigures"
to create mor
partitions (SA
Note 2044468
because log r
of a single tab
partition can't
parallelized
.
Check why a
significant ba
exists for the
replay on
secondary sit
the system
SQL:
replication
"HANA_Replic
SYSTEM Current log replay HA scenario. In c
M1853 SR ation_System 2661878
REPLICATION delay (s) limitations of tables /
Replication_
partitions with
KeyFigures"
high change l
you can cons
to create mor
partitions (SA
Note 2044468
because log r

© 2019 SAP SE or an SAP affiliate company. All rights reserved 91 of 109

2019-08-27 1999993
of a single tab
partition can't
parallelized
.
Check why a
significant ba
exists for the
replay on
secondary sit
the system
replication
scenario. In c
SQL:
of tables /
Max. log replay "HANA_Replic
SYSTEM HA partitions with
M1854 SR backlog (GB, last ation_System 2661878
REPLICATION limitations high change l
week) Replication_
you can cons
KeyFigures"
to create mor
partitions (SA
Note 2044468
because log r
of a single tab
partition can't
parallelized
.
Check why a
significant ba
exists for the
replay on
secondary sit
the system
replication
scenario. In c
SQL:
of tables /
Max. log replay "HANA_Replic
SYSTEM HA partitions with
M1855 SR delay (s, last ation_System 2661878
REPLICATION limitations high change l
week) Replication_
you can cons
KeyFigures"
to create mor
partitions (SA
Note 2044468
because log r
of a single tab
partition can't
parallelized
.
Activating log
retention
SQL:
(enable_log_
Datashipping "HANA_Config
SYSTEM Risk of retention = on
M1860 SR combined with log uration_Para 1999880
REPLICATION standstill combination w
retention meters_Value
the replication
s"
mode delta d
shipping
© 2019 SAP SE or an SAP affiliate company. All rights reserved 92 of 109
2019-08-27 1999993
(operation_m
ode =
delta_datash
ipping) doesn
make sense a
can result in
standstill situa
due to retaine
files. Don't se
enable_log_r
etention para
when delta da
shipping is us
as system
replication mo
It is not suppo
to mix operat
mode
delta_datash
ipping with a
logreplay
operation mo
SQL:
a 3-tier lands
Both delta_datash "HANA_Replic
SYSTEM Unsupported See SAP Not
M1861 SR ipping and ation_System 1999880
REPLICATION scenario 1999880 -> "I
logreplay used Replication_
possible to se
Overview"
a cascaded
replication
environment?
" and make s
that you use a
consistent
operation mo
If system
replication mo
delta_datash
ipping is used
long duration
the last shipp
savepoint can
SQL: impact the
System replication "HANA_Replic High takeover time
SYSTEM
M1865 SR savepoint delay ation_System availability 1999880 You can chec
REPLICATION
(h) Replication_ limitations following: If
Overview" system replic
is actually
configured wi
mode logrepl
no savepoints
shipped and a
huge delay is
harmless and

© 2019 SAP SE or an SAP affiliate company. All rights reserved 93 of 109

2019-08-27 1999993
be ignored. M
sure that the
parameters
global.ini ->
[system_repl
ication] ->
datashipping
_min_time_in
terval and
global.ini ->
[system_repl
ication] ->
datashipping
_logsize_thr
eshold aren't
configured wi
very large val
on the second
node. Otherw
will take a lon
time until a
savepoint shi
is triggered. C
the overall sy
replication sa
and the state
the secondar
Upgrade to S
08 Rev. >= 85
Rev. <= or Rev. >= 96
1.00.85.03, SQL: order to elimi
Maximum object Risk of
M1910 OBJECTS Rev. "HANA_Object 2155663 the risk of
ID terminations
1.00.90 - s_Overview" terminations
1.00.95 in case of larg
object IDs for
sequences.
Check for inv
procedures a
recompile the
ALTER
SQL:
PROCEDURE
Number of invalid "HANA_Object Risk of
M1920 OBJECTS global "<procedure>
procedures s_Procedures terminations
" RECOMPIL
"
recompilatio
n isn't possibl
consider adju
or dropping th
Avoid using
SQL:
Synonyms with synonym nam
"HANA_Synony Risk of
M1930 OBJECTS ABAP names identical to 2401716 that are ident
ms_Identical terminations
table name to table name
TableNames"
particularly
© 2019 SAP SE or an SAP affiliate company. All rights reserved 94 of 109
2019-08-27 1999993
in SAP ABAP
environments
- in order to a
problems like
AMDP issue
described in S
Note 2401716
Alternativel
y you can use
views with the
same name li
table.
In order to
guarantee op
performance
sequences w
limited overhe
is recommend
to activate ca
for the seque
e.g. with a siz
100: ALTER
SEQUENCE
"<sequence_
Risk of
SQL: ame>" CACH
Sequences with performance
"HANA_Config 100 Be aware
M1940 OBJECTS global insufficient regressions 2600095
uration_Sequ in case of a c
caching and
ences" there will be g
terminations
in the sequen
numbers, so
need to make
that this is ok
from applicati
perspective.
Sequences re
to ABAP table
DDLOG and
SLT triggers c
be cached wi
restriction.
Cross node
triggers are
triggers wher
triggering tab
SQL:
and the targe
"HANA_Config Risk of
Cross node tables are loc
M1945 OBJECTS global uration_Trig performance
triggers on different S
gers_CrossNo regressions
HANA nodes
deTriggers"
scale-out
environments
. This can res
unnecessary

© 2019 SAP SE or an SAP affiliate company. All rights reserved 95 of 109

2019-08-27 1999993
communicatio
n overhead a
you should ch
if moving all
involved table
the same nod
possible.
Check for freq
text indexing
errors and
eliminate the
cause. You c
use the follow
query to dete
indexing erro
a specific
<column> of
specific <tabl
SELECT
"<column>"
INDEXING_E
OR_CODE("<
SQL: lumn>")
Columns with "HANA_Indexe Reduced text ERROR_COD
M1950 OBJECTS global significant text s_TextIndexe analysis 2160391 INDEXING_E
indexing errors s_IndexingQu quality OR_MESSAG
eues" <column>")
ERROR_MES
E FROM "<ta
WHERE
INDEXING_E
OR_CODE("<
lumn>") != 0 S
SAP Note
2396942 for a
dedicated ind
issue (error 5
in IBM on Pow
environments
with SAP HAN
2.0 SPS 00 a
01.
Check if the
amount of qu
documents re
SQL:
high over time
Documents "HANA_Indexe Reduced text
even at times
M1952 OBJECTS global queued for fulltext s_TextIndexe analysis 2160391
rather low sys
indexing s_IndexingQu quality
load. If yes, y
eues"
have to check
possible
bottlenecks a

© 2019 SAP SE or an SAP affiliate company. All rights reserved 96 of 109

2019-08-27 1999993
issues in the
indexing
procedure.
Risk of
Make sure th
performance
Empty optimal table
overhead
BW, scale- TABLE_PLACEM placement an
M2010 BW due to 1908075
out ENT table in BW landscape
inadequate
scale-out redistributi
table
on is configur
placement
Avoid partitio
SQL:
of SID tables
"HANA_Tables Risk of locks
Partitioned SID order to rule o
M2020 BW BW _ColumnStore and hang 2044468
tables risks related t
_Partitioned situations
uniqueness
Tables"
checks.
Make sure fro
SQL: BW side that
SID tables > 1.5 "HANA_Tables Risk of SID number r
M2022 BW BW 1331403
billion rows _ColumnStore terminations in a single inf
_Records" object doesn'
exceed 2 billi
BW tables wi
I, J, K, P, Q, T
or Y immedia
after the seco
slash (e.g.
/BIC/P...) sho
be partitioned
unless really
SQL:
Risk of locks required, bec
Partitioned special "HANA_Tables
and partitioning
M2025 BW BW BW tables < 1.5 _ColumnStore 2044468
performance typically caus
bill. rows _Partitioned
regressions more trouble
Tables"
having benefi
there is a risk
the 2 billion re
limit is reache
partitioning
should
nevertheless
be considered
Take appropr
actions on BW
side to limit th
SQL:
Tables with high PARTNO par
"HANA_Tables
M2027 BW BW sub-partitio Terminations 2002607 numbers. The
_TablePartit
n PARTNO maximum
ions"
permitted valu
from BW side
9999 and you

© 2019 SAP SE or an SAP affiliate company. All rights reserved 97 of 109

2019-08-27 1999993
should have
sufficient
headroom to
the save side
Consider to u
least three no
SQL: in BW scale-o
BW scale-out Inefficient
BW, scale- "HANA_Config scenarios in o
M2030 BW installation table 1702409
out uration_Over to guarantee
on 2 nodes distribution
view" optimal table
distribution
.
Make sure th
SQL: temporary BW
Memory and
Temporary BW "HANA_Tables tables aren't k
M2040 BW BW administrati 2388483
tables _SpecialTabl for an
on overhead
es" unnecessary
time.
BW aggregat
are usually no
required in SA
HANA
environments
SQL:
. Check why s
BW aggregate "HANA_Tables Memory
M2042 BW BW 2388483 BW aggregat
tables _SpecialTabl overhead
tables (/<bw_
es"
>/E1%,
/<bw_prefix>
/F1%) exist a
purge them if
possible.
Remove old
SQL: temporary
Old temporary "HANA_Calcul calculation
Performance
M2044 BW BW calculation ationEngine_ 2593719 scenarios, e.g
regressions
scenarios CalculationS report
cenarios" RSDDTMPTA
ELETE.
Inverted hash
indexes aren'
BW tables with SQL: supported for
Risk of
M2050 BW BW inverted hash "HANA_Indexe 2109355 tables and ne
malfunctions
indexes s_Columns" be converted
inverted value
indexes.
SQL: Analyze the
Data
CHECK_TABLE_ "HANA_Consis reported erro
Rev. >= inconsistenc
M2110 CONSISTENCY CONSISTENCY tency_CheckT 1977584 and repair
1.00.100 ies and
errors (last month) ableConsiste corruptions if
terminations
ncy_Results" required.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 98 of 109

2019-08-27 1999993
Consider
scheduling a
regular
CHECK_TAB
CONSISTEN
SQL: Data
Last consistency run with the
Rev. >= "HANA_Statis inconsistenc
M2112 CONSISTENCY check via stat. 2116157 statistics serv
1.00.100 ticsServer_S ies and
server (days) Alternativel
chedule" terminations
y you can als
other schedu
tools like
transaction D
or cron.
Schedule a ta
consistency c
based on
CHECK_TAB
CONSISTEN
least once in
backup cycle
Make sure th
history of the
thread sampl
(SAP Note
SQL:
2114710) is k
"HANA_Thread Data
Last global table for at least 42
s_ThreadSamp inconsistenc
M2113 CONSISTENCY global consistency check 2116157 days, otherwi
les_FilterAn ies and
(days) information a
dAggregation terminations
previous
"
consistency c
runs may not
found, resultin
false positive
Also make su
that thread de
are properly
collected (SA
Note 2524020
avoid false
positives.
Schedule a ta
SQL: consistency c
Data
Tables without "HANA_Consis based on
Rev. >= inconsistenc
M2115 CONSISTENCY recent consistency tency_CheckT 2116157 CHECK_TAB
2.00.010 ies and
check ableConsiste CONSISTEN
terminations
ncy_Tables" least once in
backup cycle
SQL: Check the
Data
Tables with "HANA_Consis reported erro
Rev. >= inconsistenc
M2116 CONSISTENCY consistency check tency_CheckT 2116157 and repair ex
2.00.010 ies and
errors ableConsiste corruptions.
terminations
ncy_Tables" Make sure th
© 2019 SAP SE or an SAP affiliate company. All rights reserved 99 of 109
2019-08-27 1999993
CHECK_TAB
CONSISTEN
can be execu
without error.
Consider
upgrading to
more recent
SQL:
Rev. <= Large tables with Revision leve
"HANA_Tables Wrong
M2120 CONSISTENCY 1.00.102.03, risk of index 2264778 partitioning
_ColumnStore results
1.00.110 corruption the potentially
_Records"
impacted tabl
(SAP Note
2044468).
Make sure th
Inconsistenc Downtime
SQL: daemon and
ies between and
M2130 CONSISTENCY global "HANA_Servic 2222249 topology are
topology and erroneous
es_Overview" configured
daemon alerts
consistent.
The configure
number of sta
nodes must b
identical to th
actual numbe
standby node
Risk of there is a
Inconsistent SQL: various deviation, it n
node role "HANA_Hosts_ issues, e.g. to be correcte
M2135 CONSISTENCY scale-out
definition in LandscapeCon restore or e.g. by adjust
topology figuration" takeover the topology
problems information, in
order to rule o
unpredictabl
e issues. Ope
SAP incident
need assistan
from SAP sid
Open a SAP
incident on
SQL:
Inconsistenc component H
"HANA_Consis Risk of
M2140 CONSISTENCY global ies of metadata 2498587 DB in order to
tency_Object corruptions
and dependencies analyze and r
Dependency"
the inconsiste
y.
See SAP Not
1872652 and
SMART DATA SQL: Risk of
1926323 and
ACCESS / SDA tables "HANA_SmartD performance
M2210 global 2180119 create optimiz
SMART DATA without statistics ataAccess_Ta and resource
statistics on a
INTEGRATION bles" overhead
smart data ac
tables.
M2220 SMART DATA global SDI remote SQL: Risk of 2400022 Check why re
© 2019 SAP SE or an SAP affiliate company. All rights reserved 100 of 109
2019-08-27 1999993
ACCESS / subscription "HANA_SmartD terminations subscription
SMART DATA exceptions ataIntegrati s failed with e
INTEGRATION on_RemoteSub and eliminate
scriptionExc root cause.
eptions"
Check why
applying the S
remote
subscription
changes is
significantl
SQL: y behind and
SMART DATA "HANA_SmartD resolve errors
SDI max. remote
ACCESS / ataIntegrati Outdated bottlenecks.
M2222 glob subscription 2400022
SMART DATA on_RemoteSub data Particularly
apply delay (s)
INTEGRATION scriptionSta pay attention
tistics" the activities
indexserver
Request threa
method
DPServerReq
Applier (SAP
2114710).
Configure the
dpserver
processes ba
on the instruc
in the SAP HA
Risk of EIM Administ
SMART DATA various on Guide (“En
Slave nodes with SQL:
ACCESS / issues, e.g. the Data
M2230 scale-out dpserver "HANA_Servic 2391341
SMART DATA restore or Provisioning
processes es_Overview"
INTEGRATION takeover Server”) and
problems sure that no
dpserver
processes are
defined for SA
HANA slave
nodes.
Check why a
number of SA
HANA Studio
connections t
database exis
SQL: Risk of
check if you c
ADMINISTRATI SAP HANA Studio "HANA_Connec blocked
M2310 global 2073112 reduce them.
ON connections tions_Overvi garbage
Among others
ew" collection
can consider
following: Avo
using outdate
SAP HANA S
versions. Avo
© 2019 SAP SE or an SAP affiliate company. All rights reserved 101 of 109
2019-08-27 1999993
adjusting time
settings. Man
terminate old
no longer nee
connections.
Make sure th
you use a
sufficiently
SQL:
Connections with Risk of new SAP HA
ADMINISTRATI "HANA_Connec
M2315 global old SAP HANA instabilitie 2073112 Studio Revisi
ON tions_Overvi
Studio versions s that should at
ew"
match the SP
level of SAP
HANA.
The hdbcons
isn't officially
supported by
and so it shou
used with car
SQL:
only in situati
"HANA_Thread
Time since last Risk of where it is rea
ADMINISTRATI s_ThreadSamp
M2320 global hdbcons instabilitie 2222218 required. Che
ON les_FilterAn
execution (h) s for what purp
dAggregation
hdbcons was
"
called and av
calling hdbco
too frequently
(unless instru
by SAP supp
Check for wh
purpose
parameters a
on host level
check if it is
possible to de
parameters
SQL:
globally to sim
"HANA_Config
ADMINISTRATI Parameters set on Increased application
M2330 global uration_Para 2186744
ON host level complexity complexity. F
meters_Value
example, hos
s"
specific
parameters a
automaticall
y taken over i
case of host a
failove
r.
Parameter SQL: Outdated If parameters
ADMINISTRATI Rev. >= changes requiring "HANA_Config configuratio modified that
M2332 2186744
ON 2.00.040 a SAP HANA uration_Para n settings require a SAP
restart meters_Value used HANA restart

© 2019 SAP SE or an SAP affiliate company. All rights reserved 102 of 109
2019-08-27 1999993
s" take effect, yo
may be in a
situation that
parameter va
displays a sta
the is actually
active. This c
result in
misinterpret
ations and
unexpected
behavior of th
SAP HANA
database.
Consider this
scenario and
restart SAP H
when possibl
make sure th
new setting ta
effect.
Make sure th
section and
parameter na
are spelled
correctly, that
parameter va
matches to th
intended data
and that the
parameter va
within the
accepted ran
the paramete
SQL: raised althoug
"HANA_Config details are
ADMINISTRATI Rev. >= Parameters with
M2334 uration_Para Various 2186744 properly
ON 2.00.040 unsupported value
meters_Value considered, it
s" be caused by
missing entry
view
CONFIGURA
N_PARAMET
PROPERTIE
this case you
open a SAP
incident on
component H
DB in order to
request the
parameter to
added into th

© 2019 SAP SE or an SAP affiliate company. All rights reserved 103 of 109
2019-08-27 1999993
view.
Check which
deprecated
SQL: features you
Deprecated Risk of
ADMINISTRATI "HANA_Featur use and cons
M2340 global features used (last unforeseen 2425002
ON es_FeatureUs to use a differ
30 days) issues
age" current appro
for the same
purpose.
Check if table
SQL: Risk of
replicas are
"HANA_Replic terminations
TABLE Rev. >= Inactive table disabled
M2410 ation_TableR , 2340450
REPLICATION 1.00.120 replicas unintentiona
eplication_R performance
lly and activa
eplicas" regressions
them.
Check for the
reasons of
Last table SQL: automatic tab
Rev. >=
TABLE replication "HANA_TraceF Performance replication
M2415 1.00.122.17, 2400007
REPLICATION deactivation iles_Overvie overhead deactivation
>= 2.00.2
dump (days) w" and resolve
underlying iss
if required.
SQL: Overhead in
Drop sequenc
Orphan SLT "HANA_SLT_Or sequence
M2510 SLT global 2600095 no longer req
sequences phanSequence administrati
in context of S
s" on
With SAP HA
>= 2.0 the
previously cre
calculated ES
columns start
SQL:
Increased with '$esh:ca'
ENTERPRISE Rev. >= Orphan calculated "HANA_Tables
M2610 memory 2685716 no longer req
SEARCH 2.00.000 ESH columns _ColumnStore
consumption and can be
_Columns"
dropped usin
report
ESH_HDB_R
T_CALC_ATT
BUTES.

Products

SAP HANA, platform edition all versions

© 2019 SAP SE or an SAP affiliate company. All rights reserved 104 of 109
2019-08-27 1999993

This document refers to

SAP
Title
Note/KBA

2797078 How to configure the size of the HANA Backup files backup.log and backint.log

2779331 HANA services use large SWAP memory

2700051 Delivery of Statement Hints (SAP HANA >= 1.00.122.03)

2600095 FAQ: SAP HANA Sequences

2600030 Parameter Recommendations in SAP HANA Environments

2593893 How to delete HANA temporary tables

2555398 Erroneous System CPU Calculation

2524020 Last global table consistency check (days) shows Never

2502256 FAQ: SAP HANA Caches

2470289 FAQ: SAP HANA Non-Uniform Memory Access (NUMA)

2445867 How-To: Interpreting and Resolving SAP HANA Alerts

2400022 FAQ: SAP HANA Smart Data Integration (SDI)

2400007 FAQ: SAP HANA Runtime Dumps

2400006 FAQ: SAP HANA Statement Hints

2399993 FAQ: SAP HANA Fast Data Access (FDA)

2399990 How-To: Analyzing ABAP Short Dumps in SAP HANA Environments

2391341 HANA DB DPSERVER will not start after recovery

2388483 How-To: Data Management for Technical Tables

2380176 FAQ: SAP HANA Database Trace

2340450 FAQ: SAP HANA Table Replication

2222277 FAQ: SAP HANA Column Store and Row Store

2222276 How-To: Activating SAP HANA Memory Fencing

2222250 FAQ: SAP HANA Workload Management

2222249 How-To: Resolving SAP HANA Service Inconsistencies between Daemon and Topology

2222218 FAQ: SAP HANA Database Server Management Console (hdbcons)

© 2019 SAP SE or an SAP affiliate company. All rights reserved 105 of 109
2019-08-27 1999993
2222200 FAQ: SAP HANA Network

2222110 FAQ: SAP HANA Load History

2220627 FAQ: SAP HANA LOBs

2215131 Alert Log Switch Wait Count Ratio

2200772 FAQ: SAP HANA Statement Routing and Client Distribution Mode

2186744 FAQ: SAP HANA Parameters

2180165 FAQ: SAP HANA Expensive Statements Trace

2180119 FAQ: SAP HANA Smart Data Access

2177604 FAQ: SAP HANA Technical Performance Optimization Service

2177064 FAQ: SAP HANA Service Restarts and Crashes

2169283 FAQ: SAP HANA Garbage Collection

2160391 FAQ: SAP HANA Indexes

2159014 FAQ: SAP HANA Security

2154870 How-To: Understanding and defining SAP HANA Limitations

2147247 FAQ: SAP HANA Statistics Server

2143679 How-To: Removing Primary Keys of SAP HANA Statistics Server Histories

Analyzing problems with delivery of e-mails for Alerts raised by the SAP HANA Embedded
2133799
Statisticsserver checks

2127458 FAQ: SAP HANA Loads and Unloads

2124112 FAQ: SAP HANA Parsing

2119087 How-To: Configuring SAP HANA Traces

2116157 FAQ: SAP HANA Consistency Checks and Corruptions

2114710 FAQ: SAP HANA Threads and Thread Samples

2113228 SAP HANA: Embedded statistics server is not correctly purging

2112604 FAQ: SAP HANA Compression

2109355 How-To: Configuring SAP HANA Inverted Hash Indexes

2101244 FAQ: SAP HANA Multitenant Database Containers (MDC)

2100040 FAQ: SAP HANA CPU

2100009 FAQ: SAP HANA Savepoints

2092196 How-To: Terminating Sessions in SAP HANA

© 2019 SAP SE or an SAP affiliate company. All rights reserved 106 of 109
2019-08-27 1999993
2084747 How-To: Disabling Memory-intensive Data Collections of standalone SAP HANA Statistics Server

2081857 Handle HANA Alert 63: Granting of SAP_INTERNAL_HANA_SUPPORT role

2081591 FAQ: SAP HANA Table Distribution

2081065 Troubleshooting SAP HANA Network

2073112 FAQ: SAP HANA Studio

2057046 FAQ: SAP HANA Delta Merges

2050579 How to handle HANA Alert 68: 'total memory usage of row store'

2044468 FAQ: SAP HANA Partitioning

2031647 How to enable SQL Trace in SAP HANA Studio

2000003 FAQ: SAP HANA

2000002 FAQ: SAP HANA SQL Optimization

2000000 FAQ: SAP HANA Performance Optimization

1999998 FAQ: SAP HANA Lock Analysis

1999997 FAQ: SAP HANA Memory

1999930 FAQ: SAP HANA I/O Analysis

1999880 FAQ: SAP HANA System Replication

1994962 How-To: Activation of Hybrid LOBs in SAP HANA

1986747 How-To: Analyzing internal Columns in SAP HANA Column Store

1977314 How to handle HANA Alert 29: 'Size of delta storage of column-store tables'

1977242 How to handle HANA Alert 53: 'Pagedump files'

1977221 How to handle HANA Alert 57: 'Secure store file system (SSFS) availability'

1977218 How to handle HANA Alert 52 'Check for new crash dump files'

1977207 How to handle HANA Alert 55: Columnstore unloads

1977162 How to handle HANA Alert 50: 'Number of Diagnosis files'

1977101 How to handle HANA Alert 12: 'Memory usage of name server'

1921694 Docid overflow in current delta and main due to 2 billion limitation

1910159 How to handle HANA Alert 25: ‘Check number of connections’

1909742 How to handle HANA Alert 19: ‘Record Count of Delta Storage of Column-Store Tables'

1870858 HANA Alerts related to file system utilization

© 2019 SAP SE or an SAP affiliate company. All rights reserved 107 of 109
2019-08-27 1999993
2812427 Timeout or connection failure in SAP process after Linux kernel update

2803904 Overview Tab of Administration Console in HANA Studio Cannot be Displayed

2711824 High Number of Prepared Statements Causing High Usage of Memory Allocator Pool/Statistics

2711650 SAP HANA on Intel server systems with more than 8 CPU´s / sockets

2685716 Cleanup report for deletion of calculated attributes that are no longer required on SAP HANA

2661878 HANA System Replication log replay setting recommendations for large systems

2661792 Incorrect Swap Memory

2633077 Rowstore LOB Garbage is not Collected and the Number of Disk LOBs Keeps Increasing

2617548 Upgrade Recommendation for SAP HANA 1.0 Installations

2593719 Many left-over Calculation Scenarios on HANA (named xxx:0BW:BIA:BI0_0Q<nnnnnnnn>__CS)

2498587 Inconsistency Warning Between Metadata and OBJECT_DEPENDENCIES Table

2445363 How to delete the temporary table after HANA BPC enabled

2436619 Inconsistency After Repartitioning a Table Using Inverted Hash Indexes

2425002 SAP HANA 2.0: Deprecations reported by the HANA statistics server

2399995 Hardware requirement for SAP HANA 2.0

2382421 Optimizing the Network Configuration on HANA- and OS-Level

Increased Used Memory Size due to Pool/PersistenceManager/PersistentSpace/DefaultLPA

2301382
/Page (Rev. 110 - 122.05)

2240716 SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP4

2235581 SAP HANA: Supported Operating Systems

2214569 Poor DTP performance caused by reaching max count of no logging tables

2205917 SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12

2097613 Database is running with inconsistent Secure Storage File System (SSFS)

2002607 730SP12: Maximum partition '9999' reached in PSA/changelog table

1980196 Setting Linux Kernel Parameter /proc/sys/vm/max_map_count on SAP HANA Systems

1868829 Startup Issues Because Number of Active I/O Requests to Queue Exceeds aio-max-nr Limit

1771258 Linux: User and system resource limits

1642148 FAQ: SAP HANA Database Backup & Recovery

SAP hardware directory

Create Custom Metrics for HANA Monitoring

© 2019 SAP SE or an SAP affiliate company. All rights reserved 108 of 109
2019-08-27 1999993
github HANAChecker

© 2019 SAP SE or an SAP affiliate company. All rights reserved 109 of 109