Earlywatch Report

Service Report

Service CenterTelephoneFax

Date of Session 21.09.2004 <dat_dummy> Session No. 0010001706025Date of Report 21.09.2004 Installation No. 0020064299Author EarlyWatch Alert Service Customer No. 0000366508

<Watermark>

SAP EarlyWatch Alert

SAP System ID PRD

SAP Component R/3

Release 470

Status Productive

DB System ORACLE 9.2.0.4.0

Customer Videsh Sanchar Nigam Limited Lokmanya400 028 Prabhadevi, MumbaiIndia

1 System Status

1 System Status

During this EarlyWatch Alert Session, we detected potential problems concerning your system.We recommend that you take corrective action as soon as possible.If you would like further information, create a customer message on component XX-SER-TCC, or call your SAP Local Support organization.

Note:All recommendations provided in this report are based on our general experience only. We advise you to test our recommendations before using them in your production system. Also note that EarlyWatch Alert is an automatic service.

Service Contents

Overview: Alert MessagesThe following table contains an overview of all alerts.

Rating Performed Check

System Configuration

System Performance

Workload Distribution

SAP System Operating

Hardware Capacity

Database Settings

Database Administration

Database server load from expensive SQL statements

Priority Description New Alert

High At least one ABAP dump of type 'SAPSQL_ARRAY_INSERT_DUPREC' was found. New

Medium Performance problems exist or are expected. New

Medium Update your SAP R/3 Plug-In to the latest release available. New

Note:If you need help investigating the alerts listed, order an EarlyWatch contract by contacting your local support organization, or by creating a customer message on component XX-SER-TCC. If you already have such a contract, a detailed analysis can be performed during the next service session. Please address the topic during the preparation of the session.

Note: If you experience serious performance problems, create a customer message on component XX-SER-TCC with priority 'high' or 'very high'.

2 Performance Indicators

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

Area Indicators Value Trend

System Performance Active Users 162 up

Avg. Response Time in Dialog Task 520 ms steady

Max. Dialog Steps per Hour 16405 up

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004 2

2 Performance Indicators

Area Indicators Value Trend

Avg. Response Time at Peak Dialog Hour 581 ms up

Avg. Availability per Week 99 % steady

Database Performance Avg. DB Request Time in Dialog Task 247 ms up

Avg. DB Request Time in Update Task 79 ms up

Database Space Management DB Size 41.61 GB up

Last Month DB Growth 5.94 GB down

3 System Configuration

To ensure the optimal support of your SAP System, the SAP components, database and operating system used must be supported. Please find detailed information on SAP's platform support on the SAP Service Marketplace, service.sap.com/platforms .

Rating Check

Hardware Configuration

Software Configuration

SAP Service Preparation

3.1 Hardware ConfigurationThe table below shows the detected hardware configuration:

HARDWARE CONFIGURATION

Server Type Server OS OS Version Number of CPUs Memory [MB]

Database Server sap-prd HP-UX 11.11 4 8184

DATABASE SYSTEM

Database Server Database System Current Version

sap-prd ORACLE 9.2.0

3.2 Software ConfigurationThe table below shows the Support Packages applied:

Release Patch Number Status of Patch Patch Type

RA I SAPKITLPRA AOI

470 19 I SAPKH47019 COP

06 I SAPKGPRA06 AOP

470 26 I SAPKE47026 COP

620 37 I SAPKB62037 COP

620 37 I SAPKA62037 COP

PlugIn PlugIn Patch Level

PI 2002_1_470 0003

PI_BASIS 2002_1_620 0006


http://service.sap.com/platforms

3 System Configuration

PlugIn PlugIn Patch Level

ST-A/PI 01E_R3_470 0000

ST-PI 003C_620 0002

Your current SAP R/3 Plug-In is in status customer specific maintenance, which means that SAP will no longer provide Support Packages for this component. Besides the offering of problem resolution for known solutions you will typically be charged based on time and material for resolution of "new" problems. You can also run into problems when you want to integrate new products because they may not be supported with this Plug-In release.

