1

SAP Support Mailbox

From: Batch ID for Basis <sapsupport@email.uky.edu>Sent: Monday, April 20, 2015 12:08 PMSubject: LTD00001 - Rating not Determined (Gray) - SAP EarlyWatch Alert

Analysis from 04/13/2015 Until 04/19/2015

Report: LTD, Not ProductiveInstallation: 0020598649

Session: 0010000006988

EarlyWatch Alert-UKY Development

1 Service Summary

Some essential service data for the EarlyWatch Alert session is missing. Therefore, no rating is assigned.

Check the details in the "Service Preparation and Service Data Quality" section.

Alert Overview

Transport request have been created or changed in production

Standard users have default password.

Secure password policy is not sufficiently enforced.

A high number of users has critical authorizations

Protection of Passwords in Database Connections

Perform the following Guided Self Services.

Guided Self Service FAQ SAP Note

Security Optimization Service 696478

Transport Execution Analysis 1621722

For more information about Guided Self-Services, see SAP Enterprise Support Academy.

Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar.

Check Overview

2

Topic Rating Topic Subtopic

Rating Subtopic

SAP System Configuration

Database - Maintenance Phases

Operating System(s) - Maintenance Phases

Performance Overview

Performance Evaluation

SAP System Operating

Availability based on Collector Protocols

Program Errors (ABAP Dumps)

Update Errors

Table Reorganization

Hardware Capacity

Database Admiinstration

Security

SAP HANA System Privilege DATA ADMIN

SAP HANA Password Policy

SAP HANA Audit Trail

SAP HANA SQL Trace Level

Default Passwords of Standard Users

Control of the Automatic Login User SAP*

Protection of Passwords in Database Connections

ABAP Password Policy

Gateway and Message Server Security

Users with Critical Authorizations

Software Change Management

Number of Changes

Failed Changes

HANA Technology

HANA Download Function Module Problem

Overview

SAP HANA Stability and Alerts

SAP HANA Database Configuration

SAP HANA Resource Consumption

SAP HANA Workload and Performance

Size and Growth

Administration

SAP LT Replication Server

SLT Configuration

3

Check Overview Topic Rating Topic Subtopic

Rating Subtopic

SLT Performance

Note: The recommendations in this report are based on general experience. Test them before using them in your production system. Note that EarlyWatch Alert is an automatic service.

Note: If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager EarlyWatch Alert service, create a customer message on component SV-SMG-SER-EWA.

Note: If you require assistance in resolving any concerns about the performance of the system, or if you require a technical analysis of other aspects of your system as highlighted in this report, create a customer message on component SV-BO. For details of how to set the appropriate priority level, see SAP Note 67739.

Performance Indicators for LTD The following table shows the relevant performance indicators in various system areas.

Area Indicators Value Trend

Hardware Capacity Max. CPU Utilization on Appl. Server 5 %

Database Performance Avg. DB Request Time in Update Task 355 ms

Database Space Management DB Size 22.96 GB

DB Growth Last Month 0.25 GB

2 Landscape

2.1 Products and Components in current Landscape Product SID SAP Product Product Version LTD SAP NetWeaver 7.31 Main Instances (ABAP or Java based) SID Main Instance LTD Application Server ABAP LTD Add-on: DMIS - 2.0 Databases SID Database System Database Version LTD SQL SERVER 2008 R2 Other Main Instances Related SID Component Version or Release SID LTD SAP HANA Database 1.00.82.00 HAD

4

2.2 Servers in current Landscape SAP Application Servers SID Host Instance Name Logical Host ABAP JAVA LTD sltdev sltdev_LTD_01 SLTDEV

DB Servers SID Host Logical Host (SAPDBHOST) LTD sqldeva02 tcp:SQLDEVA02\NWCA Components Related SID Component Host Instance Name Logical Host LTD SAP HANA Database hanadev hanadev_HAD_00 hanadev LTD ABAP SCS sltdev sltdev_LTD_00 SLTDEV

2.3 Hardware Configuration Host Overview

Host Hardware Manufacturer Model CPU

Type CPU MHz Virtualization Operating

System

No. of CPUs

Memory in MB

hanadev Dell Inc. PowerEdge R910

Xeon X7560 @ 2.27GHz

2261

SuSE Linux Enterprise Server 11 (x86_64)

32 517018

sltdev VMware, Inc. VMware Virtual Platform

Xeon E5-2660 v2

VMWARE

Windows Server 2008 R2 (x86_64)

6 10239

sqldeva02

3 Service Preparation and Data Quality of LTD

Service data for overall importance is missing for this report. Because important checks could not be executed, the report is not rated (grey rating).

SAP NetWeaver system LTD is not fully prepared for delivery of future remote services.

Rating Check Performed

Service Data Quality

5

Rating Check Performed

ST-PI and ST-A/PI Plug-Ins

Service Preparation Check (RTCCTOOL)

Service Data Control Center

Service Data Collection for HANA

Hardware Utilization Data

In preparation for SAP services, ensure that connections, collectors, and service tools are up to date. These functionalities are explained in SAP Notes 91488 and 1172939.

3.1 Service Data Quality For this service, data of overall importance is missing.

The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Manager's BW or Configuration and Change Database (CCDB).

This section comprehensively shows issues with the data quality and provides hints on how to resolve them.

Legend for 'Priority' in Service Data Quality Prio. Explanation: Impact of Missing or Erroneous Data

Overall important data are missing. Detecting a critical situation may fail. Report cannot be rated green or yellow.

Data for an important chapter are missing. Some issues may not be detected. Report cannot be rated green.

Some important check could not be processed. The report can be rated green nevertheless.

Only checks of minor importance are affected.

An optional check was skipped.

3.1.1 Quality of Data in Service Data Control Center (SDCC)

Quality Of Service Data In ST-PI

Prio. Report Area affected Details and Related ST-PI Logical Function SAP

Note

Performance of ABAP System LTD

The hourly time profile of response times in the Workload Monitor (ST03) is missing for all application servers for the system. Check the configuration settings for the monitor and job SAP_COLLECTOR_FOR_PERFMONITOR. ST-PI function: SAPWL_WORKLOAD_GET_STATIST_I_W.

144864

Workload of ABAP System LTD

No activity was measured in the workload monitor (ST03). Check the configuration for the monitor and job SAP_COLLECTOR_FOR_PERFMONITOR. ST-PI function: SAPWL_TCODE_AGGREGATION_I_U_W and SAPWL_TCODE_AGGREGATION_I_M_W, SAPWL_TCODE_AGGREGATION_I_T_W,

144864

6

Quality Of Service Data In ST-PI

Prio. Report Area affected Details and Related ST-PI Logical Function SAP

Note SAPWL_WORKLOAD_GET_SUMMARY_I_W, SAPWL_WORKLOAD_GET_SUMMARY_I_X. Execption NO_DATA_FOUND occurred on SLTDEV_01 for function SAPWL_WORKLOAD_GET_SUMMARY_I_W.

3.2 ST-PI and ST-A/PI Plug-Ins The table below shows the service plug-ins implemented and their releases and patch levels. These recommendations are derived from report RTCCTOOL. For more information about RTCCTOOL, see SAP Note 309711.

Rating Plug-In Release Patch Level Release Rec. Patch Level Rec.

ST-A/PI 01Q_731 2 01R_731 1

ST-PI 2008_1_710 9 2008_1_710 11

Recommendation: The Service Tools for Applications Plug-In (ST-A/PI) is not up-to-date. For more information, see SAP Note 69455. The Solution Tools Plug-In (ST-PI) is not up-to-date. For more information, see SAP Note 539977.

3.3 Service Preparation Check (RTCCTOOL) Before we can ship any services, the latest version of the SAP Service tools must be implemented in your system. Report RTCCTOOL was last run on . During the check, the tool detected issues for which a RED rating was set.

Overall Status

SAP Note Title Tool

Status Manual Status

69455 [Note 69455] Addon ST-A/PI 01R_731

69455 [Note 69455] ST-A/PI 01R_731 Support Package 1

12103 [Note 12103] Collectors and TCOLL

539977 [Note 539977] ST-PI 2008_1_710 Support Package 11

69455 [Note 69455] Proc. after addon impl.

69455 [Note 69455] Switch on digital content verification

539977 [Note 539977] Addon ST-PI 2008_1_710

7

