SAP GoingLive Analysis

Service Report
SAP® GoingLive™ Check

Analysis Session
SAP System ID PRD
SAP Component SAP R/3
Release 4.6C
DB System ORACLE 8.0.6
Modules CO EC FI FI-AA MM MM-WM PM PP SD
Customer Alsons Cement Corporation 3/F Alsons

Makati City
Philippines
Service Center SAP Support, Malaysia

Telephone +603 21657006
Fax +603 2164 8557
Date of Session 05.04.2001 <dat_dummy> Session No. 0010000198094

Date of Report 17.04.2001 Installation No. 0120008478
Author Manimaran Tannimalai Customer No. 0000192981
<Watermark>
Service Summary
Service Summary
During this GoingLive Session, we determined that improvements
can be made in your system.
You should take corrective action as soon as possible to:
- Prevent performance problems in your core business
transactions
- Improve your data security
If you would like further information, create a customer message
on component XX-SER-TCC, or call your SAP Local Support
Organization.
Note: All recommendations provided in this report are based on our general experience only. We advise you to
test our recommendations before using them in your production system.
Summary
Generally the hardware is capable of handling the projected workload when GoingLive. About 40 or more
workload distribution was given to the additional application servers uccapp01 and uccapp02 respectively. The
remainder workload to the central instance uccprdvci. As such we would maximize the usage of the additional
application servers.
NT Zero Memory Management was also recommended for ease of monitoring and memory administration.
The following are the areas that need serious attention before GoingLive as it will severely affect the performance
and data protection of your system.
1. Database backup and Redologs Archiving need to be in place as per recommendation in the section Database
Administration.
2. Optimizer statistics need to be scheduled as per recommendation in the section Database Performance
3. SAPDBA -next and SAPDBA -check need to be scheduled as per recommendations in the section Database
Administration.
4. Periodic Housekeeping Jobs Must be scheduled as per R/3 note. 16083.
Next Session - Optimization Session
As per our phone conversation today, the next GoingLive Check -Optimization Session for your system PRD is
scheduled on 21.05.2001 as documented in customer message 47483/2001. Please ensure that the customizing
must be completed and master data available for the production client.
You have not set up the EarlyWatch Alert Service (EWA) in your system yet. With this service, a data package is
sent to SAP at regular intervals (for example, weekly) and several checks are performed
automatically. You can also view the results online in SAPNet. Because the data packages are sent regularly, SAP
can provide you with a detailed trend analysis of important parameters in your system in the
EWA reports. This service is free of charge. For further details, see SAP Note 207223 in SAPNet.
Before a TCC Service session can be performed, customers and partners must adhere to the following
prerequisites:
1. Please select up to maximum total of 5 transactions/programs from 2 R/3 Core modules for the Optimization
Session. Please state the transactions/programs in the customer message.
GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 2

Service Summary
2. The users must be available to run these transactions/programs for TCC.

3. All recommendations from the GoingLive Check - Analysis Session must be fully implemented in the system
before the start of Optimization Session
4. Customizing must be completed and master data available in that Client 100 (also known as Pre-production
Client) for the Optimization Session.
5. Questionnaires for the session must be completed correctly and return to TCC at least 2 weeks before the
scheduled session date.
6. All data of Service Connections in SAPNet - R/3 Frontend are correct and the same as the questionnaire's.
7. The System Administrator (or contact person for the session) must be available and reachable for TCC.
8. TCC can log on to the PRD and the production client via the remote connections.
9. Note 91488 must be fully implemented in the system at least 2 weeks before the scheduled session date.
10. Customer and partner need to make sure that the EarlyWatch Alert is running at all time (See Note 207223).
11. To change session date, customer message must be created/updated at least 3 weeks before the scheduled
session date.
12. The Optimization session will take 2 working days, which is 16 working hours. If the session is delayed by any
other circumstances other than the SAP, TCC will not extend the working hours for the delay.
13. If there is any additional hours required by the customer after the 2 working days, the extension of the time
required will be chargeable in the form of additional session.
14. It is customer and partner responsibilities to ensure that SDCC is working and all the data are collected and
sent to SAP Service System before the session start (See Note 178631).
15. All sessions must be utilized within the year. Sessions cannot be carried forward to the following year.
If any one of the above prerequisites is not met, the session will be cancelled and forfeited. This is to ensure
fairness to all SAP customers and the date can be reallocated to another customer.
Thank you for your cooperation and understanding.
Action Plan
Priority Short step description Deadline
1 Database optimizer statistics must be scheduled weekly Before Going Live
2 SAPDBA -next to be scheduled weekly and SAPDBA - Before GoingLive
check to scheduled daily
2 Implement the recommended parameter AsSoon AsPossible and Before GoingLive
2 Implement all SAP standard Housekeeping jobs are Before Going Live
scheduled as per R/3 note. 16083
3 Start Backup and Redolog archiving Cycle Immediately
Priorities: 1 (very high), 2 (high), 3 (medium), 4 (low).
Note: If you experience serious performance problems, create a customer message on component XX-SER-
TCC with priority high or very high.
Note: If you are not pleased with the service or results you have received, create a customer message on
component XX-SER-TCC, or call SAP Service Management directly (SAP Singapore tel: +65-7686307,
fax +65-7685307).
Note: If you need any consulting services, SAP service & support department provides remote consulting to
assist you. For more details please contact your SAP local support.
Further information, including detailed explanations of the sections in the service report, can be found at SAP's
Internet site for customers and partners, SAP Service Marketplace (service.sap.com/earlywatch and
service.sap.com/goinglivecheck).
We offer the following training courses for performance optimization: BC315 Workload Analysis (for system
administrators) and BC490 ABAP Performance Tuning (for ABAP developers).
Books from the "Official SAP Guides" series can be obtained in most book stores. The following titles are currently
available: SAP R/3 System Administration, SAP R/3 Implementation with ASAP, SAP R/3 Performance

