Vous êtes sur la page 1sur 58

Service Report

SAP GoingLive OS/DB Migration Check Analysis Session

SAP System ID SAP Component Release DB System Operating System Customer

RPB SAP NetWeaver 7.0 DB2 for z/OS 8.1.5 zOS / Linux ORACLE 10.2.0.4

HP-UX / Linux

Renfe Operadora 28036 Madrid

Service Center Telephone Fax

SAP Support, Dublin +353 1 467 4141 +353 1 467 4100

Date of Session Date of Report Author

13.04.2010 <dat_dummy> 13.04.2010 David Fry david.fry@sap.com


<Watermark>

Session No. Installation No. Customer No.

8000000000505 20267072 746694

Service Summary

1 Service Summary
During this GoingLive session, it was determined that your system could be improved in at least one of the following ways: - Prevent performance problems in your core business transactions - Improve data security You should take corrective action as soon as possible. If you require further information, create a customer message on component SV-BO-BI or call your SAP Local Support organization.

Note:

The recommendations in this report are based on general experience only. You should test these recommendations before implementing them in your production system.

1.1 Summary
This report contains the findings and recommendations of the OS/DB Migration Analysis session performed on your SAP Netweaver BW 7.0 system. The purpose of this session was to perform a sizing estimate and provide parameter recommendations for your planned migration to Oracle 10.2.0.4 with a mix of HP-UX and Linux operating systems. Our contact for this session was Eva del Carmen Gonzlez Muina. During this session we performed a sizing estimate of your system which was based on the current workload on RPB along with the contents of the Quicksizer project AUGE. We recommend that you closely monitor the performance of your system after Go Live. See section 6 for more details. We have made numerous recommendations in this report to ensure that you system is configured correctly for your GoLive, for this reason we have rated this report Yellow. You should review, test and implement all database, Java and BW instance parameter recommendations outlined in this report. Also, please ensure that you are using the latest SAP kernel release available for your system. SAP EarlyWatch Alert is an important part of making sure your core business processes work. It is tool that monitors the essential administrative areas of SAP components and keeps you up to date on their performance and stability. SAP EarlyWatch Alert runs automatically to keep you informed, so you can react to issues proactively, before they become critical. Please ensure that it is scheduled to run on your system as outlined in section 12.1 of this report. With regards to database administration, please ensure that all Oracle statistics have been created. For more information please see section 9.1. Finally, please ensure that your backup strategy meets SAP standard minimum recommendations, which are outlined in section 10.1. The Action Plan below contains more information on findings from this session. Finally, if you would like further information, please create a customer message on component SV-BO-BI or call the numbers found on the cover page.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Service Summary

1.2 System Status RPB


Performance Overview Workload Distribution Hardware Capacity Hardware Capacity Forecast SAP System Operating Database Settings Database Administration SAP J2EE Engine Parameter Settings

1.3 Action Plan


Priority Action Description 1 Monitor the performance of your system closely after your Go Live. See section 6 for more details. 2 Review, test and implement all database, java and BW instance parameter recommedations outlined in this report. 2 Ensure that you are using the latest SAP kernel release available for your system. See section 13.3.1. 2 Ensure you are using the latest JVM versions available for your system. See sections 11.3.2.1 and 11.3.3.1 for more details. 2 Setup Earlywatch Alert to run weekly on RPB. See section 12.1 for more details. 2 Ensure all Oracle 10g database statistics are correctly maintained on your system. See section 9.1 for more details. 2 Ensure your backup strategy meets SAP standard minimum recommendations outlined in section 10.1. Priorities: 1 (very high), 2 (high), 3 (medium), 4 (low). Deadline After you Go Live Before you Go Live Before you Go Live / Ongoing Before you Go Live / Ongoing Before you Go Live / Ongoing Before you Go Live / Ongoing Before you Go Live

1.4 Project Milestones


During the session, we contacted you and asked for your planned project milestones. You reported that no milestones are planned for the next 6 months. Project milestones are the critical points in the life of your project. They require special efforts in monitoring and system analysis. SAP Support offers specialized services that prepare your system for these milestones. To be able to offer you the appropriate services, it is crucial that we have information about your project plans.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Service Summary

1.5 Performance Indicators for RPB


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 Avg. Availability per Week Max. CPU Utilization on DB Server Max. CPU Utilization on App Server Avg. DB Request Time in Dialog Task Avg. DB Request Time in Update Task Value 5 665 ms 132 339 ms 100 % 0% 2% 254 ms 317 ms

Hardware Capacity Database Performance

Note:

If you require assistance in resolving concerns about performance of the system, or if you require technical analysis of other aspects of your system, as highlighted in this report, you can create a customer message in component SV-BO-BI with the priority "High" or "Very High". If you have questions concerning the correctness of the checks in this report, or concerning the correct configuration of the Solution Manager Earlywatch Alert Service, you can create a customer message in component SV-BO-BI.

Note:

For full details of our service offering, refer to http://service.sap.com/servicecatalog on SAP Service Marketplace. For full details of the objectives in this service, refer to http://service.sap.com/osdbmigration. SAP offers a comprehensive range of technical and strategic textbooks which can increase your organization's knowledge of SAP's products and best practices. For more information, refer to www.sap-press.com, where you can download the latest catalog. We recommend that you order material relevant to your particular software solution. SAP also offers "Empowering Workshops for System and Solution Optimization". Workshops relevant to this particular system include: - TASP01 EarlyWatch Empowering Workshop For a complete overview of the SAP Empowering Workshops and information about ordering these, refer to http://service.sap.com/empoweringworkshops or visit SAP Service Marketplace.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Table of Contents

2 Table of Contents
1 SERVICE SUMMARY ......................................................................................................................................2

1.1 SUMMARY ................................................................................................................................... 2 1.2 SYSTEM STATUS RPB .................................................................................................................. 3 1.3 ACTION PLAN .............................................................................................................................. 3 1.4 PROJECT MILESTONES ................................................................................................................. 3 1.5 PERFORMANCE INDICATORS FOR RPB ........................................................................................... 4
2 TABLE OF CONTENTS...................................................................................................................................5 3 PERFORMANCE OVERVIEW RPB .................................................................................................................7

3.1 SAP SYSTEM W ORKLOAD............................................................................................................. 7


3.1.1 Current Workload..............................................................................................................................7 4 WORKLOAD DISTRIBUTION RPB .................................................................................................................8

4.1 W ORKLOAD DISTRIBUTION ACROSS ABAP APPLICATION SERVERS .................................................... 8 4.2 W ORKLOAD BY APPLICATION MODULE ............................................................................................ 9 4.3 DB LOAD PROFILE ..................................................................................................................... 10 4.4 RFC COMMUNICATION ............................................................................................................... 11
5 HARDWARE CAPACITY ............................................................................................................................... 12

5.1 HARDWARE CONFIGURATION ....................................................................................................... 12 5.2 OVERVIEW SYSTEM RPB ............................................................................................................ 12 5.3 SERVER BLSAPBP2 .................................................................................................................... 13
6 HARDWARE CAPACITY: FORECAST SITUATION ....................................................................................... 14

6.1 PLANNED HARDWARE CONFIGURATION ........................................................................................ 14 6.2 HARDWARE CAPACITY: FORECAST SITUATION ............................................................................... 14
7 NETWORK SIZING GUIDELINES .................................................................................................................15 8 SAP SYSTEM OPERATING RPB .................................................................................................................. 16

8.1 AVAILABILITY BASED ON COLLECTOR PROTOCOLS .......................................................................... 16 8.2 UPDATE ERRORS ....................................................................................................................... 17 8.3 TRANSPORTS ............................................................................................................................ 17
9 DATABASE SETTINGS FOR RPB ................................................................................................................ 18

9.1 SYSTEM PERFORMANCE ............................................................................................................. 18


9.1.1 Optimizer Statistics ......................................................................................................................... 18 9.1.2 Data dictionary statistics for Oracle 10g ........................................................................................... 18 9.1.3 Fixed object statistics for Oracle 10g ............................................................................................... 19 9.1.4 Synonym to check System statistics for Oracle 10g.......................................................................... 19 10 DATABASE ADMINISTRATION FOR RPB .................................................................................................. 20

10.1 BACKUP STRATEGY .................................................................................................................. 20


10.1.1 General recommendations ............................................................................................................20 GoingLive Migration Analysis, Renfe Operadora, 13.04.2010 5

Table of Contents 10.1.2 Backup Strategy............................................................................................................................ 20 10.1.3 Backup Verification and Consistency Check................................................................................... 20

10.2 FURTHER DATABASE RECOMMENDATIONS................................................................................... 21


10.2.1 Component check in DBA_REGISTRY .......................................................................................... 21 10.2.2 SAP Tools ..................................................................................................................................... 21 10.2.3 Oracle Release ............................................................................................................................. 21 10.2.4 Oracle Patch Sets ......................................................................................................................... 21 10.2.5 Desupport of multibyte character sets as of Oracle 10g .................................................................. 21 10.2.6 Important SAP Notes for Oracle..................................................................................................... 22 11 SAP J2EE ENGINE RPB ............................................................................................................................. 23

11.1 SUPPORTABILITY ...................................................................................................................... 23


11.1.1 Setup of Remote Connection ......................................................................................................... 23

11.2 W EB BROWSER CONFIGURATION ............................................................................................... 24


11.2.1 Browser Compression ................................................................................................................... 24 11.2.2 Browser Caching ........................................................................................................................... 24 11.2.3 Further Browser Settings ............................................................................................................... 25 11.2.4 Dialog box blocker setting.............................................................................................................. 25 11.2.5 Parallel Connections ..................................................................................................................... 26

11.3 SYSTEM CONFIGURATION .......................................................................................................... 26


11.3.1 SAP J2EE Engine Configuration Overview ..................................................................................... 26 11.3.2 Instance RPBBD_RPB_00: Configuration ...................................................................................... 27 11.3.3 Instance RPBSA01_RPB_00 & RPBSA02_RPB_00: Configuration................................................. 33 12 FURTHER RECOMMENDATIONS............................................................................................................... 40

12.1 SAP EARLYWATCH ALERT ........................................................................................................ 40


12.1.1 Activation of the EW Alert Service for RPB ..................................................................................... 40 12.1.2 General Remarks .......................................................................................................................... 40 13 PARAMETER RECOMMENDATIONS.......................................................................................................... 41

13.1 DATABASE PARAMETERS FOR RPB ............................................................................................ 41 13.2 SAP SYSTEM CONFIGURATION FOR RPB ................................................................................... 45
13.2.1 Configuration for Instance RPBBD_RPB_00 .................................................................................. 45 13.2.2 Configuration for Instance RPBSA01_RPB_00............................................................................... 49 13.2.3 Configuration for Instance RPBSA02_RPB_00............................................................................... 53

13.3 SOFTWARE CONFIGURATION ..................................................................................................... 56


13.3.1 SAP Kernel Release ..................................................................................................................... 56 14 APPENDIX .................................................................................................................................................. 57

14.1 HISTORY OF ACTIVITY AND AVERAGE RESPONSE TIMES ................................................................ 57

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Performance Overview RPB