Recommendation: We strongly recommend to upgrade your Plug-In to the latest release available. You can find detailed information on the release strategy and the recommended upgrade path on the SAP Service Marketplace at the Internet address: service.sap.com/R3-Plug-In and its subfolders.

SAP Kernel Release

Your SAP kernel release (release 620, patch level 1613) is not up-to-date.

Recommendation: Ensure that you are using the latest SAP kernel. See SAP Notes 19466 and 138704. (These notes refer to further SAP Notes, depending on your system characteristics.)

In case of SAP kernel release 610 or higher, please refer to Note 502999 as well.

3.3 SAP Service Preparation

SAP Service Tools

Before we can deliver any services, the latest version of the SAP Service Tools must be available in your system.

For detailed information about the required steps see SAP Note 91488 (SAP Support Services: Central preparation note).

During the checks, no missing transports were detected. All tools are up to date. The last activation of report RTCCTOOL was 21.09.2004.

4 Performance Overview

The performance of your system was analyzed with respect to average response times and total workload. We have detected some problems that may impair system performance.

To ensure adequate performance in your core business transactions, you should take corrective action as soon as possible. For further information, please contact the TCC Team.

Rating Check

Performance Evaluation

Comparison of Response Time

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

Task typeDialog Steps

Avg. Resp. Time in ms

Avg. CPU Time in ms

Avg. Wait Time in ms

Avg. Load Time in ms

Avg. DB Time in ms

Avg. GUI Time in ms

DIALOG 626779 520,1 134,5 15,5 6,5 246,7 102,3

RFC 18577 554,3 112,5 5,4 1,6 95,9

UPDATE 68153 183,0 41,5 63,9 4,9 78,6

UPDATE2 2127 84,9 16,2 10,3 3,7 54,3

BATCH 35890 937,3 75,1 9,0 7,7 590,2


http://service.sap.com/R3-Plug-In


Task typeDialog Steps

Avg. Resp. Time in ms

Avg. CPU Time in ms

Avg. Wait Time in ms

Avg. Load Time in ms

Avg. DB Time in ms

Avg. GUI Time in ms

SPOOL 2657 4696,4 70,4 781,0 2,0 176,5

HTTP 4 4497,3 87,5 491,5 181,5 2439,0

4.1 Current WorkloadThe 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

Measured in System 99 133 29 261

4.2 Performance EvaluationFor the task types DIALOG, UPDATE, and RFC, the measured average response times and the measured average database request times were compared with reference values. (Note: If the number of transaction steps are rather small, for example less than 20,000, an overall rating for this check is not reasonable.)

The table below shows that a performance problem is expected for the task that is rated YELLOW.

Task Dialog Steps Application Server Performance Database Server Performance

Dia 626779

Upd 68153

RFC 18577

Batch 35890

4.3 Comparison of Response TimesThe table lists the 15 transactions with the highest total response time. It also includes the change in performance over the previous six Early Watch Alert reports (providing the report was performed more that one week ago).

If the biggest increase is caused by the database, the transaction is marked as 'DB relevant' in the column 'Comment'.If a transaction was not detected during the last EarlyWatch Alert session, the comment 'New' is displayed.If a transaction's response time has increased by at least 10%, this indicates that the transaction's performance has deteriorated during the last four sessions. This is indicated in the Trend column.

If you are not satisfied with the response time of some of these transactions, order an EarlyWatch contract by creating a customer message on component XX-SER-TCC.

TransactionLoad [%]

Current Avg. Resp. Time [ms]

Previous Avg. Resp. Time [ms]

Trend Comment

ZSALESCOSTREG 11,8 44791 0 New

ZFIARR001 9,7 30828 0 New

Y_DEV_09000010 9,1 24564 0 New

FB01 6,4 100 72 -- DB relevant

SESSION_MANAGER 5,5 704 619 -- DB relevant

ZFIAPR004 3,2 2339 4229 ++ DB relevant

ZFIGLR005 3,1 40576 0 New