Service Summary
Optimization, and SAP R/3 Change and Transport Management. For detailed information, see
service.sap.com/books.

Table of Contents
1 Table of Contents
SERVICE SUMMARY.............................................................................................................................................. 2
SUMMARY .............................................................................................................................................. 2
NEXT SESSION - OPTIMIZATION SESSION ................................................................................................. 2
ACTION PLAN ......................................................................................................................................... 3
1 TABLE OF CONTENTS ....................................................................................................................................... 5
QUESTIONNAIRE INFORMATION ............................................................................................................... 8

Hardware Configuration ................................................................................................................................. 8
Additional Systems......................................................................................................................................... 8
Concurrent Users in the Production System .................................................................................................. 8
Document Volume.......................................................................................................................................... 8
2 HARDWARE PLAUSIBILITY CHECK................................................................................................................ 10
System Sizing Overview............................................................................................................................... 10
Recommended Active User Distribution ....................................................................................................... 10
Recommended Work Process Distribution for R/3 ....................................................................................... 10
3 SAP SYSTEM CONFIGURATION.......................................................................................................................11
3.1 SAP KERNEL RELEASE .................................................................................................................. 11

3.2 MEMORY CONFIGURATION FOR INSTANCE UCCAPP01_PRD_00 ....................................................... 11
Buffer Settings...............................................................................................................................................11
Client Server Communication........................................................................................................................11
3.3 ADDITIONAL SAP PARAMETERS FOR INSTANCE UCCAPP01_PRD_00................................................ 12
Work Processes ........................................................................................................................................... 12
Database Interface ....................................................................................................................................... 12
3.4 MEMORY CONFIGURATION FOR INSTANCE UCCAPP02_PRD_00 ....................................................... 12
Buffer Settings.............................................................................................................................................. 12
Client Server Communication....................................................................................................................... 13
3.5 ADDITIONAL SAP PARAMETERS FOR INSTANCE UCCAPP02_PRD_00................................................ 13
Work Processes ........................................................................................................................................... 13
3.6 MEMORY CONFIGURATION FOR INSTANCE UCCPRDVCI_PRD_00 ...................................................... 13
Buffer Settings.............................................................................................................................................. 13
Client Server Communication....................................................................................................................... 14
3.7 ADDITIONAL SAP PARAMETERS FOR INSTANCE UCCPRDVCI_PRD_00 .............................................. 14
Work Processes ........................................................................................................................................... 14
4 DATABASE PERFORMANCE ........................................................................................................................... 15
4.1 DATABASE PARAMETERS................................................................................................................. 15

4.2 SYSTEM PERFORMANCE ................................................................................................................. 16
4.2.1 Setup of the Temporary Tablespace .................................................................................................... 16
4.2.2 Missing Indexes .................................................................................................................................. 16
4.2.3 Optimizer Statistics.............................................................................................................................. 16
5 DATABASE ADMINISTRATION......................................................................................................................... 17

Table of Contents
5.1 BACKUP STRATEGY ........................................................................................................................ 17

5.1.1 Backup Cycle ...................................................................................................................................... 17
5.1.2 Backup Frequency .............................................................................................................................. 17
5.1.3 Archive Frequency............................................................................................................................... 17
5.1.4 Backup Verification and Consistency Check ....................................................................................... 17
5.2 FILE DISTRIBUTION CHECK ............................................................................................................. 17
5.2.1 Mirroring of online redo log files .......................................................................................................... 17
5.2.2 Distribution of online and offline redo log files ..................................................................................... 17
5.2.3 Distribution of online redo logs and tablespace files............................................................................ 18
5.2.4 Distribution of offline redo logs and tablespace files............................................................................ 18
5.2.5 Distribution of control file copies.......................................................................................................... 18
5.3 SPACE MANAGEMENT ..................................................................................................................... 18
5.3.1 Freespace in Tablespaces................................................................................................................... 18
5.4 EXTENTS OF TABLES AND INDEXES .................................................................................................. 18
5.4.1 Schedule 'sapdba -next' weekly .......................................................................................................... 18
5.5 ADMINISTRATION MANAGEMENT ...................................................................................................... 18
5.5.1 Check sapdba -check schedule .......................................................................................................... 18
5.6 FURTHER DATABASE RECOMMENDATIONS ....................................................................................... 19
5.6.1 Oracle Memory Leak ........................................................................................................................... 19
5.6.2 SAP Tools............................................................................................................................................ 19
5.6.3 Oracle Patch Sets ............................................................................................................................... 19
5.6.4 Important Notes for Oracle .................................................................................................................. 19
6 SERVER CHECKS ............................................................................................................................................. 20
6.1 APPLICATION SERVER UCCAPP01.................................................................................................... 20

