557_Anexo_1[1]

Service Report

Processed on SAP Solution Manager SMA Service Tool 701_2008_2 Support Package 4 Analysis from 25.10.2010 <dat_dummy> Session No. 0010000007081 Until 31.10.2010 Installation No. 0020128815 <Watermark>

SAP EarlyWatch Alert SAP System ID PRF SAP Component SAP R/3 Enterprise

Release 47X200 Status PRODUCTIVE DB System ORACLE 9.2.0.8

Service Summary

EarlyWatch Alert, 0020128815 -, 25.10.2010 - 31.10.2010 2

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.

SECTION OVERVIEW

Rating Checked Area

System Performance

Workload Distribution

SAP System Operating

Database Settings

Database Administration

Security

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 01.11.2010 04:04:19. This took 4 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".

OVERVIEW OF ALERT MESSAGES

Priority Description

Very high We found relevant security-related SAP HotNews which are not applied.

2 Performance Indicators for PRF The following table shows the relevant performance indicators in various system areas.

Area Indicators Value Trend

System Performance Active Users 0 - Avg. Response Time in Dialog Task 0 ms - Max. Dialog Steps per Hour 0 - Avg. Response Time at Peak Dialog Hour 0 ms - Avg. Availability per Week 94 % steady

Performance Indicators for PRF


Area Indicators Value Trend

Database Performance Avg. DB Request Time in Dialog Task 0 ms - Avg. DB Request Time in Update Task 0 ms - Database Space Management DB Size 91.70 GB steady Last Month DB Growth 0.99 GB down

System Configuration


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 No. of CPUs Memory in MB

CHLEFE03SA01 Windows Server 2003 on x86_32 4 5120

3.2 Software Configuration

3.2.1 Database DATABASE SYSTEM

Database Server Database System Current Version

CHLEFE03SA01 ORACLE 9.2.0.8

3.2.2 SAP Application Release: Maintenance Phases SAP Product SAP Product

Version End of Mainstream

Maintenance End of Extended

Maintenance

SAP R/3 Enterprise

47X200 31.03.2009 31.03.2012

Your system &YSAP-R3_SID& is running on <(>&<)>YSAP-SAP_PRODUCT& <(>&<)>YSAP-SAP_PRODUCT_VERSION&. Mainstream maintenance for <(>&<)>YSAP-SAP_PRODUCT& <(>&<)>YSAP-SAP_PRODUCT_VERSION& ended on 31.03.2009.

Recommendation: We recommend that you upgrade your system. For more information, see SAP Service Marketplace at service.sap.com/upgrade. If you decide to continue using the current release, SAP offers extended maintenance for <(>&<)>YSAP-SAP_PRODUCT& <(>&<)>YSAP-SAP_PRODUCT_VERSION& from 01.04.2009 to 31.03.2012. For SAP Enterprise Support customers, SAP offers an additional year of extended maintenance for <(>&<)>YSAP-SAP_PRODUCT& <(>&<)>YSAP-SAP_PRODUCT_VERSION& to 31.03.2013. If you are an SAP Enterprise Support customer, your system will be covered by extended maintenance until that date and will only be in customer-specific maintenance as of 01.04.2013. For more information about the SAP maintenance strategy and ordering extended maintenance, see SAP Service Marketplace at service.sap.com/maintenance.

http://www.service.sap.com/upgrade�

http://www.service.sap.com/maintenance�



3.2.3 Support Package Maintenance SUPPORT PACKAGES

SAP Component

SAP Component Version

Patch Level

Latest Avail. Patch Level

Support Package

Component Description

ABA_PLUS 100 9 21 SAPKGPBA09 SAP R/3 Enterprise Application Basis Plug-In

EA-APPL 200 7 19 SAPKGPAB07 SAP R/3 Enterprise PLM, SCM, Finance

EA-DFPS 200 7 19 SAPKGPDB07 SAP R/3 Enterprise Defense Forces & Public Security

