2 Performance Indicators for BWP

Analysis from 19.09.2011 Until 25.09.2011 Report: BWP Installation: 0020188132 Session: 1000000002826 EarlyWatch Alert - Productive 1 Service Summary During the EarlyWatch Alert Service, we did not detect critical proble. 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 Indicators Value Trend System Performance Active Users 5 steady Average Response Time in RFC Task 254 down

Area Indicators Value Trend Max. number of RFCs per hour 542 up Average RFC response time during peak work hour 111 down Availability per Week 100 % steady Database Performance Average DB time for RFC 43 down DB Request Time in Update Task 43 down 3 System Configuration Rating 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/platfor. Check Hardware Configuration Software Configuration Service Preparation 3.1 Hardware Configuration Server Overview Server Operating System No. of CPUs Memory in MB Metis Windows Server 2003 on x86_64 4 32767 3.2 Software Configuration 3.2.1 Database Database System Database Server Database System Current Version Metis SQL SERVER 2005

3.2.2 SAP Application Release: Maintenance Phases SAP Product SAP Product Version End of Mainstream Maintenance SAP NetWeaver 7.0 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 SAP SAP Component Component Version Patch Level Latest Avail. Patch Level Support Package BI_CONT 703 9 15 SAPKIBIIP9 PI_BASIS 701 6 SAPK- 70106INPIBASIS SAP_ABA 701 6 SAPKA70106 SAP_BASIS 701 6 SAPKB70106 SAP_BW 701 6 SAPKW70106 ST-PI 2005_1_700 6 6 SAPKITLQI6 Component Description SAP Business Intelligence Content SAP R/3 Basis Plug-In SAP Application Basis SAP Basis Component SAP Business Information Warehouse SAP Solution Tools Plug-In 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 0001413377 0004 BW-BEX-ET- WJR java.lang.unsupportedoperationexception 0001168813 0006 BC-DWB- TOO-FUB Security note: Program DISPLAY_FUNC_INCLUDE 0000873603 0001 BC-TWB- TST-ECA Error in parameter transfer to Rerecord for TCD 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. Rating Plug- In Release Patch Level Rec. Release Rec. Patch Recommendation SAP Note Level ST- A/PI 01I_BCO620-01L_BCO700 - ST-A/PI is not up to date. Please run RTCCTOOL and follow the given recommendations. 69455 ST-PI 2005_1_700 0006 2008_1_700 0000 ST-PI is not up to date. Please run RTCCTOOL and follow the given recommendations. 539977 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 Function Name Exception Metis MSS_GROWING_TABLES 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 proble that could affect the performance of your system. The following table shows the average response times for various task types: Task type Dialog Steps Resp. Time in CPU Time in Wait Time in Load Time in DB Time in GUI Time in DIALOG 181 755,0 59,7 1,2 1,0 98,1 602,2 RFC 32488 254,0 57,5 3,7 0,6 43,1 0,0 UPDATE2 2 101,0 15,5 0,0 0,5 75,5 0,0 BATCH 35945 269,9 37,8 0,1 1,4 84,0 0,0 SPOOL 10078 5,4 0,9 0,0 0,1 0,4 0,0 HTTP 451 276,2 92,8 50,1 0,8 147,5 0,0 Over 200 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 Low Activity Medium Activity High Activity Total Users Measured in System 12 2 3 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 Type Dialog Steps Total Resp. Time in % Resp. Time in CPU Time in DB Time in GUI Time in Total 632 100,0 413,3 83,3 133,4 602,2 BI_CLIENT_RUNTIME HTTP 117 44,2 985,8 328,5 518,9 0,0 DB02_MSS DIA 18 18,1 2629,6 142,4 500,3 2000,5 ST06 DIA 25 7,5 786,8 38,8 18,2 728,6 DB12_MSS DIA 13 6,5 1313,8 81,8 45,2 1187,5 SESSION_MANAGER DIA 21 5,8 715,8 40,2 67,7 608,4 RSPCM DIA 17 3,7 575,1 129,6 258,8 200,4 SAPMHTTP HTTP 330 3,5 27,9 10,4 17,6 0,0 DB13 DIA 1 3,4 8985,0 313,0 114,0 8610,0 SM50 DIA 5 1,8 919,2 59,4 70,2 794,4 SM13 DIA 10 1,4 369,3 34,4 18,8 327,1 Workload by Transaction (Batch/Spool) Transaction Type Dialog Steps Total Resp. Time in % Resp. Time in CPU DB Time in Time in Total 45855 100,0 197,0 26,9 59,6 RSBTCPRIDEL BTC 28 39,4 127209,1 4242,8 5796,1 RSPROCESS BTC 235 17,6 6747,2 647,0 3045,8 RSAL_BATCH_TOOL_DISPATCHING BTC 168 10,7 5759,5 267,1 5289,3 SBIE0001 BTC 15 8,4 50403,4 3790,7 5551,7 SAPRSLOG BTC 7 4,6 59925,0 14654,0 52529,4 (BATCH) BTC 18824 4,1 19,6 10,5 7,0 RSLDAGDS BTC 14 3,4 21623,6 176,4 188,7 /BDL/TASK_SCHEDULER BTC 168 2,4 1307,8 17,3 13,2 RSPO1043 BTC 14 2,3 15079,4 5919,6 12693,6 RSBTCRTE BTC 8541 2,3 24,6 37,7 6,5 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 Type Dialog Steps Total DB Time in % DB Time in Total 632 100,0 133,4

