SAP EWA

SERVICE REPORT

SAP EarlyWatch Alert

SAP System ID TT5

SAP Product SAP ERP 6.0

Status Not Productive

DB System SQL SERVER 2005

Customer SAP AG 69190 Walldorf Germany

Processed on SAP Solution Manager TT4 Release EHP 1 for Solution Manager 7.0 Service Tool 701_2010_1 SP3 Service Content Update on 09.06.2011

Analysis from 06.06.2011 Session No. 2000000004683 Until 12.06.2011 Installation No. 0120003411 Customer No. 0000029149

Service Summary

EarlyWatch Alert, SAP AG, 06.06.2011 - 12.06.2011 2

1 Service Summary

The EarlyWatch Alert Service has detected severe problems that may cause you to lose business. We recommend that you take corrective action immediately.

ALERTS DECISIVE FOR RED REPORT

With the SAP kernel of your ABAP system the stability or consistency is at risk.

ALERT OVERVIEW

Security-related SAP HotNews have not been applied in the system.

Secure password policy is not sufficiently enforced.

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

The long-term analysis on response time and applications shows a critical trend.

We found more than 30 ABAP dumps in your system.

Standard users have default password.

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

Note: All recommendations provided in this report are based on our general experience. We advise that you

test our recommendations before using them in your production system. Note that EarlyWatch Alert is an automatic service.

CHECK OVERVIEW

Topic Rating

Topic Subtopic Rating

Subtopic

System Configuration

Hardware Configuration

System Performance

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

Database Administration

Largest Tables

Top Growing Tables

Service Pack Check

Tables With Page Locking Disabled

Performance Indicators for TT5


Topic Rating

Topic Subtopic Rating

Subtopic

Database Options

Database Interface Library Version

Remote Function Call

RFC wait time profile for Instance &YSAP-INS_NAME&

Security

SAP Security Notes: ABAP and Kernel Software Corrections

Default Passwords of Standard Users

Password Policy

Gateway and Message Server Security

Users with Critical Authorizations

Software Change Management

Java Performance Data

Availability of Java Performance Data

Java VM Activity Reporting

Java Application Performance

DEVIATION FROM LAST SESSION

Old --> New Topic Subtopic

--> SAP System Operating Program Errors (ABAP Dumps)

--> Hardware Capacity Hardware Capacity

Note: If you have any questions concerning the correctness of the checks in this report, or concerning the

correct configuration of the Solution Manager EarlyWatch Alert service, create a customer message in 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. SAP Note 67739 contains details of how to set the appropriate priority level.

2 Performance Indicators for TT5

The following table shows the relevant performance indicators in various system areas.

Area Indicators Value Trend

System Performance Active Users 5

Average Response Time in RFC Task 538 ms

Max. number of RFCs per hour 547

Average RFC response time during peak work hour 1287 ms

Avg. Availability per Week 94 %

Hardware Capacity Max. CPU Utilization on DB Server 61 %

Database Performance Average DB time for RFC 192 ms

Avg. DB Request Time in Update Task 1208 ms

Database Space Management DB Size 229.32 GB

Last Month DB Growth 0 GB

Landscape Overview


3 Landscape Overview

3.1 Products and Components in current Landscape PRODUCT

SID SAP Product Product Version

TT5 SAP ERP 6.0

MAIN INSTANCES (ABAP OR JAVA BASED)

SID Main Instance

TT5 Enterprise Portal

TT5 SAP ECC Server

DATABASES

SID Database System Database Version

TT5 SQL SERVER 2005

3.2 Servers in current Landscape SAP APPLICATION SERVERS

SID Host Instance Name Logical Host ABAP JAVA

TT5 TWDF1847 tt5tdc00_TT5_50 tt5tdc00

DB SERVERS

SID Host Logical Host (SAPDBHOST)

TT5 TWDF1847 tt5tdc00

COMPONENTS

Related SID Component Host Instance Name Logical Host

TT5 Java SCS TWDF1847 tt5tdc00_TT5_03 tt5tdc00

3.3 Hardware Configuration SERVER OVERVIEW

Server Operating System No. of CPUs Memory in MB

TWDF1847 Windows Server 2003 (x86_64) (SP 2) 4 16382

4 Software Configuration

The software versions of your systems are checked. If known issues with the software versions installed are identified they are highlighted.

Software Configuration


4.1 SAP Application Release: Maintenance Phases

SAP Product SAP Product Version End of Mainstream Maintenance End of Ext. Maintenance

SAP ERP 6.0 31.12.2015 31.12.2017

Your system TT5 is running on SAP ERP 6.0. This release will be in mainstream maintenance until 31.12.2015.

4.2 Support Package Maintenance - ABAP SUPPORT PACKAGES

Software Component

Version Patch Level

Latest Avail. Patch Level

Support Package Component Description

AIN 400 2 6 SAPK-40002INAIN SAP Auto-ID Infrastructure

BI_CONT 703 8 16 SAPKIBIIP8 SAP Business Intelligence Content

CPRXRPM 400 11 19 SAPK-40011INCPRXRPM

EA-APPL 600 11 19 SAPKGPAD11 SAP R/3 Enterprise PLM, SCM, Finance

EA-DFPS 600 11 19 SAPKGPDD11 SAP R/3 Enterprise Defense Forces & Public Security

EA-FINSERV 600 11 19 SAPKGPFD11 SAP R/3 Enterprise Financial Services

EA-GLTRADE 600 11 19 SAPKGPGD11 SAP R/3 Enterprise Global Trade

EA-HR 600 22 70 SAPKGPHD22 SAP R/3 Enterprise Human Resources

EA-IPPE 400 11 19 SAPKGPID11 SAP R/3 Enterprise Integrated Product and Process Engineering

EA-PS 600 11 19 SAPKGPPD11 SAP R/3 Enterprise Public Services

EA-RETAIL 600 11 19 SAPKGPRD11 SAP R/3 Enterprise Retail

ECC-DIMP 600 11 19 SAPK-60011INECCDIMP

ERECRUIT 600 11 19 SAPK-60011INERECRUIT

SAP E-Recruiting

FI-CA 600 11 SAPK-60011INFICA

FI-CAX 600 11 19 SAPK-60011INFICAX

FINBASIS 600 11 19 SAPK-60011INFINBASIS