Windows Operating System ......................................................................................................................... 20
Swap/Paging Space ..................................................................................................................................... 20
6.2 APPLICATION SERVER UCCAPP02.................................................................................................... 20
Swap/Paging Space ..................................................................................................................................... 20
6.3 APPLICATION SERVER UCCPRDVCI ................................................................................................... 21
7 FURTHER SAP SYSTEM CHECKS................................................................................................................... 22
7.1 SOFTWARE LOGISTICS .................................................................................................................... 22

System Landscape and TMS ....................................................................................................................... 22
Clients .......................................................................................................................................................... 22
Change Management and Modifications ...................................................................................................... 23
Documentation of Modifications ................................................................................................................... 23
Installed Software Components and SAP Support Packages ...................................................................... 23
7.2 IMPORTANT PERIODIC JOBS ............................................................................................................. 24
8 PREPARATIONS FOR THE NEXT SESSIONS ................................................................................................. 25
8.1 PREPARATIONS FOR OPTIMIZATION SESSION ................................................................................... 25

Focus of the Optimization Session............................................................................................................... 25
System of the Optimization Session............................................................................................................. 25
Buffer Configuration ..................................................................................................................................... 25
Important Notes for Financals ...................................................................................................................... 25
9 FURTHER RECOMMENDATIONS..................................................................................................................... 26

Table of Contents
9.1 SAP NOTES: PERFORMANCE 4.6 .................................................................................................... 26

9.2 EARLYWATCH ALERT ...................................................................................................................... 26

Table of Contents
Questionnaire Information
Hardware Configuration
Server type Server Manufacturer Model Number of CPUs RAM in MB
Application Server uccapp01 Compaq ProLiant DL580 3 3072
Application Server uccapp02 Compaq ProLiant DL580 3 3072
Application Server uccprdvci Compaq ProLiant DL580 2 2048
Database Server uccprdvdb Compaq ProLiant DL580 2 2048
Additional Systems
You have stated that none of the following conditions apply to your system:
1. An additional SAP System is installed on any server of the system, such as another SAP development, test, or
production system.
2. An instance of another system is installed on any server of the system, such as the instance of another SAP
development, test, or production system.
3. A database of another system is installed on any server of the system, such as the database of another SAP
development, test, or production system.
Concurrent Users in the Production System

The table 'Concurrent users in Production System' shows you the number of concurrent users per application
module.
We calculate the number of concurrent users as the sum of medium and high users.
Exception: if low_users > 10 * ( medium_users + high_users ), then 10% of the low users will be added to
the amount of concurrent users.
Module CO EC FI FI-AA MM MM-WM PM PP

No. of Users 16 16 45 5 34 22 151 38
Module SD
94
Document Volume
Document Type Module Avg. No. of Max. No. of Avg. No. of Items per
Documents per Year Documents per Hour Document
CO documents (primary CO 46500 23 10
& secondary cost
elements) for cost
centers
CO documents (primary CO 103600 150 5
& secondary cost
elements) for orders
G/L account postings FI 44000 22 5
Purchase orders MM 29000 30 10
Vendor invoices MM 36000 18 5
Goods movements MM 96000 48 5
Maintenance orders PM 146000 100 10
Production orders PP 27375 14 0
Customer inquiries SD 65000 33 0
Sales documents SD 95100 48 1
(orders, contracts, and
scheduling agreements)
Delivery notes SD 162900 81 1
Billing documents SD 153800 77 1

Table of Contents
Our recommendations are based on the information you provided in the questionnaire and on our analysis of your
SAP System. Our recommendations do not take into consideration the additional load caused by non-SAP
interfaces.

Hardware Plausibility Check
2 Hardware Plausibility Check

System Sizing Overview
The following overview summarizes the results of the Sizing Check. This overview shows whether your hardware
resources (CPU and memory) are sufficient for the expected workload, and identifies the hardware resources that
may cause a bottleneck. In this context, we distinguish between the CPU and the memory required for the
database part of the R/3 System (that is, the server on which the database is running) and the servers on which
R/3 instances are running (the R/3 part).
Rating Resource
CPU Database Server
Memory Database Server
CPU Application Servers
Memory Application Servers
Recommended Active User Distribution

The following table contains our recommendations for the distribution of your active users across your application
servers.
Instance CO EC FI FI-AA MM MM-WM PM PP

uccapp01 00 7 7 18 2 14 9 61 16
uccapp02 00 7 7 18 2 14 9 61 16
uccprdvci 00 2 2 9 1 6 4 29 6
Instance SD
uccapp01 00 38
uccapp02 00 38
uccprdvci 00 18
If you prefer a user distribution that differs from our recommendations, be careful to avoid creating bottlenecks on
any given application server.
Important: To achieve an optimal distribution of users across the R/3 instances, we recommend that you use logon
groups.
Recommended Work Process Distribution for R/3

The following table contains our recommendations for distributing the R/3 work processes across the instances of
your production system. The SAP parameter settings given in the latter part of this report reflect the recommended
work process distribution.
Instance Name Dialog Batch Update Update2 Spool Enqueue

uccapp01 00 21 3 4 1 0 0
uccapp02 00 21 6 1 1 0 0
uccprdvci 00 10 6 5 3 1 1
The R/3 work process distribution corresponds to the active user distribution recommended in the previous
section. Therefore, if you choose to modify the active user distribution, you may need to make corresponding
changes to the definition of work processes in your R/3 System. In particular, this adjustment applies to dialog
work processes.