F-02 2,9 128 64 -- DB relevant

KSU5 2,9 9404 0 New

ZST 2,2 6458 0 New

FS10N 1,9 161 139 -- DB relevant

FBL5N 1,9 240 0 New



TransactionLoad [%]

Current Avg. Resp. Time [ms]

Previous Avg. Resp. Time [ms]

Trend Comment

PC00_M40_CALC 1,7 18633 12813 -- DB relevant

SAPMS380 1,5 11072 0 New

FK10N 1,4 670 1581 ++

4.4 History of Activity and Average Response TimesThe following tables show the system activity, which is the number of dialog steps and the average response times for the past 20 weeks.

The top table compares the total system activity to the dialog activity in the time window specified. The bottom table shows the average CPU, DB, and wait times as parts of the average response time for dialog tasks in the time window specified.


5 Workload Distribution


The performance of your system was analyzed with respect to workload distribution. We did not detect any major problems that could affect the performance of your SAP System.

Rating Check

Workload by Application Module

DB Load Profile

5.1 Workload by Application ModuleThe following graphics show how each application module contributes to the total system workload. Two workload aspects are shown:- CPU time: total CPU load on all servers in the system landscape.- Database time: total database load generated by the application.The section named 'Customer' contains all programs and transactions starting with Y or Z. The section named 'Others' contains all programs that cannot be assigned to an R/3 standard application module (for example, an Industry Solution or a third party add-on development).

CPU LOAD BY APPLICATION

Module CPU Time in %

FI 50,2

BC 17,0

CO-OM 9,1

FI-GL 7,0

PY 5,2

MM 3,4

Unknown 2,7

CA 2,6

DB LOAD BY APPLICATION

Module DB Time in %

FI 77,4

BC 13,4

Unknown 1,9

FI-GL 1,2

MM 1,2

PY 1,1

CO-OM 1,1

5.2 DB Load ProfileThe following graphics show the system DB load distribution at different times of day, as well as the typical DB load peaks. These statistics are given as a weekly average. The unit is 1 hour, except for the periods between 00:00-06:00 and 21:00-24:00 (these two periods contain an average value per hour). We present the workload by total database access time. By comparing the load profiles for dialog and background activity, you have an overview of the amount of background activity during online working hours.



DB LOAD PROFILE FOR DIALOG, RFC AND BATCH

Start_End Time DB Load (DIA) DB Load (RFC) DB Load (BTC)

00--06 0,00 0,00 0,01

06--07 0,00 0,00 0,01

07--08 0,00 0,00 0,19

08--09 0,00 0,00 0,01

09--10 0,07 0,00 0,00

10--11 1,15 0,00 0,01

11--12 0,88 0,01 0,01

12--13 0,49 0,00 0,01

13--14 0,34 0,00 0,01

14--15 0,49 0,01 0,01

15--16 1,06 0,02 0,01

16--17 1,01 0,01 0,02

17--18 0,82 0,01 0,01

18--19 0,47 0,00 0,01

19--20 0,34 0,01 0,01

20--21 0,03 0,00 0,61

21--24 0,00 0,00 0,01

6 SAP System Operating

Your system was analyzed with respect to daily operation. We detected some problems that may impair system operation and stability. To ensure system stability, you should take corrective action as soon as possible.

Rating Check

System Availability

Update Errors

Table Reorganization

ABAP Dumps

6.1 System AvailabilityThe following graphic or table contains information on system availability. A value of 100% means that the system was available the whole day. 'Available' in the context of this report means that at least one SAP instance was running. If the SAP performance collector was not running properly, the values in the table and graphics may be incorrect. To check the values, call transaction ST03 and choose 'Environment'-> 'Data collector' -> 'Display log'.

SYSTEM AVAILABILITY

Date Availability, %

13.09.2004 100

14.09.2004 100

15.09.2004 100

16.09.2004 100

17.09.2004 88



Date Availability, %

18.09.2004 100

19.09.2004 100

20.09.2004 100