SAP R/3 Enterprise FINBASIS

INSURANCE 600 11 19 SAPK-60011ININSURANC

IS-CWM 600 11 19 SAPK-60011INISCWM

IS-H 600 12 25 SAPK-60012INISH

IS-M 600 11 19 SAPK-60011INISM

IS-OIL 600 11 19 SAPK-60011INISOIL

IS-PS-CA 600 11 19 SAPK-60011INISPSCA

IS-UT 600 11 19 SAPK-60011INISUT

LCAPPS 2005_700 5 10 SAPKIBHD05

LSOFE 600 11 19 SAPK-60011INLSOFE

PI_BASIS 2006_1_700 0 14 SAP R/3 Basis Plug-In

SAP_ABA 700 13 24 SAPKA70013 SAP Application Basis

SAP_AP 700 11 23 SAPKNA7011

SAP_APPL 600 11 19 SAPKH60011 SAP R/3 Standard

SAP_BASIS 700 13 24 SAPKB70013 SAP Basis Component

SAP_BW 700 15 26 SAPKW70015 SAP Business Information Warehouse



Software Component

Version Patch Level

Latest Avail. Patch Level

Support Package Component Description

SAP_HR 600 22 70 SAPKE60022 SAP R/3 Standard HR

SEM-BW 600 11 19 SAPKGS6011 SAP SEM Server

SLL-LEG 7.00 11 23 SAPK-70011INSAPSLL

ST-A/PI 01M_ECC600 1 SAPKITAR7F

ST-PI 2008_1_700 3 4 SAPKITLRD3 SAP Solution Tools Plug-In

WFMCORE 200 11 18 SAPK-20011INWFMCORE

Workforce Management

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

SUPPORT PACKAGES

Component Version SP Latest Available SP

ADSSAP 7.00 13 024

BASETABLES 7.00 13 024

BI_MMR 7.00 13 024

BI_UDI 7.00 13 024

BP_DMSCONN 6.75 0

BP_ERP4CSP 60.2 0

BP_ERP5ASS 1.0 11

BP_ERP5BUA 1.0 11

BP_ERP5BUY 1.0 11

BP_ERP5COM 1.0 11

BP_ERP5DCO 1.0 11

BP_ERP5ESS 1.0 11

BP_ERP5HRA 1.0 11

BP_ERP5INV 1.0 11

BP_ERP5MSS 1.0 11

BP_ERP5MTC 1.0 11

BP_ERP5PLA 1.0 11

BP_ERP5PRS 1.0 11

BP_ERP5QIN 1.0 11

BP_ERP5SAL 1.0 11

BP_ERP5SUP 1.0 11

BP_RETAIL 60.1 0

CAF 7.00 13 024

CAF-KM 7.00 13 024

CAF-UM 7.00 13 024

CORE-TOOLS 7.00 13 024

DI_CMS 7.00 9

EP-PSERV 7.00 13 024

EP-WDC 7.00 13 024

EPBC 7.00 13 024

EPBC2 7.00 13 024

EP_BUILDT 7.00 9 024

JLOGVIEW 7.00 13 024

JSPM 7.00 13 024

KM-KW_JIKS 7.00 13 024

KMC-BC 7.00 13 024

KMC-CM 7.00 13 024

KMC-COLL 7.00 13 024

LM-PORTAL 7.00 13 024



Component Version SP Latest Available SP

LM-TOOLS 7.00 13 024

NET-PDK 7.00 13 024

RTC 7.00 13 024

RTC-STREAM 7.00 13 024

SAP-EU 7.00 13 024

SAP-JEE 7.00 13 024

SAP-JEECOR 7.00 13 024

SAPPCUI_GP 600 11

SAP_BUILDT 7.00 9 024

SAP_ESS 600 11

SAP_JTECHF 7.00 13 024

SAP_JTECHS 7.00 13 024

SAP_MSS 600 11

UMEADMIN 7.00 13 024

UWLJWF 7.00 13 024

VCBASE 7.00 13 024

VCFLEX 7.00 13 024

VCFRAMEWORK 7.00 13 024

VCKITGP 7.00 13 024

VCKITXX 7.00 13 024

WDEXTENSIONS 7.00 13 024

JDK VERSION

Hostname Instance VM Vendor VM Version

tt5tdc00 DVEBMGS50 Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.) 1.4.2_14-b05

4.4 SAP Kernel Release

Instance(s) SAP Kernel Release Patch Level Age in Months Platform

tt5tdc00 50 700 146 41 Windows X86_64

4.4.1 Issues with current SAP Kernel Your SAP kernel release (release 700, patch level 146) may encounter serious problems. SAP tests all SAP kernels released. However, your patch level has been found to be unstable in certain cases and, therefore, is not recommended. For more information, see the release information for each SAP kernel patch on SAP Service Marketplace. For more information about issues concerning your current SAP kernel, see the SAP Notes in the table below.

Recommendation: If the SAP kernel shipped with the latest Support Package Stack of your product has

the same issue as listed below, install a more recent SAP kernel available in the "Patches" section of SAP Service Marketplace.

SAP Note Number Short Text Risk

1150058 Incomplete update records

Additional Remarks SAP releases Support Package Stacks (including SAP kernel patches) on a regular basis for most products (generally 2-4 times a year). We recommend that you base your software maintenance strategy on these stacks. You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur.

Service Preparation of TT5


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

5 Service Preparation of TT5

System TT5 is not fully prepared for service delivery.

Rating Check Performed

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

Service Preparation Check (RTCCTOOL)

Service Data Control Center

For a detailed analysis, see the checks below. For general information about service preparation, see SAP Notes 91488 and 1172939. Make sure that all functionalities mentioned in these SAP Notes are up-to-date, particularly connections, collectors, and service tools.

5.1 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 01M_ECC600 1 01N_700ECC 0

ST-PI 2008_1_700 3 2008_1_700 4

Recommendation:

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

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

Overall Status SAP Note Title Tool Status Manual Status

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

539977 [Note 539977] ST-PI Support Packages

69455 [Note 69455] Proc. after addon impl.

69455 [Note 69455] Switch on digital content verifi

539977 [Note 539977] Addon ST-PI 2008_1_700

12103 [Note 12103] Collectors and TCOLL

Recommendation:

