EarlyWatch Alert-UKY Production 1 Service Summary SAP HANA Audit Trail SAP HANA SQL Trace Level Default Passwords of Standard Users Control of the Automatic Login User SAP* Protection

1

SAP Support Mailbox

From: Batch ID for Basis <[email protected]>Sent: Tuesday, April 21, 2015 1:42 AMSubject: LTP00001 - Rating not Determined (Gray) - SAP EarlyWatch Alert

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

Report: LTP, Productive Installation: 0020598649

Session: 0010000008310

EarlyWatch Alert-UKY Production

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

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

SAP HANA database: Number of Records reaches recommended limit.

Perform the following Guided Self Services.

Guided Self Service FAQ SAP Note

Security Optimization Service 696478

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 Topic Rating Topic Subtopic

Rating Subtopic

2


Rating Subtopic

SAP System Configuration

Database - Maintenance Phases

Operating System(s) - Maintenance Phases

SAP System Operating

Availability based on Collector Protocols

Program Errors (ABAP Dumps)

Update Errors

Table Reorganization

Hardware Capacity

Database Admiinstration

Database Server Load From Expensive SQL Statements

Expensive SQL Statements

Database Server Load

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

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

3


Rating Subtopic

Administration

SAP LT Replication Server

SLT Configuration

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 LTP The following table shows the relevant performance indicators in various system areas.

Area Indicators Value Trend

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

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

Database Space Management DB Size 17.03 GB

DB Growth Last Month 0.36 GB

2 Landscape

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

4

Other Main Instances Related SID Component Version or Release SID LTP SAP HANA Database 1.00.82.00 HAP

2.2 Servers in current Landscape SAP Application Servers SID Host Instance Name Logical Host ABAP JAVA LTP sltprd sltprd_LTP_01 SLTPRD

DB Servers SID Host Logical Host (SAPDBHOST) LTP sqlclusa01 tcp:MYUKSQL\MYUKPDB Components Related SID Component Host Instance Name Logical Host LTP SAP HANA Database hanaprd hanaprd_HAP_00 hanaprd LTP ABAP SCS sltprd sltprd_LTP_00 SLTPRD

2.3 Hardware Configuration Host Overview

Host Hardware Manufacturer Model CPU

Type CPU MHz Virtualization Operating

System

No. of CPUs

Memory in MB

hanaprd Dell Inc. PowerEdge R910

Xeon X7560 @ 2.27GHz

2260

SuSE Linux Enterprise Server 11 (x86_64)

32 517018

sltprd VMware, Inc. VMware Virtual Platform

Xeon E5-2660 0

VMWARE

Windows Server 2008 R2 (x86_64)

12 24575

sqlclusa01

3 Service Preparation and Data Quality of LTP

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 LTP is not fully prepared for delivery of future remote services.

5

Rating Check Performed

Service Data Quality

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 LTP

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 LTP

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

144864

6

Quality Of Service Data In ST-PI

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

Note SAPWL_TCODE_AGGREGATION_I_M_W, SAPWL_TCODE_AGGREGATION_I_T_W, SAPWL_WORKLOAD_GET_SUMMARY_I_W, SAPWL_WORKLOAD_GET_SUMMARY_I_X. Execption NO_DATA_FOUND occurred on SLTPRD_01 for function SAPWL_WORKLOAD_GET_SUMMARY_I_W.

Landscape of Database LTP

A service data module is missing completely. ST-PI function: MSQ_ST04_DOWNLOAD used in section 'Landscape'.

539977

Quality Of Service Data In ST-A/PI

Prio. Report Area affected Details and Related ST-A/PI Module SAP

Note

Landscape of Database LTP

A service data module is missing completely. ST-A/PI function: MSSQL in project DMS used in section 'Landscape'.

69455

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

69455 [Note 69455] Switch on digital content

7

Overall Status

SAP Note Title Tool

Status Manual Status

verification

12103 [Note 12103] Collectors and TCOLL

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

69455 [Note 69455] Proc. after addon impl.

539977 [Note 539977] Addon ST-PI 2008_1_710

207223 [Note 207223] EWAlert setup

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 69455] Switch on digital content verification Switch on Digital content verification for recommendations of SAP Service prep. check (RTCCTOOL) or Security Notes Check (RSECNOTE) From the menu choose "Goto->Digital signatures" and press "Activate". [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

hanaprd SuSE Linux Enterprise Server 11 (x86_64) OK

8

Host Operating System Performance Data

sltprd Windows Server 2008 R2 (x86_64) OK

sqlclusa01 OS not detected OK

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

4 Software Configuration For LTP

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.

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

9

Support Packages

Software Component Version Patch

Level

Latest Avail. Patch Level

Support Package

Component Description

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

sqlclusa01

hanaprd SuSE Linux Enterprise Server 11 (x86_64)

03/31/2019

936887

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

10

The automatic determination of the used operating system version(s) of system LTP 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 LTP'.

4.5 SAP SLT - DMIS Version The tables below show the version of the DMIS software component installed on the SAP LT Replication Server and the connected SAP source systems.

SLT: DMIS Version Component Component Version Patch Level Rating DMIS 2011_1_731 8

Source Systems: DMIS Versions SID Component Component Version Patch Level Rating R3P DMIS 2011_1_731 8

Using SAP LT Replication Server for data replication with SAP HANA requires installing a specific DMIS add-on version and respective Support Packages on both the SAP source system(s) and the SLT system.

Recommendation: The compatibility of the different DMIS add-on versions and related Support Package levels (for SAP source systems and the SAP LT Replication Server) with related HANA Support Package Stacks is described in the following SAP Notes.

Relevant SAP Notes SAP Note Description

1577441 Installation and delta upgrade of DMIS 2011_1

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

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

11

Instance(s) SAP Kernel Release

Patch Level

Age in Months OS Family

sltprd_LTP_01 721_EXT_REL 201 17 Windows Server (x86_64)

4.7.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.7.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.8 Required DBSL Release for HANA Minimum DBSL for HANA

Instance SW Component

Current Release

Current Patch Level

Minimum Release

Minimum Patch Level Rating

sltprd_LTP_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

12

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 LTP 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 Analysis Start

Analysis End

hanaprd 5 04/13/2015

517018 0

04/13/2015 04/19/2015

sltprd 58 04/17/2015

24575 0

04/17/2015 04/17/2015

6 Workload Overview LTP

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

13

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

Batch 15724908 2850665 1974026 0

Others 79193 10714 10714 7

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

6.2 Top Applications 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]

14

Jobs Profile

Report Response Time[s]

% of Total Load

Steps CPU Time[s]

DB Time[s]

DMC_MT_STARTER_BATCH 15118796 95.7 175 1964113 2746270 IUUC_MONITOR_SCHEMA 604801 3.8 7 9800 104210 /BDL/TASK_SCHEDULER 654 0.0 168 3 4 (BATCH) 441 0.0 10465 68 60 IUUC_HOUSEKEEPING 111 0.0 7 18 84 IUUC_CREATE_COBJS_IF_TBL_ENTRY 42 0.0 3 7 17 IUUC_REPL_MASTER_CONTROLLER 23 0.0 7 1 9 RSBTCRTE 22 0.0 385 13 10 DMC_MT_PREC_ACP_CALCULATION 17 0.0 15 3 1 /SDF/CD_CUSTOM_CODE_CONNECT 0 0.0 1 0 0

History of Response Time of LTP

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 41/2014 to 16/2015

Task Type

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

(%/year) Trend

ALL 55.3

32.8

Dialog 70.4-

1,039.7-

HTTP(S) 149.7

2,560.0-

RFC 6.6

235.1

15

Total response time is increasing significantly: the long-term growth is 55.3%/year and the short-term growth is 32.8%/year.

