Analysis from Until Report: Installation: Session:

19.09.2011 25.09.2011 BWP 0020188132 1000000002826

EarlyWatch Alert - Productive 1 Service Summary

During the EarlyWatch Alert Service, we did not detect critical problems. 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. Section Overview Rating Checked Area System Configuration System Performance Workload Distribution SAP System Operating Hardware Capacity Note: For more information about EarlyWatch Alert, you can review a sample EarlyWatch Alert at: http://service.sap.com/ewa Library -> Media Library. This provides an overview of the rating strategy and the KPIs that trigger the alerts in this service. Service data was collected starting at 26.09.2011 04:45:05. This took 2 minutes. Note: If you require assistance in investigating the alerts highlighted in this report, create a customer message on process component SV-SMG-SER-EWA. Note: If performance is seriously compromised, create a customer message on component SV-BO with priority level "high" or "very high".

2 Performance Indicators for BWP

The following table shows the relevant performance indicators in various system areas. Area System Performance Indicators Active Users Average Response Time in RFC Task Value Trend 5 steady down

254

Area

Indicators

Value Trend ms

Max. number of RFCs per hour Average RFC response time during peak work hour Avg. Availability per Week Database Performance Average DB time for RFC Avg. DB Request Time in Update Task

542 111 ms

up down

100 % steady 43 ms down 43 ms down

3 System Configuration
To ensure optimal support of your SAP system, the SAP components, database, and operating system used must all be supported. Detailed information about SAP's platform support is available on SAP Service Marketplace at http://service.sap.com/platforms. Rating Check Hardware Configuration Software Configuration Service Preparation

3.1 Hardware Configuration

Server Overview Server Operating System Metis Windows Server 2003 on x86_64 No. of CPUs Memory in MB 4 32767

3.2 Software Configuration

3.2.1 Database
Database System Database Server Metis Database System SQL SERVER Current Version 2005

3.2.2 SAP Application Release: Maintenance Phases

SAP Product SAP NetWeaver SAP Product Version 7.0 End of Mainstream Maintenance 31.12.2015

Your BWP system is running on SAP NetWeaver 7.0. This release will be in mainstream maintenance until 31.12.2015.

3.2.3 Support Package Maintenance

Support Packages Latest SAP SAP Patch Avail. Support Component Component Level Patch Package Version Level BI_CONT PI_BASIS SAP_ABA SAP_BASIS SAP_BW ST-PI 703 701 701 701 701 9 6 6 6 6 6 15 SAPKIBIIP9 Component Description SAP Business Intelligence Content

SAPKSAP R/3 70106INPIBASIS Basis Plug-In SAPKA70106 SAPKB70106 SAPKW70106 SAPKITLQI6 SAP Application Basis SAP Basis Component SAP Business Information Warehouse SAP Solution Tools Plug-In

2005_1_700 6

3.2.4 SAP Kernel Release

You are running SAP Kernel Release 701, patch level 69.

3.2.4.1 Kernel probably out of date

It is likely that your current SAP kernel release is not up-to-date. If your SAP kernel patch level is not up-to-date, you cannot benefit from the error corrections and optimizations SAP offers to its customers. You may encounter errors or performance issues that have already been solved. Recommendation: Ensure that you are using the recommended SAP kernel together with the latest Support Package Stack of your product.

3.2.4.2 Additional Remarks

SAP releases Support Package Stacks (including SAP Kernel patches) on a regular basis for most products (generally 2-4 times a year). We recommend that you base your software maintenance strategy on these stacks. You should only consider using a more recent SAP Kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur. For more information, see SAP Service Marketplace at http://service.sap.com/sp-stacks (SAP Support Package Stack information) and http://service.sap.com/patches (patch information).

3.2.5 Implemented SAP Notes via SAP Notes Assistant

SAP Note Version Component Description BW-BEX-ETjava.lang.UnsupportedOperationException WJR BC-DWBTOO-FUB BC-TWBTST-ECA Security note: Program DISPLAY_FUNC_INCLUDE Error in parameter transfer to Rerecord for TCD

