SAP Knowledge Base Article

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

Component: HAN-DB (SAP HANA > SAP HANA Database), Version: 111, Released On: 09.06.2024

Symptom
You are interested in details how to use the SAP HANA database console tool hdbcons.

Environment
SAP HANA

Cause
1. What is the SAP HANA database server management console?
2. Which indications exist for hdbcons issues?
3. In which contexts is hdbcons particularly useful?
4. How can hdbcons be started?
5. Where do I find an overview about available hdbcons functionalities?
6. What are the most important hdbcons functionalities?
7. How can I configure automatic executions of hdbcons commands during startup?
8. What has to be considered when using hdbcons in multitenant environments?
9. What happens in case of a hdbcons crash?
10. What are typical errors related to hdbcons?
11. How can SAP HANA threads related to hdbcons activities be identified?
12. How can I find out when hdbcons was called?

Resolution

1. What is the SAP HANA database server management console?

The SAP HANA database server management console (hdbcons) is an expert tool delivered as part of the SAP HANA software.
In normal cases it is not required to use it, but in some scenarios you can take advantage of its functionalities.
As improper usage of hdbcons can have a severe impact on SAP HANA, you should only run it under guidance of SAP (e.g. if
recommended in a SAP case or SAP Note).
Be aware that both the available commands and the structure of the hdbcons output can change between SAP HANA
Revisions without further notice.

2. Which indications exist for hdbcons issues?

SQL: "HANA_Configuration_MiniChecks" (SAP Notes 1969700, 1999993) returns a potentially critical issue (C = 'X') for one
of the following individual checks:

Check ID Details

M2320 Time since last hdbcons execution (h)

SQL: "HANA_TraceFiles_MiniChecks" (SAP Note 2380176) reports one of the following check IDs:

Check ID Details

T2300 Transactions terminated with hdbcons

T2301 Connections terminated with hdbcons

3. In which contexts is hdbcons particularly useful?
Hdbcons is most helpful in scenarios like:
Retrieving data from secondary system replication sides if they can't be accessed via SQL (SAP Note 1999880)
Retrieving data from a hanging SAP HANA instance that is no longer accessible via SQL (SAP Note 1999020)
Advanced memory tracing and analysis (SAP Note 1999997)
Execution of functionalities not implemented via SQL (e.g. acknowledgement of internal SAP HANA events as described
in SAP Note 2147247 or resetting the SSFS consistency as described in SAP Note 2097613)

4. How can hdbcons be started?

The following alternatives exist to start hdbcons:

Tool Details

Direct call On Linux level you can start hdbcons via:

(Linux leve
l) hdbcons [-p <pid>] [-e <process_name>]