6.2 Update ErrorsUPDATE ERRORS BY DAY

Date Quantity of Errors

06.09.2004 3

13.09.2004 0

14.09.2004 0

15.09.2004 0

16.09.2004 0

17.09.2004 0

18.09.2004 0

19.09.2004 0

20.09.2004 0

We did not detect any problems.

6.3 Table ReorganizationDuring our database analysis, we found large or rapidly growing tables.

Recommendation: Implement the SAP Notes listed below to reduce the size of some of these tables.Background: For more information about data archiving, see the SAP Service Marketplace at the Internet address service.sap.com/data-archiving -> Media Center.

Tables Name Size of Tables or Indexes [MByte] Recommended SAP Note

APQD 2112 36781, 18307

6.4 TransportsThe following graphics contain information about the number of objects which were transported to the SAP system. The three graphics/tables show objects in total, programs and table (content).

TRANSPORTED OBJECTS

DateTotal Number of Transported Objects

SAP ObjectsCustomer Objects

Objects in Support Package

13.09.2004 45 0 45 0

14.09.2004 45 0 45 0

15.09.2004 34 0 34 0

16.09.2004 11 0 11 0

17.09.2004 20 0 20 0

18.09.2004 0 0 0 0

19.09.2004 0 0 0 0

20.09.2004 7 0 7 0

TRANSPORTED PROGRAMS

DateTotal Number of Transported Programs

SAP Programs

Customer Programs

Programs in Support Packages

13.09.2004 17 0 17 0


http://service.sap.com/data-archiving


DateTotal Number of Transported Programs

SAP Programs

Customer Programs

Programs in Support Packages

14.09.2004 16 0 16 0

15.09.2004 11 0 11 0

16.09.2004 4 0 4 0

17.09.2004 6 0 6 0

18.09.2004 0 0 0 0

19.09.2004 0 0 0 0

20.09.2004 2 0 2 0

TRANSPORTED TABLES

Date Total Number of Transported Tables SAP Tables Customer Tables Tables in Support Packages

13.09.2004 1 0 1 0

14.09.2004 0 0 0 0

15.09.2004 0 0 0 0

16.09.2004 0 0 0 0

17.09.2004 0 0 0 0

18.09.2004 0 0 0 0

19.09.2004 0 0 0 0

20.09.2004 0 0 0 0

6.5 Program Errors (ABAP Dumps)In your system, 34 ABAP dumps have been detected since 15.09.2004. To view the ABAP dumps in your system, call transaction ST22 and choose 'Selection'. Then select a time frame.

ABAP DUMPS PER DAY

Date Quantity of Dumps

13.09.2004 0

14.09.2004 0

15.09.2004 23

16.09.2004 12

17.09.2004 9

18.09.2004 3

19.09.2004 0

20.09.2004 8

DETECTED ABAP DUMPS

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

SAPSQL_ARRAY_INSERT_DUPREC 7 sap-prd VHRBIJOY 20040915 122022

LOAD_PROGRAM_NOT_FOUND 2 sap-prd E01189 20040915 124552

LOAD_PROGRAM_LOST 1 sap-prd E19967 20040915 162418

SAPSQL_WHERE_QUOTES 2 sap-prd E13392 20040915 180841

BCD_ZERODIVIDE 7 sap-prd VFISARVANA 20040917 161735

DBIF_RSQL_SQL_ERROR 2 sap-prd VFIPRASHANT 20040917 175808

CONTROL_NOT_FOUND 1 sap-prd E18339 20040920 145113

TIME_OUT 9 sap-prd E02419 20040920 163927

SYSTEM_CORE_DUMPED 2 sap-prd VFISARVANA 20040920 174405

COLLECT_OVERFLOW_TYPE_P 1 sap-prd VFIPRASHANT 20040920 181727



It is important for you to 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.

7 Hardware Capacity

We have checked your SAP System for potential CPU or memory bottlenecks and found that the hardware of your database and application server(s) is adequate for the current workload.