Recommendation: [Note 69455] Addon ST-A/PI 01R_731 "Servicetools for Applications Plug-In" for NetWeaver 7.31-7.40 From http://support.sap.com/supporttools->ST-A/PI->Installations&Upgrades download the installation ST-A/PI 01R_731. Upload to tx SAINT and install as per note 69455. Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'. [Note 69455] ST-A/PI 01R_731 Support Package 1 Addon supportpackage level 1 for ST-A/PI 01R_731 for NetWeaver 7.31-7.40 From http://support.sap.com/supporttools->ST-A/PI->Support packages-> ST-A/PI 01R_731 download patches up to SAPKITAB9N. For basis >=700 use the Maintenance optimizer to release the download. Upload from frontend to transaction SPAM, define a queue and import. [Note 12103] Collectors and TCOLL Planning table TCOLL for SAP workload collectors 700-702 and 731+ (SAP note 966309) plus check for master job SAP_COLLECTOR_FOR_PERFMONITOR (program RSCOLL00). Press the lights icon for details. 1) Add missing entries to table TCOLL using ST03N > Expert Mode > Collector & Performance DB > Performance Monitor Collector > Execution Times. [Do NOT add RSCOLL00 itself] 2) In SM37 program RSCOLL00 must be scheduled hourly background job. [Note 539977] ST-PI 2008_1_710 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_710 for 7.10 [your current level is one SP lower than recommended. Update recommended] Open http://support.sap.com/supporttools->ST-PI Supportpck.-> ST-PI 2008_1_710. Add patch SAPKITLREK (and predecessors if not yet implemented) download basket. Release basket via Maintenance optimizer. Upload from frontend into transaction SPAM, define a queue and import the queue.

3.4 Hardware Utilization Data

Host Operating System Performance Data

hanadev SuSE Linux Enterprise Server 11 (x86_64) OK

sltdev Windows Server 2008 R2 (x86_64) OK

sqldeva02 OS not detected OK

Hardware capacity checks could not be run successfully due to missing data. See SAP Note 1309499.

4 Software Configuration For LTD

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

8

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

4.1 SAP Application Release - Maintenance Phases

SAP Product Version End of Mainstream Maintenance Status

SAP EHP1 FOR SAP NETWEAVER 7.3 12/31/2020

In October 2014, SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025. If you are running a relevant release, see SAP Note 1648480 for more details and applicable restrictions.

4.2 Support Package Maintenance - ABAP The following table shows an overview of currently installed software components.

Support Packages

Software Component Version Patch

Level

Latest Avail. Patch Level

Support Package

Component Description

DMIS 2011_1_731 8 8 SAPK-11608INDMIS DMIS Component

PI_BASIS 731 10 15 SAPK-73110INPIBASIS

SAP R/3 Basis Plug-In

SAP_ABA 731 10 15 SAPKA73110 SAP Application Basis

SAP_BASIS 731 10 15 SAPKB73110 SAP Basis Component

SAP_BW 731 10 15 SAPKW73110 SAP Business Information Warehouse

ST-A/PI 01Q_731 2 2 SAPKITAB9L SAP Service Tools for Applications Plug-In

ST-PI 2008_1_710 9 11 SAPKITLRE9 SAP Solution Tools Plug-In

4.3 Database - Maintenance Phases

Database Version

End of Standard Vendor Support*

End of Extended Vendor Support* Comment Status SAP

Note

SQL Server 2008 07/08/2014 07/09/2019 Planned

Date

1177356

* Maintenance phases and duration for the DB version are defined by the vendor. Naming of the phases and required additional support contracts differ depending on the vendor. Support can be restricted to specific

9

patch levels by the vendor or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to guarantee support for your database version.

See the "Service Pack" section in the database section for additional information.

4.4 Operating System(s) - Maintenance Phases

Host Operating System End of Standard Vendor Support*

End of Extended Vendor Support* Status SAP

Note

sqldeva02

hanadev SuSE Linux Enterprise Server 11 (x86_64)

03/31/2019

936887

sltdev Windows Server 2008 R2 (x86_64) 01/13/2015 01/14/2020

1177282

* Maintenance phases and duration for the OS version are defined by the vendor. Naming of the phases and required additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by the vendor or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to guarantee support for your operating system version.

The automatic determination of the used operating system version(s) of system LTD did not work correctly for at least one host. For more information and possible reasons, refer to the section 'Service Preparation and Data Quality of LTD'.

4.5 HANA Database Version for HAD The following table shows your current/planned SAP HANA database version.

HANA Database Version SID SPS Stack SP Revision Maintenance Revision HAD 1.00.082.000 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).

4.6 SAP Kernel Release The following table lists all information about your SAP kernel(s) currently in use.

Instance(s) SAP Kernel Release

Patch Level

Age in Months OS Family

10

Instance(s) SAP Kernel Release

Patch Level

Age in Months OS Family

sltdev_LTD_01 721_EXT_REL 201 17 Windows Server (x86_64)

4.6.1 Kernel out of date

Your current SAP kernel release is probably not up to date.

Recommendation: Make sure that you are using the recommended SAP kernel together with the latest Support Package stack for your product.

4.6.2 Additional Remarks

SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2–4 times a year). We recommend that you base your software maintenance strategy on these stacks.

You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur.

For more information, see SAP Service Marketplace at http://service.sap.com/sp-stacks (SAP Support Package Stack information) and http://service.sap.com/patches (patch information).

4.7 Required DBSL Release for HANA Minimum DBSL for HANA

Instance SW Component

Current Release

Current Patch Level

Minimum Release

Minimum Patch Level Rating

sltdev_LTD_01 DBSL for HANA 721 201 721 34

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

5 Hardware Capacity

11

We have checked your system for potential CPU or memory bottlenecks, and found that the hardware is sufficient for the current workload.

5.1 Overview System LTD General This analysis focuses on the workload during the peak working hours (9-11, 13) and is based on the hourly averages collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note 1251291.

CPU If the average CPU load exceeds 75%, temporary CPU bottlenecks are likely to occur. An average CPU load of more than 90% is a strong indicator of a CPU bottleneck.

Memory If your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in your SAP system that can impair performance. The paging rating depends on the ratio of paging activity to physical memory. A ratio exceeding 25% indicates high memory usage (if Java has been detected 0%) and values above 50% (Java 10%) demonstrate a main memory bottleneck.

Server Max. CPU load [%] Date Rating RAM

[MB] Max. Paging [% of RAM] Date Rating

hanadev 2 04/15/2015

517018 0

sltdev 5 04/17/2015

10239 10 04/17/2015

6 Workload Overview LTD

6.1 Workload By Task Types This chart displays the main task types and indicates how their workload is distributed in the system.

12

Task Type Response Time[s] DB Time[s] CPU Time[s] GUI Time in s

RFC 47440 2022 1439 0

Batch 8290 4909 536 0

AutoABAP 3115 311 580 0

Others 457 148 148 12

The chart below lists the top task types in terms of total response time in s.

13

6.2 Top Applications This table lists the top applications of the RFC task type. The unit of measure is milliseconds [ms] for average time and seconds [s] for total time.

RFC Profile

Initial System Initial Action Total Response Time[s]

% of Total Load

Steps Avg. Resp. Time[ms]

Avg. Proc. Time[ms]

Avg. CPU Time[ms]

Avg. DB Time[ms]

SMD/smdci_SMD_01 EFWK RESOURCE MANAGER 6814 11.5 12028 567 485 40 71

SMD/smdci_SMD_01 /BDL/TASK_PROCESSOR 2908 4.9 80 36346 5247 2134 10977 LTD/SLTDEV_LTD_01 /1LT/IUC_REP_CNTR_010 165 0.3 277 594 582 6 12 LTD/SLTDEV_LTD_01 RDDMASGL 131 0.2 96 1369 363 139 962 LTD/SLTDEV_LTD_01 RSPARAGENER8M 116 0.2 2 58057 268 24102 35830 LTD/SLTDEV_LTD_01 SAPMSSY1 66 0.1 77 852 75 97 637 LTD/SLTDEV_LTD_01 SNOTE 22 0.0 18 1239 449 121 434 SMD/smdci_SMD_01 LANDSCAPE FETCH 21 0.0 32 666 608 14 56

14

RFC Profile

Initial System Initial Action Total Response Time[s]

% of Total Load

Steps Avg. Resp. Time[ms]

Avg. Proc. Time[ms]

Avg. CPU Time[ms]

Avg. DB Time[ms]

SMP/smpci_SMP_01 EFWK RESOURCE MANAGER 10 0.0 185 53 30 5 22

LTD/SLTDEV_LTD_01 RDDEXECL 8 0.0 7 1184 203 22 513

This table lists the top applications of the Batch task type. The unit of measure is milliseconds [ms] for average time and seconds [s] for total time.

Jobs Profile

Report Response Time[s]

% of Total Load Steps CPU

Time[s] DB Time[s]

RSUPG_CLONE_TABLES 6837 11.5 3 419 4560 /BDL/TASK_SCHEDULER 758 1.3 168 3 10 (BATCH) 326 0.5 10327 79 126 RSUPG_PARCLONE 141 0.2 1 11 96 RDDMASGL 51 0.1 2 1 14 RSPTBFIL 37 0.1 5 7 18 RS_GENERATE_PUTTB_SHD 29 0.0 1 3 27 RSBTCRTE 28 0.0 227 7 12 RDDGENBB 20 0.0 4 1 11 RDDMNTAB 14 0.0 2 1 7