3 Performance Overview RPB


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 RFC UPDATE BATCH SPOOL Dialog Steps 1975 11155 1 22245 10080 Avg. Resp. Time in ms 664,6 543,0 341,0 353,0 9,1 Avg. CPU Time in ms 86,2 61,2 20,0 37,0 3,1 Avg. Wait Time in ms 0,3 0,3 0,0 0,1 2,1 Avg. Load Time in ms 39,0 1,0 1,0 2,2 0,1 Avg. DB Time in ms 253,7 265,9 317,0 184,8 2,6 Avg. GUI Time in ms 271,5 0,0 0,0 0,0 0,0

3.1 SAP System Workload


3.1.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 17 Medium Activity 4 High Activity 1 Total Users 22

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Workload Distribution RPB

4 Workload Distribution RPB


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 Distribution across Servers Workload by Application Module DB Load Profile

4.1 Workload Distribution across ABAP Application Servers


To prevent a workload imbalance on one or more servers, we have analyzed the workload statistics for each SAP instance in your SAP production system. If your total hardware capacity is sufficient to handle your peak workload, an overload on one or more servers can increase response times for all users logged on to those servers. If the affected servers are running updates or a database instance, all users can be affected. The following diagrams show the system workload distribution across all instances. We strongly recommend that you distribute the workload equally across all application servers. The following aspects of the workload are evaluated below: - The total number of transaction steps performed on the different servers - The percentage of CPU time consumed by SAP applications running on the different servers If the workload is distributed equally, the distribution of CPU time should be proportional to the number of CPUs on the different servers.

Note that your database capacity is limited by the database server hardware available. This is important, since your database is a central resource for all system activities. In contrast, application servers are not a central resource and affect only the users on that particular server. CPU shortages can be solved by improving the workload distribution or by adding a new application server. For information about automatic load balancing, refer to SAP Note 26317.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Workload Distribution RPB

4.2 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 / Customer BC-DB BW

CPU Time in % 69,8 9,4 8,3 8,0 4,3

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

Workload Distribution RPB

Module BC BC-DB BC-CCM Not Assigned / Customer BW

DB Time in % 60,7 15,8 10,7 8,2 4,3

4.3 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. 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. GoingLive Migration Analysis, Renfe Operadora, 13.04.2010 10

Workload Distribution RPB

4.4 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. Outgoing function call /BDL/_REQUEST_DATA_TASK /BDL/_DO_GENERATION /BDL/_EXECUTE_FUNCTION /BDL/MAINTAIN_SDCC_TASK SALP_LOCAL_SEL_DATA_PUSH /SSF/CALL_SUBROUTINE_RFC RRTS_PARSE_MDX YCT2_TCC_NOTES_READ /SDF/CCMS_READ Incoming function call RSR_NET_INTERFACE BAPI_MDDATASET_GET_AXIS_DATA /BDL/_REQUEST_DATA_TASK /BDL/_EXECUTE_FUNCTION /BDL/_DO_GENERATION SWNC_COLLECTOR_STARTER BAPI_MDPROVIDER_GET_VARIABLES PRGN_J2EE_GET_ROLES BAPI_MDPROVIDER_GET_MEMBERS Calls 2 2 2 7 21 3 271 1 2 Calls 557 251 2 4 2 168 253 336 135 Total call time, s 588,74 261,11 251,22 49,24 13,95 6,85 5,70 4,58 4,46 Total call time, s 1207,73 972,68 588,72 346,04 261,11 183,69 91,03 69,81 54,44 Average call time, ms 294372 130556 125612 7035 664 2285 21 4584 2232 Average call time, ms Bytes sent 818 8944 2112 2863 9093 2545 270926 649 65906 Bytes sent Bytes received 1514 372 332 5299 5334 10135 428360 1724 4708007 Bytes received 3981453 67097 674 3944 8816 55272 52624 123984 187296

2168 7572280 3875 27597814 294362 1514 86510 664 130554 372 1093 0 360 355301 208 11391408 403 846842

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

11

Hardware Capacity

5 Hardware Capacity
We have checked your system for potential CPU or memory bottlenecks. However, we are missing performance statistics for server cpuz.

5.1 Hardware Configuration


SERVER OVERVIEW Server Hardware Manufacturer Model BladeCenter LS41 4 processors / 8 cores / 8 threads System z9, 2094-704 Operating System SuSE Linux Enterprise Server 10 on x86_64 z/OS 1.7 No. of CPUs 16 Memory in MB 16053

blsapbp2 IBM

cpuz

IBM

6144

5.2 Overview System RPB


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]/Min. UIC Date Rating Analysis Start Analysis End

blsapbp2 cpuz

2 23.03.2010

16053 6144

0 23.03.2010

23.03.2010 11.04.2010 -

Note: In the past you have tried to implement SAPOSCOL on database server CPUZ. However, this has not been performed successfully.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

12

Hardware Capacity

5.3 Server blsapbp2

This graph shows the average CPU load and the average paging rates in relation to the physical RAM of the blsapbp2 server. CPU This server's CPU resources are sufficient to handle the current workload. Memory The memory resources are sufficient for the current workload.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

13

Hardware Capacity: Forecast Situation

6 Hardware Capacity: Forecast Situation


We have checked your SAP System for potential CPU or memory bottlenecks. You should monitor hardware performance after you Go Live.

6.1 Planned Hardware Configuration


Server RPBBD RPBSA01 RPBSA02 Hardware Manufacturer HP IBM IBM Model Superdome Blade Blade OS OS release No. of CPUs 8 16 16 Memory in MB 56000 64000 64000 HP-UX 11.31 LINUX SUSE 10 LINUX SUSE 10

6.2 Hardware Capacity: Forecast Situation


Server RPBBD RPBSA01 RPBSA02 CPU Rating RAM [MB] 56000 64000 64000 Memory Rating

During this session we performed a basic sizing estimate which was based on the current workload on system RPB along with the contents of QuickSizer project entitled AUGE. We have rated the sizing estimate Yellow as we are unable to fully rate the performance of your current hardware, see section 5 for more details. Recommendation: You should closely monitor hardware performance after you Go Live to ensure there are no hardware bottlenecks. If you experience any issues please open a customer message on component SV-BO-BI.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

14

Network Sizing Guidelines

7 Network Sizing Guidelines


The objective of network sizing is to ensure that bottlenecks do not occur between: - Front-end PCs and application servers - Two application servers - An application server and a database or RFC server - Client programs and an application server The network load of individual SAP applications differs depending on the number of round trips and the application data transferred. Recommendation: Refer to the Network Sizing Guide for the SAP Business Solutions for different frontend SAP architectures on SAP Service Marketplace using quick link Sizing -> Sizing Guidelines -> Solutions&Platform -> "Front End Requirements for SAP Solutions". General network documentation is available on SAP Service Marketplace at: http://service.sap.com/ [http://service.sap.com/]. If a network problem already exists or you want to evaluate the network performance of the system, you can use NIPING. This tool is available on SAP Service Marketplace as described in SAP Note 799428. A detailed description of the procedure is provided in SAP Note 500235 (Network Diagnosis with NIPING) and other relevant SAP Notes.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

15

SAP System Operating RPB

8 SAP System Operating RPB


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.

Rating

Check Availability based on Collector Protocols Update Errors Table Reorganization

8.1 Availability based on Collector Protocols

A value of 100% means that the collector was available all day. "Available" in the context of this report means that at least one SAP instance was running. If the SAP collector was not running correctly, the values in the table and graphics may be incorrect. To check these logs, call transaction ST03N (expert mode) and choose "Collector and Performance DB -> Performance Monitor Collector -> Log". This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour. The job does NOT check availability; it carries out only general system tasks such as collecting and aggregating SAP performance data for all servers/instances. The log does not contain any direct information about availability; it contains only information about the status of the hourly statistical data collection. As of SAP Basis 6.40, system availability information is available in the CCMS (Computing Center Management System) of an SAP System, in Service Level Reporting of SAP Solution Manager. This function is provided by the relevant Solution Manager Support Packages as an advanced development. For more information, refer to SAP Note 944496, which also lists the prerequisites that must be fulfilled before implementation can take place."

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

16

SAP System Operating RPB

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

8.3 Transports
Transports were not found in the period analyzed.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

17

Database Settings for RPB

9 Database Settings for RPB


Some problems with database settings that could potentially lead to performance problems have been detected in your database system. Implement the recommendations provided in the following sections.

Rating

Check Database Parameters (=> see section Parameter Recommendations)

9.1 System Performance


9.1.1 Optimizer Statistics
The Oracle Cost-Based Optimizer requires current information about the distribution of the database data in order to find the best search path. If this information is not up-to-date, or is not available at all, the Cost-Based Optimizer may choose the wrong query path, which can result in severe performance problems. You should update your statistics as recommended in the SAP strategy for generation of optimizer statistics. Recommendation: Schedule the Update Statistics task weekly. For detailed information about the SAP strategy for parallel generation of optimizer statistics, including the update of the data distribution statistics of your database, see the document "Update Statistics for the Oracle Cost-Based Optimizer" in http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000038900 and http://service.sap.com/dbaora -> Performance. If you still use the SAP two-phase strategy, schedule the Update Statistics task weekly using the CCMS DBA Planning Calendar (transaction DB13). For detailed information on the two-phase strategy as recommended by SAP, see SAP Notes 132861, 93098, and 93256. This includes the update of the data distribution statistics for your database. Recommendation: While creating optimizer-statistics using SAPDBA and the two-phase strategy should lead to correct results, please note that SAPDBA is no longer being developed. New developments will only occur in BRCONNECT (SAP Note 0403704, however other SAPDBA functions continue to be fully supported) . Also, using BRCONNECT allows you to take advantage of a faster one-step procedure for creating optimizer statistics. Therefore, we recommend that you use BRCONNECT, as described in the document "Update Statistics for the Oracle Cost-Based Optimizer" in http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000038900 Note: If your users/developers are allowed to create their own tables or indexes, we recommend that you schedule the creation of statistics for tables with missing statistics daily. Otherwise, because Oracle does not create statistics for newly created objects, these objects will remain without valid statistics until the next update run for the optimizer statistics.

9.1.2 Data dictionary statistics for Oracle 10g


DDIC TABLES Table_name CON$ last_analyzed 2009/11/27 13:55:50

As of Oracle 10g, it is advisable to create database statistics on Oracle Data Dictionary objects, because the Rule Based Optimizer is no longer used as of this release and accesses to DDIC-objects are optimized by the Cost Based Optimizer. We found Oracle DDIC objects without database statistics on your system. Recommendation: You should create statistics on the Oracle DDIC objects by using brconnect with the command line: brconnect -u / -c -f stats -t oradict_stats. We recommend that you create DDIC statistics on a quarterly basis. See SAP notes 838725 and 863811 for background information. GoingLive Migration Analysis, Renfe Operadora, 13.04.2010 18

Database Settings for RPB

9.1.3 Fixed object statistics for Oracle 10g


As of Oracle 10g, we recommend that you create database statistics for fixed Oracle objects that contain information about current database activities. This is due to the fact that the rule-based optimizer is no longer used as of this release and the cost-based optimizer ensures full access to DDIC objects. Fixed objects (X$* tables ) with database statistics were not found in your system. We therefore recommend that you create statistics for the fixed objects using BRCONNECT with the following command line: brconnect -u / -c -f stats -t oradict_stats. Recommendation: You should create fixed object statistics every quarter. For more information, see SAP Notes 838725 and 863811.