SAP System Configuration
3 SAP System Configuration

The R/3 Configuration Checks cover the correct parameter settings of each R/3 instance. SAP parameters are
important for the stability and performance of an R/3 instance. Note: After any SAP parameter change in Windows
NT, restart the system immediately to avoid problems.
3.1 SAP Kernel Release

Instance SAP Kernel Release Patch Level
uccapp01 00 46D 531
uccapp02 00 46D 531
uccprdvci 00 46D 531
No problem was detected with respect to the SAP Kernels installed.
3.2 Memory Configuration for Instance uccapp01_PRD_00

Recommendation: Adapt the R/3 instance parameters to the required values in profile
\\uccprdvci\sapmnt\PRD\SYS\profile\PRD_D00_uccapp01.
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 just change the parameter value to "space".
Buffer Settings
Parameters Description Current value Recommended
value
abap/buffersize Program buffer size 150000 350000
rsdb/ntab/entrycount Number of nametab entries 20000 30000
administrated
rtbb/max_tables directory entries in the single 100 500
record buffer
rtbb/buffer_length Size of single record table buffers 2000 30000
rsdb/cua/buffersize CUA Buffer Size 3000 5000
zcsa/table_buffer_area Size of generic table buffer 6000000 50000000
zcsa/db_max_buftab Directory entries in generic table 1000 10000
buffer
zcsa/presentation_buffer_area Size of the buffer allocated for 4400000 20000000
screens
sap/bufdir_entries Maximum number of entries in the 2000 10000
presentation buffer
rsdb/obj/buffersize Size of export/import buffer 4096 20000
rsdb/obj/max_objects Max. no. of exporting/importing 2000 20000
objects
If a program buffer of more than 150 MB is allocated, defective basis addresses of NT System DLLs may fragment
the address space of work processes. The large shared memory segments (such as PXA and extended memory)
may not be created because the available free address space is being fragmented by these DLLs. This may lead
to a start with the PXA buffer of 4 MB and consequently to errors PXA_NO_SHARED_MEMORY. If these errors
occur, please refer to SAP Note 129813.
Client Server Communication

value
gw/max_conn Max. number of active 500 2000
connections
rdisp/tm_max_no Max. number of entries in array 200 2000
tm_adm
rdisp/max_comm_entries Max. number of communication 500 2000
entries


value
gw/max_overflow_size Max. swap space for CPIC- 5000000 25000000
requests in the gateway
3.3 Additional SAP Parameters for Instance uccapp01_PRD_00

Work Processes
value
rdisp/wp_no_dia Number of dialog work processes 12 21
rdisp/wp_no_btc Number of background work 0 3
processes
rdisp/wp_no_vb Number of update work processes 0 4
rdisp/wp_no_vb2 Number of update2 work 0 1
processes
Database Interface
value
DIR_ORAHOME Homedirectory of ORACLE unknown 'Insert the path to
the Oracle
homedirectory'
3.4 Memory Configuration for Instance uccapp02_PRD_00

Buffer Settings
value
administrated
record buffer
buffer
screens
presentation buffer
objects


value
connections
tm_adm
entries
3.5 Additional SAP Parameters for Instance uccapp02_PRD_00

Work Processes
value
rdisp/wp_no_btc Number of background work 4 6
processes
rdisp/wp_no_vb Number of update work processes 0 1
processes
Database Interface
value
the Oracle
homedirectory'
3.6 Memory Configuration for Instance uccprdvci_PRD_00

J:\usr\sap\PRD\SYS\profile\PRD_DVEBMGS00_uccprdvci.
Buffer Settings
value
administrated
record buffer


value
buffer
screens
presentation buffer
objects

value
connections
tm_adm
entries
3.7 Additional SAP Parameters for Instance uccprdvci_PRD_00

J:\usr\sap\PRD\SYS\profile\PRD_DVEBMGS00_uccprdvci.
Work Processes
value
processes
Database Interface
value
the Oracle
homedirectory'

Database Performance
4 Database Performance
Major performance problems have been detected in your database system.
Please implement the recommendations provided in the following sections.
4.1 Database Parameters

In the configuration file initPRD.ora, replace the "current values" of the following database parameters with the
"recommended values" as shown in the tables below.
Changes to configuration parameters come into effect after your database has been restarted.

value
event Event for Cost-Based Optimizer Please refer to
Note 128648 and
SAP note 128221
Before changing the Oracle parameter EVENT, please check whether there are special reasons to set these
events (for example, the events 10235 and 10600 might be set temporarily to analyze a special problem) and
check the following SAP Notes in SAPNet.
NOTES FOR PARAMETER 'EVENT'

Note description
number
0128648 Other index than expected is used
0128221 Increased memory consumption with Oracle 8
NOTE FOR CURRENT ORACLE PARAMETER SETTINGS

Note Description
number
0124361 Oracle database parameter setting for R/3 4.x
0132503 Update of threshold values of database system chck
0170989 Views perform poorly (Oracle 8044 & 805* & 806)

value
db_block_buffers Size of data buffer as number of 46694 90000
data blocks
db_block_lru_latches Upper bound of the number of 1 4
LRU latch sets
log_checkpoints_to_alert Checkpoints logged in alert file FALSE TRUE
optimizer_search_limit Nr. of tables for which the 3 Delete this
optimizer considers join orders parameter name
and value from
database profile
processes Maximum number of database 100 190
shadow/background processes
sessions Maximum number of concurrent 110 230
database sessions
shared_pool_size Size of Shared Pool in bytes 255013683 400000000