6.3 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 41/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 SMP/smpci_SMP_01|EFWK RESOURCE MANAGER 255722 7 791 19.3 243.8- 50 51 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_001 122778 3 677 112.1- 702.8 94 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_003 113447 3 658 104.8- 813.4 80 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_002 111829 3 623 126.1- 726.9 86 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_014 110006 3 647 140.2- 739.9 91 5 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_016 109177 3 653 135.2- 836.8 85 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_005 108864 3 651 102.1- 824.2 84 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_013 108832 3 634 130.6- 1,082.2 90 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_007 108609 3 638 97.7- 707.4 70 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_009 108441 3 633 139.2- 407.3 80 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_011 107791 3 646 130.9- 879.8 69 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_020 107375 3 635 142.8- 912.7 82 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_019 107293 3 636 142.2- 788.3 79 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_021 106922 3 643 134.1- 755.0 75 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_006 106406 3 622 107.3- 1,036.6 83 4 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_022 106335 3 636 131.7- 898.3 69 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_018 106334 3 633 133.8- 658.2 73 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_023 105699 3 637 136.5- 822.5 76 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_008 105674 3 628 138.8- 896.9 67 3 RFC LTP/SLTPRD_LTP_01|/1LT/IUC_LOAD_MT_004_024 105196 3 630 138.1- 771.6 71 3

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.

16

7 SAP System Operating LTP

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

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

17

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

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

7.4 Transports Transports were not found in the period analyzed.

7.5 Program Errors (ABAP Dumps) 5 ABAP dumps have been recorded in your system in the period 04/13/2015 to 04/20/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/13/2015 1

04/14/2015 1

04/15/2015 0

04/16/2015 0

04/17/2015 1

04/18/2015 0

04/19/2015 0

04/20/2015 2

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

SYSTEM_CORE_DUMPED 1 SLTPRD_LTP_01 KEITH 04/14/2015 11:39:40

SYSTEM_CANCELED 4 SLTPRD_LTP_01 KEITH 04/20/2015 00:00:08

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.

18

8 Security

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 HAP

SAP HANA Password Policy HAP

SAP HANA Audit Trail HAP

SAP HANA SQL Trace Level HAP

Default Passwords of Standard Users LTP

Control of the Automatic Login User SAP* LTP

Protection of Passwords in Database Connections LTP

ABAP Password Policy LTP

Gateway and Message Server Security LTP

Users with Critical Authorizations LTP

8.1 SAP HANA Database HAP

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

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

19

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.

8.2 ABAP Stack of LTP

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

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

8.2.3 ABAP Password Policy

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

8.2.3.1 Password Complexity

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

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

20

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

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 sltprd_LTP_01 0

login/min_password_letters sltprd_LTP_01 0

login/min_password_lowercase sltprd_LTP_01 0

login/min_password_uppercase sltprd_LTP_01 0

login/min_password_specials sltprd_LTP_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.

8.2.3.2 Validity of Initial Passwords

Rating Parameter Instance Current Value(s)

login/password_max_idle_initial sltprd_LTP_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.

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

8.2.4.1 Super User Accounts

21

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.

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

000 6 7

001 8 10

Authorization profile: SAP_ALL

9 Software Change and Transport Management of LTP

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

9.1 SAP Netweaver Application Server ABAP of LTP

Rating Check Performed

Number of Changes

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

No changes have been reported for the ABAP stack in the last week.

10 Data Volume Management (DVM)

22

A statement regarding Data Volume Management on your system LTP 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 LTP 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 LTP. However, the database size or growth per year could not be collected. As a consequence, a statement regarding Data Volume Management in your system LTP could not be provided.

11 Database Performance for LTP

No major performance problems were found in your database system.

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

23

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 161532 12.54 479293 0.26 3.18 7.50

File ID 2 454 0.04 179084466 98.26 1.88 14.16

File ID 3 160341 12.45 380295 0.21 2.74 10.60

File ID 4 163274 12.68 417743 0.23 2.86 7.84

File ID 5 160394 12.45 425309 0.23 2.68 7.26

File ID 6 159519 12.38 406996 0.22 2.65 6.50

File ID 7 161549 12.54 372688 0.20 2.74 8.34

File ID 8 159911 12.41 375899 0.21 2.84 9.85

File ID 9 161181 12.51 311894 0.17 2.92 7.37

Total 1288155 100 182254583 100 1.89 8.16 IO related wait events

Wait type Wait time (ms) Requests Wait time /

Requests Reference Value Rating

Analysis timeframe (ms): 2,213,446,900

WRITELOG 719,297,790 235,186,670 3.06 6.00

ASYNC_IO_COMPLETION 10,562,348 470 22,473.08 IO_COMPLETION 1,486,024 2,119,094 0.70 PAGEIOLATCH_SH 1,456,196 141,941 10.26 15.00

PAGEIOLATCH_EX 910,527 79,376 11.47 PAGEIOLATCH_UP 299,395 46,446 6.45

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

24

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.

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.

Wait type Wait time (ms) Requests Wait time /

Requests Rating

Analysis timeframe (ms): 2,213,446,900

WRITELOG 719,297,790 235,186,670 3.06

LCK_M_S 285,783,070 4,061 70,372.59

ASYNC_NETWORK_IO 158,792,450 230,602,850 0.69

LCK_M_X 80,142,768 313,867 255.34

LCK_M_U 58,409,168 3,610,764 16.18

BACKUPIO 16,254,290 2,105,182 7.72

BACKUPTHREAD 12,270,498 31,895 384.72

ASYNC_IO_COMPLETION 10,562,348 470 22,473.08

BACKUPBUFFER 7,999,950 2,411,622 3.32

SOS_SCHEDULER_YIELD 2,624,719 1,124,990,300 0.00

11.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 LTP.

25

12 Database Administration for LTP

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.

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

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

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

26

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:

Database File Name Growth activated?

Growth not restricted?

Next 2 steps possible?

Next step size

Free Space on File

Data file full?

Rating

E:\LTPDATA1\LTPDATA1.mdf

60.00 MB

701 MB

E:\LTPDATA2\LTPDATA2.ndf

60.00 MB

711 MB


60.00 MB

708 MB


60.00 MB

714 MB


60.00 MB

713 MB


60.00 MB

706 MB


60.00 MB

711 MB


60.00 MB

711 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 LTP:

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

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

27

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

Transaction Log File Name

Growth activated?


Next step possible?

Next step size

E:\LTPLOG1\LTPLOG1.ldf

10.00 %

The log file settings in system LTP are correct.

12.1.4 Tempdb Size and Settings

In an R/3 system, some actions (such as DBCC checkdb) and complex statements with JOIN and aggregate functions use a lot of space in database tempdb, depending on the size of the database and tables. In some cases, the database tempdb may grow up to several gigabytes while such actions are running. Therefore, it is important to monitor the actual size of tempdb and to provide enough disk space for it.

File Name Growth activated?


Next step possible?

Next step size

File size

Initial file size

Growth restricted to

Free on partition Rating

tempdb.mdf

10.00 %

512 MB

512 MB no limit 3755 MB

tempdev_02.ndf

1.00 MB

512 MB


tempdev_03.ndf

1.00 MB

512 MB


tempdev_04.ndf

1.00 MB

512 MB


tempdev_05.ndf

1.00 MB

512 MB


tempdev_06.ndf

1.00 MB

512 MB


tempdev_07.ndf

1.00 MB

512 MB


tempdev_08.ndf

1.00 MB

512 MB


tempdev_09.ndf

1.00 MB

512 MB


tempdev_10.ndf

1.00 MB

512 MB


tempdev_11.ndf

1.00 MB

512 MB


28



Next step possible?

Next step size

File size

Initial file size