Database Load by Transactions (Dialog/Update) Transaction Type Dialog Steps Total DB Time in % DB Time in BI_CLIENT_RUNTIME HTTP 117 72,0 518,9 DB02_MSS DIA 18 10,7 500,3 SAPMHTTP HTTP 330 6,9 17,6 RSPCM DIA 17 5,2 258,8 SESSION_MANAGER DIA 21 1,7 67,7 DB12_MSS DIA 13 0,7 45,2 ST06 DIA 25 0,5 18,2 SM37 DIA 10 0,5 40,0 SM50 DIA 5 0,4 70,2 ST22 DIA 9 0,2 21,9 Database Load by Transactions (Batch/Spool) Transaction Type Dialog Steps Total DB Time in % DB Time in Total 45855 100,0 59,6 RSAL_BATCH_TOOL_DISPATCHING BTC 168 32,5 5289,3 RSPROCESS BTC 235 26,2 3045,8 SAPRSLOG BTC 7 13,5 52529,4 RSPO1043 BTC 14 6,5 12693,6 RSBTCPRIDEL BTC 28 5,9 5796,1 (BATCH) BTC 18824 4,8 7,0 SBIE0001 BTC 15 3,0 5551,7 RSBTCRTE BTC 8541 2,0 6,5 RSBATCH_EXECUTE_PROZESS BTC 235 1,9 218,8 RSBTCDEL BTC 14 1,2 2334,1 5 Workload Distribution BWP Rating The performance of your system was analyzed with respect to workload distribution. We did not detect any major proble that could affect the performance of your SAP System. Check Workload by Application Module DB Load Profile 5.1 Workload by Application Module The following diagra 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 progra that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the "not-assigned" category. Customer progra, industry solutions, and third-party add-on developments fall into this category. Module CPU Time in % BC 69,3 BC-CCM 16,6 Not Assigned 10,5 BW 3,6

Module DB Time in % BC 51,0 Not Assigned 22,7 BC-CCM 13,2 BW 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:00-06:00 and 21:00-24:00. By comparing the load profiles for dialog and background activity, you can get an overview of the volume 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 Syste. 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. Outgoing function call Calls Total call time, s Average call time, Bytes sent Bytes received ARFC_DEST_SHIP 2485 1703,95 686 32690616 479605 RSAP_TRFC_SEND 40 1522,98 38074 2887277764 11000 QDEST_RUN_DESTINATION 370 1232,70 3332 1477582 713452 ARFC_RUN_NOWAIT 3528 711,83 202 3575180 5080402 IDOC_START_INBOUND 5100 351,73 69 44424612 3988785 SET_SLD_DATA 14 293,24 20945 56938 52962