0001413377 0004

0001168813 0006

0000873603 0001

3.3 Service Preparation

System BWP is not fully prepared for service delivery. Rating Performed Check ST-PI and ST-A/PI Plug-Ins Service Preparation Check (RTCCTOOL) Service Data Control Center Missing Function Modules Errors in Data Collection SAP OS Collector Workload Monitor (ST03)

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

SAP Solution Manager is recommended for the delivery of SAP Support remote services. For more information, see SAP Note 1170668 .

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

The table below shows the implemented service plug-ins, their releases, and patch levels, as well as the recommended releases, patch levels, and recommendations. PlugRelease In Patch Rec. Level Release Rec. SAP Patch Recommendation Note Level ST-A/PI is not up to date. Please run RTCCTOOL and follow the given recommendations.

Rating

STA/PI

01I_BCO620 -

01L_BCO700 -

69455

ST-PI is not up to date. Please run ST-PI 2005_1_700 0006 2008_1_700 0000 RTCCTOOL and 539977 follow the given recommendations.

3.3.2 Service Preparation Check (RTCCTOOL)

We were unable to perform the check. Recommendation: ST-A/PI is not up to date. Please run RTCCTOOL and follow the given recommendations. Implement SAP Note 69455 and follow the instructions in SAP Note 91488.

3.3.3 Errors in Data Collection

The following exceptions were raised during data collection: Host Metis Function Name MSS_GROWING_TABLES Exception FUNCMOD_NOT_FOUND

Recommendation: Review the SDCC(N) data collection log for this session. For function modules with an exception, check whether a help text appears when you double-click the exception. If you have access to SAP Notes, search for these errors and the corresponding short dumps or system log entries. If you cannot resolve the problem, open a message on component SV-SMG-SDD.

3.3.4 SAP Application Servers

The following information can be found in transaction SM51:

SAP Application Server Metis_BWP_00

SM51 Host Name Metis

4 Performance Overview BWP

The performance of your system was analyzed with respect to the average response times and total workload. We did not detect any major problems that could affect the performance of your system. The following table shows the average response times for various task types: Avg. Dialog Resp. Steps Time in ms 181 32488 2 35945 10078 451 755,0 254,0 101,0 269,9 5,4 276,2 Avg. Avg. Avg. Avg. Avg. CPU Wait Load DB GUI Time in Time in Time in Time in Time in ms ms ms ms ms 59,7 57,5 15,5 37,8 0,9 92,8 1,2 3,7 0,0 0,1 0,0 50,1 1,0 0,6 0,5 1,4 0,1 0,8 98,1 43,1 75,5 84,0 0,4 147,5 602,2 0,0 0,0 0,0 0,0 0,0

Task type

DIALOG RFC UPDATE2 BATCH SPOOL HTTP

Over 200 ms of the response time is GUI time. This may indicate poor GUI performance. High GUI times are normally caused by bad network connections or user menus downloading too much data. We recommend that you review SAP Notes 203617 and 203924, which explain the reasons for high GUI times.

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 12 Medium Activity 2 High Activity 3 Total Users 17

4.2 Transaction Profile Check

The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system.

4.2.1 Transactions by Total Workload

The following tables list the activities with the highest contribution to the total workload. Workload by Transaction (Dialog/Update) Transaction Total BI_CLIENT_RUNTIME HTTP DB02_MSS ST06 DB12_MSS RSPCM SAPMHTTP DB13 SM50 SM13 DIA DIA DIA DIA HTTP DIA DIA DIA Total Avg. Dialog Resp. Resp. Type Steps Time Time in % in ms 632 117 18 25 13 21 17 330 1 5 10 100,0 44,2 7,5 5,8 3,7 3,5 1,8 1,4 413,3 Avg. CPU Time in ms Avg. DB Time in ms Avg. GUI Time in ms 602,2 0,0 728,6 608,4 200,4 0,0 794,4 327,1 Avg. Avg. CPU DB Time in Time in ms ms 26,9 59,6