tempdev_12.ndf

1.00 MB

512 MB


tempdev_13.ndf

1.00 MB

512 MB


tempdev_14.ndf

1.00 MB

512 MB


tempdev_15.ndf

1.00 MB

512 MB


tempdev_16.ndf

1.00 MB

512 MB


tempdev_17.ndf

1.00 MB

512 MB


tempdev_18.ndf

1.00 MB

512 MB


tempdev_19.ndf

1.00 MB

512 MB


tempdev_20.ndf

1.00 MB

512 MB


tempdev_21.ndf

1.00 MB

512 MB


tempdev_22.ndf

1.00 MB

512 MB


tempdev_23.ndf

1.00 MB

512 MB


tempdev_24.ndf

1.00 MB

512 MB


tempdev_25.ndf

1.00 MB

512 MB


tempdev_26.ndf

1.00 MB

512 MB


tempdev_27.ndf

1.00 MB

512 MB


tempdev_28.ndf

1.00 MB

512 MB


29



Next step possible?

Next step size

File size

Initial file size



tempdev_29.ndf

1.00 MB

512 MB


tempdev_30.ndf

1.00 MB

512 MB


tempdev_31.ndf

1.00 MB

512 MB


tempdev_32.ndf

1.00 MB

512 MB


templog.ldf

10.00 %

259 MB 0 MB no limit 3755 MB

Space Usage Size (MB)

Database size 16384

free in partition E 3755

DB size + free in partitions 20139

Transaction log size 259

free in partition E 3755

Log Size + Free in Partitions 4014

Recommendation: Configure the database files to grow automatically in steps of at least 30 MB or 10% of the tempdb size. Do not specify a growth limit. Configure the transaction log files to grow automatically in steps of at least 6 MB or 10% of the log size. To ensure that the tempdb can grow automatically, make sure that there is enough free space on the drive where the files of database tempdb are located.

Recommendation: Ensure that the data and log files of database tempdb do not need to grow. If the 'File size' (current size of the file) is larger than the 'Initial file size' (initial size of the file), the database expanded since the last database restart. For performance reasons, you should avoid this by setting the initial data size to a value that is larger than the 'File size'.

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

12.2.1 Database Options

30

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 LTP, is not set according to SAP standards.

Recommendation: Set the recovery model of the LTP 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 LTP database completely.

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

12.3.1 Database Growth

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

12.3.2 Largest Tables

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

Table Name Data (kB)

Reserved (data + indexes) kB

Used (data + indexes) kB Rows Modified

Rows

REPOLOAD 3141744 3151552 3147088 103117 11618

REPOSRC 2222792 2305344 2294408 1243524 53793

31

Table Name Data (kB)

Reserved (data + indexes) kB

Used (data + indexes) kB Rows Modified

Rows

BALDAT 1453760 1476608 1476376 1710102 65018

sap_perfinfo 1249912 1333632 1324792 1777182 26031

D010TAB 221488 737600 736224 10511800 347730

DOKCLU 342832 348736 348496 466870 47480

D010INC 134752 345024 343744 4140149 218848

/SLOAP/CLU_STORT 328568 341696 341552 92713 25071

DD03L 75224 333312 322816 1135648 103120

SMIMCONT1 293464 309376 306376 112698 12626

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

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

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.

12.3.5 SAP Notes for SQL Server

32

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

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

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

13 SAP HANA - Technology for HAP

33

We have checked your SAP HANA environment and found some issues that might have a negative impact on your overall system stability. 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

Size and Growth

Administration

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

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

Version Current SAP HANA DB Version

34

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

hanaprd hanaprd 32 504.90 2.00 MASTER MASTER

13.3 SAP HANA Stability and Alerts

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

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

1,060 4

0 Identifies internal statistics server problem. 6,290 5

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

700 3

20 Determines the growth rate of non-partitioned columns tables. 10 4

59 Determines the percentage of transactions that are blocked. 1 3

3 Identifies inactive services. 1 4

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

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

35

Alerts Alert ID Alert No. of

Occurrences Highest Rating

43 Determines what percentage of its effective allocation limit a service is using. 1 3

46 Identifies new runtime dump files (*rtedump*) have been generated in the trace directory of the system. These contain informatio

1 3

42 Identifies long-idling cursors. 15 4 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

3 Investigate why the service is inactive, for example, by checking the service's trace files. 1902033

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

20 Consider partitioning the table. For details please refer to the chapter "Size and Growth". 1910140

42 Close the cursor in the application, or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION <LOGI

1849392, 1900261

43 Check for services that consume a lot of memory. 1900257, 1840954

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

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

59 Investigate blocking and blocked transactions and if appropriate cancel some of them.

62 Change the password of the database user.

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

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

Date Crash dumps OOM dumps Emergency dumps

04/14/2015 1 1 0

04/18/2015 4 0 0

36

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.

13.3.3 SAP HANA services restarts

Critical SAP HANA database services were down.

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

During the last week, critical HANA database services (index server or name server) were down.

Recommendation: Check the index server trace file and, if available, the crash dump file or the index server out of memory files for errors. Open a customer message on the component HAN-DB*, if necessary.

13.4 SAP HANA Database Configuration

13.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 persistence

DEFAULT yes yes

lock_wait_timeout indexserver.ini: section transaction

DEFAULT 1800000 <between 100000 and 7200000>

log_backup_timeout_s global.ini: DEFAULT 900 <between 300

37

Important SAP HANA Parameters

Parameter Location Layername Current Value

Recommended Value Rating SAP

Note section persistence

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

global_allocation_limit global.ini section: memorymanager 409600 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

enable nameserver.ini section: sld yes

13.4.2 Disk Configuration

There are no disk configuration issues.

Disk ID Device ID File system Host Path Usage

4 243984 nfs hanaprd /hanaprdback/log/ LOG_BACKUP

5 17207 ext3 hanaprd /usr/sap/HAP/HDB00/hanaprd/ TRACE

3 741816 xfs hanaprd /hana/log/HAP/ LOG

1 753303 ext3 hanaprd /hana/data/HAP/ DATA

2 243984 nfs hanaprd /hanaprdback/data/ DATA_BACKUP

38

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

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

hanaprd Intel(R) Xeon(R) CPU X7560 @ 2.27GHz 2260 Dell Inc.

13.4.4 Trace Settings

All trace levels 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 Default Default

SQL Trace Inactive Inactive

Expensive Statements Trace Inactive Inactive

Performance Trace Inactive Inactive

End-to-End Traces Default Default

Other Traces Default Default

The trace levels of the displayed components are set to the default values that are appropriate for a production landscape. No changes are required.

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.

13.5 Size and Growth

39

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.

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

hanaprd 1,026.00 345.00 66.00 LOG_BACKUP+DATA_BACKUP nfs

hanaprd 34.00 15.00 55.00 TRACE ext3

hanaprd 504.00 377.00 25.00 LOG xfs

hanaprd 886.00 291.00 67.00 DATA ext3

13.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 997 Indexes of Colum Tables 494 Row Tables 415 Indexes of Row Tables 45

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)

YWI224 CPE_COURSE_HISTORY 670 771

YWI224 CCC 670 771

STAGING_AREA CPE_STUDENT_HISTORY_BU 433 482

JADLE2 HRP1001Copy 382 501

YWI224 DEMOGRAPHICS1 303 325

40

Schema Name Table Name Table Size (MB)

Table Size alloc (MB)

YWI224 DEMOGRAPHICS2 303 325

ACTIVE_ANALYSIS EVENT_ENROLLMENT 275 299

JADLE2 HRP1702Copy 245 281

CPE CPE_DEGREES_HISTORY_BU 151 167

ACTIVE_ANALYSIS EVENT_STATS_PER_TERM 149 152

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.

