EWA_SEP

EarlyWatch Alert-SAP Solution

file:///X|/CTX_Config/Desktop/New folder/sep.html[2/4/2014 1:08:32 AM]

Analysis from 27.01.2014Until 02.02.2014

Report: SEP, Not ProductiveInstallation: 0020715587

Session: 8000000000277


1 Service Summary

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

Alert OverviewSecure password policy is not sufficiently enforced.Security weaknesses identified in the Gateway or the Message Server configuration.Security-related SAP Notes have not been applied in the system.Standard users have default password.A high number of users have critical authorizations

Perform the following Guided Self Services.

Guided Self Service FAQ SAP NoteSecurity Optimization Service 696478

Find more information about Guided Self Services on SAP Enterprise Support Academy.

Register for a guided self service on the Expert Guided Implementation Schedule.

Check OverviewTopicRating Topic

SubtopicRating Subtopic

SAP SystemConfiguration

Performance Overview Performance Evaluation

Workload Distribution Workload by Application Module DB Load Profile



SAP System Operating Availability based on Collector Protocols Program Errors (ABAP Dumps) Update Errors Table Reorganization

Hardware Capacity DatabasePerformance

Wait Statistics IO Performance Missing Indexes

DatabaseAdministration

DatabaseGrowth Largest Tables Top Growing Tables Service Pack Check Tables With Page Locking Disabled Database Options

Security

SAP Security Notes: ABAP and KernelSoftware Corrections Default Passwords of Standard Users Control of the Automatic Login User SAP* ABAP Password Policy Gateway and Message Server Security Users with Critical Authorizations

Software ChangeManagement

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

Note: If you have any questions concerning the correctness of the checks in this report, or concerning the correctconfiguration of the Solution Manager EarlyWatch Alert service, create a customer message under componentSV-SMG-SER-EWA.

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

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

6 ms

Area Indicators Value TrendSystem Performance Avg. Response Time in Dialog Task Max. Dialog Steps per Hour 1 Avg. Response Time at Peak Dialog Hour 6 ms Avg. Response Time in RFC Task 519 ms



Max. Number of RFCs per Hour 108 Avg. RFC Response Time at Peak Hour 595 msHardware Capacity Max. CPU Utilization on Appl. Server 5 %Database Performance Avg. DB Request Time for RFC 7 msDatabase Space Management DB Size 42.85 GB DB Growth Last Month 0 GB

2 Landscape2.1 Products and Components in current LandscapeProductSID SAP Product Product VersionSEP SAP ERP 6.06

Main Instances (ABAP or Java based)SID Main InstanceSEP Master Data GovernanceSEP SAP ECC Server

DatabasesSID Database System Database VersionSEP SQL SERVER 2008 R2

2.2 Servers in current LandscapeSAP Application ServersSID Host Instance Name Logical Host ABAP JAVASEP vss-p-erpcia vss-p-erpcia_SEP_01 vss-p-erpcia SEP vss-p-erpsa1 vss-p-erpsa1_SEP_03 vss-p-erpsa1 SEP vss-p-erpcib vss-p-erpcib_SEP_02 vss-p-erpcib

DB ServersSID Host Logical Host (SAPDBHOST)SEP vss-p-sqlerpa VSS-P-SQLERPDTC

ComponentsRelated SID Component Host Instance Name Logical HostSEP ABAP SCS sapseq-prod sapseq-prod_SEP_00 sapseq-prod

2.3 Hardware ConfigurationHost Overview

Host HardwareManufacturer ModelCPUType

CPUMHz Virtualization

OperatingSystem

No.ofCPUs

Memoryin MB



sapseq-prod VMware, Inc.

Intel(R)Xeon(R)CPU E5-2670 [email protected]

2600

WindowsServer2008 R2(x86_64)

2 16384

vss-p-erpcia

XeonE5-26700

VMWARE


2 16384

vss-p-erpcib VMware, Inc.

VMwareVirtualPlatform

XeonE5-26700

VMWARE


2 16383

vss-p-erpsa1 VMware, Inc.

VMwareVirtualPlatform

XeonE5-26700

VMWARE


2 16384

vss-p-sqlerpa VMware, Inc.

Intel(R)Xeon(R)CPU E5-2670 [email protected]

2600


2 16384

3 Service Preparation and Data Quality ofSEP

Configuration hints for optional service data are provided.

SAP ERP system SEP is not fully prepared for service delivery.

Rating Check PerformedService Data QualityST-PI and ST-A/PI Plug-InsService Preparation Check (RTCCTOOL)Service Data Control CenterHardware Utilization Data

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



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

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

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

Overall important data are missing. Detecting a critical situation may fail. Reportcannot 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 greennevertheless.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.ReportAreaaffected

Details and Related Infocube SAPNote

Workload ofSEP

Reading performance data from BW returned neither datanor an error code. A timeout may have occured.Infocube: 0CCMSMTPH used in section 'Workload OverviewSEP'.

1332428

3.2 ST-PI and ST-A/PI Plug-InsThe table below shows the service plug-ins implemented and their releases and patch levels. Theserecommendations are derived from report RTCCTOOL. For more information about RTCCTOOL, see SAP Note309711.

Rating Plug-In Release Patch Level Release Rec. Patch Level Rec.ST-A/PI 01Q_731 0 01Q_731 2ST-PI 2008_1_700 7 2008_1_700 8

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

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

OverallStatus

SAPNote Title

ToolStatus

ManualStatus

69455 [Note 69455] ST-A/PI AddonSupportpackage SP0



539977 [Note 539977] ST-PI Support Packages69455 [Note 69455] Addon ST-A/PI 01Q_73169455 [Note 69455] Proc. after addon impl.

69455 [Note 69455] Switch on digital contentverifi539977 [Note 539977] Addon ST-PI 2008_1_70012103 [Note 12103] Collectors and TCOLL

207223 [Note 207223] EWAlert setup

Recommendation:[Note 69455] ST-A/PI Addon Supportpackage SP0Addon supportpackage SP02 for ST-A/PI 01Q_731 for NetWeaver 7.31-7.40 [your current level is older than01Q SP1. Update strongly recommended]From http://service.sap.com/supporttools->ST-A/PI->Support packages-> ST-A/PI 01Q_731 download patch .For basis >=700 use the Maintenance optimizer to release the download. Upload from frontend totransactionSPAM, define a queue and import.

