You are on page 1of 24

Sample Report for SAP HANA

SAP EarlyWatch Alert

The following SAP EarlyWatch Alert (EWA) report for a SAP HANA system gives you an overview of
the checks available for the SAP HANA. It can be used as a reference for the content you can expect
to find when you have successfully set up the infrastructure required for the SAP EarlyWatch Alert.
The EarlyWatch Alert can be scheduled in the Solution Manager for product SAP HANA PLATFORM
EDITION. This requires at least ST-SER 701_2010_1 SP 23. Please see SAP Note 1958910 for all
details. For ABAP based systems running on HANA the HANA checks will already be present in the
EarlyWatch Alert for the ABAP system. To set this up the Solution Manager requires at least ST-SER
701_2010_1 SP 06 (see SAP Note 1529948).
The server where HANA is running must be prepared according to SAP Note 1542651.
In case the Solution Manager is below SER 701_2010_1 SP 23 t he EarlyWatch Alert checks for any HANA
system can be enabled in the EarlyWatch Alert report for some ABAP backend (e.g. the Solution
Manager). This ABAP backend must be prepared according to SAP Note 1543278.
Overview of SAP Notes related to the set-up of SAP EarlyWatch Alert for HANA:
Number
1958910
1543278
1542651
1529948

Short text
EarlyWatch Alert For HANA Database
Preparing the SAP back end + HANA for service sessions
EWA: Data collection for SAP HANA without Solution Manager
EWA: SAP HANA in EWA Services

SAP Note 1257308 - FAQ: Using EarlyWatch Alert is the starting point for general information about
the EarlyWatch Alert.

This sample report is available for SAP customers.

SERVICE REPORT
EarlyWatch Alert
Customer

SAP System ID

SDH

SAP Product

SAP NetWeaver 7.4

Status

Productive

DB System

SAP HANA Database 1.00.69

This example report contains only those chapters that contain


SAP HANA specific information.

SAP Solution Manager


ST-SER

Analysis from
Until

26.05.2014
01.06.2014

This sample report is available for SAP customers.

Session No.
Installation No.
Customer No.

1000000134415

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

1 Service Summary

During this EarlyWatch Alert session, we detected issues that


could potentially affect your system.
We recommend that you take corrective action as soon as possible.

ALERT OVERVIEW
SAP HANA database: More than 4 HANA Dumps occurred on your system

CHECK OVERVIEW
Topic
Rating

Topic

Subtopic
Rating

Subtopic

SAP System Configuration


Security
SAP HANA System Privilege DATA ADMIN
SAP HANA Password Policy
SAP HANA SQL Trace Level
HANA Technology
HANA Download Function Module Problem
Overview
SAP HANA Alerts
SAP HANA Database Configuration
SAP HANA Resource Consumption
SAP HANA Workload and Performance
Size and Growth
Administration

Service Summary
Customer

3/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Performance Indicators for SDH

This list of performance indicators only appear in a EarlyWatch


Alert report for an ABAP stack on HANA.
The following table shows the relevant performance indicators in various system areas.
Area

Indicators

Value

System Performance

Active Users (>400 steps)

19

Avg. Availability per Week

100 %

Avg. Response Time in Dialog Task

353 ms

Max. Dialog Steps per Hour

165

Avg. Response Time at Peak Dialog Hour

316 ms

Avg. Response Time in RFC Task

4242 ms

Max. Number of RFCs per Hour

5576

Avg. RFC Response Time at Peak Hour

3319 ms

Hardware Capacity

Max. CPU Utilization on DB Server

49 %

Database Performance

Avg. DB Request Time in Dialog Task

32 ms

Avg. DB Request Time for RFC

454 ms

Avg. DB Request Time in Update Task

10 ms

DB Size

196.73 GB

Last Month DB Growth

20 GB

Database Space Management

Service Summary
Customer

Trend

4/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

2 Software Configuration For SDH


We have listed recommendations concerning the current software
configuration on your system.

Your system's software versions are checked. If known issues with the software versions installed are identified,
they are highlighted.

2.1 HANA Database Version for SDH


The following table shows your current/planned SAP HANA database version.
HANA DATABASE VERSION
SID

SPS Stack

SP Revision

Maintenance Revision

SDH

1.00 SP 6

1.00.69

no

Recommendation: Please develop a clear SAP HANA maintenance strategy ensuring that the HANA
software is kept up to date. SAP HANA maintenance requires deployment and testing across the HANA
landscape in a controlled and timely manner (for example, system and user testing in a development
environment before updating a production environment).

2.2 Required DBSL Release for HANA


MINIMUM DBSL FOR HANA
Instance

SW
Component

ldcisdh_SDH_01 DBSL for


HANA

Current
Release

Current Patch
Level