[Note 69455] Addon ST-A/PI 01N_700ECC "Servicetools for Applications Plug-In" for ERP 2005 / ECC 6.0x From http://service.sap.com/supporttools->ST-A/PI download the installation ST-A/PI 01N_700ECC.

Service Preparation of TT5


Upload to tx SAINT and install as per note 69455. Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'. [Note 539977] ST-PI Support Packages Addon supportpackage level 4 for ST-PI 2008_1_700 for 7.00 [patches up to level 4 for Basis tools for services] Open http://service.sap.com/supporttools-> ST-PI 2008_1_700 ->Supportpk. Add patch SAPKITLRD4 (and predecessors if not yet implemented) to download basket. Release basket via Maintenance optimizer. Upload from frontend into transaction SPAM, define a queue and import the queue.

Hardware Capacity


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

6.1 Overview System TT5 General

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

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

If your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in your SAP system that can impair performance. The paging rating depends on the ratio of paging activity to physical memory.

Server Max. CPU load [%]

Date Rating RAM [MB]

Max. Paging [%

of RAM]

Date Rating Analysis Start

Analysis End

TWDF1847 61 11.06.2011 16382 15 10.06.2011 06.06.2011 12.06.2011

6.2 Paging Out for Windows 2003 Servers The following servers showed high page out rates during the analyzed time frame.

Server OS RAM [MB]

Max. Pages Out / s

Hour Date Rating

TWDF1847 Windows Server 2003 (x86_64) (SP 2)

16382 1186 0 07.06.2011

For the servers listed above, we found at least four successive hours showing a stable page out rate (under 17 pages/s). It is likely, therefore, that Microsoft fixes KB 931308 and KB 938486 have been implemented (SAP Note 1009297). Despite this, we have detected high page out rates.

Recommendation: Consider making a more detailed analysis.

Workload Overview TT5


7 Workload Overview TT5

7.1 Workload By Users The following table lists the number of current users (measured from our workload analysis) in your system.

Users Low Activity Medium Activity High Activity Total Users

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

measured in system 39 1 4 44

7.2 Workload By Task Types This chart displays the main task types and indicates how their workload is distributed in the system. The table below lists the detailed KPIs.

Task Type Response Time in s DB Time in s CPU Time in s

Batch 161481 90909 122089

AutoABAP 42489 2470 1898

RFC 27935 9957 10493

Others 1965 69 69

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



7.3 Workload by Application



7.4 Top Applications This table lists the top applications of the RFC task type.

RFC PROFILE

Initial System Initial Action Total Response Time in s

% of Total Load

Steps

Avg. Resp. Time in ms

Avg. Proc. Time in ms

Avg. CPU Time in ms

Avg. DB Time in ms

TT4 SAPLDSWP_BPM_FUNC 5544 2.4 13232

419 293 172 118

TT4 SM:TMWFLOW_CMSSYSCOL 5504 2.4 172 32001

13668

22205

17446

n_a 4703 2.0 9077

518 511 2 6

TT5 /BDL/TASK_PROCESSOR 2501 1.1 186 13449

3278

772 2141