[Note 539977] ST-PI Support PackagesAddon supportpackage level 8 for ST-PI 2008_1_700 for 7.00 [your current level is one SP lower thanrecommended. Update recommended]Open http://service.sap.com/supporttools-> ST-PI 2008_1_700 ->Supportpk. Add patch SAPKITLRD8 (andpredecessors if not yet implemented) to download basket. For basis >= 700 release basket via Maintenanceoptimizer. Upload from frontend into transaction SPAM, define a queue and import the queue.

4 Software Configuration For SEP

Your systems' software versions are checked. If known issues with the software versions installedare identified, they are highlighted.

4.1 SAP Application Release - Maintenance Phases

SAP Product Version End of Mainstream Maintenance StatusSAP ERP 6.0 31.12.2020

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

4.2 Support Package Maintenance - ABAPSAP R/3 Enterprise PLM, SCM, Finance

Support Packages



SoftwareComponent Version

PatchLevel

LatestAvail.PatchLevel

Support Package ComponentDescription

EA-APPL 606 4 10 SAPK-60604INEAAPPL

EA-DFPS 600 20 24 SAPKGPDD20SAP R/3 EnterpriseDefense Forces &Public Security

EA-FINSERV 600 19 25 SAPKGPFD19 SAP R/3 EnterpriseFinancial Services

EA-GLTRADE 600 20 24 SAPKGPGD20 SAP R/3 EnterpriseGlobal Trade

EA-HR 600 72 104 SAPKGPHD72 SAP R/3 EnterpriseHuman Resources

EA-IPPE 400 21 24 SAPKGPID21SAP R/3 EnterpriseIntegrated Product andProcess Engineering

EA-PS 600 20 24 SAPKGPPD20 SAP R/3 EnterprisePublic Services

EA-RETAIL 600 20 24 SAPKGPRD20 SAP R/3 EnterpriseRetail

ECC-DIMP 600 19 24 SAPK-60019INECCDIMPECC DiscreteIndustries Mill Products

ERECRUIT 600 20 24 SAPK-60020INERECRUIT SAP E-Recruiting

FI-CA 600 19 SAPK-60019INFICA

FI-CA, ContractAccounts Receivableand Payable (virtuell)

FI-CAX 600 19 24 SAPK-60019INFICAXFI-CAX: Extended FI-CA

FINBASIS 600 20 24 SAPK-60020INFINBASISSAP R/3 EnterpriseFINBASIS

INSURANCE 600 19 24 SAPK-60019ININSURANCINSURANCE SAPInsurance

IS-CWM 600 19 24 SAPK-60019INISCWMIS-CWM Catch WeightManagement

IS-H 600 25 36 SAPK-60025INISH IS-HospitalIS-M 600 19 24 SAPK-60019INISM IS Media

IS-OIL 600 19 24 SAPK-60019INISOIL

IS-OIL SAP OIL & GASUpstream /Downstream

IS-PS-CA 600 19 24 SAPK-60019INISPSCA

IS-PS-CA,Tax&Revenue; CampusManagement

IS-UT 600 19 24 SAPK-60019INISUT IS-UT

LSOFE 600 20 24 SAPK-60020INLSOFELearning Solution -Front End

MDG_APPL 606 4 10 SAPK-60604INMDGAPPL MDG Applications

MDG_FND 731 4 10 SAPK-73104INMDGFND MDG Foundation



PI_BASIS 731 4 10 SAPK-73104INPIBASIS SAP R/3 Basis Plug-In

SAP_ABA 731 4 10 SAPKA73104 SAP Application Basis

SAP_AP 700 27 30 SAPKNA7027 SAP ApplicationPlatformSAP_APPL 606 4 10 SAPKH60604 SAP R/3 StandardSAP_BASIS 731 4 10 SAPKB73104 SAP Basis Component

SAP_BS_FND 731 4 10 SAPK-73104INSAPBSFNDSAP Business SuiteFoundation

SAP_BW 731 4 10 SAPKW73104 SAP BusinessInformation WarehouseSAP_HR 600 72 104 SAPKE60072 SAP R/3 Standard HRSEM-BW 600 20 24 SAPKGS6020 SAP SEM ServerST-A/PI 01Q_731 0

ST-PI 2008_1_700 7 8 SAPKITLRD7 SAP Solution ToolsPlug-In

WEBCUIF 731 4 10 SAPK-73104INWEBCUIF SAP Web UIF

4.3 Database - Maintenance Phases

DatabaseSystem

DatabaseVersion

End ofStandardVendorSupport*

Comment

End ofExtendedVendorSupport*

Comment Status SAPNote

SQLSERVER 10 08.07.2014

PlannedDate 09.07.2019

PlannedDate 1177356

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

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

4.4 Operating System(s) - Maintenance Phases

Server OperatingSystem

End ofStandardVendorSupport*

Comment

End ofExtendedVendorSupport*

Comment Status SAPNote

5Servers

WindowsServer 2008R2 (x86_64)

13.01.2015 14.01.2020 1177282

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

4.5 SAP Kernel Release



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

Instance(s) SAP KernelReleasePatchLevel Age in Months OS Family

3 instances 720_EXT_REL 401 13 Windows Server(x86_64)

4.5.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 latestSupport Package stack for your product.

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

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

Formore information, see SAP Service Marketplace at http://service.sap.com/sp-stacks (SAP Support PackageStack information) and http://service.sap.com/patches (patch information).

5 Hardware Capacity

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

5.1 Overview System SEPGeneralThis analysis focuses on the workload during the peak working hours (9-11, 13) and is based on the hourlyaverages collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note1251291.

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

MemoryIf your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in yourSAP system that can impair performance. The paging rating depends on the ratio of paging activity to physicalmemory. 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. CPUload [%] Date RatingRAM[MB]

Max. Paging[% of RAM] Date Rating

vss-p-erpcia 5 02.02.2014 16384 12 02.02.2014

vss-p-erpcib 2 27.01.2014 16383 0

vss-p-erpsa1 5 02.02.2014 16384 22 02.02.2014

6 Business Key FiguresDisclaimer

Bear in mind that all assumptions and ratings in this presentation are based on our general experience with othercustomers and that the findings are not necessarily business-critical in your particular case.

The following general rule of thumb applies to most ratings of application-related backlog key figures:GREEN the backlog is smaller than one day of typical daily throughputYELLOW the backlog is between one and five days of typical daily throughputRED the backlog is above five days of typical daily throughput

Gray standard evaluation is not possible due to missing reference value

All recommendations in this section are based on our general experience only. We advise you to test ourrecommendations before using them in your production system.

Note