Minimum
Release

Minimum Patch
Level

740

38

740

Rating

Your installed SAP HANA DBSL meets the minimal requirement to access the SAP HANA database.
SAP Note Description
1597627 HANA connection
1600066 Available DBSL patches for NewDB

Software Configuration For SDH


Customer

5/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

3 Security
Critical security issues were found in your system.
See the information in the following sections.

Rating

Check
SAP HANA System Privilege DATA ADMIN
SAP HANA Password Policy
SAP HANA SQL Trace Level

3.1 SAP HANA Database SDH


3.1.1 SAP HANA System Privilege DATA ADMIN
3.1.1.1 Users with DATA ADMIN Privilege
Users in your SAP HANA database have the DATA ADMIN system privilege.
The count considers direct grants to the users as well as indirect grants using roles. Users are counted as
activated if the validity time range matches the time of the evaluation and the user is not deactivated.
The SYSTEM and _SYS_REPO users are not considered, because these users have the DATA ADMIN privilege
by design and the privilege cannot be revoked from these users.
Number of Additional Users with DATA ADMIN Privilege

DATA ADMIN provides the authorization to modify and delete every object in every schema.
Recommendation: Remove the DATA ADMIN privilege from all user accounts except the SYSTEM und
_SYS_REPO users.

3.1.1.2 Role DBA_COCKPIT with DATA ADMIN Privilege


Probably based on the SAPINST installation procedure or on a former version of SAP Note 1640741 the DATA
ADMIN system privilege was granted to role DBA_COCKPIT.
Recommendation: Remove the DATA ADMIN privilege also from role DBA_COCKPIT according to the
updated version of SAP Note 1640741 topic 5 and 12.
Note: The role DBA_COCKPIT is usually granted to the users DBACOCKPIT,
DBA_COCKPIT_<calling_sid> and/or SAP<sid>. Thus the number of users in section 'Users with DATA
ADMIN Privilege' may be reduced, if you revoke the DATA ADMIN privilege from the DBA_COCKPIT role.

3.1.1.3 Roles with DATA ADMIN Privilege


The DATA ADMIN system privilege is granted to the following roles.
Name of Role
DBA_COCKPIT
ANOTHER_DATA_ADMIN_ROLE
The DATA ADMIN privilege provides the authorization to modify and delete every object in every schema.
It must not be granted to any user in a production environment. Therefore, it should not be assigned to any
particular role since it is not required and is at risk of being misused.
Recommendation: Remove the DATA ADMIN privilege from all the above roles or delete these roles.

Security
Customer

6/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

3.1.2 SAP HANA Password Policy


The following table provides an overview of the current values of the password policy and the corresponding
values recommended by SAP. A yellow rating indicates a setting that is weaker than recommended, while a green
rating indicates a recommended or stronger setting.
This section only appears in the EWA report if at least one of the following parameters is rated yellow.
Rating

Parameter

Current Value

Recommended Value

force_first_password_change

true

true

maximum_unused_inital_password_lifetime

28

minimal_password_length

The following table provides an overview of the remaining password policy parameters.
Rating Parameter

Current Value

Recommended Value

last_used_passwords

maximum_unused_productive_password_lifetime

365

365

minimum_password_lifetime

password_expire_warning_time

14

14

password_layout

A1a

A1a

password_lock_time

1440

1440

maximum_invalid_connect_attempts

maximum_password_lifetime

182

182

Recommendation: Adapt all values to the recommended or stronger settings.

3.1.3 SAP HANA Audit Trail


Sources of information for the SAP HANA audit trail:
- SAP HANA Security Guide
- SAP HANA Administration Guide
- SAP HANA Audit Trail Best Practice in the SCN

3.1.3.1 Auditing Status


Auditing is disabled in the security settings of your SAP HANA database.
Recommendation: Activate the SAP HANA audit trail and define appropriate audit policies.

3.1.3.2 Audit Trail Target


The audit trail target is currently set to 'CSV Text File'. This is not secure enough and should only be used for test
purposes. CSV text files are not sufficiently protected against unauthorized modifications.
Recommendation: Use the "Syslog" (default) or (as of SPS07) "Database Table" target.
Note: If you use the "Syslog" option, you also need to configure the operation system syslog accordingly
so that you will not receive error messages in the event of issues with the OS syslog.

3.1.3.3 Audit Policies


No customer-defined audit policies are enabled.
Recommendation: Define audit policies according to your needs.

Security
Customer

7/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

3.1.4 SAP HANA SQL Trace Level


CURRENT SQL TRACE PARAMETER VALUES
Parameter

Value

trace
level

off
all_with_results