EA-FINSERV 200 7 19 SAPKGPFB07 SAP R/3 Enterprise Financial Services

EA-GLTRADE 200 7 19 SAPKGPGB07 SAP R/3 Enterprise Global Trade

EA-HR 200 11 93 SAPKGPHB11 SAP R/3 Enterprise Human Resources

EA-IPPE 200 13 30 SAPKGPIB13 SAP R/3 Enterprise Integrated Product and Process Engineering

EA-PS 200 7 19 SAPKGPPB07 SAP R/3 Enterprise Public Services

EA-RETAIL 200 7 19 SAPKGPRB07 SAP R/3 Enterprise Retail PI 2004_1_470 1 17 SAPKIPZI51 SAP R/3 Plug-In for SAP APO,

SAP BBP, SAP BW, SAP CRM PI_BASIS 2004_1_620 3 10 SAPKIPYI53 SAP R/3 Basis Plug-In SAP_ABA 620 41 69 SAPKA62041 SAP Application Basis SAP_APPL 470 21 34 SAPKH47021 SAP R/3 Standard SAP_BASIS 620 41 69 SAPKB62041 SAP Basis Component SAP_HR 470 30 112 SAPKE47030 SAP R/3 Standard HR ST-A/PI 01M_R3_470 0 SAPKITAR5E SAP Service Tools for

Applications Plug-In ST-PI 2008_1_620 1 3 SAPKITLRB1 SAP Solution Tools Plug-In

3.2.4 SAP Kernel Release You are running SAP Kernel Release 640, patch level 129.

3.2.4.1 Issues with current SAP Kernel You may experience problems with your SAP Kernel release. SAP tests all SAP Kernels released. However, your patch level has been found to be unstable in some cases and is therefore not recommended. For more information, see the release information for each SAP Kernel patch available on SAP Service Marketplace. For more information about issues concerning your current SAP Kernel, see the SAP Notes in the table below.

Recommendation: If the SAP Kernel shipped with the latest Support Package Stack for your product has the same problem as listed below, use a more recent SAP Kernel available in section Patches of SAP Service Marketplace.

SAP Note Number Short Text Risk

http://service.sap.com/~IRON/FM/011000358700000431401997/0981919E All work processes are used by SAPSYS, semaphore 39

http://service.sap.com/~IRON/FM/011000358700000431401997/1150058E Incomplete update records http://service.sap.com/~IRON/FM/011000358700000431401997/1076804E Incomplete update records

http://service.sap.com/~IRON/FM/011000358700000431401997/0981919E�





3.2.4.2 Kernel Supportability SAP Note

Number Description

http://service.sap.com/~IRON/FM/011000358700000431

401997/1106096E

EX2 Kernels: Extended Kernel Maintenance

3.2.4.3 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

0001150840 0010 XX-SER-LAS System measurement: Unlocking the USMM 0001096810 0002 FI-AP-AP-D FBL1/FBL3/FBL5/FK10/FS10/FD10: Special fields not filled 0000883385 0002 MM-PUR-OA-CON ME32K: Runtime error DBIF_RSQL_SQL_ERROR 0000847561 0001 BC-SRV-QUE InfoSet query: LOAD_PROGRAM_NOT_FOUND, program " " 0000802245 0005 FI-GL-GL-I RFBIBL00: XSIWE cannot be transferred by batch input 0000766392 0003 MM-IM-GI-GI CONVT_NO_NUMBER subsequent note 710763 0000756346 0006 MM-PUR-PO-GUI V1060 when you create purchase orders 0000747834 0002 FI-AA-AA-E SG105 with RAPERB00, RAPERB2000 or RAPOST2000 0000735321 0003 FI-AA-AA-A AS01: Asset class search help displays incorrect entries 0000666628 0003 FI-AA-AA-C RAPERB00/RAPERB2000: Incorrect translation date 0000441215 0004 BC-SEC-USR-ADM SU01: incorrect user SPACE