83,3 133,4

985,8 328,5 518,9 786,8 715,8 27,9 919,2 369,3 38,8 81,8 40,2 10,4 59,4 34,4 18,2 67,7 17,6 70,2 18,8

18,1 2629,6 142,4 500,3 2000,5 6,5 1313,8 45,2 1187,5

SESSION_MANAGER DIA

575,1 129,6 258,8

3,4 8985,0 313,0 114,0 8610,0

Workload by Transaction (Batch/Spool) Transaction Total RSBTCPRIDEL RSPROCESS SBIE0001 SAPRSLOG (BATCH) RSLDAGDS /BDL/TASK_SCHEDULER RSPO1043 RSBTCRTE BTC BTC BTC BTC BTC BTC BTC BTC BTC Total Avg. Dialog Resp. Resp. Type Steps Time Time in in % ms 45855 100,0 28 235 168 15 7 18824 14 168 14 8541 17,6 10,7 197,0 6747,2 5759,5

39,4 127209,1 4242,8 5796,1 647,0 3045,8 267,1 5289,3

RSAL_BATCH_TOOL_DISPATCHING BTC

8,4 50403,4 3790,7 5551,7 4,6 59925,0 14654,0 52529,4 4,1 2,4 2,3 19,6 1307,8 24,6 10,5 176,4 17,3 37,7 7,0 188,7 13,2 6,5 3,4 21623,6

2,3 15079,4 5919,6 12693,6

4.2.2 Transactions by DB Load

The following transaction profiles list the transactions that have the greatest share in the database load, sorted by percentage of total database access times. Database Load by Transactions (Dialog/Update) Transaction Total Type Dialog Steps 632 Total DB Time in % 100,0 Avg. DB Time in ms 133,4

Database Load by Transactions (Dialog/Update) Transaction DB02_MSS SAPMHTTP RSPCM DB12_MSS ST06 SM37 SM50 ST22 Type DIA HTTP DIA DIA DIA DIA DIA DIA Dialog Steps 117 18 330 17 21 13 25 10 5 9 Total DB Time in % 72,0 10,7 6,9 5,2 1,7 0,7 0,5 0,5 0,4 0,2 Avg. DB Time in ms 518,9 500,3 17,6 258,8 67,7 45,2 18,2 40,0 70,2 21,9

BI_CLIENT_RUNTIME HTTP

SESSION_MANAGER DIA

Database Load by Transactions (Batch/Spool) Transaction Total RSAL_BATCH_TOOL_DISPATCHING BTC RSPROCESS SAPRSLOG RSPO1043 RSBTCPRIDEL (BATCH) SBIE0001 RSBTCRTE RSBATCH_EXECUTE_PROZESS RSBTCDEL BTC BTC BTC BTC BTC BTC BTC BTC BTC Type Dialog Steps 45855 168 235 7 14 28 18824 15 8541 235 14 Total DB Avg. DB Time in Time in ms % 100,0 32,5 26,2 13,5 6,5 5,9 4,8 3,0 2,0 1,9 1,2 59,6 5289,3 3045,8 52529,4 12693,6 5796,1 7,0 5551,7 6,5 218,8 2334,1

5 Workload Distribution BWP

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 Module

The following diagrams 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

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

Module BC BC-CCM Not Assigned BW

CPU Time in % 69,3 16,6 10,5 3,6

Module BC Not Assigned BC-CCM BW

DB Time in % 51,0 22,7 13,2 13,1

5.2 DB Load Profile

The following diagram shows the DB load caused by dialog, RFC, and background tasks over different time frames. The data provided in the table represents the average number of database processes occupied by each task type in the database during the specified time frames. These statistics are calculated as a weekly average, which means the average values over six working days with a unit of one hour. Periods between 00:00-06:00 and 21:00-24:00 contain an average value per hour as these are not considered core business hours. The disk space of the time profile is reduced by the default creation of these time blocks. 24-hour monitoring can be enabled by implementing SAP Note 17750. With 24-hour monitoring, the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for periods between 00:0006:00 and 21:00-24:00. By comparing the load profiles for dialog and background activity, you can get an overview of the volume of background activity during online working hours.