The SQL trace level is currently set to 'ALL_WITH_RESULTS'. This setting will force the trace to write all result
sets from SQL statements in the trace file. Persons who are not authorized to see this information may still be able
to read these trace files.
Recommendation: Use SQL trace with results in exceptional cases only. Change the trace level to ALL or
a lower trace level.
Even if the SQL trace is switched off (trace=off), the trace level should not be set to ALL_WITH_RESULTS
because someone could activate this critical trace level unintentionally by switching on the SQL trace.

Security
Customer

8/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4 SAP HANA - Technology for SDH


We have checked your SAP HANA environment and found some issues that
might have a negative impact on your overall system stability and
performance. Review the report carefully and implement our
recommendations.

Rating

Check
HANA Download Function Module Problem
Overview
SAP HANA Alerts
SAP HANA Database Configuration
SAP HANA Resource Consumption
SAP HANA Workload and Performance
Size and Growth
Administration

4.1 Overview
The tables below provide an overview of your current SAP HANA database configuration.
VERSION
Current SAP HANA DB Version
1.00.69
SYSTEM ENVIRONMENT
Hostname Physical
Hostname
ld7328

Number of
CPUs

Physical
Memory [GB]

40

504,80

ld7328

Swap Nameserver:
Space Actual role
[GB]
32,00 MASTER

Indexserver:
Actual role
MASTER

SERVICES
Host

Servicename

Active

Type

ld7328
ld7328
ld7328
ld7328
ld7328
ld7328
ld7328

compileserver
xsengine
statisticsserver
indexserver
preprocessor
nameserver
daemon

YES
YES
YES
YES
YES
YES
YES

NONE
NONE
MASTER
MASTER
NONE
MASTER
NONE

SAP HANA - Technology for SDH


Customer

9/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4.2 SAP HANA Alerts


SAP HANA alerts have been issued for the monitored timeframe.
SAP HANA collects system information periodically and issues alerts of different priority levels according to
predefined thresholds. These alerts can be used to monitor the performance and stability of the SAP HANA
database. Possible alert priorities are:
1 Information
2 Low
3 Medium
4 High
5 Statistics Server Alert
The following "Alerts" table shows SAP HANA alerts that reached at least medium priority during the monitored
timeframe. It also shows how often an alert was created and the highest priority for this particular alert.
The "Recommendations" table lists recommendations for the alerts found and refers to SAP KBA Notes if
available. Further details and recommendations for SAP HANA alerts are available in the relevant sections of the
report.
ALERTS
Alert
ID

Host Alert

20

No. of Highest
Occurrences Rating

Identifies inactive services.


Determines the growth rate of non-partitioned columns tables.

18 4
310 4

RECOMMENDATIONS
Alert General Recommendation
ID

KBA

1 Investigate memory usage of processes.


Investigate disk usage of processes. Increase disk space, for example by shrinking
2 volumes, deleting diagnosis files, or adding additional storage.
Investigate why the service is inactive, for example, by checking the service's trace
3 files.
Investigate why the service had to restart or be restarted, for example, by checking
4 the service's trace files.
5 Investigate CPU usage.
10 Change in SYSTEM layer the parameter active in section(s) mergedog to yes.
In the 'transaction' section of the indexserver.ini file, set the 'lock_wait_timeout'
16 parameter to a value between 100,000 and 7,200,000 for the System layer.
17 Consider partitioning the table only if you expect it to grow rapidly.
Investigate the delta merge history in the monitoring view
19 M_DELTA_MERGE_STATISTICS. Consider merging the table delta manually.
20 Consider partitioning the table.
Investigate why the maximum number of permitted open connections is being
25 approached.
Investigate why the volume is not assigned a service. For example, the assigned
service is not active, the removal of a host failed, or the removal of a service was
26 performed incorrectly.
27 Consider repartitioning the table.
Obtain a valid license and install it. For the exact expiration date, see the monitoring
31 view M_LICENSE.

SAP HANA - Technology for SDH


Customer

1898317
1900643
1902033
1909660
1909670
1909641
1909707
1909763
1909742
1910140
1910159

1910169
1910188
1899480

10/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Alert General Recommendation


ID

KBA

If you need point-in-time recovery, reconfigure the log mode of your system to
"normal". In the "persistence" section of the global.ini configuration file, set the
parameter "log_mode" to "normal" for the System layer. When you change the log
mode, you must restart the database system to activate the changes. It is also
32 recommended that you perform a full data backup.
34 Investigate why the volume is not available.
35 Perform a data backup as soon as possible.

1900267
1900682
1900728

Recommendation: Monitor SAP HANA alerts in the system closely to get an overview of the SAP HANA
system status. React to warnings and problems visible in the alerts in due time. If you require support,
open a message on component HAN-DB*.

4.3 SAP HANA Database Configuration