Per default hdbcons will connect to the indexserver process, but you can specify the process ID of another SAP HANA p
rocess via "-p <pid>" or the name of another SAP HANA process via "-e <process_name>" (e.g. <process_name> = 'hd
bnameserver').

Starting with SAP HANA 2.0 SPS 06 calling hdbcons without any additional option will fail to connect to the indexserve
r in case the tenant name is different from the database system ID and the following error is returned (issue number 28
8374):

Try to open connection to server process 'hdbindexserver' on system '<db_system_id>', instance '<inst_
id>' and tenant '<db_system_id>'
exception 1: no.2050100 (Basis/System/SystemCall.hpp:558) TID: <tid> System call failed [generic:111]:
Connection refused

This is an intended behavior change. You can now use the new "-d" option to provide the proper tenant database name:

hdbcons -d <tenant_db_name>

SAP HANA Per default the database console isn't displayed, but you can change it via:
Studio
Window
-> Preference
-> SAP HANA
-> Global Settings
-> Show Management Console for hdbcons

Subsequently you will find an hdbcons input section at:

Systems
-> Administration
-> Console
Attention: In multitenant environments (SAP Note 2101244) hdbcons should exclusive be used from the system datab
ase, so the Console tab will not be displayed for tenant connections.
 SQL You can start certain hdbcons commands via SQL using:

CALL MANAGEMENT_CONSOLE_PROC('<hdbcons_command>', '<host>:<port>', ?)

<hdbcons_command> is a hdbcons command, e.g. the ones listed in "What are the most important hdbcons functionali
ties" below.

The possibility to use this procedure can be controlled with the following SAP HANA parameter (default: true, SAP Not
e 2893892):

global.ini -> [customizable_functionalities] -> builtinprocedure.manage​

ment_console_proc = true | fals
e

If a certain command isn't supported on SQL level, the following error is returned:

[ERROR] exception during command processing: exception 2120012: External command savepoint not availab
le in sql

Implicitly In the following contexts hdbcons is called implicitly by SAP HANA:

Selection from monitoring view M_SERVICE_THREAD_CALLSTACKS:

Implicitly triggers hdbcons with 'context l -s -f -n -p' to generate callstacks
Starting with SAP HANA 2.0 SPS 04 the statistics server (SAP Note 2147247) persists this monitoring view e
very five minutes, so it is normal that the underlying hdbcons call is executed every five minutes

5. Where do I find an overview about available hdbcons functionalities?

The following commands can be used in hdbcons to display an overview of hdbcons functionalities:

Command Details

hdbcons help Overview of available server related options

hdbcons help <command>

hdbcons -? Overview of available client related options

6. What are the most important hdbcons functionalities?

The following table provides an overview about some hdbcons functionalities. Several of the 'mm' calls can be extended by the
'-r' switch so that they apply also to sub-allocators of the specified heap allocator <allocator>.

Command SA Details
PN
ote

Overview of internal commands (like '\<')

\?

\< <file_name>
Read commands from file <file_name>

\> <file_name>
Write output to file <file_name>

209 Cancellation of connection with connection ID <conn_id>

connection c <conn_id>
219
The following kind of message is printed in the SAP HANA database trace (SAP Note 238
6
0176):

(connection external command) Cancel connection <conn_id>

(connection external command) Successfully cancelled connection <conn_id>
connection d <conn_id>
209 Disconnect of connection with connection ID <conn_id>
219
The following kind of message is printed in the SAP HANA database trace (SAP Note 238
6
0176):

(connection external command) Disconnect connection <conn_id>

(connection external command) Successfully disconnected connection <conn_id
>

231 Generate call stacks for active threads

context l -s [-f]
361
The optional "-f" option can be used to generate call stacks also for inactive threads.
9

209 Reset SSFS cache / consistency

crypto ssfs resetCache
crypto ssfs resetConsistency 761
3
281
462
3

199 Creation of a deadlock graph related to internal SAP HANA locks

deadlockdetector wg -w -o <p
ath_and_file>.dot 902
The generated file can be transformed into a PDF using a command like:
0
dot -Gsize="30,30" -Tpdf -o <path_and_file>.pdf <path_and_file>.dot

Attention: Only a subset of internal deadlocks is recognized, semaphore waits are for ex
ample not considered

distribute e <host>:<port> <

214 Execute hdbcons command <command> on remote host / service identified via <host>:
command> 698 <port>
4
Attention: Remote executions are based on TREXNet and may fail with connection erro
241
rs at times of issues (e.g. lack of JobWorkers), e.g.:
014
3 An error occurred while opening the channel; $INFO$=internal error; $PARAM$
=127.0.0.1:30240

Direct connections with hdbcons may be able to succeed at the same time. Thus, try to ru
n critical analysis commands like the generation of runtime dumps with a direct hdbcons
access to the processes whenever possible.

297 This option exists with SAP HANA >= 2.00.048.02 and >= 2.00.053 and can be used to
dvol sbtouch -n <blocks>
356 mark the last <blocks> data volume superblocks per size class (4 KB, 16 KB, ...) dirty. Thi
0 s can improve the result of data volume reclaim operations.

187 Execution of data file defragmentation comparable to ALTER SYSTEM RECLAIM DATA
dvol shrink -o <overhead_pct
> 085 VOLUME <overhead_pct>
8
A standard value of 120 is suggested for <overhead_pct>, only useful if space will remain
on a lower level permanently, preferably to be executed at times of lower system load

Must not be executed on secondary system replication sites (SAP Note 1999880)

239 Display persistence encryption status

encryption status
643
8

214 Acknowledge internal events of type <type>

event acknowledge -t <type>
724
7
help <command>
Provide further details for a specific hdbcons command <command> (e.g. 'mm')

199 As of SAP HANA SPS 12 you can use this command to display the current state of index h
indexmanager list [-f <table
>] 999 andle locks. With the "-f" option you can restrict the output to a specific table name.
8

indexmanager waitgraph -w
199 Starting with SAP HANA SPS 12 you can use this command to determine dependencies f
999 or the index handle lock. This simplifies the identification of the activity responsible for t
8 he locking. The output is a ".dot" file that can be transformed into a PDF file using a com
mand like:

dot -Tpdf -o <path_and_file>.pdf <path_and_file>.dot

210 Information about available CPUs (incl. sockets) and available SAP HANA concurrency
jexec info
004
0

jexec loginfo
2119 Current state of activated job execution log
087

jexec logprint <file_name>.j

2119 Dump of job execution log to <file_name>.jexlog
exlog 087

2119 Activation of a job execution log, a good starting point for <events_in_million> can be 3
jexec logstart -c <events_in
_million> 087 0

2119 Deactivation of a job execution log

jexec logstop
087

log backup
210 Force log backup
624
0

199 Release free log segments

log release
541
2
278
193
3

199 List the top contributors to the memory allocation of a specific heap allocator <allocator>
mm bl -t <allocator>
999
Only available for Pool allocators (name starting with "Pool/")
7
Attention: Crashes possible with SAP HANA <= 1.00.122.15, <= 2.00.012.04 and <= 2.
00.023 (SAP Note 2599979)

178 Generate output file with allocation stack trace information for heap allocator <allocator
mm cg -o <path_and_file>.dot
<allocator> 691 >
8
Only available for Pool allocators (name starting with "Pool/")
199
999 Attention: Crashes possible with SAP HANA <= 1.00.122.15, <= 2.00.012.04 and <= 2.
7 00.023 (SAP Note 2599979)
 178 Activation / deactivation (-d) of allocator call stack trace for <allocator>
mm f <allocator> as
mm f <allocator> as -d 691
Only available for Pool allocators (name starting with "Pool/")
8
199 Memory being allocated and also deallocated during the trace isn't covered, only allocatio
999 ns without subsequent deallocations are considered.
7

222 Activation of memory fencing for <allocator>

mm f <allocator> ffence,bfen
ce,areset,dreset 227
6

222 Deactivation of memory fencing for <allocator>

mm f <allocator> -d ffence,b
fence,areset,dreset' 227
6

199 Return free memory to the operating system ('-f' to consider also free fragments in big bl
mm gc [-f]
999 ocks)
7
Can cause significant performance issues and follow-up problems, so should only be used
if requested by SAP support

See SAP Note 1999997 ("How can I trigger a memory garbage collection?") for further de
tails.

199 Information related to inter process memory management including:

mm ipmm -d
999
Current memory information for SAP HANA services
7
IPMM flight recorder including self compaction activities

178 Print general heap allocator list with some statistics ('-s'), sorted by total size descending
mm l -s -S -p
691 (-S) and peak usage statistics (-p)
8

199 Details for memory management structures, useful to analyze the content of heap allocat
mm level2map (SAP HANA 1.00)
mm pagetable (SAP HANA >= 2. 999 or AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks
00) 7

247 Physical memory allocations per NUMA node

mm numa -p
028
9

247 NUMA topology information

mm numa -t
028
9

247 Virtual memory allocations per NUMA node

mm numa -v
028
9

199 Print information about SAP HANA heap memory fragmentation

mm poolallocator
999
7

199 Reset all previous memory measurements ("reset usage")

mm ru
999
7
mm top -l <num> <allocator>
199 Generate report with top <num> call stacks recorded for heap allocator <allocator>
999
Attention: Crashes possible with SAP HANA <= 1.00.122.15, <= 2.00.012.04 and <= 2.
7
00.023 (SAP Note 2599979)

253 Print content of monitor view <monitor_view_name> ('-h' is required for printing colum
monitor print -h -n <monitor
_view_name> 247 n names)
5
"monitor" is more complex than "statreg" (e.g. due to timestamp conversions)

msl check -c <container_id>

291 Check of packed LOB persistence containers, e.g. useful to purge orphan containers; <co
000 ntainer_id> needs to be specified as hex value
4
See SAP Note 2220627 for LOBs and SAP Note 2400005 for persistence details.

247 NUMA statistics of specific table (use <part_id> = 0 in case of non-partitioned table)
numa locate <schema> <table>
<part_id> 028
9

245 List valid output directories

output l

212
3

199 Provide information about SAP HANA pages currently loaded in memory
pageaccess a [ext] [d]
999
Optional parameters:
7
ext: Extended output
d: Consider all pages on disk, not only the ones loaded into memory; Attention: ve
ry high runtime because pages have to be loaded from disk for inspection

Attention: Crashes possible with SAP HANA <= 1.00.122.15 (SAP Note 2616088)

237 Make sure that all row store pages are written to persistence when next savepoint is exec
pageaccess touch row
016 uted (SAP HANA >= 1.0 SPS 12)
0

257 Touch an individual memory page (SAP HANA >= 1.0 SPS 12) so that the next savepoint
pageaccess touch <hex_pageno
> 731 flushes it to disk, not limited to row store tables
4

280 Reset kernel profiler trace

profiler clear
003
0

profiler print -o <path_and_

280 Generate a kernel profiler trace output file
file>.dot 003
0

280 Start a kernel profiler trace, different filter options are available:
profiler start [--cs <db_use
r>] [--ca <app_user>] [--cc 003
--cs <db_user>: Database user name
<conn_id>] [--ch <statement_ 0
--ca <app_user>: Application user name
hash>] --cc <conn_id>: Connection ID (SAP HANA >= 2.00.020)
--ch <statement_hash>: Statement hash (SAP HANA >= 2.00.030)

profiler stop
280 Stop a kernel profiler trace
003
0
 199 List of existing read write locks including unused ones that aren't reported via M_READ
readwritelock l
999 WRITELOCKS
7
Attention: Output can be huge (several GB).

206 Overview of system replication information

replication i
365
7
208
602
4

199 System replication establishment

replication start
988
0

199 Resource manager / resource container overview information

resman i
999
7

197 Overwrite inadequate unload_lower_bound settings during recovery

resman minswappable -s 0
053
7

214 Shrink resource container to <size_gb> GB if possible

resman s -s <size_gb>G
698
9

199 Unload of all swappable resources of type <resource>

resman unload-all <resource>
999
See M_MEMORY_OBJECTS.TYPE for <resource> values
8

240 Generate a runtime dump

runtimedump dump [-c] [-f <f
ile_name>] [-i] [-s <section 000
1>,...,<sectionN>] 7
1813
020

240 List available runtime dump section

runtimedump l
000
7

savepoint execute
222 Trigger a savepoint
8171
237
016
0

199 Analyze SAP HANA snapshot (<snapshot_id> can be retrieved via "snapshot l")
snapshot a <snapshot_id>
988
0

199 Delete SAP HANA snapshot (<snapshot_id> can be retrieved via "snapshot l")
snapshot d <snapshot_id>
988
0
210
000
9
 199 List SAP HANA snapshots
snapshot l
988
0

265 Complete online re-initialization of statistics server (SAP Note 2147247)

statisticsservercontroller i
nit 8611

240 List available statistics / monitoring views (to be printed via "statreg print" or as part of t
statreg list
000 he [STATISTICS] section of runtime dumps)
7

200 Print content of monitor view <monitor_view_name> ('-h' is required for printing colum
statreg print -h -n <monitor
_view_name> 000 n names)
0
"statreg" is more lightweight than "monitor" and provides raw statistical data

Attention: This command can result in a service crash with SAP HANA 2.00.040 - 20.0
0.042 (SAP Note 2845208).

statreg print --all -h -n M_

199 Print conditional variable information including inactive locks that aren't part of M_CO
CONDITIONAL_VARIABLES 999 NDITIONAL_VARIABLES or M_CONDITIONAL_VARIABLES_
7

222 Print mutex information including inactive mutexes that aren't part of M_MUTEXES or
statreg print --all -h -n M_
MUTEXES 2110 M_MUTEXES_

200 Reset a monitoring view (comparable with "ALTER SYSTEM RESET MONITORING VIE
statreg reset -n <monitor_vi
ew_name>_RESET 000 W <monitor_view_name>_RESET")
0

212 Print column preload information ('-f' for full information)

tablepreload c [-f]
745
8

188 Persist preload information based on columns currently loaded in memory ('-s' for synch
tablepreload w [-s]
908 ronous write)
1
210
795
9
212
745
8

209 Termination of a single transaction <transaction_id> or all transactions

transaction c <transaction_i
d> 219
Attention: Be aware that strictly speaking not the transactions themselves are cancelled
transaction c -a 6
. Instead only active operations within transactions are cancelled. So an active transactio
n without a currently active operation is left untouched.

The following kind of message is printed in the SAP HANA database trace (SAP Note 238
0176):

(transaction external command) Cancel transaction <transaction_id>

(transaction external command) Successfully cancelled <transaction_id>
(transaction external command) Successfully cancelled <transactions> transa
ction(s)
 234 Clear inactive table replication transactions (SAP HANA >= 2.00.053)
transaction clear_inactive_r
eplication 045
0

209 Forced deactivation of a trans token (SAP HANA <= 2.0 SPS 03, M_TRANSTOKEN_DI
transaction d <trans_token>
(SAP HANA <= 2.0 SPS 03) 219 RECTORY_.TRANS_TOKEN_ID) or consistent view including related trans token (SAP
6 HANA >= 2.0 SPS 04, M_CONSISTENT_VIEW_STATISTICS_.ID)
transaction d <consistent_vi
Attention: Can result in instabilities in case a still required trans token is deactivated
ew> (SAP HANA >= 2.0 SPS 04)
Attention: Can result in indexserver crashes with SAP HANA <= 2.0 SPS 03 (SAP Note
2858546)

199 List of top virtual files on persistence level

vf t
999
7

7. How can I configure automatic executions of hdbcons commands during startup?
For some reasons it can be useful to execute hdbcons commands as initial part of the SAP HANA startup, e.g. in order to
activate specific traces. This can be achieved with the following SAP HANA parameter setting:

daemon.ini -> [daemon] -> environment = 'HDB_INITIAL_COMMAND=<hdbcons_command>'

Example: (activation of allocation stack trace for Pool/malloc/libhdbcstypes.so)

ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini','SYSTEM') SET ('daemon', 'environment') =

'HDB_INITIAL_COMMAND=mm f Pool/malloc/libhdbcstypes.so as' WITH RECONFIGURE

Be aware that special characters like commata have to be quoted with a backslash.
Example: (activation of memory fencing, SAP Note 2222276)

ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini','SYSTEM') SET ('daemon', 'environment') =

'HDB_INITIAL_COMMAND=mm f Pool -rs ffence\,bfence\,areset\,dreset' WITH RECONFIGURE

8. What has to be considered when using hdbcons in multitenant environments?

The execution of hdbcons commands in tenants of a multitenant environment (SAP Note 2101244) should usually be
performed via the system database. You can use the "distribute e" command for that purpose. See SAP Note 2410143 for more
information.

9. What happens in case of a hdbcons crash?

When hdbcons crashes, a specific crash dump file with the following naming convention is created that contains further crash
details:

cons.crashdump.<timestamp>.trc

See SAP Note 2177064 for more information related to SAP HANA crashes.

10. What are typical errors related to hdbcons?

Important errors related to hdbcons are:

Error Details
 Calling hdbcons with is terminated with this error in the following scenarios:
Could not open connecti
on to server process A non-existing process ID is specified with the "-p <pid>" option
Non "-p <pid>" is used and the indexserver can't be contacted via socket

The second scenario typically happens when (at least temporarily) two indexserver processes were st
arted on the same node. In this case the following messages are printed to the database trace (SAP N
ote 2380176) of the indexservers that were started while another indexserver was already running:

Unable to create socket for name: hdbindexserver_S<sid>_I<inst_id>_ExternalCommandHan

dle
Application for this process will only work with 'hdbcons -p <pid>'

As a workaround you have to call hdbcons with the explicit “-p <pid>” option. After a stop of SAP HA
NA and a restart of a single indexserver process this problem scenario is fixed.

For security reasons hdbcons is only allowed to write to specific directories, e.g. /tmp or the SAP HA
[ERROR] Write access fo
r file with name '<path NA trace directories. In case of other destinations this error message is written. You can display the v
_and_file> is prohibite alid output directories via hdbcons option 'output l'. A typical result looks like:
d.'
# Directory valid device id inode
0 /tmp true 2049 129860
1 /usr/sap/<sid>/home true 2049 650533
2 /usr/sap/<sid>/HDB01/work true 65024 6504259795
3 /usr/sap/<sid>/HDB01/<host> true 65024 66980829
4 /usr/sap/<sid>/HDB01/<host>/trace/DB_<sid> true 65024 63347734

The path can either be specified as absolute path (starting with "/") or as relative path. In case of a rel
ative path, it is relative to the SAP HANA trace directory path. In some cases relative paths don't wor
k (issue number 321727). In this case you can use an absolute path as a workaround.

11. How can SAP HANA threads related to hdbcons activities be identified?
Depending on the scenario and the SAP HANA Revision level the type and method of a SAP HANA thread is one of the
following when hdbcons commands are executed (SAP Note 2114710):

Thread type Thread method

Request core/ngdb_console

Request ngdb_console

JobWorker ServerJob

12. How can I find out when hdbcons was called?

The following options exist to determine hdbcons executions:

Appro Details
ach

Thread You can check the historic thread samples (e.g. using SQL: "HANA_Threads_ThreadSamples_FilterAndAggregation", SA
sample P Note 1969700) as described in "How can SAP HANA threads related to hdbcons activities be identified?" in order to check
s for the thread types / thread methods related to hdbcons executions.
 Trace f Starting with SAP HANA 2.0 SPS 03 dedicated service trace files are written that track all hdbcons calls including paramete
iles rs, execution timestamp and duration:

<service>_<host>.<port>.hdbcons.trc

Example:

"runtimedump dump -s BUILD,SYSTEMINFO,STATISTICS,CPUINFO" FALSE FALSE 2018-07-13 15:03:11.847 TRUE 2018-

07-13 15:03:12.495 647.978 msec
"tablepreload status" FALSE FALSE 2018-08-03 15:49:24.358 TRUE 2018-08-03 15:49:24.358 25.000 usec
"replication info" FALSE FALSE 2018-09-07 10:33:19.012 TRUE 2018-09-07 10:33:19.013 642.000 usec

Keywords
SAP HANA hdbcons administration management console
# Directory valid device id inode0 /tmp true 2049 1298601
/usr/sap/<sid>/home true 2049 6505332 /usr/sap/<sid>/HDB01/work true 65024
65042597953 /usr/sap/<sid>/HDB01/<host> true 65024 669808294
/usr/sap/<sid>/HDB01/<host>/trace/DB_<sid> true 65024 63347734

Products
Products

SAP HANA, platform edition all versions

This document refers to

SAP Component Title
Note/KBA

2893892 HAN-DB Fatal error occurred during installation XSA.

2814623

2800030 HAN-DB- FAQ: SAP HANA Kernel Profiler

PERF

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

2452123 HAN-DB hdbcons runtimedump dump -f [ERROR] Write access for file with name ... is prohibited

2400007 HAN-DB- FAQ: SAP HANA Runtime Dumps

PERF

2400005 HAN-DB-PER FAQ: SAP HANA Persistence

2380176 HAN-DB FAQ: SAP HANA Database Trace

2340450 HAN-DB FAQ: SAP HANA Table Replication

2313619 HAN-DB- How-To: Generating and Evaluating SAP HANA Call Stacks
MON

2222276 HAN-DB How-To: Activating SAP HANA Memory Fencing

2222110 HAN-DB- FAQ: SAP HANA Load History

PERF

2220627 HAN-DB FAQ: SAP HANA LOBs

2177064 HAN-DB- FAQ: SAP HANA Service Restarts and Crashes

ENG
2147247 HAN-DB- FAQ: SAP HANA Statistics Server
MON

2127458 HAN-DB FAQ: SAP HANA Loads and Unloads

2119087 HAN-DB How-To: Configuring SAP HANA Traces

2114710 HAN-DB- FAQ: SAP HANA Threads and Thread Samples

MON

2106240 HAN-DB-PER HANA persistence startup error: ForceLogBackup - command already active

2101244 HAN-DB FAQ: SAP HANA Multitenant Database Containers (MDC)

2100040 HAN-DB- FAQ: SAP HANA CPU

PERF

2100009 HAN-DB- FAQ: SAP HANA Savepoints

ENG

2092196 HAN-DB- How-To: Terminating Sessions in SAP HANA

ENG

2000000 HAN-DB- FAQ: SAP HANA Performance Optimization

PERF

1999998 HAN-DB- FAQ: SAP HANA Lock Analysis

PERF

1999997 HAN-DB FAQ: SAP HANA Memory

1999880 HAN-DB-HA FAQ: SAP HANA System Replication

1999020 HAN-DB How-To: SAP HANA Troubleshooting when Database is no longer accessible

1870858 HAN-DB- HANA Alerts related to file system utilization

MON

1827393 HAN-DB High nameserver CPU usage due to incorrect landscapeVariables.properties

1813020 HAN-DB How to generate a runtime dump on SAP HANA

2973560 HAN-DB-PER Data Volume Reclaim Finishes Early

2910004 HAN-DB Increase Disk Usage After Performing DDL Operation on Table With Packed LOB Column

2858546 HAN-DB Indexserver Crash at TransactionManager::TransactionManager::deactivateSnapshot

2845208 HAN-DB indexserver crash when run "hdbcons 'statreg print -h'" command in OS level

2781933 HAN-DB Nameserver Crash at DataRecovery::LogSegment::freeRetainedSegment When Executing Command

hdbcons "log release -r"

2658611 HAN-DB- Embedded Statistics Service Control in live operation

MON

2616088 HAN-DB Indexserver Crash at PageAccess::PageInfoCollector::print When Executing hdbcons "pageaccess

analyse"

2599979 HAN-DB Indexserver Crash at Diagnose::CallStackManager::getStack When Using "top", "callgraph" or

"blocklist" of Category "mm" in hdbcons

2577314 HAN-DB Possible Row Store Inconsistency on IBM Power Platform

2532475 HAN-DB Long Startup Time Due to Long Running Garbage Collection

1969700 HAN-DB SQL Statement Collection for SAP HANA

SAP HANA Troubleshooting and Performance Analysis Guide

This document is referenced by

SAP Component Title
Note/KBA
2800030 FAQ: SAP HANA Kernel Profiler

1999930 HAN-DB FAQ: SAP HANA I/O Analysis

2400005 HAN-DB-PER FAQ: SAP HANA Persistence

3217547 HAN-DB "Cannot connect with process PID" error while connecting with SAP HANA database console tool
hdbcons

2154870 HAN-DB How-To: Understanding and defining SAP HANA Limitations

2499913 HAN-DB-PER How to shrink SAP HANA Data Volume size

2952353 HAN-DB Large size of memory usage on allocators Pool/RowEngine/MonitorView

1992889 HAN-DB Unknown Command 'hdbcons'

2817438 HAN-DB- How to check memory usage on secondary site in HANA system replication scenario
MON

2815245 HAN-DB-SEC Backup of a tenant database after recovering SYSTEMDB failed.

2186744 HAN-DB FAQ: SAP HANA Parameters

2572224 HAN-DB-PER How-To: Repairing SAP HANA Tables

2784291 HAN-DB How to generate runtime dumps for a specific HANA service from command line

2092196 HAN-DB- How-To: Terminating Sessions in SAP HANA

ENG

2699939 HAN-DB SAP HANA Emergency Suitcase

2222110 HAN-DB- FAQ: SAP HANA Load History

PERF

2380176 HAN-DB FAQ: SAP HANA Database Trace

2177064 HAN-DB- FAQ: SAP HANA Service Restarts and Crashes

ENG

2222217 HAN-DB How-To: Troubleshooting SAP HANA Startup Times

1999993 HAN-DB- How-To: Interpreting SAP HANA Mini Check Results

MON

2502256 HAN-DB- FAQ: SAP HANA Caches

ENG

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

2400007 HAN-DB- FAQ: SAP HANA Runtime Dumps

PERF

2399979 HAN-DB- How-To: Configuring automatic SAP HANA Data Collection with SAP HANASitter
PERF

2100040 HAN-DB- FAQ: SAP HANA CPU

PERF

1999998 HAN-DB- FAQ: SAP HANA Lock Analysis

PERF

2313619 HAN-DB- How-To: Generating and Evaluating SAP HANA Call Stacks
MON

2000000 HAN-DB- FAQ: SAP HANA Performance Optimization

PERF

2222276 HAN-DB How-To: Activating SAP HANA Memory Fencing

2147247 HAN-DB- FAQ: SAP HANA Statistics Server

MON

2127458 HAN-DB FAQ: SAP HANA Loads and Unloads

2119087 HAN-DB How-To: Configuring SAP HANA Traces

2114710 HAN-DB- FAQ: SAP HANA Threads and Thread Samples
MON

2100009 HAN-DB- FAQ: SAP HANA Savepoints

ENG

1999997 HAN-DB FAQ: SAP HANA Memory

1999880 HAN-DB-HA FAQ: SAP HANA System Replication

1999020 HAN-DB How-To: SAP HANA Troubleshooting when Database is no longer accessible

3435831 HAN-DB- Indexserver Crash at Metadata::TemporaryTableMemoryStatistics::makeRecordsForTempIndex

ENG

3405343 HAN-DB SAP HANA Database Server Management Console Crash at

Stream::impl::ExternalClientImpl::doReceive

2902494 HAN-DB Memory Leak in Pool/RowEngine/QueryExecution/SearchAlloc and Pool/RowEngine/GlobalHeap

2857855 HAN-DB Crash With Exception "Wrong savepoint version: Expected XXXX but found XXXX"

2781933 HAN-DB Nameserver Crash at DataRecovery::LogSegment::freeRetainedSegment When Executing Command

hdbcons "log release -r"

2743294 HAN-DB System not Responsive due to High Memory Consumption Causing Deadlocks in Handling NO
LOGGING RETENTION Tables

2701292 HAN-DB-HA Impaired System Replication When Having Network Issues and OOM on Primary Site Simultaneously

2637781 HAN-DB SQL Query Fails With "Data receive failed [Connection reset]", Indexserver Reports Error "close
channel while sending reply message"

2576669 HAN-DB-HA Increasing Log Volume Size on Secondary Site of a Multitier System Replication Setup With Operation
Mode Logreplay

2519008 HAN-DB Indexserver Crash at DataAccess::DisasterRecoverySecondaryHandlerImpl::evictVirtualFilePages

2301382 HAN-DB Increased Used Memory Size due to Pool/PersistenceManager/PersistentSpace/DefaultLPA/Page

(Rev. 110 - 122.05)