TT4 EFWK Resource Manager (01 Minute

1795 0.8 2093

858 586 317 249

TT5 /SSF/ULIB 553 0.2 3334

166 35 48 130

TT5 SAP_COLLECTOR_FOR_PERFMONITOR

357 0.2 465 769 533 371 225

TT5 PFCG 344 0.1 2 171981

18804

34141

67128

TT4 BIREQU_DAMCZMI3SCQU7LLUL9DYGJTIG

139 0.1 6 23223

21851

1367

1363

tt5tdc00.wdf.sap_TT5_507562850

84 0.0 5060

17 7 5 8

This table lists the top applications of the Batch task type.

JOBS PROFILE

Report Response Time in s

% of Total Load

Steps CPU Time in s

DB Time in s

Z_SALES_PROCESSING 122793 52.5 714 120743 57409

SAPRSLOG 33321 14.2 8 3642 30745

RSCOLL00 2793 1.2 158 683 1613

/BDL/TASK_SCHEDULER 1836 0.8 1584 39 70

Performance Overview TT5


Report Response Time in s

% of Total Load

Steps CPU Time in s

DB Time in s

RSAL_BATCH_TOOL_DISPATCHING 1834 0.8 162 540 1045

(BATCH) 1532 0.7 60238 690 513

RMCVNEUF 1398 0.6 1 172 1275

RMCVNEUA 1168 0.5 1 115 1082

RMCVNEUL 1137 0.5 1 79 1084

RS_CI_DELETE 714 0.3 8 1 712

8 Performance Overview TT5

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

Rating Check

Performance Evaluation

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

Avg. CPU Time in ms

Avg. Wait Time in ms

Avg. DB Time in ms

Avg. GUI Time in ms

RFC 51961 538 202 1 192 0

HTTP(S) 4 39008 82 34729 2866 0

Dialog 56 772 52 0 574 111

The times measured are compared with reference times to provide a rating. - If the task type is not listed in the "Task Type Overview" table in the "Workload Overview TT5" section, it is not included in the evaluation. - DIALOG, RFC and HTTP(S) are considered to be related to the end user's dialog activity. Performance problems are anticipated for tasks rated YELLOW or RED in the table below.

RATINGS

Task Steps Application Server Performance Database Server Performance

RFC 51961

REFERENCE TIMES

Task Reference for Avg. Response Time (ms) Reference for Avg. DB time (ms)

RFC 2400 1200

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

Trend Analysis for TT5


9 Trend Analysis for TT5

The performance of your system was analyzed with respect to the trend of response times for each system and application. We found some problems that may impair system performance. To ensure adequate performance for your system, take corrective action as soon as possible. For more information, contact SAP Support.

Rating Check Description

History of response time of TT5 The long-term analysis of the response time shows a remarkable trend

Application profile of TT5 The long-term analysis of applications shows a remarkable growth

9.1 History of Response Time of TT5



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

We analyzed the trend within the following time periods: Short Term: From 20/2011 to 23/2011 Long Term: From 23/2010 to 23/2011

Tasktype Long term Growth (%/year) Trend Short term Growth (%/year) Trend

ALL 23,5 9,9-

Dialog 44,2- 2.387,9-

HTTP(S) 30,7- 767,3-

RFC 7,8 407,5

A significant long-term growth of response time: 23.5%/year was found during the analyzed time frame but this improved over the past four weeks: the short-term decrease is 9.9%/year.

9.2 Application profile The table below shows the time profile of the top 5 applications.

TIME PROFILE OF TOP 5 APPLICATIONS

Week SESSION_MANAGER SCI SNOTE SE38 SPAM

24/2010 4941 0 0 0 0

25/2010 14485 0 0 0 8529

26/2010 2268 0 1015 1136 1943

27/2010 1335 0 2861 1422 0

28/2010 1404 0 2689 628 0

29/2010 743 0 467 2133 0

30/2010 2638 0 1474 951 0

31/2010 1344 0 2112 2327 0

32/2010 3109 0 0 0 0

33/2010 1460 0 3403 509 0

34/2010 3096 0 0 1524 0

35/2010 514 0 1020 0 0

36/2010 1529 0 6046 15496 0

37/2010 1096 513884 4462 500 0

38/2010 3374 0 1425 374 14990

39/2010 2598 0 771 235 0

40/2010 1764 0 396 1246 0

41/2010 3512 0 0 565 0



Week SESSION_MANAGER SCI SNOTE SE38 SPAM

42/2010 8508 0 0 543 0

43/2010 2506 0 0 2149 0

44/2010 3260 0 10015 772 0

45/2010 4123 0 0 1750 0

46/2010 29302 0 3315 720 39400

47/2010 80603 0 2016 2303 0

48/2010 1977 0 0 972 0

49/2010 1395 0 5968 4133 0

50/2010 23530 0 0 1320 0

51/2010 3727 0 0 0 0

52/2010 0 0 0 0 0

53/2010 0 0 0 0 0

02/2011 13979 0 0 0 0

03/2011 0 0 0 0 0

04/2011 0 0 0 0 0

05/2011 987 0 1952 0 0

06/2011 357 0 0 0 0

07/2011 3818 0 0 2011 0

08/2011 2323 0 38104 985 0

09/2011 571 0 0 179 0

10/2011 3675 0 0 0 0

11/2011 16959 0 0 3811 0

12/2011 0 0 0 0 0

13/2011 1928 0 511 996 0

14/2011 4679 0 0 2501 0

15/2011 12496 0 2075 0 0

16/2011 0 0 0 0 0

17/2011 12319 0 0 1009 0

18/2011 1394 0 0 0 0

19/2011 3227 0 0 0 0

20/2011 2225 0 8361 470 0

21/2011 4736 0 0 2077 0

22/2011 943 0 0 0 0

23/2011 734 0 0 1472 0

The graph below shows how the average response time of the top 5 applications varies over time. The data has been normalized to 100% to equal the average value.



The table below lists the applications that have been analyzed in detail.

ANALYZED APPLICATIONS

Tasktype Application Resp. time in s

Avg. Resp. time in ms

Long term Growth(%/year)

Trend Short term Growth (%/year)

Trend

Dialog SPAM 2686 18913 711,3 711,3

Dialog SE80 162 904 238,0 238,0

9.2.1 Time Profile of SE80 The graph below shows the time profile of SE80.

A significant long-term growth in average response time: 238.0%/year was found within the application SE80 and the short-term growth during the past four weeks is 238.0%/year. Close monitoring and analysis are required.

9.2.2 Time Profile of SPAM The graph below shows the time profile of SPAM.



A significant long-term growth in average response time: 711.3%/year was found within the application SPAM and the short-term growth during the past four weeks is 711.3%/year. Close monitoring and analysis are required.

SAP System Operating TT5


10 SAP System Operating TT5

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

Rating Check

Availability based on Collector Protocols

Program Errors (ABAP Dumps)

Update Errors

Table Reorganization

10.1 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.2 Program Errors (ABAP Dumps) 59 ABAP dumps have been recorded in your system in the period 06.06.2011 to 13.06.2011. 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

06.06.2011 9

07.06.2011 8

08.06.2011 6

09.06.2011 6

10.06.2011 13

11.06.2011 11

12.06.2011 7

13.06.2011 1

Name of Runtime Error Occurences

Server (e.g.) User (e.g.) Date (e.g.) Time (e.g.)

CALL_FUNCTION_SINGLE_LOGIN_REJ

11 tt5tdc00_TT5_50

SAPSYS 10.06.2011

13:31:18

RFC_NO_AUTHORITY 2 tt5tdc00_TT5_50

TEGI_CDMC_U

11.06.2011

09:05:23

TABLE_INVALID_INDEX 2 tt5tdc00_TT5_50

MASTER 11.06.2011

09:06:48

INVALID_PRI_PARAMS 2 tt5tdc00_TT5_50

BURMANM 12.06.2011

06:00:06

CALL_FUNCTION_NOT_FOUND 42 tt5tdc00_TT5_50

THORNW 12.06.2011

23:00:11

Security


11 Security

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

Rating Check

SAP Security Notes: ABAP and Kernel Software Corrections

Default Passwords of Standard Users

Password Policy

Gateway and Message Server Security

Users with Critical Authorizations

11.1 SAP Security Notes: ABAP and Kernel Software Corrections Software corrections from SAP Security HotNews are missing on this system. Your system is probably exposed to security threats.

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

A complete list of SAP Security Notes, including Security HotNews, is available on the SAP Service Marketplace at https://service.sap.com/securitynotes. The tool RSECNOTE in transaction ST13 lists the SAP Security Notes missing in this EWA check. RSECNOTE covers SAP Security HotNews with software-related corrections for ABAP or Kernel, and an additional selection of SAP Security Notes. For more information, refer to SAP Note 888889. In the Security Notes list on the SAP Service Marketplace referenced above, the flag Automatic check in EWA (last column) identifies those SAP Security Notes for which the implementation is completely checked in the EWA.

11.2 Default Passwords of Standard Users Standard users have default passwords.

Recommendation: Use report RSUSR003 to check the default passwords of standard users.

Ensure that users SAPCPIC and EARLYWATCH have non-default passwords in all clients.

For more information, see section "Protecting Standard Users" either in the SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide. Make sure that the standard password for user TMSADM is changed in client 000 and delete this user in

any other client. The SAP Note 1414256 describes a support tool for changing the password of user TMSADM in all systems of the transport domain.

11.3 Password Policy If password login is allowed in specific instances only, the password policy is checked only for these instances.

Security


11.3.1 Password Complexity PARAMETER: LOGIN/MIN_PASSWORD_LNG

Rating Instance Current Value Recommended Value

tt5tdc00_TT5_50 6 8

The current system settings allow a minimum password length of less than 8 characters. This allows weak passwords. Attackers may successfully decode such passwords and gain unauthorized access to the system.

Recommendation: Use a minimum value of 8 for the profile parameter login/min_password_lng.

SAP provides options to enforce complex passwords. The current settings of the corresponding profile parameters are in the following table.

Parameter Instance Current Value

login/min_password_digits tt5tdc00_TT5_50 0

login/min_password_letters tt5tdc00_TT5_50 0

login/min_password_lowercase tt5tdc00_TT5_50 0

login/min_password_uppercase tt5tdc00_TT5_50 0

login/min_password_specials tt5tdc00_TT5_50 0

Recommendation: Enforce a minimum of 3 independent character categories using the corresponding

profile parameters. More information can be found in SAP Note 862989 and in section Profile Parameters for Logon and Password (Login Parameters) either in the SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

11.3.2 Validity of Initial Passwords

Rating Parameter Instance Current Value

login/password_max_idle_initial tt5tdc00_TT5_50 0

Initial passwords are valid for an unrestricted period.

Recommendation: Restrict the password validity to 14 days or less. More information can be found in

SAP Note 862989 and in section Profile Parameters for Logon and Password (Login Parameters) either in the SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

11.4 Gateway and Message Server Security

11.4.1 Kernel Patch Level

Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level

700 146 260

a minimum patch level of the kernel is required to enable certain Gateway security functionality. Your system does not satisfy this requirement.

Recommendation: Update the kernel of your system to the newest patch level available, or at least to a

kernel patch level equal to or higher than the minimum required level given above. Additional information is in SAP Note 1298433.

11.4.2 Gateway Security

Gateway Security Properties

The parameter gw/reg_no_conn_info controls the activation of certain security properties of the SAP Gateway. It is a bit mask with one bit per property. On your system, the following properties were identified:

Security


PARAMETER: GW/REG_NO_CONN_INFO

Rating Instance Value Name Current Value

Recommended Value

tt5tdc00_TT5_50 Bypassing security in reg_info & sec_info 0 1

tt5tdc00_TT5_50 Bypassing sec_info without reg_info 0 2

tt5tdc00_TT5_50 Uppercase/lowercase in the files reg_info and sec_info

0 8

Recommendation: Enable the missing properties by adding the recommended values to the current

value of gw/reg_no_conn_info. More information regarding gw/reg_no_conn_info is in SAP Note 1444282.

11.5 Users with Critical Authorizations For more information about the following check results, please refer to SAP Note 863362.

Recommendation:

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

11.5.1 Users Authorized to Display all Tables Unauthorized access to sensitive data is possible if too many users are granted authorization. The number of users with this authorization is stated for each client.

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

600 232 259

800 4159 4341

801 145 160

802 145 160

803 144 159

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.5.2 Users Authorized to start all Reports This authorization allows critical functions and reports without authorization checks to be executed. The number of users with this authorization is stated for each client.


600 230 259

800 4153 4341

801 143 160

802 143 160

803 142 159


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

Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*

Security


11.5.3 Users Authorized to Debug / Replace This authorization provides access to data and functions since ABAP authorization checks are bypassed. You can also change data during processing, which may lead to inconsistent results. The number of users with this authorization is stated for each client.


600 221 259

800 2621 4341

801 141 160

802 141 160

803 140 159


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 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 are still possible. You can do this by linking two authorizations to object S_DEVELOP: One with all object types (except "DEBUG") and all activities and another for object type DEBUG only with all activities (except 02).

11.5.4 Users Authorized to Display Other Users Spool Request This authorization allows unauthorized access to sensitive data contained in spool requests. The number of users with this authorization is stated for each client.


600 229 259

800 4096 4341

801 141 160

802 141 160

803 140 159


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.5.5 Users Authorized to Administer RFC Connections If too many users have this authorization, two issues may arise: - Unauthorized access to other systems - Interfaces malfunction when invalid connection data is entered The number of users with this authorization is stated for each client.


600 220 259

800 2061 4341

801 142 160

802 142 160

803 141 159


Security


Object 1: S_TCODE with TCD=SM59

Object 2: S_ADMI_FCD with S_ADMI_FCD = NADM

11.5.6 Users Authorized to Reset/Change User Passwords The following users are authorized to change and reset the passwords of all users. This is very risky because these users could change the password of users and log on as these users themselves. The only consequence would be that the real user would no longer be able to log on because the password was changed. In this case, however, the password is normally reset because it may be that the real user has forgotten his or her password.


600 222 259

800 3901 4341

801 141 160

802 141 160

803 140 159


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

Software Change Management TT5


12 Software Change Management TT5

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

12.1 SAP Netweaver Application Server ABAP


Number of Changes

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 SAP Solution Manager Change Diagnostics application. 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 Software Maintenance Parameter Transport Requests SAP Notes Miscellaneous

06.06.2011 0 0 0 0 0

07.06.2011 0 0 0 0 0

08.06.2011 0 0 0 0 0

09.06.2011 0 0 0 0 0

10.06.2011 0 0 0 0 0

11.06.2011 0 12 0 0 0

12.06.2011 0 0 0 0 0



12.2 SAP Netweaver Application Server JAVA


Number of Changes

Enhanced Change and Transport System (CTS+)

12.2.1 Number of Changes No data could be extracted because Solution Manager Diagnostics is not configured or the managed system is not connected. Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services. Set up Solution Manager Diagnostics and connect the managed systems. For more information, see SAP Service Marketplace http://service.sap.com/diagnostics -> Installation and Configuration

12.2.2 Enhanced Change and Transport System (CTS+) We could not determine whether CTS+ is used. Either it is not used or information about its use is not available in SAP Solution Manager. If CTS+ is not used, you must configure it. For more information about setup, see SAP Service Marketplace http://service.sap.com/changecontrol. If CTS+ is used but this information is not available, you must connect the CTS+ communication system to SAP Solution Manager. Run the Solution Manager Setup Wizard for the CTS+ communication system and maintain at least the RFC READ connection. The information will be available in SAP Solution Manager after the landscape data is next updated. You must also set up reporting for CTS+ transports as described in SAP Note 1385527.



12.3 System Activity Overview The following table, "System Activity Overview - Weekly", provides information about the system for the week indicated by the "Date Collected" column. The data provided is for information purposes only.

SYSTEM ACTIVITY OVERVIEW - WEEKLY

Parameter Start Date Finish Date

Weekly Data Description

Reads 06.06.2011 13.06.2011 16689555 no. of disk reads by MS SQL Server

Writes 06.06.2011 13.06.2011 9057008 no. of disk writes by SQL Server

CPU busy 06.06.2011 13.06.2011 215706 CPU busy time in seconds

CPU idle 06.06.2011 13.06.2011 1977298 CPU idle time in seconds

I/O busy 06.06.2011 13.06.2011 5771 I/O busy time in seconds

SQL Batches 06.06.2011 13.06.2011 72359161 no. of Transact SQL Command Batches received by SQL Server

Requested Buffer Pages

06.06.2011 13.06.2011 39533674811 no. of requests for data cache pages

Page Reads 06.06.2011 13.06.2011 25388933 no. of physical page reads to data cache

Page Writes 06.06.2011 13.06.2011 48125791 no. of physical page writes from data cache to disk

Read Aheads 06.06.2011 13.06.2011 20096473 no. of requests asynchronously prefetched from disk

User Connections 06.06.2011 13.06.2011 0 average no. of User Connections

See Description 06.06.2011 13.06.2011 99.94 ratio of physical page reads to total page requests in percent

See Description 06.06.2011 13.06.2011 99.88 as above including readaheads

The "System Activity Overview - Peak" table is an indicator of the system's highest level of activity. The data sampled is from the same week as the data evaluated in the table above (refer to table "System Activity Overview - Weekly"). The date and time at which the peak activity was recorded is a two-hour window indicated by the "Date/Time collected" column. The data provided is for information purposes only.

SYSTEM ACTIVITY OVERVIEW - PEAK

Parameter Date Collected

Time Collected

Peak Data Description

Reads 07.06.2011 00:10:00 2687821 peak no. of disk reads by SQL Server

Writes 13.06.2011 00:09:56 1128308 peak no. of disk writes by SQL Server

CPU busy 11.06.2011 18:10:03 20217 peak CPU busy time in milliseconds

CPU idle 08.06.2011 18:09:51 27862 peak CPU idle time in milliseconds

I/O busy 10.06.2011 00:09:50 200 peak IO busy time in milliseconds

SQL Batches 10.06.2011 00:09:50 2501973 peak no. of Transact SQL Command Batches received by SQL Server

Requested Buffer Pages

11.06.2011 18:10:03 7149575717 peak no. of requests for data cache pages

Page Reads 10.06.2011 00:09:50 9866039 peak no. of physical page reads to data cache

Page Writes 13.06.2011 00:09:56 7390689 peak no. of physical page writes from data cache to disk

Read Aheads 10.06.2011 00:09:50 9411655 peak no. of requests asynchronously prefetched from disk

12.4 Wait Statistics The analysis of the wait statistics did not reveal any problems. The wait times for wait types PAGEIOLATCH_SH and WRITELOG are shown for information only.

Wait type Wait time (ms) Requests Wait time / Requests Reference Value Rating

Total 607.635.070 68.765.352 8,84

PAGEIOLATCH_SH 13.043.140 1.901.523 6,86 15,00



Wait type Wait time (ms) Requests Wait time / Requests Reference Value Rating

WRITELOG 1.354.312 588.640 2,30 6,00

12.5 IO Performance The following tables show how I/O operations are distributed over the data files and log files respectively. Additionally, the average wait time per I/O operation is shown below for each file. Note that high read times are not always an accurate indication of performance issues, therefore we recommend that you review SAP Note 987961 for information on the interpretation of the various I/O statistics available with SQL Server 2005. ,, With respect to the data files, the I/O activity must be evenly distributed among the files. Usually, only one log file is in use at any given time.

File Reads % of Reads

Writes % of Writes

IOStallWrite [ms] / write request

IOStallRead [ms] / read request

Rating

ID3DATA1 140083 9.32 3723 9.40 2.39 40.21

ID3DATA2 135024 8.98 3002 7.58 3.06 43.00

ID3DATA3 133945 8.91 3260 8.23 2.72 43.27

ID3DATA4 145918 9.71 3725 9.40 2.78 45.62

ID3DATA5 122605 8.16 3201 8.08 2.78 47.21

ID3DATA6 116618 7.76 2776 7.01 2.76 50.15

ID3DATA7 113561 7.55 2870 7.25 3.19 52.45

ID3DATA8 108892 7.24 2939 7.42 2.91 54.37

ID3DATA9 113247 7.53 3072 7.76 2.53 55.66

ID3DATA10 124160 8.26 3919 9.89 2.81 57.40

ID3DATA11 124750 8.30 3424 8.64 2.70 63.38

ID3DATA12 124354 8.27 3701 9.34 2.64 67.81

Total 1503157 100 39612 100 2.76 51.34

File Reads Writes IOStallWrite [ms] / write request IOStallRead [ms] / read request

ID3LOG1 35 59224 2.27 21.94

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

Name of missing database index

MEMGMT_DEPLOYMNT~0

The above indexes have been defined in the ABAP Dictionary but do not exist in the database.

Recommendation: If a primary index is missing, check whether there are double records for the primary

index in the corresponding table, and eliminate these (if necessary, in cooperation with SAP Support by opening a customer message on SAP Service Market Place). Next, recreate the missing primary indexes in your database immediately. The same procedure applies for a missing secondary index, unless it was dropped intentionally (in rare cases this may be recommended by SAP Support for performance reasons).

Implementation: Use the ABAP Dictionary (transactions SE11 and SE14).

Note: If an index was deleted intentionally, it can be registered in the DB02 consistency check algorithm

so that the index is no longer listed in this check (refer to SAP Note 33814).



13 Database Administration

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

Rating Check

Largest Tables

Top Growing Tables

Service Pack Check

Tables With Page Locking Disabled

Database Options

Database Interface Library Version

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

13.1.1 Database Free Space With SQL Server, the database files can be expanded dynamically on the disks where they are located. If files run full and no freespace is left on disk, an error occurs and you risk system downtime. Therefore, we recommend that you pay close attention to the potential growth of the database. If you have database files located on several disks and you have to enlarge files, you should spread database free space evenly across all disks. SQL Server can then spread I/O load on all available disks. The free space within your database files is currently below 10% of the database space used. Ensure that you manually expand your database files before free space is exhausted.

Note: We recommend using the 'Automatic growth' mechanism for the database files in exceptional cases

only. The automatic growth mechanism will expand the data files most likely at a time of heavy system usage. While the file is expanded, database access is strongly impaired. Therefore, you should only expand the files manually during periods of low system activity.

13.1.2 Largest Tables The following table shows the largest tables currently in the TT5 database.

Table Name Data (kB)

Reserved (data + indexes) kB

Used (data + indexes) kB

Rows Modified Rows

D010TAB 7421312 14861584 14847600 56983940 9027187

D010INC 3159968 6477880 6444032 18161705 2932538

DD03L 1752584 6417656 6321272 5518828 192256

AGR_HIERT 4913056 4981400 4980440 38888932 2622720

MC13VD0KONSETUP 4372136 4425000 4422896 5212886 153251

GLFUNCA 2456496 4060656 4057112 5053221 4155

DOKCLU 3332560 3376688 3376096 4545559 129753

MC13VD0ITMSETUP 3306840 3347624 3345352 5212717 154920

BALDAT 3079448 3151424 3144752 5034747 493849

PCL2 3063848 3086304 3086264 798780 6



13.1.3 Top Growing Tables

Table Name Data (kB) Delta Data Size (kB)

Indexes (kB)

Delta Index Size (kB)

Delta Reserved Size (kB)

Delta Rows

MC13VD0KONSETUP 3048040 25920 33064 344 26304 30925

MC13VD0ITMSETUP 2304448 19616 25120 256 19904 30924

BALDAT 2074608 16288 42176 360 16640 31178

DYNPLOAD 1363104 1232 3016 0 1472 3-

REPOTEXT 3260048 576 8160 8 904 0

CATM 2355152 392 18552 8 456 815

CATN 2290768 256 23456 8 264 863

GLFUNCA 2456240 144 1600400 96 392 300

REPOSRC 6709480 128 23168 8 520 0

REPOLOAD 17018408 24 26320 0 960 0

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

13.1.4 Service Pack Microsoft releases updated SQL Server builds, known as Service Packs, at regular intervals. For certain problems or bugs in SQL, Server Hotfixes are made available immediately. In certain situations it is also recommended to apply a certain Hotfix for a SAP system.

Build in use Builds Comment

2047 9.00.2047 SQL SERVER 2005 Service Pack 1

9.00.3042 SQL SERVER 2005 Service Pack 2

9.00.3228 SQL SERVER 2005 Service Pack 2 Cumulative Update 6

9.00.4035 SQL SERVER 2005 Service Pack 3

Recommendation: To ensure optimal performance and data security for your database system, upgrade

your database server to the latest available build listed above. For information about database releases and builds currently supported by SAP, refer to SAP Note 62988.

Implementation: Install the same service pack for the SQL Server client utilities on all application servers.

Note: The service packs are available on the CDs shipped by SAP or from Microsoft. Preliminary

corrections will also be available on the SAP Service Marketplace at: http://service.sap.com/swcenter-3pmain For more information on obtaining the latest service pack, refer to SAP Note 62988.

13.1.5 Tables With Page Locking Disabled

Table Page locking Rating

VBMOD Page locking disallowed

VBHDR Page locking disallowed

ARFCSDATA Page locking disallowed

VBDATA Page locking disallowed

ARFCRDATA Page locking disallowed

EDI40 All lock levels allowed

EDIDC All lock levels allowed

EDIDS All lock levels allowed As shown above, page locking must be disallowed for some tables.

Recommendation: Disallow page locking for tables VBHDR, VBMOD, VBDATA, ARFCSDATA,

ARFCRDATA, and TRFCQUEUE (if it exists).

Implementation: You can do so using the SQL command: EXEC sp_indexoption ,

"DisAllowPageLocks", "TRUE"



Background: For some tables, disallowing page locks improves the concurrency of accesses from different users

to these tables, therefore avoiding deadlocks.

13.1.6 Compatibility Level

SQL Server Release Compatibility Level

9.00.2047.00 90

The following compatibility level has been set in your SQL Server database TT5 (the compatibility level is set according to SAP recommendations):

Remote Function Call for TT5


14 Remote Function Call for TT5

Remote Function Call issues which require your attention have been found. See the recommendation in the following section.

Rating Check

RFC wait time profile for Instance &YSAP-INS_NAME&

14.1 qRFC Administration

14.1.1 qRFC Queues

14.1.1.1 qRFC Outbound Queues

qRFC outbound queues in error status

qRFC outbound queues with error statuses were detected in the qRFC Monitor. The table below lists the queues with the highest number of entries for each error status found.

Recommendation: Analyze the errors according to SAP Note 378903. Monitor the qRFC outbound

queues daily using transaction SMQ1.

Queue Name Status Date of first entry Entries Error Message

SALES_0 SYSFAIL 18.10.2006 2545 Hello World Please Try Again ;-)


