The diagram above indicates that the CPUs can handle the database load.

5.3 RFC Communication

The performance of your system was analyzed with respect to the average call times and the workload created by remote function calls between the current system and other SAP and non-SAP Systems. The following tables show statistics about RFCs. Note: Internal RFC communication (that is, communication between the instances of the analyzed system) is not shown in the tables. Average Total call Bytes Calls call Bytes sent time, received time, s ms 2485 1703,95 40 1522,98 370 1232,70 3528 711,83 5100 351,73 14 293,24 686 32690616 479605 11000 713452

Outgoing function call

ARFC_DEST_SHIP RSAP_TRFC_SEND QDEST_RUN_DESTINATION ARFC_RUN_NOWAIT IDOC_START_INBOUND SET_SLD_DATA

38074 2887277764 3332 202 69 20945 1477582

3575180 5080402 44424612 3988785 56938 52962

Outgoing function call

Average Total call Bytes Calls call Bytes sent time, received time, s ms 12604 253,38 2 118,28 5 108,63 20 59138 21726 5251896 5545556 560 11084 576 730

RFC_PING /BDL/_REQUEST_DATA_TASK /BDL/_DO_GENERATION

Incoming function call

Average Total call Bytes Calls call time, sent time, s ms 546 2318,73 118 2310,36 40 1433,09 178 1241,05 742 1232,91 2445 676,55 4776 481,26 4247 35705

Bytes received

ARFC_DEST_SHIP RSAR_TRFC_DATA_RECEIVED RSAP_TRFC_SEND QDEST_RUN QDEST_RUN_DESTINATION ARFC_RUN_NOWAIT ARFC_DEST_SHIP

35642084 52014606

19579 52005284 35827 6972 1662

25560 2887276324 0 852138 67012 2931820 2390714 13008646 4609614 22110306

277 6008340 101 496203

IDOC_INBOUND_ASYNCHRONOUS 5121 456,44 IDOC_START_INBOUND 2550 323,41

89 2772235 127 4916985

6 SAP System Operating BWP

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

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

6.2 Transports

Transports were not found in the period analyzed.

6.3 Program Errors (ABAP Dumps)

3 ABAP dumps have been recorded in your system in the period 19.09.2011 to 26.09.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 19.09.2011 20.09.2011 21.09.2011 22.09.2011 23.09.2011 24.09.2011 25.09.2011 26.09.2011 Name of runtime Error(s) CONVT_NO_NUMBER CALL_FUNCTION_CONFLICT_LENG Total of User Server (e.g.) Error(s) (e.g.) Quantity of Dumps 2 0 0 0 0 0 0 1 Date (e.g.) Time (e.g.)

1 Metis_BWP_00 AEPEX_TB 19.09.2011 04:47:08 2 Metis_BWP_00 AEPEX_TB 26.09.2011 04:45:15

It is important that you monitor ABAP dumps using transaction ST22 on a regular basis. If ABAP dumps occur, you should determine the cause as soon as possible. Based on our analysis, we expect no serious problems at the moment.

6.4 Security-related SAP Notes

Security-related SAP Notes cannot be checked because the RSECNOTE tool is missing. The new RSECNOTE tool enables you to analyze security-relevant SAP Notes for your system. Recommendation: Apply relevant security-related SAP HotNews and Notes. An overview about such notes is published on SAP Service Marketplace at /securitynotes . To display a list of relevant security-related SAP HotNews and Notes that can be implemented easily, run the RSECNOTE tool in transaction ST13. It provides a detailed list of the vulnerabilities discovered and the corresponding SAP Notes for correction. More security issues may exist. Install RSECNOTE using the correction in SAP Note 888889 and review this SAP Note for more information.