3.3 Service Preparation System PRF 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, particularly 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.








http://service.sap.com/sp-stacks�

http://service.sap.com/patches�



3.3.1 Service Preparation Check (RTCCTOOL) Before we can deliver any services, the latest version of the SAP Service tools must be available in your system. Report RTCCTOOL was last run on 01.11.2010. During the check, the tool detected issues that were rated RED.

Overall Status SAP Note Title Tool Status Manual Status

69455 Switch on digital content verifi MISSING

69455 ST-A/PI Addon Supportpackage SP0 MISSING

1443908 y workload missing MISSING

539977 Addon ST-PI 2008_1_620 IMPLEMENTED

539977 ST-PI Support Packages MISSING IMPLEMENTED

12103 Collectors and TCOLL IMPLEMENTED

207223 EWAlert setup IMPLEMENTED

69455 Addon ST-A/PI 01M_R3_470 IMPLEMENTED

69455 Proc. after addon impl. IMPLEMENTED

Recommendation: ST-A/PI Addon Supportpackage SP0 Addon supportpackage SP01 for ST-A/PI 01M_R3_470 for R/3 Enterprise 470 From http://service.sap.com/supporttools->ST-A/PI->Support packages-> ST-A/PI 01M_R3_470 download patch SAPKITAR5F. For basis >=700 use the Maintenance optimizer to release the download. Upload from frontend to transaction SPAM, define a queue and import. Switch on digital content verifi Switch on Digital content verification for recommendations of SAP Service prep. check (RTCCTOOL) or Security Notes Check (RSECNOTE) From the menu choose "Goto->Digital signatures" and press "Activate". y workload missing Weekly workload data are missing in ST03N as well as EarlyWatch/EWAlert as of 22th Feb. 2010 on SAP basis <= 640 [basis 640 to lvl 25, basis 620 to lvl 67, 46C to lvl 59, 40B-46B, 46D-610] Implement the correction instruction from note 1443908. Future weeks will then be calculated and kept properly again. [The missing weeks could also be recalculated using a program attached to the note. But this takes more effort].

3.3.2 Errors in Data Collection The following exceptions were raised during data collection:

Host Function Name Exception

SAPR3EFE SAPWL_WORKLOAD_GET_SUMMARY_I_W NO_DATA_FOUND SAPR3EFE SAPWL_RFC_AGGREGATION_INST NO_DATA_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.3 Workload Monitor (ST03) Instance Comment

SAPR3EFE 00 No workload data available

Recommendation: See SAP Note 12103. If required, open a message on component BC-CCM-MON-TUN.

3.3.4 SAP Application Servers The following information can be found in transaction SM51:



SAP Application Server SM51 Host Name

SAPR3EFE_PRF_00 SAPR3EFE

Performance Overview PRF


4 Performance Overview PRF

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:

Task type

Dialog 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

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 0 0 0 0

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.

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.

Workload Distribution PRF


5 Workload Distribution PRF

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.

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.

SAP System Operating PRF


6 SAP System Operating PRF

The daily operation of your system was analyzed. We detected some problems that may impair system operation and stability.

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 Table Reorganization When analyzing your database, we detected large or rapidly growing tables or indexes.

Recommendation: Implement the SAP Notes listed below to reduce the size of some of these tables or indexes.

Background: For more information about SAP Data Volume Management, refer to SAP Service Marketplace at: service.sap.com/dvm

Table / Index Name Size of Table / Index [MByte] Recommended SAP Note

TST03 2886,0 48400, 130978, 16083

6.3 Transports Transports were not found in the period analyzed.

6.4 Program Errors (ABAP Dumps) 8 ABAP dumps have been recorded in your system in the period 26.10.2010 to 29.10.2010. 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

26.10.2010 6 27.10.2010 0 28.10.2010 1 29.10.2010 1