Server Max. CPU load [%] Rating RAM [MB] Max. Paging [% of RAM] Rating

sap-prd 33 8184 6

8 Database Settings

We have detected some problems with the settings of the database. These settings may affect performance.

Rating Check

Missing Indexes

Setup of the Temporary Tablespace

Database Key Performance Indicators

Database Parameters

Order of Redo Log Files

Optimizer Statistics

8.1 Load per userThe following table tries to give an overview of the load caused by the different database users.

Listed for each database user is: their percentage of(a) executed statements(b) the number of block reads from disk (indicative for the I/O load caused by this database user)(c) the number of buffers accessed and(d) the number of records returned as obtained from the shared pool (Oracle view v$sql) at the time of the download.

The first line with the name 'TOTAL' indicates the total number of (a), (b), (c) and (d) for all the user names.

USER NAME EXECUTIONS DISK READS BUFFER GETS ROWS PROCESSED

TOTAL (not a user name!) 11837827 11729829 1121248909 61541966


8 Database Settings

USER NAME EXECUTIONS DISK READS BUFFER GETS ROWS PROCESSED

SYS 16% 1% 1% 4%

SYSTEM 0% 1% 0% 0%

OPS$PRDADM 0% 3% 1% 1%

SAPPRD 83% 95% 98% 96%

8.2 Database ParametersWe noticed that the following database parameters, which are currently active in your system, do not follow our standard recommendations. These standard recommendations cannot take into account possible special aspects for your system. Deviations from those standard recommendations may be necessary in your case. We therefore advise you to discuss theses parameter settings in your next Service session.

NOTE FOR CURRENT ORACLE PARAMETER SETTINGS

Note number Description

0124361 Oracle database parameter setting for R/3 4.x

0132503 Update of threshold values of database system check

0170989 Views perform poorly (Oracle 8044 & 805* & 806)

Parameters Description Current value Recommended value

_optim_peek_user_binds Bind value picking Please check SAP note 0124361

To provide special functionality or control system behavior, Oracle has a number of events. These can be activated in the configuration file and/or dynamically in the server manager or sqlplus.

In general, these events and parameters should only be activated on request. When they are no longer needed, they should be removed. However, there might be the need to activate some events during normal database operation.

The following table displays the values for the parameter "event" as found in your system:

Parameter Current Value

event 10183 trace name context forever, level 1

The following table lists events that may have to be activated. Please check the mentioned SAP Notes for details.

Event Note number for Event Description

10191 128221 Increased memory consumption with Oracle 8

8.3 Order of Redo Log FilesUsing the Oracle views v$log and v$logfiles, we found the name and the order of the redo log files as listed in the following table. Please note that the files are ordered by the "sequence number" as found in v$log. This is because the sequence number indicates the actual order in which the redo log files are used and NOT the group number.

GROUP# SEQUENCE# File Name

3 5532 1

3 5532 1

4 5533 1

4 5533 1

2 5534 1

2 5534 1

1 5535 1

1 5535 1


8 Database Settings

To avoid contention, it is recommended to locate the redo log files on different disks such that two successive redo log files are NOT located on the same disk. In this way, there is no competition between the "write" requests of the logwriter and the "read" requests of the archive process.

While we cannot check the exact disk layout, the names of the redo log files indicate that successive redo log files are located on the same file.

Recommendation: Please check the order of the redo log files. If you find that they do not match our recommendations and you want to change the order of the redo log files, you can do this without stopping the database, simply by adding new redo log files (which have to be created in the right sequence) and dropping those redo log files which were NOT in the right sequence. Note that a newly created redo log file will be the next to be used after the next logswitch.Furthermore, you can drop redo log files if they have the status "inactive" (as seen in v$log).

9 Database Administration

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

Rating Check

Database Growth

Backup Frequency

Archive Frequency

Freespace in Tablespaces

brconnect -f next (sapdba -next) schedule

brconnect -f check (sapdba -check) schedule

Problems with SAP Tools

9.1 Database GrowthThe following figure shows the development of the size of your database in GB.