Largest Column Tables according to Size Schema Name Table Name Partition

ID Memorysize (Total) [MB]

BBCORE ACTIVITY_ACCUMULATOR 0 8,621 SAPECC HRP1001 0 3,484 UKMOBILE MESSAGE_REFERENCEKEY_TEMP 0 2,074 STUDENT EVENT_COLLECTIONS 0 2,001 SAPECC DFKKOP 0 1,039 SAPECC PIQDBPI_PINDEX 0 916 SAPECC DFKKOPK 0 898 SAPECC PIQDBAGR_GEN 0 819 SAPECC HRT1721 0 340 SAPECC DFKKKO 0 293

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 exceeds or is close to the defined thresholds.

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 BBCORE ACTIVITY_ACCUMULATOR 620,735,629

UKMOBILE MESSAGE_REFERENCEKEY_TEMP 283,272,758

CORE ROOM_UTILIZATION 178,341,120

CROSS_REF EVENT_COLLECTIONS_OLD 156,132,587

41

Largest Non-partitioned Column Tables According To Records Schema Name Table Name Records (Total) Rating STUDENT ROOM_UTILIZATION 154,667,520

STUDENT_TEMP ROOM_UTILIZATION 151,750,177

CORE EVENT_COLLECTIONS 147,524,959

STUDENT EVENT_COLLECTIONS 147,524,959

SAPECC HRP1001 59,509,048

CORE EVENTS_DETAIL_ROLLUP 50,877,625

There are objects with high number of records (more than 300 million). This is not yet critical with regard to the technical limit of SAP HANA (2 billion records), but table partitioning should be considered if these tables are expected to grow rapidly in the future.

Recommendation: Consider partitioning for tables that are expected to grow rapidly in order to ensure parallelization and adequate performance. We recommend that you partition tables before inserting mass data or while they are still small. For more information, see SAP Note 1650394 or refer to the SAP HANA Administration Guide (http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf).

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

hanaprd_HAP_00 MASTER

Some of the SAP HANA hardware resources are not sufficient for the current workload. This may lead to performance and stability issues. Details of resource consumption issues are listed in the sections below.

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

42

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]

hanaprd_HAP_00 400

13.6.2 HANA Instance hanaprd_HAP_00

CPU Usage of HANA server

The average CPU usage of the SAP HANA server exceeds 75%. This may have an impact on SAP HANA performance.

The graphics below show the average and maximum CPU consumption per hour. The data is obtained from the statistics tables of the SAP HANA database. If the average CPU consumption exceeds 75%, a YELLOW rating is assigned. If it exceeds the threshold of 90%, a RED rating is assigned.

43

Within the analyzed period, we observed an average 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 average CPU consumption.

Memory Usage of HANA server

No memory bottlenecks were detected.

The following graph shows the physical memory usage during the monitored timeframe. The average and maximum memory used by SAP HANA (and possibly other processes) is compared with the available physical memory of the SAP HANA server.

No critical issues were detected in this area.

Memory Allocation of Tables

44

The memory consumption of tables is below any critical threshold.

This graphic shows the average memory consumption for storing row and column tables, and the memory available for temporary calculations and other operations.

From a SAP HANA sizing perspective, it is recommended that the memory usage for SAP HANA tables remains below 50% of the global allocation limit.

If the memory usage for SAP HANA tables reaches 70% of the global allocation limit, the remaining memory resources for temporary calculations may be too small.

13.7 SAP HANA Workload and Performance

13.7.1 SAP HANA Response Times

45

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.

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)

13.7.2 SAP HANA Column Unloads

46

Column unloads were detected during the time period analyzed.

The following graph shows column unloads in the SAP HANA system during the monitored timeframe. It displays data from a maximum of 10 hosts.

Column unloads with reason "Low Memory" indicate that there was not sufficient SAP HANA memory available for working operations. This can be due to a number of different reasons: Either the memory for the working space is too small or one or more expensive memory operations were occupying the complete SAP HANA memory. The SAP HANA memory remaining for working operations is currently sufficient, but may become critical.

Recommendation: Monitor the SAP HANA memory consumption closely and identify and optimize applications with high memory consumption.

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

Memorysize in Main Store [MB]

Memorysize in Delta Store [MB]

Records in Delta Store

Sum of Records

BBCORE ACTIVITY_ACCUMULATOR 0 8,495 127 1,338,028 620,735,629 UKMOBILE MESSAGE_REFERENCEKEY_TEMP 0 2,006 68 1,201,302 283,272,758 SAPECC HRP1001 0 3,419 65 214,061 59,509,048 SAPECC PIQDBPI_PINDEX 0 893 23 102,334 13,216,590 ECHO PRESENTATION_PRESENTER 0 93 11 118,495 18,761,667

47

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 1,035 4 4,226 16,607,917 SAPECC DFKKOPK 0 894 4 15,978 32,512,831 SAPECC DFKKKO 0 291 2 6,524 12,812,431 SAPECC PIQDBAGR_GEN 0 818 1 4,781 10,322,201 SAPECC HRT1721 0 339 1 3,703 13,467,843

13.8 Administration

13.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 hanaprd Weekly Log 4 43.95 hanaprd Weekly Trace 15 126.07 hanaprd Weekly Dump 6 27.69 hanaprd Unlimited TOTAL 47 227.11

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.

13.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 491 0 04/14/2015 Tuesday 629 0 04/15/2015 Wednesday 621 0 04/16/2015 Thursday 619 0 04/17/2015 Friday 661 0 04/18/2015 Saturday 627 0 04/19/2015 Sunday 617 0 Data Backup History Date Weekday Successful Data Backups Unsuccessful Data Backups

48

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

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

HAP 0020598649 TRUE TRUE SAP-HANA 256

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

49

SAP Notes for SAP HANA SAP Note Description

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 .

14 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

14.1 SLT Configuration

14.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).

50

Configuration Overview

Configuration Name

Mass Transfer ID

Source System Type

Source System Destination System Type

Destination System

SAPECC 004 SAP r3prda02_R3P_02 HDB hanaprd.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

14.1.2 Background Job Configuration


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

Configuration Name

Mass Transfer ID

Initial Load Jobs Configured

Data Transfer Jobs Configured

Data Transfer Jobs Calculated

Rating

SAPECC 004 15 25 16

TOTAL 15 25 16 Configured Background Work Processes Instance Name

Operation Mode

No. of BTC Work Processes

No. of BTC Work Processes (class A)

SLTPRD_LTP_01 DUMMY 40 0

51

Configured Background Work Processes Instance Name

Operation Mode

No. of BTC Work Processes

No. of BTC Work Processes (class A)

TOTAL DUMMY 40 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.

14.1.3 Background Job Scheduling


All background jobs for data replication are running correctly.

14.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).

Replicated Tables Configuration Name

Mass Transfer ID

Replication Mechanism

Replication Status

Number of Tables

SAPECC 004 Replication In Process 154

SAPECC 004 Load tables (Initial Load) Executed 125

14.1.5 Replication Errors


No replication errors were detected.

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

14.2 SLT Performance

14.2.1 Performance Statistics


52


Performance statistics are not reliable.

The graphics below provide performance and throughput statistics for data replication. The SLT replication performance is measured by latency. This latency is measured from the trigger until the point at which the table is stored in the SAP HANA database. For sufficient SLT replication performance, the median latency should not exceed 5 seconds.

Note: The calculated replication latency also considers the initial load. For this reason, the latency may be higher during the first 24 hours after the successful completion of the initial load.

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

SAP KBA Description

1971400 SLT Schema Latency (Replication Statistics)

We found negative latency times in the system. This is because the source and SLT system are not synchronized in terms of OS time. Therefore, the latency measurements are not reliable.