Name of runtime Error(s) Total of Error(s) Server (e.g.) User (e.g.) Date (e.g.) Time (e.g.)

MESSAGE_TYPE_X 3 SAPR3EFE EFEMAA 26.10.2010 09:25:06 RAISE_EXCEPTION 3 SAPR3EFE EFERLW 26.10.2010 19:12:41 CALL_FUNCTION_NOT_FOUND 1 SAPR3EFE WF-BATCH 28.10.2010 10:26:13 CALL_FUNCTION_OPEN_ERROR 1 SAPR3EFE CVALENCIA 29.10.2010 11:37:06

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.

Security


7 Security

Critical security issues were found in your system. See the information in the following sections.

Rating Check

Security-related SAP Notes

Users with Critical Authorizations

7.1 Security-related SAP Notes Vulnerabilities exist in this system that can be resolved easily. We found relevant security-related SAP HotNews that have not been applied.

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 Notes that can be implemented easily, run the tool RSECNOTE in transaction ST13. It provides a detailed list of the vulnerabilities discovered and the corresponding SAP Notes for correction. More security issues may exist. For more information, refer to SAP Note 888889.

7.2 Users with Critical Authorizations For more information about the following check results, refer to SAP Note 863362.

Recommendation: Depending on your environment, review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations. You can use the User Information System (transaction SUIM) to check the results. For each check, you can review the roles or profiles that include the authorization objects listed in the corresponding chapter.

7.2.1 Users Authorized to Display all Tables Unauthorized access to sensitive data is possible if too many users are granted authorization. The number of users with this authorization is stated for each client.

Client No. of Users Having This Authorization No. of Valid Users Rating

001 2 3 300 23 143

Authorization objects:

Object 1: S_TCODE with TCD=SE16, TCD=SE16N, TCD=SE17, TCD=SM30, or TCD=SM31

Object 2: S_TABU_DIS with ACTVT = 03 or 02 and DICBERCLS = *

7.2.2 Users Authorized to start all Reports This authorization allows critical functions and reports without authorization checks to be executed. The number of users with this authorization is stated for each client.


001 2 3

https://service.sap.com/securitynotes�

https://service.sap.com/sap/support/notes/888889�


Security



300 24 143


Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38

Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*

7.2.3 Users Authorized to Display Other Users Spool Request This authorization allows unauthorized access to sensitive data contained in spool requests. The number of users with this authorization is stated for each client.


001 2 3 300 17 143


Object 1: S_TCODE with TCD = SP01 or SP01O

Object 2: S_ADMI_FCD with S_ADMI_FCD = SP01 or SP0R

Object 3: S_SPO_ACT with SPOACTION = BASE and DISP and SPOAUTH = * or __USER__

7.2.4 Users Authorized to Administer RFC Connections If too many users have this authorization, two issues may arise: - Unauthorized access to other systems - Interfaces malfunction when invalid connection data is entered The number of users with this authorization is stated for each client.


001 2 3 300 16 143


Object 1: S_TCODE with TCD=SM59

Object 2: S_ADMI_FCD with S_ADMI_FCD = NADM

Hardware Capacity


8 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

CHLEFE03SA01 5 26.10.2010 5120 0

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

CHLEFE03SA01 Windows Server 2003 on x86_32

5120 480 11 26.10.2010

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



Database Settings


9 Database Settings

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

Rating Check

Missing Indexes

Database Key Performance Indicators

Setup of the Temporary Tablespace

Database Parameters

Optimizer Statistics

9.1 Load per user The following table provides an overview of the load caused by different database users. The following information is listed for every database user: (A) Percentage of statements executed (B) Number of block reads from disk (indicative of the I/O load caused by this database user) (C) Number of buffers accessed (D) Number of records returned as obtained from the shared pool (Oracle view V$SQL) at the time of the download The first row ('Total') indicates the total of (A), (B), (C), and (D) for all user names.