Java Performance and Workload for TT5


15 Java Performance and Workload for TT5

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 "Availability of Java Performance Data". 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.

Rating Check

Availability of Java Performance Data

Java VM Activity Reporting

Java Application Performance

15.1 Availability of Java Performance Data

Some of the Java performance and workload data is missing.

Some of the Java performance and workload data from your system was not available automatically for this service session. We could not, therefore, check the performance and workload of your system fully. The managed system configuration with diagnostics in SAP Solution Manager is required to retrieve performance and workload data from a Java-based SAP system.

Recommendation:

Ensure that performance and workload data is displayed for your system in the "Workload Analysis" application of solution manager diagnostics. If the data is missing, open a customer message on component SV-SMG-DIA. If data is displayed in the "Workload Analysis" application but is missing in the service session and report, open a customer message on component SV-SMG-SER. SAP Note 1332428 provides troubleshooting information for the event that data for a Java-based system is missing in a service session of SAP Solution Manager.

Implementation:

Choose "End-to-End Analysis" in the "Root Cause Analysis" work center of SAP Solution Manager. Select your system and open the "Workload Analysis" application. Prerequisites for the "Workload Analysis" application in solution manager diagnostics: - Solution manager diagnostics must be set up, including CCDB, BW, and integrated Wily Introscope in SAP Solution Manager 7.0. - The managed system configuration must have been executed successfully for this system as described in SAP Note 1265070. - SMD agents must be running in your system. - Periodic extractors must be running successfully in your system.

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