Overdue or exceptional business documents could be included in the measurements as a result of system errors(for example, user handling issues, configuration or master data issues, open documents on inactive organizationalunits or document types). Often, these documents are not processed further by the business departments and donot have a direct impact on customer satisfaction, revenue, or working capital.

Note however that these documents could have negative impacts on other areas such as supply chain planningaccuracy, performance (of other transactions, reports, or processes), and data and reporting quality.

6.1 SAP Business Process AnalyticsWith SAP Business Process Analytics in SAP Solution Manager, you can continuously analyze the above keyfigures and around 500 additional out-of-the-box key figures for continuous improvement potential in your SAPbusiness processes.

(1) You can perform internal business process benchmarking (across organizational units, document types,customers, materials, and so on) for the number of exceptional business documents and/or for the cumulatedmonetary value of these documents.

(2) You can perform an age analysis to measure how many leftovers you have from previous years or months.

(3)You can analyze a trend for these exceptions over a specific time period.

(4) You can obtain a detailed list for all of these exceptional business documents in the managed system andperform a root cause analysis to identify reasons why these documents are open, overdue, or exceptional.

SAP Business Process Analytics can help you to achieve thefollowing main goals:



Global transparency of business-relevant exceptions

Reduced standardization issues (business process template adherence)

Improved process efficiency due to a reduction in system issues (such as user handling, configuration issues,and master data issues)

Improved process effectiveness (optimized working capital, increased customer satisfaction, improved supplychain planning)

Improved process compliance for internal auditing

SAP also provides business process improvement methodology to help you identify and analyze improvementpotential within your business processes using Business Process Analytics in SAP Solution Manager and visualizeit for your senior management.

For more information, navigate to the following link: here.

6.2 SAP Active Global Support Follow-Up Opportunities

If you have an SAP Enterprise Support contract, SAP Active Global Support provides you with thefollowing offering for obtaining business process analytics and implementing improvements:

- SAP Expert Guided Implementation Business Process Analytics and Improvement (SAP EGI Portfolio Overview)

- CQC Business Process Analytics and Improvement (fact sheet).

If you have an SAP Max Attention Contract, contact your Technical Quality Manager (TQM) forinformation about how SAP Active Global Support can help you obtain business process analytics andimplement improvements.

7 Workload of System SEPThis chart displays the main task types and indicates how their workload is distributed in the system. The tablebelow lists the detailed KPIs.



Response Time Components In HoursTask Type Response Time Wait Time CPU Time DB Time GUI TimeBATCH 0,3 0,0 0,0 0,1 0,0RFC 0,1 0,0 0,0 0,0 0,0Others 0,0 0,0 0,0 0,0 0,0

7.1 Workload By UsersUser activity is measured in the workload monitor. Only users of at least medium activity are counted as 'activeusers'.

Users Low Activity Medium Activity High Activity Total Usersdialog steps per week 1 to 399 400 to 4799 4800 or more measured in system 4 0 0 4

7.2 Workload Distribution SEPThe performance of your system was analyzed with respect to workload distribution. We did not detect any majorproblems that could affect the performance of your SAP System.

7.2.1 Workloadby Application Module

The following diagrams show how each application module contributes to the total system workload. Twoworkload aspects are shown:- CPU time: total CPU load on all servers in the system landscape- Database time: total database load generated by the application

All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the"Not-Assigned" category. Customer programs, industry solutions, and third-party add-on developments fall intothis category.



7.2.2 DB Load Profile

The number of work processes creating database load in parallel is not significantlyhigh.

The following diagram shows the DB load caused by dialog, RFC, HTTP(S), and background tasks, over differenttime frames.

The data in the table represents the average number of database processes occupied by each task type in thedatabase, during the specified time frames.

These statistics are calculated as a weekly average, the average values over six working days with a unit ofone hour. Periods between 00:00-06:00 and 21:00-24:00 contain an average value per hour, as these are notcore business hours.

24-hour monitoring can be enabled by implementing SAP Note 910897. With 24-hour monitoring, the timeprofile returns the workload of the system or application server hourly, rather than returning an average valueper hour for periods between 00:00-06:00 and 21:00-24:00.

By comparing the load profiles for dialog and background activity, you can get an overview of the volume ofbackground activity during online working hours.



8 Performance Overview SEP

The performance of your system was analyzed with respect to the average response times and totalworkload. We did not detect any major problems that could affect the performance of your system.

Rating Check Performance Evaluation

The following table shows the average response times for various task types:

Averages of Response Time Components in msTasktype

DialogSteps

ResponseTime

CPUTime

WaitTime

LoadTime

DBTime

GUITime

DIALOG 3 6,0 0,0 0,0 0,0 0,0 0,0RFC 706 519,4 18,5 1,4 0,8 7,0 0,0BATCH 3303 386,2 49,2 0,3 1,8 74,3 0,0SPOOL 1098 5,6 0,7 0,3 0,1 0,4 0,0

8.1 Performance Evaluation



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

- If the number of dialog steps in an hour is less than 1000, this hour is not considered.

- If the total number of transaction steps is less than 24000, the rating for the task is not performed (indicatedby a gray icon in the table).

Task Steps Application Server Performance Database Server PerformanceDia 3Upd 0HTTP 0HTTPS 0

The ratings in the table above are determined by comparisons against the reference table below.

If the dialog response times are very poor, it will cause a RED rating for the entire check.

TaskReference for Avg.Response Time(ms) Yellow Rating

Reference for Avg.Response Time(ms) Red Rating

Reference forAvg. DB time(ms) YellowRating

Reference forAvg. DB time(ms) Red Rating

Dia 1200 3600 600 1800Upd 2400 3600 1200 1800HTTP 1200 3600 600 1800HTTPS 1200 3600 600 1800

8.2 Transaction Profile CheckThe following tables show the response times and the number of dialog steps for the transactions that cause theheaviest workload in your system.

8.2.1 Transactions by Total Workload

The following tables list the activities with the highest contribution to the total workload.

Workload by Transaction (Batch)

Transaction DialogSteps

TotalResp.Time in %

TotalResp.Time in s

TotalCPU Timein s

Total DBTime in s

SWNC_TCOLL_STARTER 260 38,4 486,0 34,0 75,6RSBTCDEL2 7 15,2 192,0 53,0 53,5RSAL_BATCH_TOOL_DISPATCHING 11 9,2 116,0 1,0 0,2RSBPCOLL 7 7,9 101,0 12,0 40,3(BATCH) 2207 6,4 81,0 11,0 12,0RSBTCRTE 548 5,0 63,0 22,0 7,8RSN3_STAT_COLLECTOR 11 4,4 55,0 0,0 0,2RSTS0043 1 3,9 50,0 10,0 6,5RSLDAGDS 1 2,6 33,0 6,0 3,1RSXMB_ARCHIVE_MESSAGES 7 1,7 21,0 2,0 3,9