Database Performance

value
shared_pool_reserved_size Part of Shared Pool for large 25501368 Delete this
statements parameter name
and value from
database profile
sort_area_size Max. memory in bytes taken by 65536 2097152
each shadow process for sorts
timed_statistics Switch on time-based monitoring FALSE TRUE
statistics?
transaction_auditing Generate audit information for TRUE FALSE
session and users
4.2 System Performance

4.2.1 Setup of the Temporary Tablespace
Some of the R/3 queries will require the usage of temporary tablespace (usually PSAPTEMP), for example, order
by, group by, aggregates. In order to ensure maximum performance and stability, it is important to set up the
temporary tablespace and the related data files properly.
Recommendation: For the setup of the temporary tablespace, follow the guidelines in SAP Note 164925.
Additionally, place the temporary tablespace in a separate device (disk) away from any other heavy used
data files, the online redo log files, or the archive directory. If the workload created by sort accesses is very
heavy, it may be beneficial to have the data files of the temporary tablespace on dedicated disks in a
separate controller.
Note Description
Number
0164925 Storage parameter of tablespace PSAPTEMP
0183791 Locking on temporary tablespace of Oracle
4.2.2 Missing Indexes

We have checked the system for indexes that are defined in the SAP Data Dictionary but do not exist on the
database. There is no such index in the system at present.
4.2.3 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.
The data distribution statistics of your database are not updated following the SAP strategy for parallel generation
of optimizer statistics. For optimal performance, perform a statistical update regularly.
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 SAP Note 184513.
Note: If your users/developers are allowed to create their own tables or indexes, we recommend that you
schedule the second phase of the SAP two-phase strategy (as described in SAP Notes 132861, 93098,
and 93256) daily. Because Oracle does not create statistics for newly created objects, these objects remain
without valid statistics until the next update run for the uptimizer statistics. Running the second phase of the
two-phase strategy daily will create only a very small overhead but will identify and refresh objects without
statistics.
Note Description
number
132861 CBO: Weekly scheduling with SAPDBA
184513 CBO: Parallel generation of optimizer statistics
93098 Changes to the upgrade to 4.0 - CBO Oracle
93256 CBO: Changes for installation of 4.0

Database Administration
5 Database Administration
Major problems regarding database administration have been found. Check the following sections for
problems and errors that may be caused by the way you administrate your database.
NOTE: A remote service cannot verify certain important aspects of your administration strategy, such
as your offsite storage of database backups and whether the backup tapes can be read correctly.
5.1 Backup Strategy

5.1.1 Backup Cycle
Right now there is no backup cycle in place yet.
Recommendation:
SAP strongly recommends using a backup cycle of at least 4 weeks. The more backups are available in
case of recovery, the better you are protected against physical tape errors and logical database errors.
5.1.2 Backup Frequency

According to the answers you provided on the GoingLive Questionnaire, you are planning to perform a full
database backup at the end of every business day. This meets the requirements established by the GoingLive
Check.
5.1.3 Archive Frequency

According to your answers in the GoingLive Questionnaire, you plan to archive your redo logs at least once a day,
which is the minimum required. We recommend that you make two additional copies of each redo log (for
example, by using the BRARCHIVE option "cds").
5.1.4 Backup Verification and Consistency Check

Recommendation: Performing a verification run of a backup at least once during the backup cycle to
detect problems in the restore scenario at an early point of time. Note that the verification run will double
the backup time. You should also check the database for corrupted blocks at least once during the backup
cycle, as described in SAP Note 23345. As of R/3 Release 4.0, you can use the Oracle tool DB Verify to
check the database for corrupted blocks using the option "-w use_dbv" of the brbackup and brrestore. If
backups are performed using BACKINT, use the option "-w only_dbv" instead (see SAP Note 155524).
To protect against data loss, you must have a correct backup strategy. It is crucial for your database to
have at least one backup with a subsequent verification available at any point of time. In addition to
security aspects, the maximum available downtime in case of recovery must also be taken into account
when planning a backup strategy.
In case of block corruption, the last verified successful backup may be needed for the restore and recovery
not the last successful one.
We recommend testing a restore and recovery scenario at least once before going live.
5.2 File Distribution Check

To ensure maximum data security and optimum performance, the Oracle database files must be distributed over
the available disks according to certain rules.
5.2.1 Mirroring of online redo log files

To increase data security, the online redo log files must be mirrored and the original online and mirrored online
redo log files must be located on different disks.
Recommendation: Verify that your Oracle online redo log files are mirrored either at the database level or
at the hardware level (RAID1).
5.2.2 Distribution of online and offline redo log files

For optimal performance, the online redo log files should be stored on disks that are separate from those where
the offline redo log files are located. Separating online from offline redo log files also increases data security.

Recommendation: Verify that all online redo log files in your installation are on disks that are separate
from those with offline redo log files.
5.2.3 Distribution of online redo logs and tablespace files

For optimum performance, the online redo log files should be on disks that are separate from those where the
tablespace data files are located. Separating tablespace data files from online redo log files also increases data
security.
Recommendation:
Please verify that no disk contains both online redo log files and tablespace data files.
5.2.4 Distribution of offline redo logs and tablespace files