LOAD PER USER (PERCENTAGES)

User Name Executions Disk Reads Buffer Gets Rows Processed

total (not a user name!) 35210231 146885536 3038770835 111294578 OPS$CHLEFE03SA01\SAPSE 0% 0% 0% 0% PATROL 5% 31% 33% 1% SAPR3 95% 69% 67% 99%

9.2 Database Parameters for PRF 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. 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.

9.2.0.1 Database Parameters

Database Settings


To carry out an automatic check of all configured Oracle parameters, refer to SAP Note 1171650. There are two .TXT files attached to this SAP Note. One file is for Oracle releases up to and including 10.1, and the other is for releases as of 10.2. Each file includes an SQL statement that automatically checks whether the current parameter settings are correct (depending on the Oracle release, patch set, and/or system type). For instructions about using each SQL statement, refer to the SAP Note.

SAP NOTE FOR ORACLE PARAMETER SETTINGS

SAP Note Number

Description

124361 Oracle DB parameters for R/3 Release >= 4.x 1238487 Update of threshold values of database system check 1171650 Automated Oracle DB parameter check

Parameters Description Current value Recommended

value

_b_tree_bitmap_plans Enable use of bitmap plans for tables w. only B-tree indexes

Please check SAP note 0124361

_push_join_predicate Enable pushing join predicate inside a view


_sort_elimination_cost_ratio Efficient index with FIRST_ROWS and ORDER BY


_optimizer_join_sel_sanity_check

Checks the order of join conditions Please check SAP note 0124361

_optimizer_or_expansion control or expansion approach used


filesystemio_options Filesystem I/O options Please check SAP note 0124361

Parameters Description Current value Recommended value

hash_join_enabled Enables the using of hash-joins TRUE Please check SAP note 0124361

log_checkpoint_interval Checkpoint frequency as number of redo log blocks written

300000 Please check SAP note 0124361

log_checkpoint_timeout Checkpoint frequency as time interval in seconds


log_checkpoints_to_alert Checkpoints logged in alert file FALSE Please check SAP note 0124361

optimizer_index_cost_adj Percentage of the calculated index costs


shared_pool_reserved_size Part of Shared Pool for large statements


star_transformation_enabled Enables the star transformation functionality

true Please check SAP note 0124361

_optim_peek_user_binds Bind value peeking Please check SAP note 0124361

_table_lookup_prefetch_size Table lookup prefetch vector size Please check SAP note 0124361

9.2.0.2 Parameter EVENT 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 be activated on request only. When they are no longer needed, they should be removed. However, it might be necessary 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 The following table lists events that may have to be activated. Please check the mentioned SAP Notes for details.

Event SAP Note number for Event Description

10183 128648 Other access path than expected is used 10191 128221 Increased memory consumption with Oracle >8.0.X 10027 596420 System downtime during deadlock (ORA-60) 10028 596420 System downtime during deadlock (ORA-60) 38068 176754 Problems with CBO and RBO 38043 960633 Merge Join Cartesian in complex join

10 Database Administration

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

10.1 Database Growth The following figure shows the development of the size of your database in GB.

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



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

30.11.2009 82,45 0,71 31.12.2009 83,46 1,01 31.01.2010 84,40 0,94 28.02.2010 85,77 1,37 31.03.2010 86,85 1,08 30.04.2010 87,26 0,41 31.05.2010 87,77 0,51 30.06.2010 88,30 0,53 31.07.2010 88,66 0,36 31.08.2010 89,45 0,79 30.09.2010 90,71 1,26 31.10.2010 91,70 0,99

10.2 Check brconnect -f check (sapdba -check) schedule When we checked the brconnect -f check schedule, we detected that it is not scheduled as recommended For an analysis of the 01.11.2010, we noticed the following problems: Brconnect -f check is not scheduled at all. BRCONNECT with the option -f check (or SAPDBA with the option -check) offers you an easy way to check for database problems specific to the SAP environment.