15.2 Java VM Activity Reporting This chapter displays the distribution of activity per server node. If multiple instances are configured, the values give an overview of the balanced load provided that all nodes were running during the reporting interval.

15.2.1 HTTP Sessions The diagram displays the average and maximum hourly distribution of HTTP sessions.



15.2.2 Logins per hour The diagram displays the average and maximum hourly distribution of UME logins.

15.2.3 HTTP Requests

The distribution of http requests among different server nodes is normal.

The table below shows the weekly average and maximum HTTP requests per server node. If the values differ significantly for different server nodes, the load distribution may be unbalanced or different server nodes may be configured differently.

Host name Instance name Node name Average Max

TT5TDC00 DVEBMGS50 SERVER0 29.87 40

15.2.4 Active Threads

The number of active application threads is not critical.

The table below shows the weekly average and maximum values of active application threads per server node. A significant difference between the values for different server nodes may be caused by unbalanced load distribution or different server nodes being configured differently.



Host name Instance name Node name Average Max Configured

TT5TDC00 DVEBMGS50 SERVER0 8.43 10 40

15.3 Java Application Performance Java application performance can be assessed based on two methods: The average response time of these applications is displayed as well as the accumulated time. The latter is better suited to assess the overall effects on performance , since it takes into account how often an application was actually called.