Recommendation: We recommend ensuring time synchronization between the source and SLT system. For more information, see SAP Note 1740419 - Time synchronization of SAP system and time stamps.

15 Database server load from expensive SQL statements - LTP

53

The SQL statements identified did not lead to performance problems. The load overview is listed in the table below for reference, and further details of the most expensive statements are included at the end of the section.

Database Load From Expensive Statements Rating Logical reads [%] Physical reads [%] Elapsed time [%]

92 4 83

The table above shows the cumulative amount of problematic statements identified. If the database was inactive for more than one day before the analysis was performed, the information provided may not be entirely accurate.

Note: The overall section rating is linked to the above table rating; the ratings are described in SAP Note 2021756. If the table rating is RED, there are SQL statements that cause a high percentage of the overall load on your SAP system. If the table rating is YELLOW, there are SQL statements that cause a considerable percentage of the overall load on your SAP system. If the table rating is GREEN, your system SQL statement cache contains no significant problems. If the table rating is UNRATED, the total reads of your system's SQL statement cache were <= 100,000,000, or some analysis data was unavailable.

The following table lists the load of each SQL statement individually. The load of the statement is evaluated against the total load since database startup.

Note: If an object name in this table contains the character "/", it may indicate a join. If an object is not in the ABAP Dictionary (transaction SE12) with the object name listed, check for each part of the join (items separated by "/").

16 Database and ABAP Load Optimization of LTP

We analyzed your SAP system and found expensive SQL statements or transaction design or performance problems. Follow the recommendations below to improve performance of this SAP system.

54

16.1 Analysis of DB SQL CACHE on 04/20/2015 04:33:55 Expensive SQL Statements Overview

Object Name Elapsed time [%]

Calls [%] Calls Total rows

Logical reads [%]

Physical reads [%]

CPU time [%]

BALHDR 77 3 140598947 46866488 87 0 86 DMC_FIELD 1 1 62929889 1189154226 2 0 1 DMC_FIELD 0 1 31464914 191298626 2 0 0 0 0 21659 463529 1 0 0 DMC_STREE 0 2 125859747 94395032 0 0 0 IUUC_RS_ORDER 2 0 352970 53946237 0 0 3 IUUC_RS_ORDER 2 0 352840 53926425 0 0 3 1 0 773754 773754 0 4 0 DMC_ACS_PLAN_HDR 0 4 205812295 31465029 0 0 0 DMC_ACS_PLAN_HDR 0 4 205812134 205813063 0 0 0

The statements were selected for analysis and optimization based on the "Logical reads [%]" column. Logical reads are a measure of the workload on a database server because they cause CPU and memory utilization.

The "Total Rows expected" column indicates the expected number of rows returned by the statement.

16.1.1 Access on BALHDR

Statement Data:

Cache Statistics

Object type

Total executions

Total elapsed time[ms]

Elapsed time[ms]/Record Records/Execution Estimated

Records/Execution

TABLE 140598947 3244480994 23.08 1 1

55

SELECT "MANDANT" AS c ,"LOGNUMBER" AS c ,"OBJECT" AS c ,"SUBOBJECT" AS c ,"EXTNUMBER" AS c ,"ALDATE" AS c ,"ALTIME" AS c , "ALUSER" AS c ,"ALTCODE" AS c ,"ALPROG" AS c ,"ALMODE" AS c ,"ALTEXT" AS c ,"USEREXITP" AS c ,"USEREXITF" AS c ,"PROBCLASS" AS c ,"ALDATE_DEL" AS c ,"DEL_BEFORE" AS c ,"ALSTATE" AS c ,"USEREXITT" AS c ,"ALCHDATE" AS c ,"ALCHTIME" AS c ,"ALCHUSER" AS c , "LOG_HANDLE" AS c ,"TABNAME" AS c ,"MSG_CNT_AL" AS c ,"MSG_CNT_A" AS c ,"MSG_CNT_E" AS c ,"MSG_CNT_W" AS c ,"MSG_CNT_I" AS c , "MSG_CNT_S" AS c ,"LAST_MSGNR" AS c ,"TIM_STMP" AS c ,"DB_VERSION" AS c ,"MSG_CNT_P1" AS c ,"MSG_CNT_P2" AS c ,"MSG_CNT_P3" AS c ,"MSG_CNT_P4" AS c ,"CLIENT_CRE" AS c ,"CHAR_SIZE" AS c FROM "BALHDR" WHERE "LOG_HANDLE" = @P1 AND "MANDANT" = @P2 /* R3:SAPLSBAL_DB:190 T:BALHDR */

Execution Plan Estimated rows: 1,0000000000000 Subtree costs: 0,0032831000000 |-- Clustered Index Seek SEEK: [BALHDR].MANDANT EQ [@P2] ORDERED 1 WHERE: [LTP].[ltp]. [BALHDR].[LOG_HANDLE]=[@P1] |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001581000000 |--Subtree costs: 0,0032831000000

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On LSBAL_DBU04 0000081 SAP SAP 02/26/2014

0000072 DELETE ADJACENT DUPLICATES FROM l_t_balhdr_all. 0000073 DESCRIBE TABLE l_t_balhdr_all LINES lines_specified. 0000074 * no select necessary, table is already filled 0000075 ELSEIF NOT i_t_log_handle IS INITIAL. 0000076 DESCRIBE TABLE i_t_log_handle LINES lines_specified. 0000077 0000078 CLEAR l_t_balhdr_all. 0000079 SELECT mandt FROM t000 INTO l_mandt. "mav1762906 0000080 *>>>>>>>>>>>>>>>>> 0000081 SELECT * FROM balhdr CLIENT SPECIFIED 0000082 APPENDING TABLE l_t_balhdr_all 0000083 FOR ALL ENTRIES IN i_t_log_handle 0000084 WHERE log_handle = i_t_log_handle-table_line 0000085 AND mandant = l_mandt. 0000086 0000087 ENDSELECT. *<<<<<<<<<<<<<<<<<< 0000088 0000089 ELSEIF NOT i_t_lognumber IS INITIAL. 0000090 DESCRIBE TABLE i_t_lognumber LINES lines_specified.

16.1.2 Access on DMC_FIELD

56

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 62929889 28412828 0.02 19 20

SELECT "GUID" AS c ,"DSTRUCTURE" AS c ,"FORKEYFELD" AS c ,"FIELDNAME" AS c ,"IDENT" AS c ,"KEYFLAG" AS c ,"SCRTEXT_L" AS c , "SUPPLY_STATUS" AS c ,"RULECALL" AS c ,"SPLIT" AS c ,"VERSIO" AS c ,"CHNAM" AS c ,"CHANGEDATE" AS c ,"AUTHOR" AS c , "CREATEDATE" AS c ,"DESCR" AS c ,"LEN" AS c ,"OUTPUTLEN" AS c ,"DECS" AS c ,"POS" AS c ,"INTTYPE" AS c ,"DATATYPE" AS c , "IDFIELD" AS c ,"IDCHAR" AS c ,"GCHANGE" AS c ,"GCHGKIND" AS c ,"TYP_PROP" AS c ,"CHECKTABLE" AS c ,"GCCHAR" AS c ,"SELPAR" AS c ,"AGGREG" AS c ,"TECHNICAL" AS c ,"DOMNAME" AS c ,"ROLLNAME" AS c ,"SEQNR" AS c ,"NOT_INITIAL" AS c ,"UPDATE_LOCK" AS c FROM "DMC_FIELD" WHERE "DSTRUCTURE" = @P1 /* R3:CL_DMC_STRUCTFIELD_LIST=======CP:1648 T:DMC_FIELD */