DATABASE SIZE

Date DB Size used

30.04.2004 23,45

31.05.2004 23,55

30.06.2004 26,07

31.07.2004 33,38

31.08.2004 39,32

21.09.2004 41,61

An overview of the freespace development of your database in GB is shown here.

DATABASE FREE SPACE

Date DB Size free

30.04.2004 17,15

31.05.2004 17,05

30.06.2004 14,53


9 Database Administration

Date DB Size free

31.07.2004 11,57

31.08.2004 9,38

21.09.2004 11,39

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

Date Current Size in GB Monthly Growth in GB

31.05.2004 23,55 0,10

30.06.2004 26,07 2,52

31.07.2004 33,38 7,31

31.08.2004 39,32 5,94

21.09.2004 41,61

9.2 Freespace in TablespacesWe checked your system for tablespaces that may overflow in the near future. We considered the following three cases:

Tablespaces - Autoextend ON

Tablespace Size (KB) Free (KB) Avg. Chg/Week (KB) %-Used AutoExt %-Used after AutoExt

PSAPPRD 31432696 2026304 1529063 93 133,120,000 22

PSAPPRD620 22528000 8801664 29055 60 112,640,000 12

PSAPPRDUSR 20480 17152 34 16 10,240,000 0

You have set the 'autoextend' option to 'unlimited' or to 'limited' for some datafiles. Therefore, we cannot check if the related tablespaces can allocate enough freespace for growing database objects.

Recommendation: Please ensure that there is enough freespace on the disks to allow for the growth of the data files of the tablespaces listed in the table above.

9.3 Oracle release upgradeRecommendation: Upgrade your release 9.2 of Oracle to the latestavailable patch set for your version

Refer also to the following SAP Notes:

610445 Merge fix for Oracle 9.2.0.3695080 Merge fix for Oracle 9.2.0.4

10 Database server load from expensive SQL statements


10 Database server load from expensive SQL statements

Expensive SQL StatementsDATABASE LOAD CAUSED BY EXPENSIVE STATEMENTS

CPU & memory load [%] I/O load [%] DB startup date DB analysis date Comment

74.4 -> 83.4 73.3 -> 82.4 17.09.2004 21.09.2004

The following table lists the objects that have the highest load due to expensive SQL statements. The load of the statement is evaluated against the current load on the database and the total load since startup. If the statement was first executed at a point in time close to the database startup or a point in time close to the analysis; the lower or the higher value will be more appropriate. A more technical explanation can be found in SAP Note 551646. The database administrator should conduct a detailed analysis, or you may prefer to order one of the remote or onsite optimization services from the SAP Marketplace at service.sap.com/smo.

EXPENSIVE STATEMENTS

Object nameCPU & memory load [%]

I/O Load [%] ExecutionsRecords processed

First load date/time

M_KREDA 20.7 -> 23.2 negligible 2 102004-09-17/16:08:05

RFBLG 18.7 -> 20.9 negligible 62272 392668 2004-09-17/18:11:32

BKPF 6.9 -> 7.7 negligible 40515 405152004-09-17/15:56:34



ANLP 3.5 -> 3.9 negligible 4095 1274462004-09-20/14:01:46

DBA_LOBS 3.2 -> 3.6 negligible 16 30722004-09-17/20:18:53

USER_INDEXES 3.2 -> 3.5 negligible 78 32153942004-09-17/16:42:26

USER_TABLES 1.4 -> 1.6 negligible 39 13564592004-09-17/16:42:09

DBA_SEGMENTS 1.3 -> 1.5 22.0 -> 24.8 19 192004-09-19/00:42:24

DBA_SEGMENTS 1.3 -> 1.5 28.1 -> 31.6 16 12341442004-09-17/20:01:06

DBA_EXTENTS 0.9 -> 1.1 8.4 -> 9.5 14 142004-09-19/00:42:42

DBA_SEGMENTS 0.9 -> 1.0 11.6 -> 13.0 20 202004-09-19/00:42:13