9.1.4 Synonym to check System statistics for Oracle 10g


As of Oracle 10g, we recommend that you create "NOWORKLOAD" system statistics. These statistical values provide additional information about the Oracle cost-based optimizer, such as CPU speed without system load or disk-seek-time for block accesses. For more information about Oracle system statistics, see SAP Notes 838725 and 927295. The system statistics are stored in internal Oracle table aux_stat$. Since an object with the SAPR3 or SAP<SID> user that belongs to the SYS user cannot be queried, the corresponding sys.aux_stats$ synonym is queried. The analysis showed that this synonym does not exist in your database. We therefore recommend that you check whether NOWORKLOAD system statistics were created in your Oracle database. To create these statistics, use BRCONNECT with the following command: brconnect -u / -c -f stats -t system_stats [-i <minutes>]. Also see SAP Note 601395 for information about how to use BRCONNECT to collect system statistics. To check the system statistics in your database using transaction st04n, create the sys.aux_stats$ synonym by following the instructions in SAP Note 706927. Recommendation: You should create system statistics: - After creating the database - After creating new tablespaces - After a database upgrade to Oracle Database 10g - If you change DB server hardware (different/more CPUs, more hard disks, faster network) - Once every quarter

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

19

Database Administration for RPB

10 Database Administration for RPB


Some problems were found regarding database administration. Check the following sections for problems that may be caused by your database administration strategy. Note:A remote service cannot verify certain important aspects of your administration strategy such as offsite storage of database backups and whether backup tapes can be read correctly.

10.1 Backup Strategy


10.1.1 General recommendations
You must have a backup strategy, to prevent data loss. When you implement your backup strategy, you must take the maximum downtime in case of recovery into consideration. Recommendation: Set up a restore and recovery scenario, taking the following into account: 1. Once you have uploaded the first load of each InfoCube and the masterdata, perform an offline backup. 2. Your routine backup strategy should include: - Performing a full online backup after each delta load or at least oncea week - Performing an offline backup at least once a month - Performing an offline backup of the redo log files at least once a day 3. You should back up at least the offline redo log files on two different tapes, and store each of these tapes in a different physical location. 4. You should also check the database for corrupted blocks, once during each offline backup (see SAP Note 23345). You can use the DB-verify Oracle tool to check the database for corrupted blocks, using the option "-w use_dbv" for BRBACKUP and BRRESTORE. Test your restore and recovery scenario at least once before start of production.

10.1.2 Backup Strategy


Recommendation: SAP strongly recommends using a backup cycle of at least 4 weeks. The more backups are available for recovery, the better you are protected against physical tape errors and logical database errors. SAP recommends performing a full database backup after each working day. If the available backup window is too short for performing full backups, partial backups should be performed on a daily basis. The more frequently you back up your database, the shorter the duration of a potential recovery. SAP recommends backing up the offline redo log files on a daily basis. Because offline redo log files are important in case of recovery, we strongly recommend writing a second copy of each offline redo log file to a second tape. If you must restore your database from a backup, a complete recovery requires the complete sequence of offline redo log files written since the creation time of the backup. If an offline redo log file is missing, recovery must end at the missing offline redo log file, and all subsequent changes to the database are lost.

10.1.3 Backup Verification and Consistency Check


Recommendation: perform a verification run of a backup at least once during the backup cycle to detect possible problems in the restore scenario. Note that the verification run will double the backup time. In addition, we strongly recommend that you check the database periodically for corrupted blocks as described in SAP Note 23345. Perform this at least once in a backup cycle. A summary of "Frequently Asked Questions", including a discussion of the advantages and restrictions of different consistency check methods, is presented in SAP Note 540463. It is crucial for your database that you have at least one backup with a subsequent verification available at any point of time. Should block corruption occur, the last VERIFIED successful backup is required for the restore and recovery, as opposed to the last successful backup.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

20

Database Administration for RPB

10.2 Further Database Recommendations


10.2.1 Component check in DBA_REGISTRY
Performance problems may occur if the CATALOG and CATPROC objects do not have an adequate patch level or status. The table below shows that one or both of the objects have an incorrect patch level or status. Recommendation: If the patch level displayed for CATALOG or CATPROC is older than the patch set used in the system, the catalog scripts have not run correctly (see Note 539921). You can use SAP Note 582427 to correct this problem. If either CATALOG or CATPROC is INVALID, validate them as described in SAP Note 648203. In certain cases, serious performance problems may occur if the catalog information is obsolete.

10.2.2 SAP Tools


Recommendation: Implement the latest release of SAP tools SAPDBA, BRBACKUP, BRARCHIVE, BRCONNECT, BRRESTORE, BRSPACE, BRRECOVER, and BRTOOLS from sapserv before the start of production. See SAP Notes 12741 and 19466.

10.2.3 Oracle Release


Release Recommendation 10.2.0 We recommend that you install the latest Oracle patch set as soon as possible (refer to SAP Note 415900). Check SAP Note 871735 regularly for the latest patch set for Oracle 10.2.0.

Note that in addition to the patch set, further bug fixes may be available and recommended. Refer to the following SAP Notes: Patch set 10.2.0.4 SAP Note number 1137346 Description Oracle 10.2.0: Patches/patch collections for Oracle 10.2.0.4

10.2.4 Oracle Patch Sets


Recommendation: Apply the current Oracle patch set before the start of production. SAP Note number 871735 Description Current patch set for Oracle 10.2.0

10.2.5 Desupport of multibyte character sets as of Oracle 10g


We checked your NLS multibyte character set according to SAP Note 858869. The following multibyte character set is in use: We were unable to check your NLS multibyte character set. Make sure that it is set according to SAP Note 858869.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

21

Database Administration for RPB

10.2.6 Important SAP Notes for Oracle


To optimize system performance and prevent data loss or system downtime, read and, if necessary, implement the following SAP Notes. SAP Note Number 985118 838725 971261 964858 766349 619188 618868 540477 354080 128221 519448 558746 871455 841728 871096 871735 850306 1021454 1039393 1144178 1368640 Description Wrong values when you execute parallel queries Oracle Database 10g: New database statistics Hanging queries in Oracle 10.2.0.2 STAR_TRANSFORMATION Incorrect vals w/ STAR_TRANSFORMATION_ENABLED in Oracle 10.2 FAQ: Oracle SQL optimization FAQ: Oracle Wait Events FAQ: Oracle performance Collective note: Oracle - Hot News notes Note collection for Oracle performance problems Increased memory consumption with Oracle >8.0.X Performance problems when deactivating aggregates Better Oracle Data Dictionary BW Performance Poor performance when accessing DBA and V$ views Oracle 10.2.0: Composite note for problems and workarounds Oracle Database 10g: Patch sets/Patches for 10.2.0 Current Patchset for Oracle 10.2.0 Oracle Critical Patch Update Program Oracle Segment Shrinking may cause LOB corruption. DATAPUMP creates corruptions in tables with (LONG) Invalid float values Array Update can corrupt a row.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

22

SAP J2EE Engine RPB

11 SAP J2EE Engine RPB


11.1 Supportability
SUPPORTABILITY SUMMARY Rating Description Setup of Remote Connections Solution Manager Diagnostics

11.1.1 Setup of Remote Connection


To provide services and support, SAP requires access to your SAP NetWeaver AS Java at application level and therefore provides the option to set up service connection type 'HTTP Connect' via SAP Service Marketplace. However, remote connections to application sharing services on Windows-based computers can also be set up and used to access the SAP NetWeaver application. A connection of this type is mainly required for root cause analysis if serious problems occur when SAP Support and SAP Development access the system. For UNIX boxes, a Telnet connection can be set up for access at operating system level. For more information about remote connections in general, see 'Setup Remote Connectivity for SAP NetWeaver' on SAP Service Marketplace at http://service.sap.com/access-support -> Media Library. Remote Connection Type HTTP Connect Netviewer Windows Terminal Service Netmeeting pcAnywhere Telnet SAP Notes 592085 1036616 655502 356635 89510 and 100740 37001

You already provide remote access to your SAP NetWeaver AS Java system at application level via HTTP. This is sufficient for standard SAP services.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

23

SAP J2EE Engine RPB

11.2 Web Browser Configuration


11.2.1 Browser Compression
If you have users that log on to the system via WAN connections, we recommend that you enable compression for communication between the Web browser and the application server. To enable compression for communication between the Web browser and the application server (client-side) when using Microsoft Internet Explorer as the client browser, activate the HTTP 1.1 setting. Note: If you want to use compression, you must enable it (server-side) by configuring the HTTP service of the J2EE Engine accordingly.

11.2.2 Browser Caching


Browser caching reduces network load and enhances performance since static content (such as .css or .js files) does not have to be transferred to the Web browser if already available in the browser cache. Implementation: To enable browser caching for MS Internet Explorer (IE): 1. From the Tools menu of Internet Explorer: Choose Internet Options -> General -> Temporary Internet files -> Settings. 2. Under "Check for newer versions of stored pages", select either "Automatically" or "Every time you start Internet Explorer". Note: Do not select "Every visit to the page". To enable browser caching for Mozilla Firefox: 1. In the browser address bar, enter "about:config". 2. Check that parameters browser.cache.disk.enable and browser.cache.memory.enable are set to "true". 3. Set parameter browser.cache.check_doc_frequency to: - "0" (Check for a new version of a page once per session) or - "3" (Check for a new version when the page is out of date.(Default)). Note: Do not select 1 (Check for a new version every time a page is loaded). To enable browser caching for Netscape Communicator: 1. From the Edit menu of Netscape Communicator: Choose Preferences. 2. Under Category, choose Advanced -> Cache. 3. Under "Document in cache is compared to document in network", select either "Never" or "Once per session". Note: Do not select "Every time".

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

24

SAP J2EE Engine RPB

11.2.3 Further Browser Settings


Web applications (such as iViews) are often programmed in a script language and use cookies. To ensure that Web applications are executed correctly, several settings are recommended that affect your browser options for scripting and cookies. Implementation: For MS Internet Explorer (IE): 1. From the Tools menu of Internet Explorer: Choose Internet Options -> Security and choose either the Internet or Intranet icon depending on your configuration. 2. Choose Custom Level. 3. In the Security Settings dialog box, make sure the Enable radio button is selected for the following options: - Cookies -> Allow per-session cookies (not stored) - Scripting -> Active scripting - Scripting -> Scripting of Java applets 4. Return to the Internet Options dialog box by choosing OK and choose tab page Advanced. 5. Make sure that "Show friendly HTTP error messages" is not selected for option "Browsing". 6. Choose OK to save your settings and close the Internet Options dialog box. For Mozilla Firefox: 1. From the Tools menu of Mozilla Firefox: Choose Options -> Privacy and activate "Accept cookies from sites". 2. From the Tools menu of Mozilla Firefox: Choose Options -> Content and activate both "Enable JavaScript" and "Enable Java". For Netscape Communicator: 1. From the Edit menu of Netscape Communicator: Choose Preferences -> Advanced. 2. In the Cookies area, make sure that "Accept all cookies" is selected. Also select "Warn me before accepting a cookie" if required. 3. Save your settings by choosing OK.