To ensure minimal loss of data in case of disk failure, the offline redo log files must be on disks that are separate
from those where the tablespace data files are located. Otherwise, data loss cannot be ruled out, even if the
backup strategy is correct. Separating redo log files from tablespace data files also improves performance.
Recommendation:
Please verify that no offline redo log files are on the same disks as tablespace files.
5.2.5 Distribution of control file copies

For a database recovery you need a current version of the database control file. To make potential recoveries
easier, ensure that you always have a current version of the control file available, even in case of disk failure.
Recommendation: Verify that you have at least three control file copies located on different disks.
5.3 Space Management

5.3.1 Freespace in Tablespaces
You should have received an estimate of the initial and maximum size of the production database from your
hardware partner, and sized the planned production database according to these values. <*>
Recommendation:
To avoid production downtimes due to full tablespaces, and performance loss due to I/O hot spots, we
recommend that you set up your production database to the size expected after 1 year of production
operation. In particular tablespaces PSAPSTABD, PSAPSTABI, PSAPBTABD, and PSAPBTABI should
have adequate freespace and be distributed across several disks.
In addition, if the sizing performed by your hardware vendor indicates that certain tables will grow to over 2
GB, these should be located in their own dedicated tablespaces.
5.4 Extents of Tables and Indexes

5.4.1 Schedule 'sapdba -next' weekly
Recommendation: To minimize the allocation of new extents by table or index growth, schedule "SAPDBA
-next PSAP%" on a weekly basis. After SAPDBA -next has been executed, you should check for space-
critical objects. To do this, call transaction DB02 and refresh.
Background: SAPDBA adjusts the value of the storage parameter NEXT according the current size of the
table and the settings in the ABAP Dictionary. Increasing the value of NEXT results in fewer but larger
extents.
Note: For more information about SAPDBA -next, see SAP Note 28962.
5.5 Administration Management

5.5.1 Check sapdba -check schedule
SAPDBA with the option -check offers you an easy way to check for database problems specific to the SAP
environment.
Recommendation: Schedule SAPDBA -check to run daily during periods of low system activity, using
either the DBA Planning Calendar (transaction DB13) or by entering command sapdba -check at the
command prompt. After each run, check the log information written by the SAPDBA -check.

5.6 Further Database Recommendations

5.6.1 Oracle Memory Leak
Warning: Because of a bug in Oracle 8 (only when using SAP Basis Release 4.0 and higher), there may be a
major increase in memory consumption of the Oracle shadow processes on the database server (see SAP Note
128221).
To ensure that the Oracle bug does not affect your system, check the paging on the database server carefully after
going live. If the paging on the database server is abnormally high, implement SAP Note 128221.
5.6.2 SAP Tools

Recommendation: Implement the newest release of the SAP tools SAPDBA, BRBACKUP, BRARCHIVE,
BRCONNECT, BRRESTORE, and BRTOOLS from sapserv before the start of production. See SAP Notes
12741 and 19466.
5.6.3 Oracle Patch Sets

Recommendation: Apply the current Oracle patch set before the start of production. Note: If you upgrade
to Oracle 8.0.5, delete the parameter event = '10181...' from the profile and set parameter
optimizer_index_cost_adj to 10, as described in SAP Note 114716.
Note Description
number
184134 Current patch set for Oracle 8.0.6
5.6.4 Important Notes for Oracle

To optimize system performance and to prevent data loss or system downtime, implement the following SAP
Notes as soon as possible.
Note Description
number
0354080 Performance problems / Overview of Notes
0135048 CBO: Long runtimes statements w/ ROWNUM <= conditn
0184134 Current patch set for Oracle rel. 8.0.6
0128221 Increased memory consumption with Oracle 8
0339498 RESIZE or AUTOEXTEND can corrupt the Oracle dictionary
0353154 ALERT: Security problem of the Oracle Listener
0326743 RZ20: Oracle collecting tool causes expensive SQL

Server Checks
6 Server Checks
The server checks cover the correct operating system settings and a swap/paging space check for each server. To
ensure the stability of the SAP System, enough swap space must be available on the server where the SAP
System and the database run.
Note: Only SAP applications and the database should run on this server. If non-SAP applications are running, and
are using a significant amount of swap space, these applications are not recognized. We will only report the result
of the swap space check if a server does not have enough swap space.
6.1 Application Server uccapp01

Windows Operating System
NT Disk Performance Counters
Performance counters for disk I/O are only available if enabled. This enhances the possibilities to detect hardware
bottlenecks.
Recommendation: Enable NT disk performance counters.
Implementation: Proceed as described in SAP Note 8767: Use the NT command 'diskperf -y' to enable
counters. This changes registry settings and will be effective as of the next system startup.
Consequences: Gathering performance data for I/O causes some additional system load. With current
fast CPUs, this overhead is negligible.
Swap/Paging Space
Available Swap/Paging Space in MByte Recommended Swap/Paging Space in MByte
10000 12288
Recommendation: Increase the operating system paging space to at least the recommended size listed in
the above table.
6.2 Application Server uccapp02

bottlenecks.
Swap/Paging Space
Available Swap/Paging Space in MByte Recommended Swap/Paging Space in MByte
10000 12288
Recommendation: Increase the operating system paging space to at least the recommended size listed in
the above table.

Server Checks
6.3 Application Server uccprdvci