4.3.1 Parameter Recommendation
Important SAP HANA parameters checked in this service are set in accordance with SAP
recommendations.
IMPORTANT SAP HANA PARAMETERS
Parameter

Location

active

indexserver.ini: section
mergedog
lock_wait_timeout
indexserver.ini: section
transaction
log_mode
global.ini: section
persistence
enable_auto_log_backup global.ini: section
persistence
log_backup_timeout_s
global.ini: section
persistence
active
statisticsserver.ini: section
statisticsserver_general
plan_cache_size
indexserver.ini: section sql
socket_keepalive
tcp_keepalive_time
tcp_keepalive_intvl
tcp_keepalive_probes

Layername Current
Value

Recommended
Value

DEFAULT

yes

yes

DEFAULT

1800000

DEFAULT

normal

<between 100000
and 7200000>
normal

DEFAULT

yes

yes

DEFAULT

900

SYSTEM

true

<between 300 and


3600>
true

SYSTEM

5368709120 >=2147483648

indexserver.ini: section
session
indexserver.ini: section
session
indexserver.ini: section
session
indexserver.ini: section
session

Rating

on
60
1
5

The parameters in the table below deviate from the default value.
This may affect performance and system stability. Check why these parameters have been modified and whether
they should be reset to the default values.
Note that parameters for which a custom value has been configured cannot be changed automatically with new
HANA revisions.
SAP HANA PARAMETERS DEVIATING FROM DEFAULT
Parameter

Location

Current Value

Default Value

cpu_time_measurement_mode

global.ini section:
resource_tracking

off

<restore default>

SAP HANA - Technology for SDH


Customer

11/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Parameter

Location

Current Value

Default Value

enable_tracking

global.ini section:
resource_tracking
global.ini section:
resource_tracking
indexserver.ini section:
distribution
indexserver.ini section:
mergedog

off

<restore default>

off

<restore default>

statement

<restore default>

(THM>=256000 and
(((DMS>100 or
DCC>100 or
DLS>1000) and DRC >
MRC/100) or
(DMR>0.2*MRC and
DMR > 1000))) or
(THM<256000 and
(DMS>50 or DCC>8 or
DLS>100))
2

(THM>=256000 and
(((DMS>100 or
DCC>100 or
DLS>1000) and DRC >
MRC/100) or
(DMR>0.2*MRC and
DMR > 0.001))) or
(THM<256000 and
(DMS>50 or DCC>8 or
DLS>100))
<restore default>

24

<restore default>

memory_tracking
client_distribution_mode
auto_merge_decision_func

token_per_table

indexserver.ini section:
mergedog
min_hours_since_last_merge_of_part indexserver.ini section:
optimize_compression
sql_executors
indexserver.ini section:
sql
enable
nameserver.ini section:
sld
force_interval
nameserver.ini section:
sld
interval
nameserver.ini section:
sld

80
yes
43200
300

SAP HANA - Technology for SDH


Customer

12/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4.3.2 Disk Configuration


There are no disk configuration issues.
Disk ID

Device ID

File system

Host

Path

Usage

5
4
3
2
1

997991
384465
376712
384465
365857

ext3
ext3
ext3
ext3
ext3

ld7328
ld7328
ld7328
ld7328
ld7328

/usr/sap/SDH/HDB10/ld7328/
/usr/sap/SDH/HDB10/backup/log/
/hdb/SDH/log/
/usr/sap/SDH/HDB10/backup/data/
/hdb/SDH/data/

TRACE
LOG_BACKUP
LOG
DATA_BACKUP
DATA

There are no disk configuration issues. Data and log data is stored on separate physical devices.

4.3.3 CPU Configuration


The CPU clock frequency is set as expected.
The following table shows the CPU type, CPU clock frequency, and hardware vendor of the hosts. If the CPU
clock frequency is set too low, this has a negative impact on the overall performance of the SAP HANA system.
Usually the CPU clock frequency should be above 2000 MHz.
CPU CONFIGURATION
Host

CPU Type / Architecture

CPU Frequency

HW Manufactor

ld7328

Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz

2395

FUJITSU

Rating

4.3.4 Trace Settings


SAP HANA Trace settings do not match default settings
If an inappropriate trace level is set for SAP HANA database components, a high amount of trace information may
be generated during routine operation. This can impair system performance and lead to unnecessary consumption
of disk space.
SAP HANA TRACE SETTINGS
HANA Trace Area

Current Configuration

Recommended Configuration

Database Trace

Default

Default

SQL Trace

Inactive

Inactive

Expensive Statements Trace

Active

Inactive

Performance Trace

Inactive

Inactive

End-to-End Traces

Not default

Default

Other Traces

Default

Default

Rating

