Service Report

SAP EarlyWatch Alert

SAP System ID SAP Component Release Status DB System

PRD R/3 470 Productive ORACLE 9.2.0.4.0

Customer

Videsh Sanchar Nigam Limited Lokmanya 400 028 Prabhadevi, Mumbai India

Service Center Telephone Fax Date of Session Date of Report Author 21.09.2004 21.09.2004 EarlyWatch Alert Service
<Watermark>

<dat_dummy>

Session No. Installation No. Customer No.

0010001706025 0020064299 0000366508

3 System Configuration

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 Messages The 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 High At least one ABAP dump of type 'SAPSQL_ARRAY_INSERT_DUPREC' was found. Medium Performance problems exist or are expected. Medium Update your SAP R/3 Plug-In to the latest release available. New Alert New New 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 System Performance Indicators Active Users Avg. Response Time in Dialog Task Max. Dialog Steps per Hour Avg. Response Time at Peak Dialog Hour EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004 Value 162 520 ms 16405 581 ms Trend up steady up up 2

3 System Configuration Area Database Performance Database Space Management Indicators Avg. Availability per Week Avg. DB Request Time in Dialog Task Avg. DB Request Time in Update Task DB Size Last Month DB Growth Value 99 % 247 ms 79 ms 41.61 GB 5.94 GB Trend steady up up up 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 Configuration

The table below shows the detected hardware configuration: HARDWARE CONFIGURATION Server Type Database Server DATABASE SYSTEM Database Server sap-prd Database System ORACLE Current Version 9.2.0 Server sap-prd OS HP-UX OS Version 11.11 Number of CPUs 4 Memory [MB] 8184

3.2 Software Configuration

The table below shows the Support Packages applied: Release 470 470 620 620 PlugIn PI 2002_1_470 PI_BASIS 2002_1_620 ST-A/PI 01E_R3_470 ST-PI 003C_620 Patch Number RA 19 06 26 37 37 Status of Patch I I I I I I Patch SAPKITLPRA SAPKH47019 SAPKGPRA06 SAPKE47026 SAPKB62037 SAPKA62037 PlugIn Patch Level 0003 0006 0000 0002 3 Type AOI COP AOP COP COP COP

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration

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 type DIALOG RFC UPDATE UPDATE2 BATCH SPOOL HTTP Dialog Steps 626779 18577 68153 2127 35890 2657 4 Avg. Resp. Time in ms 520,1 554,3 183,0 84,9 937,3 4696,4 4497,3 Avg. CPU Time in ms 134,5 112,5 41,5 16,2 75,1 70,4 87,5 Avg. Wait Time in ms 15,5 5,4 63,9 10,3 9,0 781,0 491,5 Avg. Load Time in ms 6,5 1,6 4,9 3,7 7,7 2,0 181,5 Avg. DB Time Avg. GUI in ms Time in ms 246,7 95,9 78,6 54,3 590,2 176,5 2439,0 102,3

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration

4.1 Current Workload

The following table lists the number of current users (measured from our workload analysis) in your system. Users Measured in System Low Activity 99 Medium Activity 133 High Activity 29 Total Users 261

4.2 Performance Evaluation

For 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 Dia Upd RFC Batch Dialog Steps 626779 68153 18577 35890 Application Server Performance Database Server Performance

4.3 Comparison of Response Times

The 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. Transaction ZSALESCOSTREG ZFIARR001 Y_DEV_09000010 FB01 SESSION_MANAGER ZFIAPR004 ZFIGLR005 F-02 KSU5 ZST FS10N FBL5N PC00_M40_CALC SAPMS380 FK10N Load [%] 11,8 9,7 9,1 6,4 5,5 3,2 3,1 2,9 2,9 2,2 1,9 1,9 1,7 1,5 1,4 Current Avg. Resp. Time [ms] 44791 30828 24564 100 704 2339 40576 128 9404 6458 161 240 18633 11072 670 Previous Avg. Resp. Time [ms] 0 0 0 72 -619 -4229 ++ 0 64 -0 0 139 -0 12813 -0 1581 ++ Trend Comment New New New DB relevant DB relevant DB relevant New DB relevant New New DB relevant New DB relevant New

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration

4.4 History of Activity and Average Response Times

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

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration Rating Check Workload by Application Module DB Load Profile

5.1 Workload by Application Module

The 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 FI BC CO-OM FI-GL PY MM Unknown CA DB LOAD BY APPLICATION Module FI BC Unknown FI-GL MM PY CO-OM DB Time in % 77,4 13,4 1,9 1,2 1,2 1,1 1,1 CPU Time in % 50,2 17,0 9,1 7,0 5,2 3,4 2,7 2,6

5.2 DB Load Profile