DBA_SEGMENTS negligible 2.3 -> 2.6 2 1542702004-09-20/03:00:23

Some statement loads are given within a range. If we state the load is 'up to' a certain value, the load ranges from very low value up to the maximum value (which is given after the '->').

You should cross reference the 'first load' date of each statement to the 'database startup' date, to see if the minimum load value or the maximum load value is most appropriate for a statement.

If the database has not been active for at least one day when the analysis is done, the information given may not be accurate.

Note: If an object name in the table above contains the character '/' it is a statement to a join. The different tables of the join are separated by '/'. Therefore, no object exists in the ABAP dictionary (transaction SE12) with the object name.


http://service.sap.com/smo.

11 Trend Analysis

11 Trend Analysis

This section contains the trend analysis for key performance indicators (KPIs). Diagrams or tables are built week by week after activating the EarlyWatch Alert Service (starting as of April 2002).

11.1 System ActivityThe following diagrams or tables show data on the system activity:

- Total Activity: Transaction steps per week- Dialog Activity: Transaction steps in dialog task per week- Peak Activity: Transaction steps in hour in peak- Total Users: Users that logged on in the week- Active Users: Users with more than 400 transaction steps in the week

SYSTEM ACTIVITY

Date Total Activity Dialog Activity Peak Activity

01.08.2004 801 625 14

19.09.2004 754 627 16

USERS

Date Logged on Active

01.08.2004 346 147

19.09.2004 261 162

11.2 Response TimesThe following diagram or table show the development of the response times:- Average response time in dialog task (total, DB and CPU parts)- Average response times for database requests- Average response times for the top 5 transactions

SYSTEM PERFORMANCE

Date Dialog Response Time Dialog DB Response Time Dialog CPU Time

01.08.2004 519 129 127

19.09.2004 520 247 135

DATABASE PERFORMANCE

Date

Time per Direct Read in Dialog task (ms)

Time per Seq. Read in Dialog task (ms)

Time per Change in Dialog task (ms)

Time per Direct Read in Background task (ms)

Time per Seq. Read in Background task (ms)

Time per Change in Background task (ms)

01.08.2004 0.0 0.8 4.2 0.2 8.4 3.5

19.09.2004 0.1 3.0 3.6 0.4 16.4 3.7

TOP 5 TRANSACTIONS

Date Transaction 1 Transaction 2 Transaction 3 Transaction 4 Transaction 5

01.08.2004 72 619

19.09.2004 44791 30828 24564 100 704

No Transaction Code Load (%)

Transaction 1 ZSALESCOSTREG 11.8

Transaction 2 ZFIARR001 9.7

Transaction 3 Y_DEV_09000010 9.1

Transaction 4 FB01 6.4

Transaction 5 SESSION_MANAGER 5.5


11 Trend Analysis

11.3 System OperationThe 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.

SYSTEM OPERATION

Date Availabity (%) Program Errors (ABAP) Update Errors

01.08.2004 99 33 0

19.09.2004 99 34 0

11.4 Hardware CapacityHARDWARE CAPACITY

Date Database Server CPU Max. Load (%) Appl. Server CPU Max. Load (%)

01.08.2004 21 0

19.09.2004 33 0

12 News in Service and Support

12.1 SAP Remote Performance OptimizationThe SAP Remote Performance Optimization tackles bottlenecks having a large impact on your system performance. It focuses on SQL statement optimization, customer program optimization or application optimization.

This service is best used when a previous service such as SAP EarlyWatch Alert or SAP Solution Management Assessment has already analyzed your mySAP.com solution and has identified and prioritized existing performance bottlenecks. SAP Remote Performance Optimization then focuses on eliminating the serious bottlenecks. In the end, you receive an action plan explaining the steps that you need to take to eliminate bottlenecks, thereby improving system performance.

Additional information regarding the SAP Remote Performance Optimization can be found on the SAP Service Marketplace under service.sap.com/rpo .


http://service.sap.com/rpo

Documents

Earlywatch Report