11.2.4 Dialog box blocker setting


If you are using a Web-based application, termination can be triggered by several events: 1. You explicitly log off using a function provided by the application or the SAP Enterprise Portal. 2. You navigate to another application in the system by directly entering a URL in the address line of the Web browser or by choosing a menu path. 3. You close the Web browser in which the application is running. 4. The Web browser or client host crashes. In scenario 1, you are logged off automatically via a browser request, which transfers the logoff command to the server. In this case, no browser window is shown in the task bar. In scenarios 2 and 3, the browser window ensures that the logoff command is submitted. As already mentioned, this is required system behavior and is not an error. If you use dialog box blockers, however, you may not be able to close the session on the server. Recommendation: When you use Java or ABAP BEx Web applications, the dialog box blocker must be deactivated at least for the server on which the BEx Web application is started. In this case, both the Java SAP Web application server and the ABAP SAP Web application server must be included in the exception list of the dialog box blocker. For more information, refer to the documentation for the dialog box blocker product you are using. Note that in the version of Microsoft Internet Explorer shipped with Windows XP, Service Pack 2, the dialog box blocker is activated by default. In scenario 4, the client host cannot send a logoff command to the server. The application is closed, therefore, due to a timeout on the server.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

25

SAP J2EE Engine RPB

11.2.5 Parallel Connections


The Internet Explorer and Firefox browsers open two parallel HTTP ports only. This means that if a Web page uses HTML tag "iframe" to include several Web templates, the system does not process all the Web templates in BI at the same time. A maximum of two processes can run in parallel. When a process ends, the system begins processing the next template. Recommendation:When you use Internet Explorer, consider changing the "MaxConnectionsPerServer" parameter under Windows registry "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet", or create this as a DWORD and set it to "10", for example. For the Firefox browser, set the following parameter in the "user.js" file: user_pref("network.http.maxconnections", 48). For more information, refer to SAP Note 968283.

11.3 System Configuration


SYSTEM CONFIGURATION SUMMARY Rating Description Java VM Version Java VM Configuration SAP J2EE Engine Parameters

11.3.1 SAP J2EE Engine Configuration Overview


The table displays an overview of all SAP J2EE Engine instances covered in this report. Each cluster element is listed in a line together with its name, the cluster node type (Dispatcher, Server, or Central Services), and the host on which the cluster element is running. Use this overview table to identify the components of the SAP J2EE Engine to which the individual sections of this chapter refer. OVERVIEW OF SAP J2EE ENGINE INSTALLATIONS AND THEIR ELEMENTS Instance Name RPBBD_RPB_00 RPBBD_RPB_00 RPBSA01_RPB_00 RPBSA01_RPB_00 RPBSA02_RPB_00 RPBSA02_RPB_00 Cluster Element Name dispatcher server0 dispatcher server0 dispatcher server0 Type Dispatcher Server Dispatcher Server Dispatcher Server Server Name RPBBD RPBBD RPBSA01 RPBSA01 blsapbp2 blsapbp2 Installation Directory <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable>

11.3.1.1 Keep Startup Framework Log Files


By restarting the J2EE Engine, you recreate the log files of the J2EE Startup and Control Framework. The information about the period prior to the restart is lost. By setting parameter "jstartup/keep_old_logfiles" in the instance profile to a value between "0" and "100", you can specify the number of generations of the J2EE Startup and Control Framework log files to be retained. This means that the log information for the period prior to the restart is available after the restart. Recommendation: We recommend that you retain the log files created prior to the last restart and that you set the value of this parameter to "3". For more information about this parameter, refer to SAP Note 1062511. Implementation: For a Java-only installation, open instance profile file /usr/sap/<SID>/SYS/profile/<SID>_<instance name>_<hostname> using any text editor and search for parameter "jstartup/keep_old_logfiles". Note that the file must have an empty line at the end. For Java AddIn instances, you can use transaction RZ10 to maintain SAP profile parameters.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

26

SAP J2EE Engine RPB

11.3.2 Instance RPBBD_RPB_00: Configuration


11.3.2.1 Java VM Vendor and Version
Cluster Element dispatcher server0 OS HPUX_IA64 HPUX_IA64 VM Vendor Current VM BIT Rec. VM Version 1.4.2.24 1.4.2.24 Rating Hewlett-Packard Company 64 Hewlett-Packard Company 64

The Java version used to run the J2EE Engine is not up-to-date. Recommendation: We recommend that you use the most up-to-date Java version from the 1.4 family released to run the J2EE Engine. Implementation: Download and install the latest Java 2 SDK from HP as recommended in SAP Note 716926. Downloads are available from HP: http://www.hp.com/go/java Follow the instructions in SAP Note 718901 to change the JDK of a J2EE Engine. Background: The Java Virtual Machine is part of the corresponding JRE (Java Runtime Environment) and the J2SDK (Java 2 Software Development Kit). To use the Web Container service of the J2EE Engine, you must install the SDK - the Java Runtime Environment is not sufficient since Java compiler "javac" is required.

11.3.2.2 General Recommendations for J2EE Engine Configuration


Most of the following recommendations for SAP J2EE nodes refer to changing the properties of individual managers or services. If you notice a significant difference between the value you have selected and the recommendation for a parameter that you have changed intentionally, contact the author or open a customer message on component SV-BO. You can change the configuration in several ways. We recommend that you use the Config Tool, which comes with a graphical user interface. Recommendation: If possible, set the configuration for each cluster element globally rather than locally so that it does not have to be maintained twice. Go through all the properties you changed in the Config Tool and check whether they can be configured globally. Using the Config Tool: 1. Start the Config Tool using the command line (Windows: <central_instance_dir>\j2ee\configtool\configtool.bat or UNIX: <central_instance_dir>/j2ee/configtool/configtool). 2.a. In the tree, navigate to "Global server configuration". Under this node, highlight the manager or service you want to change globally. On the right-hand side, select the property you want to modify. Enter a new value and choose "Add". The parameters are not changed until you choose "Apply" (or menu path "File -> Apply"). 2.b. To change Java VM parameters, select the corresponding J2EE cluster node separately. On the righthand side, adapt the Java VM configuration and choose "Save". 3. Restart the AS Java.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

27

SAP J2EE Engine RPB

11.3.2.3 Dispatcher of RPBBD_RPB_00: Parameters


Java VM Configuration
M AX HEAP SIZE (IN MB) Current Parameter Value <unavailable> JAVA PARAMETERS Current Parameter Value <unavailable> <unavailable> Recommended Parameter Value -Xms256M -verbose:gc Rating Recommended Parameter Value 256 Rating

<unavailable> -Djava.security.policy=./java.policy The tables list a summary of parameters for the Java VM that help boost performance or that are required to run all applications (with all their functions) on the SAP J2EE Engine. For detailed information about this topic, refer to SAP Note 723909 and the related SAP Notes specified therein. If the table contains parameters that are not mentioned in the "Recommended Parameter Value" column, check carefully whether these parameters are still required. Recommendation: Add the parameters listed in the table above to the command line of your Java VM. Implementation: Start the Config Tool in directory ../j2ee/configtool, navigate to tree instance_ID<n>, and highlight the node to be updated. Update the JVM parameters in the "Java parameters" field as recommended, and apply the changes except for the maximum heap size. Enter the maximum heap size in the "Max heap size" field and not as Java parameter "-Xmx".

Log Settings
We identified log controllers configured with low severity ("Info") causing a large amount of logging activity. Recommendation: Consider reducing the severity of log categories and trace locations to "ERROR". Implementation: SAP NetWeaver Administrator: System Management -> Configuration -> Log Configuration Visual Administrator: Services -> Log Configurator -> Runtime Config Tool: Select J2EE cluster node and choose the "Log Configuration" tab page. Choose "(Log) Categories" or "(Trace) Locations" -> "Root Category" and set the severity to "ERROR". Copy the severity settings to the subtree and choose "Save". Background: Reducing the logging activity improves performance.

ThreadManager Properties
Property Name InitialThreadCount MinThreadCount MaxThreadCount ChangeThreadCountStep Description Current Value <unavailable> <unavailable> <unavailable> <unavailable> Recommended Value 50 50 200 50

Initial size of thread pool Minimum size of thread pool Maximum size of thread pool Number of threads added/removed when resizing the thread pool InitialRQSize Initial size of waiting objects queue ChangeRQSizeStep The step, which with the size of the request queue will be changed MaxRQSize Maximum size of waiting objects queue CheckForDecreaseTimeout When thread count grows, check time must decrease

<unavailable> 500 <unavailable> 100 <unavailable> 5000 <unavailable> 3

The table lists the current and recommended values for ThreadManager properties of the Java dispatcher node. Recommendation: Use the Config Tool to change the properties of the ThreadManager for the Java dispatcher node. Note that the change can take effect after you have restarted the dispatcher node.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

28

SAP J2EE Engine RPB

11.3.2.4 Server0 of RPBBD_RPB_00: Parameters


Java VM Configuration
M AX HEAP SIZE (IN MB) Current Parameter Value <unavailable> JAVA PARAMETERS Current Parameter Value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended Parameter Value -Xms2048M -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+HandlePromotionFailure -XX:+UseParNewGC -XX:+DisableExplicitGC -XX:+UseTLAB -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass= com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass. com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass= com.sap.engine.system. PortableRemoteObjectProxy -Djco.jarm=1 Rating Recommended Parameter Value 2048 Rating

The tables list a summary of parameters for the Java VM that help boost performance or that are required to run all applications (with all their functions) on the SAP J2EE Engine. For detailed information about this topic, refer to SAP Note 723909 and the related SAP Notes specified therein. If the table contains parameters that are not mentioned in the "Recommended Parameter Value" column, check carefully whether these parameters are still required. Recommendation: Add the parameters listed in the table above to the command line of your Java VM. Implementation: Start the Config Tool in directory ../j2ee/configtool, navigate to tree instance_ID<n>, and highlight the node to be updated. Update the JVM parameters in the "Java parameters" field as recommended, and apply the changes except for the maximum heap size. Enter the maximum heap size in the "Max heap size" field and not as Java parameter "-Xmx".

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

29

SAP J2EE Engine RPB

Portal Runtime Configuration


Parameter Current value Recommended value Description Max. no. of pages that can be rendered concurrently If set to false, PRT caching is switched on

async.response.pool.size <unavailable> 100 caching.off <unavailable> false

The portal runtime configuration might be insufficient to handle many concurrent requests with good performance. Recommendation: To ensure that the portal server is configured to handle the expected maximum number of concurrent requests, adjust the PRT configuration as specified in the table above. Implementation: 1.async.response.pool.size Can only be maintained with the Visual Administrator or Config Tool for service com.sap.portal.prt.sapj2ee of server nodes 2.caching.off Can be maintained in the portal by choosing "System Administration -> System Configuration -> Service Configuration -> Portal Runtime", and right-clicking "Central Configuration".