Recommendation: Schedule BRCONNECT -f check (or SAPDBA -check) to run daily during periods of low system activity, using either the DBA Planning Calendar (transaction DB13) or by entering command BRCONNECT -f check (or sapdba -check) at the command prompt. After each run, check the log information written by the BRCONNECT -f check (SAPDBA -check). Check SAP Note 403704 for information about SAPDBA and BRCONNECT.

10.3 Oracle Release Standard maintenance for Oracle Version 9.2 ended on July 31, 2007 (see SAP Note 925871). The chargeable phase of Oracle extended support began on July 31st, 2008 for Oracle Version 9.2 (see SAP Note 1110995).



We recommend that you install the latest Oracle patch set as soon as possible (see SAP Note 415900). The latest patch set is 9.2.0.8. See SAP Note 539921. Note that in addition to the patch set, further bug fixes may be available and recommended. See the following SAP Notes:

Patch set SAP Note number Description

9.2.0.8 992261 Optimizer merge fix for Oracle 9.2.0.8

Database server load from expensive SQL statements - PRF


11 Database server load from expensive SQL statements - PRF

The expensive SQL statements identified did not lead to performance problems. For reference, the load overview is listed in the table below and further details of the most expensive statements are included at the end of the section. For more information about the rating of this check, see SAP Note 551646.

DATABASE LOAD FROM EXPENSIVE STATEMENTS

Rating Buffer Load [%] Disk Load [%] CPU Load [%]

31 62 21 The table above shows the cumulative load of the problematic statements identified. If the database was inactive for at least one day before the analysis was performed, the information given may not be accurate.

Note: The table rating is independent of the section rating, as described in SAP Note 551646. If the table rating is RED, expensive SQL statements were found that cause a high load on your SAP system. If the table rating is YELLOW, some expensive SQL statements were found. If the table rating is GREEN, the analysis of your system's SQL statement cache found no significant problems. The following table lists the load of each expensive SQL statement individually. The load of the statement is evaluated against the current load in the database and the total load since startup. A more technical explanation is given in SAP Note 551646. The database administrator must conduct a detailed analysis, or you may prefer to order an EarlyWatch session with a focus on SQL statement tuning.

Note: If an object name in this table contains the character "/", it may be a statement to a join. If an object does not exist in the ABAP dictionary (transaction SE12) with the listed object name, check for each part of the join (items separated by "/").

11.1 Analysis of DB SQL CACHE EXPENSIVE SQL STATEMENTS OVERVIEW

Object Name CPU Load [%]

I/O Load [%]

Elapsed Time [%]

Executions Records Processed

BEGINP$POPULATE_CONT 30 30 12 1900 1900 SWWWIHEAD 1 15 3 326 0 SWFREVTLOG 0 5 2 245 245 SWWWIHEAD 0 7 2 326 0 SWFREVTLOG 0 5 2 245 245

11.1.1 Access on BEGINP$POPULATE_CONT Statement Data:

CACHE STATISTICS

Object Type Total Executions Disk Reads Elapsed Time Buffer Gets Records Processed

TABLE 1900 44698731 16295948 928617380 1900

begin P$POPULATE_CONTAINERS(null,null); end;& Execution Plan



SQL Scripts This statement is an expensive SQL script. Because the contents of such a script are not visible in the SQL cache, we cannot analyze this statement in detail. Recommendation: Please check if: a) The script has to be run at all. b) The script can be run less frequently. c) The script can be tuned so that it consumes less database resources.

11.1.2 Access on SWWWIHEAD Statement Data:

CACHE STATISTICS


TABLE 326 21932167 4056850 21955739 0

