earlywatch alert-uky development 1 service summary sap hana stability and alerts sap hana database...

1

SAP Support Mailbox

From: Batch ID for Basis <[email protected]>Sent: Monday, April 20, 2015 11:08 AMSubject: SMD - Critical (Yellow) - SAP EarlyWatch Alert

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

Report: SMD, ProductiveInstallation: 0020175120

Session: 0010000006984

EarlyWatch Alert-UKY Development

1 Service Summary

This EarlyWatch Alert session detected issues that could potentially affect your system. Take corrective action as soon as possible.

Alert Overview

Security weaknesses identified in the Gateway or the Message Server configuration.

Gateway Access Control List (reg_info/sec_info) contains trivial entries

Some tablespaces with long read or write times were detected.

Hardware resources may have been exhausted with the risk of performance degradation.

Expensive SQL statements cause load on the database server.

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

Based on response times in your ABAP system performance problems may occur.

Perform the following Guided Self Services.

Guided Self Service FAQ SAP Note

SQL Statement Tuning 1601951

Security Optimization Service 696478

2

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

SAP System Configuration

Database - Maintenance Phases

Operating System(s) - Maintenance Phases

Performance Overview

Performance Evaluation

SAP System Operating

Availability based on Collector Protocols

Program Errors (ABAP Dumps)

Update Errors

Table Reorganization

Hardware Capacity

DB Performance

Database Version

Locking

Average Read and Write Times

Missing Indexes

DB Administration

Database Growth and Freespace

10 Largest and Fastest Growing Tables

Tablespaces with a critical size

Tables with a critical size

Table Virtualization

Enhanced Monitoring

Log File Management

Logfiles Recommendations

Database Backup History

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

3

Check Overview Topic Rating Topic Subtopic

Rating Subtopic

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

Java System Data

HANA Technology

HANA Download Function Module Problem

Overview

SAP HANA Stability and Alerts

SAP HANA Database Configuration

SAP HANA Resource Consumption

SAP HANA Workload and Performance

Size and Growth

Administration

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

Area Indicators Value Trend

System Performance Active Users (>400 steps) 12

Avg. Availability per Week 100 %

Hardware Capacity Max. CPU Utilization on DB Server 9 %

4

Area Indicators Value Trend

Max. CPU Utilization on Appl. Server 25 %

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

Database Space Management DB Size 190.02 GB

DB Growth Last Month 1.25 GB

2 Landscape

2.1 Products and Components in current Landscape Product SID SAP Product Product Version SMD SAP Solution Manager 7.1 Main Instances (ABAP or Java based) SID Main Instance SMD Solution Manager ABAP Stack SMD Solution Manager JAVA Stack SMD Add-on: Gateway BEP - 2.0 SMD Add-on: DMIS - 1.0 Databases SID Database System Database Version SMD DB2 for Linux UNIX and Windows 9.7 Other Main Instances Related SID Component Version or Release SID SMD SAP HANA Database 1.00.82.00 HAD

2.2 Servers in current Landscape SAP Application Servers SID Host Instance Name Logical Host ABAP JAVA SMD smdci smdci_SMD_01 smdci

DB Servers SID Host Logical Host (SAPDBHOST) SMD devdb devdb Components Related SID Component Host Instance Name Logical Host SMD SAP HANA Database hanadev hanadev_HAD_00 hanadev SMD Java SCS smdci smdci_SMD_00 smdci

2.3 Hardware Configuration

5

Host Overview

Host Hardware Manufacturer Model CPU

Type CPU MHz Virtualization Operating

System

No. of CPUs

Memory in MB

devdb IBM 8205-E6B POWER7 SPLPAR, UNCAPPED AIX 6.1 16 12288

hanadev Dell Inc. PowerEdge R910

Xeon X7560 @ 2.27GHz

2261

SuSE Linux Enterprise Server 11 (x86_64)

32 517018

smdci IBM 8205-E6B POWER7 SPLPAR, UNCAPPED AIX 6.1 16 61440

3 SAP Solution Manager Service Readiness of SMD

Important service data is missing for this report. Some important checks could not be executed.

SAP Solution Manager system SMD is not fully prepared for delivery of future remote services.

Rating Check Performed

Service Data Quality

SAP Solution Manager Software Configuration

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

Service Preparation Check (RTCCTOOL)

SAP Solution Manager Functionality

We recommend that the SAP Solution Manager is used to ship SAP Support remote services. For more information, see SAP Note 1170668.

3.1 Service Data Quality For this service, data of high 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).

6

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 Service Data in Solution Manager Diagnostics - BW

Prio. Report Area affected Details and Related Infocube SAP

Note

Performance of Java System SMD

No performance data is returned from BW InfoCube. Infocube: 0SMD_MPEH , metric type: APPLICATION THREADS , metric name: ACTIVETHREADSCOUNT / metric type: JAVA MEMORY USAGE , metric name: FULLGC FRACTION (%) used in section 'Java System Data for SMD'.

1332428

3.1.2 Quality of Service Data in Configuration And Change Database

Prio. Report Area affected Details and Related CCDB Store SAP

Note

Configuration of Java System SMD

To analyze missing data in CCDB, call transaction CCDB. Choose the system and the store. CCDB Store: instance.properties with key fields LANDSCAPE CLASS = CL_DIAGLS_JAVA_INSTANCE used in section 'Software Configuration For SMD'.

1777751

Security of Java System SMD

The store is missing. CCDB Store: userstores.entry used in section 'Security'. 1777751

3.2 SAP Solution Manager Software Configuration The ST version determines which functionality can be used or is available for delivery. The ST-SER version determines the session content of services. Certain functionalities may not be available. For further information, see SAP Notes 394616 and 569116.

SAP Component

SAP Component Version

Patch Level

Latest Avail. SAP Component

Latest Avail. SAP Component Version

ST 710 10 710 12

7

SAP Component

SAP Component Version

Patch Level

Latest Avail. SAP Component

Latest Avail. SAP Component Version

ST-SER 701_2010_1 21 701_2010_1 25

3.3 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_700 2 01Q_700 2

ST-PI 2008_1_700 11 2008_1_700 11

3.4 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 20.04.2015. During the check, the tool detected issues for which a RED rating was set.

Overall Status

SAP Note Title Tool

Status Manual Status

1159758 SAP Note 2077703 for DVM


1159758 SAP Note 2053426 for CCM









8

Overall Status

SAP Note Title Tool

Status Manual Status




1159758 SAP NOTE 2115837 for DVM

1159758 SAP Note 2051761 for DB6

1159758 SAP Note 1936913 for 01Q SP02 [DVM]






207223 [Note 207223] EWAlert setup

12103 [Note 12103] Collectors and TCOLL

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

539977 [Note 539977] Addon ST-PI 2008_1_700

69455 [Note 69455] Switch on digital content verification

69455 [Note 69455] Proc. after addon impl.

69455 [Note 69455] ST-A/PI 01Q_700 Support Package 2

69455 [Note 69455] ST-A/PI on SolMan<=SP11: 01Q_700 SP02

1159758 [Note 1159758] ST-SER 2010 SP0 required

Recommendation: SAP Note 2077703 for DVM DVM Decision Maker: Appliction Area Restiction is not working Please implement coding correction from note 2077703 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections.

9

SAP Note 2077326 for DVM Log Viewer for EFWK : missing DVM extractros displayed Please implement coding correction from note 2077326 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 2053426 for CCM DVM Decision Maker - Final Score Pop-Up - KPI Scores do not sum up to Final Score Please implement coding correction from note 2053426 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 2035210 for DVM DVM WoC Template Variants Automated Solution Please implement coding correction from note 2035210 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 2033839 for DVM No new Requests found error from AGS_DVM_TOPOBJ_EXTRACT Please implement coding correction from note 2033839 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 2025096 for DVM Wrong RFC Destination for extractor DVM_ANALYSES_SCHEDULER Please implement coding correction from note 2025096 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 2015536 for DVM DVM Fact Sheet shows wrong results for Document Type Please implement coding correction from note 2015536 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 1998195 for DVM Correction of Extractor DVM Size Statistics Extractor (DBCON) Please implement coding correction from note 1998195 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 1989053 for DVM DVM Business Object Footprint: Extractor corrections (ST) Please implement coding correction from note 1989053 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 1979207 for DVM Incorrect size of DVM workcenter caused by different timezone in managed system Please implement coding correction from note 1979207 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 1968225 for DVM DVM Work Center: Error loading templates Please implement coding correction from note 1968225 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections SAP Note 1950413 for DVM Duplicate entries in Analysis Administration for managed system with more than one productive clients Please implement coding correction from note 1950413 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 1945514 for DVM DVM Compression and Reorganization Analysis Corrections Please implement coding correction from note 1945514 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections.

10

SAP Note 2079337 for DVM DVM Status Summury Dumps : Wrong Client for SUGEN Extractors Please implement coding correction from note 2079337 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP NOTE 2115837 for DVM SolMan READ user has no auth for FUGR /SSF/INTDLFTC (ST14 download fetch to SolMan) [managed] Please implement coding correction from note 2115837 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections. SAP Note 2051761 for DB6 DB6: Wrong Table Size in Reports from Data Volume Management and Early Watch Alerts Please implement the coding corrections from note 2051761. SAP Note 1936913 for 01Q SP02 [DVM] Data Collectors corrections ST-A/PI 01Q SP02 [managed system] Please implement coding correction from note 1936913 using SNOTE. Please perform the manual activities as mentioned in the SAP Note before implementing the attached coding corrections.

3.5 SAP Solution Manager Functionality This service session was performed for an SAP Solution Manager. You may want to configure your SAP Solution Manager for use in different scenarios. SAP offers Expert Guided Implementation sessions, which allow you to create baseline functionality for implementing end-to-end solution operations. Please visit the Expert Guided Implementation page to learn more.

Overview - SAP Solution Manager Self-Diagnosis Rating Functionality Group

General Infrastructure