Log Settings
We identified log controllers configured with low severity ("Info") causing a large amount of logging activity. Recommendation: Consider reducing the severity of log categories and trace locations to "ERROR". Implementation: SAP NetWeaver Administrator: System Management -> Configuration -> Log Configuration Visual Administrator: Services -> Log Configurator -> Runtime Config Tool: Select J2EE cluster node and choose the "Log Configuration" tab page. Choose "(Log) Categories" or "(Trace) Locations" -> "Root Category" and set the severity to "ERROR". Copy the severity settings to the subtree and choose "Save". Background: Reducing the logging activity improves performance.

ApplicationThreadManager Properties
Property InitialThreadCount MinThreadCount MaxThreadCount Description Initial size of thread pool Minimum size of thread pool Maximum size of thread pool Current Value <unavailable> <unavailable> <unavailable> Recommended Value 40 40 150

The table lists the recommended values for the ApplicationThreadManager properties of the current cluster element. Recommendation: Use the Config Tool or the Visual Administrator to change the properties of the ApplicationThreadManager for the cluster element to match the recommended values.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

30

SAP J2EE Engine RPB

HTTP Provider Service Properties (Server Part)


Parameter Keep Alive Description Current value Recommended value

Enable the reuse of HTTP connections for multiple requests Use Cache Enable the memory-based cache Directory List List all files in directory of default files not found Log Responses Log all HTTP requests CacheControl Static content expiration time in seconds (for browser cache) SapCacheControl Static content expiration time in seconds (for ICM cache)

<unavailable> enabled <unavailable> <unavailable> <unavailable> <unavailable> enabled disabled disabled 604800

<unavailable> 604800

Recommendation: Change the configuration of the HTTP Provider Service in the server to match the recommended values. Implementation: Open the Visual Administrator and navigate to the HTTP Provider Service of the server. The "Log Responses", "UseCache", "KeepAlive", and "Directory List" parameters are displayed on the "Runtime" tab page. The other parameters are displayed on the "Properties" tab page. Change the values of the properties as recommended and choose "Save". You must restart the J2EE Engine node for the changes to take effect. Background: LogResponses: This parameter activates the J2EE Engine HTTP access log. If you have a Web server in front of the J2EE Engine, you probably do not need this access log since the Web server can log all requests. If you do not have a Web server, decide whether you need this access log for purposes such as auditing or Web reporting. Disabling this log improves the performance of the J2EE Engine.

HTTP Compression
Service HTTP Provider HTTP Provider Parameter CompressedOthers MinimumGZipLength Current value <unavailable> <unavailable> Recommended Value to Enable Compression true 1024

The table lists the parameters that are recommended to enable HTTP compression. Recommendation: Check whether HTTP compression is appropriate for your environment. HTTP compression is highly recommended if you have only limited bandwidth available between client browsers and the J2EE Engine. Background: HTTP compression puts additional workload on servers running the J2EE Engine, which may not be part of the sizing procedure. Furthermore, compression is optimal when HTTP 1.1 support is activated in the browser. Note: Older browser versions may not be able to handle compressed cascaded style sheets (.css) or Java script (.js) files. If you expect logons with older browser versions, maintain "CSS" and "JS" in parameter "NeverCompressed".

Web Container Service Properties


Parameter InternalCompiler Description Avoid usage of internal compiler Current value <unavailable> Recommended value false

Recommendation: Change the configuration of the Web Container (servlet_jsp) service in the server to match the recommended values. Implementation: Call the Visual Administrator (or Config Tool) and navigate to the Web Container (servlet_jsp) service of the server. Change the values of the properties as recommended and choose "Save". You must restart the J2EE Engine node for the changes to take effect.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

31

SAP J2EE Engine RPB

Maximum JDBC Connections


The table shows the currently configured value of the maximum DB pool connections of the J2EE server node as well as the recommended minimum value. Parameter sysDS.maximumConnections Current value <unavailable> Recommended value 50 Description Maximum DB connections

The maximum number of JDBC connections might be insufficient for the DBPool of the J2EE server node. Recommendation: Consider increasing the maximum number of JDBC connections. Implementation: Use the Config Tool to change the properties of the JDBC Connector (DB pool) globally. Open the Global Server Configuration and expand the "Services" and "dbpool" sections. Here you can change the value globally. If you have set the values locally for any cluster element, you must delete them. This has the advantage that when new server nodes are added in the future, their configuration is identical to the current nodes.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

32

SAP J2EE Engine RPB

11.3.3 Instance RPBSA01_RPB_00 & RPBSA02_RPB_00: Configuration


11.3.3.1 Java VM Vendor and Version
Cluster Element dispatcher server0 OS LINUX_X86_64 LINUX_X86_64 VM Vendor IBM Corporation IBM Corporation Current VM BIT 64 64 Rec. VM Version j9xa64142-20090306 j9xa64142-20090306 Rating

The Java version used to run the J2EE Engine is not up-to-date. Recommendation: We recommend that you use the most up-to date-version of the new IBM 1.4.2 Hybrid JVM with J9 technology released to run the J2EE Engine. Implementation: Download and install the latest Java 2 SDK from IBM as recommended in SAP Note 861215. Downloads are available from: IBM for Red Hat Enterprise Linux (RHEL): https://www14.software.ibm.com/webapp/iwm/web/reg/download.do?source=lxdk&S_PKG=amd64142sr10 &S_TACT=105AGX05&S_CMP=JDK&lang=en_US&cp=UTF-8 Novell for Suse Linux Enterprise Server 9 (SLES): http://download.novell.com/Download?buildid=tLx4a4yRYj0~ Novell for Suse Linux Enterprise Server 10 (SLES): http://download.novell.com/Download?buildid=dnVRjvWzzUI~ Follow the instructions in SAP Note 718901 to change the JDK of a J2EE Engine. Background: The Java Virtual Machine is part of the corresponding JRE (Java Runtime Environment) and the J2SDK (Java 2 Software Development Kit). To use the Web Container service of the SAP J2EE Engine, you must install the SDK - the Java Runtime Environment is not sufficient since Java compiler "javac" is required.

11.3.3.2 General Recommendations for J2EE Engine Configuration


Most of the following recommendations for SAP J2EE nodes refer to changing the properties of individual managers or services. If you notice a significant difference between the value you have selected and the recommendation for a parameter that you have changed intentionally, contact the author or open a customer message on component SV-BO. You can change the configuration in several ways. We recommend that you use the Config Tool, which comes with a graphical user interface. Recommendation: If possible, set the configuration for each cluster element globally rather than locally so that it does not have to be maintained twice. Go through all the properties you changed in the Config Tool and check whether they can be configured globally. Using the Config Tool: 1. Start the Config Tool using the command line (Windows: <central_instance_dir>\j2ee\configtool\configtool.bat or UNIX: <central_instance_dir>/j2ee/configtool/configtool). 2.a. In the tree, navigate to "Global server configuration". Under this node, highlight the manager or service you want to change globally. On the right-hand side, select the property you want to modify. Enter a new value and choose "Add". The parameters are not changed until you choose "Apply" (or menu path "File -> Apply"). 2.b. To change Java VM parameters, select the corresponding J2EE cluster node separately. On the righthand side, adapt the Java VM configuration and choose "Save". 3. Restart the AS Java.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

33

SAP J2EE Engine RPB

11.3.3.3 Dispatcher of RPBSA01_RPB_00 & RPBSA02_RPB_00: Parameters


Java VM Configuration
M AX HEAP SIZE (IN MB) Current Parameter Value <unavailabe> JAVA PARAMETERS Current Parameter Recommended Parameter Value Value <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> -Xms200M -Xmn70M -Xjvm:j9vm23 -Xthr:minimizeUserCPU -Xgcpolicy:gencon -Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError, request=exclusive+prepwalk -verbose:gc -Djava.security.policy=./java.policy Rating Recommended Parameter Value 200 Rating

The tables list a summary of parameters for the Java VM that help boost performance or that are required to run all applications (with all their functions) on the SAP J2EE Engine. For detailed information about this topic, refer to SAP Note 723909 and the related SAP Notes specified therein. If the table contains parameters that are not mentioned in the "Recommended Parameter Value" column, check carefully whether these parameters are still required. Recommendation: Add the parameters listed in the table above to the command line of your Java VM. Implementation: Start the Config Tool in directory ../j2ee/configtool, navigate to tree instance_ID<n>, and highlight the node to be updated. Update the JVM parameters in the "Java parameters" field as recommended, and apply the changes except for the maximum heap size. Enter the maximum heap size in the "Max heap size" field and not as Java parameter "-Xmx".

Log Settings
We identified log controllers configured with low severity ("Info") causing a large amount of logging activity. Recommendation: Consider reducing the severity of log categories and trace locations to "ERROR". Implementation: SAP NetWeaver Administrator: System Management -> Configuration -> Log Configuration Visual Administrator: Services -> Log Configurator -> Runtime Config Tool: Select J2EE cluster node and choose the "Log Configuration" tab page. Choose "(Log) Categories" or "(Trace) Locations" -> "Root Category" and set the severity to "ERROR". Copy the severity settings to the subtree and choose "Save". Background: Reducing the logging activity improves performance.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

34

SAP J2EE Engine RPB

ThreadManager Properties
Property Name InitialThreadCount MinThreadCount MaxThreadCount ChangeThreadCountStep Description Current Value <unavailabe> <unavailabe> <unavailabe> <unavailabe> Recommended Value 50 50 200 50

Initial size of thread pool Minimum size of thread pool Maximum size of thread pool Number of threads added/removed when resizing the thread pool InitialRQSize Initial size of waiting objects queue ChangeRQSizeStep The step, which with the size of the request queue will be changed MaxRQSize Maximum size of waiting objects queue CheckForDecreaseTimeout When thread count grows, check time must decrease

<unavailabe> 500 <unavailabe> 100 <unavailabe> 5000 <unavailabe> 3

The table lists the current and recommended values for ThreadManager properties of the Java dispatcher node. Recommendation: Use the Config Tool to change the properties of the ThreadManager for the Java dispatcher node. Note that the change can take effect after you have restarted the dispatcher node.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

35

SAP J2EE Engine RPB

11.3.3.4 Server0 of RPBSA01_RPB_00 & RPBSA02_RPB_00: Parameters


Java VM Configuration
M AX HEAP SIZE (IN MB) Current Parameter Value <unavailabe> JAVA PARAMETERS Current Parameter Value <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> <unavailabe> Recommended Parameter Value Rating Recommended Parameter Value 2048 Rating

-Xms2048M -Xmn400M -Xgcpolicy:gencon -Xdisableexplicitgc -Xjvm:j9vm23 -Xsoftrefthreshold1 -Xthr:minimizeUserCPU -Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError, request=exclusive+prepwalk -verbose:gc -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass. com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass= com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1

The tables list a summary of parameters for the Java VM that help boost performance or that are required to run all applications (with all their functions) on the SAP J2EE Engine. For detailed information about this topic, refer to SAP Note 723909 and the related SAP Notes specified therein. If the table contains parameters that are not mentioned in the "Recommended Parameter Value" column, check carefully whether these parameters are still required. Recommendation: Add the parameters listed in the table above to the command line of your Java VM. Implementation: Start the Config Tool in directory ../j2ee/configtool, navigate to tree instance_ID<n>, and highlight the node to be updated. Update the JVM parameters in the "Java parameters" field as recommended, and apply the changes except for the maximum heap size. Enter the maximum heap size in the "Max heap size" field and not as Java parameter "-Xmx".

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