SELECT "WI_ID" FROM "SWWWIHEAD" WHERE "CLIENT" = :A0 AND "WI_TYPE" IN ( :A1 , :A2 , :A3 , :A4 ) AND "WI_STAT" IN ( :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A11 ) AND "CHECK_STAT" = :A12& Execution Plan (From: V$SQL_PLAN addr= AEFF30C8 hash= 1845066171 ) SELECT STATEMENT Estimated Costs= 7.945 Estimated Rows= 0 Optimizer: CHOOSE 1 TABLE ACCESS FULL SWWWIHEAD Estimated Costs= 7.945 Estimated Rows= 1 Filter predicates: "CLIENT"=:A0 AND ("WI_TYPE"=:A1 OR "WI_TYPE"=:A2 OR "WI_TYPE"=:A3 OR "WI_TY PE"=:A4) AND ("WI_STAT"=:A5 OR "WI_STAT"=:A6 OR "WI_STAT"=:A7 OR "WI_STAT"= :A8 OR "WI_STAT"=:A9 OR "WI_STAT"=:A10 OR "WI_STAT"=:A11) AND "CHECK_STAT"= :A12 Optimizer: ANALYZED Estim. Bytes: 26 Estim. CPU-Costs = 0 Estim. IO-Costs = 7.945

Program Data:

ORIGIN OF ABAP CODING

Program Name Line Created By Last Changed By Last Changed On

RSWWCOND 156 SAP SAP 18.05.2004

000155 * Note 684130 000156 select wi_id into corresponding fields of table 000157 lt_swwwihead 000158 from swwwihead where 000159 wi_type in type and 000160 wi_stat in stat and 000161 wi_rh_task in task and 000162 check_stat eq '01'.

11.1.3 Access on SWFREVTLOG Statement Data:

CACHE STATISTICS


TABLE 245 7696949 2544757 8333899 245

SELECT MAX( "TIMESTAMP" ) FROM "SWFREVTLOG"



WHERE "CLIENT" = :A0 AND "EVENT_ID" = :A1 AND "RECTYPE" = :A2 AND "RECKEY" = :A3 AND "ERROR" = :A4& Execution Plan (From: V$SQL_PLAN addr= AEFF30C8 hash= 1845066171 ) SELECT STATEMENT Estimated Costs= 4.174 Estimated Rows= 0 Optimizer: CHOOSE 2 SORT AGGREGATE Estimated Costs= 0 Estimated Rows= 1 Estim. Bytes: 47 1 TABLE ACCESS FULL SWFREVTLOG Estimated Costs= 4.174 Estimated Rows= 1 Filter predicates: "CLIENT"=:A0 AND "EVENT_ID"=:A1 AND "RECTYPE"=:A2 AND "RECKEY"=:A3 AND "ERR OR"=:A4 Optimizer: ANALYZED Estim. Bytes: 47 Estim. CPU-Costs = 0 Estim. IO-Costs = 4.174

Program Data:



CL_SWF_EVT_LOG================CM007 10 SAP SAP 23.02.2001

000010 SELECT MAX( timestamp ) FROM swfrevtlog INTO l_timestamp 000011 WHERE event_id = im_event_id 000012 AND rectype = im_rectype 000013 AND reckey = space 000014 AND error = 0 .

11.1.4 Access on SWWWIHEAD Statement Data:

CACHE STATISTICS


TABLE 326 9617195 2378295 3955583 0