The 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 00--06 06--07 07--08 08--09 09--10 10--11 11--12 12--13 13--14 DB Load (DIA) 0,00 0,00 0,00 0,00 0,07 1,15 0,88 0,49 0,34 DB Load (RFC) 0,00 0,00 0,00 0,00 0,00 0,00 0,01 0,00 0,00 DB Load (BTC) 0,01 0,01 0,19 0,01 0,00 0,01 0,01 0,01 0,01 7

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration Start_End Time 14--15 15--16 16--17 17--18 18--19 19--20 20--21 21--24 DB Load (DIA) 0,49 1,06 1,01 0,82 0,47 0,34 0,03 0,00 DB Load (RFC) 0,01 0,02 0,01 0,01 0,00 0,01 0,00 0,00 DB Load (BTC) 0,01 0,01 0,02 0,01 0,01 0,01 0,61 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 Availability

The 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 13.09.2004 14.09.2004 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 Availability, % 100 100 100 100 88 100 100 100

6.2 Update Errors

UPDATE ERRORS BY DAY Date 06.09.2004 13.09.2004 14.09.2004 EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004 Quantity of Errors 3 0 0 8

3 System Configuration Date 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 We did not detect any problems. Quantity of Errors 0 0 0 0 0 0

6.3 Table Reorganization

During 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 APQD Size of Tables or Indexes [MByte] Recommended SAP Note 2112 36781, 18307

6.4 Transports
The 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 Date 13.09.2004 14.09.2004 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 TRANSPORTED PROGRAMS Date 13.09.2004 14.09.2004 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 TRANSPORTED TABLES Date 13.09.2004 14.09.2004 Total Number of Transported Tables SAP Tables Customer Tables Tables in Support Packages 1 0 0 0 1 0 0 0 9 Total Number of Transported Programs 17 16 11 4 6 0 0 2 SAP Programs 0 0 0 0 0 0 0 0 Customer Programs 17 16 11 4 6 0 0 2 Programs in Support Packages 0 0 0 0 0 0 0 0 Total Number of Transported Objects 45 45 34 11 20 0 0 7 SAP Objects 0 0 0 0 0 0 0 0 Customer Objects 45 45 34 11 20 0 0 7 Objects in Support Package 0 0 0 0 0 0 0 0

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration Date 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 Total Number of Transported Tables SAP Tables Customer Tables Tables in Support Packages 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 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 13.09.2004 14.09.2004 15.09.2004 16.09.2004 17.09.2004 18.09.2004 19.09.2004 20.09.2004 DETECTED ABAP DUMPS Error SAPSQL_ARRAY_INSERT_DUPREC LOAD_PROGRAM_NOT_FOUND LOAD_PROGRAM_LOST SAPSQL_WHERE_QUOTES BCD_ZERODIVIDE DBIF_RSQL_SQL_ERROR CONTROL_NOT_FOUND TIME_OUT SYSTEM_CORE_DUMPED COLLECT_OVERFLOW_TYPE_P Number Server (e.g.) 7 2 1 2 7 2 1 9 2 1 sap-prd sap-prd sap-prd sap-prd sap-prd sap-prd sap-prd sap-prd sap-prd sap-prd User (e.g.) VHRBIJOY E01189 E19967 E13392 VFISARVANA VFIPRASHANT E18339 E02419 VFISARVANA VFIPRASHANT Date (e.g.) Time (e.g.) 20040915 20040915 20040915 20040915 20040917 20040917 20040920 20040920 20040920 20040920 122022 124552 162418 180841 161735 175808 145113 163927 174405 181727 Quantity of Dumps 0 0 23 12 9 3 0 8

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.

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

10

3 System Configuration Server sap-prd Max. CPU load [%] 33 Rating RAM [MB] 8184 Max. Paging [% of RAM] 6 Rating

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 user

The 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 TOTAL (not a user name!) SYS SYSTEM OPS$PRDADM SAPPRD EXECUTIONS 11837827 16% 0% 0% 83% DISK READS 11729829 1% 1% 3% 95% BUFFER GETS 1121248909 1% 0% 1% 98% ROWS PROCESSED 61541966 4% 0% 1% 96%

8.2 Database Parameters

We 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 0124361 Description Oracle database parameter setting for R/3 4.x 11

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration Note number 0132503 0170989 Parameters _optim_peek_user_binds Description Update of threshold values of database system check Views perform poorly (Oracle 8044 & 805* & 806) Description Bind value picking Current value Recommended value 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 event Current Value 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 10191 Note number for Event 128221 Description Increased memory consumption with Oracle 8

8.3 Order of Redo Log Files

Using 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# 3 3 4 4 2 2 1 1 SEQUENCE# 5532 5532 5533 5533 5534 5534 5535 5535 File Name 1 1 1 1 1 1 1 1

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

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

12

3 System Configuration

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 Growth

The following figure shows the development of the size of your database in GB. DATABASE SIZE Date 30.04.2004 31.05.2004 30.06.2004 31.07.2004 31.08.2004 21.09.2004 An overview of the freespace development of your database in GB is shown here. DATABASE FREE SPACE Date 30.04.2004 31.05.2004 30.06.2004 31.07.2004 31.08.2004 21.09.2004 The following table shows you the current size and the monthly growth of your database in GB. Date 31.05.2004 30.06.2004 31.07.2004 31.08.2004 21.09.2004 Current Size in GB 23,55 26,07 33,38 39,32 41,61 Monthly Growth in GB 0,10 2,52 7,31 5,94 DB Size free 17,15 17,05 14,53 11,57 9,38 11,39 DB Size used 23,45 23,55 26,07 33,38 39,32 41,61

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