36

SAP J2EE Engine RPB

Portal Runtime Configuration


Parameter Current value Recommended value Description Max. no. of pages that can be rendered concurrently If set to false, PRT caching is switched on

async.response.pool.size <unavailabe> 100 caching.off <unavailabe> false

The portal runtime configuration might be insufficient to handle many concurrent requests with good performance. Recommendation: To ensure that the portal server is configured to handle the expected maximum number of concurrent requests, adjust the PRT configuration as specified in the table above. Implementation: 1.async.response.pool.size Can only be maintained with the Visual Administrator or Config Tool for service com.sap.portal.prt.sapj2ee of server nodes 2.caching.off Can be maintained in the portal by choosing "System Administration -> System Configuration -> Service Configuration -> Portal Runtime", and right-clicking "Central Configuration".

Log Settings
We identified log controllers configured with low severity ("Info") causing a large amount of logging activity. Recommendation: Consider reducing the severity of log categories and trace locations to "ERROR". Implementation: SAP NetWeaver Administrator: System Management -> Configuration -> Log Configuration Visual Administrator: Services -> Log Configurator -> Runtime Config Tool: Select J2EE cluster node and choose the "Log Configuration" tab page. Choose "(Log) Categories" or "(Trace) Locations" -> "Root Category" and set the severity to "ERROR". Copy the severity settings to the subtree and choose "Save". Background: Reducing the logging activity improves performance.

ApplicationThreadManager Properties
Property InitialThreadCount MinThreadCount MaxThreadCount Description Initial size of thread pool Minimum size of thread pool Maximum size of thread pool Current Value <unavailabe> <unavailabe> <unavailabe> Recommended Value 40 40 150

The table lists the recommended values for the ApplicationThreadManager properties of the current cluster element. Recommendation: Use the Config Tool or the Visual Administrator to change the properties of the ApplicationThreadManager for the cluster element to match the recommended values.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

37

SAP J2EE Engine RPB

HTTP Provider Service Properties (Server Part)


Parameter Keep Alive Description Current value Recommended value

Enable the reuse of HTTP connections for multiple requests Use Cache Enable the memory-based cache Directory List List all files in directory of default files not found Log Responses Log all HTTP requests CacheControl Static content expiration time in seconds (for browser cache) SapCacheControl Static content expiration time in seconds (for ICM cache)

<unavailabe> enabled <unavailabe> <unavailabe> <unavailabe> <unavailabe> enabled disabled disabled 604800

<unavailabe> 604800

Recommendation: Change the configuration of the HTTP Provider Service in the server to match the recommended values. Implementation: Open the Visual Administrator and navigate to the HTTP Provider Service of the server. The "Log Responses", "UseCache", "KeepAlive", and "Directory List" parameters are displayed on the "Runtime" tab page. The other parameters are displayed on the "Properties" tab page. Change the values of the properties as recommended and choose "Save". You must restart the J2EE Engine node for the changes to take effect. Background: LogResponses: This parameter activates the J2EE Engine HTTP access log. If you have a Web server in front of the J2EE Engine, you probably do not need this access log since the Web server can log all requests. If you do not have a Web server, decide whether you need this access log for purposes such as auditing or Web reporting. Disabling this log improves the performance of the J2EE Engine.

HTTP Compression
Service HTTP Provider HTTP Provider Parameter CompressedOthers MinimumGZipLength Current value <unavailabe> <unavailabe> Recommended Value to Enable Compression true 1024

The table lists the parameters that are recommended to enable HTTP compression. Recommendation: Check whether HTTP compression is appropriate for your environment. HTTP compression is highly recommended if you have only limited bandwidth available between client browsers and the J2EE Engine. Background: HTTP compression puts additional workload on servers running the J2EE Engine, which may not be part of the sizing procedure. Furthermore, compression is optimal when HTTP 1.1 support is activated in the browser. Note: Older browser versions may not be able to handle compressed cascaded style sheets (.css) or Java script (.js) files. If you expect logons with older browser versions, maintain "CSS" and "JS" in parameter "NeverCompressed".

Web Container Service Properties


Parameter InternalCompiler Description Avoid usage of internal compiler Current value <unavailabe> Recommended value false

Recommendation: Change the configuration of the Web Container (servlet_jsp) service in the server to match the recommended values. Implementation: Call the Visual Administrator (or Config Tool) and navigate to the Web Container (servlet_jsp) service of the server. Change the values of the properties as recommended and choose "Save". You must restart the J2EE Engine node for the changes to take effect.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

38

SAP J2EE Engine RPB

Maximum JDBC Connections


The table shows the currently configured value of the maximum DB pool connections of the J2EE server node as well as the recommended minimum value. Parameter sysDS.maximumConnections Current value <unavailabe> Recommended value 50 Description Maximum DB connections

The maximum number of JDBC connections might be insufficient for the DBPool of the J2EE server node. Recommendation: Consider increasing the maximum number of JDBC connections. Implementation: Use the Config Tool to change the properties of the JDBC Connector (DB pool) globally. Open the Global Server Configuration and expand the "Services" and "dbpool" sections. Here you can change the value globally. If you have set the values locally for any cluster element, you must delete them. This has the advantage that when new server nodes are added in the future, their configuration is identical to the current nodes.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

39

Further Recommendations

12 Further Recommendations
12.1 SAP EarlyWatch Alert
We checked the data on our system concerning your usage of the EarlyWatch Alert Service. We recommend that you follow our recommendations in this area to ensure that you use the EarlyWatch Alert service as efficiently as possible.

12.1.1 Activation of the EW Alert Service for RPB


It was determined that you have set up the SAP EarlyWatch Alert service. However, recommendations exist that you should implement to increase the benefits of SAP EarlyWatch and optimize the performance of your SAP solution. Recommendation: We recommend that you review the following sections containing recommendations for the EarlyWatch Alert service. The software tool recommended for this service is SAP Solution Manager. For best practice documents, see SAP Service Marketplace at: http://service.sap.com/solutionmanagerbp. For Java-based systems, we also recommend that you refer to SAP Note 976054.

12.1.1.1 EW Alert session frequency


The schedule for your EarlyWatch Alert sessions was reviewed. Several EarlyWatch Alert sessions have been completed in the previous month. Recommendation: Review the frequency with which you schedule your EarlyWatch Alert reports. We recommend that you schedule the EarlyWatch Alert service on a weekly basis. If the interval between reports is too great, the data returned may not be detailed enough to analyze performance.

12.1.2 General Remarks