Execution Plan Estimated rows: 20,000000000000 Subtree costs: 0,0633643000000 |-- Nested Loops |--Estimated rows: 20,000000000000 |--Estimated CPU costs: 0,0000836000000 |--Subtree costs: 0,0633643000000 |-- Index Seek SEEK: [DMC_FIELD].DSTRUCTURE EQ [@P1] ORDERED 1 |--Estimated rows: 20,000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001790000000 |--Subtree costs: 0,0033040000000 |-- Clustered Index Seek SEEK: [DMC_FIELD].GUID EQ [LTP].[ltp].[DMC_FIELD].[GUID] ORDERED 1 |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001581000000 |--Subtree costs: 0,0599767000000

57

Program Data:

Origin of ABAP coding

Program Name Line Created By

Last Changed By

Last Changed On

CL_DMC_STRUCTFIELD_LIST=======CM004 0000099 SAP SAP 03/21/2015

0000090 nametab_check_s = '-'. 0000091 ENDIF. 0000092 ENDIF. 0000093 ENDIF. 0000094 0000095 * Wenn die Struktur eben kopiert wird, dann brauchen wir den folgenden 0000096 * Programteil nicht: 0000097 IF im_for_copy NE dmct_true. 0000098 *>>>>>>>>>>>>>>>>> 0000099 SELECT * FROM dmc_field INTO TABLE fields 0000100 WHERE dstructure = my_data_structure->if_dmc_pobject~guid. 0000101 0000102 IF my_data_structure->from_ddic CA '1X' AND fields IS INITIAL. *<<<<<<<<<<<<<<<<<< 0000103 0000104 IF im_create_technical_fields = dmct_true. 0000105 * Technische Felder aus der Struktur EDI_DD40 einlesen

16.1.3 Access on DMC_FIELD

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 31464914 12346276 0.06 6 54

SELECT "GUID" AS c ,"DSTRUCTURE" AS c ,"FORKEYFELD" AS c ,"FIELDNAME" AS c ,"IDENT" AS c ,"KEYFLAG" AS c ,"SCRTEXT_L" AS c ,

58

"SUPPLY_STATUS" AS c ,"RULECALL" AS c ,"SPLIT" AS c ,"VERSIO" AS c ,"CHNAM" AS c ,"CHANGEDATE" AS c ,"AUTHOR" AS c , "CREATEDATE" AS c ,"DESCR" AS c ,"LEN" AS c ,"OUTPUTLEN" AS c ,"DECS" AS c ,"POS" AS c ,"INTTYPE" AS c ,"DATATYPE" AS c , "IDFIELD" AS c ,"IDCHAR" AS c ,"GCHANGE" AS c ,"GCHGKIND" AS c ,"TYP_PROP" AS c ,"CHECKTABLE" AS c ,"GCCHAR" AS c ,"SELPAR" AS c ,"AGGREG" AS c ,"TECHNICAL" AS c ,"DOMNAME" AS c ,"ROLLNAME" AS c ,"SEQNR" AS c ,"NOT_INITIAL" AS c ,"UPDATE_LOCK" AS c FROM "DMC_FIELD" WHERE "DSTRUCTURE" = @P1 AND "FORKEYFELD" <> @P2 /* R3:CL_DMC_FORKEY_LIST============CP:661 T:DMC_FIELD */

Execution Plan Estimated rows: 54,082400000000 Subtree costs: 0,1584010000000 |-- Nested Loops |--Estimated rows: 54,082400000000 |--Estimated CPU costs: 0,0002260640000 |--Subtree costs: 0,1584010000000 |-- Index Seek SEEK: [DMC_FIELD].DSTRUCTURE EQ [@P1] ORDERED 1 |--Estimated rows: 54,082400000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0002164910000 |--Subtree costs: 0,0033414900000 |-- Clustered Index Seek SEEK: [DMC_FIELD].GUID EQ [LTP].[ltp].[DMC_FIELD].[GUID] ORDERED 1 WHERE: [LTP].[ltp].[DMC_FIELD].[FORKEYFELD]<[@P2] OR [LTP].[ltp]. [DMC_FIELD].[FORKEYFELD]>[@P2] |--Estimated rows: 2,8079800000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001581000000 |--Subtree costs: 0,1548330000000

Program Data:



Last Changed By

Last Changed On

CL_DMC_FORKEY_LIST============CM007 0000013 SAP SAP 09/23/2013

0000004 0000005 wa_fields TYPE dmc_field, 0000006 wa_forkey TYPE dmc_forkey, 0000007 wa_val TYPE dmc_forkey_rec. 0000008 0000009 CLEAR: _vals, 0000010 _dbvals. 0000011 0000012 * get all foreign key relations in DMC_FIELD *>>>>>>>>>>>>>>>>> 0000013 SELECT * FROM dmc_field 0000014 INTO CORRESPONDING FIELDS OF TABLE lt_fields 0000015 WHERE dstructure = my_owner->if_dmc_pobject~guid 0000016 AND forkeyfeld <> space. 0000017 0000018 * get foreign key from DMC_FORKEY *<<<<<<<<<<<<<<<<<< 0000019 LOOP AT lt_fields INTO wa_fields. 0000020 * SELECT SINGLE * FROM dmc_forkey INTO wa_forkey 0000021 * WHERE guid = wa_fields-forkeyfeld. (DEL) MH000040

59

16.1.4 Access on

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

JOIN 21659 1208969 2.61 21 1

SELECT "KMC_UWL_SITEM"."ITEM_ID","I_CONNECTOR_ID","SYSTEM_ID","EXTERNAL_ID","KMC_UWL_SITEM"."USER_ID","APP_CONTEXT", "ATTACHMENT_COUNT","CREATED_DATE","CREATOR_ID","DUE_DATE","EXTERNAL_OBJECT_ID","EXECUTION_URL","EXTERNAL_TYPE","EXPIRY_DATE", "FLAGS","ITEM_TYPE","PRIORITY","PROCESSOR","STATUS","SUBJECT","DELETED_FLAG","SUBSTITUTED_FOR","USER_ACTION_FLAG" FROM "KMC_UWL_SITEM", "KMC_UWL_ITEMS2" WHERE "KMC_UWL_SITEM"."ITEM_ID" = "KMC_UWL_ITEMS2"."ITEM_ID" AND "KMC_UWL_SITEM"."USER_ID" = @P0 AND ("ITEM_TYPE" = @P1 OR "ITEM_TYPE" LIKE @P2) AND "I_CONNECTOR_ID" = @P3 AND "SYSTEM_ID" = @P4;

Execution Plan Statement not in LTP

SQL Scripts

This statement comes from an expensive SQL script or from a stored procedure (SP) which exists at DB level and is not originated from the ABAP stack. We cannot analyze this statement in detail. Recommendation: Check if: a) The script or SP has to be run at all. b) The script or SP can be run less frequently. c) The script or SP can be tuned so that it consumes fewer database resources.

16.1.5 Access on DMC_STREE

60

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 125859747 9930874 0.08 1 1

SELECT "GUID" AS c ,"CONTAINER" AS c ,"STYPE" AS c ,"SEQNUM" AS c ,"IDENT" AS c ,"STRUCT" AS c ,"FILEDESC" AS c ,"PREC" AS c , "VERSIO" AS c ,"CHNAM" AS c ,"STRUCLEVEL" AS c ,"PARENTID" AS c ,"CHANGEDATE" AS c ,"AUTHOR" AS c ,"CREATEDATE" AS c ,"DESCR" AS c ,"REFNAME" AS c ,"STREE_TYPE" AS c FROM "DMC_STREE" WHERE "CONTAINER" = @P1 AND "PARENTID" = @P2 /* R3:CL_DMC_STRUCT_TREE_LIST=======CP:2714 T:DMC_STREE */