7 Performance Overview LTD

The performance of your system was analyzed with respect to average response time and total workload. No problems that could significantly impair system performance were detected.

Rating Check

Performance Evaluation

7.1 Performance Evaluation The following table shows the average response times of task types running in dialog work processes.

Dialog WP related task types Task Type Steps Avg. Resp.

Time[ms] Avg. CPU Time[ms]

Avg. Wait Time[ms]

Avg. DB Time[ms]

Avg. GUI Time[ms]

15

Dialog WP related task types Task Type Steps Avg. Resp.

Time[ms] Avg. CPU Time[ms]

Avg. Wait Time[ms]

Avg. DB Time[ms]

Avg. GUI Time[ms]

RFC 96082 494 15 1 21 0 HTTP(S) 20155 5 4 0 0 0 Dialog 58 1380 174 0 688 214

The measured times are compared against reference times to provide a rating.

- If the task type is not listed in the "Task Type Overview" table in the "Workload Overview LTD" section, the task type is not included in the evaluation.

- DIALOG, RFC, and HTTP(S) are considered to be related to the end user's dialog activity.

The table below indicates that performance problems are anticipated for tasks rated YELLOW or RED.

Ratings Task Steps Application Server Performance Database Server Performance RFC 96082

Reference Times

Task Ref. for Avg. Response Time[ms] - Yellow Rating

Ref. for Avg. Response Time[ms] - Red Rating

Ref. for Avg. DB time[ms] - Yellow Rating

Ref. for Avg. DB time[ms] - Red Rating

RFC 2400 3600 1200 1800

The chart below displays the time profile for the RFC task type.

History of Response Time of LTD

16

The graphs below show the time profiles of the following task types: RFC.

In the following, we analyzed the trend within the following time frames:

Short term: From calendar week 13/2015 to 16/2015

Long term: From calendar week 52/2014 to 16/2015

Task Type

Long Term Growth (%/year) Trend Short Term Growth

(%/year) Trend

ALL 156.6-

183.4

Dialog 167.5

278.9-

HTTP(S) 9.4-

356.3

RFC 24.6-

31.1

17

A long-term decrease of response time: 156.6%/year was found within the period analyzed and this increased further during the last four weeks: the short-term growth is 183.4%/year.

7.2 Application profile In the following, we analyzed the trend within the following time frames:

Short term: From calendar week 13/2015 to 16/2015

Long term: From calendar week 52/2014 to 16/2015

The table below shows the time profile of the top applications by total workload during the analyzed period.

Top Applications by Response Time

Task Type Application

Total Resp. Time in s

% of Total Load

Avg. Resp. Time in ms

Long Term Growth (%/year)

Short Term Growth (%/year)

Avg. DB Time in ms

Avg. CPU Time in ms