8.2.2 Transactions by DB Load

The following transaction profiles list the transactions that have the greatest share in the database load, sortedby percentage of total database access times.

Database Load by Transactions (Batch)

Transaction DialogStepsTotal DB Time in%

Total DB Time ins

SWNC_TCOLL_STARTER 260 31,4 76,0RSBTCDEL2 7 22,2 53,0RSBPCOLL 7 16,8 40,0RSPO1043 7 5,6 13,0(BATCH) 2207 5,0 12,0RSPO0041 7 3,3 8,0RSBTCRTE 548 3,2 8,0RSTS0043 1 2,7 6,0RSXMB_ARCHIVE_MESSAGES 7 1,6 4,0BTC_DELETE_ORPHANED_IVARIS 1 1,6 4,0

8.3 RFC Load by Initiating ActionThe load in task type RFC is shown. In the workload monitor, this information is shown as 'Load from ExternalSystems'. The calling system can be an application server of the system itself or any external system using theRFC interface. The 'Initial Action' is the calling program initiating the RFC. The total response time for each initialaction is shown as an absolute value and as a percentage compared to the total RFC load considered in thistable. Because this total RFC load may differ from the load in the 'Performance Overview' section, the load ofthat section is listed for comparison. 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 areshown if they account for at least 24h or 20% of the total RFC load.

Load OverviewInitial System Load [s] Load %Local system SEP 180 49,13Sum of external systems 186 50,87RFC load (sum of above) 367 100,00RFC load in Performance Overview 367 100,03Load of all task types in Performance Overview 2.326 634,46

Top 20 RFC Calls From External Systems - Average Times [ms]

InitialSystem Initial Action

TotalResp.Time in s

% ofRFCLoad

Avg.ResponseTime

Avg.CPUTime

Avg.DBTime

Avg.RollWaitTime

SMP LANDSCAPE FETCH 185 50,38 4.504,4 39,2 57,0 0,4SMP SAP_SLD_DATA_COLLECT 2 0,49 127,1 2,2 0,5 0,0

Top 20 RFC Calls FromLocal System - Average Times [ms]

InitialSystem Initial Action

TotalResp.Timein s

% ofRFCLoad

Avg.ResponseTime

Avg.CPUTime

Avg.DBTime

Avg.RollWaitTime



SEP SAP_COLLECTOR_PERFMON_SWNCCOLL 106 28,98 376,7 16,7 5,8 1,5SEP SAP_COLLECTOR_PERFMON_RSAMON40 41 11,17 758,0 35,6 1,5 6,4SEP SAP_CCMS_MONI_BATCH_DP 14 3,88 154,4 25,8 5,5 0,3SEP SAP_COLLECTOR_PERFMON_RSHOSTDB 13 3,67 364,0 46,0 6,4 3,0SEP SAP_COLLECTOR_PERFMON_RSICFDMN 2 0,45 46,7 6,2 2,9 0,0SEP SAP_COLLECTOR_PERFMON_RSRFCDMN 2 0,44 48,9 7,1 0,4 0,5SEP ARV_BC_XMB_WRP20140130003002 1 0,16 297,5 8,0 0,0 0,0SEP ARV_BC_XMB_WRP20140201003016 1 0,15 270,0 0,0 0,0 0,0SEP ARV_BC_XMB_WRP20140202003023 0 0,09 333,0 16,0 0,0 0,0SEP SAP_COLLECTOR_FOR_NONE_R3_STAT 0 0,08 77,8 11,8 0,5 4,0SEP ARV_BC_XMB_WRP20140127003002 0 0,06 233,0 0,0 0,0 0,0

9 SAP System Operating SEP

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

Rating CheckAvailability based on Collector ProtocolsProgram Errors (ABAP Dumps)Update ErrorsTable Reorganization

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

We did not detect any problems.

9.2 Program Errors (ABAP Dumps)No ABAP dumps have been recorded in your system in the period analyzed. ABAP dumps are generally deletedafter 7 days by default. To view the ABAP dumps in your system, call transaction ST22 and choose Selection.Then select a timeframe.

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.



10 Security

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

Rating CheckSAP Security Notes: ABAP and Kernel Software CorrectionsDefault Passwords of Standard UsersControl of the Automatic Login User SAP*ABAP Password PolicyGateway and Message Server SecurityUsers with Critical Authorizations

10.1 ABAP Stack of SEP

10.1.1 SAP Security Notes: ABAP and Kernel Software Corrections

Software corrections from SAP Security Notes are missing in this system. Your system is probably exposed tosecurity threats.You have also marked 2 security-related SAP Notes as not to be considered.

Recommendation: Apply SAP Security Notes that are relevant to your system.

A complete list of SAP Security Notes, including Security HotNews, is available on SAP Service Marketplace, athttps://service.sap.com/securitynotes.

The RSECNOTE tool in transaction ST13 provides a list of missing SAP Security Notes. RSECNOTE covers SAPSecurityHotNews with software-related corrections for ABAP or kernel, and a selection of other SAP SecurityNotes.For more information, see SAP Note 888889.

In the Security Notes list at the SAP Service Marketplace location above, the "Automatic check in EWA" flag(last column) identifies those SAP Security Notes for which the implementation is fully checked by theRSECNOTE tool.

10.1.2 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 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 ASABAP Security Guide.

Make sure that the standard password for user TMSADM has been changed in client 000 and delete this userin any other client. SAP Note 1414256 describes a support tool to change the password of user TMSADM in allsystems of the transport domain.SAP Note 1552894 shows how to update the report RSUSR003 to show the status of user TMSADM.

10.1.3 Control of the Automatic Login User SAP*

The profile parameter login/no_automatic_user_sapstar is set to 0 on at least one instance.

If the user master record belonging to user SAP* is deleted, it is possible to log on again with SAP* and theinitial password. SAP* then has the following attributes:- Theuser has all authorization, as authorization checks cannot be executed.- You cannot change the standard password.You can deactivate the special attributes of SAP* using profile parameter login/no_automatic_user_sapstar.

Recommendation: Set profile parameter login/no_automatic_user_sapstar to 1. For further information, seeSAP Note 68048.

10.1.4 ABAP Password Policy

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

10.1.4.1 Password Complexity

Parameter: login/min_password_lngRating Instance Current Value(s) Recommended Value

All instances 6 8