SELECT "WI_ID" FROM "SWWWIHEAD" WHERE "CLIENT" = :A0 AND "WI_TYPE" IN ( :A1 , :A2 , :A3 , :A4 ) AND "WI_STAT" = :A5& Execution Plan (From: V$SQL_PLAN addr= AEFF30C8 hash= 1845066171 ) SELECT STATEMENT Estimated Costs= 7.021 Estimated Rows= 0 Optimizer: CHOOSE 5 VIEW Estimated Costs= 7.021 Estimated Rows= 203.552 Filter predicates: "CLIENT"=:A0 AND ("WI_TYPE"=:A1 OR "WI_TYPE"=:A2 OR "WI_TYPE"=:A3 OR "WI_TY PE"=:A4) AND "WI_STAT"=:A5 Estim. Bytes: 5.088.800 4 HASH JOIN Estimated Costs= 0 Estimated Rows= 203.552 Access predicates: ROWID=ROWID Estim. Bytes: 5.088.800 2 INLIST ITERATOR 1 INDEX RANGE SCAN SWWWIHEAD~C Estimated Costs= 1.924 Estimated Rows= 203.552 Access predicates: "WI_TYPE"=:A1 OR "WI_TYPE"=:A2 OR "WI_TYPE"=:A3 OR "WI_TYPE"=:A4 Search Columns: 1 Optimizer: ANALYZED Estim. Bytes: 5.088.800 Estim. CPU-Costs = 0 Estim. IO-Costs = 1.924 3 INDEX RANGE SCAN SWWWIHEAD~0 Estimated Costs= 1.924 Estimated Rows= 203.552 Access predicates: "CLIENT"=:A0 Search Columns: 1 Optimizer: ANALYZED Estim. Bytes: 5.088.800 Estim. CPU-Costs = 0 Estim. IO-Costs = 1.924

Program Data:





RSWWCOND 211 SAP SAP 18.05.2004

000210 * Note 684130 000211 select wi_id into corresponding fields of table lt_swwwihead 000212 from swwwihead 000213 where 000214 wi_type in type and 000215 wi_stat eq swfco_wi_status_checked and 000216 wi_rh_task in task.

11.1.5 Access on SWFREVTLOG Statement Data:

CACHE STATISTICS


TABLE 245 7871260 2193854 8334151 245

UPDATE "SWFREVTLOG" SET "RECCATEG" = :A0 , "RECTYPEID" = :A1 , "RECKEY" = :A2 WHERE "CLIENT" = :A3 AND "EVENT_ID" = :A4 AND "RECTYPE" = :A5 AND "RECKEY" = :A6 AND "ERROR" = :A7 AND "TIMESTAMP" = :A8& Execution Plan (From: V$SQL_PLAN addr= AEFF30C8 hash= 1845066171 ) UPDATE STATEMENT Estimated Costs= 4.174 Estimated Rows= 0 Optimizer: CHOOSE 2 UPDATE 1 TABLE ACCESS FULL SWFREVTLOG Estimated Costs= 4.174 Estimated Rows= 1 Filter predicates: "CLIENT"=:A3 AND "EVENT_ID"=:A4 AND "RECTYPE"=:A5 AND "RECKEY"=:A6 AND "ERR OR"=:A7 AND "TIMESTAMP"=:A8 Optimizer: ANALYZED Estim. Bytes: 51 Estim. CPU-Costs = 0 Estim. IO-Costs = 4.174

Program Data:



CL_SWF_EVT_LOG================CM007 29 SAP SAP 23.02.2001

000027 * end of note: 642184 000028 000029 UPDATE swfrevtlog SET reccateg = im_handler_por-catid 000030 rectypeid = im_handler_por-typeid 000031 reckey = im_handler_por-instid 000032 WHERE event_id = im_event_id 000033 AND rectype = l_rectype "note: 642184 000034 * AND rectype = im_rectype "note: 642184 000035 AND reckey = space 000036 AND error = 0 000037 AND timestamp = l_timestamp.

Trend Analysis


12 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. In this report, historical data is taken from workload monitor ST03 directly.

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

Historical data for "Transaction Activity" is obtained directly from ST03 transaction data.

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.

Trend Analysis


12.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. Historical data for "System Performance" is obtained directly from ST03 transaction data.

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.

Trend Analysis


The "Transaction Code" table below shows the load percentage caused by the top 5 transactions.

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

Trend Analysis


12.4 Hardware Capacity

557_Anexo_1[1]

Documents

Transcript of 557_Anexo_1[1]