Service Data Download Center

Service Session Workbench

Service Plan

EarlyWatch Alert

The Self Diagnosis tool detected the following issues when checking whether the prerequisites have been fulfilled for running the SAP Solution Manager correctly. For more information about the Self Diagnosis tool, see SAP Note 1073382 and the related SAP Notes and documentation mentioned here.

The following tables provide details of problems found by the Self-Diagnosis tool on .

Recommendation: Access the Self Diagnosis tool in SAP Solution Manager by calling transaction DSWP and choosing 'Self Diagnosis' or in the 'System Monitoring' Work Center (transaction SOLMAN_WORKCENTER). To resolve any issues, follow the instructions provided in the tool. If these instructions are not clear, create a message in SV-SMG-SDG.

Details - SAP Solution Manager Self-Diagnosis Rating Alert Functionality Group

SDCCN in managed system General Infrastructure

The status of your Service Delivery Readiness is rated GRAY, which means there is no Service Delivery Readiness result in the Self Diagnosis tool in your Solution Manager system. For detailed documentation on this tool, see the guide at https://support.sap.com/solutionmanager -> Media Library -> How-To Documents -> How to work with Function Service Delivery Readiness. This detailed guide provides information on how to set up Self Diagnosis in such a way that the relevant

11

solutions and alerts are included and that the results of the 'Service Delivery Readiness' function can be transferred to SAP. Also refer to SAP Note 1712380 - Service Delivery Readiness in ST 7.10 - SAP SolMan 7.1.

4 Software Configuration For SMD

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 SOLUTION MANAGER 7.1 12/31/2017

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

BBPCRM 701 10 13 SAPKU70110 SAP BBPCRM Server

BI_CONT 707 5 12 SAPK-70705INBICONT

SAP Business Intelligence Content

CPRXRPM 500_702 10 13 SAPK-50010INCPRXRPM

SAP xRPM/cProjects/cFolders 4.00 (ABAP)

CTS_PLUG 200 10 15 SAPK-20010INCTSPLUG CTS Plug-in

DMIS 2010_1_700 7 10 SAPK-91707INDMIS DMIS Component

GW_CORE 200 7 10 SAPK- GW_CORE

12

Support Packages

Software Component Version Patch

Level

Latest Avail. Patch Level

Support Package Component Description

20007INGWCORE

IW_BEP 200 7 10 SAPK-20007INIWBEP Backend Event Provider

IW_FND 250 7 10 SAPK-25007INIWFND

SAP IW FND - IW Foundation

IW_GIL 100 3 6 SAPK-10003INIWGIL

SAP IW Generic Interaction Layer

PI_BASIS 702 13 17 SAPK-70213INPIBASIS SAP R/3 Basis Plug-In

RTCISM 100 0 Integration into SAP IT Infrastructure Management

SAP_ABA 702 13 17 SAPKA70213 SAP Application Basis SAP_AP 700 29 32 SAPKNA7029 SAP Application Platform SAP_BASIS 702 13 17 SAPKB70213 SAP Basis Component

SAP_BS_FND 702 11 14 SAPK-70211INSAPBSFND

SAP Business Suite Foundation

SAP_BW 702 13 17 SAPKW70213 SAP Business Information Warehouse

SOCO 101 3 3 SAPK-10103INSOCO

SAP Solution Composer Server

ST 710 10 10 SAPKITL710 SAP Solution Manager Tool

ST-A/PI 01Q_700 2 2 SAPKITAB7L SAP Service Tools for Applications Plug-In

ST-BCO 710 8 8 SAPK-71008INSTBCO

BI Content for SAP Solution Manager

ST-ICO 150_700 39 44 SAPK-15083INSTPL SAP Solution Manager Implementation Content

ST-PI 2008_1_700 11 11 SAPKITLRDK SAP Solution Tools Plug-In

ST-SER 701_2010_1 21 SAPKITLOSL SAP Solution Manager Service Tools

ST-TST 300 2 2 SAPKITLEG2 ST-TST

UISAPUI5 100 4 11 SAPK-10004INUISAPUI5

SAP UI CLIENT RUNTIME LIBRARIES for HTML5 for AS ABAP

UI_INFRA 100 4 11 SAPK-10004INUIINFRA

Infrastructure for UI add-on for SAP NetWeaver

WEBCUIF 701 10 13 SAPK-70110INWEBCUIF SAP Web UIF

4.3 Support Package Maintenance - JAVA The table below shows the version found.

Support packages

13

Component Version SP Latest Available SP ADSSAP 7.02 13 017 BASETABLES 7.02 13 017 BI_MMR 7.02 13 017 BI_UDI 7.02 13 017 CAF 7.02 13 017 CAF-UM 7.02 13 017 CORE-TOOLS 7.02 13 017 ETPRJSCHEDULER 7.02 13 017 ISAGENT 8 24 024 ISAGENT_MIN_J5 9 10 015 JLOGVIEW 7.02 13 017 JSPM 7.02 13 017 KM-KW_JIKS 7.02 13 017 LM-SERVICE 7.10 10 013 LM-TOOLS 7.02 13 017 SAP-JEE 7.02 13 017 SAP-JEECOR 7.02 13 017 SAP_JTECHF 7.02 13 017 SAP_JTECHS 7.02 13 017 SWLIFECYCL 7.02 13 017 UMEADMIN 7.02 13 017

4.4 Database - Maintenance Phases

Database Version End of Standard Vendor Support* Comment Status SAP

Note

DB2 for Linux, UNIX and Windows 9.7 See Relevant SAP

Note

1168456

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

The end of vendor support dates given in this table are the regular End-of-Support dates published by IBM. If you have obtained your DB2 license from SAP ("application-specific license" (ASL) or "OEM license", as explained in SAP Note 1260217), refer to the SAP Note listed in the table.

See the "Database Version" section in the database section for additional information.

4.5 Operating System(s) - Maintenance Phases

Host Operating System End of Standard Vendor Support* Comment Status SAP

Note

2 Hosts AIX 6.1 Not Yet Defined

1179765

14

Host Operating System End of Standard Vendor Support* Comment Status SAP

Note

by Vendor

hanadev SuSE Linux Enterprise Server 11 (x86_64) 03/31/2019

936887

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

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

HANA Database Version SID SPS Stack SP Revision Maintenance Revision HAD 1.00.082.000 no

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

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

smdci_SMD_01 721_EXT_REL 201 17 AIX

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.

15

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

smdci_SMD_01 DBSL for HANA 721 219 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

We have checked your solution for potential CPU or memory bottlenecks and found that the hardware resources may have been exhausted. An increase in the workload may have a negative impact on performance.

No CPU virtualization data is available for at least one shared CPU pool LPAR (SPLPAR).

Recommendation: For more information about providing the data required for SAP services, see SAP Notes 994025 and 1147334.

5.1 Overview System SMD 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

16

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

devdb 9 04/17/2015

12288 0

hanadev 2 04/15/2015

517018 0

smdci

61440 0

6 Workload Overview SMD

6.1 Workload By Users User activity is measured in the workload monitor. Only users of at least medium activity are counted as 'active users'.

Users Low Activity Medium Activity High Activity Total Users

dialog steps per week 1 to 399 400 to 4799 4800 or more

measured in system 19 4 8 31

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

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

17

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

RFC 3620269 1715224 91412 2

Batch 1216388 462595 21337 0

WS-HTTP 792861 287628 33964 0

Others 49907 31115 31115 198

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

18

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

RFC Profile

Initial System Initial Action Total Response Time[s]

% of Total Load

Steps Avg. Resp. Time[ms]

Avg. Proc. Time[ms]

Avg. CPTime[m

SMD/smdci_SMD_01 EFWK RESOURCE MANAGER 2567869 45.2 373200 6881 998 126 SMD/smdci_SMD_01 SAP_ALERT_CALCULATION_ENGINE 576571 10.2 62849 9174 3791 467 SMD/smdci_SMD_01 SAPMHTTP 394177 6.9 199962 1971 288 29 SMD/smdci_SMD_01 SM:EXEC SERVICES 41467 0.7 7405 5600 520 263 SMD/smdci_SMD_01 E2E BI HOUSEKEEPING 37275 0.7 925 40297 3495 458 SMD/smdci_SMD_01 SAP_ALERT_HOUSEKEEPING 12026 0.2 352 34164 167 24 SMD/smdci_SMD_01 SAP_COLLECTOR_FOR_PERFMONITOR 10955 0.2 1072 10219 5984 3503 SMD/smdci_SMD_01 GN_GENERATE_CHECK 9264 0.2 40 231608 31923 12476 SMD/smdci_SMD_01 E2E DCC AGENT MONITORING 9016 0.2 1061 8498 442 60 SMD/smdci_SMD_01 SAP_DBA_DBH_SETUP_UPDATE_CHECK 7552 0.1 16 471982 32598 7329

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]

ACE_CALCULATION_CONTROLLER 449982 7.9 10053 134 4302 E2E_EFWK_RESOURCE_MGR 217132 3.8 10055 2358 33631 AI_LMDB_R_SYNC_RUNNER 58570 1.0 1007 2731 46184 E2E_DCC_AGT_MON 49449 0.9 1007 374 35777 AI_LMDB_R_NOTIFY_RUNNER 41379 0.7 778 2759 36100 RSDBAJOB 38441 0.7 7 2281 34716 CCMSBI_TWINCUBE_REORG 35976 0.6 161 845 33947

19

Jobs Profile

Report Response Time[s]

% of Total Load

Steps CPU Time[s]

DB Time[s]

CCMSBI_MOVE_RAWDATA_TO_CUBE 34128 0.6 168 1294 31864 E2E_HK_CONTROLLER 31609 0.6 7 1 45 RSCOLL00 18475 0.3 168 484 16915