RFC LTD/SLTDEV_LTD_01|/1LT/IUC_REP_CNTR_010 145780 51 596 1.8 26.4 13 8 RFC SMD/smdci_SMD_01|EFWK RESOURCE MANAGER 106371 38 551 8.2 23.8 58 47 RFC SMD/smdci_SMD_01|/BDL/TASK_PROCESSOR 27290 10 33321 28.8 62.4- 11089 2636 Dialog SPAM 695 0 34764 0.0 0.0 6547 1526 RFC SMD/smdci_SMD_01|LANDSCAPE FETCH 298 0 641 6.3 6.4- 49 15 RFC LTD/SLTDEV_LTD_01|RDDMASGL 234 0 1635 0.0 0.0 1124 194 Dialog SESSION_MANAGER 168 0 1448 73.3 463.7- 262 33 Dialog LTRC 165 0 840 38.1- 577.3- 517 135 Dialog USMM 144 0 474 198.9- 198.9- 137 20 RFC SMP/smpci_SMP_01|EFWK RESOURCE MANAGER 113 0 39 31.9 125.4 17 6 Dialog <NUMBER RANGE BUFFER> 85 0 7 133.3 199.5 3 0 HTTP(S) ? 67 0 22254 4,327.4 4,327.4 9694 400 RFC SMD/smdci_SMD_01|DIAGLS_COMPUTE_STATUS 61 0 521 2.7- 2.1 3 4 Dialog SE11 57 0 7145 0.0 0.0 348 27 Dialog SNOTE 50 0 2069 0.0 0.0 1210 354 RFC LTD/SLTDEV_LTD_01|SAPMSSY1 41 0 1166 0.0 0.0 797 137 HTTP(S) {REPL_MON_SCHEMA_OIF 35 0 1577 586.6 586.6 982 211 Dialog SU01 34 0 385 0.0 0.0 269 34 RFC LTD/SLTDEV_LTD_01|/1LT/IUC_LOAD_MT_010_001 33 0 869 0.0 0.0 116 41 Dialog RSTPDAMAIN 29 0 1225 0.0 0.0 219 44

The graph below shows how the average response time of the top five applications varies over time. Data is normalized to 100% equaling the average value.

18

8 SAP System Operating LTD

The daily operation of your system was analyzed. We detected some problems that may impair system operation and stability.

8.1 Availability based on Collector Protocols No download information is available about the Availability based on Collector Protocols of your system.

Possible reasons are: - The most recent ST-PI is not applied to the system - Service definitions (in SDCC) should be refreshed - Download data was corrupted during data transmission (check first two items and try to collect and transmit the data one more time).

This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour.

The job does NOT check availability; it carries out only general system tasks such as collecting and aggregating SAP performance data for all servers/instances. The log does not contain any direct information about availability; it contains only information about the status of the hourly statistical data collection.

As of SAP Basis 6.40, system availability information is available in the CCMS (Computing Center Management System) of an SAP System, in Service Level Reporting of SAP Solution Manager.

This function is provided by the relevant Solution Manager Support Packages as an advanced development. For more information, refer to SAP Note 944496, which also lists the prerequisites that must be fulfilled before implementation can take place."

19

8.2 Update Errors In a system running under normal conditions, only a small number of update errors should occur. To set the rating for this check, the number of active users is also taken into consideration.

We did not detect any problems.

8.3 Table Reorganization The largest tables and/or rapidly growing tables of system LTD were checked. No standard SAP recommendations for the applicable data volume management were found.

8.4 Transports Transports were not found in the period analyzed.

8.5 Program Errors (ABAP Dumps) 4 ABAP dumps have been recorded in your system in the period 04/15/2015 to 04/16/2015. ABAP dumps are generally deleted after 7 days by default. To view the ABAP dumps in your system, call transaction ST22 and choose Selection. Then select a timeframe.

Date Number of Dumps

04/15/2015 2

04/16/2015 2

Name of Runtime Error Dumps Server (e.g.) User (e.g.) Date (e.g.) Time (e.g.)

DBIF_REPO_SQL_ERROR 2 SLTDEV_LTD_01 SAPSYS 04/15/2015 04:14:14

SYNTAX_ERROR 2 SLTDEV_LTD_01 SAPSYS 04/16/2015 16:27:49

It is important that you monitor ABAP dumps using transaction ST22 on a regular basis. If ABAP dumps occur, you should determine the cause as soon as possible. Based on our analysis, we expect no serious problems at the moment.

9 Security

20

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

Rating Check System ID

SAP HANA System Privilege DATA ADMIN HAD

SAP HANA Password Policy HAD

SAP HANA Audit Trail HAD

SAP HANA SQL Trace Level HAD

Default Passwords of Standard Users LTD

Control of the Automatic Login User SAP* LTD

Protection of Passwords in Database Connections LTD

ABAP Password Policy LTD

Gateway and Message Server Security LTD

Users with Critical Authorizations LTD

9.1 SAP HANA Database HAD

9.1.1 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

9.1.1.1 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.

21

9.2 ABAP Stack of LTD

9.2.1 Default Passwords of Standard Users

Standard users have default passwords.

Recommendation: Run report RSUSR003 to check the usage of default passwords by standard users. Ensure that users SAP* (must exist in all clients), SAPCPIC, and EARLYWATCH have non-default passwords in all clients. For more information, see "Protecting Standard Users" either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide. Make sure that the standard password for user TMSADM has been changed in client 000, and delete this user in any other client. SAP Note 1414256 describes a support tool to change the password of user TMSADM in all systems of the transport domain. SAP Note 1552894 shows how to update the report RSUSR003 to show the status of user TMSADM.

9.2.2 Protection of Passwords in Database Connections

Database user passwords of connected systems can be found in table DBCON. At least one critical record was found in table DBCON. This indicates that at least the manual postprocessing step of SAP Note 1823566 was not performed.

Recommendation: Apply SAP Security Note 1823566 and make sure that you execute the valid manual postprocessing step if you apply the Note correction or the corresponding support package.

Note: This Note is valid for all ABAP installations that use database connections, including when the text focuses on SAP Solution Manager. The Note refers to SAP Solution Manager because typically, many DB connections are maintained. If this recommendation is displayed, there are DB connections with passwords on the analyzed system. Although transaction DBCO (which you use to maintain such DB connections) does not show the passwords, you can find the obfuscated passwords using transaction SE16 for table DBCON with the field value PASSWORD <> space.

9.2.3 ABAP Password Policy

If password login is allowed for specific instances only, the password policy is checked only for these instances.

9.2.3.1 Password Complexity

Parameter: login/min_password_lng Rating Instance Current Value(s) Recommended Value

sltdev_LTD_01 6 8

The current system settings allow a password length of fewer than 8 characters. This allows weak passwords. Attackers may successfully recover these passwords and gain unauthorized access to the system.

Recommendation: Assign a minimum value of 8 to the profile parameter login/min_password_lng.

22

In addition, SAP provides options to enforce complex passwords. Find the current settings of the corresponding profile parameters in the following table.

Parameter Instance Current Value(s)

login/min_password_digits sltdev_LTD_01 0

login/min_password_letters sltdev_LTD_01 0

login/min_password_lowercase sltdev_LTD_01 0

login/min_password_uppercase sltdev_LTD_01 0

login/min_password_specials sltdev_LTD_01 0

Recommendation: Enforce a minimum of 3 independent character categories using the corresponding profile parameters. For more information, see SAP Note 862989 and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

9.2.3.2 Validity of Initial Passwords

Rating Parameter Instance Current Value(s)

login/password_max_idle_initial sltdev_LTD_01 0

Initial passwords are valid for more than 14 days.

Recommendation: Proceed as follows: -- Handle users of type C (Communication) with initial passwords because they will be locked if the above profile parameter is set. Use transaction SUIM/report RSUSR200 in each client to find users of type C (Communication). If these users are active and in use, switch the user type to B (System). This has no negative effect. -- Restrict the password validity to 14 days or less. Note that the value 0 grants unlimited validity. -- For more information, see SAP Note 862989 and the Profile Parameters for Logon and Password (Login Parameters) section, either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

9.2.4 Users with Critical Authorizations

For more information about the following check results, see SAP Note 863362.

Recommendation: Depending on your environment, review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations. You can use the User Information System (transaction SUIM) to check the results. For each check, you can review the roles or profiles that include the authorization objects listed in the corresponding section.

9.2.4.1 Super User Accounts

Users with authorization profile SAP_ALL have full access to the system. There should be a minimum of such users. The number of users with this authorization profile is stated for each client.

23

Client No. of Users Having This Authorization No. of Valid Users Rating

000 6 7

001 9 12

Authorization profile: SAP_ALL

10 Software Change and Transport Management of LTD

No critical software change management issues were found in your system.

10.1 SAP Netweaver Application Server ABAP of LTD

Rating Check Performed

Number of Changes

Failed Changes

10.1.1 Number of Changes

Performing changes is an important cost driver for the IT department. It is only acceptable to make a large number of software and configuration changes in exceptional situations, such as during go-live for an implementation project.

The following diagram shows the number of changes per day that were performed in the SAP system in the last week. The data is extracted from the Change Diagnostics application in SAP Solution Manager. The changes are grouped into "Software Maintenance" (such as support or enhancement packages), "Parameter" (instance, database, operating system), "Transport Requests", "SAP Notes", and "Miscellaneous" (such as security settings).

24

Date Security Software Maintenance Parameter Transport

Requests SAP Notes Miscellaneous

04/16/2015 0 2 3 2 2 0

04/17/2015 0 0 1 0 0 4

10.1.2 Number of Transport Requests

The following diagram contains information about the number of transport requests per day that were imported into the SAP system in the last week.

Date Workbench and Relocation Requests

Customizing Requests

Transport of Copies

04/16/2015 2 0 0

25

10.1.3 Number of Transported Objects

The following diagram contains information about the number of objects per day that was imported into the SAP system in the last week.

Date Objects in Workbench and Relocation Requests

Objects in Customizing Requests

Objects in Transport of Copies

04/16/2015 18 0 0

10.1.4 Failed Changes

In this check, we analyzed the number of failed changes in system LTD during the last week.

Rating Item Value Explanation

Transport requests with import errors

0 Number of transport requests with import errors that were not resolved within one hour.

Overtakers and bypassed transport requests

0

If an old object version overwrites a newer one we count this as a transport sequence error. We count both the overtaker transport and the bypassed transport. Each transport is only counted once.

11 Data Volume Management (DVM)

26

A statement regarding Data Volume Management on your system LTD could not be provided.

This report does not have a Data Volume Management (DVM) section because your SAP Solution Manager system does not fulfill the technical requirements, or the ST-A/PI release on your system LTD is too low (or could not be identified). For more information, see SAP Note 2036442. As a workaround, an attempt was made to check the database size and growth per year for your system LTD. However, the database size or growth per year could not be collected. As a consequence, a statement regarding Data Volume Management in your system LTD could not be provided.

12 Database Performance for LTD

No major performance problems were found in your database system.

12.1 I/O Performance The following tables show how I/O operations are distributed across the data files and log files respectively.

The average wait time per I/O operation is also shown below for each file (IOStallRead and IOStallWrite).

Generally, high I/O read times cannot be used as a direct indication of DB performance issues. We recommend, therefore, that you refer to SAP Note 987961 for information about interpreting the various I/O statistics available with SQL Server 2005 and 2008.

With respect to the data files, the I/O activity must be evenly distributed among the files. This can be achieved by manually maintaining an even amount of free space in data files.

Transaction log files are used sequentially, which is why having more than one file does not improve performance. If you have multiple log files for other reasons, uneven distribution can be ignored.

Additionally, the "IO related wait events" table summarizes and assesses all wait events relevant to disk I/O performance.

Note: The average wait time for each I/O operation (IOStallRead) of the files with YELLOW rating deviates by more than 50% from the best one. If this is not expected behavior of your storage subsystem, contact the

27

storage administrator or vendor. There may be potential to improve performance for the corresponding logical volumes.

Data Files

File Reads % of Reads Writes % of

Writes IOStallWrite [ms] / write request

IOStallRead [ms] / read request

File ID 1 112760 13.05 170997 6.99 9.89 37.20

File ID 2 676 0.08 1139741 46.60 2.06 15.77

File ID 3 105841 12.25 178899 7.31 10.15 37.87

File ID 4 105139 12.17 153192 6.26 10.04 40.62

File ID 5 109731 12.70 160116 6.55 10.18 41.79

File ID 6 108661 12.58 158419 6.48 9.95 46.50

File ID 7 107493 12.44 161353 6.60 10.28 50.11

File ID 8 106595 12.34 159709 6.53 10.45 52.59

File ID 9 107071 12.39 163486 6.68 9.80 52.94

Total 863967 100 2445912 100 6.35 44.89 IO related wait events

Wait type Wait time (ms) Requests Wait time /

Requests Reference Value Rating

Analysis timeframe (ms): 431,617,600

WRITELOG 14,571,618 12,948,244 1.13 6.00

ASYNC_IO_COMPLETION 7,882,824 391 20,160.68 PAGEIOLATCH_SH 3,836,173 524,558 7.31 15.00

PAGEIOLATCH_EX 882,140 105,266 8.38 IO_COMPLETION 162,869 77,052 2.11 PAGEIOLATCH_UP 16,073 6,982 2.30

12.2 Wait Statistics The wait statistics of the SQL Server show long wait times for the event(s) highlighted below. This can indicate slow performance of the I/O system or other unusual conditions. Note that wait events that are known to have no relevance to user queries ("idle events") are not shown in the table. High wait time for some events may indicate a performance bottleneck. In the "Rating" column, you may find the following symbols: "Red flash" - in a well-tuned database, the event should not appear among the top events. Its appearance indicates a bottleneck and thus potential for improvement. See explanations below. "Yellow exclamation mark" - it is normal that the wait event is among the top events, but its average value exceeds a threshold. An improvement may be possible. "Blue information sign" - this wait event is important for performance but does not have a critical value. No symbol - we do not have experience with a wait event of that type. If the overall database performance is not affected; it can be ignored.

28

A DB task goes to wait state SOS_SCHEDULER_YIELD if it has been running too long on a CPU. This indicates that there are a lot of expensive, long-running statements.

Analyze the SQL statement cache by looking for statements with high total and average CPU time, and then tune them. If SQL statements have been optimized, but there are still high total figures for this wait event, the database engine is suffering from an overall CPU bottleneck because of too slow CPUs or too few CPUs for the current load. Also check whether the CPU bottleneck itself is caused by excessive paging. If the paging rate is high, make sure you allow the SQL Server to lock pages in the memory, as described in SAP Note 1134345, irrespective of whether you are experiencing the symptoms described in this SAP Note.

Long total wait time for PAGELATCH_xx events is related to allocation of new extents in data files. Appearance of such events indicates a non-optimal data file layout or data file management.

Create a sufficient number of data files for the main database and for the tempdb database. Make sure that the initial size of tempdb is large enough so that it does not need to be expanded.

One of the events LCK_M_X, LCK_M_S, or LCK_M_U appears in the "Top Wait Events Statistics" table. This indicates that some processes must wait for exclusive database locks. Exclusive DB locks are caused either by application logic holding exclusive locks for longer than needed, by expensive statements executed within a database transaction, or by too high parallelization grade during background processing.

Analyze the lock history as explained in SAP Note 806342 to find the root cause.

Wait type Wait time (ms) Requests Wait time /

Requests Rating

Analysis timeframe (ms): 431,617,600

WRITELOG 14,571,618 12,948,244 1.13

ASYNC_IO_COMPLETION 7,882,824 391 20,160.68

BACKUPIO 6,812,100 1,703,399 4.00

BACKUPBUFFER 6,145,251 1,198,595 5.13

PREEMPTIVE_COM_GETDATA 4,361,363 51,973,832 0.08

PAGEIOLATCH_SH 3,836,173 524,558 7.31

PREEMPTIVE_OLEDBOPS 2,631,007 34,532 76.19

ASYNC_NETWORK_IO 1,981,757 2,888,109 0.69

BACKUPTHREAD 1,815,007 5,909 307.16

SOS_SCHEDULER_YIELD 1,423,565 19,671,488 0.07

PAGELATCH_EX 1,416,524 37,480,388 0.04

PAGEIOLATCH_EX 882,140 105,266 8.38

LCK_M_U 638,287 5,617 113.63

29

Wait type Wait time (ms) Requests Wait time /

Requests Rating

PREEMPTIVE_COM_QUERYINTERFACE 605,447 64,817 9.34

MSQL_DQ 604,603 8,644 69.94

12.3 Missing Indexes This check verifies that the indexes defined by SAP application developers in the SAP data dictionary also exist in the database. Missing primary indexes can lead to inconsistent data in the SAP system. A missing index of any kind can lead to severe performance problems.

No missing indexes were found in system LTD.

13 Database Administration for LTD

Major problems regarding database administration have been found. Check the following sections for problems and errors that may be caused by the way you administrate your database. Note: A remote service cannot verify certain important aspects of your administration strategy, such as your offsite storage of database backups and whether the backup tapes can be read correctly.

13.1 Database Files The following checks analyze the settings for database and transaction log files.

13.1.1 Data Separation

To distribute I/O load, place heavily used files such as database files, transaction log files, files of database tempdb, and the Windows paging files on separate disks.

Note: From the SAP side, we are not in a position to check whether your partitions are distributed across multiple physical devices.

Make sure the following brief guidelines for security, maximum performance, and scalability are taken into account.

1. The temporary database for SQL Server (tempdb) is used by queries to execute large join, sort, and group operations when the SQL Server buffer pool cannot provide enough memory.

For SAP BW, SAP SEM, and SAP SCM, tempdb I/O performance can become a major bottleneck when reporting queries are executed that use the fact table or perform aggregation. To prevent bottlenecks, we recommend that you manage tempdb as a normal SAP database. Use a data tempdb file on the same partition with each data SAP database file. Furthermore, do not place tempdb on the partition and disks

30

that contain the transaction log. For Storage Area Network (SAN) storage, tempdb can share space with the tempdb log files.

2. For security and performance reasons, store the SAP data files and the SAP transaction log file(s) on separate disk systems. They should not share disks with other SQL Server programs and database files.

3. Store the Windows paging file(s) on dedicated disks.

13.1.2 Database Free Space

With SQL Server, the database files can be expanded dynamically on the disks where they are located. If files run full and no freespace is left on disk, an error occurs and you risk system downtime. Therefore, we recommend that you pay close attention to the potential growth of the database. If you have database files located on several disks and you have to enlarge files, you should spread database free space evenly across all disks. SQL Server can then spread I/O load on all available disks.

The free space within your database files is currently below 10% of the database space used. Ensure that you manually expand your database files before free space is exhausted.

Note: We recommend allowing the 'Automatic growth' mechanism to work in exceptional cases only. The automatic growth mechanism will expand the data files most likely at a time of heavy system usage. While the file is expanded, database access is strongly impaired. Therefore, you should only expand the files manually during periods of low system activity.

Space Usage Size (MB) Rating

Database size 34780

used size 33297

free 1483

free in partition F 27693

total free 29176

13.1.3 Database File Settings

When distributing database files, adhere to the following general rules:

1. If you use directly attached disks, distribute the I/O load to multiple physical disks. This can be achieved by assigning each data file to an individual disk spindles.

2. For all data files in the R/3 system, enable "Autogrowth" option using SQL Server tools. Set the file growth to at least 100 MB.

3. Starting from SQL Server 2008 on Windows 2008R2 you can rely on automatic growth feature if a number of prerequisites are met. Please check SAP Note 1238993 for details.

4. Ensure that after a manual or automatic file expansion all data files have approximately equal amount of free space in them.

Note: Your current database file settings are:

31

Database File Name Growth activated?

Growth not restricted?

Next 2 steps possible?

Next step size

Free Space on File

Data file full?

Rating

F:\LTDDATA1\LTDDATA1.mdf

60.00 MB

182 MB

F:\LTDDATA2\LTDDATA2.ndf

60.00 MB

136 MB

F:\LTDDATA3\LTDDATA3.ndf

60.00 MB

214 MB

F:\LTDDATA4\LTDDATA4.ndf

60.00 MB

103 MB

F:\LTDDATA5\LTDDATA5.ndf

60.00 MB

119 MB

F:\LTDDATA6\LTDDATA6.ndf

60.00 MB

182 MB

F:\LTDDATA7\LTDDATA7.ndf

60.00 MB

281 MB

F:\LTDDATA8\LTDDATA8.ndf

60.00 MB

266 MB

Recommendation:

Use SQL Server tools to change the data file settings and ensure that enough free space is available. The standard settings for database files are: - Autogrowth = Enabled - File growth = at least 100 MB - No growth limit set

We found the following incorrect settings in system LTD:

The step size configured for automatic file growth is smaller than the recommended size of 100 MB.

13.1.4 Transaction Log File Settings

When transaction log files of an SQL Server database are full, log files can grow automatically, limited only by the space available on the Windows partition. This is only true if the files are allowed to grow and sufficient space is available.

The current settings of your transaction log files are as follows:

Transaction Log File Name

Growth activated?

Growth not restricted?

Next step possible?

Next step size

F:\LTDLOG1\LTDLOG1.ldf

10.00 %

32

The log file settings in system LTD are correct.

13.2 Error Analysis In this section, the database is analyzed for critical situations and some maintenance tasks.

13.2.1 Database Options

Certain database options may severely impair the data security of your database in the case of a disk crash. These options should never be set in a production system. If these options have been set (in exceptional cases only), additional backups must be performed.

DB Option Description Option Value Recommended Value Rating

Recovery RECOVERY MODEL SIMPLE FULL

We have detected that the recovery model on SAP System, database instance LTD, is not set according to SAP standards.

Recommendation: Set the recovery model of the LTD database to 'FULL' using SQL Server Management Studio. Using any other recovery model significantly increases the risk of data loss in the event of a storage or disk failure. You must then back up the LTD database completely.

13.3 Environment and Operating In this section, basic information on the database and its software environment are shown.

13.3.1 Database Growth

The figures show a history of the total size and usage of the database files.

13.3.2 Largest Tables

33

The following table shows the largest tables currently in the LTD database.

Table Name

Data (kB)

Reserved (data + indexes) kB

Used (data + indexes) kB Rows Modified

Rows

BALDAT 4731816 4816320 4815488 6242469 789018

REPOLOAD~ 3262368 3269632 3269272 99686 3752

REPOLOAD 3130480 3139264 3135928 103084 12378

REPOSRC 2188424 2276864 2259816 1235531 30280

REPOSRC~ 1834440 1899528 1899112 1276473 45192

sap_perfinfo 1495456 1605280 1594592 1826368 13570

D010TAB~ 239632 804160 803944 10979568 10951258

D010TAB 220592 734400 733168 10503585 451872

VARI 578464 681728 680952 3032119 406100

TBTCO 205472 432256 430336 1527302 103039

13.3.3 Service Pack

SAP always recommends the latest SQL Server Service Pack. For details on the SAP support strategy for SQL Server, see SAP Note 62988.

The recommendations for this check are as up to date as the SAP Service Tool.

Build In Use Builds Comment Release

Date

4295 See SAP Note 62988 and Microsofts KB article 321185 for SQL Server builds

Full information about all SQL server builds is linked in Microsoft Knowledge Base Article 321185.

13.3.4 Database Maintenance Jobs

Job SAP Note Rating

Blocking Lockstats Job not Scheduled! (CCMS Blocking Locks statistics) 547911

DBCC Job not Scheduled! (CCMS Check Database) 142731

Update Tabstats Job not Scheduled! (CCMS Update Table Statistics) 1027512

34

There are a number of database maintenance jobs that should be scheduled in order to alleviate troubleshooting and help with the administration of your system. Some of these jobs are not scheduled.

13.3.5 SAP Notes for SQL Server

The following SAP Notes contain useful information to operate the NetWeaver system on SQL Server.

SAP Note Title

1085937 Wait Event Analysis For SQL Server

111291 FAQ: SQL server analysis and avoiding deadlocks

1152848 FAQ: SQL Server Wait Events

1237682 Configuration Parameters for SQL Server 2008

555223 FAQ: Microsoft SQL Server

62988 Service packs for Microsoft SQL Server

806342 FAQ: Analyzing exclusive database locks on SQL Server

13.4 Installation Checks In this section database configuration properties are checked, which are normally set during the installation or are only rarely changed.

13.4.1 Auto Update Statistics option should be enabled for tables

Table Or Index Auto Update Statistics Rating

sap_workload_snapshot~0 OFF

Note: If the table contain many entries, not all the tables will be listed above. The total number of tables for which the automatic update statistics option has been disabled is 14.

As shown above, the automatic update statistics option has been disabled for some tables. Recommendation: Set the AUTOMATIC UPDATE STATISTICS option for the tables listed above to "ON". Implementation: You can do this using SQL command: EXEC sp_autostats <tablename>, 'ON' Background: AUTOMATIC UPDATE STATISTICS must only be set to "OFF" for tables VBHDR, VBMOD, and VBDATA, as described in SAP Note

879941. For all other tables, the automatic update mechanism must be set to "ON". This creates up-to-date statistics and ensures that the optimizer chooses the correct access path. Set the option to "ON" even if the statistics are updated regularly by a scheduled job. As long as the job runs successfully, no automatic update is necessary. If the job fails, the automatic update is beneficial.

35

13.4.2 Tables With Special Locking Setting

Table Lock Setting Rating

STXH Page locking disallowed

ATAB Page locking disallowed

CROSS Page locking disallowed

STXL Page locking disallowed

As shown above, row or page locking is disallowed for some tables.

Recommendation: Check whether this setting is intended for your system. If you cannot find a reason to use this setting, allow all locking levels for the tables listed.

Implementation: You can do this using SQL command: EXEC sp_indexoption <tablename>, 'DisAllowPageLocks', FALSE EXEC sp_indexoption <tablename>, 'DisAllowRowLocks', FALSE

Background: Disallowing PAGE LOCKING for a table can improve performance when processing simultaneous users. Under some circumstances, it may prevent deadlocks on this table. PAGE LOCKING may, therefore, have been disallowed intentionally.

14 SAP HANA - Technology for HAD

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 Stability and Alerts

SAP HANA Database Configuration

SAP HANA Resource Consumption

SAP HANA Workload and Performance

36

Rating Check

Size and Growth

Administration

14.1 HANA Download Function Module Problem

Problems with the SAP HANA download were detected.

Checks with download problems Check Title Memory Utilization Details for HANA Services Size of HANA schemas Memory consumption of Indexserver

Some monitoring data from your SAP HANA database could not be read because the related download function module of your ST-PI software component is not up to date.

Recommendation: Implement at least Support Package 09 for ST-PI 2008_1_xx and further changes according to SAP Note 1985402.

14.2 Overview The tables below provide an overview of your current SAP HANA database configuration.

Version Current SAP HANA DB Version 1.00.82.00 System environment

Hostname Physical Hostname

Nr. of CPU cores

Physical Memory [GB]

Swap Space [GB]

Nameserver: Actual role

Indexserver: Actual role

hanadev hanadev 32 504.90 2.00 MASTER MASTER

14.3 SAP HANA Stability and Alerts

14.3.1 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

37

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 Alert No. of

Occurrences Highest Rating

0 Identifies internal statistics server problem. 5,810 5

62 Identifies database users whose password is due to expire in line with the configured password policy. If the password expires,

410 3

65 Determines whether or not the most recent log backup terminates in the given time. 144 4

5 Determines the percentage CPU idle time on the host and therefore whether or not CPU resources are running low.

9 4

4 Identifies services that have restarted since the last time the check was performed. 1 4

52 Identifies new crashdump files that have been generated in the trace directory of the system. 1 3

Recommendations Alert ID General Recommendation KBA

0 Resolve the problem. For more information, see the trace files. You may need to activate tracing first. 1803039

4 Investigate why the service had to restart or be restarted, for example, by checking the service's trace files. For details please refer to the chapter "SAP HANA Stability and Alerts".

1909660

5 Investigate CPU usage. For details please refer to the chapter "SAP HANA Resource Consumption". 1909670

52 Check the contents of the dump files. For details please refer to the chapter "SAP HANA Stability and Alerts".

62 Change the password of the database user. 65 Investigate why the log backup runs for too long, and resolve the issue.

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*.

14.3.2 SAP HANA Dumps

SAP HANA dumps were detected during the time period analyzed.

SAP HANA dumps indicate critical situations during SAP HANA system operation.

38

Date Crash dumps OOM dumps Emergency dumps

04/18/2015 1 0 0

We observed a number of dumps in your SAP HANA system. Depending on the type of dump, different actions have to be performed: Out-of-memory dumps: There are two main reasons for out-of-memory dumps: - Too much data is loaded into the system, leaving insufficient memory for normal operation. - Processing of expensive SQL statements in SAP HANA consumes too much memory. The root cause has to be evaluated by analyzing the related OOM diagnosis file. Open a customer incident on component HAN-DB*, if necessary. All other dumps: In the event of emergency dumps or crash dumps, the call stack has to be evaluated. Open a customer incident on component HAN-DB*, if necessary.

14.3.3 SAP HANA services restarts

We detected downtimes of less critical services.

Service restarts Service name Number of restarts indexserver 1 nameserver 0 xsengine 0 preprocessor 0 daemon 0 statisticsserver 0

During the last week, we detected downtimes of less critical services (such as the statistics server). Ensure that these services are operating properly.

Recommendation: Investigate the corresponding trace files with regard to root cause error messages. For further assistance, open a customer message on the component HAN-DB*, if necessary.

14.4 SAP HANA Database Configuration

14.4.1 Parameter Recommendation

Important SAP HANA parameters checked in this service are set in accordance with SAP recommendations.

Important SAP HANA Parameters

Parameter Location Layername Current Value

Recommended Value Rating SAP

Note

active indexserver.ini: section mergedog

DEFAULT yes yes

enable_auto_log_backup global.ini: section DEFAULT yes yes

39

Important SAP HANA Parameters

Parameter Location Layername Current Value

Recommended Value Rating SAP

Note persistence

lock_wait_timeout indexserver.ini: section transaction

DEFAULT 1800000 <between 100000 and 7200000>

log_backup_timeout_s global.ini: section persistence

DEFAULT 900 <between 300 and 3600>

log_mode global.ini: section persistence

DEFAULT normal normal

plan_cache_size indexserver.ini: section sql DEFAULT 2147483648 >=2147483648

2040002

savepoint_interval_s global.ini: section persistence

DEFAULT 300 <between 10 and 7200>

socket_keepalive indexserver.ini: section session DEFAULT on on

1836774

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

default daemon.ini section: trace error <restore default>

global_allocation_limit global.ini section: memorymanager 400000 0

cer_rserve_addresses indexserver.ini section: calcengine 128.163.185.234:30120

cer_rserve_maxsendsize indexserver.ini section: calcengine 0

cer_timeout indexserver.ini section: calcengine 1200

num_cores indexserver.ini section: parallel 24

alert indexserver.ini section: trace error <restore

default>

authorization indexserver.ini section: trace debug

default indexserver.ini section: trace error <restore

default>

logger indexserver.ini section: trace info <restore

default>

persistencemanager indexserver.ini section: trace info <restore

default>

enable nameserver.ini section: sld yes

40

SAP HANA Parameters deviating from default

Parameter Location Current Value Default Value

alert nameserver.ini section: trace error <restore

default>

default nameserver.ini section: trace error <restore

default>

alert preprocessor.ini section: trace error <restore

default>

default preprocessor.ini section: trace error <restore

default>

alert xsengine.ini section: trace error <restore

default>

default xsengine.ini section: trace error <restore

default>

14.4.2 Disk Configuration

There are no disk configuration issues.

Disk ID Device ID File system Host Path Usage

4 899979 nfs hanadev /hanadevback/log/ LOG_BACKUP

5 17207 ext3 hanadev /usr/sap/HAD/HDB00/hanadev/ TRACE

3 741816 xfs hanadev /hana/log/HAD/ LOG

1 753303 ext3 hanadev /hana/data/HAD/ DATA

2 899979 nfs hanadev /hanadevback/data/ DATA_BACKUP

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

14.4.3 CPU Configuration

Rating Recommendation

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 Rating

hanadev Intel(R) Xeon(R) CPU X7560 @ 2.27GHz 2261 Dell Inc.

41

14.4.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 Rating

Database Trace Not default Default

SQL Trace Inactive Inactive

Expensive Statements Trace Active Inactive

Performance Trace Inactive Inactive

End-to-End Traces Default Default

Other Traces Default Default

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.

The following table lists HANA parameters set specifically for traces.

HANA Trace Area

Configuration File Section Trace Component

Current Trace Level

Database Trace daemon.ini trace default error

Database Trace indexserver.ini trace alert error

Database Trace indexserver.ini trace authorization debug

Database Trace indexserver.ini trace default error

Database Trace indexserver.ini trace logger info

Database Trace indexserver.ini trace persistencemanager info

42

HANA Trace Area

Configuration File Section Trace Component

Current Trace Level

Database Trace nameserver.ini trace alert error

Database Trace nameserver.ini trace default error

Database Trace preprocessor.ini trace alert error

Database Trace preprocessor.ini trace default error

Database Trace xsengine.ini trace alert error

Database Trace xsengine.ini trace default error

Expensive Statements Trace

indexserver.ini expensive_statement enable true

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.

14.5 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.

14.5.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 Space [GB]

Used Disk Space [GB]

Percentage of free Disk Space

Usage Types File system Rating

hanadev 504.00 435.00 14.00 LOG xfs

hanadev 34.00 17.00 52.00 TRACE ext3

hanadev 886.00 143.00 84.00 DATA ext3

hanadev 562.00 232.00 59.00 DATA_BACKUP+LOG_BACKUP nfs

43

More than 80% of the disk for your SAP HANA installation is used. This high usage might be caused by a lot of trace files or a high number of log files.

Recommendation: Back up your SAP HANA database immediately and find the root cause of the high disk usage. Delete either trace files or reorganize the log volumes.

14.5.2 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 1,312 Indexes of Colum Tables 803 Row Tables 785 Indexes of Row Tables 69

Largest Row Store Tables (Size)

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

Schema Name Table Name Table Size (MB)

Table Size alloc (MB)

PROSAM MEM 1,661 1,876

CLJ CPE_COURSE_HISTORY 628 725

CPE CPE_COURSE_HISTORY_20141210 597 700

CPE CPE_STUDENT_HISTORY 546 610

CPE CPE_STUDENT_HISTORY_BKP_030415 493 551

CPE CPE_STUDENT_HISTORY_BKP_120814 490 544

CLJ CPE_STUDENT_HISTORY_BKP_120814 490 544

CPE CPE_STUDENT_HISTORY_BKP 490 544

CLJ CPE_STUDENT_HISTORY 490 544

STAGING_AREA CPE_STUDENT_HISTORY_BU 433 482

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

Largest Column Tables (Size)

The tables below list the largest tables of the SAP HANA column store in terms of size.

44

Largest Column Tables according to Size

Schema Name Table Name Partition ID

Memorysize (Total) [MB]

SAPECC HRP1001 0 4,463 SAPECC DFKKOP 0 923 SAPECC DFKKOPK 0 831 SAPECC PIQDBAGR_APPR 0 669 SAPECC PIQDBAGR_GEN 0 667 SAPECC HRT1721 0 256 _SYS_STATISTICS HOST_RECORD_LOCKS_BASE 0 105 SAPECC GMIA 0 0 SAPECC ZHR_9016_DETAILS 0 0 SAPECC PIQPROC_PG_MB 0 0

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

Largest Non-partitioned Column Tables (Records)

The number of records in column-based table partitions 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) Rating SAPECC GMIA 145,420,640