13

3 System Configuration

9.2 Freespace in Tablespaces

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

Tablespaces - Autoextend ON
Tablespace PSAPPRD PSAPPRD620 Size (KB) Free (KB) Avg. Chg/Week (KB) 31432696 2026304 22528000 8801664 17152 1529063 29055 34 %-Used AutoExt 93 60 16 %-Used after AutoExt 133,120,000 22 112,640,000 12 10,240,000 0

PSAPPRDUSR 20480

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 upgrade

Recommendation: Upgrade your release 9.2 of Oracle to the latest available patch set for your version Refer also to the following SAP Notes: 610445 Merge fix for Oracle 9.2.0.3 695080 Merge fix for Oracle 9.2.0.4

10 Database server load from expensive SQL statements

Expensive SQL Statements

DATABASE LOAD CAUSED BY EXPENSIVE STATEMENTS CPU & memory load [%] 74.4 -> 83.4 I/O load [%] 73.3 -> 82.4 DB startup date 17.09.2004 DB analysis date 21.09.2004 Comment

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 name M_KREDA RFBLG BKPF M_KREDA CPU & memory load [%] 20.7 -> 23.2 18.7 -> 20.9 6.9 -> 7.7 6.4 -> 7.1 I/O Load [%] Executions negligible negligible negligible negligible 2 62272 40515 130 Records processed 10 392668 40515 1653 First load date/time 2004-09-17/16:08:05 2004-09-17/18:11:32 2004-09-17/15:56:34 2004-09-17/15:58:19 14

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

3 System Configuration Object name M_KREDA ANLP DBA_LOBS USER_TABLES CPU & memory load [%] 5.9 -> 6.6 3.5 -> 3.9 3.2 -> 3.6 1.4 -> 1.6 I/O Load [%] Executions negligible negligible negligible negligible negligible 4 4095 16 78 39 Records processed 14 127446 3072 3215394 1356459 19 1234144 14 20 154270 First load date/time 2004-09-20/13:02:51 2004-09-20/14:01:46 2004-09-17/20:18:53 2004-09-17/16:42:26 2004-09-17/16:42:09 2004-09-19/00:42:24 2004-09-17/20:01:06 2004-09-19/00:42:42 2004-09-19/00:42:13 2004-09-20/03:00:23

USER_INDEXES 3.2 -> 3.5 DBA_SEGMENTS 1.3 -> 1.5 DBA_SEGMENTS 1.3 -> 1.5 DBA_EXTENTS 0.9 -> 1.1 DBA_SEGMENTS 0.9 -> 1.0 DBA_SEGMENTS negligible

22.0 -> 24.8 19 28.1 -> 31.6 16 8.4 -> 9.5 2.3 -> 2.6 14 2 11.6 -> 13.0 20

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.

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 Activity

The 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 01.08.2004 19.09.2004 USERS Date 01.08.2004 19.09.2004 Logged on 346 261 Active 147 162 Total Activity 801 754 Dialog Activity 625 627 Peak Activity 14 16

11.2 Response Times

The 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 EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004 15

3 System Configuration SYSTEM PERFORMANCE Date 01.08.2004 19.09.2004 Dialog Response Time 519 520 Dialog DB Response Time 129 247 Dialog CPU Time 127 135

DATABASE PERFORMANCE Date Time per Direct Read in Dialog task (ms) Time per Seq. Read in Dialog task (ms) 0.8 3.0 Time per Change in Dialog task (ms) 4.2 3.6 Time per Direct Read in Background task (ms) 0.2 0.4 Time per Seq. Time per Change Read in in Background Background task task (ms) (ms) 8.4 16.4 3.5 3.7

01.08.2004 0.0 19.09.2004 0.1 TOP 5 TRANSACTIONS Date 01.08.2004 19.09.2004 No Transaction 1 Transaction 2 Transaction 3 Transaction 4 Transaction 5 44791

Transaction 1

Transaction 2 30828 Transaction Code ZSALESCOSTREG ZFIARR001 Y_DEV_09000010 FB01

Transaction 3 24564

Transaction 4 72 100

Transaction 5 619 704 Load (%) 11.8 9.7 9.1 6.4 5.5

SESSION_MANAGER

11.3 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. SYSTEM OPERATION Date 01.08.2004 19.09.2004 Availabity (%) 99 99 Program Errors (ABAP) 33 34 Update Errors 0 0

11.4 Hardware Capacity

HARDWARE CAPACITY Date 01.08.2004 19.09.2004 Database Server CPU Max. Load (%) 21 33 Appl. Server CPU Max. Load (%) 0 0

12 News in Service and Support

12.1 SAP Remote Performance Optimization
The 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 EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004 16

3 System Configuration 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 .

EarlyWatch Alert Report , Videsh Sanchar Nigam Limited Lokmanya, 21.09.2004

17