By activating the Expensive Statement Trace, you can identify long-running SQL statements that lead to increased
response times or a high database load. This can also be beneficial for production systems. Note that, depending
on the configured threshold for expensive statements (parameter "threshold_duration" in indexserver.ini, section:
expensive_statement), the trace activity may be high and should be monitored. The Expensive Statement Trace is
deactivated by default.
The trace levels of the displayed components are not set to the default values that are suitable for a production
landscape.
Recommendation: For production usage of your SAP HANA database, we recommend setting the trace
level of all components according to the recommendations in the table above.
Background: Traces can be switched in the 'Trace Configuration' tab of the SAP HANA studio
Administration Console.

SAP HANA - Technology for SDH


Customer

13/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

The following table lists HANA parameters set specifically for traces.
HANA Trace Area

Configuration
File

Section

Trace Component Current Trace


Level

End-to-End Traces
End-to-End Traces
Expensive
Statements Trace
Expensive
Statements Trace

indexserver.ini
indexserver.ini
indexserver.ini

traceprofile_sap_passport_high
embeddedapi
traceprofile_sap_passport_medium embeddedapi
expensive_statement
enable

indexserver.ini

expensive_statement

info
info
true

threshold_duration 2000000

Note that activating traces and setting detailed trace levels may cause a high system load. It generates a large
number of trace files that can take up a lot of disk space and may have an impact on performance.
Recommendation: Activate traces for specific analysis only and make sure that trace levels are set to the
necessary level of detail. Make sure that traces are deactivated after analysis of the system has been
completed.

4.4 Size and Growth


Monitoring the size and growth of the HANA database is crucial for system stability and performance. In terms of
stability, the growth on disk is shown. In terms of performance, the size of row and column tables as well as the
size of delta areas in column tables are analyzed.

4.4.1 Disk Usage


Percentage of free disk space > 20%
The table below shows the disk occupancy with respect to the partitions and their usage types. If the percentage
of free disk space falls below 10%, an intermediate action has to be performed. Otherwise, there is a risk of
standstill in the SAP HANA database.
DISK SPACE
Host

Available Disk Used Disk


Space [GB] Space [GB]

Percentage of Usage Types


free Disk Space

File
system

ld7328

2.111,00

229,00

ld7328

512,00

4,00

89,00 DATA

ext3

99,00 LOG

ext3

ld7328

512,00

59,00

88,00 LOG_BACKUP+DATA_BACKUP ext3

ld7328

49,00

16,00

68,00 TRACE

Rating

ext3

4.4.2 Volume Files


The table below shows the number and size of the data files for the different SAP HANA server processes.
VOLUME FILES
Service

Files

statisticsserver
statisticsserver
statisticsserver
xsengine
xsengine
xsengine
indexserver
indexserver
indexserver

1
14
15
1
5
6
1
4
5

Size [GB] Host


17,06
0,81
17,88
0,26
0,03
0,29
179,41
3,00
182,41

SAP HANA - Technology for SDH


Customer

ld7328
ld7328
ld7328
ld7328
ld7328
ld7328
ld7328
ld7328
ld7328

File Type
DATA
LOG
TOTAL
DATA
LOG
TOTAL
DATA
LOG
TOTAL

14/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4.4.3 Tables and Indexes


The table below displays the number of column and row tables together with their indexes.
TABLES AND INDEXES
Objects

Number

Column Tables
Indexes of Colum Tables
Row Tables
Indexes of Row Tables

48.838
52.705
1.865
2.490

4.4.4 Row Store Size


The allocated row store size is not critical.
The table below shows the size of the HANA row store. The row store contains mainly SAP Basis and statistics
tables. The rating indicates whether the size limit of 750 GB will be reached in the near future.
ROW STORE SIZE
Host

Port

ld7328

31003

Allocated Size [MB]

Rating

82.944

4.4.5 Row Store Fragmentation


The row store is not very fragmented.
The following table shows the allocated size and free page ratio (fragmentation) of the row store. The term
'fragmentation' refers to unused space in the SAP HANA row store that cannot be used for technical reasons. High
fragmentation can cause performance issues and longer backup times. Row store reorganization is generally
recommended if the allocated row store size is larger than 10 GB and the free page ratio is higher than 30%.
ROW STORE SIZE AND FRAGMENTATION
Host

Port

Row Store Reorganization


Recommended

Free Page Ratio


[%]

Allocated Size
[MB]

Free Size
[MB]

2,38

82.944

1.981

ld7328 31003 FALSE

4.4.6 Largest Row Store Tables (Size)


The table lists the 10 largest row tables according to size.
Schema Name

Table Name

SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH

SNAP
REPOLOAD
SATC_AC_RESULTVT
REPOSRC
SASACONT1
TRFCQDATA
D010TAB
D010INC
SACONT01
VRSX3