The current system settings allow a password length less than 8 characters.This allows weak passwords. Attackers may successfully recover these passwords and exploit this to gainunauthorized 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 thecorresponding profile parameters in the following table.

Parameter Instance Current Value(s)login/min_password_digits All instances 0login/min_password_letters All instances 0login/min_password_lowercase All instances 0login/min_password_uppercase All instances 0login/min_password_specials All instances 0

Recommendation: Enforce a minimum of 3 independent character categoriesusing the correspondingprofile parameters. For more information, see SAP Note 862989 and the section Profile Parameters forLogon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAPSecurity Guide.

10.1.4.2 Validity of Initial Passwords



Rating Parameter Instance Current Value(s)login/password_max_idle_initial All instances 0

There is no time restriction on the validity of initial passwords.

Recommendation: Proceed as follows:-- Handle users of type C (Communication) with initial passwords, because they will be locked if the profileparameter aboveis 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.-- 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.

10.1.5 Gateway and Message Server Security

10.1.5.1 Gateway Security

Gateway Access Control Lists

Parameters: gw/sec_info gw/reg_infoRating Instance Error Condition

All instances gw/reg_info and gw/sec_info are defined

reg_infoRating Instance Error Condition File does not exist (default)

vss-p-erpcia_SEP_01 TP=* HOST=* vss-p-erpcib_SEP_02 vss-p-erpsa1_SEP_03 TP=* HOST=*

sec_infoRating Instance Error Condition File does not exist (default)

USER=*, HOST=*, TP=* USER=*, HOST=*, TP=*

10.1.6 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 (transactionPFCG) to correct roles and authorizations. You can use the User Information System (transaction SUIM) tocheck the results. For each check, you can review the roles or profiles that include the authorization objectslisted in the corresponding section.

10.1.6.1 Super User Accounts

Users with authorization profile SAP_ALL have full access to the system. There should be a minimum of suchusers. 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 3 4001 2 2300 5 10

Authorization profile: SAP_ALL

11 Software Change and TransportManagement of SEP

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

11.1 SAP Netweaver Application Server ABAP of SEP

11.1.1 Number of Changes

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

No data from the managed system could be found in the configuration and change database (CCDB). Checkwhether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465.Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data sourcefor various support services.The CCDB data is required here to check the configuration of the managed system.

12 Database Performance

No major performance problems have been found in your database system.



Rating CheckWait StatisticsIO PerformanceMissing Indexes

12.1 Wait StatisticsThe wait statistics of the SQL Server show long wait times for the event(s) highlighted below. This can indicateslow performance of the I/O system or other unusual conditions. Wait time for some events may indicate aperformance bottleneck while other events are not relevant for performance. In the "Rating" column, you mayfind the following

symbols:"Gray diamond" - not relevant for performance; can be ignored."Red flash" - in a well-tuned database, the event should not appear among the top events. Its appearanceindicates a bottleneck and thus potential for improvement. See explanations below."Yellow exclamation mark" - it is normal that the wait event is among the top events, but its average valueexceeds a threshold. An improvement may be possible."Blue information sign" - this wait event is important for performance but does not have a critical value.No symbol - we do not have experience with a wait event of that type. If the overall database performance isnot affected; it can be ignored.

Wait type Wait time(ms) RequestsWait time /Requests Rating

Analysis timeframe (ms): 845.038.140 Total 6.786.148.900 217.259.170 31,24REQUEST_FOR_DEADLOCK_SEARCH 845.050.110 168.996 5.000,41LAZYWRITER_SLEEP 845.042.110 854.181 989,30LOGMGR_QUEUE 845.038.140 275.955 3.062,23XE_TIMER_EVENT 845.036.740 28.169 29.998,82SQLTRACE_INCREMENTAL_FLUSH_SLEEP 844.884.100 211.203 4.000,34CHECKPOINT_QUEUE 843.251.010 603 1.398.426,22FT_IFTS_SCHEDULER_IDLE_WAIT 838.028.480 13.968 59.996,31SLEEP_TASK 422.702.140 3.131.682 134,98BROKER_TO_FLUSH 422.525.020 412.537 1.024,21OLEDB 15.617.615 201.497.860 0,08PAGEIOLATCH_SH 11.815.703 981.699 12,04WRITELOG 2.424.829 440.085 5,51SLEEP_BPOOL_FLUSH 1.333.220 135.056 9,87



12.2 I/O PerformanceThe following tables ("Data files" and "Log files") show how I/O operations are distributed over the data files andlog files respectively.

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

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

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

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

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

Note: The average wait time for each I/O operation (IOStallRead) of the files with YELLOW rating deviates bymore than 50% from the best one. If this is not expected behavior of your storage subsystem, contact thestorage administrator or vendor. There may be potential to improve performance for the corresponding logicalvolumes.

Data Files

File Reads % ofReads Writes% ofWrites

IOStallWrite [ms] /write request

IOStallRead [ms] /read request

FileID 1 25790 13.05 26512 5.07 17.51 65.32

FileID 2 331 0.17 321003 61.38 12.90 35.65

FileID 3 24483 12.39 20925 4.00 17.70 67.91

FileID 4 24907 12.60 25444 4.86 17.10 67.17

FileID 5 24910 12.60 25021 4.78 18.05 68.47

FileID 6 23812 12.05 22261 4.26 18.32 73.06

FileID 7 25210 12.76 33302 6.37 19.50 73.23

FileID 8 24132 12.21 21970 4.20 18.63 74.30

FileID 9 24066 12.18 26575 5.08 17.38 81.48

Total 197641 100 523013 100 14.89 71.23

IO related wait events

Wait type Wait time(ms) RequestsWait time /Requests

ReferenceValue Rating

Analysis timeframe(ms): 845.038.140

PAGEIOLATCH_SH 11.815.703 981.699 12,04 15,00WRITELOG 2.424.829 440.085 5,51 6,00



IO_COMPLETION 828.896 178.477 4,64 PAGEIOLATCH_EX 428.500 14.943 28,68 PAGEIOLATCH_UP 15.738 1.093 14,40 ASYNC_IO_COMPLETION 5.897 10 589,70

12.3 Missing IndexesThis check verifies that the indexes defined by SAP application developers in the SAP data dictionary also exist inthe database. Missing primary indexes can lead to inconsistent data in the SAPsystem. A missing index of anykind can lead to severe performance problems.

No missing indexes were found on system SEP.

13 Database Administration

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

Rating CheckDatabase GrowthLargest TablesTop Growing TablesService Pack CheckTables With Page Locking DisabledDatabase Options