6.4 RFC Load by Initiating Action The load in task type RFC is shown. In the workload monitor, this information is shown as 'Load from External Systems'. The calling system can be an application server of the system itself or any external system using the RFC interface. The 'Initial Action' is the calling program initiating the RFC. The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table. The average times (per dialog step) are shown in milliseconds [ms]. Calls from external systems are shown if they account for at least 8h or 5% of the total RFC load. Local calls are shown if they account for at least 24h or 20% of the total RFC load.

Load Overview Initial System Load [s] Load % Local system SMD 4,217,632 99.97 Sum of external systems 364 0.01 n/a (not available) 900 0.02 RFC load (sum of above) 4,218,896 100.00 RFC load in Performance Overview 3,623,862 85.90 Load of all task types in Performance Overview 5,679,426 134.62 Top 20 RFC Calls From Local System - Average Times [ms]

Initial System Initial Action Total Resp. Time in s

% of RFC Load

Avg. Response Time

Avg. CPU Time

AvgTime

SMD EFWK RESOURCE MANAGER 2,415,777 57.26 6,791.6 126.5 2,SMD SAPMHTTP 1,131,893 26.83 2,984.3 95.4 1,SMD SAP_ALERT_CALCULATION_ENGINE 537,410 12.74 9,012.3 465.8 4,SMD SM:EXEC SERVICES 41,467 0.98 5,599.8 263.1 3,SMD E2E BI HOUSEKEEPING 31,522 0.75 38,868.3 458.8 35,SMD SAP_ALERT_HOUSEKEEPING 11,281 0.27 33,774.4 24.1 33,SMD SAP_COLLECTOR_FOR_PERFMONITOR 10,329 0.24 10,136.6 3,437.8 4,SMD E2E DCC AGENT MONITORING 8,421 0.20 8,362.8 60.0 7,SMD GN_GENERATE_CHECK 8,113 0.19 231,789.9 12,554.6 180,SMD SAP_DBA_DBH_SETUP_UPDATE_CHECK 6,606 0.16 471,841.9 7,406.4 438,SMD SAP_LMDB_LDB_0000000001 4,592 0.11 6,560.3 22.9 6,SMD DIAGST_ADMIN_TASKS 2,641 0.06 1,565.4 34.1 1,smdci.iris.uky.edu_SMD_13096150 E2E DCC AGENT MONITORING 2,598 0.06 430.0 8.4 SMD SAP_LMDB_NOTIFY_LDB_0000000001 2,048 0.05 5,551.1 127.9 5,SMD E2E DPC SELFMON 1,012 0.02 1,508.7 189.9 SAP_LMDB_NOTIFY_LDB_0000000001 900 0.02 50,019.6 350.6 49,SMD SM:SYNC ISSUES FROM CRM 701 0.02 4,121.1 23.1 4,SMD RDDMASGL 320 0.01 5,809.9 130.0 4,SMD SAP_METRIC_STORE_CLEANUP 198 0.00 1,178.3 38.1

20

Top 20 RFC Calls From Local System - Average Times [ms]

Initial System Initial Action Total Resp. Time in s

% of RFC Load

Avg. Response Time

Avg. CPU Time

AvgTime

SMD /BDL/TASK_PROCESSOR 175 0.00 1,771.2 23.9 1,

7 Performance Overview SMD

The performance of your system was analyzed with respect to average response time and total workload. Some problems that may impair system performance were detected. To ensure adequate performance in your core business transactions, you should take corrective action as soon as possible. For more information, contact SAP Support.

Rating Check

Performance Evaluation

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

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

Time[ms] Avg. CPU Time[ms]

Avg. Wait Time[ms]

Avg. DB Time[ms]

Avg. GUI Time[ms]

RFC 928872 3897 98 9 1847 0 HTTP(S) 15357 236 6 17 162 0 Dialog 2075 1207 14 1 497 96

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

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

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

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

Ratings Task Steps Application Server Performance Database Server Performance RFC 928872

Time Profile Rating

Rating Task Time Steps Avg. Response Time[ms]

Avg. CPU Time[ms]

Avg. Database Time[ms]

21

Time Profile Rating

Rating Task Time Steps Avg. Response Time[ms]

Avg. CPU Time[ms]

Avg. Database Time[ms]

RFC 00-01 38533 6796 105 3761

RFC 01-02 41851 6105 92 3200

RFC 02-03 41791 4197 87 2091

RFC 03-04 38415 3475 95 1598

RFC 04-05 37651 2810 98 1263

RFC 05-06 37601 3351 98 1508

RFC 06-07 37393 3115 89 1428

RFC 07-08 37355 2951 94 1258

RFC 08-09 37219 2622 94 1161

RFC 09-10 39732 2522 98 1144

RFC 10-11 39813 2950 106 1310

RFC 11-12 40691 3136 99 1380

RFC 12-13 40546 3700 90 1821

RFC 13-14 39191 3593 92 1752

RFC 14-15 36926 3693 98 1799

RFC 15-16 38119 3724 91 1817

RFC 16-17 38594 2891 90 1347

RFC 17-18 37697 3259 88 1527

RFC 18-19 37998 3064 91 1425

RFC 19-20 38130 3662 101 1640

RFC 20-21 40031 5818 134 2523

RFC 21-22 38012 3949 109 1878

RFC 22-23 36579 4594 111 2220

RFC 23-24 39004 7227 109 3282

Reference Times

22

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

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

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

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

RFC 2400 3600 1200 1800

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

History of Response Time of SMD

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

23

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

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

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

Task Type

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

(%/year) Trend

ALL 85.3

402.2

Dialog 296.5

2,083.6

HTTP(S) 126.9

3,082.4

RFC 81.2

381.3

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

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

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

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

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

Top Applications by Response Time

Task Type Application

Total Resp. Time in s

% of Total Load

Avg. Resp. Time in ms

Long Term Growth (%/year)

Short Term Growth (%/year)

24

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)

RFC SMD/smdci_SMD_01|EFWK RESOURCE MANAGER 28431030 72 5292 39.8 389.0 RFC SMD/smdci_SMD_01|SAP_ALERT_CALCULATION_ENGINE 5662482 14 5704 77.3 393.9 RFC SMD/smdci_SMD_01|SAPMHTTP 4001486 10 1443 63.1 413.9 RFC SMD/smdci_SMD_01|SM:EXEC SERVICES 321710 1 3164 147.9 638.1 RFC SMD/smdci_SMD_01|E2E BI HOUSEKEEPING 318248 1 23801 103.6 183.6 RFC SMD/smdci_SMD_01|SAP_ALERT_HOUSEKEEPING 130684 0 23534 50.8 146.1 RFC SMD/smdci_SMD_01|SAP_COLLECTOR_FOR_PERFMONITOR 92308 0 5327 36.5- 3,682.5 RFC SMD/smdci_SMD_01|GN_GENERATE_CHECK 88794 0 153358 89.6 355.4 RFC SMD/smdci_SMD_01|E2E DCC AGENT MONITORING 88762 0 5317 85.9 198.2 RFC SMD/smdci_SMD_01|SAP_DBA_DBH_SETUP_UPDATE_CHECK 88368 0 332211 45.1 168.0 RFC SMD/smdci_SMD_01|SAP_LMDB_LDB_0000000001 34971 0 4997 53.4 123.7 RFC SMD/smdci_SMD_01|DIAGST_ADMIN_TASKS 28045 0 1149 23.8 464.6

RFC smdci.iris.uky.edu_SMD_13096150|E2E DCC AGENT MONITORING 24943 0 249 57.3 558.3