Table Size (MB)

Table Size alloc (MB)

31.105
7.574
6.319
4.362
3.858
2.159
2.134
1.543
1.295
1.213

32.586
8.369
7.632
5.011
4.277
2.390
2.268
1.578
1.436
1.471

For large SAP Basis tables, remove obsolete data regularly according to SAP Note 706478.

SAP HANA - Technology for SDH


Customer

15/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4.4.7 Largest Column Tables (Size)


The tables below list the largest tables in the SAP HANA column store in terms of size.
LARGEST COLUMN TABLES ACCORDING TO SIZE
Schema Name

Table Name

Partition ID

SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDJDB
SAPSDH
SAPSDH
SAPSDJDB

LMDB_P_INSTANCE
BALDAT
LMDB_P_CHANGELOG
WBCROSSGT
LMDB_P_ASSOC
DSVASRESULTSGEN
BC_SLD_INST
/SDF/SQLHIST
USOB_AUTHVALTRC
BC_SLD_ASSINST

0
0
0
0
0
0
0
0
0
0

Memory Size (Total) [MB]


6.819
6.507
3.079
2.322
1.124
1.089
699
647
560
467

For large SAP Basis tables, remove obsolete data regularly according to SAP Note 706478.

4.4.8 Largest Non-partitioned Column Tables (Records)


The number of records in column-based tables is not critical.
The table below shows the largest non-partitioned column tables in terms of the number of records.
LARGEST NON-PARTITIONED COLUMN TABLES ACCORDING TO RECORDS
Schema Name

Table Name

Records (Total)

SAPSDH

LMDB_P_INSTANCE

58.202.592

SAPSDH

WBCROSSGT

57.757.294

SAPSDH

AGS_TBOM_BASE

18.881.885

SAPSDH

BALDAT

17.772.244

SAPSDH

DSVASRESULTSGEN

14.913.412

SAPSDH

DOKTL

11.721.864

SAPSDH

LMDB_P_ASSOC

9.878.238

SAPSDH

DSVASRESULTSATTR

9.450.413

SAPSDJDB

BC_SLD_ASSINST

8.462.452

SAPSDH

E071K

7.316.471

Rating

Your tables can handle the number of the records.

4.4.9 Largest Partitioned Column Tables (Records)


The number of records in column-based tables is not critical.
The table below shows the largest partitioned column tables in terms of the number of records.
LARGEST PARTITIONED COLUMN TABLES ACCORDING TO RECORDS
Schema Name

Table Name

Partition ID

SAPSDH

/BI0/F0HDB_C12H

38.121.514

SAPSDH

/BI0/F0SM_STAT

14.059.105

SAPSDH

/BI0/F0HDB_C07H

8.254.697

SAPSDH

/BI0/F0HDB_C08H

7.534.026

SAPSDH

/BI0/F0SMD_PEH1

4.142.584

SAPSDH

/BI0/F0SMD_CV02

1.677.184

SAPSDH

/BI0/F0HDB_C09H

1.135.134

SAP HANA - Technology for SDH


Customer

Records (Total)

Rating

16/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Schema Name

Table Name

Partition ID

Records (Total)

SAPSDH

/BI0/F0CCMHOUR1

970.041

SAPSDH

/BI0/F0HDB_C13H

947.189

SAPSDH

/BI0/F0SMD_PE2H

781.475

Rating

Your tables can handle the number of the records.

4.4.10 Largest Column Tables in terms of delta size


No problems with the delta size of column store tables were detected.
The separation into main and delta storage allows high compression and high write performance at the same time.
Write operations are performed on the delta store and changes are transferred from the delta store to the main
store asynchronously during delta merge.
The column store automatically performs a delta merge according to several technical limits that are defined by
parameters.
If applications require more direct control over the merge process, the smart merge function can be used for
certain tables (for example, BW prevents delta merges during data loading for performance reasons).
LARGEST COLUMN TABLES IN TERMS OF DELTA SIZE
Schema
Name

Table Name

Partition
ID

SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH
SAPSDH

DSVASRESULTSGEN
USOB_AUTHVALTRC
BALHDR
BALDAT
LMDB_P_INSTANCE
/BI0/F0HDB_C12H
/BI0/F0HDB_C09H
LMDB_P_CHANGELOG
/BI0/F0HDB_C07H
/BI0/F0HDB_C13H

0
0
0
0
0
4
4
0
4
4

Memory Size in
Main Store [MB]

Memory Size in Records in


Delta Store Delta Store
[MB]

1.024
531
283
6.494
6.816
118
3
3.077
22
2

64
29
26
12
3
2
2
2
2
1

239.641
80.557
224.908
19.957
11.713
13.532
9.504
1.163
10.985
5.000

