2UDFOHRQ8QL[DQG:LQGRZV17
Release 4.0B
R
SAP Labs, Inc.
Palo Alto, California
Overviewing R/3 System and Roles
Overview
1998 SAP Labs, Inc. 151
Chapter 15: Overviewing R/3 System and Roles
Contents
Overview............................................................................................................................................................................................................151
System Landscapes..........................................................................................................................................................................................151
The One-System Landscape.......................................................................................................................................................................152
The Two-System Landscape.......................................................................................................................................................................153
The Three-System Landscape....................................................................................................................................................................154
Client Definition.................................................................................................................................................................................................154
Role of the Client...............................................................................................................................................................................................154
Transports for System Landscape Maintenance.........................................................................................................................................155
Client Copy versus Client Transport ...............................................................................................................................................................156
Transporting Clients ....................................................................................................................................................................................156
Copying Clients ...........................................................................................................................................................................................157
Deleting a Client ................................................................................................................................................................................................157
Useful OSS Notes..............................................................................................................................................................................................157
Overview
Begin the implementation of SAP by defining all R/ 3 Systems and clients necessary for your production
environment. Depending on the size of your R/ 3 installation and the projects planned, you may require
several R/ 3 Systems that serve different purposes in your system group. These systems form the system
landscape, and clients are distributed within this landscape. Once the system landscape is defined, an
implementation strategy is needed to setup and maintain the systems and clients.
System Landscapes
In general, there are three kinds of system landscapes:
One-system
Two-system
Three-system
The following sections describe these different types and the advantages and disadvantages of each.
Overviewing R/3 System and Roles
System Landscapes
152 1998 SAP Labs, Inc.
A client is a commercially and organizationally independent unit in the R/ 3 System, which means that it
has its own data environment. In general, four different types of clients exist, and each type has a different
functionality, as illustrated below:
CUST Customizing and development client
TEST Unit test client
QTST - Quality assurance testing
PROD - Production client
The One-System Landscape
Because all clients in a one-system landscape reside in the same R/ 3 System but are used for different
purposes (development, testing, master copy, and production), SAP strongly recommends that customers
do not use this configuration. The obvious advantage to this landscape is that there is less hardware to
purchase and maintain for a single R/ 3 System. In the long run, however, the initial savings do not pay
off because of the problems and limitations associated with this configuration. Another notable
disadvantage is that it is not possible to test a R/ 3 upgrade in a single-system landscape. Please see the
following list for additional advantages and disadvantages.
Advantages
Minimal hardware resources
Fewer administrative requirements
Disadvantages
Development immediately effects production environment
Global customizing will immediately affect production
Other clients can impact production performance
Upgrades of production without suitable testing
Not possible to test a R/ 3 upgrade in a one-system landscape
CUST
TEST
PROD
Development & Production
QTST
Overviewing R/3 System and Roles
System Landscapes
1998 SAP Labs, Inc. 153
As a consequence of these limitations, no further development is possible after production work has
started. Changes to repository objects can only be made when production operations are stopped for
development and testing. If the system is stopped, the production downtime could adversely affect your
company.
The Two-System Landscape
CUST
TEST
PROD
Development
Production
QTST
A two-system landscape allows development and production to be performed in two separate systems.
Development and testing must still take place in the same system, which means that development and
testing activities could interrupt each other. Normally, SAP recommends using a three-system landscape,
but the minimum requirement for most needs is a two-system landscape.
The limitations of the two-system landscape arise because development and quality assurance testing
must both take place in the development system. Since no separate quality assurance system is available,
all objects transported to the production system immediately become active. Complicated development
projects often involve transporting partial functionality, without always taking dependencies into account.
This step can cause inconsistencies in the production system and affect the production process.
The following list provides additional advantages and disadvantages.
Advantages
Production data secure
Production performance not affected by other clients
Development efforts separate from production
Disadvantages
Development and quality assurance testing within the same system
Transport of changes from the development system immediately become active in production
Inability to verify the transport contents
Overviewing R/3 System and Roles
Client Definition
154 1998 SAP Labs, Inc.
The Three-System Landscape
The recommended three-system landscape is the one most commonly used, and can meet the needs of
most customers. In a three-system landscape, new developments can be tested without affecting the
production environment, and upgrades can be performed without limitations. The quality assurance
system integrates development efforts and allows you to check the validity and consistency of transported
objects before moving them into production.
Ideally, client roles should be distributed across three different R/ 3 Systems.
Advantages
Production data secure
Production performance not affected by other clients
Independent test environment
Transports are verified before delivery to production
Disadvantages
An increase in hardware requirements
Client Definition
A client represents a commercially and organizationally independent unit in the R/ 3 System with its own
separate data environment, including:
Customizing
Master and transaction data
User master records
The client can be formed under legal, economic, or administrative perspectives. All business data is
protected against access by other clients. The client is characterized by a three-digit client number.
Role of the Client
The role of a client indicates whether a production, test, training, demonstration, or prototype client is
involved. When you configure a client, the attribute role of the client can be used to describe its use.
CUST
TEST QTST PROD
Development
Quality Assurance Production
Overviewing R/3 System and Roles
Role of the Client
1998 SAP Labs, Inc. 155
The following clients can exist in a R/ 3 System:
Customizing client Used for customizing the R/ 3 System
Test client Enables you to unit test Customizing
Quality Assurance client Checks the validity and consistency of transported objects before moving
them into production.
Production client Used for production work
Transports for System Landscape Maintenance
Use the following tools to setup a system landscape:
Change request: All newly created or changed Repository objects are collected in change requests. The
contents of these change requests can be transported together to another R/ 3 System.
Client copy: The client copy tool copies all client dependent customizing applications and user
data to another client in the same R/ 3 System. The tool depends on profiles, allowing
for variations in which data is actually included in a client copy.
Client transport: The client transport tool can transport most of the customizing settings (both client-
independent and client-dependent), application data, and user master data to
another R/ 3 System. Like the client copy tool, client transport requires a profile for
definition of inclusion.
To establish a three-system landscape, you will need to use the transport tools:
Use the client copy tools to setup additional clients in the same system.
Use client transports to copy a client from one system to another.
Overviewing R/3 System and Roles
Client Copy versus Client Transport
156 1998 SAP Labs, Inc.
Use change requests to allow new or modified Repository objects and customizing to be imported into
other systems.
To transport a client to another system:
With a profile select the data to be copied
Export the data to a transport file
Import the data into the target system
Adapt the runtime environment to the current state of the data (if client validation exits)
Client Copy versus Client Transport
There are two ways to copy a client:
Client transport
Client copy
During a client transport, the client is exported out of one R/ 3 System and imported to a different R/ 3
System. During a client copy, a client is replicated within the same R/ 3 System to make a new client. The
diagram below illustrates the two processes:
Client Transport
Client Copy
R/3 Sys. 1
R/3 Sys. 1
R/3 Sys. 2
Client 2
Client 2
Client 1
Client 1
Transporting Clients
The client copy and client transport tools are necessary to actual setup various systems. Client copies
provide a mechanism to duplicate a client in the same R/ 3 System. Client transport allows the movement
of a client from one R/ 3 System to another.
There are two types of client transportsa client export (also refer as client transport) and a remote client
copy. We will discuss client export in chapter 17 of this guidebook. A client transport involves extracting
client-dependent information from the database to a file on the hard drive. This file can then be later
imported into any number of R/ 3 Systems.
Overviewing R/3 System and Roles
Deleting a Client
1998 SAP Labs, Inc. 157
When a client is copied to another system, by default, the client-independent tables are not copied.
However, when you setup a new system, ensure that all customized tables are transported. Select the
option for client-independent tables when performing client-transport.
Copying Clients
The Client Copy tool allows you to copy the customizing environment of a source client to a target client.
To setup the new client:
Prior to client copy, delete the target client
Copy the data from the source client to the target client.
Schedule subsequent processing activities to regenerate the runtime environment (client validation
exits). Reports, screens and name ranges have to be adapted to the current state of the data.
Significant time is required to copy the data because all the client-specific data in the R/ 3 system has to be
replicated. When copying just the customizing data, up to 150 MB is involved, so the process only requires
a few hours (depending on the hardware and system load). Because of time considerations, we
recommend that you execute the client copy program in the background.
You can view the status of an online copying process on the monitor. The status of a background process
can be requested with transaction SCC3 at any time.
Due to its long runtime, the client copy program, if processing is aborted, allows you to restart at any
point.
Deleting a Client
Two different methods exist to delete a client. You can perform the deletion either at the operating system
level or from within the R/ 3 System. The following chapters detail both methods.
Useful OSS Notes
Note # Description
70547 CC-TOPIC: Client transport
70128 CC-TOPIC: Info/ Docu/ Help for copying clients
62739 Configuring a central transport host
40672 System changeability and client control
31557 The multi-client concept of R/ 3 Overview
05206 Client compare for tables: Which tool?
Overviewing R/3 System and Roles
Useful OSS Notes
158 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
Installing a Central Instance of SAP R/3 Version 3.1H with Oracle on Windows NT (Ch. 5)
Completing and Checking the Central Instance Installation of R/3 With Oracle on Win. NT (Ch. 6)
Overviewing Customization and Workbench Development (Ch. 71)
Using the Customizing Organizer for IMG Customization (Ch. 72)
Using the Workbench Organizer to Modify an ABAP/4 Program (Ch. 73)
R/3 Basis Knowledge Products
SAP Software Logistics CD Reference Pre-Installation Systems and Roles
Technical Implementation Pre-Installation Roles and Responsibilities,
System and Roles
Technical Implementation Implementation Define Procedures
Basis Courses
Workbench Organizer, Transport System & Upgrade (BC325)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Copying a Client within a R/3 System
Overview
1998 SAP Labs, Inc. 161
Chapter 16: Copying a Client within a R/3 System
Contents
Overview............................................................................................................................................................................................................161
Creating a New Target Client within the Source Client .................................................................................................................................161
Performing the Client Copy in the New Target Client....................................................................................................................................166
Viewing the Client Copy Activities ..................................................................................................................................................................169
Useful OSS Notes............................................................................................................................................................................................1613
Overview
When a separate client is needed to test, customize, or train, you can create this client by copying an
existing one. During the client copy, ensure that:
The tables copied are not changed in the source client
No one is working in the target client
The following example will show you how to copy client 000 to client 100. Client 100 is used later as a
development/ customizing client.
Creating a New Target Client within the Source Client
Login to the source client (for example,
000).
1. Enter the Source Client number in
the Client field.
2. Enter DDIC in the username field.
3. Enter the password for DDIC.
4. Press Enter to accept the user
default language or enter a
language code (e for English.)
1
2
3
4
Copying a Client within a R/3 System
Creating a New Target Client within the Source Client
162 1998 SAP Labs, Inc.
5. Choose Tools Administration
Administration Client admin.
Client maintenance.
Alternative:
6. Choose Table View Display
Change.
7. Click Enter.
8. Click the New entries button to
create a new target client.
5
6
7
8
Copying a Client within a R/3 System
Creating a New Target Client within the Source Client
1998 SAP Labs, Inc. 163
9. Enter the new target client number
(any new three digit number, for
example, 100).
Do not use client numbers 000, 001, or
066 for your new clients because they
are reserved by SAP.
10. Enter the new client name.
11. Enter the City in which the client is
located.
The Logical System field applies
only to the ALE application.
12. Enter a currency code in the Std
currency field (enter usd for U.S.
dollars).
13. Enter a category (in this example,
Customizing).
14. Because this client will be used for
development/ customization, select
Automatic Recording of Changes
15. Click the possible entries button to
select Changes to Repository and
client-ind. customizing allowed.
16. Click the Save icon to proceed to the
next screen.
17. Click the Back icon to return to
previous screen.
For more information about the Client-
independent object changes field, position
the cursor in this field and press F1.
9
10
11
12
13
14
15
16 17
Copying a Client within a R/3 System
Creating a New Target Client within the Source Client
164 1998 SAP Labs, Inc.
The chart below defines when certain change options can be used. It can serve as a helpful reference and
provide examples of the change options for both clients and systems. The X indicates for which clients or
systems the attribute may be used. Notice that multiple attributes may apply to some clients or systems. In
such a situation, the most appropriate attribute depends on the landscape structure.
Clients: DEV TEST QTST PRD TRAIN SANDBOX
Client -dependent change opt ions
Changes w/ o automatic recording X
Automatic recording of changes X
No changes allowed X X X
No transports allowed X X
Client -independent change opt ions
Changes to Repository and client-
ind. customizing allowed
X
No changes to client-independent
customizing objects
X X
No changes to Repository objects X X
No changes to Repository and
client-independent custom obj.
X X X X X
DEV Development client (development/ customizing)
TEST Unit test client
QTST Quality Assurance or Test client (to test the customization or new development)
PRD Production Client (used as daily production)
TRAIN Training Client (used to train end users in the use of the customer-specific
developed/ customized functions)
SANDBOX Playground client (test other advanced R/ 3 function, self-train, etc.)
Copying a Client within a R/3 System
Creating a New Target Client within the Source Client
1998 SAP Labs, Inc. 165
18. You should see the new target
client in the list.
19. Enter the transaction /nEND to exit
the system.
20. Click Yes.
Before you begin the actual copy process, do the following:
Turn Archiving off in the database by using sapdba (see chapter 109, Changing the Archive
Mode).
Check your available tablespace allocation with transaction code DB02 (see chapter 92,
Analyzing Current Tablespaces Sizes. You may need to expand these tablespaces by adding
a datafile using sapdba. When finished, refresh the statistics to get an accurate result.
We recommend that you first perform a test run:
1. Go to transaction code SCCL
2. Check the test box
3. Run the copy
4. Ensure a successful run
Remember, a client copy test run can take just as long as the actual client copy.
Since the operation is computationally intensive, client copies should be run when users
are not on the system.
18
19
20
Copying a Client within a R/3 System
Performing the Client Copy in the New Target Client
166 1998 SAP Labs, Inc.
Performing the Client Copy in the New Target Client
To logon to the R/ 3 System:
1. Enter the client number in the
Client field (in this example, 100).
2. Enter sap* in the username field.
3. Enter the password for SAP*.
4. Press Enter to accept the user
default language or enter a
language code (e for English.)
5. Choose Tools Administration
Administration Client admin.
Client copy Local client copy.
Alternative:
6. In the Selected profile field, enter
SAP_ALL to copy data from the
source client (in this example,
SAP_USR).
7. Enter the Source client number (in
this example, 000).
8. Click the Execute in backgrd. button
to run the client copy as a
background job.
1
2
3
4
5
6
7
8
Copying a Client within a R/3 System
Performing the Client Copy in the New Target Client
1998 SAP Labs, Inc. 167
The following profiles are delivered from SAP:
PROFILE DESCRIPTION
SAP_ALL All data of a client.
SAP_APPL All Customizing data and application data, incl. the user profiles are copied.
SAP_CUST All Customizing tables, incl. the user profiles are copied.
SAP_UAPP All Customizing data and application data, incl. the user profiles and user data are
copied.
SAP_UCUS All Customizing tables, incl. user master data and user profiles are copied.
SAP_USR Authorization and user masters.
9. Click Schedule job.
10. In the Verification screen, click Yes.
9
10
Copying a Client within a R/3 System
168 1998 SAP Labs, Inc.
11. To schedule the job to run
immediately, click the Immediate
button. Otherwise, select Date/Time
to choose an appropriate start time
(in this example, click Immediate).
12. Click the Save icon.
13. Enter an Output device (in this
example, LP01).
14. Click the Save button.
The message The background job was
successfully scheduled; result displayed
in SCC3 appears.
Depending on the size of the R/ 3 client and profile that you selected, client copy could take
from five minutes (if copying authorization and user masters only) up to a few hours.
11
12
13
14
Copying a Client within a R/3 System
Viewing the Client Copy Activities
1998 SAP Labs, Inc. 169
Viewing the Client Copy Activities
Follow this step-by-step procedure to ensure that your client copy was successful:
1. From the System Administration
window, choose Administration
Client admin. Copy logs.
Alternative:
2. To see the client copy activity detail,
first select the desired target client
(in this example, 100) by positioning
the cursor on its line.
3. Click Choose.
After the client copy is completed,
the Status text should read
Successfully completed.
4. After the process is completed,
position the cursor on the line item
containing your source client.
5. Click Choose.
1
2
3
5
4
Copying a Client within a R/3 System
Viewing the Client Copy Activities
1610 1998 SAP Labs, Inc.
A Log Analysis screen appears that
shows the client copy.
6. Click the Log button to see a
detailed analysis of the client copy.
6
Copying a Client within a R/3 System
Viewing the Client Copy Activities
1998 SAP Labs, Inc. 1611
This screen shows a detailed log of
the client copy.
7. To view the log in even greater
detail, click the Display more button.
This step increases the number in
the Expand level in overall log field (1
is the lowest level, 4 is the highest
level).
7
Copying a Client within a R/3 System
Viewing the Client Copy Activities
1612 1998 SAP Labs, Inc.
This screen shows the most
detailed log (level 4) of the client
copy.
If your client copy fails:
1. Examine your tablespaces with DB02, and then refresh the statistics to get current
information. Refer to chapter 92, Analyzing Current Tablespaces Sizes.
2. Check your archive directory <drive>:\ oracle\ saparch. If it is full, you have an archive
stuck condition. Using sapdba, backup the saparch directory and rerun the client copy
with archive mode set to off.
Copying a Client within a R/3 System
Useful OSS Notes
1998 SAP Labs, Inc. 1613
Useful OSS Notes
Note # Description
70290 CC-INFO: Exceptions in the client copy
70128 CC TOPIC: Info/ Docu/ Help for copying clients
67205 CC INFO: Copying large, productive clients
For further details refer to
R/3 System Administration Made Easy
Deleting a SAP Client Using a SAP Executable (Ch. 19)
Deleting a Client Using R/3 Functionality (Ch. 20)
R/3 Basis Knowledge Products
System Logistics CD Reference Pre-Installation Systems and Roles Setting Up a System
Landscape
R/3 System Online Help
Online Documentation CD Transport Control Using the R/3 Transport Program R/3 Transport:
General Information
Basis Courses
Workbench Organizer, Transport System & Upgrade (BC325)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Transporting a R/3 Client to another R/3 System
Overview
1998 SAP Labs, Inc. 171
Chapter 17: Transporting a R/3 Client to another R/3 System
Contents
Overview............................................................................................................................................................................................................171
Creating the Transport Request ......................................................................................................................................................................171
Scheduling the Client Transport Background Job ........................................................................................................................................174
Checking the Transport Log ............................................................................................................................................................................178
Useful OSS Notes............................................................................................................................................................................................1711
Overview
This chapter describes the first part of the export process, creating a transport request with transaction
SCC8. The process is completed when the client is imported to the target R/ 3 System (see chapter 18,
Importing a Client from another R/3 System).
Transporting a R/ 3 client from one R/ 3 System to another involves the following steps:
The export described in this chapter
The creation of the client entry described in Creating the Target Client (chapter 18)
The import described in Importing the Data into the Target R/ 3 System (chapter 18)
The post-processing activities described in Performing Post Import Activities (chapter 18)
When you export from a R/ 3 client, transport client data from one R/ 3 System to another. This process is
different from a client copy were a duplicate client is made within the same System. Exported files are
found in the <drive>:\ usr\ sap\ trans\ data and <drive>:\ usr\ sap\ trans\ cofiles directories. The following
step-by-step procedure shows how to export a R/ 3 client.
Creating the Transport Request
Login to the client that you want to
export.
1. Enter the client number in the
Client field (in this example, 001).
2. Enter DDIC in the username field.
3. Enter the password for DDIC.
4. Press Enter to accept the user
default language or enter a
language code (e for English.)
1
2
3
4
Transporting a R/3 Client to another R/3 System
Creating the Transport Request
172 1998 SAP Labs, Inc.
5. Choose Tools Administration
Administration Client
admin. Client transport Client
export.
Alternative:
SCC8 is the preferred transaction
instead of SCC2.
6. From the Selected profile field, click
the possible entries button to list the
default profiles.
7. Based on the Description, click the
Profile name containing the
elements you want to transport (for
example, SAP_CUST).
8. Click Choose.
5
6
7
8
Transporting a R/3 Client to another R/3 System
Creating the Transport Request
1998 SAP Labs, Inc. 173
9. From the Target system field, click
the possible entries button to list the
choices.
10. Select the target system
identification, <SAPSID> (in this
example, PRD).
11. Click Choose.
12. Click the Enter button to review the
parameters.
9
11
10
12
Transporting a R/3 Client to another R/3 System
Scheduling the Client Transport Background Job
174 1998 SAP Labs, Inc.
Scheduling the Client Transport Background Job
1. Ensure that the Selected profile
entries are correct.
You can now select the Test run
checkbox to ensure that you have
correctly configured everything
before transporting the client.
2. Click Execute in backgrd.
3. Click Schedule Job to schedule the
background job to transport client
001.
1
3
2
Transporting a R/3 Client to another R/3 System
Scheduling the Client Transport Background Job
1998 SAP Labs, Inc. 175
4. Verify the parameters, then click
Yes to continue.
An INFO client export screen
appears.
5. After reading the instructions, click
Enter.
4
5
Transporting a R/3 Client to another R/3 System
Scheduling the Client Transport Background Job
176 1998 SAP Labs, Inc.
6. Click Immediate to start the job.
7. Click the Save icon.
6
7
Transporting a R/3 Client to another R/3 System
Scheduling the Client Transport Background Job
1998 SAP Labs, Inc. 177
8. From the Output device field, click
the possible entries button to list the
choices.
9. Click Save.
The messages Format set to
X_65_132 and The background job
was successfully scheduled; result
displayed in SCC3 appears.
10. Do not panic if you see this screen.
It means that the client copy has
already started and is preventing
two client copies from running
together.
When you see this screen, simply
click OK.
8
9
10
Transporting a R/3 Client to another R/3 System
Checking the Transport Log
178 1998 SAP Labs, Inc.
Checking the Transport Log
To monitor the progress of the client export:
1. Choose
Tools Administration Administr
ation Client admin. Copy logs.
Alternative:
2. In the beginning the Status text
should display Initializing
3. To refresh the status, enter the
transaction /nSCC3.
3
2
1
Transporting a R/3 Client to another R/3 System
Checking the Transport Log
1998 SAP Labs, Inc. 179
While you wait for the export process,
invoke Qslice.exe (a program that is
included in the Microsoft Resource Kit)
to monitor the progress of the process
online. The graphics at the right-hand
side shows you that Oracle73.exe and
r3trans.exe are currently active. The bar
shows you the CPU usage by the
programs.
The Client Copy Log Analysis screen
appears. Ensure that the Status text
says Successfully completed for the
Target Client EXP.
4. Click once on the log entry of the
EXP client transport that just
completed.
5. Click Choose.
4
5
Transporting a R/3 Client to another R/3 System
1710 1998 SAP Labs, Inc.
6. Click once on the line item again.
7. Click Choose.
A summary of the Client Copy Log
Analysis appears.
To view the complete technical
information on the export process, click
the Log button.
6
7
Transporting a R/3 Client to another R/3 System
Useful OSS Notes
1998 SAP Labs, Inc. 1711
Useful OSS Notes
Note # Description
70547 CC-TOPIC: Client transport
70128 CC-TOPIC: Info/ Docu/ Help for copying clients
For further details refer to
R/3 System Administration Made Easy
Importing a R/3 Client from another R/3 System (Ch. 18)
R/3 Basis Knowledge Products
Software Logistics CD Reference Implementation QA Procedures Planning Imports
R/3 System Online Help
Online Documentation CD System Administration Transport System/Transport Control
Basis Courses
Workbench Organizer, Transport System & Upgrade (BC325)
Importing a R/3 Client from another R/3 System
Overview
1998 SAP Labs, Inc. 181
Chapter 18: Importing a R/3 Client from another R/3 System
Contents
Overview............................................................................................................................................................................................................181
Before You Begin..............................................................................................................................................................................................181
Creating the Target Client ................................................................................................................................................................................182
Sharing the Transport Directory of the Source R/3 System in the Target R/3 System...............................................................................186
Importing the Data into the Target R/3 System..............................................................................................................................................188
Performing Post-Import Activities...................................................................................................................................................................189
Checking the Import Logs..............................................................................................................................................................................1812
Useful OSS Notes............................................................................................................................................................................................1816
Overview
The goal of performing a client export and import is to move a client between two R/ 3 Systems.
Importing of a client from another system depends upon the exporting process explained in chapter 17,
Transporting a R/3 Client to another R/3 System, which describes how to export a client with transaction
SCC8. The end of the export process results in files created in the source systems directories.
<drive>:\ usr\ sap\ trans\ cofiles
<drive>:\ usr\ sap\ trans\ data
The target R/ 3 System shares these files so that a transport can be performed. In the following example,
certain assumptions are made:
Source R/ 3 System: PNSFO36
Source <SAPSID>: DEV
Source Client: 001
Target R/ 3 System: DODGERS
Target <SAPSID>: PRD
Target Client: 100
Before You Begin
Check if the transport file tpparam in directory <drive>:\ usr\ sap\ trans\ bin is correctly configured.
Ensure that the transport system has been initialized with transaction SE06.
Importing a R/3 Client from another R/3 System
Creating the Target Client
182 1998 SAP Labs, Inc.
You cannot reverse or undo a transport! SAP does provide such a function in the transport
system. The R3trans function SAFETYEXPORT will not provide this functionality because:
The order of transport requests being reloaded would have to be the exact opposite of the
import sequence. This reason alone makes reversing individual transports impossible.
The transport process includes actions that are irreversable, especially (but not limited to):
- Executing XPRAs (eXecute PRogram After import)
- Structure changes in the database (new tables, fields, indices)
- Mixed transport of INSERTs and DELETEs
If an error occurs, the alternatives are to restore a data backup or continue onwards. If you
regularly perform large or critical transports, it makes sense to first import to a test system.
Creating the Target Client
Logon to any client (for this example, we use client 000) of the target R/ 3 System as user SAP*. Then follow
the step-by-step procedure below to create the target client:
1. Choose Tools Administration
Administration Client
admin. Client maintenance.
Alternative:
2. Click the Display/Change button.
The message Warning: the table is
client-independent (see Help for
further Info) appears.
1
2
Importing a R/3 Client from another R/3 System
Creating the Target Client
1998 SAP Labs, Inc. 183
3. Click New entries.
4. Enter the new target client number
(any new three digit number, for
example, 100).
Do not use 000, 001, or 066 for your
new clients because they are reserved
by SAP.
5. Enter the City where the client is
located.
The Logical System field applies
only to the ALE application.
6. Enter a currency code in the Std
currency field (enter usd for U.S.
dollars).
7. Because this client will be used for
development/ customization, select
Automatic Recording of Changes
8. Click the possible entries button to
select Changes to Repository and
client-ind. customizing allowed.
9. Click the Save icon to proceed to the
next screen.
10. Click the Back icon to return to the
previous screen.
3
4
5
6
7
8
9 10
Importing a R/3 Client from another R/3 System
Creating the Target Client
184 1998 SAP Labs, Inc.
For more information about the client-independent object changes field, position the cursor in
this field and press F1.
11. Double-click the desired client
category type to select it (in this
example, Test is selected.
Do not select the Productive category. If
you do, the post-import process can
not be performed.
12. In the Client-independent object
changes field, click the possible
entries button.
11
12
Importing a R/3 Client from another R/3 System
Creating the Target Client
1998 SAP Labs, Inc. 185
13. Select the desired option and click
Enter.
14. Click Save.
15. Choose System Log off.
13
14
15
13
Importing a R/3 Client from another R/3 System
Sharing the Transport Directory of the Source R/3 System in the Target R/3 System
186 1998 SAP Labs, Inc.
16. Click Yes.
Sharing the Transport Directory of the Source R/3 System in the Target R/3 System
The following three data files result from creating the export process:
<drive>\ usr\ sap\ trans\ data\ KT<transport number>.<SAPSID> (such as KT00010.DEV) as data file for
client-independent tables
<drive>\ usr\ sap\ trans\ data\ KO<transport number>.<SAPSID> (such as RT00010.DEV) as data file for
client-specific tables
<drive>\ usr\ sap\ trans\ data\ SX<transport number>.<SAPSID> (such as SX00010.DEV) as data file for
texts
The following two data files result from the creation of the export process:
<drive>\ usr\ sap\ trans\ cofiles\ KT<transport number>.<SAPSID> (such as KT00010.DEV) as cofile for
client-independent tables
<drive>\ usr\ sap\ trans\ cofiles\ KO<transport number>.<SAPSID> (such as KT00010.DEV) as cofile for
client-dependent tables
The target R/ 3 System shares these two files so that transport can be performed. The following procedure
assumes that a network connection exists between the source and target systems. If this is not the case, then
this step should be performed with the help of some form of magnetic media.
1. Right-click the Windows NT Start
button and choose Explore.
16
1
Importing a R/3 Client from another R/3 System
Sharing the Transport Directory of the Source R/3 System in the Target R/3 System
1998 SAP Labs, Inc. 187
2. Choose Tools Map Network Drive.
3. Select the drive that you wish to
declare as the shared drive (in this
example, drive T).
4. Enter the shared drive name of the
source R/ 3 server (in this example,
\\pnsfo36\sapmnt.)
5. Click OK.
The shared directory T with its
subdirectories are displayed.
2
3
4
5
Importing a R/3 Client from another R/3 System
Importing the Data into the Target R/3 System
188 1998 SAP Labs, Inc.
Importing the Data into the Target R/3 System
1. On the R/ 3 System, click the
Windows NT Start button and
choose Programs Command
Prompt.
To obtain the proper transport request number, change to directory trans\ cofiles and execute
dir to view the KO and KT transport request file names. The highest number is the most recent
transport request number.
2. Change the directory to the shared
transport directory (in this
example, T).
3. To change to the proper directory,
enter cd trans\bin at the
command prompt.
4. To ensure the buffers have been
added by the R/ 3 Transport
System, enter tp showbuffer <Target
SAPSID> (in this example, tp
showbuffer prd).
1
2
4
3
Importing a R/3 Client from another R/3 System
Performing Post-Import Activities
1998 SAP Labs, Inc. 189
First import client-independent data,
then client-dependent data.
5. To import client-independent data,
enter tp import <Source
SAPSID>KO<Nr.> client<Target
Client Nr.> <Target SAPSID> (in
this example, tp import
DEVKO00010 client100 PRD).
6. To import client-dependent data,
enter tp import <Source
SAPSID>KT<Nr.> client<Target
Client Nr.> <Target SAPSID> (in
this example, tp import
DEVKT00010 client100 PRD).
Performing Post-Import Activities
Logon to the target system in the client that has just been imported (100 in this example) as user SAP*.
Enter pass as the password, or the current password if user master records have been imported.
To logon to the target client of the
target R/ 3 System:
1. Enter the client number in the
Client field (in this example, 100).
2. Enter sap* in the username field.
3. Enter the password for sap*.
4. Press Enter to accept the user
default language or enter a
language code (e for English.)
5
6
1
2
3
4
Importing a R/3 Client from another R/3 System
Performing Post-Import Activities
1810 1998 SAP Labs, Inc.
5. Choose Tools Administration
Administration Client
admin. Client Transport Client
Import.
Alternative:
6. Review the parameters and click
Execute in backgrd. button.
7. Click Schedule Job.
5
6
7
Importing a R/3 Client from another R/3 System
1998 SAP Labs, Inc. 1811
8. Click Immediate.
9. Click Save.
10. Enter the proper Output device.
11. Click Save.
The messages Format set to
X_65_132 and The background job
was successfully scheduled; result
displayed in SCC3 appears.
8
9
10
11
Importing a R/3 Client from another R/3 System
Checking the Import Logs
1812 1998 SAP Labs, Inc.
Checking the Import Logs
After completing the import procedure, check the log files to ensure that the process concluded
successfully.
1. Choose Tools Administration
Client admin. Copy logs.
Alternative:
2. The status of the post import
process appears. Click on the line
item that displays Processing
3. Click Choose.
4. Click the line item that displays
Processing again.
5. Click Choose.
2
1
3
5
4
Importing a R/3 Client from another R/3 System
Checking the Import Logs
1998 SAP Labs, Inc. 1813
The processing information
appears.
Another way to view the post
import process is to review
background job status.
6. To monitor the post-import
process, enter the transaction
/nSMX.
6
Importing a R/3 Client from another R/3 System
Checking the Import Logs
1814 1998 SAP Labs, Inc.
The screen informs you that the
CLIENTEXPORT/IMPORT 100 job
is running.
7. Click Job overview to review
detailed information.
Accept the default values.
8. Click Enter to continue.
7
8
Importing a R/3 Client from another R/3 System
1998 SAP Labs, Inc. 1815
9. The job is marked as an active job.
Depending on the amount of data you
have, the process may take a while.
You may use any OS activity
monitoring tool (for example,
QSLICE.EXE) to see the activities of the
processes (for example, oracle73.exe and
disp+work.exe).
9
Importing a R/3 Client from another R/3 System
Useful OSS Notes
1816 1998 SAP Labs, Inc.
Useful OSS Notes
Note # Description
70547 CC-TOPIC: Client transport
70128 CC-TOPIC: Info/ Docu/ Help for copying clients
34395 tp return codes and programs used by tp
11677 Transports with event-controlled RDDIMPDP
For further details refer to
R/3 System Administration Made Easy
Transporting a R/3 Client to another R/3 System (Ch. 17)
R/3 Basis Knowledge Products
System Logistics CD Reference Implementation QA ProceduresPlanning Imports
R/3 System Online Help
Online Documentation CD System Administration Transport System/Transport Control
Basis Courses
Workbench Organizer, Transport System & Upgrade (BC325)
Deleting a Client Using R/3 Functionality
Overview
1998 SAP Labs, Inc. 201
Chapter 20: Deleting a Client Using R/3 Functionality
Contents
Overview............................................................................................................................................................................................................201
Heres How.....................................................................................................................................................................................................201
Monitoring the Delete Client Background Job...............................................................................................................................................204
Useful OSS Notes..............................................................................................................................................................................................208
Overview
Deleting a client permanently removes the client from a R/ 3 System. Essentially, this process is the reverse
process of creating a client (Client Copy, Client Transport, etc.). Before deleting any client, consult with all
R/ 3 users to ensure that the client should indeed be deleted. (It is recommended that clients be deleted
using SCC5.)
In this chapter, we perform the deletion from within the client.
Deleting a client is permanent and unrecoverable. Ensure that the client is not in use!
Deleting a client using the R/ 3 transaction code SCC5 mentioned in this chapter will clean up
the SAPSCRIPT and Batch-input data. SCC5 requires much smaller rollback-segments than
using R3TRANS to delete a client that is mentioned in chapter 19, Deleting a SAP Client Using a
R/3 Executable. R3TRANS runs faster than SCC5. SAP recommends using the method discussed
in this chapter.
Heres How
Logon to the client that you would like
to delete:
1. Enter the client number in the
Client field (in this example, 100).
2. Enter sap* in the username field.
3. Enter the password for sap*.
4. Press Enter to accept the user
default language or enter a
language code (e for English.)
1
2
3
4
Deleting a Client Using R/3 Functionality
Heres How
202 1998 SAP Labs, Inc.
5. Choose Tools Administration.
6. Choose Administration Client
admin. Special functions Delete
client.
Alternative:
7. Click the Background button to
delete the client in background.
There are two options that you
may choose:
Test run allows you to
simulate client delete and
obtain a report for the
process.
Delete entry from T000 cleans
up the client information in
table T000 that stores the
client information.
To use the default/ current R/ 3
server, you do not need to
provide any server name into
Background servers field. To
choose a different server, just
enter the servers name.
8. Click the Schedule job button.
5
6
7
8
Deleting a Client Using R/3 Functionality
Heres How
1998 SAP Labs, Inc. 203
9. Click Yes.
10. Click Immediate.
11. Click the Save icon.
9
10
11
Deleting a Client Using R/3 Functionality
Monitoring the Delete Client Background Job
204 1998 SAP Labs, Inc.
12. Enter a printer name in the Output
Device field.
13. Click the Save button.
The message The background job was
successfully scheduled; result
displayed in SCC3 appears.
Monitoring the Delete Client Background Job
Follow the steps below to monitor the Delete Client background job:
1. Choose Tools Administration
Administration Client admin.
Copy logs.
Alternative:
12
13
1
Deleting a Client Using R/3 Functionality
Monitoring the Delete Client Background Job
1998 SAP Labs, Inc. 205
2. Select the line item that indicates
the target client we want to delete
(in this example, 100).
3. Click Choose.
4. Select the line item that indicates
the target client we want to delete
(in this example, 100).
2
3
4
Deleting a Client Using R/3 Functionality
Monitoring the Delete Client Background Job
206 1998 SAP Labs, Inc.
The client deletion is still running.
5. Click Refresh to view the latest
status.
6. To view the status online, click
Monitor.
The bar chart shows you the
current activities.
5 6
Deleting a Client Using R/3 Functionality
Monitoring the Delete Client Background Job
1998 SAP Labs, Inc. 207
7. Using QuickSlice, we can see that
oracle73.exe, the tenth disp+work.exe
are running. This view tells you
that the Oracle database is busy
deleting client dependent data
(client 100). Meanwhile, the
Background Work Processes are
busy communicating with the
database.
7
7
Deleting a Client Using R/3 Functionality
Useful OSS Notes
208 1998 SAP Labs, Inc.
Congratulations on successfully
deleting a client!
Useful OSS Notes
Note # Description
35952 Client deleted, space still filled in database
Deleting a Client Using R/3 Functionality
Useful OSS Notes
1998 SAP Labs, Inc. 209
For further details refer to
R/3 System Administration Made Easy
Deleting a R/3 Client Using a R/3 Executable (Ch. 19)
R/3 System Online Help
Online Documentation CD Transport Control Client Copy Tools
Basis Components System Administration Transport
System/Transport Control
Basis Courses
Workbench Organizer, Transport System, and Upgrade (BC325)
Overviewing R/3 Profile Maintenance Tool
Overview
1998 SAP Labs, Inc. 241
Chapter 24: Overviewing R/3 Profile Maintenance Tool
Contents
Overview............................................................................................................................................................................................................241
What are Profiles?.............................................................................................................................................................................................242
Instance Profile............................................................................................................................................................................................244
Default Profile..............................................................................................................................................................................................244
Start Profile..................................................................................................................................................................................................244
Process of Profile Maintenance.......................................................................................................................................................................245
R/3 Profiles Definition.......................................................................................................................................................................................248
How Do I Maintain Profiles?.............................................................................................................................................................................249
Basic Tasks.................................................................................................................................................................................................249
Extended Tasks.........................................................................................................................................................................................2410
Hints and Questions .......................................................................................................................................................................................2411
Useful hints for Profile Maintenance..........................................................................................................................................................2411
Warning: Values are not allowed.......................................................................................................................................................2411
Changed Parameters become Not Active .........................................................................................................................................2411
Frequently Asked Questions .....................................................................................................................................................................2411
Useful OSS Notes............................................................................................................................................................................................2413
Overview
This chapter introduces the R/ 3 Basis tools that help you configure the R/ 3 Application Servers. When
setting up a R/ 3 application server, configure the following parameters:
The runtime environment of the instance (resources such as main memory size, shared memory, roll,
and paging size)
Services available to the instance (dialog, background processes, etc.)
The location of other services (database host)
Operating system files, called profiles, store the setup information. For each component of the
configuration exists a parameter, and the profiles assign values to these parameters. The R/ 3 System uses
three different profile types:
Instance
Default
Start
You can modify each of these. However, changes in profiles are infrequent for most productive R/ 3
Systems.
The instance profile provides an application server with configuration parameters that define the available
instance resources (main memory, shared memory, etc.), and determines how to allocate memory to the
R/ 3 application buffers. Typically, these parameter settings adapt the instance based on the desired
resources.
Overviewing R/3 Profile Maintenance Tool
What are Profiles?
242 1998 SAP Labs, Inc.
To assign the same parameter value for all application servers, enter it in the default profilefor example,
the name of the database host or the computer on which the message server is running. When you start a
R/ 3 instance on a host, the start profile defines which R/ 3 services are started (for example, message
server, dialog, gateway, or enqueue process). The SAP program startsap is responsible for initiating these
service processes, and it uses a start profile to begin the startup process.
All host computers in a R/ 3 System can access these profiles. Several R/ 3 instances may simultaneously
use a single profile. Separate profiles are not required for each R/ 3 instance. In general, you could change
the configuration of an application server either manually or dynamically without downtime of the server.
Only after restarting the R/ 3 instance are manual profile changes activated.
An R/ 3 application server always uses the profile file at the operating system level when it is started.
The chapters 2436 about R/3 Profile Maintenance describe how to maintain profiles from the Computing
Center Management System (CCMS). The CCMS profile maintenance tool analyzes and assists in making
changes to the profiles. The tool not only checks the accuracy of each profile, it also checks the integrity of
your cumulative system setup. The benefits of using the CCMS over editing profiles at the operating
system level will be discussed later in this chapter (see Process of Profile Maintenance).
From release 3.0A, you can manage your profiles from the CCMS. You should not directly edit the active
profiles at the operating system level.
System configuration changes occur infrequently for most productive R/ 3 Systems. Alterations are
required only in exceptional cases. For example, SAP service processes may need to be moved between
instances. Changes for non-productive systems can be frequent. In either of these two cases, having an
easy mechanism for maintaining these changes and establishing a high degree of integrity is important.
SAP provides the profile maintenance tool for these tasks.
In this section, we begin by describing R/ 3 profiles and how the profile maintenance process works. We
then show you how to maintain profiles. We divided the actions into basic tasks and extended tasks. To
prevent or solve problems, useful hints and frequently asked questions appear at the end of this section.
What are Profiles?
A profile is an operating system file that contains instance setup information. During R/ 3 installation, the
following three profiles are automatically created in the file system:
Instance profile: <SAPSID>_<Instance>_<hostname> (such as DEV_DVEBMGS00_pfsn036)
Default profile: DEFAULT.PFL (such as DEFAULT.PFL)
Start profile: START_<Instance>_<hostname> (such as START_DVEBMGS00_pfsn036)
Overviewing R/3 Profile Maintenance Tool
What are Profiles?
1998 SAP Labs, Inc. 243
<SAPSID> is the SAP system name, <Instance> is the SAP instance name, and <hostname> is the name of
the server related to this profile. When the first instance of a R/ 3 System is installed, the system creates a
default profile. Otherwise, the existing default profile is simply updated.
The global file directory stores the R/ 3 profiles in:
Windows NT systems: \ \ <SAPGLOBALHOST>\ sapmnt\ <SAPSID>\ sys\ profile
UNIX systems: /usr/sap/<SAPSID>/SYS/profile
<SAPSID> is the SAP system name and <SAPGLOBALHOST> is the name of the NT machine where the
global profile directory is physically located. This global directory should be accessible from all host
computers in a R/ 3 System. Several R/ 3 instances can simultaneously use a single profile. Separate
profiles are not required for each R/ 3 instance.
In the following graphic, the location of R/ 3 Profiles on Windows NT; SAPSID is DEV; Instance is
DVEBMGS00; and the hostname is pnsfo36:
The same parameter can be in a default or instance profile. The SAP startup process first looks for a profile
parameter in the instance profile. If the parameter is not found, then the default profile is searched. If the
parameter cannot be found in either of these locations, the default value is taken from the startup program
coding.
The profile file is structured as follows:
# This is a comment in a SAP profile:
Parametername1 = Value1
Parametername2 = Value2
Parameter names with a common root logically belong together. For example, the root of parameters that
control the dispatcher within an application server is: rdisp/ .
Overviewing R/3 Profile Maintenance Tool
What are Profiles?
244 1998 SAP Labs, Inc.
Instance Profile
The instance profile provides an application server with configuration parameters that adapt the instance
based on the desired resources. They also define the available instance resources (main memory, shared
memory, roll memory, etc.), and how to allocate memory to the R/ 3 application buffers. To start
application servers on several computers using identical parameter settings, a single instance profile can
be used. It is generally unnecessary for each application server to have its own instance profile.
You can choose any name for an instance profile. The SAP naming convention is:
Profile used by several instances
<SID>_<instance_name> (such as, DEV_DVEBMGS00)
Profile used by one instance
<SID>_<instance_name>_<hostname> (such as, DEV_DVEBMGS00_PNSFO36)
Default Profile
To assign the same parameter value for all application serversfor example, the name of the database host
or the computer where the message server is runningenter this value in the default profile. Although,
you may list any parameter, we recommend that you use the following values:
Parameter Definition Parameter Name in Profile
Name of the database host SAPDBHOST
Name of the update server rdisp/vbname
Name of the enqueue server rdisp/enqname
Name of the server for handling background processing events rdisp/btcname
Name of the computer on which the message server is running rdisp/msname
Name of the TCP service under which the message server can be reached rdisp/msserv
Name of the computer on which the SNA Gateway is running rdisp/sna_gateway
Name of the TCP service under which the SNA Gateway can be reached rdisp/sna_gw_service
You cannot choose a name for the default profile. It is always called DEFAULT.PFL.
Start Profile
When you start a R/ 3 instance on a host, the start profile defines which of the following R/ 3 services are
started, such as the message server, dialog, gateway, or enqueue processes. The SAP program startsap is
responsible for starting these service processes, and it uses a start profile to begin the startup process. To
start the same SAP service processes on several computers, you can use a single start profile. Each R/ 3
instance does not need to have its own start profile.
Processes that can be started include:
Application server
Message server
SNA Gateway
Unix only: System log send daemon System log receive daemon
Overviewing R/3 Profile Maintenance Tool
Process of Profile Maintenance
1998 SAP Labs, Inc. 245
Aside from the general profile parameters, other parameters include:
SAPSYSTEMNAME
name of the R/ 3 System
SAPSYSTEM
instance number
INSTANCE_NAME
name of the R/ 3 instance
Parameter names that are only permitted in a start profile are:
Execute_xx
This starts the operating system commands, which prepare the R/ 3 System to start. For example, you
can use this parameter to start the SAP related database or to set up links to executables on Unix
platforms.
Start_Program_xx
This starts a R/ 3 instance, for example, on an application server.
Stop_Program_xx
This starts an operating system command or SAP program after the R/ 3 instance was stopped, for
example, the halting or removal of shared memory areas that were used by the R/ 3 System.
The number xx (xx = 00-99) defines the execution sequence. The programs specified in Execute_parameter
begin before the programs listed in the Start_Program parameters. After the R/ 3 instance has been stopped,
the programs specified in the Stop_Program parameters are started.
Use the following SAP naming convention when choosing a start profile name:
Profile used by several instances
START_<instance_name> (such as, START_DVEBMGS00)
Profile used by one instance
START_<instance_name>_<hostname> (such as, START _DVEBMGS00_PNSFO36)
Process of Profile Maintenance
You should only edit the profiles from the R/ 3 System using the CCMS profile maintenance tool, not at the
O/ S level. This tool archives the profiles as operating system files and stores a reference copy in the
database. The database copy contains a reference character used to create the profiles at the operating
system level. This process is called activating a profile, that at the operating system level, only gets
overwritten if specified in the profile maintenance tool (the system prompts you to save a profile). At the
operating system level, the reverse procedure is called importing a profile into the database.
Overviewing R/3 Profile Maintenance Tool
Process of Profile Maintenance
246 1998 SAP Labs, Inc.
The following graphic shows the process of importing R/ 3 Profiles from a flat file to the R/ 3 System:
The R/ 3 profiles are automatically generated or updated at the operating system level when you:
First install a R/ 3 System
Upgrade to a new R/ 3 release
Add a new application server
Unfortunately, the installation program cannot save these profiles straight to the database. Therefore, you
must import the R/ 3 profiles before they can be edited by the profile maintenance tool. Two ways exist to
import profiles using the profile maintenance tool:
Importing R/ 3 profiles from all active application servers
You can import the default profile and all start and instance profiles used by the active instances. This
procedure is helpful after you have installed your R/ 3 System or a new R/ 3 release.
Importing individual profiles
This function should be used if a new application server has been installed, or a profile was modified
at the operating system level.
If you have imported the R/ 3 profiles, you can maintain the values of the profile parameters with three
different tools:
Administration data
Basic maintenance
Extended maintenance
These tools help edit and display profiles. Do not work with editors on the operating system level. You can
also use R/ 3 profile maintenance to work on profiles that belong to different application servers at the
same time.
When you modify and store a profile, the old status in the database is not overwritten. Instead, a separate
version with the changed values is created. The R/ 3 System allocates an individual number for each
Overviewing R/3 Profile Maintenance Tool
Process of Profile Maintenance
1998 SAP Labs, Inc. 247
profile version. Thus, the history of profile changes is stored in the database and each version can be
restored at any time.
After a modification, you can complete extensive verification checks of one or more profiles. These checks
include:
Making profile syntax checks
Spell-checking the parameter names
Semantic checks
These checks, for example, verify whether the value of a certain R/ 3 profile parameters is within the
allowed range of values of the parameters. The result of these checks appears in the form of a log, which
contains two message types: warnings and error messages.
The following graphic shows the activation process of a newly modified R/ 3 profile in the database with
flat file changes:
Changes do not take effect immediately in the associated R/ 3 instance. To activate the changes, you have
to activate the changed profile by creating a new profile file at the operating system level. Then stop and
restart the R/ 3 instance(s) for which you want the profile change to become effective.
Overviewing R/3 Profile Maintenance Tool
R/3 Profiles Definition
248 1998 SAP Labs, Inc.
R/3 Profiles Definition
System parameters are defined and stored:
In the coding
In the default profile
The default profile / usr/ sap/ SID/ SYS/ profile/ DEFAULT.PFL overwrites the settings from the
coding.
In the instance profile
The instance profile usr/ sap/ <SAPSID>/ SYS/ profile/ ... overwrites the settings in the coding and in
the default profile.
As of release 3.0E some parameters can be dynamically changed during system operation. Many
parameters do not normally require changes and are therefore defined only in the code. For this reason,
although the parameters exist, they may not be listed in the profile files.
If you change profile parameters, they only become active after the instance has been restarted. (Only on
Windows NT and AS/ 400, when a work process is restarted while the system is running, the new
parameters will be valid for this process. This is not valid for Unix.)
Parameter maintenance is done in the following fashion:
By editing the profile files, up to and including Release 2.2
Before making changes, make a backup copy. Changes must be documented. No tab characters may be
used.
With transaction RZ10 in Release 3.0
The profile file is activated when this is used. You are not allowed to edit the files on the operating
system level.
You can display the parameters as follows:
Call up the report RSPFPAR (using Transaction SA38) to display the parameters for the instance that
you are logged on to. (Report RSPARAM does the same, but RSPFPAR is more comfortable.) When
you double-click on the corresponding line the origin of the current value appears on screen.
Use Transaction TU02 to display the parameters for all the instances.
From Release 3.0, you can display the parameters in the profile maintenance (RZ10).
On the operating system level, you can display the parameters using:
sappfpar name=<SID> nr=<nn>
or
sappfpar pf=<full_path_of_profile>
The transaction AL11 (DIR_PROFILE) displays the profile files.
Documentation is available as follows:
On the documentation CD
Up to release 2.2*:
In the hypertext structure BC_SYSPROPAR (use transaction SO70)
Overviewing R/3 Profile Maintenance Tool
How Do I Maintain Profiles?
1998 SAP Labs, Inc. 249
As of release 3.0C:
Using transaction RZ11
In Basic and Extended Maintenance (transaction RZ10) using the F1 key
As of release 3.1G:
Run RSPFPAR to get a list of all active parameters (see above).
To display the parameter documentation, set the cursor to the corresponding line and click on the "?" icon
(or press the F1 key).
How Do I Maintain Profiles?
We divided the activities to maintain the R/ 3 profiles into two parts: basic and extended tasks. All of the
activities for these tasks are carried out with the profile maintenance tool.
To start this tool from the main screen,
choose Tools Administration
Computer Center Management System
Configuration Profile Maintenance.
Alternative:
Basic Tasks
The following items describe how to perform the basic tasks to maintain R/ 3 profiles:
Importing profiles of active servers
If you are using the profile maintenance tool for the first time, you need to import all the necessary R/ 3
profiles from all application servers.
Importing individual profiles
If a new application server has been installed or a profile was modified at the operating system level,
you must import the individual profiles.
Changing profile parameters
The R/ 3 profile parameters can be maintained in three ways:
Administration data
Maintain the name of the file where the profile should be activated.
Basic maintenance
Maintain the most important profile parameters.
Extended maintenance
Overviewing R/3 Profile Maintenance Tool
How Do I Maintain Profiles?
2410 1998 SAP Labs, Inc.
Creating, changing, or deleting entries for all profile parameters
Checking R/ 3 profiles
After you changed parameters in the profiles, you should:
- Perform syntax checks
- Spell-check the parameter names and semantic checks
Activating R/ 3 profiles
If a new version of a profile has been created and checked, activate the new version, so that a new
profile file is created at the operating system level.
Checking active parameters
When restarting the R/ 3 System, you should check whether the parameters have been correctly
changed.
Extended Tasks
This section describes the extended tasks used to maintain R/ 3 profiles:
Creating a profile
If a new profile is needed, you can manually create it.
Copying a profile
If a new profile is needed, you can copy an existing profile.
Deleting a profile
When a profile is not used anymore, you can delete it from the database and the corresponding profile
files from the operating system level.
Switching back to an older profile version
If an old version of a profile has to be activated, switch back by copying or deleting profiles.
Comparing a profile in the database with an active version
You can confirm whether a profile file has been manually changed at operating system level by
comparing the profile information in the database with the profile existing on the operating system.
Dynamic switching of profile parameters.
You can change and switch special R/ 3 profile parameters for instance profiles without restarting the
system.
Overviewing R/3 Profile Maintenance Tool
Hints and Questions
1998 SAP Labs, Inc. 2411
Hints and Questions
Useful hints for Profile Maintenance
The following useful hints for profile maintenance were compiled to help you to identify and resolve
problems:
Warning: Values are not allowed
When you maintain the system profiles with the CCMS tools with the transaction RZ10, the warningValues
are not allowed appears. It occurs only when parameters with numeric values are affected. The reason is
that the value to be set deviates from the default value for this parameter, or is not within the permissible
area as determined in the transaction RZ11.
Two alternatives exist to solve the problem:
Wrong typing of the value (warning makes sense and the value must be corrected)
Value makes sense (such as recommend by SAPs Earlywatch Service)
In the second case you can solve the problem by changing the default value or permissible area for this
parameter by using transaction RZ11 (see note 52744: RZ10 profile maintenance: Values are not allowed)
Changed Parameters become Not Active
If the changed system parameters become inactive, the most frequent causes are:
R/ 3 System has not been restarted
Profiles are used only during the startup process. Thus, changed system parameters are activated after
a restart. For a system with several instances, you have to restart only the instance for which you have
changed the parameters.
Profile has not been activated
If you maintain the profiles within CCMS with transaction RZ10, they are stored in the database.
During the startup process, profiles on operating system level are used. Thus, after maintaining
profiles within CCMS you also have to create a new version of the profile on operating system level.
Do this by activating the profile (see Activating the R/ 3 Profile Changes).
Frequently Asked Questions
Q1: Where are system parameters defined?
A1: System parameters are defined and stored:
In the coding.
In the default profile, where the default profile overwrites the setting from the coding.
In the instance profile, where the instance profile overwrites the settings in the coding and the default
profile.
As of release 3.0E, some parameters can be changed dynamically during system operation.
Overviewing R/3 Profile Maintenance Tool
Hints and Questions
2412 1998 SAP Labs, Inc.
Q2: Are all system parameters listed in the profiles?
A2: Many parameters do not normally require changes and are therefore defined only in the code. Thus
parameters exist that are not listed in the default profile or instance profile.
Q3: How can system parameters be displayed?
A3: You can display the parameters as follows:
Call up the report RSPFPAR using transaction SE38 to display the parameters for the instance on
which you are currently logged on. When you double-click on the corresponding line, the origin of the
current value appears.
Use transaction TU02 to display the active parameters.
On the operating system level, you can display the parameters using sappfpar.
Q4: Where can I find documentation?
A4: Documentation is available:
On the documentation CD.
Using transaction RZ11 (type in the parameter name, click on the Display button and the click on the
Documentation button.).
In basic or extended maintenance - transaction RZ10 - using the F1 key.
Q5: Should the profiles for each instance be defined individually, or is it better to have a common profile
of them?
A5: The instance profiles are managed centrally, stored in the directory:
Windows NT: \ \ <SAPGLOBALHOST>\ sapmnt\ <SAPSID>\ sys\ profile
Unix: / usr/ sap/ / <SAPSID>/ SYS/ profile
Therefore, several instances can access the same profile. In some cases, instance profiles must be
individually maintained, because each system needs individual settings of the system parameters. In
particular it applies:
If different hardware is used for the instances
If the applications are different (for example, FI on one instance and PP on another)
If different code pages are used (for example, West European, Cyrillic, or Japanese)
For the database server
If several systems have common system parameters settings, use a common profile. This gives you the
following advantages:
- Simplified maintenance
- Lower rate of errors
Overviewing R/3 Profile Maintenance Tool
Useful OSS Notes
1998 SAP Labs, Inc. 2413
Useful OSS Notes
Note # Description
31395 System parameters: Defined where? Displayed how?
21636 RAM extension: Which changes to profile?
39412 How many work processes to configure?
For further details refer to
R/3 System Administration Made Easy
Introducing R/3 Release 3.1x Architecture (Ch. 1)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Computer Center Management System R/3 System Administration
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Importing Profiles of Active Servers
Overview
1998 SAP Labs, Inc. 251
Chapter 25: Importing Profiles of Active Servers
Contents
Overview............................................................................................................................................................................................................251
Importing All R/3 Profiles from Active Servers ..............................................................................................................................................251
Viewing the Imported Profiles..........................................................................................................................................................................252
Overview
Importing the profiles of active servers is complicated during the post-installation process of a new R/ 3
System or when adding an application server. Profiles exist as flat files in your R/ 3 Server and are
imported into R/ 3s database so that they can be effectively maintained. The following step-by-step
procedure shows how to import these profiles.
Importing All R/3 Profiles from Active Servers
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Choose Utilities Import profiles
Of active servers.
After importing the profiles, they should always be maintained using this tool, not at the
operating system level.
1
2
Importing Profiles of Active Servers
Viewing the Imported Profiles
252 1998 SAP Labs, Inc.
The Display of Profile Check Log
screen appears after first importing
the R/ 3 profiles.
3. Scroll through the log to quickly
check for errors.
4. Click Back to return to the previous
Edit profiles screen.
Viewing the Imported Profiles
After importing all of the profiles from the file system level to the R/ 3 database, check them:
1. From Profile click the possible entries
button to display a list of all R/ 3
profiles.
3 4
1
Importing Profiles of Active Servers
Viewing the Imported Profiles
1998 SAP Labs, Inc. 253
The list of all imported R/ 3 profiles
to the database appears.
2. Choose the Profile name.
3. Click Enter to copy.
The Default, Instance, and Start profiles used by the R/ 3 instances are then imported. These profiles are
checked and a log appears. (The profile names in the database are taken from the corresponding file names
on the operating system.) When you have finished importing profiles, position the cursor in the Profile
field and select PF4. The names of the imported profiles will be displayed.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
2
3
Importing Individual Profiles
Overview
1998 SAP Labs, Inc. 261
Chapter 26: Importing Individual Profiles
Contents
Overview............................................................................................................................................................................................................261
Heres How.....................................................................................................................................................................................................261
Overview
The creation of an instance profile results in a new R/ 3 application server is added to your R/ 3 System. To
manage the new instance profile, you must import it.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the profile name (in this
example, test_pro).
3. Click Create or choose Profile
Create.
3
1
2
Importing Individual Profiles
Heres How
262 1998 SAP Labs, Inc.
4. Enter a Short description of the
profile.
5. Specify the Administration Data (in
this example, the default values are
displayed).
6. Select the Profile type.
7. Click Copy.
8. After transferring the
administration data, click Import or
choose Profile Import.
4
5
7
8
6
Importing Individual Profiles
Heres How
1998 SAP Labs, Inc. 263
9. From the list, specify the operating
system file to which the profile
should be imported.
You can display all the profile files
in the global profile directory by
clicking the Possible entries icon.
10. Click Copy. (The message
/usr/sap/DEV/SYS/profile/DEV_DVE
BMGS00_pnsfo36 imported appears.)
11. To save the new profile, choose
Profile Save or simply click Save.
12. R/ 3 will ask if you want to activate
the profile. Click Yes to activate.
Otherwise, click No. (The message
Profile TEST_PRO [version 0000001]
saved and activated appears.)
9
10
11
12
Importing Individual Profiles
Heres How
264 1998 SAP Labs, Inc.
13. After reading the Caution dialog
window, click the Enter icon or
press Enter to continue.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
13
Changing a Profiles Parameters
Overview
1998 SAP Labs, Inc. 271
Chapter 27: Changing a Profiles Parameters
Contents
Overview............................................................................................................................................................................................................271
Changing Administration Data Parameters....................................................................................................................................................271
Changing Basic Maintenance Parameters......................................................................................................................................................274
Changing Extended Maintenance Parameters...............................................................................................................................................275
Overview
To edit individual R/ 3 profiles you have the following three tools:
Administration Data
Basic Maintenance
Extended Maintenance
Changing Administration Data Parameters
The Administrative Data tool enables you to quickly and conveniently edit parameters. The following
example shows how to change the Short description of a profile is provided in the procedures below.
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. From Profile use the possible entries
button.
2
1
Changing a Profiles Parameters
Changing Administration Data Parameters
272 1998 SAP Labs, Inc.
3. Double-click on the line of the
profile you wish to change (in this
example, DEFAULT).
4. Select the Administration data
button.
5. Click Change to alter its original
value.
From this screen, you can modify the
following administration data:
Short description of the profile
File name in which the profile
should be activated
Reference server for profile
parameter check
Profile type
6. After changing the data, click Copy.
(In this example, the Short
Description was changed.)
3
4
6
5
6
Changing a Profiles Parameters
Changing Administration Data Parameters
1998 SAP Labs, Inc. 273
7. To save the profile with changes,
click the Save icon or choose Profile
Save.
8. R/ 3 will ask if you want to activate
the profile. Click Yes, to activate.
Otherwise, click No. (The message
Profile DEFAULT [version 000002]
saved and activated appears.)
9. After you have read the Caution
dialog box, click Enter.
Remember, when changing a profile, R/ 3 automatically creates a new version. You can go to
a previous version by using the procedure explained in chapter 34, Switching Back to an Older
Version of a Profile.
7
8
9
Changing a Profiles Parameters
Changing Basic Maintenance Parameters
274 1998 SAP Labs, Inc.
Changing Basic Maintenance Parameters
The Basic maintenance tool enables you to quickly and conveniently edit parameters. The following
example shows you how to change the ABAP program buffer size.
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Choose the profile you wish to
modify from the Profile field (in this
example,
DEV_DVEBMGS00_PNSFO36).
3. Select the Basic maintenance button.
4. Click Change to alter its original
value.
From this screen, you can change the
following basic maintenance
information:
General data
Buffer and work processes
Number of work processes
5. In this example, the ABAP program
name buffer size has been changed
to 70,000 KB. You may use the
>>, >, <, << buttons to
change the parameters for any of
the listed items.
6. Click Copy or choose Profile
Copy.
5
6
2
3
4
1
Changing a Profiles Parameters
Changing Extended Maintenance Parameters
1998 SAP Labs, Inc. 275
7. Click the Save icon or choose Profile
Save.
The profile data is automatically
checked before you leave the Basic
maintenance screens. Any errors or
inconsistencies will be displayed.
8. R/ 3 will ask if you want to activate
the profile. Click Yes, to activate.
Otherwise, click No. (The message
Profile DEV_DVEBMGS00_
PNSFO36 [version 000002] saved and
activated appears.)
9. After you read the Caution dialog
box, click Enter.
Changing Extended Maintenance Parameters
The Extended maintenance tool enables you to maintain profiles on an individual parameter level. This
tool comprises an editor that creates, modifies, and deletes individual parameters. To change the system
default client follow the step-by-step procedure below.
7
8
9
Changing a Profiles Parameters
Changing Extended Maintenance Parameters
276 1998 SAP Labs, Inc.
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Choose the profile you want to
change from the Profile field (in this
example,
DEV_DVEBMGS00_PNSFO36).
3. Select the Extended maintenance
button.
4. Click Change to alter its original
value.
Because the list contains many
parameters, use the Find function.
(The system default client belongs to
the group login, therefore, we could
use login as the keyword for
searching purposes.)
5. Choose System List Find
Two colors indicate the values of parametersin this example black and red. Colors are used
for ease of viewing and do not indicate errors.
3
2
4
5
1
Changing a Profiles Parameters
Changing Extended Maintenance Parameters
1998 SAP Labs, Inc. 277
6. Enter login.
7. Click Find.
If parameters of the group login are
defined in the profile, then a pop-up
menu will list them. To replace a
parameter value, follow the remaining
steps:
8. Click on the line login/system_client.
9. Click the Position cursor button.
10. Change the indicated parameter to
the value you need.
11. Click Copy or choose Profile
Copy.
If the copy process is successful,
the message The changed profile was
transferred appears.
6
7
8
10
11
9
Changing a Profiles Parameters
Changing Extended Maintenance Parameters
278 1998 SAP Labs, Inc.
12. Click Back.
13. Click Save or choose Profile Save.
The profile data is checked
automatically before you leave the
Extended maintenance screens. Any
errors or inconsistencies will be
displayed.
14. R/ 3 will ask if you want to activate
the profile. Click Yes, to activate.
Otherwise, click No. (The message
Profile DEV_DVEBMGS00_
PNSFO36 [version 000003] saved and
activated appears.)
14
12
13
Changing a Profiles Parameters
Changing Extended Maintenance Parameters
1998 SAP Labs, Inc. 279
15. After you read the Caution dialog
box, click Enter.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
15
Checking Profiles
Overview
1998 SAP Labs, Inc. 281
Chapter 28: Checking Profiles
Contents
Overview............................................................................................................................................................................................................281
Heres How.....................................................................................................................................................................................................281
Overview
Before you leave either the Basic or Extended maintenance screens, the profile data is automatically
checked and errors or inconsistencies are displayed. Choose Profile Save to:
Check the profile for errors and inconsistencies
Check the consistency of all profiles involved in the switch between operation modes
Save profile data in the database
Activate a profile if corresponding profile files are created at the operating system level
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
To check a single profile:
2. Click the possible entries button to
obtain the Profile name and Version.
3. Click Check or choose Profile
Check.
The message No errors in profile
DEFAULT [version 000002] appears.
3
2
1
Checking Profiles
Heres How
282 1998 SAP Labs, Inc.
CHECK RULES FOR PROFILE CLASSES
Parameter Class Check Rule
Integer value Value smaller than default value Error
Value larger than default by a factor of 10 Warning
Time value Value smaller than 0 Error
Permissible characters: 09
Boolean value Valid value set: 0, 1
ON, OFF
YES, NO
TRUE, FALSE
Other values Error
File directory Directory does not exist Warning
No write authorization Warning
File name File does not exist Error
TCP computer name Computer is not known to TCP Error
TCP service name Service name is not known to TCP Error
SAP server name Server name is not known to R/ 3 System Error
File mask Check is not possible
Strings Check is not possible
Cannot be changed by customer If particular parameters are changed by the customer Error
Special parameters If value does not contain a particular character string Error
Start profile If one program at least is not started Error
Parameters within a single profile are divided into classes, and a separate check rule exists for each class.
In addition to a single profile check, the R/ 3 System tests to see if all profiles are consistent with each
other. For example, all start profiles are checked to see whether exactly one message server has started.
Other features of checking R/ 3 profiles are:
All profiles of an active R/ 3 System (/nRZ10 Utilities Check all profiles Of active servers)
All profiles used for operation mode (/nRZ10 Utilities Check all profiles Of operation mode)
Checking Profiles
Heres How
1998 SAP Labs, Inc. 283
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Activating Profiles
Overview
1998 SAP Labs, Inc. 291
Chapter 29: Activating Profiles
Contents
Overview............................................................................................................................................................................................................291
Heres How.....................................................................................................................................................................................................291
Overview
Before using a newly created or modified profile, you must:
1. Activate the profile
2. Stop the R/ 3 System
3. Restart the R/ 3 System
The following step-by-step procedure will show you how to activate your most recently created profile.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the Profile name and the most
recent Version of the profile to be
activated (in this example,
TEST_PRO is the Profile name and
000001 is the Version).
1
2
2
Activating Profiles
Heres How
292 1998 SAP Labs, Inc.
3. Choose Profile Activate.
The message Profile TEST_PRO
[version 000001] activated appears.
4. Click Enter to continue.
Once you have activated the profile, restart the R/ 3 System to use the new profile values.
Another information screen tells
you that to activate the new
changes, you need to restart the
application server.
5. Click Enter to exit.
An active profile that already exists in the R/ 3 System is automatically backed up, and is given the
extension .bak. You can copy and display this backup file even if the R/ 3 System is unavailable.
3
5
Activating Profiles
Heres How
1998 SAP Labs, Inc. 293
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Checking Active Profile Values
Overview
1998 SAP Labs, Inc. 301
Chapter 30: Checking Active Profile Values
Contents
Overview............................................................................................................................................................................................................301
Heres How.....................................................................................................................................................................................................301
Overview
One of the features of the R/ 3 Profile maintenance is to ensure that:
The parameters are valid R/ 3 parameters
The value of the parameter should fall into a defined range of value
The following steps show you how to check active profile value.
Heres How
To check the active profile values of an instance:
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Choose Goto Profile values Of a
server.
The message Choose an application
server appears.
1
2
Checking Active Profile Values
Heres How
302 1998 SAP Labs, Inc.
3. Double-click on the server name to
choose an application server.
A list appears, containing:
4. Parameter names in alphabetic
order.
5. Active values of the individual
parameters.
Scroll through the list.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
3
4 5
Creating a Profile
Overview
1998 SAP Labs, Inc. 311
Chapter 31: Creating a Profile
Contents
Overview............................................................................................................................................................................................................311
Heres How.....................................................................................................................................................................................................311
Overview
There are two ways to create new R/ 3 profiles. You can either manually create them or copy them from
another R/ 3 profile. This chapter shows you how to manually create a profile.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the profile name you want to
create in the Profile field.
3. Click Create or choose Profile
Create.
1
2
3
Creating a Profile
Heres How
312 1998 SAP Labs, Inc.
4. Enter the name of the operating
system file, reference server, and
profile type, or accept the default
values.
5. Click Copy.
Adjust the parameter values:
6. Select the Basic maintenance or
Extended maintenance button (in this
example, the Basic maintenance
button has been selected).
7. Click Change.
4
5
6
7
Creating a Profile
Heres How
1998 SAP Labs, Inc. 313
8. Modify the parameters as needed
(in this example, the System name,
System number, and Instance name,
and the number of work processes
have been modified).
9. Click Enter (if any errors exist, an
error screen appears).
10. Click Copy or choose Profile
Copy.
11. To save the profile, choose Profile
Save.
The profile data is automatically
checked before leaving the
maintenance screens. Any errors or
inconsistencies will be displayed.
This example of an error screen
shows that R/ 3 has detected
incorrect parameter values (click
Yes to display the error or click No
to correct without display).
12. Click Yes to display the incorrect
value.
The message Invalid profile
parameters detected appears.
8
11
9
10
12
Creating a Profile
Heres How
314 1998 SAP Labs, Inc.
13. Scroll down and locate the error
message.
In this example, an error resulted
from a lower-than-acceptable
parameter value.
14. Enter the correct value.
15. Click Copy or choose Profile
Copy.
The message The changed profile was
transferred appears.
16. Click the Back icon.
13
14
15
16
Creating a Profile
Heres How
1998 SAP Labs, Inc. 315
17. An Activate profile dialog box asks if
you want to activate the profile.
Click Yes to activate. Otherwise,
click No.
The message Profile NEW_PRO
[version 000001] saved and activated
appears.
18. After you read the Caution dialog
box, click Enter.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ 360/ BC361/ BC362/ BC370)
17
18
Copying a Profile
Overview
1998 SAP Labs, Inc. 321
Chapter 32: Copying a Profile
Contents
Overview............................................................................................................................................................................................................321
Heres How.....................................................................................................................................................................................................321
Overview
Use the copy function to create a new profile with some, or all, of the features of another source profile.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the Profile name.
3. Enter the Version.
4. Click Copy or choose Profile
Copy.
1
2
4
3
Copying a Profile
Heres How
322 1998 SAP Labs, Inc.
The Copy Profile screen with the
source profile name and version
and target profile name appears.
5. Enter the Profile name to be copied
(for example, DEV_NEW_PROFILE).
6. Click Copy.
A new version of
DEV_NEW_PROFILE will be
generated based on the profile
DEV_DVEBMGS00_DODGERS.
The message Profile
DEV_NEW_PROFILE [version
000001] was generated appears.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
5
6
Deleting a Profile
Overview
1998 SAP Labs, Inc. 331
Chapter 33: Deleting a Profile
Contents
Overview............................................................................................................................................................................................................331
Deleting a Single Profile...................................................................................................................................................................................331
Deleting All Versions of a Profile.....................................................................................................................................................................332
Preparing Profile Sample for Deletion.........................................................................................................................................................332
Deleting the Profiles ....................................................................................................................................................................................335
Overview
You can either delete single profiles or all versions of a profile.
Deleting a Single Profile
Deleting a single profile means deleting the latest version of a R/ 3 profile. The following step-by-step
procedure shows you how to delete the profile.
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the Profile name and Version
of the profile you want to delete.
1
2
Deleting a Profile
Deleting All Versions of a Profile
332 1998 SAP Labs, Inc.
3. Choose Profile Delete
Individual profile.
4. Click Yes if you want to delete the
particular profile from the
database.
5. A dialog window appears and asks
if you want to delete the profile at
the operating system level. Click
Yes if you want to delete the
particular file; otherwise, click No.
The message Profile NEW_PRO
[version 000001 deleted appears.
Deleting All Versions of a Profile
Before deleting all versions of a R/ 3 profile, we will prepare an example of multiple versions of an R/ 3
Profile (in the following example, TEST_PRO). Later, we will delete all versions of profile TEST_PRO.
Preparing Profile Sample for Deletion
We will use TEST_PRO as an example of a multiple version profile. Currently, TEST_PRO has version 1
only. The following steps show you how to add another version of the profile.
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
3
4
5
1
Deleting a Profile
Deleting All Versions of a Profile
1998 SAP Labs, Inc. 333
2. From the Profile field, enter the
profile name you want to modify
or click the possible entries button to
list the profiles.
3. Click Change.
4. For this example, we will modify
the Short Description by adding
additional comments.
5. Click Copy.
2
4
5
3
Deleting a Profile
Deleting All Versions of a Profile
334 1998 SAP Labs, Inc.
6. Click Save or choose Profile Save
to save current modification.
7. Click Yes to activate the new
version.
The message Profile TEST_PRO
[version 000002] saved and activated
appears.
8. After reading the message, click
Enter.
6
7
8
Deleting a Profile
Deleting All Versions of a Profile
1998 SAP Labs, Inc. 335
Deleting the Profiles
To delete all versions of a profile:
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. From the Profile field, enter the
profile name you want to modify
or click the possible entries button to
list the profiles.
3. Choose Profile Delete All
versions Of a profile.
1
3
2
Deleting a Profile
Deleting All Versions of a Profile
336 1998 SAP Labs, Inc.
4. Click Yes if you want to delete all
versions of the profile.
5. A dialog window appears and asks
if you want to delete the profile
residing at the operating system
level. Click Yes if you want to
delete it; otherwise, click No.
The message All versions of profile
TEST_PRO deleted appears.
6. Click the possible entries button.
The deleted profile is no longer in
the list.
7. Click Cancel to continue.
4
5
6
7
Deleting a Profile
Deleting All Versions of a Profile
1998 SAP Labs, Inc. 337
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Switching Back to an Older Version of a Profile
Overview
1998 SAP Labs, Inc. 341
Chapter 34: Switching Back to an Older Version of a Profile
Contents
Overview............................................................................................................................................................................................................341
Overview
To revert to an older version of the R/ 3 profile:
Copy the older version and activate it to make it the current version (see chapter 32, Copying a Profile).
Delete the current profile version(s) up to the older version that you want to use (see chapter 33,
Deleting a Profile).
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Comparing a Profile in a Database with an Active Profile
Overview
1998 SAP Labs, Inc. 351
Chapter 35: Comparing a Profile in a Database with an Active Profile
Contents
Overview............................................................................................................................................................................................................351
Heres How.....................................................................................................................................................................................................351
Overview
You can compare two R/ 3 profiles to check their similarities or differences. The following steps show you
how to compare a profile in the database with a file in the operating system.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. From the Profile field, enter the
profile name you want to compare
or click the possible entries button to
list the profiles.
1
2
Comparing a Profile in a Database with an Active Profile
Heres How
352 1998 SAP Labs, Inc.
3. Choose Profile Comparison
Profile in database With active
profile.
If any discrepancies exist, a log is
displayed. Otherwise, the message
Profile data in database and active
profile are consistent appears.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
3
Dynamic Switching of Profile Parameters
Overview
1998 SAP Labs, Inc. 361
Chapter 36: Dynamic Switching of Profile Parameters
Contents
Overview............................................................................................................................................................................................................361
Heres How.....................................................................................................................................................................................................361
Overview
As of R/ 3 Release 3.0E, it is possible to dynamically switch some of the parameters. This step means that
changes to specific parameters take effect, without having to restart the application server.
Heres How
1. Choose Tools Administration
Computer Center Management
System Configuration Profile
Maintenance.
Alternative:
2. Enter the Profile name and Version
in the appropriate fields (in this
example, the Profile name is
DEV_DVEBMGS00_PNSFO36; the
Version is 000003).
Click the possible entries button to
display a list of profiles.
1
2
Dynamic Switching of Profile Parameters
Heres How
362 1998 SAP Labs, Inc.
3. Choose Profile Dyn. switching
Display parameters.
The list of switchable memory
management parameters appears.
4. Change the relevant profile
parameters using extended
maintenance (as described in
chapter 27) and save these
parameters.
5. From the profile maintenance main
screen, choose Profile Dyn.
switching Execute or click the
Switch parameter.
6. From the list of active application
servers, select the checkbox of the
application server.
7. Click Continue.
3
4
5
6
7
Dynamic Switching of Profile Parameters
Heres How
1998 SAP Labs, Inc. 363
8. Click the Back icon to return to the
R/ 3 Profile Maintenance main
screen.
The profile can be used
immediately after the change. You
need not restart the system. At the
end, a parameter switching log
appears.
For further details refer to
R/3 System Administration Made Easy
Overviewing R/3 Profile Maintenance Tool (Ch. 24)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Configuration
R/3 System Online Help
Online Documentation Basis Components System Administration Computing Center
Management System R/3 System Administration Profiles
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
8
Overviewing System Administration
Overview
1998 SAP Labs, Inc. 621
Chapter 62: Overviewing System Administration
Contents
Overview............................................................................................................................................................................................................621
Introduction to Starting and Stopping the R/3 System and Database.........................................................................................................621
Overview
A R/ 3 System consists of two instances: a R/3 instance and database instance. Both instances must be started
for the system to be active.
Introduction to Starting and Stopping the R/3 System and Database
Here are several possible methods to start and stop the instances:
SAP Database Administration (SAPDBA)
is a utility that starts from the
command prompt. SAPDBA executes
SQL statements to start and stop the
System.
SAP Service Manager is a Windows NT
application.
2. Click CPU to view the time usage
of each work process.
1
2
Monitoring Work Processes
Heres How...
662 1998 SAP Labs, Inc.
The CPU time usage of each work
process appears.
3. To view detailed information on a
process in this list, position the
cursor in the entry line of the
process. (In this example, the first
process in the list has been chosen.)
4. Click Detail info.
An activity snapshot of the instance is available with the Process Monitor. This is a useful tool for
getting a quick overview of the instance status.
Field Descript ion
No. Work Process number
Ty. Type of service
PID OS PID (Process ID) number
Status Current Action
Cause Cause ID
Start Status of work process
Err Number of detected Errors in the work process
Sem Semaphore resource being used (see OS monitor for further information)
CPU CPU accumulation
Time Time in process accumulation
Program Name of the ABAP running
4
3
Monitoring Work Processes
Heres How...
1998 SAP Labs, Inc. 663
5. Use the Page-up and Page-down
buttons to scroll the screen for
more information.
The CPU time field allows you to
monitor how much activity has been
allocated to a particular work process.
5
5
Monitoring Work Processes
Useful OSS Notes
664 1998 SAP Labs, Inc.
Useful OSS Notes
Note # Description
42074 Using the R/ 3 dispatcher monitor dpmon
For further details refer to
R/3 System Online Help
Online Documentation CD Basis Components System Administration System Services Tools for
Monitoring the Systems Displaying and Controlling Work Processes
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Viewing Transaction Codes
Overview
1998 SAP Labs, Inc. 671
Chapter 67: Viewing Transaction Codes
Contents
Overview............................................................................................................................................................................................................671
Finding the Transaction Code for the Current Screen ..................................................................................................................................671
Overview
Menu paths and transaction codes are two ways to get to a desired screen within the R/ 3 System. While
following a menu path is generally more intuitive, it is slower than using a transaction code. To get to a
desired screen quickly with a transaction code, simply follow the step-by-step procedure below.
Finding the Transaction Code for the Current Screen
1. To view the transaction code of any
screen, from that screen choose
System Status.
2. The Transaction field found in SAP
data will show you how to quickly
get to the same screen in the future.
Enter /n before the transaction code to
go from one screen to another. For
example, if you are in the User
Maintenance screen and want to send a
system message, simply enter /nSM02
in the Command Field. You will go
directly to the System Message window
without having to first exit the User
Maintenance window.
2
1
Viewing Transaction Codes
Finding the Transaction Code for the Current Screen
672 1998 SAP Labs, Inc.
Other information found in the
Syst em St at us Window:
1. License Expirat ion: The date your
user license expires. Note that the
date is in the American format
(Month/ Day/ Year). If the license
has not been applied for yet, this
screen will be blank.
2. Node Name: This is equivalent to
your Host Name.
3. Dat abase Name: This is equivalent
to the System ID.
For further details refer to
R/3 System Administration Made Easy
Locking and Unlocking Transaction Codes (Ch. 68)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Administration
R/3 System Online Help
Online Documentation CD Basis Components System Administration System Services Utilities
Basis Courses
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
1
2
3
Locking and Unlocking Transaction Codes
Overview
1998 SAP Labs, Inc. 681
Chapter 68: Locking and Unlocking Transaction Codes
Contents
Overview............................................................................................................................................................................................................681
Locking a Transaction Code............................................................................................................................................................................681
Unlocking a Transaction Code ........................................................................................................................................................................683
Overview
Locking a transaction code immediately prevents users from using the function represented by the
transaction. For example, locking transaction SA38 (ABAP/4 Reporting) would prevent users from running
ABAP/4 reports from the System menu.
Locking a Transaction Code
1. To view a list of all of the
transaction codes, choose Tools
Administration Administration
Tcode administration.
Alternative:
2. Locate the transaction code you
want to lock.
If you are looking for a particular
Transaction Code, you can search for it
using a wild card. For example, enter
SE* to display all transaction codes
starting with SE.
1
2
Locking and Unlocking Transaction Codes
Locking a Transaction Code
682 1998 SAP Labs, Inc.
3. Position the cursor on the
transaction code you want to lock
(in this example, SE01).
4. Choose Transaction code
Lock/unlock. Or select the Locked
checkbox and click the Enter icon.
5. The checkmark in the Locked
checkbox indicates that the
transaction code is locked.
6. To verify that the transaction code
has been locked, try to run the
transaction by entering it in the
Command field.
A dialog box informs you that the
transaction has been locked.
7. Click OK.
3
4
5
6
7
Locking and Unlocking Transaction Codes
Unlocking a Transaction Code
1998 SAP Labs, Inc. 683
Unlocking a Transaction Code
1. Enter the transaction /nSM01.
2. Locate the transaction you want to
unlock (in this example, SE01).
3. Position the cursor on the
transaction you want to unlock.
4. Choose Transaction Code
Lock/unlock.
1
2
3
4
Locking and Unlocking Transaction Codes
Unlocking a Transaction Code
684 1998 SAP Labs, Inc.
5. To verify that the transaction has
been unlocked, run the transaction.
The transaction code will now
properly execute (in this example,
transaction /nSE01 has returned us
to the Transport System window).
For further details refer to
R/3 System Administration Made Easy
Viewing Transaction Codes (Ch. 67)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Administration
R/3 System Online Help
Online Documentation CD Basis Components System Administration
5
Monitoring System Updates
Overview
1998 SAP Labs, Inc. 691
Chapter 69: Monitoring System Updates
Contents
Overview............................................................................................................................................................................................................691
Producing an Update Error as an Example ....................................................................................................................................................691
Monitoring a Flawed Update Process .............................................................................................................................................................694
Update Components and U1 and U2 Updates................................................................................................................................................695
Useful OSS Notes..............................................................................................................................................................................................697
Overview
The R/ 3 System provides a utility that monitors updates made to your system and ensures that it is
working normally. The Updating process records changes made by users in the systems database. This
utility provides a comprehensive set of tools which analyze and correct problems that can occur during an
update.
This utility enables you to:
Activate and deactivate system-wide updating
Display and debug update records that caused an abnormal termination in an update task, or that have
not yet been processed
Reprocess an update record that caused an abnormal termination (a test mode is also available for
repeating an update without making any changes to the database)
Display the data in an update record that abnormally terminated, so that the update can be manually
repeated
Manually process the unprocessed update records that accumulated while updating was stopped
Manually process a particular unprocessed update record or set of records (you can further select from
U1 (critical data) or U2 (statistics) update records)
Delete update records
Display and reset update statistics
Producing an Update Error as an Example
The following example shows you a Duplicate Key problem that is encountered during an upgrade. This
example is for illustration purposes only. It is not recommended that you do it in your system.
By inserting a Duplicate Key in this example, we expect the R/ 3 System to encounter problems during the
update process.
Monitoring System Updates
Producing an Update Error as an Example
692 1998 SAP Labs, Inc.
1. To execute the ABAP program
VBTST300, enter the transaction
/nSE38.
2. Enter VBTST300 into the Program
field.
3. Click Execute.
1
2
3
Monitoring System Updates
Producing an Update Error as an Example
1998 SAP Labs, Inc. 693
By default, the following
parameters and their values are
displayed.
4. From the Operation field, change
the value U to I, so that Duplicate
Key problems are produced during
the update process.
5. Click Execute.
This screen shows the result of the
execution.
4
5
Monitoring System Updates
Monitoring a Flawed Update Process
694 1998 SAP Labs, Inc.
Monitoring a Flawed Update Process
1. To go to the Update Records: Main
Menu choose Tools
Administration Monitoring
Update.
Alternative:
2. By default, the current Client
number is displayed (in this
example, 001).
3. The current User name is also
displayed (in this example, WLEE).
4. Select the Status of the transaction
(in this example, All).
5. Click Enter.
Update requests can be selected and displayed by means of their Status. Choose the following
options from the Status menu:
Terminated: Displays all canceled requests
To be updated: Displays all update requests not yet executed.
V1: Displays primary update status
V2: Displays secondary update status
All: Displays all requests, whether canceled, pending, or in progress.
1
2
3
4
5
Monitoring System Updates
Update Components and V1 and V2 Updates
1998 SAP Labs, Inc. 695
Update Components and V1 and V2 Updates
In the R/ 3 System, the processing of an update record, along with the execution of the database changes
can be broken down into several parts. These parts describe the update components. By further breaking the
update process down into several smaller parts, it is possible to organize update operations along object-
oriented lines, with one component assuming responsibility for the changes made to one data object.
A distinction should be made between primary (V1) and secondary (V2) update components.
Differentiating between update components based on priority lets the system process critical database
changes ahead of less-critical changes. Critical (or primary) changes are those that have control functions
in the R/ 3 System, such as the placement of an order or a change in the inventory of a material. Some less-
critical secondary changes include purely statistical updates, such as the calculation of results.
Since primary database changes need to be done quickly, these changes are assigned to primary
transaction components that generate updates. Secondary database operations, which are not as time-
critical, are declared secondary components. Therefore, the dispatcher attaches a lower priority to these
operations when assigning update requests to update work processes.
All of the primary components of an update must be processed before the processing of secondary
components.
Both the primary and the secondary components are processed sequentially in a single application server.
Each cluster of components is processed in a single work process. If no V2 update processes (work
processes dedicated to processing V2 update components) are available, the V2 components are processed
by a V1 update process.
1. This screen indicates an Error has
occurred while entering the
transaction /nSE38 by user WLEE.
2. Click Update modules.
A message from the SAP office
appears.
1
2
Monitoring System Updates
Update Components and V1 and V2 Updates
696 1998 SAP Labs, Inc.
3. Select the module name (in this
example, TH_VB_TEST_01) by
clicking once on its line.
4. Click Update status.
5. The popup window indicates that
the Update process was terminated;
its error message is ABAP/4
processor: RAISE EXCEPTION.
6. Click ABAP/4 short dump to view
more detailed information.
The ABAP/4 dump screen appears.
7. Click the Page-Down button to view
other error messages.
3
4
5
6
7
Monitoring System Updates
Useful OSS Notes
1998 SAP Labs, Inc. 697
Useful OSS Notes
Note # Description
25801 New work process type UP2
For further details refer to
R/3 System Administration Made Easy
Overviewing System Administration (Ch. 62)
R/3 Basis Knowledge Products
System Management CD System Services The System Log Viewing and Retrieving a Dump
Analysis
R/3 System Online Help
Online Documentation CD Basis Components System Services Managing Update Records
Basis Courses
Advanced R/ 3 Administration (BC305)
Viewing the Dump Analysis
Overview
1998 SAP Labs, Inc. 701
Chapter 70: Viewing the Dump Analysis
Contents
Overview............................................................................................................................................................................................................701
Heres How.....................................................................................................................................................................................................701
Overview
Dump Analysis is an extensive list of information designed to help a user quickly pinpoint and resolve
program errors.
The ABAP/4 Development Workbench issues a short dump when a report or transaction is terminated
because of a serious error. The system records the error in the system log and writes a snapshot of the
program at the time of its termination to a special database table called SNAP. The following step-by-step
procedure shows you how to view the Dump Analysis to get more information about the nature of the
error(s).
Heres How
1. Choose Tool Administration
Monitoring Dump analysis.
Alternative:
2. Choose Edit Display list or click
the display list icon.
1
2
2
Viewing the Dump Analysis
Heres How
702 1998 SAP Labs, Inc.
3. Place the cursor in the line of the
dump you wish to view.
4. Choose Short dump Dump
analysis.
5. Choose Goto Overview.
6. This ABAP/4 Short Dump List
overview screen allows you to
analyze the problem based on the
sections of the dump. You can
double-click on any of these
sections to display information
about the nature of the error(s).
3
4
5
6
Viewing the Dump Analysis
Heres How
1998 SAP Labs, Inc. 703
For further details refer to
R/3 System Administration Made Easy
Overviewing System Administration (Ch. 62)
R/3 Basis Knowledge Products
System Management CD Reference Implementation System Management
R/3 System Online Help
Online Documentation CD Basis Components System Administration System Services The
System Log Dump Analysis
Basis Courses
Advanced R/ 3 Administration (BC305)
Overviewing R/3 System Workload and Buffer Performance Monitor
Overview
1998 SAP Labs, Inc. 761
Chapter 76: Overviewing R/3 System Workload and Buffer Performance
Monitor
Contents
Overview............................................................................................................................................................................................................762
Workload Monitor..............................................................................................................................................................................................762
What Can You Check with the Workload Monitor? .....................................................................................................................................762
Using the Workload Monitor ........................................................................................................................................................................763
Buffers in the R/3 System.................................................................................................................................................................................763
Client Cache................................................................................................................................................................................................763
Pool .............................................................................................................................................................................................................764
SAP Configuration Check.................................................................................................................................................................................764
Useful OSS Notes..............................................................................................................................................................................................764
Activity
Tables/Indices
Global
Alerts Workload Setup/Buffers
Local
Remote
Network
Operating System
Exceptions Analyses
Statistics Records
Buffers
Calls
Parameter Changes
Activity
System Configuration
Parameter Changes
Activity
System Configuration
Parameter Changes
LAN Check with ping
Network Monitor
Exclusive Lockwaits
Parameter Changes
System Log
DUMP Analyses
SAP-Directories
Active Users
Except/User
Performance Monitoring
SAP System
Database System
Network Monitor
Global
Operating System
File System
Call Statistics
Current Workload
Local
Operating System
File System
Remote
Database
Processes
Instances
Users, local
Users, global
Download Statistics
Performance Report
SAPOSCOL Destination
This section contains the System Performance layout and recommendations to ensure optimal
performance of your system. You should consider all possible factors before changing any of
the parameters. The procedures described in this section do not replace the EarlyWatch Service
that all R/ 3 customers should use.
Overviewing R/3 System Workload and Buffer Performance Monitor
Overview
762 1998 SAP Labs, Inc.
Overview
The R/ 3 buffers frequently store user data and make this data available to the local application server
instance. This process helps reduce access and workload on the database server, which does not need to be
repeatedly accessed to obtain the same information. It also reduces network traffic, improving system
performance.
Buffered data includes:
ABAP/ 4 programs
Screens
ABAP/ 4 Dictionary data
Company-specific data, which typically remains unchanged during system operation
You can change, or tune, buffer size to optimize performance for a particular hardware configuration.
Since many interdependencies must be considered when changing buffer sizes, this is not a
straightforward task.
You can also use table buffering to fine-tune applications which means that some or all of the contents of
frequently changed tables can be held in local buffers.
Workload Monitor
The R/ 3 Workload Monitor provides all the functionality necessary to monitor service levels provided to
the end users. This monitor is also used to analyze bottlenecks. When reviewing system performance, you
should normally start by analyzing the workload statistics. You can analyze workload statistics for the
server you are working on or all other servers. You can also use the Workload Monitor to find out how the
workload is distributed over the servers and transactions. Furthermore, you can display the totals for all
servers and compare the performance of individual servers over specified time periods.
What Can You Check with the Workload Monitor?
You can display views of the R/ 3 statistics data such as:
Workload for today or a recent period
Daily statistics records
Daily monitor response times
Performance history for recent periods for all servers or users
Performance history periods compared
You can also display detailed information on response times and consumption on any application server
in your R/ 3 System.
Overviewing R/3 System Workload and Buffer Performance Monitor
Buffers in the R/3 System
1998 SAP Labs, Inc. 763
Using the Workload Monitor
You can use the Workload Monitor to display the:
Number of configured R/ 3 instances
Services supported by the R/ 3 instances
Number of users working on the different instances
Most frequently used transactions
Response time distribution
Differences between the response times for the different instances
Buffers in the R/3 System
The R/ 3 System has a modular software client/ server architecture. The R/ 3 System can have a three-tier
architecture consisting of one database server, one or more application servers and many presentation
servers, or a two-tier architecture consisting of one machine to support the database and application
server, with several presentation servers.
Client Cache
Each R/ 3 instance (application server) has its own buffers. These buffers are also known as client caches
because they cache the customers programs in memory. The R/ 3 buffers are allocated in memory areas
local to the work process and in individual shared memory areas accessible by all the work processes.
These memory areas are executed for the application server.
Overviewing R/3 System Workload and Buffer Performance Monitor
SAP Configuration Check
764 1998 SAP Labs, Inc.
Some of the many buffers:
Program buffer This buffer occupies a whole shared memory segment.
Generic buffer This buffer is held in a shared memory pool. All work processes can access this
pool.
Screen buffer These are the local work process buffers. Only one work process may
Roll area access these buffers at a time.
Pool
Some SAP shared memory segments are grouped into one shared memory segment known as a pool. This
grouping is done to meet the operating system limits on the number of shared memory allocations per
process. In most operating systems, you can allocate as many shared memory segments as required. The
limits depend on the kernel configuration.
SAP Configuration Check
Poor configuration of the R/ 3 System can cause general performance degradation. Examples of poor
configurations include inefficient workload distributions of the different SAP services, or untuned setups
of SAP instances.
Useful OSS Notes
Note # Description
71346 Collective note: Monitoring: ST04, DB02, ST10, ST03
45580 How are syslog files deleted?
33576 Memory Management (from Release 3.0C, Unix and NT)
23863 MEMORY MANAGEMENT 3.0
15374 Checklist: Performance analysis
11886 Central SysLog cut off
Overviewing R/3 System Workload and Buffer Performance Monitor
Useful OSS Notes
1998 SAP Labs, Inc. 765
For further details refer to
R/3 System Administration Made Easy
All chapters about R/ 3 System Workload and Buffer Performance Monitor (Ch. 7681)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System
R/3 System Online Help
Online Documentation CD Computer Center Management System CCMS Monitors Buffer
Monitor
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Analyzing the R/3 System Workload
Overview
1998 SAP Labs, Inc. 771
Chapter 77: Analyzing the R/3 System Workload
Contents
Overview............................................................................................................................................................................................................771
Heres How.....................................................................................................................................................................................................772
Reviewing the Top 40 Response Times..........................................................................................................................................................777
Reviewing the Transaction Profile ..................................................................................................................................................................778
Overview
When analyzing system performance, you should review the workload statistics. You can analyze
workload statistics for the server you are working on, or all the servers. Use the Workload Monitor to find
out how the workload statistics are distributed over the servers and transactions, to display the totals for
all servers, and to compare the performance of individual servers over specified time periods.
CPU Time
Presentation
Server
Roll
in
Roll
out
Load
Time
Process Time
Wait
Time
DB Time
Dispatch Time
Response Time
Application Server Database Server
N
e
t
w
o
r
k
N
e
t
w
o
r
k
Analyzing the R/3 System Workload
Heres How
772 1998 SAP Labs, Inc.
Review the following statistic definitions before analyzing your R/ 3 workload:
Definition Description
Average response time Response time is measured from the time a work process is instructed by the
dispatcher to perform the execution to the time the result is returned to the
SAPgui. The response time between the SAPgui and the dispatcher is not
included in this value.
Average wait time The amount of time an unprocessed dialog step waits in the dispatcher queue for
a free work process. A high server workload could produce higher wait times.
Average CPU time CPU time used in the work process.
Average load time The amount of time needed to load and generate objects such as ABAP/ 4 source
code and screen information from a database.
Database calls The number of parsed requests sent to the database.
Database requests The number of logical ABAP/ 4 requests for data in the database. These requests
are passed through the SAP DB interface and parsed into individual database
calls. Take note of the proportion of database calls to database requests. If access
to information in a table is buffered in the SAP buffers, database calls to the
database server are not needed. Therefore, the ratio of calls/ requests gives an
overall indication as to the efficiency of table buffering. A good ratio would be
1:10.
Dispatch time The amount of time occupied in the work process. (Response time minus Wait
time.)
Average DB request
time
The logical database request time required for a dialog step. The time depends
on the CPU capacity of the database server, network server and buffering, and
on the input/ output capabilities of the database server.
Average roll ins Average processing time for roll ins
Average roll outs Average processing time for roll outs
Heres How
1. To go to the SAP R/3 CCMS
Performance Monitoring menu,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
1
Analyzing the R/3 System Workload
Heres How
1998 SAP Labs, Inc. 773
2. To view the Workload Analysis, from
the Performance Monitoring
window, choose Workload
Analysis.
Alternative:
The only application server for this
example is dodgers.
3. Click Choose for analysis.
4. Click the server name once to select
an application server (in this
example, pnsfo36).
5. Click the Enter icon.
2
3
4
5
Analyzing the R/3 System Workload
Heres How
774 1998 SAP Labs, Inc.
6. Select a time period. You can
choose daily, weekly, or monthly
statistics. From this screen you can
also compare the performance
development of a day, a week, and
a month for specific time periods or
for specific servers. (In this
example, Previous weeks has been
selected.)
7. Click the Enter icon.
8. Double-click on one of the weeks
listed to select the time period.
6
7
8
Analyzing the R/3 System Workload
Heres How
1998 SAP Labs, Inc. 775
The following is an example of the workload overview of a R/ 3 Server:
9. The Average Response Time is only for the application server. It has the value of 313.7 ms (= 0.3 second).
The Average Response Time of most transactions is approximately less than 2 seconds.
10. The Average CPU Time is 194.2 ms (= 61.9% of the Average Response Time) which is higher than the
normal value. CPU intensive tasks have occurred during the time interval. The Average CPU Time
should be approximately 40% of the Average Response Time. If it is above 40%, the problem may be
one of the following:
Input/ output (I/ O) bottleneck
Network problem
Slow or old CPU speed
Too much swapping
Wrong allocation of I/ O intensive files, such as
- Swap files
- Oracle online redo log files
9-13
14-17
18
19
Analyzing the R/3 System Workload
Heres How
776 1998 SAP Labs, Inc.
- Oracle offline redo log files
- Oracle data files
11. The Average Wait Time is 6.9 ms (= 2.2% of the Average Response Time) which is a little bit high. The
Average Wait Time should be less than 1% of the Average Response Time. (A high server workload can
produce higher wait times.) If it is above 1%, there may not be enough work processes, or work
processes are too busy.
12. The Average Load Time is 18.7 ms (= 5.96% of the Average Response Time) which is normal. Load Time
normally represents the time for loading and generating ABAP/ 4 source code and screen information
from a database. The Average Load Time should be less than 10% of the Average Response Time. If it is
above 10%, there may be missing indices, or R/ 3 buffers are too small.
13. The Average Database Request time is 95.8 ms (= 30.5% of the Average Response Time) which is normal.
Average Database request time should be around 40% of average response time. If it is above 40%,
there may be missing indices, too many extents, database CPU bound, or database memory bound.
The Operating System affects approximately 10% of the above values.
Database Calls are the number of parsed requests sent to a database. There have been 159,892 calls in this
example since the R/ 3 System started up.
14. Database Requests are the number of logical ABAP/ 4 requests for data in the database. These requests
are passed through the SAP database interface and parsed into individual database calls. Take note of
the proportion of database calls to database requests. If access to information in a table is buffered in
the SAP buffers, database calls to the database server are not needed. There are 250,137 requests that
are divided into three kinds of requests:
Direct reads
Sequential reads
Changes
15. The time of Direct Reads for each Database Request is 63,774 ms, which is too high. The normal value
should be less than 10 ms.
16. The time of Sequential Reads for each Database Request is 16.2 ms, which is a little too high. The normal
value should be less than 10 ms.
17. The time of Changes and Commits for each Database Request is 10.9 ms, which is normal because this
value should be less than 25 ms.
Note that the R/ 3 System in this example has been used to import a whole client from another R/ 3
System, and therefore there are many read and write activities. These values are not indicative of a
correctly configured and tuned R/ 3 System.
18. Select Dialog or Background to switch between statistics.
From the Workload Monitor, you can display further statistics for the server(s) and the selected time
interval. These statistics help you pinpoint which transactions have the highest resource consumption.
Analyzing the R/3 System Workload
Reviewing the Top 40 Response Times
1998 SAP Labs, Inc. 777
19. Click Top Time to view the top 40 response times.
Reviewing the Top 40 Response Times
Points of interest to analyze are the:
Programs which always have high response times
Number of sessions the program is using
Number of KB of information transferred
Possibility of starting the program at another time (for example, at night)
The following is an example of the top 40 response time statistics of a R/ 3 System:
1. In this example, program RSCOLL00 took significant amount of response time that includes CPU time,
Load time, etc.
RSCOLL00 is a R/ 3 performance collector program that runs periodically to collect performance data of
your R/ 3 System.
2. You can switch between the response time list and the database requests list by clicking Top requests or
Top Time.
3. Click the Back icon to return the main Performance Workload Overview screen.
1
2
3
Analyzing the R/3 System Workload
Reviewing the Transaction Profile
778 1998 SAP Labs, Inc.
Reviewing the Transaction Profile
1. Click the Transaction profile button
to view the time consumption for
each transaction code.
2. Click in the Response time avg (ms) column to select the column you wish to sort.
Notice that RSCOLL00 (COLLECTOR_FOR_PERFORMANCE background job) took significant amount
of time among all other R/ 3 programs.
3. Click the Sort icon.
1
2
3
Analyzing the R/3 System Workload
Reviewing the Transaction Profile
1998 SAP Labs, Inc. 779
The average response time for a transaction should not be greater than one second, with the exception of
the following transactions:
Type of Transaction Transaction
Code
Approximate Response Time
Create Sales Order VA01 < 1,500 ms
Change Sales Order VA02 < 1,500 ms
Display Sales Order VA03 < 1,000 ms
Create billing document VF01 < 1,500 ms
Create delivery VL01 < 2,000 ms
Maintain master HR data PA30 < 1,000 ms
Create material MM01 < 700 ms
Post account document FB01 < 600 ms
Change account document FB02 < 500 ms
Display account document FB03 < 400 ms
Your response times may vary depending on your hardware and customizing.
Analyzing the R/3 System Workload
Reviewing the Transaction Profile
7710 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about R/ 3 System Workload and Buffer Performance Monitors (Ch. 7681)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System Workload Monitor
Functionality of Workload Monitor Workload Overview of a Server
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computer Center
Management System CCMS Monitors Buffers Monitor Working
with Buffers Monitor
Basis Components System Administration Computer Center
Management System CCMS Monitors Workload Monitors
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Analyzing the R/3 Buffers
Overview
1998 SAP Labs, Inc. 781
Chapter 78: Analyzing the R/3 Buffers
Contents
Overview............................................................................................................................................................................................................781
Heres How.........................................................................................................................................................................................................781
Overview
With the CCMS Buffer Performance Monitor, you can analyze the state of R/ 3 buffers and evaluate their
quality. You can then use this analysis to pinpoint areas in which buffer sizes can be changed to improve
performance. The information displayed has been collected since server startup.
Heres How
1. To go to the SAP R/3 CCMS
Performance Monitoring menu,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
2. To view the SAP Setup/buffers, from
the Performance Monitoring window,
choose Setup/buffers Buffers.
Alternative:
1
2
Analyzing the R/3 Buffers
Heres How
782 1998 SAP Labs, Inc.
After starting R/ 3, the Hitratio % of the buffers have values of less than 95% (the normal
value is greater than 95%). The Hitratio % should increase after a few days of use.
Ratings lower than 90% can be tolerated for certain buffers, such as the single record buffer
or the calendar buffer. These buffers do not impede the overall system performance.
As a rule of thumb, the value of the Swaps is considered high if it is greater than 1,000. If this
happens, you need to increase the size of the buffers (if you have enough free memory) by
maintaining the related instance parameters. After restarting the system, the Swaps objects
will be reset to 0.
Swaps occur when objects are removed from the buffer and cannot be replaced until a new
database access retrieves the data.
3
7
4
8
5
9
6
Analyzing the R/3 Buffers
Heres How
1998 SAP Labs, Inc. 783
The Tune Summary Screen is divided into four parts:
R/ 3 Application Server Buffers (see ref. 3 above)
As a rule of thumb, the following R/3 Hitratio percents should have the following minimum values:
- Short NTAB (Name tab): 99%
- Program: 97%
- CUA: 99%
- Screen: 99%
- Generic key: 90%
- Single key: 80%
SAP Memory (see ref. 4)
SAP Cursor Cache (see ref. 5)
Call Statistics (see ref. 6)
In addition, two important parameters need to be constantly monitored for the various buffers.
They are the Hitratio [%] column (ref. 7) and the Swaps column (ref. 8).
Over time, the Swaps need to be observed. Even if the buffer is sufficient, we recommend
that you recycle the server since fragmentation of the buffer could occur over time.
Buffer Bottleneck occurs if buffer Swaps begin happening, or Max. Use of Extended memory
equals Current Use.
The R/3 Repository Buffers consist of four buffers in shared memory, one for each of the following:
Table Definitions TTAB Buffer Table DDNTT
Field Descriptions FTAB Buffer Table DDNTF
Short Name Type SNTAB Short Summary of TTAB and FTAB buffers
Initial Record Layouts IREC Buffer Record layouts that are initialized depending
on the field type
9. To view the detailed information on R/ 3 buffers, click on the Detail analysis menu button.
Analyzing the R/3 Buffers
Heres How
784 1998 SAP Labs, Inc.
This window provides a link to a
more detailed analysis of the
buffers.
Paging may occur if too much memory is taken from the operating system and given to the
R/ 3 buffers!
If there is a limitation on main memory, the R/ 3 buffer memory could be decreased. From a
performance standpoint, this configuration is the most beneficial.
Analyzing the R/3 Buffers
Heres How
1998 SAP Labs, Inc. 785
The following table provides information on the instance parameters that should be maintained for the
various buffers.
Buffer Instance Parameter
Program Buffer (PXA) abap/ buffersize
abap/ pxa
abap/ programs
CUA buffer (CUA) rsdb/ cua/ buffersize
Screen Buffer (SCRE) zcsa/ presentation_buffer_area
sap/ bufdir_entries
Generic key table buffer (TABL) zcsa/ db_max_buftab
zcsa/ table_buffer_area
rtbb/ frame_length
Single key table buffer (TABLP) rtbb/ max_tables
rtbb/ buffer_length
rtbb/ frame_length
Table description buffer (TTAB) rsdb/ ntab/ entrycount
Field catalog buffer (FTAB) rsdb/ ntab/ entrycount
rsdb/ ntab/ ftabsize
Initial record buffer (IRBD) rsdb/ ntab/ entrycount
rsdb/ ntab/ irbdsize
Short nametab buffer (SNTAB) rsdb/ ntab/ entrycount
rsdb/ ntab/ sntabsize
Analyzing the R/3 Buffers
Heres How
786 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about R/ 3 System Workload and Buffer Performance Monitor (Ch. 7681)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System SAP Buffers R/3
Buffers and Buffer Monitor Tuning Buffers
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Buffer Monitor Working with Buffer Monitors Displaying
Table Buffers
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Analyzing Buffer Statistics
Overview
1998 SAP Labs, Inc. 791
Chapter 79: Analyzing Buffer Statistics
Contents
Overview............................................................................................................................................................................................................791
Heres How.........................................................................................................................................................................................................791
Overview
This chapter shows how to use the CCMS Buffer Performance Monitor to display statistics about buffer and
memory usage over a period of time.
Heres How...
1. To go to the SAP R/3 CCMS
Performance Monitoring menu,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
2. To view the SAP Setup/buffers from
the Performance Monitoring window,
choose Setup/Buffers Buffers.
Alternative:
2
1
Analyzing Buffer Statistics
Heres How...
792 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
4. Click the Program button.
3
4
Analyzing Buffer Statistics
Heres How...
1998 SAP Labs, Inc. 793
5. If you want to view detailed R/ 3
buffer information, click the
Previous buffer, Next buffer, Buffered
objects, or History buttons.
If the program buffer has swapped
objects and the numbers continue to
increase, consider:
Increasing the ABAP/buffer size
parameter, which is located in the
file instance profile (for example,
DEV_DVEBMGS00_pnsfo36).
Shutting down the R/ 3 System and
re-booting it, since program buffer
fragmentation can occur after the
system has been in use for a while.
6. Click the Back icon to return to the
previous screen.
7. Click Back icon to return to the
previous screen.
5
6
7
Analyzing Buffer Statistics
Heres How...
794 1998 SAP Labs, Inc.
8. To view the activities of the
program buffer history click the
History button.
An example of History of R/ 3 Buffers and Memory:
8
9
Analyzing Buffer Statistics
Heres How...
1998 SAP Labs, Inc. 795
9. In the time that has elapsed since this example, the R/ 3 System was re-booted and the free buffer size
changed from 0 to 120.
For further details refer to
R/3 System Administration Made Easy
All chapters about R/ 3 System Workload and Buffer Performance Analysis (Ch. 7681)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System SAP Buffers R/3 Buffers
and Buffer Monitor Tuning Buffers
R/3 System Online Help
Online Documentation CD Basis Components System Administration Computer Center
Management System CCMS Monitors Buffers Monitor Working
with Buffers Monitor
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Analyzing Parameters of R/3 Buffers
Overview
1998 SAP Labs, Inc. 801
Chapter 80: Analyzing Parameters of R/3 Buffers
Contents
Overview............................................................................................................................................................................................................801
Heres How.....................................................................................................................................................................................................801
Viewing Parameters ..........................................................................................................................................................................................803
Overview
This chapter explains how to analyze R/ 3 buffer history to find the correct buffer sizes.
Heres How
1. To go to the SAP R/3 CCMS
Performance Monitoring menu,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
2. To view the SAP Setup/buffers from
the Performance Monitoring window,
choose Setup/Buffers Buffers.
Alternative:
2
1
Analyzing Parameters of R/3 Buffers
Heres How
802 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
4. Click the Parameters button.
3
4
Analyzing Parameters of R/3 Buffers
Viewing Parameters
1998 SAP Labs, Inc. 803
Viewing Parameters
There is one application server for this
R/ 3 System:
1. Select one of the hostnames by
clicking once on the item line (in
this example, pnsfo36).
2. Click the History of file button.
3. This screen shows the history of
parameter changes. In this
example, since 10/ 31/ 97, the
abap/buffersize has been changed
from 65,000 to 70,000.
To view only the active parameters
(without the history of changes), click
the Active parameters button.
1
2
3
Analyzing Parameters of R/3 Buffers
Viewing Parameters
804 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about R/ 3 System Workload and Buffer Performance Monitor (Ch. 7681)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System SAP Buffers Using
Buffer Statistics
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS Monitors
Buffer Monitor Tuning Buffers
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Analyzing Buffer Storage
Overview
1998 SAP Labs, Inc. 811
Chapter 81: Analyzing Buffer Storage
Contents
Overview............................................................................................................................................................................................................811
Analyzing Buffers..............................................................................................................................................................................................811
Overview
The CCMS Buffers Monitor lets you analyze the state of the R/ 3 buffers and evaluate their quality. By doing
so, you can pinpoint areas in which buffer sizes can be changed to improve performance.
Analyzing Buffers
1. To go to the SAP R/3 CCMS
Performance Monitoring menu,
choose Tools Administration
Computer Center Management
System Monitor Performance
Menu.
Alternative:
2. To view the SAP Setup/buffers from
the Performance Monitoring window,
choose Setup/Buffers Buffers.
Alternative:
2
1
Analyzing Buffer Storage
Analyzing Buffers
812 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
4. Click the Storage button.
3
4
Analyzing Buffer Storage
Analyzing Buffers
1998 SAP Labs, Inc. 813
This screen contains generated
Storage information.
A Pool is a group of SAP shared memory segments.
Analyzing Buffer Storage
Analyzing Buffers
814 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
Analyzing R/3 Buffers (Ch. 78)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools SAP System SAP Buffers Storage
Check
R/3 System Online Help
Online Documentation CD Computer Center Management System CCMS Monitors Buffer Monitor
Buffers in the R/3 System
Basis Components System Administration Computer Center
Management System Buffers Monitor Working with Buffers Monitor
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC314/ BC360/ BC361/ BC362/ BC370)
Overviewing the Oracle Performance Monitor
Overview
1998 SAP Labs, Inc. 821
Chapter 82: Overviewing the Oracle Performance Monitor
Contents
Overview............................................................................................................................................................................................................821
Database Performance Check..........................................................................................................................................................................822
Policies and Procedures..............................................................................................................................................................................823
System Environment ...........................................................................................................................................................................823
Procedures ..........................................................................................................................................................................................823
Roles and Responsibilities ..................................................................................................................................................................823
Database System Controlling ..........................................................................................................................................................................823
Policies and Procedures..............................................................................................................................................................................823
System Environment ...........................................................................................................................................................................823
Policies ................................................................................................................................................................................................824
Procedures ..........................................................................................................................................................................................824
Roles and Responsibilities ..................................................................................................................................................................824
Useful OSS Notes..............................................................................................................................................................................................824
Overview
Activity
Tables/Indices
Global
Alerts Workload Setup/Buffers
Local
Remote
Network
Operating System
Exceptions Analyses
Statistics Records
Buffers
Calls
Parameter Changes
Activity
System Configuration
Parameter Changes
Activity
System Configuration
Parameter Changes
LAN Check with ping
Network Monitor
Exclusive Lockwaits
Parameter Changes
System Log
DUMP Analyses
SAP-Directories
Active Users
Except/User
Performance Monitoring
SAP System
Database System
Network Monitor
Global
Operating System
File System
Call Statistics
Current Workload
Local
Operating System
File System
Remote
Database
Processes
Instances
Users, local
Users, global
Download Statistics
Performance Report
SAPOSCOL Destination
This section contains the System Performance layout and recommendations to ensure optimal
performance of your R/ 3 System. Consider all the possible factors before changing any
parameters. The procedures described in this chapter do not replace the EarlyWatch Service that
all R/ 3 customers should use.
Overviewing the Oracle Performance Monitor
Database Performance Check
822 1998 SAP Labs, Inc.
Database Performance Check
The database system is the most complex subsystem in the R/ 3 client/ server architecture. A system
administrator must be able to analyze the database and determine whether bottlenecks in the database are
causing poor performance for all users. Some questions the system administrator should consider and be
able to answer are:
Are there resource constraints in the database configuration?
Are there exclusive lockwaits?
Are there any poorly-performing SQL statements?
SAP chose to implement its own database monitor rather than use the native monitoring tools provided by
database vendors for the following reasons:
To adequately separate monitoring and administration
To monitor the database in read-only mode
To provide a standard interface to support staff for monitoring database activity
To get information from both the database and the R/ 3 System for monitoring specific database
resources (The R/ 3 System, in particular, due to its three-tier client/ server architecture, places special
demands on database monitoring software.)
All information comes from Oracles own monitoring views and tables. Oracle provides information on the
state of the database in virtual tables, called dynamic performance tables or V$ tables, which are held
in memory. The SAP/ Oracle Database Monitor uses these and other Oracle administrative tables to collect,
evaluate, and present its information. The SAP/ Oracle Database Monitor is written in ABAP/ 4, which is,
or can be, directly or regularly started.
Database performance problems can be caused by database configuration or application problems. Here is
a list of possible problem areas:
1. Database Configuration
Bad hit ratio of database buffer
Bad hit ratio of shared pool objects
Disks with high response times
2. Application Problems
Expensive Statements
Bad statements / bad execution (optimizer)
Bad indices (low fill level)
Lock Wait Situations
Lock held too long
Parallel modifications
Overviewing the Oracle Performance Monitor
Database System Controlling
1998 SAP Labs, Inc. 823
Policies and Procedures
This section offers samples of policies and procedures for monitoring database performance.
System Environment
Software Components
System Name Software
DEV CCMS
QAS CCMS
PD1 CCMS
PD2 CCMS
Database Monitoring is a permanent process, and R/ 3 CCMS is used for this task.
Additional checks to be performed:
Type of check DEV QAS PD1 PD2
Table extents T T D D
Tablespace Fill level T T D D
Missing Indices T T D D
D: Daily T: every 2 days
Procedures
After defining and setting the thresholds, the CCMS Alert Monitor has to be watched regularly for each
system. This level of monitoring is of special importance on production machines.
Roles and Responsibilities
Task Role
Watching systems permanently Operator/ DBA
Database System Controlling
Policies and Procedures
System Environment
Software Components
System Name Software
DEV SAPDBA 3.1H
QAS SAPDBA 3.1H
PD1 SAPDBA 3.1H
PD2 SAPDBA 3.1H
Overviewing the Oracle Performance Monitor
Useful OSS Notes
824 1998 SAP Labs, Inc.
Policies
Database maintenance tasks will be performed in special maintenance time frames using SAPDBA (for
example, Saturday during evening hours).
Procedures
All aspects of the database maintenance are covered by SAPDBA. See SAPDBA manual for a detailed
description of SAPDBA.
Roles and Responsibilities
Task Role
Reorganize Tables DBA
Reorganize Tablespaces DBA
Creating Missing Indices DBA
Enlarging Tablespaces DBA
Distributing Database files DBA
Tuning Database DBA
Useful OSS Notes
Note # Description
71346 Collective note: Monitoring: ST04, DB02, ST10, ST03
45580 How are syslog files deleted?
15374 Checklist: Performance analysis
11886 Central SysLog cut off
Overviewing the Oracle Performance Monitor
Useful OSS Notes
1998 SAP Labs, Inc. 825
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle
R/3 System Online Help
Online Documentation CD CCMS CCMS Monitors Database Monitor SAP/Oracle Database
Monitor
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing Database Activity
Overview
1998 SAP Labs, Inc. 831
Chapter 83: Analyzing Database Activity
Contents
Overview............................................................................................................................................................................................................831
Performance Analysis.......................................................................................................................................................................................831
Overview
The database buffer pool contains the database System Global Area (SGA ) block of memory and reduces
time-intensive disk accesses. A high-quality SGA means that there are only a few disk accesses, and that
user calls are mostly requests to the SGA database.
Performance Analysis
What follows is the Performance Analysis and recommendations of the underlying Oracle database:
A recently started database instance may show misleading statistics with regard to hit ratios.
To prevent misleading results, you should let the database warm up before initiating the
performance analysis. To warm up the database, let it run for at least four hours, or until it has
a significantly high total data buffer reads level (for example, 1,000,000 reads).
1. To go to the SAP R/3 CCMS
Performance Monitoring window,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
1
Analyzing Database Activity
Performance Analysis
832 1998 SAP Labs, Inc.
2. To view the Oracle general database
from the Performance Monitoring
window, choose Database
Activity.
Alternative:
3. A typical Data Buffer Size should be
between 16 MB (16.384 KB) and 32
MB (32.768 KB). In this example,
39,320 KB is adequate. Data buffer
quality should be at least 95%. In
this example, the value of the Data
buffer Quality is 99.2%.
If the data buffer has a quality level
of 70% or less, it indicates that the
data buffer is too small. The data
buffer size can be changed by
modifying the value of db_block_size
which is defined in the
init<SAPSID>.ora file.
4. The ratio of Reads to Physical reads
should be greater than 10:1. Here,
the ratio is 18,450,597 : 150,919
which corresponds to a 122 : 1 ratio.
This is okay because it is greater
than a 10:1 ratio.
These fields indicate that of the
18,450,597 Reads, 150,919 block
reads have resulted from blocks
being physically read from
disk.
The Physical writes field
indicates that 54,009 Oracle
blocks have been written to
disk by the Database Writer
process.
2
3
4
5
6
7 8
9
10
11
Analyzing Database Activity
Performance Analysis
1998 SAP Labs, Inc. 833
5. The value of the Busy Wait is 18 (=0.00009 % of 18,240,597 Reads). A normal value for the Busy Wait is
less than 5% of Data Buffer (Oracle Block) Read. Higher values for the Busy Waits indicate excessive
contention. In this example, 18 is an adequate value.
6. The value of the Shared Pool Size is 28,227 KB. In this case, a normal value is at least 20 MB (20,480 KB)
or more. It should be higher than 10% of the physical memory (in this example, 256 MB). For the above,
20 MB / 256 MB * 100% = 7.8% which is lower than 10%. The Shared Pool Size should be increased.
7. The DD Cache quality value is 59.1% (a normal value is greater than 90%). If it is between 80% and 90%,
and the User Calls/ Recursive Calls ratio is 4:1 or higher, then the DD Cache quality is fine. If none of the
conditions are fine, you may need to increase the Shared Pool Size. The low quality of the Cache could
result from the System not being used enough (startup).
8. The value of the Log Buffers Allocation Retries is 9 (= 0.004% of 217,376 Entries). A normal value is less
than 1% of Entries, so this percentage is within normal parameters.
9. The percentage of Table scans: Long tables is 198 (which is 0.07% of the total 275,894 User Calls). This
percentage should be very low, usually less than 1%.
10. The ratio of User Calls to Recursive Calls is 0.05:1 (= 275,894 / 5,858,686). A normal value should be more
than 4:1 (the larger the better.) Since the System has recently been rebooted, it is not unusual for the
percentage to be low. However, a few days later the percentage should increase significantly and
return to a normal value.
The ratio of Reads to User Calls is 67:1 (= 18,450,597 / 275,894). A normal value should be around 15:1
to 20:1. If the ratio is 50:1 or higher, there may be expensive SQL statement, or the R/ 3 System has not
been used more than one full business day.
11. The ratio of User Calls to Parses is 2.3:1 (= 275,894 / 121,713). A normal value should be greater than
4:1. If it is lower than 4:1, you may need to increase the Shared Pool Size.
To view detailed information regarding Oracle performance, choose Database Activity Detail
Analysis Menu from the Performance Monitoring window.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Implementation Monitoring Tools Database
Monitors Introduction to the R/3 Database Monitor for
Oracle SAP/Oracle Performance Monitoring Strategies Monitoring the
Database Buffer (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS Monitors
Database Monitor SAP/Oracle Database Monitor SAP/Oracle
Performance Monitoring Strategies Monitoring the Data Buffer (Oracle)
Analyzing Database Activity
Performance Analysis
834 1998 SAP Labs, Inc.
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing Exclusive Lockwaits
Overview
1998 SAP Labs, Inc. 841
Chapter 84: Analyzing Exclusive Lockwaits
Contents
Overview............................................................................................................................................................................................................841
Heres How.........................................................................................................................................................................................................841
Overview
A lockwait occurs when a large number of R/ 3 user requests are channeled into a relatively small number
of R/ 3 work processes (at the application server).
A user holding a lock occupies a R/ 3 work process. Other users trying to apply the same lock will have to
wait. This waiting period is called a lockwait. As the number of lockwaits increases, fewer and fewer R/ 3
user requests can be processed by available R/ 3 work processes. In the worst case scenariowhen the
number of lockwaits equals the number of R/ 3 work processesa small number of users can cause the
entire R/ 3 System to freeze.
For example, an order taker puts a lock on available material, gets distracted, and does not confirm the
order. No other order taker will be able to lock the same item until the initial lock is released. A typical way
of solving this problem is to find the person holding the lock so that he or she can confirm the order and
release it. If this is not possible, the lock is deleted. This will roll back the transaction of the lock-holder and
release the material for other users.
You can search for exclusive lockwaits where at least one process is locked through a lock held by another
process. The process of holding the lock and the waiting process(es) is described in the following step-by-
step procedure.
Heres How...
1. To go to the SAP R/3 CCMS
Performance Monitoring screen,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
1
Analyzing Exclusive Lockwaits
Heres How...
842 1998 SAP Labs, Inc.
2. To go to the Database Performance
Analysis window, choose Database
Exclusive lockwaits.
Alternative:
3. This screen indicates that there are
No exclusive lock-waits found, which
is desirable.
Lockwaits can cause poorly timed holds on resources that result in inefficient system
performance. Lockwait situations can also cause an instant halt to the system performance. It is
necessary to find out which SAP Object or Objects lock a process. If a lockwait is caused by a
long-running job and is interfering with other processes, SAP administrators should identify
the user running the job and decide whether it should be postponed until a more convenient
time. If the lockwait is caused by a bad program, appropriate action, such as deleting the process
that causes the lock, should be taken.
3
2
Analyzing Exclusive Lockwaits
Heres How...
1998 SAP Labs, Inc. 843
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle) Detail
Analysis Menu (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing the Dictionary Buffer
Overview
1998 SAP Labs, Inc. 851
Chapter 85: Analyzing the Dictionary Buffer
Contents
Overview............................................................................................................................................................................................................851
Heres How.........................................................................................................................................................................................................851
Overview
The Dictionary Buffer information is read into memory from the dictionary tables stored on disk. When an
Oracle instance is first started, this cache is empty and must be loaded as the dictionary information is
accessed. For this reason, hit ratios are generally low at database instance startup and stabilize over time.
Heres How...
Follow this step-by-step procedure to analyze the dictionary buffer:
1. To go to the SAP R/3 CCMS general
performance menu, choose Tools
Administration Computer Center
Management System Control
Performance Menu.
Alternative:
2. To go to the Database Performance
Analysis screen, choose Database
Activity.
Alternative:
2
1
Analyzing the Dictionary Buffer
Heres How...
852 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
4. Click the Dictionary buffer button.
4
3
Analyzing the Dictionary Buffer
Heres How...
1998 SAP Labs, Inc. 853
5. Click once in the first row of the
Used(%) column to select it.
6. Click the Sort button to view the
Used(%) list from the highest to the
lowest value.
7. Notice that the Used(%) for some of
the Dictionary Cache Objects has
reached 100%. This is not a critical
issue because the system quickly
allocates the Dictionary Cache
Objects as needed, and fixes itself.
7
5
6
Analyzing the Dictionary Buffer
Heres How...
854 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle) Detail
Analysis Menu (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor
SAP/Oracle Performance Monitoring Strategies Detailed Analysis of the
Dictionary Buffer (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing Database Performance
Overview
1998 SAP Labs, Inc. 861
Chapter 86: Analyzing Database Performance
Contents
Overview............................................................................................................................................................................................................861
Heres How.........................................................................................................................................................................................................861
Overview
Monitoring call activity determines the work done on the system separated by both user and internal
operations.
Heres How...
1. To go to the SAP R/3 CCMS
Performance Monitoring window,
choose Tools Administration
Computer Center Management
System Monitor Performance
Menu.
Alternative:
2. To go to the Database Performance
Analysis window, choose Database
Activity.
Alternative:
1
2
Analyzing Database Performance
Heres How...
862 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button to view other options.
4. Click the Performance database
button.
3
4
Analyzing Database Performance
Heres How...
1998 SAP Labs, Inc. 863
5. The ratio of User calls to Recursive
calls is about 3:2 (544,795 : 371,630);
the ideal ratio is 5:1. The ratio in this
newly-established R/ 3 System will
improve with use over time.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
5
Analyzing Database Parameter Changes
Overview
1998 SAP Labs, Inc. 871
Chapter 87: Analyzing Database Parameter Changes
Contents
Overview............................................................................................................................................................................................................871
Heres How.....................................................................................................................................................................................................871
Overview
This section determines both the current and historical settings of the init<SID>.ora parameters. Note that
changes to these parameters only take effect after the database instance has been restarted.
Heres How
1. To go to the SAP R/3 CCMS general
performance menu, choose Tools
Administration Computer Center
Management System Control
Performance Menu.
Alternative:
2. To go to the Database Performance
Analysis window, choose Database
Activity.
Alternative:
1
2
Analyzing Database Parameter Changes
Heres How
872 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
4. Click the Parameter changes button.
3
4
Analyzing Database Parameter Changes
Heres How
1998 SAP Labs, Inc. 873
5. This example indicates that
06/10/1997 was the last date that this
parameter was changed.
6. Click the History of file button.
7. This example indicates that the
Database Parameters value
SHARED_POOL_SIZE was
changed from 26,214,400 to
26,200,000 on 11/17/1997.
5
6
7
Analyzing Database Parameter Changes
Heres How
874 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle) Detail
Analysis Menu (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle) Detail Analysis Menu (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing the V$ROWCACHE
Overview
1998 SAP Labs, Inc. 881
Chapter 88: Analyzing the V$ROWCACHE
Contents
Overview............................................................................................................................................................................................................881
Heres How.........................................................................................................................................................................................................881
Overview
The Shared Pool (that is, the memory area in the SGA) is used by Oracle to hold several key memory
structures. Most important among these structures are the Data Dictionary Cache and the Shared SQL Area.
The Data Dictionary Cache contains information about naming, definition, and access, for Oracle objects. It
is regularly referenced by Oracle, as well as some application programs and database users. This chapter
shows you how to analyze the Dictionary Cache statistics (V$ROWCACHE).
Heres How...
1. To reach the SAP R/3 CCMS
general performance menu, choose
Tools Administration Computer
Center Management System
Control Performance Menu.
Alternative:
2. To go to the Database Performance
Analysis window, choose Database
Activity.
Alternative:
2
1
Analyzing the V$ROWCACHE
Heres How...
882 1998 SAP Labs, Inc.
3. Click the Detail analysis menu
button.
To review the Database Performance, it is
necessary to display the v$values of the
database. Refer to the Oracle database
training manual for more information.
4. Click the Display V$ values button.
3
4
Analyzing the V$ROWCACHE
Heres How...
1998 SAP Labs, Inc. 883
5. Choose Goto Statistics
V_Rowcache to reach the V$ values.
6. The percentage ratio of the total
Gets and Getmisses should be less
than 15% for the database and less
than 10% if using SAP. In this
example, the total number of all
Gets is 5,112 and the total number
of Getmiss is 1,428 which results in
a ratio of 28%. This ratio is a little
too high. If the percentage ratio is
significantly higher than 15% (for
example, 30%), the Shared Pool
needs to be enlarged.
To enlarge the Shared Pool Size (if you have enough additional memory), locate the file in the
directory <drive>:\ ORANT\ DATABASE\ INIT<SAPSID>.ORA (for example,
C:\ ORANT\ DATABASE\ INITDEV.ORA) and change the value parameter shared_pool_size.
You may have to experiment to achieve an optimal ratio of Gets to Getmisses.
5
6
Analyzing the V$ROWCACHE
Heres How...
884 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to
the R/3 Database Monitor for Oracle Detailed Analysis (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing the Databases Tables and Indices
Overview
1998 SAP Labs, Inc. 891
Chapter 89: Analyzing the Databases Tables and Indices
Contents
Overview............................................................................................................................................................................................................891
Heres How.........................................................................................................................................................................................................891
Overview
This chapter shows you how to do internal database and consistency checks between the database and the
R/ 3 System.
Check the status of the database tables and database indices frequently. Slightly fragmented
tables can adversely affect system performance!
Heres How...
1. To go to the SAP R/3 CCMS general
performance menu, choose Tools
Administration Computer Center
Management System Control
Performance Menu.
Alternative:
2. To view the databases tables and
indices information, choose
Database Tables/Indexes.
2
1
Analyzing the Databases Tables and Indices
Heres How...
892 1998 SAP Labs, Inc.
3. From the Data Base Performance:
Tables and Indexes screen, you can
check the following:
Internal database consistency
Tables without indices
Database and R/ 3 System
Missing database objects (tables
and indices)
Missing objects in the SAP Data
Dictionary.
Click Refresh to get the most
current statistics. Otherwise,
old statistics will be displayed.
To do further analyses, from this screen select Goto Check Installation DB <->ABAP
Dict. The missing objects will be displayed.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Analyzing Missing Indices Contents
Overview
1998 SAP Labs, Inc. 901
Chapter 90: Analyzing Missing Indices Contents
Overview............................................................................................................................................................................................................901
Checking for Missing Indices ..........................................................................................................................................................................901
Useful OSS Notes..............................................................................................................................................................................................903
Overview
You can verify whether objects such as tables or indices defined in the ABAP/4 Dictionary are also defined
in the database system. Indices will only be missing if you ignore an error message (such as Table created or)
when creating a table or when deleting an index.
Indices are sometimes accidentally deleted during an incorrect reorganization. When this happens, access
times may increase and duplicate records may be created which make access unsafe.
Checking for Missing Indices
1. To check for missing indices, go to
the SAP R/3 CCMS Performance
Monitoring window. Choose Tools
Administration Computer
Center Management System
Control Performance Menu.
Alternative:
2. From the Performance Monitoring
screen, choose Database
Tables/Indexes.
2
1
Analyzing Missing Indices Contents
Checking for Missing Indices
902 1998 SAP Labs, Inc.
3. Click the Missing Indexes button.
4. In this example, the directories
listed under Indexes missing in the
database indicate that there are no
missing indices. If you find missing
indices, be sure to recreate them to
achieve optimal performance.
Primary indices (ending in 0) ensure that line keys (row keys) are unique. Missing primary
indices are therefore critical. If a primary index is missing, you should consult SAP for help
with its restoration. There is no simple procedure for restoring an index if a large number of
duplicate keys were created in a table.
Secondary indices (not ending in 0) are used for special scans and are only relevant for their
performance. You may restore a secondary index for SAP tables using the Database Utility of
the ABAP/4 Dictionary (transaction / nSE14). You can likewise access this utility from the
individual index analysis functions.
3
4
Analyzing Missing Indices Contents
Useful OSS Notes
1998 SAP Labs, Inc. 903
Useful OSS Notes
Note # Description
44395 SAPDBA: Missing indexes after reorg run
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle)
R/3 System Online Help
Online Documentation CD Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle) Table without Indexes (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Monitoring Space-Critical Objects
Overview
1998 SAP Labs, Inc. 911
Chapter 91: Monitoring Space-Critical Objects
Contents
Overview............................................................................................................................................................................................................911
Heres How.....................................................................................................................................................................................................911
Overview
This chapter shows you how to examine Space-critical objects to do internal database checks and consistency
checks between the database and the R/ 3 System. Related issues include situations where an object cannot
be allocated and overflow problems.
Heres How
1. To go to the SAP R/3 CCMS
Performance Monitoring window,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
2. To view information on the
databases tables and indices from
the Performance Monitoring window,
choose Database Tables/Indexes.
1
2
Monitoring Space-Critical Objects
Heres How
912 1998 SAP Labs, Inc.
3. Click the Space critical objects button.
4. The message There are no critical
tables/indexes appears in the status
bar at the bottom of the window. In
this example, no space-critical
objects were found for this R/ 3
server.
If space-critical objects are found, you may want to check the tablespace status and the extent of
tables and indices (see chapter 93, Viewing and Extending Tablespaces, and chapter 94, Analyzing
Extents of Tables and Indices).
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for an R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle)
R/3 System Online Help
Online Documentation Basis Components System Administration CCMS CCMS
Monitors Database Monitor SAP/Oracle Database Monitor Detailed
Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
3
4
Analyzing Current Tablespace Sizes
Overview
1998 SAP Labs, Inc. 921
Chapter 92: Analyzing Current Tablespace Sizes
Contents
Overview............................................................................................................................................................................................................921
Heres How.........................................................................................................................................................................................................921
Overview
After installing the system and before transferring data, you should verify that space exists in all
tablespaces. Do this regularly when your system is productive. If you find full tablespaces, you must
analyze whether they should be extended and/ or reorganized.
Heres How...
1. To go to the SAP R/3 CCMS
Performance Monitoring window,
follow the path Tools
Administration Computer Center
Management System Control
Performance Menu.
Alternative:
2. To view information on the
Databases tables and indices, from
the Performance Monitoring window,
follow the path Database
Tables/Indexes.
2
1
Analyzing Current Tablespace Sizes
Heres How...
922 1998 SAP Labs, Inc.
3. Click on the Current sizes button.
The Memory Management:
Tablespaces window appears.
4. This list is sorted by Used%. Notice
that all of the Used Tablespace
values are less than 90%the
standard values for the system.
If the Used% of Tablespace is larger
than 90%, you should extend the
Tablespace (see chapter 93, Viewing and
Extending Tablespaces).
4
3
Analyzing Current Tablespace Sizes
Heres How...
1998 SAP Labs, Inc. 923
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for an R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Detailed Analysis (Oracle) Checking
for Full Tablespaces
R/3 System Online Help
Online Documentation Basis Components System Administration CCMS CCMS Monitors
Database Monitor SAP/Oracle Database Monitor Detailed Analysis
(Oracle) Checking for Full Tablespaces
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Viewing and Extending Tablespaces
Overview
1998 SAP Labs, Inc. 931
Chapter 93: Viewing and Extending Tablespaces
Contents
Overview............................................................................................................................................................................................................931
Check Current Tablespace Sizes.....................................................................................................................................................................931
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb) .................................................................................933
Overview
When the database system can no longer assign extents in a tablespace (Oracle error 1547), you must extend
the tablespace by adding a data file. The data file creates new storage space.
The extension of a tablespace changes the structure of the database. The database can only be completely
restored if you back up the new file and the control file. SAP recommends that you backup the extended
tablespace with the SAPDBA backup program BRBACKUP.
It is highly recommended that you perform a full system data backup before extending a
tablespace! Perform the following steps only if a backup has been completed! Table extensions
should only be performed by qualified system administrators.
Check Current Tablespace Sizes
1. Click the Windows NT Start button
and choose Programs Command
Prompt.
2. At the Command Prompt, enter
sapdba.
2
1
Viewing and Extending Tablespaces
Check Current Tablespace Sizes
932 1998 SAP Labs, Inc.
3. Enter c to choose Tablespace
administration.
4. Enter c to choose Free space and
fragmentation of all tablespaces.
You can also view the tablespace
allocations from within SAP by
entering the transaction /nDB02.
Look for the percent of tablespace
allocation under %-Alloc. As a rule of
thumb, write down the names of those
that are greater than or equal to 90%.
5. Press Return to continue to view
the next page.
3
4
5
Viewing and Extending Tablespaces
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)
1998 SAP Labs, Inc. 933
6. Press Return to continue.
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)
1. Enter a to alter a tablespace.
2. Enter the name of the first
tablespace you want to alter (in this
example, PSAPES31HI).
3. Enter f to Alter tablespace
<tablespace> and Add Datafile.
1
2
3
6
Viewing and Extending Tablespaces
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)
934 1998 SAP Labs, Inc.
4. Enter s to Start (Add datafile).
5. Press Return to continue.
6. Press Return to continue.
4
5
6
Viewing and Extending Tablespaces
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)
1998 SAP Labs, Inc. 935
7. Enter q and press Return to go back
to the Tablespace administration
screen (assuming that a database
backup has already been
performed).
Repeat steps 17 to alter additional
tablespaces.
8. When the tablespace extensions are
finished, enter q to return to the
SAPDBA main menu.
9. Enter q to Quit sapdba.
10. Enter y to confirm that you want to
quit.
7
8
9
10
Viewing and Extending Tablespaces
How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)
936 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for an R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
DBA Oracle CD Reference Production Growth Management Managing Tablespace
Extension
R/3 System Online Help
Online Documentation CD Basis Components Database Administration Oracle Tablespace
Administration
Basis Courses
Database Administration ORACLE (BC505)
Analyzing Extents of Tables and Indices
Overview
1998 SAP Labs, Inc. 941
Chapter 94: Analyzing Extents of Tables and Indices
Contents
Overview............................................................................................................................................................................................................941
Heres How.........................................................................................................................................................................................................941
Useful OSS Notes..............................................................................................................................................................................................943
Overview
Eventually, the extents of a table or index may reach their maximum limit. These extents need to be
monitored and reorganized as the values begin to approach the threshold. Before you transfer data to a
table or index, you should check if tables are close to reaching their maximum number of extents.
Heres How...
1. To go to the SAP R/3 CCMS
Performance Monitoring window,
choose Tools Administration
Computer Center Management
System Control Performance
Menu.
Alternative:
2. To view information on the
Databases tables and indices from
the Performance Monitoring window,
choose Database Tables/Indexes.
1
2
Analyzing Extents of Tables and Indices
Heres How...
942 1998 SAP Labs, Inc.
3. Click the Checks button.
4. Click the Extents of tables and indexes
button.
3
4
Analyzing Extents of Tables and Indices
Useful OSS Notes
1998 SAP Labs, Inc. 943
5. If the difference between the MaxExtents column and the Extents column is less than 100, database
reorganization is needed for the particular object(s). In this example, the differences are fine, because
the largest Extent is 74 and the lowest MaxExtent is 300. If database reorganization is needed, use the
SAPDBA to reorganize database objects. See chapter 95, Performing Database Reorganization.
The MaxExtents value for the SAP tables is usually 300 or 505. If there is a table or index in
which the number of extents comes close to this value, take notice. The value may reach the
MaxExtent value and cause a terminated transaction. If you find tables with problems with the
maximum number of extents, we recommend that you reorganize the table or the index. If a
reorganization is not possible, you can temporarily increase the MaxExtents value for the table
or the index.
Useful OSS Notes
Note # Description
39650 Maximum number of extents per tablespace
09321 Next-extents in ORACLE system tables are too large
5
Analyzing Extents of Tables and Indices
Useful OSS Notes
944 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for an R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
System Monitoring CD Reference Monitoring Tools Database Monitors Introduction to the
R/3 Database Monitor for Oracle Diagnosing SAP/Oracle Performance
Problems Monitoring Table and Index Fragmentation
R/3 System Online Help
Online Documentation CD Computer Center Monitor System CCMS Monitors Database Monitor
SAP/Oracle Database Monitor Detailed Analysis (Oracle)
Basis Courses
Workload Analysis (BC315)
Technical Core Competence (BC310/ BC360)
Performing Database Reorganization
Overview
1998 SAP Labs, Inc. 951
Chapter 95: Performing Database Reorganization
Contents
Overview............................................................................................................................................................................................................951
Checking Statistics...........................................................................................................................................................................................951
Using Archiving Mode During the Reorganization ........................................................................................................................................951
Advantages of a Reorganization in NOARCHIVELOG Mode: ....................................................................................................................951
Data Security for a Reorganization in NOARCHIVELOG Mode..................................................................................................................952
Checking Extents using SAPDBA before Performing a Reorganization.....................................................................................................952
Checking Extents using R/3 before Performing a Reorganization...............................................................................................................956
Performing the Reorganization........................................................................................................................................................................959
Checking Number of Extents After Performing Reorganization Using SAPDBA .....................................................................................9515
Useful OSS Notes............................................................................................................................................................................................9519
Overview
Over time, tablespaces in the database may become fragmented and cause performance problems. A
reorganization can de-fragment a tablespace and increase its performance.
Checking Statistics
You can use the following tools to inspect the statistics relevant for a reorganization:
The Performance Monitor of the R/ 3 System (see online help of the Computing Center Management System)
Command line option sapdba -check.
Command line option sapdba -analyze.
SAPDBA option Reorganization Check extents and fragmentation.
SAPDBA option Tablespace administration.
Using Archiving Mode During the Reorganization
Because a reorganization always involves the transport of mass data, a large number of redo logs are
written. If you deactivate the ARCHIVELOG mode, there is no significant acceleration of the
reorganization. Since the archive process ARCH runs parallel to the remaining background database
processes, the CPU is only briefly more heavily loaded if you operate the database in ARCHIVELOG mode.
Therefore, the reorganization is not significantly slowed down.
Advantages of a Reorganization in NOARCHIVELOG Mode:
1. You can safeguard against the risk of an archive getting stuck. You also have the benefit of saving space
in the archiving directory of the offline redo log files <drive>:\ oracle\ <SAPSID\ saparch.
Performing Database Reorganization
Checking Extents using SAPDBA before Performing a Reorganization
952 1998 SAP Labs, Inc.
BRARCHIVE does not have to run for the period of the reorganization because no offline redo log files
are created.
2. Time is saved in the event of a recovery, as you can resume from the backup done after the
reorganization (this is mandatory with the NOARCHIVELOG method).
Data Security for a Reorganization in NOARCHIVELOG Mode
SAP recommends deactivating ARCHIVELOG mode only under certain conditions because it interrupts the
continuity of the redo log files. Once reorganization is complete, you must reactivate the ARCHIVELOG
mode and do a complete offline backup of the database.
Checking Extents using SAPDBA before Performing a Reorganization
Use SAPDBA to check the number of extents before performing a reorganization.
1. To show the current login NT user,
enter the command net config
workstation.
The Windows NT User DEVADM
should be seen directly beneath the
name of the local computer. If it is
not shown, log off and try again.
2. Click the Windows NT Start button
and choose Programs Command
Prompt.
3. Enter the command sapdba to start
the SAP Database Administration
program.
3
2
1
Performing Database Reorganization
Checking Extents using SAPDBA before Performing a Reorganization
1998 SAP Labs, Inc. 953
4. To reach the Reorganization menu,
enter option d.
5. Enter a to check extents and
fragmentation.
6. From the Check menu, reselect a to
check objects with at least a
specified number of extents.
4
5
6
Performing Database Reorganization
Checking Extents using SAPDBA before Performing a Reorganization
954 1998 SAP Labs, Inc.
7. Enter d to specify the least number
of extents the object must have for
the check.
8. Enter your specified number at the
Enter number of extents prompt (for
example, 10).
9. Now, select s to start the check.
10. The number of objects with up to
ten extents will appear at the
bottom of your screen. (In this
example, three objects have been
selected. Record the tablespace
names for future steps in this
chapter.)
11. Press the Return key to proceed.
7
8
9
10
11
Performing Database Reorganization
Checking Extents using SAPDBA before Performing a Reorganization
1998 SAP Labs, Inc. 955
12. Enter option q to return to the
Check screen.
13. From the Check screen, return to the
previous screen by entering q.
14. Re-enter q to return to the
Reorganization screen.
12
13
14
Performing Database Reorganization
Checking Extents using R/3 before Performing a Reorganization
956 1998 SAP Labs, Inc.
15. Re-enter q to quit SABDBA.
16. Enter y to confirm.
Checking Extents using R/3 before Performing a Reorganization
To check the number of extents before performing a reorganization using R/ 3:
1. Enter the transaction /nDB02 to
view the Database Performance
screen. 1
15
16
Performing Database Reorganization
Checking Extents using R/3 before Performing a Reorganization
1998 SAP Labs, Inc. 957
2. Click Checks.
3. Select the Extents of tables and indexes
button.
2
3
Performing Database Reorganization
Checking Extents using R/3 before Performing a Reorganization
958 1998 SAP Labs, Inc.
4. To begin sorting, click anywhere in
the Extents column.
5. Click Sort.
4
5
Performing Database Reorganization
Performing the Reorganization
1998 SAP Labs, Inc. 959
As a rule of thumb to judge which table, index, or tablespace needs to be reorganized, simply
calculate the difference between MaxEntents and Extents. If the difference is less than 100, then
you should reorganize. In this example, the difference of MaxExtents and the Extents of Table
D010Q of tablespace PSAPEL31HD is 289 (300-11). Since 289 exceeds 100, there is no need to
perform a reorganization! To show you how to reorganize a table, we will use D010Q as an
example.
In cases where reorganization is not possible, you may temporarily increase the MaxExtents
value for the table and index.
6. Click the Windows NT Start button
and choose Programs SAP R3
SAP Service Manager for PRD_01.
7. Click Stop to shutdown R/ 3.
8. Click OK to verify intentional
shutdown.
Performing the Reorganization
Before performing a reorganization, you must first backup the database! Refer to chapter 102,
Performing a Full System Backup using NT Backup and chapter 105, Performing Offline Backup
using SAPDBA for a detailed explanation of backup procedures.
The R/ 3 System must be stopped before continuing the following steps. Refer to chapter 63,
Starting and Stopping the R/3 System Using Service Manager for a detailed explanation of how to
stop the R/ 3 System.
6
7
8
Performing Database Reorganization
Performing the Reorganization
9510 1998 SAP Labs, Inc.
1. To show the current login NT user,
enter the command net config
workstation.
The Windows NT User DEVADM
should be shown directly beneath
the name of the local computer. If it
is not shown, log off and try again.
2. Click the Windows NT Start button
and choose Programs Command
Prompt.
3. Enter sapdba to start the SAP
Database Administration program.
4. Enter d to select Reorganization.
1
2
3
4
Performing Database Reorganization
Performing the Reorganization
1998 SAP Labs, Inc. 9511
You can reorganize several different ways, with a:
Single table and index
List of tables and indices
Single tablespace
Tablespace and data files
Reorganizing with a tablespace and data files will de-fragment the tablespace and compress
the data files used by that tablespace. In this example, we will reorganize the table D010Q of
tablespace PSAPEL31HD.
5. Enter c to select Reorganize single
table and index.
6. Enter b to select the Table or index
name.
7. Enter the name of the table to be
reorganized.
5
6
7
Performing Database Reorganization
Performing the Reorganization
9512 1998 SAP Labs, Inc.
8. Enter s to start the reorganization.
9. If you have backed up the database,
proceed with y. If not, enter n and
perform the full database backup
first.
Since our database has been backed
up, enter y to proceed.
Working
8
9
Performing Database Reorganization
Performing the Reorganization
1998 SAP Labs, Inc. 9513
10. Enter 1 to select Start script(s)
immediately.
Depending on the size of the table,
transport may take a while. After
transport, an index is created.
Reorganization is complete when
you see this message: Reorganization
SUCCESSFULLY completed.
11. Press Return to continue.
10
11
Performing Database Reorganization
Performing the Reorganization
9514 1998 SAP Labs, Inc.
12. Enter q to return to the previous
screen.
13. Re-enter q to return to the SAP
Database Administration screen.
14. Enter q to leave the SAP Database
Administration program.
15. Enter y to confirm that you really
want to quit.
12
13
14
15
Performing Database Reorganization
Checking Number of Extents After Performing Reorganization Using SAPDBA
1998 SAP Labs, Inc. 9515
Checking Number of Extents After Performing Reorganization Using SAPDBA
1. To show the current login NT user,
enter the command net config
workstation.
The Windows NT User DEVADM
should be shown directly beneath
the name of the local computer. If it
is not shown, log off and try again.
2. Click the Windows NT Start button
and choose Programs Command
Prompt.
3. Enter the command sapdba to start
the SAP Database Administration
program.
1
2
3
Performing Database Reorganization
Checking Number of Extents After Performing Reorganization Using SAPDBA
9516 1998 SAP Labs, Inc.
4. Enter d to begin the reorganization
process.
5. Enter a to Check extents and
fragmentation.
6. Enter a again to specify that you
want to check objects with a certain
number of extents.
4
5
6
Performing Database Reorganization
Checking Number of Extents After Performing Reorganization Using SAPDBA
1998 SAP Labs, Inc. 9517
7. Enter d to define a higher or equal
value of number of extents that you
want to view.
8. Since we have previously used 10,
re-enter this number.
9. Enter s to start the process.
10. Table D010Q is not included in the
list of the tables which has greater
than or equal to 10 extents. In this
case, the extent of table D010Q has
been reduced.
11. Press the Return key to continue.
7
8
9
10
11
Performing Database Reorganization
Checking Number of Extents After Performing Reorganization Using SAPDBA
9518 1998 SAP Labs, Inc.
12. Enter q to return.
13. Re-enter q.
14. Re-enter q to return to the SAP
Database Amdinistration screen.
12
13
14
Performing Database Reorganization
Useful OSS Notes
1998 SAP Labs, Inc. 9519
15. Enter q to quit.
16. Enter y to confirm that you really
want to quit.
Useful OSS Notes
Note # Description
44935 SAPDBA: Missing indexes after reorg run
44595 SAPDBA: General procedure for reorganizations
43487 Collective note: SAPDBA Reorganization
40521 Reorganization (external tools)
39650 Max. number of extents per tablespace
38006 Ora -1631 max extents reached. Which table?
29348 SAPDBA - Reorganization of single Table; PSAPTEMP
19193 SAPDBA - Size and reorg. of table space PSAPTEMP
12921 Reorganization of SYSTEM tablespace
12621 SAPDBA - speeding up reorganization
15
16
Performing Database Reorganization
Useful OSS Notes
9520 1998 SAP Labs, Inc.
For further details refer to
R/3 System Administration Made Easy
All chapters about Managing the Oracle Database for a R/ 3 System (Ch. 8295)
R/3 Basis Knowledge Products
Oracle Database Administration CD Reference Implementation Database Tools Database Tool
SAPDBA
R/3 System Online Help
Online Documentation CD Basis Components System Administration Database
Administration Oracle Database Administration Database
Reorganization
Basis Courses
Database Administration ORACLE (BC505)
R/3 System Administration Made Easy
41
Chapter 4: 8cheduled Daily Tasks
Contents
Overview..................................................................................................................42
Checklists ................................................................................................................43
Critical Tasks...........................................................................................................47
Verify that R/3 Is Running.........................................................................................47
Verify that the Backups Ran Successfully ................................................................47
R/3 Tasks ...............................................................................................................413
Check that All Application Servers Are Up (Transaction SM51).............................413
CCMS Central Alert Monitor (Transaction RZ20) ...................................................414
Failed Updates (Transaction SM13) .......................................................................419
System Log (Transaction SM21) ............................................................................423
Background Jobs (Transaction SM37)....................................................................427
Graphical Job Monitor (Transaction RZ01).............................................................429
Locks (Transaction SM12) ......................................................................................431
Active Users (Transactions SM04 and AL08).........................................................433
Check the Spool (Transaction SP01)......................................................................436
Batch Input Jobs, In-Error or To Be Processed (Transaction SM35) .....................438
Work Processes (Transactions SM50 and SM51)..................................................440
ABAP Dump Analysis (Transaction ST22) .............................................................442
Workload Analysis of the System (Transaction ST03) ...........................................445
Buffers (Transaction ST02).....................................................................................450
Database Tasks.....................................................................................................452
Checking the Database...........................................................................................452
Database Alert ........................................................................................................452
Database Error Logs...............................................................................................454
Operating System Tasks......................................................................................456
System Logs ...........................................................................................................456
Other Tasks ...........................................................................................................460
Check the Uninterruptible Power Supply................................................................460
< MO (Magneto-Optical)
< CD (Recordable)
Preprinted forms:
< Shipping documents
< Invoices
< Checks
Special supplies, such as
magnetic toner cartridge.
Normal supplies:
< Laser printer toner
< Paper (for printers)
< Batteries
< Diskette
< Pens, and so on
Check consumable supplies
Chapter 6: Scheduled Monthly Tasks
Checklists
Release 4.0B
64
Notes
Problem Action Resolution
Chapter 6: Scheduled Monthly Tasks
R/3 Tasks
R/3 System Administration Made Easy
65
R/3 Tasks
Memory Defragmentation
What
A computers memory behaves similar to that of a hard disk. As different programs execute,
they are loaded into and later deleted out of memory. Over time, like a hard disk, the usage
of the computers memory becomes fragmented with unused spaces scattered throughout.
Why
At a certain point you may have sufficient free memory (that is, the total of all the unused
spaces), but not a contiguous (single) piece of memory large enough to allow certain
programs to execute. At that point, those types of programs attempting to run that need
contiguous memory will fail because they cannot be loaded into memory.
How
To defragment the systems memory:
1. Stop R/ 3.
This step includes stopping R/ 3 on all application and database servers.
See chapter 10, the section Start/Stop R/3.
2. Restart R/ 3.
You only need to restart R/ 3, you do not need to cycle the server.
Whenever R/ 3 is restarted, the buffers are refreshed. This process means that the first
person who accesses the buffered object will have a long response because the system must
get the data from disk and load it into the buffer. The second person will have a normal
(quick) response time. This process repeats until all normally used objects are loaded into
the buffer. This usually takes up to a day to accomplish.
Chapter 6: Scheduled Monthly Tasks
Database Tasks
Release 4.0B
66
Database Tasks
Plotting Database Growth
What
Plotting database growth is a basic requirement to planning for database and hardware
expansion.
Why
Hardware expansion typically requires that the server be brought down before installation
of additional hardware. The time required to complete this shutdown, and possible
problems that may occur, need to be considered when planning the expansion. Because of
the system shutdown, possible problems, and significant lead times, the expansion needs to
be coordinated with the users.
Plan ahead for critical periods such as year-end, when you do not want the system to be
changed. You need to do your change before or after the critical period. If the decision is to
make the change after this time, consider whether you have sufficient capacity to get
through the critical period.
How
To effectively plan for this expansion, record the database and tablespace sizes and plot
their growth curve over time. This information should give you a rough estimate as to when
you will need to expand the storage space. Remember, if new SAP functionality is
implemented, the slope of the growth curve will change. For additional information, see
chapter 5, the section Monitor and Plot Database Growth.
Chapter 6: Scheduled Monthly Tasks
Operating System Tasks
R/3 System Administration Made Easy
67
Operating 8ystem Tasks
Performing a Full 8erver Backup
What
An offline backup of the entire server is done at the operating system level. This process
requires that the R/ 3 System and the database be down so that no files are open.
Why
Performing an offline backup is necessary for files that cannot be backed up if the R/ 3
System or the database is active. With this full-server backup, you know you have
everything on the server. If you experience major system problems, you will have a
defined point from where everything is backed up and from where you can begin a restore.
When
A full-server backup should be performed before and after major changes on the server,
such as:
< Installing new software
< Upgrading installed software
< Changing hardware
If a change has a catastrophic effect (a disaster), you will need to recover the server to its
before-the-change state.
How
To perform a full server backup:
1. Stop the R/ 3 System.
2. Stop the database.
3. Stop all services (NT).
4. Execute the backup using your backup program (database and file system).
5. Check backup times and logs.
6. Cycle the server.
Reviewing File 8ystem Usage
The monthly tasks for reviewing file system usage are the same as the weekly tasks, but are
completed monthly. For additional information, see chapter 5, the section Review File System
Usage.
Chapter 6: Scheduled Monthly Tasks
Other Tasks
Release 4.0B
68
Other Tasks
Checking Consumable 8upplies
What
Consumable supplies are those that you use regularly. Examples are: cleaning cartridges,
data cartridges (tape and disk), laser printer toner, ink cartridges, batteries, forms,
envelopes, etc.
Within the group of consumable supplies are critical supplies. These are supplies which if
they run out, could affect or stop the business operations. Examples are preprinted forms
with your companys name or other special printing, and magnetic toner cartridges.
The amount of spare supplies purchased and on-hand should be enough to handle normal
and slightly abnormal usage and to allow for time to purchase replacements.
Why
Running out of supplies will create an inconvenience, or even an operational problem.
Critical 8upplies
If an item is critical, and you run out of it, business operation may stop.
Example, if you run out of the magnetic toner cartridge for the check printer, you will not be
able to generate checks out of the system. At this point, either you cannot print checks to
pay your vendors, or you have to manually type the checks (if you have blank manual check
stock on hand).
Special or custom supplies such as the following require special consideration:
< Special magnetic ink toner cartridges to print the MICR characters on checks.
Not every computer supplier will stock these special cartridges.
< Preprinted forms (with company header, instructions, or other custom printing).
Because of the custom nature of these items, there is usually a significant lead time to
restock these items.
If it is a critical item, stock extras, the first spare may be bad or defective.
Murphy says: When you need something immediately, it will be Friday evening and
vendors and stores will be closed.
Chapter 6: Scheduled Monthly Tasks
Other Tasks
R/3 System Administration Made Easy
69
How
To check consumable supplies:
< Check the expiration date on supplies that are subject to aging.
This applies to supplies in use and those in inventory (not yet in use).
< Check supplies that have a time in service expiration, such as hours, cycles, etc.
Example, certain DAT tapes are rated for 100 full backups. After that they should be
discarded and replaced with new tapes. (This usage limit can be entered into the
SAPDBA control file.)
< Keep in touch with your purchasing agent and the market place.
Market conditions may make certain supplies difficult to purchase. In such conditions,
the lead time and quantities to be purchased need to be increased.
For example, at one time, 120 meter DAT tapes cartridges were difficult to buy. . . at any
price.
< Track usage rates and adjust stocking levels and purchasing plans as needed.
Other Considerations
Certain supplies may have long lead times for purchase, manufacture, or shipping.
Do not make your lack of planning the purchasing agents emergency. If you do this too
often, you will soon use up your favors. Then when you really need help, the
purchasing agent may not be as willing to help you.
Chapter 6: Scheduled Monthly Tasks
Other Tasks
Release 4.0B
610
R/3 System Administration Made Easy
71
Chapter 7: 8cheduled Ouarterly Tasks
Contents
Checklists ................................................................................................................72
R/3 Tasks .................................................................................................................74
Backups ....................................................................................................................74
Security .....................................................................................................................74
Database Tasks.......................................................................................................78
Performing a Database Test Restore .......................................................................78
Operating System Tasks........................................................................................79
Cleaning Out Old Transport Files .............................................................................79
Other Tasks ...........................................................................................................710
Checking Maintenance Contracts...........................................................................710
Check your UPS Shutdown Process ......................................................................711