bottlenecks.

Further SAP System Checks
7 Further SAP System Checks
7.1 Software Logistics

A remote analysis of your production system and the settings related to software logistics has been made. Our
comments and recommendations follow.
System Landscape and TMS

System Landscape and Domain
The following system landscape and TMS configuration was derived from your production system PRD in order to
review the change and transport system in your production system.
Transport Domain Configuration
Domain Name Domain Controller Domain Description

DOMAIN_PRD PRD Transport domain PRD
Systems in Domain
Domain Name System Name Transport Group

DOMAIN_PRD PRD GROUP_PRD
Clients
Defined Clients
The following clients exist in the production system.
Client Description
000 SAP AG
001 Auslieferungsmandant R11
066 EarlyWatch
Client-dependent change option

The client attributes for the production client allow the client-dependent Customizing settings to be set accordingly.
Recommendation: To ensure a stable production environment, set the client attributes to prevent
Customizing setting changes.
Background: Customizing setting changes should be performed in the development client. The results
should then be tested and verified in the quality assurance environment, and finally transported to the
production client. This ensures consistent Customizing across all clients in the system landscape.
Note: If it is necessary to perform specific client-dependent Customizing tasks from within the production
client (see SAP Notes 38737 and 77430), use authorizations to ensure that these changes can only be
performed by the appropriate users.
Client-indep. Customizing and Repository Objects

The client attributes for one or more clients in your production environment allow the client-independent
Customizing and/or Repository objects in the production system to be changed.
Recommendation: To ensure a stable production environment, set the client attributes to prevent changes
to client-independent Customizing and Repository objects.
Background: Changing Customizing and Repository objects should be performed in the development
client. The results should then be tested and verified in the quality assurance environment, and finally
transported to the production client. This ensures consistent Customizing across all R/3 Systems in the
system landscape.

Category
The client category 'Production' is not assigned to the production client. The client category is maintained for
documentation and to ensure appropriate use of the client.
Recommendation: Use the client maintenance functions to set the category of your production client to
'Production'.
Background: If a production client exists in a target system, R/3 ensures that client transports from other
systems that include client-independent Customizing objects are not imported into the target system.
Importing settings that affect all clients can result in inconsistencies in the production client. In the future,
SAP will link additional functions - based on the client category - to ensure more production client security.
Copy protection
The client attributes allow the client copy to overwrite the production client. This means a client copy can delete all
contents of a client prior to introducing new client settings and data.
Recommendation: To ensure that the production client is not accidentally overwritten by a client copy,
modify overwritten client attributes for the production client using the client maintenance function.
CATT
The production client settings allow CATT procedures.
CATT procedures in a production client can cause data inconsistency and poor performance.
Recommendation: Change the production client attributes using the client maintenance functions so that
CATT procedures are not allowed.
Change Management and Modifications

Changes in the production system
Change requests have been created in the production system.
Recommendation: Change requests should only be created in the development system, and transported
from there to the other systems in your system landscape, as defined in the transport system. To avoid
making changes in the production system, use the client attributes and the system change option
appropriately. If it is necessary to make changes in the production system, verify that these changes are
also distributed to all other systems in the system landscape.
Documentation of Modifications
To be able to decide how to adjust modifications for an upgrade of your SAP system, you should always record
the purpose and source of these modifications. Documentation can consist of comments in the source code or in
the related change request, or an external written log.
Recommendation: Always document modifications. If your modifications are based on SAP-supplied error
corrections, document the SAP Notes and release dependencies you used.
Installed Software Components and SAP Support Packages

These are the components that are installed in your SAP System.
Software Components Component Release Type

SAP_ABA 46C C
SAP_APPL 46C C
SAP_BASIS 46C C
SAP_HR 46C C
SAP Support Packages

SAP Support Packages contain collections of corrections that should be performed in the SAP System. SAP
Support Packages are available to all customers through SAPNet - Further R/3 Frontend (Service -> SAP Patch
Service) and SAPNet - Web Frontend (SAPNet alias ocs-download). You can apply SAP Support Packages using
the SAP Patch Manager (transaction SPAM).

SUPPORT PACKAGE LEVEL OF COMPONENTS

Patch Type of Patch Description
SAPKA46C16 COP ABA Support Package 16 for 4.6C
SAPKB46C16 COP Basis Support Package 16 for 4.6C
SAPKH46C16 COP R/3 Support Package 16 for 4.6C
The Support Package Level of Components table displays the current status of your SAP System with respect to
Support Packages.
7.2 Important periodic jobs

Certain jobs must run periodically in a production R/3 System - for example, deleting obsolete jobs or spool
objects. If these periodic jobs are not run, system performance may get worse over time. Unfortunately, there is
currently no easy-to-use support for such jobs in Basis Customizing. Therefore, the jobs must be scheduled
manually. For more information, see SAP Note 16083.

Preparations for the next sessions
8 Preparations for the next sessions
8.1 Preparations for Optimization Session

The Optimization Session is the second session of the SAP GoingLive Check. During this session, the core
business transactions you are using are checked.
Recommendation: To prepare for the session, perform the steps described in the following sections.
Focus of the Optimization Session

The Optimization Session of the SAP GoingLive Check will focus on the following modules:
MM and SD especially the folowed transaction codes:
Scheduling Agreement - VA31
Delivery - VL01N
Billing - VF01
Purchase Order - ME21N
ERS - MRRL
To prepare the session, we need more information on your implementation.