Outgoing function call Calls Total call time, s Average call time, Bytes sent Bytes received RFC_PING 12604 253,38 20 5251896 5545556 /BDL/_REQUEST_DATA_TASK 2 118,28 59138 560 576 /BDL/_DO_GENERATION 5 108,63 21726 11084 730 Incoming function call Calls Total call time, s Average call time, Bytes sent Bytes received ARFC_DEST_SHIP 546 2318,73 4247 35705 35642084 RSAR_TRFC_DATA_RECEIVED 118 2310,36 19579 52005284 52014606 RSAP_TRFC_SEND 40 1433,09 35827 25560 2887276324 QDEST_RUN 178 1241,05 6972 0 67012 QDEST_RUN_DESTINATION 742 1232,91 1662 852138 2931820 ARFC_RUN_NOWAIT 2445 676,55 277 6008340 2390714 ARFC_DEST_SHIP 4776 481,26 101 496203 13008646 IDOC_INBOUND_ASYNCHRONOUS 5121 456,44 89 2772235 4609614 IDOC_START_INBOUND 2550 323,41 127 4916985 22110306 6 SAP System Operating BWP Your system was analyzed with respect to daily operation proble. We did not detect any major proble 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 proble. 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 Quantity of Dumps 19.09.2011 2 20.09.2011 0 21.09.2011 0 22.09.2011 0 23.09.2011 0 24.09.2011 0 25.09.2011 0 26.09.2011 1 Name of runtime Error(s) Total of User Server (e.g.) Error(s) (e.g.) Date (e.g.) Time (e.g.) CONVT_NO_NUMBER 1 Metis_BWP_00 AEPEX_TB 19.09.2011 04:47:08 CALL_FUNCTION_CONFLICT_LENG 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 proble 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. Server Max. CPU load [%] Date Rating RAM [MB] Max. Paging [% of RAM] Date Rating Metis 3 20.09.2011 32767 0 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 RAM [MB] Max. Pages Out / s Hour Date Rating Metis Windows Server 2003 on x86_64 32767 803 12 23.09.2011 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 proble. No missing indexes were found on system BWP. 7.3.1 Largest Tables The following table shows the largest tables currently in the database. Table Name Data (kb) Reserved (data + indexes) kb Used (data + indexes) kb Rows Modified Rows /BIC/B0000334000 7174160 9671096 9669120 12407825 1586208 /BIC/B0000544000 6678080 6782912 6781376 29260633 4016167 /BIC/B0000337000 4601736 5295712 5294664 4026269 502251 /BIC/B0000335000 4287288 4966064 4965136 3751365 63037 /BIC/B0000332000 2842408 4924712 4923328 12435358 1559375 RSDDSTATLOGGING 3281904 3340296 3339392 21549506 22103046 WBCROSSGT 1194976 2902416 2900560 10682388 9877 /BIC/B0000479000 2291176 2328120 2327368 16896756 916600 EDI40 2170088 2193720 2193080 1262607 115731 RSMONMESS 632504 2065040 2062488 2237647 235701 7.3.2 Service Pack Microsoft releases updated SQL Server builds, known as Service Packs, at regular intervals. For certain proble 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 4053 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 Page locking Rating EDI40 VBMOD VBHDR ARFCSDATA VBDATA EDIDS EDIDC ARFCRDATA D010TAB 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 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). Diagra 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 diagra 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 diagra 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 Load (%) DB02_MSS 34.6

Transaction Code Load (%) ST06 14.4 DB12_MSS 12.5 SESSION_MANAGER 11.0 RSPCM 7.2 8.3 System Operation The following diagram or table shows important KPIs for system operation. Note: The column 'Availability' is filled for syste with SAP Basis 4.6 and higher. 8.4 Hardware Capacity