13.1 Environment and OperatingIn this section, basic information on the database and its software environment are shown.

13.1.1 Database Growth

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



13.1.2 Largest Tables

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

Used (data + indexes) kB 1285312

Table Name Data(kB)Reserved (data +indexes) kB Rows

ModifiedRows

REPOLOAD 13785736 13800256 13798488 252856 6093REPOSRC 6103744 6285440 6264312 3402512 541810D010TAB 591240 1824512 1823824 29744291 76137DD03L 342176 1481088 1478312 6453384 706312DDNTF 1307736 1320320 1316888 820054 36867DOKCLU 1275304 1298304 1298008 1935874 18438DDNTF_CONV_UC 1276224 1288264 810964 0DYNPLOAD 948552 962496 950248 43221 251D010INC 308968 789056 788552 10887039 49239FPLAYOUTT 662616 663440 662688 2907 124

13.1.3 Top Growing Tables

Table Name Data(kB)Delta DataSize (kB)

Indexes(kB)

Delta IndexSize (kB)

DeltaReservedSize (kB)

DeltaRows

REPOSRC 6161712 9656 102560 608 13056 279sap_perfinfo 347696 3584 0 0 3456 13346BALDAT 231976 2776 0 0 2752 5043WDY_CTLR_COMPO 217672 1272 0 0 1184 274DD03L 348776 904 1129536 1568 2688 99E071 208608 864 191528 208 1152 1640TADIR 134464 800 169416 392 1280 79



SEOCOMPODF 167432 640 114896 376 1024 103OCSCMPLOBJ 394984 504 68872 112 640 1507SEOSUBCODF 114392 488 100976 256 768 206

The table above shows the top 10 growing tables (Delta Data Size) within the last two months.

13.1.4 Service Pack

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

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

BuildIn Use Builds Comment

ReleaseDate

2769 10.50.2769 SQL SERVER 2008 R2 Service Pack 1 CumulativeUpdate 1 18.07.2011

10.50.2772 SQL SERVER 2008 R2 Service Pack 1 CumulativeUpdate 2 15.08.2011



10.50.2799 2633357 FIX: "Non-yielding Scheduler" error 22.02.2012


10.50.2807 2675522 FIX: Access violation when you run DMLstatements against a table that has partitioned indexes 12.03.2012


10.50.3720 SQL Server 2008 R2 Service Pack 2 CTP 13.05.2012 10.50.4000 SQL Server 2008 R2 Service Pack 2 26.07.2012

10.50.4260 2720425 Cumulative update package 1 (CU1) for SQLServer 2008 R2 Service Pack 2 01.08.2012





10.50.4285 2830140 Cumulative update package 6 (CU6) for SQLServer 2008 R2 Service Pack 2 (updated) 13.06.2013


Ensure that you are always using the latest SQL server builds. Full information about all SQL server builds islinked in Microsoft's Knowledge Base Article 321185.

13.2 Installation Checks



In this section database configuration properties are checked, which are normally set during the installation orare only rarely changed.

13.2.1 Tables With Page Locking Disabled

Table Page locking RatingEDI40 Page locking disallowedREPOSRC Page locking disallowedVBMOD Page locking disallowedD010TAB Page locking disallowedVBHDR Page locking disallowedARFCSDATA Page locking disallowedREPOLOAD Page locking disallowedD010INC Page locking disallowedTRFCQIN Page locking disallowedVBDATA Page locking disallowedEDIDS Page locking disallowedCOVREF Page locking disallowedEDIDC Page locking disallowedARFCRDATA Page locking disallowedTRFCQOUT All lock levels allowed

As shown above, page locking must be disallowed for some tables.

Recommendation: Disallow page locking for tables VBDATA, VBHDR, VBMOD, ARFCRDATA, ARFCSDATA,EDIDC, EDIDS, EDI40, TRFCQUEUE (if it exists), TRFCQOUT, TRFCQIN, D010TAB, D010INC, REPOLOAD,REPOSRC, and COVREF as described in SAP Note 1609057.

Implementation: You can do this using SQL command: EXEC sp_indexoption ,"DisAllowPageLocks", "TRUE"

Background: For some tables, disallowing page locks improves the concurrency of accesses from differentusers to these tables, therefore avoiding deadlocks.

13.2.2 Database Options

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

DB Option Description Option Value Recommended Value RatingRecovery RECOVERY MODEL SIMPLE FULL

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

Recommendation: Set the recovery model of the SEP database to 'FULL' using SQL Enterprise Manager. Usingany other recovery model significantly increases the risk of data loss in the event of disk failure. You must thenback up the SEP database completely.

We have detected that table statistics are not created as recommended.

Recommendation: Ensure that the following database options in the SAP System database are activated:



- Auto create statistics

- Auto update statistics

- Asynchronous update statistics

Implementation: Set database options "Auto create statistics", "Auto update statistics", and "Asynchronousupdate statistics" in your database. For detailed information, refer to Books Online "Setting Database Options".

14 Database and ABAP Load Optimizationof SEP

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

14.1 Analysis of DB SQL CACHE on 03.02.2014 23:39:13Expensive SQL Statements Overview

Object NameElapsedtime[%]

Calls[%] Calls Total rows estimated

Logicalreads[%]

Physicalreads[%]

CPUtime[%]

SQL_SCRIPT 10 0 703 7.0300000000000000E+02 15 18 9SQL_SCRIPT 4 0 9 9.0000000000000000E+00 10 3 4SQL_SCRIPT 0 0 704 7.0400000000000000E+02 6 0 1SQL_SCRIPT 0 0 6 6.0000000000000000E+00 4 1 1SQL_SCRIPT 0 0 704 7.0400000000000000E+02 3 0 0TTREE_SFW_NODES 0 0 35580 3.5580000000000000E+04 3 0 2SQL_SCRIPT 0 0 161 1.6100000000000000E+02 3 0 0SQL_SCRIPT 1 1 123231 1.2323100000000000E+05 2 0 5SQL_SCRIPT 0 0 9 9.0000000000000000E+00 2 0 0SQL_SCRIPT 0 9 1107041 1.1070410000000000E+06 2 0 0

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

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

14.1.1 Access on SQL_SCRIPT



Statement Data:

Cache StatisticsObjecttype Calls

Total elapsedtime[ms]

Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 703 648326 922,00 1

insert into sap_workload_snapshot select * from #c -- -- Collect some performance counters -- Execution PlanNo explain

SQL Scripts

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


Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 9 276630 30.737,00 1