Sum of
Records
14.913.412
5.188.230
5.373.514
17.772.244
58.202.592
38.121.514
1.135.134
4.005.420
8.254.697
947.189

4.5 SAP HANA Resource Consumption


The following table shows an overview of resource consumption of the HANA instances in the monitored
timeframe. Details are listed in the chapters below, if we found issues with the resource consumption.
HANA INSTANCES OVERVIEW
HANA Instance

Role

ld7328_SDH_10

MASTER

CPU Usage

Memory Usage

Memory Usage of the HANA System

Some hardware resources of the SAP HANA are not sufficient for the current workload. This may lead to
performance and stability issues.

4.5.1 Memory Utilization Details for HANA Services


The following table shows the memory usage of the SAP HANA engines (services). This is a snapshot of memory
data taken during the time of the data collection for the service data.
Different aspects of the memory consumption of the HANA database are highlighted:
"Physical Memory Used by Services" corresponds to the "Database Resident Size" in the SAP HANA studio and
can be compared with the resident size of the service in the operating system.
The sum of "Heap Memory Used Size" and "Shared Allocated Size" roughly corresponds to the memory usage of
the SAP HANA database, which is shown in the SAP HANA studio as "Database Memory Usage".
The difference between the "Database Memory Usage" and the "Resident Database Memory" can usually be
explained by the "Heap Memory Allocated Size".
SAP HANA - Technology for SDH
Customer

17/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

PHYSICAL MEMORY USAGE BY HANA SERVICES


Host

ServiceName

ld7328
ld7328
ld7328
ld7328
ld7328
ld7328

statisticsserver
xsengine
compileserver
indexserver
preprocessor
nameserver

Physical
Memory used by
Service [GByte]
24,19
5,22
0,61
374,67
0,55
4,90

Heap Memory Heap Memory


Allocated Size
used Size
[GByte]
[GByte]
25,11
11,94
0,58
293,80
0,52
11,93

9,18
1,51
0,35
108,48
0,25
1,31

Shared Memory
Allocated Size
[GByte]

Shared
Memory used
Size [GByte]

0,31
0,31
0,00
81,18
0,00
0,28

0,14
0,14
0,00
79,12
0,00
0,11

4.5.2 HANA Instance ld7328_SDH_10


CPU Usage
The CPU usage of the SAP HANA appliance exceeds 75%. This may have an impact on HANA
performance.
The graphics below show the total average CPU usages and the maximum CPU usages per hour.
The data is obtained from the statistics tables of the HANA database.
If the CPU usage exceeds 75%, a yellow rating is given. If it exceeds the threshold of 90%, a red rating is
assigned.

SAP HANA - Technology for SDH


Customer

18/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Within the analyzed period, we observed a CPU consumption greater than 75%. High CPU consumption can
result in significant performance problems.
Recommendation: Monitor the CPU usage and analyze the reason for the high CPU consumption.

Memory Usage
We did not observe any memory bottlenecks.
The following graph shows the physical memory usage of the last week. The average and maximum memory
used by SAP HANA (and possibly other processes) is compared with the available physical memory and the
global allocation limit.
If this memory approaches the global allocation limit, objects have to be unloaded or memory-related dumps occur.
This may impair overall HANA performance and stability. The memory usage should not exceed the global
allocation limit.

We did not find any critical issues in this area.

Detailed Memory Usage of the HANA System


The memory usage of the tables exceeds the critical limit of the available memory of the system.
SAP HANA - Technology for SDH
Customer

19/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

This graphic shows the average memory consumption for storing row and column tables, and the memory
allocated for temporary calculations (workspace).

This graphic shows the average memory allocation of SAP HANA for row and column store tables in relation to the
allocation limit.
We do not expect any problems to occur if the memory allocation for SAP HANA tables remains below 50% of the
allocation limit.
If the memory allocation for SAP HANA tables becomes higher than 70% of the allocation limit, critical problems
may occur.

We have evaluated the amount of memory used for database tables in comparison to the memory available for
temporary computations (workspace). The memory left for working operations is adequate but may become critical.
Monitor the SAP HANA memory consumption closely. For more information about SAP HANA memory
consumption and monitoring, see the SAP HANA Administration Guide, chapter "Monitoring SAP HANA systems"
at http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf.

SAP HANA - Technology for SDH


Customer

20/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

4.6 SAP HANA Workload and Performance


4.6.1 SAP HANA Response Times
The following graph shows the overall response time of the SAP HANA system in the monitored timeframe. The
SAP HANA response times are collected from the history data of the SQL Plan Cache.

The following graph shows the response time distribution of the SAP HANA system. The data is collected from the
history data of the SQL Plan Cache.

Explanation of the SAP HANA response time shares:


- Preparation time time share for plan preparation
- Open time time share for cursor open
- Fetch time time share for cursor fetch
- Lock wait time - lock wait time share for the plan
- Table load time time share for loading tables during plan preparation (available as of SAP HANA rev. 50)
- Undefined response time time share not covered by the above response time shares

SAP HANA - Technology for SDH


Customer

21/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

Memory Usage of the HANA System

All other dumps:


In case of emergency dumps or crash dumps, the call stack has to be evaluated. Open a customer incident on
component HAN-DB*, if necessary.

4.7 Administration
4.7.1 Diagnosis Files
The trace directory contains a high number of diagnosis files or the files occupy a lot of disk space.
During operation, the SAP HANA database service writes messages and information to log files in its trace
directory. The system administrator should check these files regularly and react to error messages accordingly. A
large number of files may be generated, which can take up a lot of disk space and impair performance. The
following table shows the number of files contained in the trace directory.
DIAGNOSIS FILES
Server

Measured Time Period

Type

ld7328
ld7328
ld7328
ld7328

Weekly
Weekly
Weekly
Unlimited

Log
Trace
Dmp
TOTAL

Number of Files

Total Size in MB

2
18
2
219

242,14
89,57
3,93
4.298,99

We recommend that you check the content of the trace folder in the SAP HANA database installation directory on
a regular basis and delete any files that are no longer required.

4.7.2 Backup and Recovery


No issues with data and log backups were detected
LOG BACKUP HISTORY
Date

Weekday

26.05.2014
27.05.2014
28.05.2014
29.05.2014
30.05.2014
31.05.2014
01.06.2014

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

Successful Log Backups

Unsuccessful Log Backups

219
259
277
276
265
265
265

0
0
0
0
0
0
0

Successful Data Backups

Unsuccessful Data Backups

1
1
1
1
1
1
1

0
0
0
0
0
0
0

DATA BACKUP HISTORY


Date

Weekday

26.05.2014
27.05.2014
28.05.2014
29.05.2014
30.05.2014
31.05.2014
01.06.2014

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

4.7.3 License Information


Your license is permanent and will not expire in the near future.
SAP HANA - Technology for SDH
Customer

22/24

EarlyWatch Alert

SDH

26.05.2014 - 01.06.2014

The following table shows information about the validity of your license. The license should be permanent and
should be valid for more than one month.
LICENSE INFORMATION
System ID

Installation Number

SDH

0020270862

Expiration Date

Permanent

Valid

Product Name

TRUE

TRUE SAP-HANA

Product Limit
512

4.8 Important SAP Notes for SAP HANA


The following tables list important SAP Notes for SAP HANA.
SAP NOTES FOR CRITICAL SAP HANA ISSUES
SAP Note Description
1932132 SAP HANA : Large time difference between application server and HANA database.
1963779 Reaching the 768 GB limit of rowstore can cause data loss
2001840 SAP HANA SPS06: Restart or recovery terminates
SAP NOTES FOR SAP HANA
SAP Note Description
1514967
1523337
1542651
1592925
1642148
1664432
1681092
1661202
1650394
1823343
1953429
1813245
1948334
1935871
1921675
1815547
1814339
1944771

SAP HANA: Central Note


SAP In-Memory Database 1.0: Central Note
EWA for SAP HANA: Service data collection
SAP HANA Database service connections
FAQ: SAP HANA Database Backup & Recovery
DBA Cockpit: SAP HANA database as remote database
Multiple SAP HANA databases on one appliance
Support for multiple applications on SAP HANA
SAP HANA DB: Partitioning and Distribution of Large Tables
Deactivating log mode LEGACY with SAP HANA SPS 07
SAP HANA and SAP NetWeaver AS ABAP on one Server
SAP HANA DB: Row store reorganization
SAP HANA Database Update Paths for Maintenance Revisions
SAP HANA SPS 06 Database Maintenance Revisions
SAP HANA Platform SPS 07 Release Note
Row/ColumnStore check without rowstorelist.txt
SHDB: Development tool classes NW 7.30 SP10
SAP HANA SPS 07 Database Revision 70

SAP NOTES FOR OPERATING SYSTEM


SAP Note Description
1310037 SUSE LINUX Enterprise Server 11: Installation notes
1824819 SAP HANA DB: Recommended OS settings for SLES11/SLES4SAP SP2
1954788 SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP3
Deployment Best Practices for SAP HANA
Deployment Best Practices for SAP HANA offer a comprehensive suite of knowledge articles and guided
procedures on implementing and operating SAP HANA and applications powered by SAP HANA.
This new format allows for content integration into your on-premise SAP Solution Manager. For detailed
information, see http://www.service.sap.com/dbp4hana

SAP HANA - Technology for SDH


Customer

23/24