15.3.1 Top Servlets The following top list is sorted by the accumulated response time during the reporting interval. This is useful for determining which application placed the greatest load on the J2EE, as this is influenced by both the average response time and the number of times that the application is created at runtime.

Rank Name Accumulated time [s]

Executions Average response time[ms]

1 COM.SAP.LCR.CIMSRV.CIMOMSERVLET 17 1158 14

2 COM.SAP.LCR.SAGENT.DATASUPPLIERSERVLET 2 3 640

Recommendation:

Servlet/JSP requests with a high accumulated time value may have a greater overall impact on performance that may be worth investigating further.

15.3.2 Top JCO Calls The following top list is sorted by the accumulated response time during the reporting interval.

Rank Name Accumulated time [s]

Executions Average response time[ms]

1 JCO-TT5-800@TT5TDC00|JCO|PRGN_J2EE_GET_ROLES 32 75 428

2 JCO-TT5-800@TT5TDC00|JCO|BAPI_USER_GET_DETAIL 19 169 111

3 JCO-TT5-800@TT5TDC00|JCO|SUSR_CHECK_LOGON_DATA

8 671 12

4 JCO-TT5-800@TT5TDC00|JCO|PRGN_J2EE_USER_GET_ROLENA MES

4 709 6

5 JCO-TT5-800@TT5TDC00|JCO|BAPI_USER_EXISTENCE_CHECK