INSERT INTO @size_sample select MAX(ISNULL(new.sampledate,'')), MAX(ISNULL(old.sampledate,'')), [object_id], OBJECT_NAME(OBJECT_ID) AS [NAME] , schema_id(object_schema_name([object_id])) AS [SCHEMA] , [index_id] , sum(used_page_count) * 8 ASUSED_KB, sum(reserved_page_count) * 8 AS RESERVED_KB, sum(row_count) AS ROW_COUNT, stats_date([object_id],[index_id]) AS [STATS_DATE], ( select count(*) from sys.indexes whereobject_id = ps.object_id and indexproperty(object_id,name,'IsStatistics') = 0 ) AS NUM_INDEXES, ( select count(*) from sys.stats where object_id = ps.object_id and indexproperty(object_id,name,'IsStatistics') = 1 ) AS NUM_STATS from sys.dm_db_partition_stats ps left outer join sap_tabstats_V_newest new on ps.object_id = object_id( new.tablename ) and schema_id(object_schema_name([object_id])) = new.uid left outer join sap_tabstats_V_oldest old on ps.object_id = object_id( old.tablename ) and schema_id(object_schema_name([object_id])) = old.uid where ps.object_id > 100 group by [object_id],[index_id] having sum(reserved_page_count) > 0 -- delete tables from sap_tabstats which don't exist anymore Execution PlanStatement not in SEP

SQL Scripts



Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.



TABLE 704 19422 27,59 1

UPDATE #perfinfo SET accumulat = b.accumulat, to_id = ( SELECT MAX(to_id)FROMsap_perfvali c WHEREc.counter_id = a.COUNTER_ID AND c.inst_name = a.INST_NAME ) FROM#perfinfo a, @perfcntr b WHEREa.COUNTER_ID = b.counter_id -- Join the counter value of the previous measurementExecution PlanNo explain

SQL Scripts

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


Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 6 29696 4.949,00 1

SELECT statement with PIVOT clause ----*/ Execution PlanASSIGN(@P1 nvarchar(4000),@P2 nvarchar(4000),@P3 nvarchar(4000),@P4 nvarchar(4000))--sap_dbszhist: Get the database size history from the DB Collector data declare@db_name sysname declare @obj_schema sysname declare @from_dt datetime declare @to_dset @obj_schema = @P2 set @from_dt = @P3 set @to_dt = @P4 begin declare @stmt nvarchar(max) declare @par nvarchar(200) set nocount on create table #coll ( TIMESTMP datetime , obj_name varchar(128) , cntr_name varchar(128) , INST_NAME varchar(128) , CNTR_VALUE bigint ,SLOPE float ) if @db_name is null or @db_name = N'' |-- select @db_name = DB_NAME() if @obj_schema is null or @obj_schema = N'' |-- select @obj_schema = schema_name() if @to_dt is null or @to_dt = N'' |-- set @to_dt = GETDATE() if @from_dt is null or @from_dt = N'' |-- set @from_dt = DATEADD(YEAR,-3,@to_dt) set @stmt = N'exec [' + @obj_schema + N'].sap_coll_list '+ N'@obj_schema,@cclass,@from_dt,@to_dt,@step,@stepunit' set @par = N'@obj_schema sysname,@cclass char(1),'+ N'@from_dt datetime,@to_dt datetime,@step int,@stepunit char(1)' insert into #coll exec sp_executesql @stmt,@par, @obj_schema,'s',@from_dt,@to_dt,1,'D' /*--- Dynamically construct SELECT statement with PIVOT clause----*/ |-- Table Insert SET: [#coll].[TIMESTMP] = [Parameter Table].[TIMESTMP] as[ParameterTable].[TIMESTMP],[#coll].[obj_name] = [Parameter Table].[obj_name] as[ParameterTable].[obj_name],[#coll].[cntr_name] = [Parameter Table].[cntr_name] as[Paramete|-- Top|-- Parameter Table Scanset @stmt = N'select sampledate,sampletime,dbname,' + N'"Database size[MB] ' +@db_name + N'",' + N'"Used[MB] ' + @db_name + N'",' + N'"Log size[MB] ' + @db_name+ N'",' + N'"Log allocated[MB] ' + @db_name + N'",' + N'"Reserved[MB] 'set @stmt = @stmt + N'"Database size[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"Used[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"Log size[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"Log allocated[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"Reserved[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"# of tables ' + @db_name + N'",' set @stmt = @stmt + N'"Table data size[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"# of indexes ' + @db_name + N'",' set @stmt = @stmt + N'"Index data size[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"Unused[MB] ' + @db_name + N'",' set @stmt = @stmt + N'"# of procedures ' + @db_name + N'"' set @stmt = @stmt + N') ) AS PVT ORDER BY sampledate desc' /*--- Execute the selectstatement and cleanup table --------*/ --print @stmt



exec(@stmt) drop table #coll

SQL Scripts



Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 704 5121 7,27 1

UPDATE #perfinfo SETnorm_value = 0 WHEREnorm_value IS NULLExecution PlanNo explain

SQL Scripts


14.1.6 Accesson TTREE_SFW_NODES

Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 35580 30094 0,85 1

SELECT T_00 ."SFW_ASS_ID" AS c ,T_00 ."SWITCH_ID" AS c ,T_00 ."TREE_ID" AS c ,T_00 ."NODE_ID" AS c ,T_00 ."REACTION" AScFROM"TTREE_SFW_NODES" T_00 ,(SELECT "C_01" = @P1 , "C_02" = @P2 UNION SELECT @P3 , @P4 UNION SELECT @P5 , @P6 UNION SELECT@P7, @P8 UNION SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 , @P14 UNION SELECT @P15 , @P16 UNION SELECT@P17 , @P18 UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23 , @P24 UNION SELECT @P25 , @P26 UNIONSELECT @P27, @P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT @P33 , @P34 UNION SELECT @P35 , @P36UNION SELECT @P37 , @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION SELECT @P43 , @P44 UNION SELECT @P45 ,@P46 UNION SELECT @P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION SELECT @P53 , @P54 UNION SELECT@P55 , @P56 UNION SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62 UNION SELECT @P63 , @P64 UNIONSELECT @P65 , @P66 UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71 , @P72 UNION SELECT @P73 , @P74UNION SELECT @P75 , @P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT @P81 , @P82 UNION SELECT @P83 ,@P84 UNION SELECT @P85 , @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION SELECT @P91 , @P92 UNION SELECT@P93 , @P94 UNION SELECT @P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) T_01WHERET_00 ."TREE_ID" = T_01 .C_01 AND T_00 ."NODE_ID" = T_01 .C_02 /* R3:SAPLSHI25:187 T:TTREE_SFW_NODES */ Execution Plan|-- Nested Loops|-- Nested Loops|-- Merge Join