SAPECC ZHR_9016_DETAILS 55,843,321

SAPECC PIQPROC_PG_MB 52,778,833

SAPECC HRP1001 50,431,016

DATA_SCIENTIST GRADE_PAIRS 49,052,534

ACPD MEMBR_SPANS 29,991,897

SAPECC DFKKOPK 29,910,928

SAPECC PA2002 28,447,761

SAPECC ZCAFLATTABLCHAN 24,435,345

ACTIVE_ANALYSIS GRADE_PAIRS 23,759,241

The table partitions can handle the number of the records.

14.6 SAP HANA Resource Consumption The following table shows an overview of the resource consumption of the SAP HANA instances in the monitored timeframe.

HANA Instances Overview

HANA Instance Role CPU Usage

Memory Usage

Memory Allocation of Tables

Memory Consumption Indexserver

hanadev_HAD_00 MASTER

45

The SAP HANA hardware resources are sufficient for the current workload.

14.6.1 Memory Utilization Details for HANA Instances

The following table shows the memory usage of the SAP HANA database. The table displays weekly average values of the HANA memory areas:

'Memory usage of the HANA database' corresponds to the memory that was used by the entire HANA database (comparable to 'DB used memory' in SAP HANA studio).

'Global allocation limit' is the limit for the overall memory usage of the HANA instance defined by parameter global_allocation_limit.