7 Hardware Capacity
We have checked your solution for potential CPU or memory bottlenecks and found that the hardware resources have been exhausted. An increase in the workload may have a negative impact on performance. 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, refer to SAP Note 1251291: 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 for a CPU bottleneck. Memory If your hardware cannot handle the maximum memory consumption, your SAP system will suffer from a memory bottleneck that can impair performance. The paging rating depends on the ratio between the paging activity and the physical memory. Max. Server CPU load Date [%] Metis 3 20.09.2011 RAM [MB] 32767 Max. Paging Date Rating [% of RAM] 0

Rating

7.1 Paging Out for Windows 2003 Servers

The following servers showed high paging out rates in at least three successive hours even though sufficient memory was available. Server OS Windows Server 2003 on x86_64 RAM [MB] 32767 Max. Pages Hour Date Out / s 803 12 23.09.2011 Rating

Metis

Recommendation: See SAP Note 1009297 and consider implementing the solution provided by Microsoft.

7.2 Wait Statistics

This check was not carried out, since at the time of data collection, the database had not been running long enough to provide meaningful data.

7.3 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 system. A missing index of any kind can lead to severe performance problems. No missing indexes were found on system BWP.

7.3.1 Largest Tables

The following table shows the largest tables currently in the database. Reserved (data + indexes) kB 9671096 6782912 5295712 4966064 4924712 3340296 2902416 2328120 2193720 2065040 Used (data + Rows indexes) kB 9669120 12407825 6781376 29260633 5294664 4026269 4965136 3751365 4923328 12435358

Table Name

Data (kB)

Modified Rows

/BIC/B0000334000 7174160 /BIC/B0000544000 6678080 /BIC/B0000337000 4601736 /BIC/B0000335000 4287288 /BIC/B0000332000 2842408 RSDDSTATLOGGING 3281904 WBCROSSGT 1194976

1586208 4016167 502251 63037 1559375

3339392 21549506 22103046 2900560 10682388 2327368 16896756 2193080 1262607 2062488 2237647 9877 916600 115731 235701

/BIC/B0000479000 2291176 EDI40 RSMONMESS 2170088 632504

7.3.2 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 4053 Builds Comment See SAP Note 62988 for newest build

The current Service Pack appears to be the latest Service Pack available from Microsoft. To verify this, see SAP Note 62988. Note: New Service Packs are available on the CDs shipped by SAP or can be obtained directly from Microsoft.

See SAP Note 62988 for more information on how to obtain the latest Service Pack and on the Service Packs that are currently supported by SAP.

7.3.3 Tables With Page Locking Disabled

Table EDI40 VBMOD VBHDR ARFCSDATA VBDATA EDIDS EDIDC ARFCRDATA D010TAB Page locking Page locking disallowed Page locking disallowed Page locking disallowed Page locking disallowed Page locking disallowed Page locking disallowed Page locking disallowed Page locking disallowed All lock levels allowed Rating

As shown above, page locking must be disallowed for some tables. Recommendation: Disallow page locking for tables VBHDR, VBMOD, VBDATA, ARFCSDATA, ARFCRDATA, D010TAB (as of Basis Release 6.10), and TRFCQUEUE (if it exists) as described in SAP Note 879941. Implementation: This can be done using SQL command: EXEC sp_indexoption <tablename>, "DisAllowPageLocks", "TRUE" Background: For some tables, disallowing page locks improves the concurrency of accesses from different users to these tables, therefore avoiding deadlocks.

8 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. Historical data for "Transaction Activity" and "System Performance" is taken from workload monitor ST03 directly if data has been accumulated for less than 20 sessions.

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

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.

8.2 Response Times

The following diagrams show how the response time varies over time.

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

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

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

The "Transaction Code" table below shows the load percentage caused by the top 5 transactions. Transaction Code DB02_MSS Load (%) 34.6

Transaction Code ST06 DB12_MSS SESSION_MANAGER RSPCM

Load (%) 14.4 12.5 11.0 7.2

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

8.4 Hardware Capacity