|-- Index Seek SEEK: [TTREE_SFW_NODES].TREE_ID EQ [Union1002] AND [TTREE_SFW_NODES].NODE_ID EQ [Union1003] ORDERED 1|-- Clustered Index Seek SEEK: [TTREE_SFW_NODES].SFW_ASS_ID EQ [SEP].[sep].[TTREE_SFW_NODES].[SFW_ASS_ID] as [T_00].[SFW_ASS_ID] ORDERED 1


Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 161 7843 48,71 1

UPDATE #perfinfo SET norm_value = ( SELECT TOP 1 cntr_valueFROMsap_perfinfo b WHEREb.counter_id = a.COUNTER_ID AND b.inst_name = a.INST_NAME AND b.resi_flag = 0 AND b.sample_id > @thresh ORDER BYb.sample_id DESC ), old_value = ( SELECT TOP 1 cntr_valueFROMsap_perfinfo b WHEREb.counter_id = a.COUNTER_ID AND b.inst_name = a.INST_NAME AND b.resi_flag = 0 ORDER BYb.sample_id DESC ) FROM#perfinfo a -- Correct overflowsExecution PlanNo explain

SQL Scripts



Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 123231 95850 0,78 1

if ( @olddate @newdate and @newdate IS NOT NULL and @olddate is NOT NULL and EXISTS( select * from sap_tabstats s where s.sampledate =@newdate and s.tablename =@tabname and s.uid = @schema_id and s.totalrows = @rows and s.datasize = @data and s.reserved =@reserved and s.indexsize = @index and s.indexdepth = @index_depth and s.numindexes =@num_inds and s.numstats = @num_stats and tableoptions = @table_opts )) -- Save records to update insap_tabstats later Execution PlanStatement not in SEP

SQL Scripts

This statement comes from an expensive SQL script or from a stored procedure (SP) which exists at DB leveland is not originated from the ABAP stack. We cannot analyze this statement in detail.Recommendation: Check if:a) The script or SP has to be run at all.b) The script or SP can be run less frequently.



c) The script or SP can be tuned so that it consumes fewer database resources.


Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 9 19336 2.148,00 1

update sap_tabstats set sampledate = us.newsampledate, lastduration = us.lastduration from sap_tabstats ts innerjoin @upd_stats us on ts.sampledate = us.sampledate and ts.tablename = us.tablename and ts.uid = us.uid Execution PlanStatement not in SEP

SQL Scripts

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


Statement Data:



Elapsedtime[ms]/row

Estimatedrows/exec.

TABLE 1107041 5855 0,53E-02 1

FETCH NEXTFROMgrid INTO @sample_id, @stype, @cntr_valExecution PlanSET ON/OFF-- =================================================================== -- Data rollupschedule: -- Phase 1: Records younger than @retention/6 days -- All scheduledsnapshots will be retained -- Phase 2: Records younger than @retention days declare @phase smallint declare @gridline datetime declare @t_phase1datetime declare @t_phase2 datetime declare @t_phase3 datetime declare @t_resetdatetime -- time threshold for "since reset" declare @phase3_id intset @phase3_id = NULL -- Calculate time thresholdsset @gridline = convert (datetime, convert(varchar(10), getdate(), 112))set @t_phase1 = dateadd (Day, - @retention/6, @gridline)set @t_phase2 = dateadd (Day, - @retention, @gridline)set @t_phase3 = dateadd (Day, - @retention * 12, @gridline)set @t_reset = dateadd (Hour, -72, getdate())set @gridline = @t_phase1set @reset_id = ( select TOP 1 sample_id from sap_perfsample where startat = @startat|-- if @phase = 1|-- set @gridline = dateadd(Hour, -1, @gridline)|-- else if @phase = 2|-- set @gridline = dateadd(Day, -1, @gridline)|-- else -- error ! break|-- END ELSE -- @startat >= @gridline set @stype = 'Z' ---- Insert @sampler record|-- INSERT INTO @sampler VALUES (@sample_id, @startat, @stype)|-- Table Insert SET: [sample_id] = [@sample_id],[startat] = [@startat],[stype] =[@stype]|-- FETCH NEXT FROM curs INTO @sample_id, @startatEND ---- Cursor cleanup CLOSE cursDEALLOCATE curs ---- Remove unnecessary @sampler recordsDELETE FROM @sampler WHERE sample_id IN ( SELECT a.sample_id from @sampler a, @samplerb WHERE a.stype = 'T' AND b.stype = 'T' AND b.sample_id = ( select top 1 sample_id from@sampler where sample_id < a.sample_id order by sample_id desc ) ) --sele|-- Table Delete|-- Top|-- Sort ORDER BY: .Bmk1000 ASC|-- Nested Loops WHERE: [sample_id]=@sampler.[sample_id] as [b].[sample_id]|-- Nested Loops|-- Nested Loops WHERE: [sample_id]=@sampler.[sample_id] as [a].[sample_id]|-- Sort ORDER BY: .Bmk1000 ASC|-- Table Scan|-- Table Scan WHERE: @sampler.[stype] as [a].[stype]='T'|--Sort|-- Table Scan WHERE: [sample_id]



|-- Clustered Index Scan WHERE: [SEP].[sep].[sap_perfvali].[to_id]



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.

15.2 Response TimesThe following diagrams show how the response time varies over time.

The "System Performance" diagram below shows the average response time in dialog tasks for the previousweek.

Historical data for "System Performance" is obtained from the Workload Monitor (ST03).



The "Database Performance" diagram below shows the average DB response time in dialog tasks.

The "Top 5 transactions" diagram below show the average response time in dialog tasks for the top 5transactions.



The "Transaction Code" table below shows the loadpercentage caused by the top 5 transactions.



15.3 Application profileIn the following, we analyzed the trend within the following time frames:

Short term: From calendar week 01/2014 to 01/2014

Long term: From calendar week 37/2013 to 01/2014

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

Top Applications by Response Time

Tasktype Application

TotalResp.Time ins

% ofTotalLoad

Avg.Resp.Time inms

LongTermGrowth(%/year)

ShortTermGrowth(%/year)

Avg.DBTimein ms

Avg.CPUTime inms

Dialog



15.5 Hardware Capacity

Report time frame: Service data was collected starting at 03.02.2014 23:35:33. This took 4 minutes.

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

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

Local DiskEarlyWatch Alert-SAP Solution

Documents

EWA_SEP