'Row store size' shows the average size of row store tables in HANA memory.

'Column store size' shows the average size of column store tables in HANA memory.

The main HANA workload is handled in the HANA index server. We list the average 'Memory usage of the index server' and the 'Effective allocation limit' of the index server.

If we observe memory shortage for a HANA instance, more detailed information is shown in the sections below.

Avg. memory usage by SAP HANA Instances

HANA instance

Memory usage of SAP HANA [GB]

Global allocation limit [GB]

Row store size [GB]

Column store size [GB]

Memory usage of indexserver [GB]

Effective allocation limit of indexserver [GB]

hanadev_HAD_00 391

14.7 SAP HANA Workload and Performance

14.7.1 SAP HANA Response Times

The following graph shows the execution times of the SAP HANA system in the monitored timeframe aggregated from all SAP HANA nodes. The displayed "Execution Time" is the hourly average execution time obtained by the historized SQL Plan Cache.

Since the "Execution Time" in the SQL Plan Cache does not contain all response time parts, we also show in the graph below the "Sum Execution Time", which is the sum of the "Execution Time" plus preparation time and table load time. For more information, see SAP Note 2000002 - FAQ: SAP HANA SQL Optimization.

46

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 and select - 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)

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.

47

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

Memorysize in Main Store [MB]