RFC SMD/smdci_SMD_01|SAP_LMDB_NOTIFY_LDB_0000000001 19384 0 2221 278.9 411.8 RFC SMD/smdci_SMD_01|E2E DPC SELFMON 11094 0 997 52.4 408.1 RFC SMD/smdci_SMD_01|SM:SYNC ISSUES FROM CRM 7307 0 2620 24.9 1,009.7 RFC SMD/smdci_SMD_01|SAPMSSY1 5962 0 24739 104.0- 148.5- HTTP(S) {AGS_WORKCENTER 5051 0 5328 214.0 1,322.2 HTTP(S) {WD_SISE_WIZARD_APP 4078 0 7080 68.7 941.3 HTTP(S) {DB_WDA_EXPL_OIF_CFG 4037 0 7517 97.1- 273.6

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.

8 SAP Solution Manager General of SMD

25

8.1 Background Jobs In this check, the background processing in transaction SM37 that is specific to SAP Solution Manager is evaluated. For this purpose, a number of different SAP Solution Manager standard jobs are checked for their executions in the last 4 weeks. To obtain a better overview, the various jobs are divided into generic SAP Solution Manager jobs (jobs with a job name starting with "SM:") and other standard SAP Solution Manager jobs.

If at least one of the evaluated jobs has been canceled in at least one of the last ten executions, the line in the table is rated RED. In this case, the check shows the name of the canceled jobs in a second table. If both lines in the first table are rated GREEN, the background processing in your SAP Solution Manager needs no further attention.

BGJobs Overview Job Category Available Distinct Jobs Occurrences Jobs Cancelled Rating Generic SSM Jobs 56 2222 1

Other 24 18347 5

The check was rated RED because the jobs listed in the following table have been cancelled at least once during the last ten executions. You can also see the "Last Job Date", "Last Job Status", the "Total Jobs" during the last four weeks, and the number of "cancelled" jobs during the last four weeks. For these jobs, check why the job was cancelled or whether the job is needed at all.

BGJobs Details JobName Last Job Date Last Job Status # Total Jobs # Cancelled SM:EXEC SERVICES 04/19/2015 F-Finished 9 1

9 SAP Solution Manager Usage of SMD The number of managed systems, diagnostics systems, implementation projects, and solutions indicates the scale of usage of this SAP Solution Manager. The number of connected managed systems is derived from the available systems in transaction SOLMAN_SETUP, whereas the number of diagnostics systems is the number of systems for which Solution Manager Diagnostics is active. The projects can be found in transaction SOLAR01, whereas the solutions can be found in the Solution Manager Administration work center. For more information, see SAP Service Marketplace at http://service.sap.com/solutionmanager and http://service.sap.com/diagnostics.

Overview – SAP Solution Manager Usage Application Area Object Type # of Objects System Landscape Connected Managed Systems 62 Solution Manager Diagnostics Number of Diagnostics Systems 22 Implementation Projects 6 Operations Solutions 5 EarlyWatch Alert Sessions 3608

9.1 Application-Specific Usage The tables in this section provide an overview as to whether and to what extent some selected scenarios in SAP Solution Manager are used. For an overview of all the supported processes, check the Application Life-Cycle Management page on SAP Service Marketplace at http://service.sap.com/alm.

26

9.1.1 Collaboration

The collaboration scenario includes service delivery, problem management (with issues, top issues, and tasks) and expertise on demand (EoD). The number of service delivery objects counts delivered standard remote services such as SAP EarlyWatch Check, SAP GoingLive Check, SAP GoingLive Functional Upgrade Check, and SAP OS/DB Migration Check (see also http://service.sap.com/supportservices ). The "Last Created" column indicates whether the functionality is still in use. For more information concerning the collaboration platform, check SAP Note 914722.

Collaboration Scenario Application Area # of Objects Last Created Service Delivery 0 00/00/0000 Issues 7 04/23/2014 Expertise on Demand (EoD) 0 00/00/0000

9.1.2 IT Service Management

To show how many transaction types exist in the system. Entries with the message > 0 show how many messages exist in the system and how many of them were created in the EWA time frame.

IT Service Management Application Area # of Objects Business Partners 28 Transaction Types 4 Support Notification (SLFN) 2 - created in EWA timeframe 0

9.1.3 Change Request Management

In standard Change Request Management, SAP delivers seven messages types; all other message types are customer created message types. The number of change request transactions (created in the last ten days) indicates whether and to what extent the scenario is used. For more information about Change Request Management and other change control functionalities, see http://service.sap.com/changecontrol .

Change Request Management Scenario Application Area # of Objects Process Types 6 Change Request Transactions 0 - created in last 10 days 0 ChaRM activated Projects 0 Task Lists 0

9.1.4 Quality Gate Management

With this Quality Gate Management check, you can review whether, and to what extent the Quality Gate Management scenario is used within your SAP Solution Manager. The number of gate switches, the number of created and released transport requests under the control of Quality Gate Management, and the number of SAP Solution Manager projects used to run Quality Gate Management indicate how, and how much this scenario is used.

QGM Usage

27

Application Area # of Objects Number of Gate switches 0 - in last 90 days 0 Created Transports under QGM Control 0 - in last 90 days 0 Number of QGM-Projects 0 - in last 90 days 0 Number of Released Transports 0 - in last 90 days 0

9.1.5 Implementation Scenario

The number of defined business scenarios and defined business processes and steps indicate whether and to what extent the implementation scenario is used. It includes all business scenarios and business processes that have been defined in the different projects and can be checked in transaction SOLAR01.

Implementation Scenario Application Area # of Objects Defined Business Scenarios 12 Defnied Business Processes 37

9.1.6 Test Management

The test management scenario is part of the implementation scenario. A number larger than zero indicates whether and to what extent the test management functionality is used. The functionality can be accessed using the Test Management work center.

Test Management Scenario Application Area

# of Objects

# of Testcases

# of Messages assigned

Last Status Analysis

Test Plans 9 132 0 01/23/2012 Test Packages 12 249 2 01/03/2013

9.1.7 Business Process Monitoring

For the Business Process Monitoring (BPM) scenario, the number of solutions with BPM, the number processes with BPM, and the number of monitoring objects in BPM is shown. The functionality can be accessed using the Business Process Operations work center.

Business Process Monitoring

Application Area # of Solutions with BPM

# of Processes with BPM

# of Monitoring Objects

Business Process Monitoring 0 0 0

9.1.8 Job Scheduling Management

This check shows how many job requests and how many job documents have been created in SAP Solution Manager and how many of them were created in the EWA time frame.

28

Number of job requests and job documentations Application Area Number of object Number of Job Requests 0 - Created in EWA timeframe 0 Number of Job Documentations 1 - Created in EWA timeframe 0

10 SAP System Operating SMD

Your system was analyzed with respect to daily operation problems. We did not detect any major problems that could affect the operation of your SAP System.

10.1 Availability based on Collector Protocols

A value of 100% means that the collector was available all day. "Available" in the context of this report means that at least one SAP instance was running. If the SAP collector was not running correctly, the values in the table and graphics may be incorrect.

To check these logs, call transaction ST03N (expert mode) and choose "Collector and Performance DB -> Performance Monitor Collector -> Log".

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.

29

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

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

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

10.4 Transports Transports were not found in the period analyzed.

10.5 Program Errors (ABAP Dumps) 2 ABAP dumps have been recorded in your system in the period 04/13/2015 to 04/17/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 0

04/15/2015 0

04/16/2015 0

04/17/2015 1

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

Date (e.g.)

Time (e.g.)

SYSTEM_CANCELED 1 smdci_SMD_01 BAT-BC 04/13/2015 14:51:58

LOAD_PROGRAM_CLASS_MISMATCH 1 smdci_SMD_01 DBA006 04/17/2015 15:26:55

30

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.

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

SAP HANA Password Policy HAD

SAP HANA Audit Trail HAD

SAP HANA SQL Trace Level HAD

Default Passwords of Standard Users SMD

Control of the Automatic Login User SAP* SMD

Protection of Passwords in Database Connections SMD

ABAP Password Policy SMD

Gateway and Message Server Security SMD

Users with Critical Authorizations SMD

11.1 SAP HANA Database HAD

11.1.1 SAP HANA System Privilege DATA ADMIN

11.1.1.1 Users with DATA ADMIN Privilege

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

31

Number of Additional Users with DATA ADMIN Privilege 1

DATA ADMIN provides the authorization to modify and delete every object in every schema.

Recommendation: Remove the DATA ADMIN privilege from all user accounts except the SYSTEM und _SYS_REPO users.

11.1.2 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

11.1.2.1 Audit Trail Target

The audit trail target is currently set to 'CSV Text File'. This is not secure enough and should only be used for test purposes. CSV text files are not sufficiently protected against unauthorized modifications.

Recommendation: Use the "Syslog" (default) or (as of SPS07) "Database Table" target.

Note: If you use the "Syslog" option, you also need to configure the operation system syslog accordingly so that you will not receive error messages in the event of issues with the OS syslog.

11.2 ABAP Stack of SMD

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

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

32

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.

11.2.3 ABAP Password Policy

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

11.2.3.1 Password Complexity

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

smdci_SMD_01 6 8

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

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

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

login/min_password_letters smdci_SMD_01 0

login/min_password_lowercase smdci_SMD_01 0

login/min_password_uppercase smdci_SMD_01 0

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

11.2.3.2 Validity of Initial Passwords

Rating Parameter Instance Current Value(s)

login/password_max_idle_initial smdci_SMD_01 0

33

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.

11.2.4 Gateway and Message Server Security

11.2.4.1 Gateway Security

Enabling an Initial Security Environment

Parameter: gw/acl_mode Rating Instance Current Value Recommended Value

smdci_SMD_01 0 1

Recommendation: Parameter gw/acl_mode can be set to 1 to activate a more secure default behavior if either of the access control lists defined by gw/sec_info and gw/reg_info does not exist. SAP recommends setting gw/acl_mode to 1 to establish an additional line of defense should any of the access control lists be missing. For more information, see SAP Note 1480644.

Gateway Access Control Lists

Parameters: gw/sec_info gw/reg_info Rating Instance Error Condition

All instances gw/reg_info and gw/sec_info are defined reg_info Rating Instance Error Condition File does not exist (default)

All instances P TP=* sec_info

Rating Instance Error Condition File does not exist (default)

All instances

P TP=* USER=* USER-HOST=* HOST=*

Recommendation: The profile parameters gw/sec_info and gw/reg_info provide the file names of the corresponding access control lists. These access control lists are critical to controlling RFC access to your system, including connections to RFC servers. You should create and maintain both access control lists, which you can do using transaction SMGW. For more information, see "Configuring Connections between SAP Gateway and External Programs Securely" on SAP Help Portal.

11.2.5 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

34

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

11.2.5.1 Super User Accounts

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

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

000 6 7

001 19 80

Authorization profile: SAP_ALL

11.2.5.2 Users Authorized to Change or Display all Tables

Unauthorized access to sensitive data is possible if too many users have this authorization. The specified number of users for each client have the checked authorization.


001 27 80

Authorization objects:

Object 1: S_TCODE with TCD=SE16, TCD=SE16N, TCD=SE17, TCD=SM30, or TCD=SM31

Object 2: S_TABU_DIS with ACTVT = 03 or 02 and DICBERCLS = *

11.2.5.3 Users Authorized to Start all Reports

This authorization allows critical functions and reports that do not contain their own authorization checks to be executed. The specified number of users for each client have the checked authorization.


001 24 80

066 2 2


Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38

Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*

35

11.2.5.4 Users Authorized to Debug / Replace

This authorization provides access to data and functions, since any authorization check that is built in ABAP can be bypassed. In addition, you can change data during processing, which may lead to inconsistent results. The specified number of users for each client have the checked authorization.


001 24 80


Object 1: S_DEVELOP with ACTVT=02 (change) and OBJTYPE=DEBUG

Note: If you do not want to disable development in your system, you have to exclude the OBJTYPE=DEBUG with ACTVT=02 from the profile and allow any other object type for S_DEVELOP. This means that development and debugging with visualization is still possible. You can achieve this by linking two authorizations to the object S_DEVELOP: one with all object types (except for "DEBUG") and all activities, and another for the object type DEBUG only and all activities (except for 02).

11.2.5.5 Users Authorized to Display Other Users Spool Request

This authorization allows unauthorized access to sensitive data contained in spool requests. The specified number of users for each client have the checked authorization.


001 19 80


Object 1: S_TCODE with TCD = SP01 or SP01O

Object 2: S_ADMI_FCD with S_ADMI_FCD = SP01 or SP0R

Object 3: S_SPO_ACT with SPOACTION = BASE and DISP and SPOAUTH = * or __USER__

11.2.5.6 Users Authorized to Administer RFC Connections

If too many users have this authorization, two problems can occur: - Unauthorized access to other systems - Malfunction of interfaces if invalid connection data is entered

The specified number of users for each client have the checked authorization.


001 24 80


36

Object 1: S_TCODE with TCD=SM59

Object 2: S_ADMI_FCD with S_ADMI_FCD = NADM

Object 3: S_RFC_ADM with ACTVT NE 03

11.2.5.7 Users Authorized to Reset/Change User Passwords

The following users are allowed to change and reset the passwords of all users. This is very risky because any of these users could change the password and log on themselves with any user. The only consequence is that the "real user" would no longer be able to log on because the password was changed. However, this normally results in the password being reset, because there is a chance that the "real user" might have forgotten the correct password.


001 23 80

066 1 2


Object 1: S_TCODE with TCD=SU01 or TCD=OIBB or TCD=OOUS or TCD=OPF0 or TCD=OPJ0 or TCD=OVZ5

Object 2: S_USER_GRP with ACTVT=05

12 Software Change and Transport Management of SMD

Software change management issues were found in your system. See the information in the following sections.

12.1 SAP Netweaver Application Server ABAP of SMD


Number of Changes

37

12.1.1 Number of Changes

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

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

Date Security Software Maintenance Parameter Transport

Requests SAP Notes Miscellaneous

04/15/2015 0 0 0 0 1 0

04/17/2015 0 2 0 0 1 0

12.2 SAP Netweaver Application Server JAVA of SMD


Number of Changes

Enhanced Change and Transport System (CTS+)

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

38

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

12.2.2 Enhanced Change and Transport System (CTS+)

The enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-related non-ABAP applications in your system landscape along with ABAP objects. The tracking and logging features of the ABAP Change and Transport System are also available for non-ABAP applications in a central user interface. This provides maximum transparency for all changes in the complete landscape, including ABAP and non-ABAP systems. CTS+ is SAP's recommended tool for distributing changes across the transport landscape.

We could not determine whether CTS+ is used. Either it is not used or information about its usage is not available in SAP Solution Manager. If CTS+ is not configured, you should set it up as described in the online help http://help.sap.com/nwcts --> Application Help. If CTS+ is configured but this information is not available in SAP Solution Manager, repeat the managed system configuration for this system in transaction SOLMAN_SETUP of your SAP Solution Manager. In step "Enter System Parameters", section "CTS+ Reporting", select CTS+ as active and enter the communication system. Also run the managed system configuration for the CTS+ communication system.

13 Data Volume Management (DVM)

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

14 Database Performance

39

In the checks performed, problems regarding the performance of your database were found.

Rating Check

Database Version

Locking

Average Read and Write Times

Missing Indexes

14.1 Database Version SMD

SID Database Version Fix Pack level Build Level DBSL Patch

SMD DB2 for Linux UNIX and Windows 9.7 8 s130316 137

For the latest database versions and Fix Packs, see also SAP Note 101809. For more information about known errors in DB2 Fix Packs, see SAP Note 1346902.

SID Database Start Date [yyyy/mm/dd]

Database Up Time [Days]

Download Collection Date [yyyy/mm/dd]

SMD 2014/10/16 187 2015/04/20

14.1.1 Average Read and Write Times for Tablespaces

Tablespace Partition

Avg. Read Time [ms]

Read Time Threshold [ms]

Avg. Write Time [ms]

Write Time Threshold [ms]

% of Total Reads

SMD#ES702IX 0 18.99 10.00 2.02 5.00 0.35

SMD#DBI 0 15.71 10.00 1.57 5.00 0.71

SMD#BTABI 0 15.16 10.00 1.61 5.00 13.15

SMD#DDICI 0 15.15 10.00 1.27 5.00 0.29

40

Tablespace Partition

Avg. Read Time [ms]

Read Time Threshold [ms]

Avg. Write Time [ms]

Write Time Threshold [ms]

% of Total Reads

SMD#ODSI 0 14.76 10.00 1.85 5.00 14.58

SMD#POOLI 0 14.47 10.00 2.08 5.00 2.12

SMD#FACTI 0 14.40 10.00 1.53 5.00 2.26

SMD#STABD 0 14.22 10.00 1.56 5.00 5.11

SMD#STABI 0 14.07 10.00 1.54 5.00 0.97

SMD#ES702DX 0 13.74 10.00 1.63 5.00 0.42

SAPTOOLS 0 13.32 10.00 2.07 5.00 2.05

SMD#POOLD 0 12.58 10.00 1.64 5.00 2.00

SMD#DIMD 0 11.41 10.00 1.59 5.00 0.28

SMD#DIMI 0 10.11 10.00 1.88 5.00 0.44

We have checked active tablespaces for poor performance. Tablespaces with long read or write times were detected. This may be due to a non-optimal storage layout.

Note: To avoid unrealistic figures and to ensure that only active tablespaces are checked, the analysis is restricted to 95% of the total workload. The remaining tablespaces are considered inactive.

Recommendation: For optimal I/O performance, ensure the following: - Each tablespace should consist of several containers, distributed over your SAP data directories in a round-robin fashion. - DB2_PARALLEL_IO is enabled only for tablespaces with one container per RAID device or stripe set. - Individual containers are not too large. Avoid too many levels of striping. - All containers for one DB2 stripe set are the same size. If some containers are smaller, parallel prefetching may not be optimal. - If the operating system and file system type allow direct (DIO) or concurrent (CIO) I/O, deactivate file system caching at database level (see tablespace snapshot) to avoid double buffering. System caching should only be active for dedicated tablespaces used to store LONG/LOB data only. For more information, see the document "Creating table spaces without file system caching" in the IBM Information Center.

15 Database Administration

41

In the checks performed, problems regarding the administration of your database were found.

Rating Check

Database Growth and Freespace

10 Largest and Fastest Growing Tables

Tablespaces with a critical size

Tables with a critical size

Table Virtualization

Enhanced Monitoring

Log File Management

Logfiles Recommendations

Database Backup History

15.1 Database Storage These two graphs show your database growth and free space development over the past few months.

Note: If limited history is displayed (for example 1 or 2 months), it is most likely due to the setting of the DCF collector 'Tablespaces (Storage)' in DBACOCKPIT. Go to transaction DBACOCKPIT -> Configuration -> Data Collection Framework using the Webdynpro. Check the retention ('Days Kept in History' column). The default is 90 days but you can increase this value to a longer timeframe.

42

The following table displays the current size and the monthly growth of your database in GB.

Date Current Size (GB) Monthly Growth (GB)

02/01/2015 188.19 0.00

03/01/2015 188.77 0.58

04/01/2015 190.02 1.25

15.2 10 Largest and Fastest Growing Tables The following tables displays the 10 largest and fastest growing tables stored in the database.

Table Name Tablespace Size (GB)

43

Table Name Tablespace Size (GB)

REPOLOAD SMD#EL702DX 9.16

BALDAT SMD#BTABD 8.46

REPOSRC SMD#ES702DX 6.37

LMDB_P_CHANGELOG SMD#BTABD 6.20

TST03 SMD#BTABD 4.95

/BI0/F0DB6_C13H SMD#FACTD 4.62

SASACONT1 SMD#BTABD 4.48

DYNPSOURCE SMD#ES702DX 3.85

DSVASRESULTSGEN SMD#BTABD 3.29

ALRT_NGTRACE SMD#BTABD 3.05

Name Tablespace Monthly Growth (GB)

/BI0/ACCMVAL100 SMD#ODSD 0.17

/BI0/E0SMD_PEH2 SMD#FACTD 0.07

/BI0/E0CCMRTDH1 SMD#FACTD 0.02

/BI0/E0CCMRSDH1 SMD#FACTD 0.02

/BI0/E0SMD_PED1 SMD#FACTD 0.01

/BI0/F0DB6_C12H SMD#FACTD 0.01

/BI0/E0CCMRCDD1 SMD#FACTD 0.01

/BI0/F0CCMHOUR1 SMD#FACTD 0.00

/BI0/F0SMD_PEH2 SMD#FACTD 0.00

/BI0/F0CCMDAY1 SMD#FACTD 0.00

15.3 Data Collection Framework As of SAP_BASIS 7.02 and DB2 V9.5, a new infrastructure is used to manage the history of data. This infrastructure is called the data collection framework (DCF). The DCF collects the data independently of the SAP system. The history data for the database objects (tables and indexes) is collected with this DCF infrastructure. The default retention of the DCF collector that stores tablespace details is currently set to 14 days, as opposed

44

to several weeks with the older method. This DCF collector is used to monitor the database size and growth in remote services such as SAP EarlyWatch Alert. Limited reporting of such data is therefore available with the default settings. Recommendation: To overcome this, we recommend that you change the default setting of the DCF collector 'Tablespaces (Storage)' (or 'Tablespaces' depending on your SAP_BASIS release) from 14 days to at least 90 days for 'Days Kept in History'. Note that the additional space impact for longer history is low. We also recommend that you use at least the 'SAP Default' template when configuring the DCF collectors.

15.4 Tablespaces with a critical Size No DMS tablespaces were found for which the 'Used Size' or 'Total Size' is critical.

Note: Make sure the relevant file systems are large enough to allow further tablespace growth.

15.5 Tables with a critical size Your system was checked for tables that have reached their size limits. No tables were critical. For technical reasons (expensive operation to check all tables in the system), we could not check whether all tables are already enabled for 'Large RIDs'.

Background: For tables that are not enabled for 'Large RIDs', the size restrictions of DB2 V8 64, 128, 256, or 512 GB still apply (depending on whether they are stored in tablespaces of page size 4, 8, 16, or 32 KB). This is the case even if the tablespaces have been converted to type 'Large'. Even if such tables are far smaller than the old size limits, they could still be affected. Once all pages below the old size limit are occupied by tables enabled for 'Large RIDs', even small tables that are not enabled for 'Large RIDs' cannot grow any further, leading to SQL errors, or even to unplanned downtime.

Recommendation: Convert ALL DMS tablespaces to type 'Large' (if not already done) and enable ALL tables for 'Large RIDs' as soon as possible, to benefit from the increased table and tablespace size limits. This is especially important for tablespaces that only contain a single table and are close to the former V8 size limit. Such tables require at least a reorganization of their indexes before they can grow beyond the V8 size limit.

To check whether a tablespace has been converted to type 'Large', use the following command: SELECT tbspace FROM syscat.tablespaces WHERE datatype = 'L'

To convert a tablespace to type 'Large', use the following command: db2 alter tablespace <tablespace> convert to large It is not necessary to convert SYSCATSPACE to large.

With the following SQL statement, you can count the number of tables that are not yet enabled for 'Large RIDs': select large_rids, count(*) as number from sysibmadm.admintabinfo where tabschema not like 'SYSIBM%' group by large_rids

To ease the task of converting tablespaces to type 'large' and reorganizing tables/indexes, SAP has developed the tool 'Large RID Tool'. It can be found as an attachment to SAP Note 1108956. The PDF document that is also attached describes the use in detail and offers the possibility to reorganize tables/indexes via a convenient front end. See the following article in SDN, which describes the tool in more detail: http://scn.sap.com/people/johannes.heinrich/blog/2007/11/14/new-tool-for-activation-of-large-record-identifiers-in-db2-9-for-linux-unix-and-windows

45

15.6 Table Virtualization SAP systems contain thousands of empty tables that consume unnecessary space. Virtual tables were introduced by SAP to save disk storage and help improve the performance of many utilities, such as Automatic RUNSTATS and Automatic REORG. The concept of virtual tables is as follows: No empty table is created in the database. It is defined logically in the SAP DDIC instead. When the first row is inserted into a virtual table, the SAP Database Support Layer (DBSL) determines that the table does not yet exist in the database. DBSL issues the CREATE TABLE statement to create the table before inserting the first row.

We have checked if specific SAP Notes related to virtual tables needed to be implemented on your system. The following table shows that no action is necessary. For more information on converting empty tables to virtual tables, refer to SAP Notes 1399128, 1458921, and 1478193 for details.

SAP Note Description Implemented ?

1399128 DB6: Wrong DB column order after table virtualization

1478193 DB6: Correction Instructions for SAP HotNews 1458921

15.7 Enhanced Monitoring Settings

Parameters Description Current Value Recommendation

MON_LOCKWAIT Monitoring lock wait configuration parameter WITHOUT_HIST NONE

MON_LW_THRESH Monitoring lock wait threshold configuration parameter 300000000 5000000

At least one of the parameters listed above is not set according to our standard recommendations.

Recommendation: Adjust the parameters to the recommended settings.

Background: If you are using the new time-spent metrics introduced in DB2 V9.7, you first need to ensure that the new in-memory metrics are activated in the database configuration. These are activated by default for new databases created on DB2 >= V9.7 but deactivated for migrated databases.

Once these are activated, the new metrics (including time spent) are collected within DB2 memory and can be accessed in any number of ways. You can look at the current in-memory values using one of the new table functions (that is, look for the ones with the prefix MON_GET_*) for any connection, unit of work, and so on, or from the package cache. You can also collect data for a specific execution using the activity event monitor (introduced in DB2 V9.5) for a specific unit of work using the new UOW event monitor, and so on. This data is also used in SAP Solution Manager 7.1 and DBACOCKPIT.

15.8 Log File Management The DB2 database is running in log retention mode as recommended. Ensure that all log files are archived starting from the last complete backup to allow any kind of recovery.

46

15.9 Logfiles Recommendations Database Logging Information (Since Database Start) Parameter / KPI Current Setting / Value logfilsiz (MB) 128 logprimary 20 logsecond 60 Total Log Space Available To Database (MB) 10147 Maximum Log Space Used in (MB) 3738 Maximum Secondary Log Space Used in (MB) 1192 Maximum Number of Secondary Log Files Used 10

Unless experience indicates otherwise, set the following parameters for the number and size of log files to the values indicated. Do not configure less than 4 GB of log space. If you change any of the parameters LOGFILSIZ, LOGPRIMARY, or LOGSECOND, ensure that you have allocated sufficient space in your LOGPATH directory. If you want to configure LOGSECOND to a value other than zero, refer to SAP Note 1493587 and SAP FAQ Note 1497040.

We recommend the following size for directories that contain log files: - The "log_dir" directory should be at least large enough to hold all primary and secondary log files. As a safety margin, we recommend that you double the size of this directory. - If indirect log archiving is in use, the offline log directory "log_archive" should be large enough to store all the log files for three working days.

Parameters Description Current Value Recommendation

logprimary Number of primary logfiles 20 35

logsecond Number of secondary logfiles 60 50

15.10 Further Recommendations Administration of db2diag.log The DB2 diagnostic file db2diag.log contains diagnostic records about administrative events and specific error information about problems encountered within DB2. Once created, the db2diag.log file grows continually. To avoid long access times via transaction DBACOCKPIT, we recommend that you keep the size of the file reasonably small. Use the command "dbdiag -A" to create a new db2diag.log file on a regular basis. Alternatively, rename the file at OS level. A new db2diag.log file will then be created automatically by the DB2 database manager. As of DB2 V9.7, a series of 10 rotating diagnostic log and 10 administration notification log files can be used by setting the DBM CFG parameter DIAGSIZE. Its value determines the combined, overall size of the database diagnostic and administration notification log files. In this way, these log files can be used in a rotating order with a fixed maximum size. As of SAP Basis Release 7.02, the Web dynpro-based DBA Cockpit offers a "Weekly Switch" of the database diagnostic log as an alternative way of archiving the db2diag.log under a new name (similar to using db2diag –A). You can access this option from the menu by choosing "Configuration-> Monitoring Settings". For more information, see the IBM DB2 Information Center and the guide "Database Administration Using the DBA Cockpit: IBM DB2 for LUW", which is available on SAP Service Marketplace at https://service.sap.com/instguides -> SAP NetWeaver -> SAP NetWeaver<release> -> Operations -> Database-Specific Guides.

47

Supported DB2 versions and Fix Packs SAP Note 101809 contains a complete list of supported DB2 versions and Fix Packs. Check this SAP Note at regular intervals for the latest available DB2 Fix Pack and also to verify that your Fix Pack is still supported.

Also see the following important SAP Notes for DB2:

SAP Note Number Description

101809 DB6: Supported Fix Packs for DB2 UDB for UNIX and Windows

975352 DB6: Configuring DB2 Auto Reorg for space reclaim and index cleanup

1168456 DB6: End-of-Support Dates

1309424 DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11

1314750 DB6: DBA Cockpit Correction Collection SAP Basis 7.00 / 7.10

1329179 DB6: DB2 V9.7 Standard Parameter Settings

1346902 DB6: Known Errors and available Fixes in DB2 9.7 for LUW

1351160 DB6: Using DB2 9.7 with SAP Software

1425488 DB6: Performance problems with volatile tables

1456402 DB6: DBA Cockpit Correction Collection SAP Basis 7.02/7.30/7.31

1499214 DB6: Database Administration - Learning Offerings

1628029 DB6: Error when collecting historical data

1630506 DB6: History management of monitoring data

1837312 DB6: Upgrade to Version 10.5 of DB2 for LUW

1929142 DB6: DROP INDEX may result in database marked as bad

1942183 DB6: When to consider a table or index reorganization

16 Java System Data for SMD

48

A YELLOW rating has been set for one of the following reasons.

1. Some of the performance data is missing. For more information, see chapter "Quality of Service Data in Solution Manager Diagnostics".

2. We have detected some problems that may impair system performance. Take corrective action as soon as possible to ensure a sufficient level of performance in your core business transactions. For more information, contact SAP Support.

Note that if performance data is available, if the system has more than 20 server nodes, only the data for the 10 server nodes with the highest values and 10 server nodes with the lowest values are listed.

16.1 Java VM Heap Size The Java heap size data was not found. The configuration data can be found in the 'Root Cause Analysis' work center under 'System Analysis'--> 'Change Reporting'. If the data is already missing there, open a message under component SV-SMG-DIA. If data is available in 'Change Reporting', but is missing here, open a message under component SV-SMG-SER.

16.2 Availability of Java Performance Data

Some of the Java performance and workload data is missing.

There are three parts for Java-related performance data. These are Java VM Memory Performance, Java Workload Overview, and Java Application Performance. The data for at least one of the three parts is missing.

Recommendation:

Check whether the missing data is displayed for this system in the 'Workload Analysis' application. This can be found in the 'Root Cause Analysis' work center under 'End To End Analysis'. If the data is already missing there, open a message under component SV-SMG-DIA.

If data can be displayed in the workload analysis but is missing here, open a message under component SV-SMG-SER.

For more troubleshooting information regarding missing Java-related performance data in a service session, please refer to the attachment in SAP Note 1332428.

Requirements for the 'Workload Analysis' are:

- Setup of solution manager diagnostics including BI.

- The managed system configuration must have been executed successfully for this system as described in SAP Note 1265070.

- SMD agents are set up and running.

- Periodic extractors are running successfully.

For more information, see http://service.sap.com/diagnostics.

49

17 SAP HANA - Technology for HAD

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

Rating Check

HANA Download Function Module Problem

Overview

SAP HANA Stability and Alerts

SAP HANA Database Configuration

SAP HANA Resource Consumption

SAP HANA Workload and Performance

Size and Growth

Administration

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

Version Current SAP HANA DB Version 1.00.82.00 System environment

Hostname Physical Hostname

Nr. of CPU cores

Physical Memory [GB]

Swap Space [GB]

Nameserver: Actual role

Indexserver: Actual role

hanadev hanadev 32 504.90 2.00 MASTER MASTER

17.2 SAP HANA Stability and Alerts

17.2.1 SAP HANA Alerts

50

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

0 Identifies internal statistics server problem. 4,198 5

62

Identifies database users whose password is due to expire in line with the configured password policy. If the password expires, the user will be locked. If the user in question is a technical user, this may impact application availability. It is recommended that you disable the password lifetime check of technical users so that their password never expires (ALTER USER <username> DISABLE PASSWORD LIFETIME).

287 3

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

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

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

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

Recommendations Alert ID General Recommendation KBA

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

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

1909660

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

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

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

51

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

17.2.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/18/2015 1 0 0

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

17.2.3 SAP HANA services restarts

We detected downtimes of less critical services.

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

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

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

17.3 SAP HANA Database Configuration

17.3.1 Parameter Recommendation

52

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: section persistence


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


socket_keepalive indexserver.ini: section session DEFAULT on on

1836774

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

SAP HANA Parameters deviating from default

Parameter Location Current Value Default Value

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

global_allocation_limit global.ini section: memorymanager 400000 0

cer_rserve_addresses indexserver.ini section: calcengine 128.163.185.234:30120

cer_rserve_maxsendsize indexserver.ini section: calcengine 0

cer_timeout indexserver.ini section: calcengine 1200

num_cores indexserver.ini section: parallel 24

alert indexserver.ini section: trace error <restore

default>

authorization indexserver.ini section: trace debug

53

SAP HANA Parameters deviating from default

Parameter Location Current Value Default Value

default indexserver.ini section: trace error <restore

default>

logger indexserver.ini section: trace info <restore

default>

persistencemanager indexserver.ini section: trace info <restore

default>

enable nameserver.ini section: sld yes

active nameserver.ini section: statisticsserver true false

alert nameserver.ini section: trace error <restore

default>

default nameserver.ini section: trace error <restore

default>

alert preprocessor.ini section: trace error <restore

default>

default preprocessor.ini section: trace error <restore

default>

alert xsengine.ini section: trace error <restore default>

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

17.3.2 Disk Configuration

There are no disk configuration issues.

Disk ID Device ID File system Host Path Usage

4 899979 nfs hanadev /hanadevback/log/ LOG_BACKUP

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

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

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

2 899979 nfs hanadev /hanadevback/data/ DATA_BACKUP

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

17.3.3 CPU Configuration

Rating Recommendation

The CPU clock frequency is set as expected.

54

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

CPU Configuration

Host CPU Type / Architecture CPU Frequency

HW Manufactor Rating

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

17.3.4 Trace Settings

SAP HANA Trace settings do not match default settings

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

SAP HANA Trace Settings

HANA Trace Area Current Configuration

Recommended Configuration Rating

Database Trace Not default Default

SQL Trace Inactive Inactive

Expensive Statements Trace Active Inactive

Performance Trace Inactive Inactive

End-to-End Traces Default Default

Other Traces Default Default

By activating the Expensive Statement Trace, you can identify long-running SQL statements that lead to increased response times or a high database load. This can also be beneficial for production systems. Note that, depending on the configured threshold for expensive statements (parameter "threshold_duration" in indexserver.ini, section: expensive_statement), the trace activity may be high and should be monitored. The Expensive Statement Trace is deactivated by default.

The trace levels of the displayed components are not set to the default values that are suitable for a production landscape.

Recommendation: For production usage of your SAP HANA database, we recommend setting the trace level of all components according to the recommendations in the table above.

Background: Traces can be switched in the 'Trace Configuration' tab of the SAP HANA studio Administration Console.

The following table lists HANA parameters set specifically for traces.

HANA Trace Area

Configuration File Section Trace Component

Current Trace Level

Database Trace daemon.ini trace default error

55

HANA Trace Area

Configuration File Section Trace Component

Current Trace Level

Database Trace indexserver.ini trace alert error

Database Trace indexserver.ini trace authorization debug

Database Trace indexserver.ini trace default error

Database Trace indexserver.ini trace logger info

Database Trace indexserver.ini trace persistencemanager info

Database Trace nameserver.ini trace alert error

Database Trace nameserver.ini trace default error

Database Trace preprocessor.ini trace alert error

Database Trace preprocessor.ini trace default error

Database Trace xsengine.ini trace alert error

Database Trace xsengine.ini trace default error

Expensive Statements Trace

indexserver.ini expensive_statement enable true

Note that activating traces and setting detailed trace levels may cause a high system load. It generates a large number of trace files that can take up a lot of disk space and may have an impact on performance.

Recommendation: Activate traces for specific analysis only and make sure that trace levels are set to the necessary level of detail. Make sure that traces are deactivated after analysis of the system has been completed.

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

17.4.1 Disk Usage

Percentage of free disk space <(><<)> 20%

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

56

Disk Space

Host

Available Disk Space [GB]

Used Disk Space [GB]

Percentage of free Disk Space

Usage Types File system Rating

hanadev 504.00 435.00 14.00 LOG xfs

hanadev 34.00 17.00 52.00 TRACE ext3

hanadev 886.00 143.00 84.00 DATA ext3

hanadev 562.00 233.00 58.00 DATA_BACKUP+LOG_BACKUP nfs

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

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

17.4.2 Tables and Indexes

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

Tables and Indexes Objects Number Column Tables 1,312 Indexes of Colum Tables 803 Row Tables 785 Indexes of Row Tables 69

17.4.3 Size of HANA schemas

The following table lists the size of schemas in the SAP HANA database.

Size of HANA schemas Host Schema name Size in MB Store type hanadev SAPECC 13,307 Column store hanadev _SYS_STATISTICS 1,623 Column store hanadev CORE 354 Column store hanadev _SYS_REPO 323 Column store hanadev CORE_SCHEDULES 306 Column store hanadev CPE 141 Column store hanadev STAGING_AREA 43 Column store hanadev ACADEMIC_STATS 34 Column store hanadev SAPBW 31 Column store hanadev CROSS_REF 25 Column store hanadev BBCORE 24 Column store hanadev CPE_PRELIMINARY 17 Column store hanadev PROSAM 10 Column store hanadev _SYS_BI 9 Column store hanadev STARREZ 4 Column store hanadev SKOLLD 4 Column store

57

Size of HANA schemas Host Schema name Size in MB Store type hanadev DATA_QUALITY 2 Column store hanadev STUDENT_ORGSYNC 1 Column store hanadev SYS_HANA 11,522 Row store hanadev CPE 4,176 Row store hanadev PROSAM 3,908 Row store hanadev CLJ 2,684 Row store hanadev STAGING_AREA 513 Row store hanadev CBYU2 368 Row store hanadev CBORD 163 Row store hanadev SYS 124 Row store hanadev CROSS_REF 70 Row store hanadev ECHO 65 Row store hanadev _SYS_STATISTICS 37 Row store hanadev THE_STUDY 28 Row store hanadev STUDENT_TEMP 28 Row store hanadev SAPECC 20 Row store hanadev ASTRA_ETL 13 Row store hanadev BBCORE 8 Row store hanadev SKOLLD 5 Row store hanadev CPE_PRELIMINARY 4 Row store hanadev ESI_SURVEY 3 Row store

Row Store Size

The allocated row store size is not critical.

The table below shows the size of the SAP HANA row store. The row store contains mainly SAP Basis and application statistics tables. The rating indicates whether the size limit will be reached in the near future.

Row Store Size Host Port Allocated Size [MB] Rating hanadev 30003 32,140

Row Store Fragmentation

The fragmentation of the row store is not critical.

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

Row Store Size and Fragmentation

Host Port Allocated Size [MB]

Free Size [MB]

Free Page Ratio [%]

Row Store Reorganization Recommended

58

Row Store Size and Fragmentation

Host Port Allocated Size [MB]

Free Size [MB]

Free Page Ratio [%]

Row Store Reorganization Recommended

hanadev 30003 32,140 7,415 23 No

Largest Row Store Tables (Size)

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

Schema Name Table Name Table Size (MB)

Table Size alloc (MB)

PROSAM MEM 1,661 1,876

CLJ CPE_COURSE_HISTORY 628 725

CPE CPE_COURSE_HISTORY_20141210 597 700

CPE CPE_STUDENT_HISTORY 546 610

CPE CPE_STUDENT_HISTORY_BKP_030415 493 551

CPE CPE_STUDENT_HISTORY_BKP_120814 490 544

CLJ CPE_STUDENT_HISTORY_BKP_120814 490 544

CPE CPE_STUDENT_HISTORY_BKP 490 544

CLJ CPE_STUDENT_HISTORY 490 544

STAGING_AREA CPE_STUDENT_HISTORY_BU 433 482

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

Largest Column Tables (Size)

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

Largest Column Tables according to Size Schema Name Table Name Partition ID Memorysize (Total) [MB] SAPECC HRP1001 0 4,463 SAPECC HRPAD506 0 957 SAPECC DFKKOP 0 923 SAPECC DFKKOPK 0 831 SAPECC PIQDBAGR_APPR 0 669 SAPECC PIQDBAGR_GEN 0 667 SAPECC HRT1721 0 256 SAPECC GMIA 0 0 SAPECC ZHR_9016_DETAILS 0 0 SAPECC PIQPROC_PG_MB 0 0

59

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

Largest Non-partitioned Column Tables (Records)

The number of records in column-based table partitions is not critical.

The table below shows the largest non-partitioned column tables in terms of the number of records.

Largest Non-partitioned Column Tables According To Records Schema Name Table Name Records (Total) Rating SAPECC GMIA 145,420,640

SAPECC ZHR_9016_DETAILS 55,843,321

SAPECC PIQPROC_PG_MB 52,778,833

SAPECC HRP1001 50,431,016

DATA_SCIENTIST GRADE_PAIRS 49,052,534

ACPD MEMBR_SPANS 29,991,897

SAPECC DFKKOPK 29,910,928

SAPECC PA2002 28,447,761

SAPECC ZCAFLATTABLCHAN 24,435,345

ACTIVE_ANALYSIS GRADE_PAIRS 23,759,241

The table partitions can handle the number of the records.

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

HANA Instances Overview

HANA Instance Role CPU Usage

Memory Usage

Memory Allocation of Tables

Memory Consumption Indexserver

hanadev_HAD_00 MASTER

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.

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

60

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

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

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

Avg. memory usage by SAP HANA Instances

HANA instance

Memory usage of SAP HANA [GB]

Global allocation limit [GB]

Row store size [GB]

Column store size [GB]

Memory usage of indexserver [GB]

Effective allocation limit of indexserver [GB]

hanadev_HAD_00 77 391 32 15 78 383

17.5.2 HANA Instance hanadev_HAD_00

CPU Usage of HANA server

No CPU bottlenecks were detected.

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.

61

We did not find any critical issues in this area.

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

The memory consumption of tables is below any critical threshold.

62

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.

Memory consumption of Indexserver

The memory consumption of the index server is critical.

The index server is the most critical component regarding the SAP HANA memory consumption and has to be monitored regularly. If the memory consumption of the index server comes close to the effective allocation limit, the table may unload or out-of-memory dumps may even occur. The following graph shows the memory consumption of the index server in relation to its effective allocation limit.

63

The memory consumption of the index server was high.

This is due to either large/large amounts of loaded tables or query processing in SAP HANA database consuming too much memory.

Recommendation: Analyze the reason for high memory consumption of the index server and plan measures to reduce the memory consumption of the SAP HANA database.

17.6 SAP HANA Workload and Performance

17.6.1 SAP HANA Response Times

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

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

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.

64

Explanation of the SAP HANA response time shares: - Preparation time – time share for plan preparation - Open time – time share for cursor open and select - Fetch time – time share for cursor fetch - Lock wait time - lock wait time share for the plan - Table load time – time share for loading tables during plan preparation (available as of SAP HANA rev. 50)

Largest Column Tables in terms of delta size

No problems with the delta size of column store tables were detected.

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

Largest Column Tables in terms of Delta size

Schema Name Table Name Partition

ID

Memorysize in Main Store [MB]

Memorysize in Delta Store [MB]

Records in Delta Store

Sum of Records

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

65

17.7 Administration

17.7.1 Diagnosis Files

The number and size of diagnosis files is uncritical.

During operation, the SAP HANA database service writes messages and information to log files in its trace directory. The system administrator should check these files regularly and react to error messages accordingly. A large number of files may be generated, which can take up a lot of disk space and impair performance. The following table shows the number of files contained in the trace directory.

Diagnosis Files Server Measured Time Period Type Number of Files Total Size in MB hanadev Weekly Log 2 56.61 hanadev Weekly Trace 22 154.21 hanadev Weekly Dump 1 6.74 hanadev Unlimited TOTAL 47 227.98

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.

17.7.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 229 0 04/14/2015 Tuesday 288 0 04/15/2015 Wednesday 288 0 04/16/2015 Thursday 288 0 04/17/2015 Friday 288 0 04/18/2015 Saturday 288 0 04/19/2015 Sunday 288 0 Data Backup History Date Weekday Successful Data Backups Unsuccessful Data Backups 04/13/2015 Monday 1 0 04/14/2015 Tuesday 1 0 04/15/2015 Wednesday 1 0 04/16/2015 Thursday 1 0 04/17/2015 Friday 1 0 04/18/2015 Saturday 1 0 04/19/2015 Sunday 1 0

17.7.3 License Information

66

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

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

License Information System ID

Installation Number

Expiration Date Permanent Valid Product

Name Product Limit

HAD 0020598649 TRUE TRUE SAP-HANA 256

17.8 Important SAP Notes for SAP HANA The following tables list important SAP Notes for SAP HANA.

SAP Notes for critical SAP HANA issues SAP Note Description

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

67

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 .

18 Database server load from expensive SQL statements - SMD

The SQL statements that we have identified cause a significant load on the database server. This results in performance problems, not only for the transactions that execute these statements but also for other users.

Database Load From Expensive Statements Rating Total Execution Time[%]

62.73

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 1625795. 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 analysis of your system's SQL statement cache found that the total SQL statements were <= 1,000,000, or statements per day were below 500,000 or some analysis data was unavailable for evaluation.

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

18.1 Analysis of DB SQL CACHE on 04/20/2015 at 04:35

68

Expensive SQL Statements Overview

Object Name Total Execution Time[%]

Avg. Execution Time[ms]

Executions Rows Read[%]

Rows Returned [%]

Rows Written[%]

Sort Overflows

/BI0/ACCMAGGR00 23.54 175.06 2920609 5.68 12.26 0.00 0 GENROW 9.93 2.71 79444304 5.50 0.00 29.03 0 E2E_ACTIVE_WLI 5.48 2.61 45573792 3.08 6.41 0.00 0 E2E_EFWK_LOG 4.55 68.85 1435739 10.30 22.31 0.00 0 E2E_EFWK_LOG 4.45 1,156.62 83592 0.01 0.01 0.00 0 E2E_RECORDS_WLI 3.84 1,832.87 45444 0.40 0.87 0.00 0 E2EREP_MAPPING 3.26 11.40 6200311 0.41 0.87 0.00 0 E2E_RECORDS_WLI 2.75 1,359.21 43962 0.61 0.05 0.00 0 /BI0/ACCMAGGR00 2.62 4.41 12890053 0.84 0.00 4.72 0 /BI0/ACCMAGGR00 2.31 293.36 170973 0.00 0.00 0.00 0

18.1.1 Access on /BI0/ACCMAGGR00

Statement Data:

Cache Statistics

Total Executions

Total Execution Time[ms]


Rows Read

Rows Written

Rows Returned

Total User CPU Time[ms]

Total Logical Reads

Sort Overflows

2920609 511280959 175.06 87646017 0 87205638 2358180 361250677 0

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On LSCSM_BI_DATALOADF07 00000271 SAP SAP 01/10/2014

000271 SELECT * FROM (tabname_aggr) INTO <struc> FOR ALL ENTRIES IN key_table 000272 WHERE smd_grda = 'DAY' 000273 AND smd_grti = 'DAY' 000274 AND smd_lsid = key_table-smd_lsid 000275 AND smd_luid = key_table-smd_luid 000276 AND smd_mehi = key_table-smd_mehi 000277 AND calday = key_table-calday 000278 AND time = 000000.

18.1.2 Access on GENROW

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

79444304 215675313 2.71 84855422 79346048 0 6003803 328670492 0

69

Program Data:


000063 MODIFY (db_table_name) FROM TABLE data.

18.1.3 Access on E2E_ACTIVE_WLI

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

45573792 118909912 2.61 47476159 0 45573796 3171537 177104347 0

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On LE2E_DPC_LUWU05 00000125 SAP SAP 01/10/2014

000123 000124 * Get the corresponding WLI parameters 000125 SELECT SINGLE * FROM e2e_active_wli INTO wa_e2e_active_wli 000126 WHERE wli_id = wa_local_worklist-wli_id.

18.1.4 Access on E2E_EFWK_LOG

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

1435739 98848872 68.85 158786113 0 158694917 312678 166900714 0

Program Data:

Origin of ABAP coding

Program Name Line Created By

Last Changed By

Last Changed On

CL_E2EEFWK_LOGGING============CM001 00000015 SAP SAP 06/20/2012

70

000014 000015 SELECT * FROM e2e_efwk_log INTO TABLE it_e2e_efwk_log WHERE wli_id = wli_id.

18.1.5 Access on E2E_EFWK_LOG

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

83592 96683836 1,156.62 131208 0 104658 1127800 60552585 0

18.1.6 Access on E2E_RECORDS_WLI

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

45444 83292848 1,832.87 6229314 0 6206912 75716 6500580 0

Program Data:



Last Changed By

Last Changed On

CL_E2EEFWK_ME_LUW_DB==========CM00C 00000196 SAP SAP 01/10/2014

000195 000196 select * 000197 into table lt_e2e_records_wli 000198 from e2e_records_wli 000199 where wli_id = me->worklist_item-wli_id and 000200 ( timestamp between lv_timestamp_start and lv_timestamp_end ).

18.1.7 Access on E2EREP_MAPPING

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

6200311 70699522 11.40 6313642 0 6198511 408661 32141714 0

71

Program Data:



Last Changed By

Last Changed On

CL_E2EREP_MAPPING_ACCESSOR====CM00S 00000015 SAP SAP 02/08/2012

000013 000014 000015 SELECT * FROM e2erep_mapping INTO ch_act_set 000016 WHERE mte_hkey EQ map-mte_hkey 000017 AND ind EQ 0.

18.1.8 Access on E2E_RECORDS_WLI

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

43962 59753618 1,359.21 9474915 0 332548 76751 9803051 0

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On LE2E_FUNCU39 00000205 SAP SAP 01/10/2014

000204 000205 select * FROM E2E_RECORDS_WLI into wa_records 000206 WHERE 000207 WLI_ID = WLI_ID and 000208 ( timestamp BETWEEN timestamp_start and timestamp_end ) AND 000209 status ne 0 ORDER BY timestamp ascending.


Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

12890053 56795050 4.41 12999008 12890346 0 480610 77889015 0


72

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

170973 50155976 293.36 36881 0 0 160971 19531657 0

Program Data:


000285 000286 SELECT * FROM (tabname_aggr) INTO <struc> FOR ALL ENTRIES IN key_table 000287 WHERE smd_grda = 'WEEK' 000288 AND smd_grti = 'HOUR' 000289 AND smd_lsid = key_table-smd_lsid 000290 AND smd_luid = key_table-smd_luid 000291 AND smd_mehi = key_table-smd_mehi 000292 AND calday = key_table-calday_week 000293 AND time = key_table-time.

19 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 section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.

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

73

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

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

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

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

74

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

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