Recommendation: Fill out the questionnaire and return it at least two weeks before the scheduled date of
the session.
Note: The questionnaires are available in SAPNet R/3 Frontend. Choose Service -> Remote Services and
click on the icon indicating that a questionnaire needs to be filled out. Download the attached document
and upload the completed document.
System of the Optimization Session

You have stated that the Optimization Session of the SAP GoingLive Check will be performed on the production
system.
Recommendation: Ensure that the core business processes can be performed on the session day. Before
the session is performed, a Service Engineer will agree details with you.
Buffer Configuration
You have stated that the Optimization Session of the SAP GoingLive Check will be performed on the production
system that was analyzed in the Analysis Session.
Recommendation: Before the Optimization Session, implement the recommendations from the Analysis
Session.
Background: The buffer settings must be optimal in order to perform the SQL Trace Analysis in the
Optimization Session.
Important Notes for Financals

Severe performance problems can occurr in mySAP Financials.
Recommendation: Implement the SAP Notes below to optimize performance.
SAP Note Description

145647 F110: Performance and deadlocks in payment program
332402 FFI: deadlocks/long lock times for FDSR and FDSB

Further Recommendations
9 Further Recommendations
9.1 SAP Notes: Performance 4.6

Consider the following SAP Notes to prevent or solve performance problems that may occur with R/3 Release 4.6.
For network sizing issues, refer to the document "Network Load for Release 4.6". You can find this document in
the Service Marketplace under Hardware Sizing -> Media Center -> Literature.
Note number Description

203924 Collective Note: Performance 4.6
178616 Resource Requirements for Release 4.6 B/C
26417 SAPGUI Resources: hardware and software
103747 Performance 4.0/4.5/4.6: Parameter recommendations
203617 High memory consumption with Easy Access menu
164102 Network load between app-servrs + front-end
9.2 EarlyWatch Alert

You have not set up the SAP EarlyWatch Alert Service in your system yet.
Recommendation: Set up the new SAP EarlyWatch Alert Service as described in SAP Note 207223.
Background: With this new service, performance and monitoring data is processed in regular intervals (for
example, weekly) and several checks are performed automatically. The EarlyWatch Alert reports provide
you with a detailed trend analysis of important performance indicators of your system. You can view the
results online.
Note: This service is free of charge and runs in the same environment as the EarlyWatch Service provided
by SAP.

SAP GoingLive Analysis

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP GoingLive Analysis

Încărcat de

Drepturi de autor:

Formate disponibile

Service Report

SAP® GoingLive™ Check

SAP System ID PRD

SAP Component SAP R/3

DB System ORACLE 8.0.6

Modules CO EC FI FI-AA MM MM-WM PM PP SD

Customer Alsons Cement Corporation 3/F Alsons

Service Center SAP Support, Malaysia

Date of Session 05.04.2001 <dat_dummy> Session No. 0010000198094

4. Periodic Housekeeping Jobs Must be scheduled as per R/3 note. 16083.

Next Session - Optimization Session

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 2

2. The users must be available to run these transactions/programs for TCC.

Thank you for your cooperation and understanding.

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 3

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 4

QUESTIONNAIRE INFORMATION ............................................................................................................... 8

3.1 SAP KERNEL RELEASE .................................................................................................................. 11

4.1 DATABASE PARAMETERS................................................................................................................. 15

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 5

5.1 BACKUP STRATEGY ........................................................................................................................ 17

6.1 APPLICATION SERVER UCCAPP01.................................................................................................... 20

7.1 SOFTWARE LOGISTICS .................................................................................................................... 22

8.1 PREPARATIONS FOR OPTIMIZATION SESSION ................................................................................... 25

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 6

9.1 SAP NOTES: PERFORMANCE 4.6 .................................................................................................... 26

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 7

Concurrent Users in the Production System

Module CO EC FI FI-AA MM MM-WM PM PP

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 8

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 9

2 Hardware Plausibility Check

Recommended Active User Distribution

Instance CO EC FI FI-AA MM MM-WM PM PP

Recommended Work Process Distribution for R/3

Instance Name Dialog Batch Update Update2 Spool Enqueue

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 10

3 SAP System Configuration

3.1 SAP Kernel Release

3.2 Memory Configuration for Instance uccapp01_PRD_00

Client Server Communication

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 11

Parameters Description Current value Recommended

3.3 Additional SAP Parameters for Instance uccapp01_PRD_00

3.4 Memory Configuration for Instance uccapp02_PRD_00

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 12

Client Server Communication

3.5 Additional SAP Parameters for Instance uccapp02_PRD_00

3.6 Memory Configuration for Instance uccprdvci_PRD_00

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 13

Parameters Description Current value Recommended

Client Server Communication

3.7 Additional SAP Parameters for Instance uccprdvci_PRD_00

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 14

4.1 Database Parameters

Parameters Description Current value Recommended

NOTES FOR PARAMETER 'EVENT'

NOTE FOR CURRENT ORACLE PARAMETER SETTINGS

Parameters Description Current value Recommended

GoingLive Check Report , Alsons Cement Corporation 3/F Alsons, 05.04.2001 15

Parameters Description Current value Recommended

4.2 System Performance

4.2.2 Missing Indexes

4.2.3 Optimizer Statistics