Execution Plan Estimated rows: 1,0000000000000 Subtree costs: 0,0065703800000 |-- Nested Loops |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000041800000 |--Subtree costs: 0,0065703800000 |-- Index Seek SEEK: [DMC_STREE].CONTAINER EQ [@P1] ORDERED 1 |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001581000000 |--Subtree costs: 0,0032831000000 |-- Clustered Index Seek SEEK: [DMC_STREE].GUID EQ [LTP].[ltp].[DMC_STREE].[GUID] AND [DMC_STREE].CONTAINER EQ [LTP].[ltp].[DMC_STREE].[CONTAINER] AND [DMC_STREE]. STYPE EQ [LTP].[ltp].[DMC_STREE].[STYPE] ORDERED 1 WHERE: [LTP].[ltp].[DMC_STREE]. [ |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001581000000 |--Subtree costs: 0,0032831000000

Program Data:

61



Last Changed By

Last Changed On

CL_DMC_STRUCT_TREE_LIST=======CM00Q 0000013 SAP SAP 09/23/2013

0000004 stree_tab TYPE dmc_struct_tree_rel_tab, 0000005 street_text_tab TYPE STANDARD TABLE OF dmc_street, 0000006 wa TYPE dmc_strec, 0000007 wa_dmc_street TYPE dmc_street, 0000008 buf TYPE dmct_struct_tree_rel. 0000009 0000010 0000011 CLEAR: _vals, _dbvals. 0000012 *>>>>>>>>>>>>>>>>> 0000013 SELECT * FROM dmc_stree INTO TABLE stree_tab 0000014 WHERE container = my_struct_tree_factory->my_container->guid 0000015 AND parentid = my_struct_tree_factory->guid. 0000016 0000017 IF sy-dbcnt > 0 AND cl_dmc_conv_object=>source_type < cl_dmc_super_conv_object=>co_source_cwb. *<<<<<<<<<<<<<<<<<< 0000018 *** load description 0000019 SELECT * FROM dmc_street INTO TABLE street_text_tab 0000020 FOR ALL ENTRIES IN stree_tab

16.1.6 Access on IUUC_RS_ORDER

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 352970 98605552 1.83 153 300

SELECT T_00 ."TABLE_NAME" "TABLENAME" ,T_00 ."ACTION" AS c FROM "IUUC_RS_ORDER" T_00 ,(SELECT "C_01" = @P1 UNION SELECT @P2 ) T_01

62

WHERE T_00 ."MT_ID" = @P3 AND T_00 ."STATUS" = @P4 AND T_00 ."ACTION" = T_01 .C_01 AND T_00 ."IS_LAST" = @P5 /* R3: CL_IUUC_RS_ORDER_ACCESS=======CP:290 T:IUUC_RS_ORDER */

Execution Plan Estimated rows: 300,17900000000 Subtree costs: 3,1576300000000 |-- Nested Loops |--Estimated rows: 300,17900000000 |--Estimated CPU costs: 0,0013293200000 |--Subtree costs: 3,1576300000000 |-- Clustered Index Seek SEEK: [IUUC_RS_ORDER].MT_ID EQ [@P3] ORDERED 1 WHERE: [LTP]. [ltp].[IUUC_RS_ORDER].[STATUS] as [T_00].[STATUS]=[@P4] AND [LTP].[ltp]. [IUUC_RS_ORDER].[IS_LAST] as [T_00].[IS_LAST]=[@P5] |--Estimated rows: 318,01800000000 |--Estimated I/O costs: 1,2164600000000 |--Estimated CPU costs: 1,0774500000000 |--Subtree costs: 2,2939000000000 |-- Top |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000001000000 |--Subtree costs: 0,0005344280000 |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000002000000 |--Subtree costs: 0,0005026260000 |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P1] |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000004800000 |--Subtree costs: 0,0004708240000 |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000011570000 |--Subtree costs: 0,0003181750000 |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P2] |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000004800000 |--Subtree costs: 0,0004708240000 |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000011570000 |--Subtree costs: 0,0003181750000

Program Data:



Last Changed By

Last Changed On

CL_IUUC_RS_ORDER_ACCESS=======CM005 0000027 SAP SAP 09/23/2013

0000018 0000019 * LOOP AT iv_actions INTO lwa_action. 0000020 * IF sy-tabix = 1. 0000021 * CONCATENATE lv_temp `'` lwa_action `'` INTO lv_temp. 0000022 * ELSE. 0000023 * CONCATENATE lv_temp `, '` lwa_action `'` INTO lv_temp. 0000024 * ENDIF. 0000025 * ENDLOOP. 0000026 * CONCATENATE `action in (` lv_temp `)` INTO lv_actions. *>>>>>>>>>>>>>>>>> 0000027 SELECT table_name AS tablename action 0000028 FROM iuuc_rs_order AS rs1 INTO CORRESPONDING FIELDS OF TABLE rt_rs_order 0000029 FOR ALL ENTRIES IN iv_actions

63

0000030 WHERE mt_id = iv_mt_id AND 0000031 status = co_status_obtain AND 0000032 * (lv_actions) and 0000033 action = iv_actions-table_line AND 0000034 * handltime = ( SELECT MAX( handltime ) 0000035 * FROM iuuc_rs_order 0000036 * WHERE mt_id = iv_mt_id AND 0000037 * status = co_status_obtain AND 0000038 * table_name = rs1~table_name ). 0000039 is_last = 'X'. 0000040 *<<<<<<<<<<<<<<<<<< 0000041 0000042 0000043 ENDMETHOD.

16.1.7 Access on IUUC_RS_ORDER

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 352840 98463332 1.83 153 1

SELECT T_00 ."TABLE_NAME" "TABLENAME" ,T_00 ."ACTION" AS c FROM "IUUC_RS_ORDER" T_00 ,(SELECT "C_01" = @P1 UNION SELECT @P2 UNION SELECT @P3 UNION SELECT @P4 UNION SELECT @P5 ) T_01 WHERE T_00 ."MT_ID" = @P6 AND T_00 ."STATUS" = @P7 AND T_00 ."ACTION" = T_01 .C_01 AND T_00 ."IS_LAST" = @P8 /* R3: CL_IUUC_RS_ORDER_ACCESS=======CP:290 T:IUUC_RS_ORDER */

Execution Plan |-- Nested Loops |-- Clustered Index Seek SEEK: [IUUC_RS_ORDER].MT_ID EQ [@P6] ORDERED 1 WHERE: [LTP]. [ltp].[IUUC_RS_ORDER].[STATUS] as [T_00].[STATUS]=[@P7] AND [LTP].[ltp]. [IUUC_RS_ORDER].[IS_LAST] as [T_00].[IS_LAST]=[@P8]

64

|-- Top |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P1] |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P2] |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P3] |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P4] |-- Filter WHERE: [LTP].[ltp].[IUUC_RS_ORDER].[ACTION] as [T_00].[ACTION]=[@P5]

Program Data:



Last Changed By

Last Changed On

CL_IUUC_RS_ORDER_ACCESS=======CM005 0000027 SAP SAP 09/23/2013

0000018 0000019 * LOOP AT iv_actions INTO lwa_action. 0000020 * IF sy-tabix = 1. 0000021 * CONCATENATE lv_temp `'` lwa_action `'` INTO lv_temp. 0000022 * ELSE. 0000023 * CONCATENATE lv_temp `, '` lwa_action `'` INTO lv_temp. 0000024 * ENDIF. 0000025 * ENDLOOP. 0000026 * CONCATENATE `action in (` lv_temp `)` INTO lv_actions. *>>>>>>>>>>>>>>>>> 0000027 SELECT table_name AS tablename action 0000028 FROM iuuc_rs_order AS rs1 INTO CORRESPONDING FIELDS OF TABLE rt_rs_order 0000029 FOR ALL ENTRIES IN iv_actions 0000030 WHERE mt_id = iv_mt_id AND 0000031 status = co_status_obtain AND 0000032 * (lv_actions) and 0000033 action = iv_actions-table_line AND 0000034 * handltime = ( SELECT MAX( handltime ) 0000035 * FROM iuuc_rs_order 0000036 * WHERE mt_id = iv_mt_id AND 0000037 * status = co_status_obtain AND 0000038 * table_name = rs1~table_name ). 0000039 is_last = 'X'. 0000040 *<<<<<<<<<<<<<<<<<< 0000041 0000042 0000043 ENDMETHOD.