Memorysize in Delta Store [MB]

Records in Delta Store

Sum of Records

SAPECC DFKKOP 0 923 0 0 15,345,479 SAPECC DFKKOPK 0 831 0 0 29,910,928 SAPECC HRP1001 0 4,463 0 0 50,431,016 SAPECC PIQDBAGR_APPR 0 669 0 0 9,408,834 SAPECC PIQDBAGR_GEN 0 667 0 0 9,408,827 _SYS_STATISTICS HOST_RECORD_LOCKS_BASE 0 105 0 0 19,161,924 SAPECC HRT1721 0 256 0 0 11,298,612 SAPECC GMIA 0 0 0 0 145,420,640 SAPECC ZHR_9016_DETAILS 0 0 0 0 55,843,321 SAPECC PIQPROC_PG_MB 0 0 0 0 52,778,833

14.8 Administration

14.8.1 Diagnosis Files

The number and size of diagnosis files is uncritical.

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 Number of Files Total Size in MB hanadev Weekly Log 2 56.60 hanadev Weekly Trace 22 154.28 hanadev Weekly Dump 1 6.74 hanadev Unlimited TOTAL 47 227.90

We did not detect any issues with the number or size of these files.

Nevertheless, 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.

14.8.2 Backup and Recovery

No issues with data and log backups were detected

Log Backup History Date Weekday Successful Log Backups Unsuccessful Log Backups 04/13/2015 Monday 630 0

48

Log Backup History Date Weekday Successful Log Backups Unsuccessful Log Backups 04/14/2015 Tuesday 768 0 04/15/2015 Wednesday 768 0 04/16/2015 Thursday 766 0 04/17/2015 Friday 768 0 04/18/2015 Saturday 767 0 04/19/2015 Sunday 766 0 Data Backup History Date Weekday Successful Data Backups Unsuccessful Data Backups 04/13/2015 Monday 1 0 04/14/2015 Tuesday 1 0 04/15/2015 Wednesday 1 0 04/16/2015 Thursday 1 0 04/17/2015 Friday 1 0 04/18/2015 Saturday 1 0 04/19/2015 Sunday 1 0