All SAP Notes mentioned in this report can be found on the SAP Service Marketplace (http://service.sap.com). The EarlyWatch Service is designed to maintain your system's high level of performance and availability by monitoring your system throughout all stages of its lifecycle.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

40

Parameter Recommendations

13 Parameter Recommendations
13.1 Database Parameters for RPB
In the configuration file initRPB.ora (or the spfile, if the spfile feature is used) replace the "current value" of the following database parameters with the "recommended value" as shown in the tables below. If the parameter can not be found in the configuration file, the default value has been used. In this case, the recommended parameter has to be added to the configuration file. If the spfile feature is used, the recommendation to "remove a parameter from the profile" means the parameter should be reset back to its default value. Changes to configuration parameters come into effect after your database has been restarted (unless the spfile feature - possible for Oracle >= 9 is used - and a parameter is changed with scope "both"). Carefully check any additional remark that might be added to the parameter recommendation. In the configuration file initRPB.ora (or the spfile, if the spfile feature is used) replace the "current value" of the following database parameters with the "recommended value" as shown in the tables below. If the parameter can not be found in the configuration file, the default value has been used. In this case, the recommended parameter has to be added to the configuration file. If the spfile feature is used, the recommendation to "remove a parameter from the profile" means the parameter should be reset back to its default value. Changes to configuration parameters come into effect after your database has been restarted (unless the spfile feature - possible for Oracle >= 9 is used - and a parameter is changed with scope "both"). Carefully check any additional remark that might be added to the parameter recommendation.

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 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 10191 10027 10028 38068 10183 10629 14532 38087 10091 38085 10411 44951 10142 10753 128221 596420 596420 176754 128648 869521 1031682 948197 1227227 1165319 1137346 1166242 1284478 1351737 Description Increased memory consumption with Oracle >8.0.X System downtime during deadlock (ORA-60) System downtime during deadlock (ORA-60) Problems with CBO and RBO Other access path than expected is used Preventing TM enqueues due to REBUILD ONLINE ORA-04031 due to shared pool component "mvobj part Merge fix for DBMS_STATS package on Oracle 9.2.x and 10.2.x SQL statement runs endlessly or times out (kkompr) Problems with CBO and RBO Oracle Database 10g: Patches for Release 10.2.0.4 10g: "enq: HW contention" waits for LOB Inserts in ASSM TBS Poor performance when using Btree bitmap plans Oracle 10.2.0.4: Table Prefetching causes Wrong Results Current Value

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

41

Parameter Recommendations

Parameter _FIX_CONTROL
Oracle has provided the '_fix_control' parameter to determine whether fixes for bugs in the optimizer can be activated. The recommendations for '_fix_control' depend on the Oracle release and whether specific fixes have been activated in your system. For further information, see the recommended SAP Notes. SAP NOTES SAP Note 1165319 Description Optimizer merge fix for Oracle 10.2.0.4

You are either upgrading the database release or migrating the database to Oracle Version 10.2.0.2 or 10.2.0.4. It is therefore likely that the system has not yet been configured for the new release. There are currently no accurate recommendations available for setting the _fix_control parameter during this analysis session. Recommendation: For the latest parameter settings for the new database release, see SAP Note 830576.

Database Parameters
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 830576 1171650 Description Parameter recommendations for Oracle 10g Automated Oracle DB parameter check

Note: The SAP Note highlighted in the table above contains an automated script which can be used to check the configuration of your database. Parameters _sort_elimination_cost_ratio _optimizer_mjc_enabled _first_spare_parameter Description Efficient index with FIRST_ROWS and ORDER BY Enable merge join cartesian first spare parameter - integer Current value <unavailable> <unavailable> <unavailable> Recommended value 10

compatible control_file_record_keep_time db_block_size

Enables the newest features of Oracle Nr. of days when a record in the controle file can be reused Size of an Oracle data block in bytes

FALSE Please check SAP Notes 1273790 and 830576 <unavailable> 10.2.0 <unavailable> <unavailable> 30 8192

The block size configured for your database (db_block_size) does not correspond to the value required by SAP. This value cannot be changed except by exporting, recreating, and importing the entire database. Parameter db_block_size must NOT be changed under any circumstances without recreating the database. Parameters db_cache_size filesystemio_options Description Size of the buffer cache (DEFAULT buffer pool) Filesystem I/O options Current value <unavailable> <unavailable> Recommended value 12884901888 SETALL

For restrictions to parameter "filesystemio_options", see the following SAP Notes: 914177.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

42

Parameter Recommendations Parameters log_buffer log_checkpoints_to_alert max_dump_file_size open_cursors optimizer_features_enable Description Size of Redo Log Buffer in bytes Checkpoints logged in alert file Maximum size of the optimizer trace file Max. Nr. of concurrently open cursors per database session Enables the newest cost-based features of Oracle Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 1048576 TRUE 20000 Please check SAP Note 830576 Delete this parameter name and value from database profile 16384 40

parallel_execution_message_size Parallel Query: Size of messages for parallel execution parallel_max_servers Parallel Query: Maximum number of parallel execution servers

<unavailable> <unavailable>

See SAP Notes 830576 and 651060 to confirm the correct configuration of PARALLEL_MAX_SERVERS. Parameters parallel_threads_per_cpu Description Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 1 14461541000 210 FALSE OFF FALSE

Number of parallel execution processes/threads per CPU pga_aggregate_target Target aggregate PGA memory available to all processes processes Maximum number of database shadow/background processes query_rewrite_enabled Enables query rewriting recyclebin Enables the use of Oracle's recyclebin replication_dependency_tracking Produce information for the Replication Server

If you use replication in your system do not change the setting of parameter 'replication_dependency_tracking', otherwise you can switch it off. Parameters sessions shared_pool_size star_transformation_enabled undo_management _optim_peek_user_binds _push_join_union_view Description Maximum number of concurrent database sessions Size of Shared Pool in bytes Enables the star transformation functionality Specifies the undo space management mode Bind value peeking Enable pushing join predicate inside a union all view Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 420 2147483648 TRUE AUTO FALSE Please check SAP Notes 1248584 and 830576

SAP Note Number 123366

Description Maximum addressable memory for the Oracle SGA

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

43

Parameter Recommendations

Adjust the Oracle Session Data Unit (SDU)


Oracle's own network software, called Net8, uses 2KB as the default packet size for frontend/backend communication. Recommendation: For BW Systems, the default packet size for frontend/backend communication should be changed to 32KB, which is the maximum value possible. Implementation: To do this, add the line (SDU = 32768) to the Net8 profile listener.ora and all copies of the file tnsnames.ora. Example (from listener.ora) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SDU = 32768) (SID_NAME = TC1) (ORACLE_HOME = /oracle/TC1) (PRESPAWN_MAX = 10) Example (from tnsnames.ora) TC1.WORLD= (DESCRIPTION = (SDU = 32768) (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) Please note that you have to add the same line to the listener.ora and all tnsnames.ora files on all application servers. You must also restart the listener after the changes have been made.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

44

Parameter Recommendations

13.2 SAP System Configuration for RPB


The SAP configuration checks cover the correct parameter settings of each SAP instance. SAP parameters are important for the stability and performance of an SAP instance. Procedure: 1. Use transaction RZ10 to maintain SAP profile parameters. Be aware that warnings and error messages may occur. Rely on the recommendations given in this report and ignore these messages. Recommendations in this report are carefully checked by your Service Consultant and overrule the standard checks provided by RZ10. 2. Before starting the SAP instance with the new parameter settings, run program SAPPFPAR (see SAP Note 166551). If any errors occur here, save the output file and contact your Service Center for advice. Restore the old parameter settings and restart the SAP instance. Note: If the "recommended value" of any parameter in the following list is set to "<to be deleted>", you should delete the parameter from the parameter profile. Do not simply change the parameter value to "space".

13.2.1 Configuration for Instance RPBBD_RPB_00


Recommendation: Adapt the SAP instance parameters to the required values in profile .

13.2.1.1 Buffer Settings


Parameters abap/buffersize rsdb/ntab/entrycount rsdb/ntab/ftabsize rsdb/ntab/sntabsize rsdb/ntab/irbdsize rtbb/max_tables rtbb/buffer_length rsdb/cua/buffersize zcsa/table_buffer_area zcsa/db_max_buftab zcsa/presentation_buffer_area sap/bufdir_entries nobuf/max_no_buffer_entries rsdb/obj/buffersize rsdb/obj/max_objects rsdb/otr/buffersize_kb rsdb/esm/buffersize_kb rsdb/esm/max_objects Description Program buffer size Number of nametab entries administrated Data area size for field description buffer Data area size for short NTAB buffer Data area size for initial records buffer directory entries in the single record buffer Size of single record table buffers CUA Buffer Size Size of generic table buffer Directory entries in generic table buffer Size of the buffer allocated for screens Maximum number of entries in the presentation buffer Number range buffer size Size of export/import buffer Max. no. of exporting/importing objects Size of OTR buffer Size of exp/imp SHM buffer Max. number of objects in the buffer. Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 1000000 30000 60000 2500 8000 2000 60000 10000 100000000 10000 10000000 10000 1000 80000 20000 4096 40000 10000

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

45

Parameter Recommendations

13.2.1.2 Memory Management


Parameters em/initial_size_MB em/global_area_MB ztta/roll_first ztta/roll_area ztta/roll_extension abap/heap_area_dia abap/heap_area_nondia rdisp/ROLL_SHM rdisp/ROLL_MAXFS rdisp/PG_SHM rdisp/PG_MAXFS ztta/max_memreq_MB abap/shared_objects_size_MB Description Size of extended memory pool Size of SAP Ext. Global Memory Quota for early allocation of roll area Maximum roll area per user context Quota for extended memory per user mode Heap memory limit for dialog workprocess Heap memory limit for non-dialog workprocesses Roll buffer size in shared memory Maximum size of roll file Paging buffer size in shared memory Maximum size of ABAP/4 paging file. Memory for a single call Size of Shared Objects Memory in MB Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 12288 255 1 6500000 2000000000 2000000000 2000000000 32768 32768 16384 32768 256 20

13.2.1.3 Client Server Communication


Parameters rdisp/max_arq rdisp/bufrefmode gw/max_conn rdisp/tm_max_no rdisp/max_comm_entries gw/max_overflow_size gw/max_sys Description Max. number of internal asynchronous messages Buffer refresh mode Max. number of active connections Max. number of entries in array tm_adm Max. number of communication entries Max. swap space for CPICrequests in the gateway Max. number of connected clients Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 2000 sendon,exeauto 2000 2000 2000 25000000 2000

13.2.1.4 Internet Communication Manager


Recommendation: To maximize the benefits of the "Internet Communication Manager", modify the parameter settings according to the recommendations provided in the table below. Parameters mpi/buffer_size rdisp/plugin_auto_logout icm/keep_alive_timeout Description Current value Recommended value 65536 3600 90

buffer size for memory pipes (MPI) <unavailable> General timeout. <unavailable> Network Connection Keep Alive <unavailable> Timeout

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

46

Parameter Recommendations

Fully qualified domain name


Recommendation: Verify that the full name of the host is specified for the icm/host_name_full parameters. For example: For a server with server name <myhost>, domain name <sap-ag> and TLD <.com>, the fully qualified host name is <server name>.<domain name>.<ext>: "myhost.sap-ag.com". If the parameter SAPLOCALHOSTFULL is set explicitly in one of the SAP profiles (Default- or Instance profiles), verify that the fully qualified host name is set. For more information, see http://help.sap.com/saphelp_nw2004s/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm . Parameters icm/host_name_full Description Full qualified host name of the ICM host Current value <unavailable> Recommended value $(SAPLOCALHOS T).<domain>.<ext>

Activation of ICM Logging


Recommendation: Enable logging to analyze problems in the Internet Communication Manager. Implementation: We recommend that you set parameter ICM/HTTP/LOGGING_0 to the following: icm/HTTP/logging_0 = PREFIX=/, LOGFORMAT=SAPSMD, LOGFILE=icmhttp.log, MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on

Detailed Performance Monitoring for HTTP(S)


The value for the entry rdisp/no_statistic is empty and the "Breakdown by Application" option is selected for "Web Application Server Statistics."

13.2.1.5 Work Processes


Parameters rdisp/wp_no_dia rdisp/wp_no_btc rdisp/wp_no_vb rdisp/wp_no_vb2 rdisp/wp_no_spo rdisp/wp_no_enq Description Number of dialog work processes Number of background work processes Number of update work processes Number of update2 work processes Number of spool work processes Number of enqueue work processes Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 20 10 3 2 1 1

Note: See SAP Note 39412 - "How many work processes should be configured?" for more details.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

47

Parameter Recommendations

13.2.1.6 Database Interface


Parameters DIR_ORAHOME Description Homedirectory of ORACLE Current value <unavailable> Recommended value insert the path to the Oracle Home directory 1000000 Please check SAP note 634263 Please check SAP note 634263

dbs/ora/array_buf_size rsdb/max_in_blocking_factor rsdb/min_in_blocking_factor

Array size for input/output buffer Max. split factor for FOR ALL ENTRIES queries (IN opt) Min. split factor for FOR ALL ENTRIES queries (IN opt)

<unavailable> <unavailable> <unavailable>

13.2.1.7 Performance Statistics


Parameters rsdb/staton stat/tabrec Description Activate extended table statistics standard table statistic Current value <unavailable> <unavailable> Recommended value 1 0

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

48

Parameter Recommendations

13.2.2 Configuration for Instance RPBSA01_RPB_00


Recommendation: Adapt the SAP instance parameters to the required values in profile . Note: For recommendations for the parameters in your Linux operating system, see SAP Note 941735.

13.2.2.1 Buffer Settings


Parameters abap/buffersize rsdb/ntab/entrycount rsdb/ntab/ftabsize rsdb/ntab/sntabsize rsdb/ntab/irbdsize rtbb/max_tables rtbb/buffer_length rsdb/cua/buffersize zcsa/table_buffer_area zcsa/db_max_buftab zcsa/presentation_buffer_area sap/bufdir_entries nobuf/max_no_buffer_entries rsdb/obj/buffersize rsdb/obj/max_objects rsdb/otr/buffersize_kb rsdb/esm/buffersize_kb rsdb/esm/max_objects Description Program buffer size Number of nametab entries administrated Data area size for field description buffer Data area size for short NTAB buffer Data area size for initial records buffer directory entries in the single record buffer Size of single record table buffers CUA Buffer Size Size of generic table buffer Directory entries in generic table buffer Size of the buffer allocated for screens Maximum number of entries in the presentation buffer Number range buffer size Size of export/import buffer Max. no. of exporting/importing objects Size of OTR buffer Size of exp/imp SHM buffer Max. number of objects in the buffer. Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 1000000 30000 60000 2500 8000 2000 60000 10000 100000000 10000 10000000 10000 1000 80000 20000 4096 40000 10000

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

49

Parameter Recommendations

13.2.2.2 Memory Management


Parameters es/implementation Description Memory Management setting Current value <unavailable> Recommended value std

Follow the recommendations in SAP Note 941735 for Linux OS parameters, which also need to be adjusted: kernel.shmmax,,150% physical mem (in bytes) kernel.shmall,,em/initial_size_MB) + SAP buffers (in bytes) Parameters em/initial_size_MB em/global_area_MB ztta/roll_first ztta/roll_area ztta/roll_extension abap/heap_area_dia abap/heap_area_nondia rdisp/ROLL_SHM rdisp/ROLL_MAXFS rdisp/PG_SHM rdisp/PG_MAXFS ztta/max_memreq_MB abap/shared_objects_size_MB Description Size of extended memory pool Size of SAP Ext. Global Memory Quota for early allocation of roll area Maximum roll area per user context Quota for extended memory per user mode Heap memory limit for dialog workprocess Heap memory limit for non-dialog workprocesses Roll buffer size in shared memory Maximum size of roll file Paging buffer size in shared memory Maximum size of ABAP/4 paging file. Memory for a single call Size of Shared Objects Memory in MB Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 12288 255 1 6500000 2000000000 2000000000 2000000000 32768 32768 16384 32768 256 20