16.1.8 Access on

65

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 773754 31338848 40.50 1 1

SELECT "COMPRESSED","CONTENT" FROM "KMC_DBRM_CONTENT" WHERE "ID" = @P0 /*@ sqlserver 'DRIVER LONGDATACACHESIZE=-1'*/;

Execution Plan Statement not in LTP

SQL Scripts

This statement comes from an expensive SQL script or from a stored procedure (SP) which exists at DB level and is not originated from the ABAP stack. We cannot analyze this statement in detail. Recommendation: Check if: a) The script or SP has to be run at all. b) The script or SP can be run less frequently. c) The script or SP can be tuned so that it consumes fewer database resources.

16.1.9 Access on DMC_ACS_PLAN_HDR

66

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 205812295 9844153 0.05 1 1

SELECT TOP 1 "OWNER" AS c ,"CONVOBJ" AS c ,"ID" AS c ,"GUID" AS c ,"DESCR" AS c ,"IS_CALCULATED" AS c ,"TS_CREATED" AS c , "TS_CHANGED" AS c ,"BLOCKSIZE" AS c ,"PREC_STATE" AS c ,"FAILED" AS c ,"IN_PROCESS" AS c ,"LOADED" AS c ,"TEMPLATE" AS c , "ORIGIN_ID" AS c ,"SUB_ID" AS c FROM "DMC_ACS_PLAN_HDR" WHERE "OWNER" = @P1 AND "ID" = @P2 AND "FAILED" = @P3 AND "IN_PROCESS" = @P4 AND "IS_CALCULATED" = @P5 AND "LOADED" = @P6 ORDER BY "OWNER" ,"CONVOBJ" ,"ID" /* R3:CL_DMC_ACCESS_PLAN_LIST=======CP:4841 T:DMC_ACS_PLAN_HDR */

Execution Plan Estimated rows: 1,0000000000000 Subtree costs: 0,0032846600000 |-- Top |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000001000000 |--Subtree costs: 0,0032846600000 |-- Clustered Index Seek SEEK: [DMC_ACS_PLAN_HDR].OWNER EQ [@P1] ORDERED 1 WHERE: [LTP].[ltp].[DMC_ACS_PLAN_HDR].[ID]=[@P2] AND [LTP].[ltp].[DMC_ACS_PLAN_HDR]. [FAILED]=[@P3] AND [LTP].[ltp].[DMC_ACS_PLAN_HDR].[IN_PROCESS]=[@P4] AND [LTP]. [ltp].[D |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001592000000 |--Subtree costs: 0,0032842000000

Program Data:

67



Last Changed By

Last Changed On

CL_DMC_ACCESS_PLAN_LIST=======CM01B 0000032 SAP SAP 12/07/2014

0000023 WHERE owner = l_cobj_guid 0000024 AND is_calculated = im_is_calculated 0000025 AND id = im_acp_id. 0000026 ENDSELECT. 0000027 IF sy-subrc NE 0. 0000028 RAISE id_not_exist. 0000029 ENDIF. 0000030 0000031 * get standard access plan of convobj by id *>>>>>>>>>>>>>>>>> 0000032 SELECT * FROM dmc_acs_plan_hdr INTO wa_acs_plan_hdr 0000033 UP TO 1 ROWS 0000034 WHERE owner = l_cobj_guid 0000035 AND id = im_acp_id 0000036 AND failed = im_failed 0000037 AND in_process = im_in_process 0000038 AND is_calculated = im_is_calculated 0000039 AND loaded = im_loaded 0000040 ORDER BY PRIMARY KEY. 0000041 ENDSELECT. 0000042 *<<<<<<<<<<<<<<<<<< 0000043 IF sy-subrc = 0. 0000044 wa_acs_plan_hdr-in_process = true. 0000045 UPDATE dmc_acs_plan_hdr FROM wa_acs_plan_hdr.

16.1.10 Access on DMC_ACS_PLAN_HDR

Statement Data:

Cache Statistics

Object type

Total executions



Records/Execution

68

Cache Statistics

Object type

Total executions



Records/Execution

TABLE 205812134 11117889 0.05 1 1

SELECT TOP 1 "OWNER" AS c ,"CONVOBJ" AS c ,"ID" AS c ,"GUID" AS c ,"DESCR" AS c ,"IS_CALCULATED" AS c ,"TS_CREATED" AS c , "TS_CHANGED" AS c ,"BLOCKSIZE" AS c ,"PREC_STATE" AS c ,"FAILED" AS c ,"IN_PROCESS" AS c ,"LOADED" AS c ,"TEMPLATE" AS c , "ORIGIN_ID" AS c ,"SUB_ID" AS c FROM "DMC_ACS_PLAN_HDR" WHERE "OWNER" = @P1 AND "IS_CALCULATED" = @P2 AND "ID" = @P3 /* R3:CL_DMC_ACCESS_PLAN_LIST=======CP:4797 T:DMC_ACS_PLAN_HDR */

Execution Plan Estimated rows: 1,0000000000000 Subtree costs: 0,0032843000000 |-- Top |--Estimated rows: 1,0000000000000 |--Estimated CPU costs: 0,0000001000000 |--Subtree costs: 0,0032843000000 |-- Clustered Index Seek SEEK: [DMC_ACS_PLAN_HDR].OWNER EQ [@P1] ORDERED 1 WHERE: [LTP].[ltp].[DMC_ACS_PLAN_HDR].[IS_CALCULATED]=[@P2] AND [LTP].[ltp]. [DMC_ACS_PLAN_HDR].[ID]=[@P3] |--Estimated rows: 1,0000000000000 |--Estimated I/O costs: 0,0031250000000 |--Estimated CPU costs: 0,0001592000000 |--Subtree costs: 0,0032838900000

Program Data:



Last Changed By

Last Changed On

CL_DMC_ACCESS_PLAN_LIST=======CM01B 0000021 SAP SAP 12/07/2014

0000012 IF sy-subrc <> 0. 0000013 RAISE owner_not_found. 0000014 ENDIF. 0000015 0000016 *** get next access plan 0000017 CASE im_access_plan_type. 0000018 WHEN SPACE. 0000019 * first check if there is at all an entry for the 0000020 * specified access plan ID, otherwise raise exception: *>>>>>>>>>>>>>>>>> 0000021 SELECT * FROM dmc_acs_plan_hdr INTO wa_acs_plan_hdr 0000022 UP TO 1 ROWS 0000023 WHERE owner = l_cobj_guid 0000024 AND is_calculated = im_is_calculated 0000025 AND id = im_acp_id. 0000026 ENDSELECT. 0000027 IF sy-subrc NE 0. *<<<<<<<<<<<<<<<<<< 0000028 RAISE id_not_exist.

69

0000029 ENDIF. 0000030

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

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

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

70

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

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

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

71

Report time frame: Service data was collected starting at 04/20/2015 04:30:37. This took 4 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.

Documents

EarlyWatch Alert-UKY Production 1 Service Summary SAP HANA Audit Trail SAP HANA SQL Trace Level Default Passwords of Standard Users Control of the Automatic Login User SAP* Protection