1 55 15

6 JCO-TT5-800@TT5TDC00|JCO|SUSR_GET_ADMIN_USER_LOGIN _INFO

0 167 2

Recommendation:

Investigate the potential overall performance impact of JCo calls with large accumulated time values.

15.3.3 Top SQL Selects The following top list is sorted by the accumulated response time during the reporting interval.

Rank Name Accumulated Time [s]

Executions Average[ms]

1 SELECT "CONTENTID", "MODIFYCOUNTER", "INTCONTENTLENGTH", "INTCREATIONDATE", "INTLASTMODIFIED" FROM "KMC_DBRM_NODES" WHER

49 162756 0

2 SELECT * FROM "CAF_GP_SCHED_QUEUE" WHERE "NEXTEXEC" < ? AND "STATUS" = ? ORDER BY ?

47 27902 2

3 SELECT * FROM "CAF_GP_CODUE" WHERE "DUE_DATETIME" < ?

44 27893 2



Rank Name Accumulated Time [s]

Executions Average[ms]

4 SELECT "INST_HANDLE", "INSTNAME_BYTES" FROM "BC_SLD_INST" WHERE "APPL" = ? AND "NA_KEY" = ? AND "INST_HASH" = ?

36 21692 2

5 SELECT MIN ("ID"), "PRIORITY" FROM "KMC_TQ_QUEUE" WHERE "NAMESPACE_HASH" = ? AND "NAMESPACE" = ? AND "TASK_STATE" = ? GR

29 47453 1

6 SELECT COUNT (*) FROM "BC_SLD_INST" WHERE "APPL" = ? AND "NA_KEY" = ? AND "INST_HASH" = ?

28 21727 1

7 SELECT COUNT (*) FROM "BC_SLD_NAMESP" WHERE "APPL" = ? AND "NA_HASH" = ?

27 21621 1

8 SELECT "NAME", "CHANGE" FROM "KMC_CMCC_TABLE" WHERE "CHANGE" > ?

23 13951 2

9 SELECT "FBLOB" FROM "J2EE_CONFIGENTRY" WHERE "CID" = ? AND "NAMEHASH" = ? AND "NAME" = ? AND "ISFILE" = ?

21 4014 5

Recommendation:

Investigate the potential overall performance impact of SQL statements with large accumulated time values.

Trend Analysis


16 Trend Analysis

This section contains the trend analysis for key performance indicators (KPIs). Diagrams are built week by week once the EarlyWatch Alert service is activated. In this report, historical data for "Transaction Activity", "System Performance", and "Database Performance" is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions. In this section, "weeks" are from Monday to Sunday. The date displayed is Sunday at the end of the week.

16.1 System Activity The following diagrams show the system activity over time. The "Transaction Activity" diagram below depicts transaction activity in the system over time.

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

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

- Peak Activity: Transaction steps (in thousands) during the peak hour; this peak hour is calculated as

the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week. (Peak Activity is absent if "Activity Data" is taken from ST03 data directly).

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

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

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

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

Trend Analysis


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

Note: The column 'Availability' is filled for systems with SAP Basis 4.6 and higher.

Trend Analysis


16.3 Hardware Capacity

Report timeframe: Service data was collected starting at 13.06.2011 04:02:37. This took 11 minutes.

For more information about EarlyWatch Alert, you can review 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.

SAP EWA

Documents

Transcript of SAP EWA