14.8.3 License Information

Your license is permanent and will not expire in the near future.

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

Expiration Date Permanent Valid Product

Name Product Limit

HAD 0020598649 TRUE TRUE SAP-HANA 256

14.9 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

2066313 SAP HANA DB: Possible columnstore table corruption after point-in-time recovery

SAP Notes for SAP HANA SAP Note Description

1514967 SAP HANA: Central Note 1523337 SAP In-Memory Database 1.0: Central Note 2000003 FAQ: SAP HANA 2039883 FAQ: SAP HANA database and storage snapshots 1999997 FAQ: SAP HANA Memory 1999880 FAQ: SAP HANA System Replication

49

SAP Notes for SAP HANA SAP Note Description

1542651 EWA for SAP HANA: Service data collection 1592925 SAP HANA Database service connections 1642148 FAQ: SAP HANA Database Backup & Recovery 1664432 DBA Cockpit: SAP HANA database as remote database 1681092 Multiple SAP HANA databases on one appliance 1661202 Support for multiple applications on SAP HANA 1650394 SAP HANA DB: Partitioning and Distribution of Large Tables 1823343 Deactivating log mode LEGACY with SAP HANA SPS 07 1953429 SAP HANA and SAP NetWeaver AS ABAP on one Server 1813245 SAP HANA DB: Row store reorganization 1948334 SAP HANA Database Update Paths for Maintenance Revisions 1921675 SAP HANA Platform SPS 07 Release Note 1815547 Row/ColumnStore check without rowstorelist.txt 1814339 SHDB: Development tool classes NW 7.30 SP10

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 .

15 SAP LT Replication Server (SLT)

The performance, configuration, and administration of your SAP LT Replication Server have been analyzed and areas have been highlighted that require your attention. To ensure system stability and performance, you should implement the recommendations in the following section.

Rating Check

SLT Configuration

SLT Performance

50

15.1 SLT Configuration

15.1.1 Configuration Overview

The table below provides information about all configurations defined in the SAP LT Replication Server, including connections to SAP/non-SAP source systems and target system (SAP HANA).

Configuration Overview

Configuration Name

Mass Transfer ID

Source System Type

Source System Destination System Type

Destination System

SAPECC 010 SAP R3SBXA02_UKD_02 HDB hanaqas.iris.uky.edu:00 SAPECC 016 SAP R3SBXA02_UKD_02 HDB hanaqas.iris.uky.edu:00

The following Knowledge Base articles are part of a series of HANA operational recommendations and provide detailed step-by-step explanations.

SAP KBA Description

1971030 SLT - How to Check Source System Status

1971463 SLT - How to check Target System Status

1972009 How to create an SLT Configuration Step-by-Step

15.1.2 Background Job Configuration

Rating Recommendation

The number of data transfer jobs defined in the SLT configuration needs to be reviewed.

A couple of background jobs are involved in the replication process. In total, each configuration requires 2+N background jobs to be available: - 1 master controller job - 1 additional job either for the migration objects definition, access plan calculation, or to change configuration settings in the Configuration & Monitoring Dashboard. - N data transfer jobs

In addition, there is 1 monitoring job (master job) running in the SLT system. It must be ensured that enough background work processes are configured to run data replication jobs. Important to note is that having too many data load jobs running concurrently may cause high CPU consumption on the sources systems.

For more information, see the SLT Data Replication Administration Guide at http://help.sap.com/hana/.

The following tables show the number of load/replication jobs configured for each replication configuration as well as the background work process configuration.

Background Jobs in Configuration

51

Configuration Name

Mass Transfer ID

Initial Load Jobs Configured

Data Transfer Jobs Configured

Data Transfer Jobs Calculated

Rating

SAPECC 010 8 10 1

SAPECC 016 3 5 5

TOTAL 11 15 6 Configured Background Work Processes Instance Name

Operation Mode

No. of BTC Work Processes

No. of BTC Work Processes (class A)

SLTDEV_LTD_01 DUMMY 50 0 TOTAL DUMMY 50 0

The number of data transfer jobs defined in SLT configurations is set unnecessarily high for the current replication volume. Lowering the number of data transfer jobs reduces the CPU load on SAP source systems.

Recommendation: Use the "Configuration and Monitoring" dashboard (transaction LTR) to adjust the number of data load jobs. Ensure that you have an appropriate number of background work processes configured to allow parallel execution of data replication. An insufficient number of background work processes results in sequential execution of the replication and, consequently, in longer execution times.

15.1.3 Background Job Scheduling

Rating Recommendation

The background jobs for data replication are not running correctly.

Inactive Master Jobs Configuration Name Mass Transfer ID Job Name Latest Status Rating - - /1LT/IUC_REP_MSTR No job log found

The master job for data replication is not active for the above configurations. This job should always be active as it checks in the SAP HANA system whether there are new tasks and, if so, triggers the master control jobs. It also monitors the data transfer jobs and restarts them if necessary.

Recommendation: Restart the master job from the Configuration & Monitoring Dashboard (transaction LTR), 'Jobs and Connections' tab page. The master job resumes as well as all related jobs.

15.1.4 Tables for Replication

The following table provides an overview of the tables replicated, grouped by replication mechanism and replication status. This snapshot data was read when data was downloaded from your system for this service. You can monitor the replication status in the Configuration and Monitoring Dashboard (transaction LTR).

If replication errors occurred, their details are described in the subsequent 'Replication Errors' section.

Replicated Tables Configuration Name

Mass Transfer ID

Replication Mechanism

Replication Status

Number of Tables

SAPECC 010 Load tables (Initial Load) Executed 112

SAPECC 010 Stop replication Executed 1

52

Replicated Tables Configuration Name

Mass Transfer ID

Replication Mechanism

Replication Status

Number of Tables

SAPECC 010 Replication suspended Error 2

SAPECC 010 Replication In Process 1

SAPECC 016 Load tables (Initial Load) Executed 131

SAPECC 016 Load tables (Initial Load) Error 5

15.1.5 Replication Errors

Rating Recommendation

There are tables for which replication has stopped.

We found 7 tables with status 'error'. The following list shows tables that have most recently received this status (max. 20 tables are listed).

Replicated Tables with Errors Configuration Name

Mass Transfer ID Table Name Action Timestamp

SAPECC 010 ADRC Replication suspended

01/09/2015 20:59:35

SAPECC 010 SWWWIHEAD Replication suspended

01/09/2015 21:01:17

SAPECC 016 ZCACHARCHANGROU Load tables (Initial Load)

11/07/2014 20:55:11

SAPECC 016 ZCACHARNAMEALTE Load tables (Initial Load)

11/07/2014 20:55:11

SAPECC 016 ZCMSTUDNAMESELE Load tables (Initial Load)

11/07/2014 20:55:12

SAPECC 016 ZCACHARNAMEVALU Load tables (Initial Load)

11/07/2014 20:55:11

SAPECC 016 ZCMREPORECLSELE Load tables (Initial Load)

11/07/2014 20:33:11

Recommendation: Use the application log in the SAP LT Replication Server to identify and analyze errors that might occur during the replication process. In transaction SLG1, enter object DMC and check the alerts shown. Restart the replication afterwards via SAP HANA Studio.

16 Trend Analysis This section contains the trend analysis for key performance indicators (KPIs). Diagrams are built weekly once the EarlyWatch Alert service is activated.

In this report, historical data for "Transaction Activity", "System Performance", and "Database Performance" is taken directly from workload monitor ST03, because EarlyWatch Alert data has been accumulated for less than 20 sessions.

53

In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.

16.1 System Activity The following diagrams show the system activity over time.

The "Transaction Activity" diagram below depicts transaction activity in the system over time.

- Total Activity: Transaction steps performed each week (in thousands)

- Dialog Activity: Transaction steps performed in dialog task each week (in thousands)

- Peak Activity: Transaction steps (in thousands) during the peak hour; this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week.

(Peak Activity is absent if "Activity Data" is taken from ST03 data directly).

Historical data for "Transaction Activity" is obtained from the Workload Monitor (ST03).

The "User Activity" diagram below shows the user activity on the system over time.

- Total Users: Total users that logged on in one week.

- Active Users: Users who performed more than 400 transaction steps in one week.

54

16.2 System Operation The following diagram or table shows important KPIs for system operation.

16.3 Hardware Capacity The following diagram or table shows CPU max load from database server and all Appl servers.

55

Report time frame: Service data was collected starting at 04/20/2015 04:15:51. This took 7 minutes.

You can see sample EarlyWatch Alert reports on SAP Service Marketplace at /EWA -> Library -> Media Library.

General information about the EarlyWatch Alert is available at SAP Note 1257308.