Early Watch Report
Early Watch Report
Early Watch Report
Status DB System
02.08.2010 08.08.2010
3000000003055 0020297356
Service Summary
1 Service Summary
During this EarlyWatch Alert Session, we detected issues that could potentially affect your system. We recommend that you take corrective action as soon as possible.
Note: All recommendations provided in this report are based on our general experience. We advise that you test our recommendations before using them in your production system. Note that EarlyWatch Alert is an automatic service.
CHECK OVERVIEW Topic Rating Topic System Configuration Hardware Configuration Software Configuration Service Preparation System Performance Workload Distribution Workload by Application Module DB Load Profile SAP System Operating Availability based on Collector Protocols Program Errors (ABAP Dumps) Update Errors Table Reorganization Database Performance Database Parameters Database Administration Freespace in Tablespaces Software Change Management Java Performance Data Availability of Java Performance Data Subtopic Rating Subtopic
The table below lists all of the checks that are not performed automatically.
Rating Not Performed Checks Database Growth Missing Indexes SAP Kernel Release
Checks were not performed. This is most likely due to a problem with data collection or transfer. The overall report has a yellow rating due to these unperformed checks.
EarlyWatch Alert, 0020297356 - PDI, 02.08.2010 - 08.08.2010 2
Service Summary
Recommendation: Check the "log" for this session in the Service Data Control Center (call transaction SDCC or the new SDCCN in your system). If an error is listed, perform the Service Preparation Check. You can execute this check in the SDCC by choosing "Information -> Service prep. check", or by creating a new "Service Preparation Check" task in SDCCN. If the check displays a missing SAP Note, implement this Note.
Service Summary
4 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs). Diagrams are built week by week once the EarlyWatch Alert service is activated. In this report, historical data for "Transaction Activity", "System Performance", and "Database Performance" is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions. In this section, "weeks" are from Monday to Sunday. The date displayed is Sunday at the end of the week.
5 System Activity
The following diagrams show the system activity over time. The "Transaction Activity" diagram below depicts transaction activity in the system over time. - Total Activity: Transaction steps performed each week (in thousands) - Dialog Activity: Transaction steps performed in dialog task each week (in thousands) - Peak Activity: Transaction steps (in thousands) during the peak hour; this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week. (Peak Activity is absent if "Activity Data" is taken from ST03 data directly). Historical data for "Transaction Activity" is obtained from the Workload Monitor (ST03).
The "User Activity" diagram below shows the user activity on the system over time. - Total Users: Total users that logged on in one week.
EarlyWatch Alert, 0020297356 - PDI, 02.08.2010 - 08.08.2010 4
Service Summary
- Active Users: Users who performed more than 400 transaction steps in one week.
6 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. Historical data for "System Performance" is obtained from the Workload Monitor (ST03).
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.
Service Summary
The "Transaction Code" table below shows the load percentage caused by the top 5 transactions.
7 Hardware Capacity
8 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.
Service Summary
10 Hardware Configuration
SERVER OVERVIEW Server netwprod Operating System No. of CPUs 0 Memory in MB 0
11 Software Configuration
12 Codepage Technology Support
It was not possible to detect whether you are using other codepage technologies in addition to Unicode. We support and fully recommend Unicode in systems involving multiple languages. As of SAP NetWeaver Release 7.0, Unicode is the only supported and available codepage technology. We can only ensure data consistency in installations with multiple languages if the entire system is based on Unicode. See SAP Note 838402 -> Attachments -> "Customer Letter" for information about our supported codepage technologies. Recommendation: If you are using a codepage technology other than Unicode, we recommend that you review our disclaimer, which you can find at: /unicode -> Unicode Media Library -> SAP ERP 6.0 and MDMP -> "Disclaimer: MDMP with SAP 6.0". For more information about how to migrate to Unicode completely, see the document "Roadmap: From MDMP to SAP ERP 6.0 Unicode", which you can find at the path above. If you are not using multiple languages, ignore this recommendation.
Service Summary
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).