13.2.2.3 Client Server Communication


Parameters rdisp/max_arq rdisp/bufrefmode gw/max_conn rdisp/tm_max_no rdisp/max_comm_entries gw/max_overflow_size gw/max_sys Description Max. number of internal asynchronous messages Buffer refresh mode Max. number of active connections Max. number of entries in array tm_adm Max. number of communication entries Max. swap space for CPICrequests in the gateway Max. number of connected clients Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 2000 sendon,exeauto 2000 2000 2000 25000000 2000

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

50

Parameter Recommendations

13.2.2.4 Internet Communication Manager


Recommendation: To maximize the benefits of the "Internet Communication Manager", modify the parameter settings according to the recommendations provided in the table below. Parameters mpi/buffer_size rdisp/plugin_auto_logout icm/keep_alive_timeout Description Current value Recommended value 65536 3600 90

buffer size for memory pipes (MPI) <unavailable> General timeout. <unavailable> Network Connection Keep Alive <unavailable> Timeout

Fully qualified domain name


Recommendation: Verify that the full name of the host is specified for the icm/host_name_full parameters. For example: For a server with server name <myhost>, domain name <sap-ag> and TLD <.com>, the fully qualified host name is <server name>.<domain name>.<ext>: "myhost.sap-ag.com". If the parameter SAPLOCALHOSTFULL is set explicitly in one of the SAP profiles (Default- or Instance profiles), verify that the fully qualified host name is set. For more information, see http://help.sap.com/saphelp_nw2004s/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm . Parameters icm/host_name_full Description Full qualified host name of the ICM host Current value <unavailable> Recommended value $(SAPLOCALHOS T).<domain>.<ext>

Activation of ICM Logging


Recommendation: Enable logging to analyze problems in the Internet Communication Manager. Implementation: We recommend that you set parameter ICM/HTTP/LOGGING_0 to the following: icm/HTTP/logging_0 = PREFIX=/, LOGFORMAT=SAPSMD, LOGFILE=icmhttp.log, MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on

Detailed Performance Monitoring for HTTP(S)


The value for the entry rdisp/no_statistic is empty and the "Breakdown by Application" option is selected for "Web Application Server Statistics."

13.2.2.5 Work Processes


Parameters rdisp/wp_no_dia rdisp/wp_no_btc rdisp/wp_no_vb rdisp/wp_no_vb2 rdisp/wp_no_spo Description Number of dialog work processes Number of background work processes Number of update work processes Number of update2 work processes Number of spool work processes Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 15 7 3 2 1

Note: See SAP Note 39412 - "How many work processes should be configured?" for more details.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

51

Parameter Recommendations

13.2.2.6 Database Interface


Parameters DIR_ORAHOME Description Homedirectory of ORACLE Current value <unavailable> Recommended value insert the path to the Oracle Home directory 1000000 Please check SAP note 634263 Please check SAP note 634263

dbs/ora/array_buf_size rsdb/max_in_blocking_factor rsdb/min_in_blocking_factor

Array size for input/output buffer Max. split factor for FOR ALL ENTRIES queries (IN opt) Min. split factor for FOR ALL ENTRIES queries (IN opt)

<unavailable> <unavailable> <unavailable>

13.2.2.7 Performance Statistics


Parameters rsdb/staton stat/tabrec Description Activate extended table statistics standard table statistic Current value <unavailable> <unavailable> Recommended value 1 0

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

52

Parameter Recommendations

13.2.3 Configuration for Instance RPBSA02_RPB_00


Recommendation: Adapt the SAP instance parameters to the required values in profile . Note: For recommendations for the parameters in your Linux operating system, see SAP Note 941735.

13.2.3.1 Buffer Settings


Parameters abap/buffersize rsdb/ntab/entrycount rsdb/ntab/ftabsize rsdb/ntab/sntabsize rsdb/ntab/irbdsize rtbb/max_tables rtbb/buffer_length rsdb/cua/buffersize zcsa/table_buffer_area zcsa/db_max_buftab zcsa/presentation_buffer_area sap/bufdir_entries nobuf/max_no_buffer_entries rsdb/obj/buffersize rsdb/obj/max_objects rsdb/otr/buffersize_kb rsdb/esm/buffersize_kb rsdb/esm/max_objects Description Program buffer size Number of nametab entries administrated Data area size for field description buffer Data area size for short NTAB buffer Data area size for initial records buffer directory entries in the single record buffer Size of single record table buffers CUA Buffer Size Size of generic table buffer Directory entries in generic table buffer Size of the buffer allocated for screens Maximum number of entries in the presentation buffer Number range buffer size Size of export/import buffer Max. no. of exporting/importing objects Size of OTR buffer Size of exp/imp SHM buffer Max. number of objects in the buffer. Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 1000000 30000 60000 2500 8000 2000 60000 10000 100000000 10000 10000000 10000 1000 80000 20000 4096 40000 10000

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

53

Parameter Recommendations

13.2.3.2 Memory Management


Parameters es/implementation Description Memory Management setting Current value <unavailable> Recommended value std

Follow the recommendations in SAP Note 941735 for Linux OS parameters, which also need to be adjusted: kernel.shmmax,,150% physical mem (in bytes) kernel.shmall,,em/initial_size_MB) + SAP buffers (in bytes) Parameters em/initial_size_MB em/global_area_MB ztta/roll_first ztta/roll_area ztta/roll_extension abap/heap_area_dia abap/heap_area_nondia rdisp/ROLL_SHM rdisp/ROLL_MAXFS rdisp/PG_SHM rdisp/PG_MAXFS ztta/max_memreq_MB abap/shared_objects_size_MB Description Size of extended memory pool Size of SAP Ext. Global Memory Quota for early allocation of roll area Maximum roll area per user context Quota for extended memory per user mode Heap memory limit for dialog workprocess Heap memory limit for non-dialog workprocesses Roll buffer size in shared memory Maximum size of roll file Paging buffer size in shared memory Maximum size of ABAP/4 paging file. Memory for a single call Size of Shared Objects Memory in MB Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 12288 255 1 6500000 2000000000 2000000000 2000000000 32768 32768 16384 32768 256 20

13.2.3.3 Client Server Communication


Parameters rdisp/max_arq rdisp/bufrefmode gw/max_conn rdisp/tm_max_no rdisp/max_comm_entries gw/max_overflow_size gw/max_sys Description Max. number of internal asynchronous messages Buffer refresh mode Max. number of active connections Max. number of entries in array tm_adm Max. number of communication entries Max. swap space for CPICrequests in the gateway Max. number of connected clients Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 2000 sendon,exeauto 2000 2000 2000 25000000 2000

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

54

Parameter Recommendations

13.2.3.4 Internet Communication Manager


Recommendation: To maximize the benefits of the "Internet Communication Manager", modify the parameter settings according to the recommendations provided in the table below. Parameters mpi/buffer_size rdisp/plugin_auto_logout icm/keep_alive_timeout Description Current value Recommended value 65536 3600 90

buffer size for memory pipes (MPI) <unavailable> General timeout. <unavailable> Network Connection Keep Alive <unavailable> Timeout

Fully qualified domain name


Recommendation: Verify that the full name of the host is specified for the icm/host_name_full parameters. For example: For a server with server name <myhost>, domain name <sap-ag> and TLD <.com>, the fully qualified host name is <server name>.<domain name>.<ext>: "myhost.sap-ag.com". If the parameter SAPLOCALHOSTFULL is set explicitly in one of the SAP profiles (Default- or Instance profiles), verify that the fully qualified host name is set. For more information, see http://help.sap.com/saphelp_nw2004s/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm . Parameters icm/host_name_full Description Full qualified host name of the ICM host Current value <unavailable> Recommended value $(SAPLOCALHOS T).<domain>.<ext>

Activation of ICM Logging


Recommendation: Enable logging to analyze problems in the Internet Communication Manager. Implementation: We recommend that you set parameter ICM/HTTP/LOGGING_0 to the following: icm/HTTP/logging_0 = PREFIX=/, LOGFORMAT=SAPSMD, LOGFILE=icmhttp.log, MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on

Detailed Performance Monitoring for HTTP(S)


The value for the entry rdisp/no_statistic is empty and the "Breakdown by Application" option is selected for "Web Application Server Statistics."

13.2.3.5 Work Processes


Parameters rdisp/wp_no_dia rdisp/wp_no_btc rdisp/wp_no_vb rdisp/wp_no_vb2 rdisp/wp_no_spo Description Number of dialog work processes Number of background work processes Number of update work processes Number of update2 work processes Number of spool work processes Current value <unavailable> <unavailable> <unavailable> <unavailable> <unavailable> Recommended value 15 7 3 2 1

Note: See SAP Note 39412 - "How many work processes should be configured?" for more details.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

55

Parameter Recommendations

13.2.3.6 Database Interface


Parameters DIR_ORAHOME Description Homedirectory of ORACLE Current value <unavailable> Recommended value insert the path to the Oracle Home directory 1000000 Please check SAP note 634263 Please check SAP note 634263

dbs/ora/array_buf_size rsdb/max_in_blocking_factor rsdb/min_in_blocking_factor

Array size for input/output buffer Max. split factor for FOR ALL ENTRIES queries (IN opt) Min. split factor for FOR ALL ENTRIES queries (IN opt)

<unavailable> <unavailable> <unavailable>

13.2.3.7 Performance Statistics


Parameters rsdb/staton stat/tabrec Description Activate extended table statistics standard table statistic Current value <unavailable> <unavailable> Recommended value 1 0

13.3 Software Configuration


13.3.1 SAP Kernel Release
You are running SAP Kernel Release 700, patch level 221. 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.

Additional Remarks
SAP releases Support Package Stacks (including SAP Kernel patches) regularly 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).

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

56

Appendix

14 Appendix
14.1 History of Activity and Average Response Times
The following diagrams show the system activity, which is the number of dialog steps and the average response times recorded using transaction ST03.

Week 07.03.2010 14.03.2010 21.03.2010 28.03.2010 04.04.2010 11.04.2010

Total Activity 78 72 65 66 67 67

Dialog Activity 10 6 5 3 2 2

The table and graphic above compare the total system activity for the dialog activity in the time window specified.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

57

Appendix

Week 07.03.2010 14.03.2010 21.03.2010 28.03.2010 04.04.2010 11.04.2010

Avg. Response Time 908 442 278 459 374 665

Avg. DB Time 425 219 139 237 220 254

Avg. CPU Time 336 75 40 54 49 86

Avg. GUI Time 76 108 73 103 92 271

Avg. Wait Time 0 0 0 1 0 0

The table and graphic above compare the average CPU, DB, and wait times as parts of the average response time for dialog tasks in the time window specified.

GoingLive Migration Analysis, Renfe Operadora, 13.04.2010

58