SAP System Administration Made Easy 4.0B

��

��

Release 4.0B

R

SAP Labs, Inc.

Palo Alto, California

Overviewing R/3 System and RolesOverview

© 1998 SAP Labs, Inc. 15–1

Chapter 15: Overviewing R/3 System and Roles

ContentsOverview ............................................................................................................................................................................................................15–1

System Landscapes..........................................................................................................................................................................................15–1The One-System Landscape.......................................................................................................................................................................15–2The Two-System Landscape.......................................................................................................................................................................15–3The Three-System Landscape ....................................................................................................................................................................15–4

Client Definition.................................................................................................................................................................................................15–4

Role of the Client...............................................................................................................................................................................................15–4Transports for System Landscape Maintenance.........................................................................................................................................15–5

Client Copy versus Client Transport ...............................................................................................................................................................15–6Transporting Clients ....................................................................................................................................................................................15–6Copying Clients ...........................................................................................................................................................................................15–7

Deleting a Client ................................................................................................................................................................................................15–7

Useful OSS Notes..............................................................................................................................................................................................15–7

Overview

Begin the implementation of SAP by defining all R/3 Systems and clients necessary for your productionenvironment. Depending on the size of your R/3 installation and the projects planned, you may requireseveral R/3 Systems that serve different purposes in your system group. These systems form the systemlandscape, and clients are distributed within this landscape. Once the system landscape is defined, animplementation 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 RolesSystem Landscapes

15–2 © 1998 SAP Labs, Inc.

A client is a commercially and organizationally independent unit in the R/3 System, which means that ithas its own data environment. In general, four different types of clients exist, and each type has a differentfunctionality, 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 differentpurposes (development, testing, master copy, and production), SAP strongly recommends that customersdo not use this configuration. The obvious advantage to this landscape is that there is less hardware topurchase and maintain for a single R/3 System. In the long run, however, the initial savings do not payoff because of the problems and limitations associated with this configuration. Another notabledisadvantage is that it is not possible to test a R/3 upgrade in a single-system landscape. Please see thefollowing 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 RolesSystem Landscapes

© 1998 SAP Labs, Inc. 15–3

As a consequence of these limitations, no further development is possible after production work hasstarted. Changes to repository objects can only be made when production operations are stopped fordevelopment and testing. If the system is stopped, the production downtime could adversely affect yourcompany.

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 andtesting 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 testingmust 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 developmentprojects 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 RolesClient Definition

15–4 © 1998 SAP Labs, Inc.

The Three-System Landscape

The recommended three-system landscape is the one most commonly used, and can meet the needs ofmost customers. In a three-system landscape, new developments can be tested without affecting theproduction environment, and upgrades can be performed without limitations. The quality assurancesystem integrates development efforts and allows you to check the validity and consistency of transportedobjects 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 ownseparate data environment, including:

• Customizing

• Master and transaction data

• User master recordsThe client can be formed under legal, economic, or administrative perspectives. All business data isprotected 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 isinvolved. 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 RolesRole of the Client

© 1998 SAP Labs, Inc. 15–5

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 movingthem 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. Thecontents 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 userdata to another client in the same R/3 System. The tool depends on profiles, allowingfor 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 toanother R/3 System. Like the client copy tool, client transport requires a profile fordefinition 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 RolesClient Copy versus Client Transport

15–6 © 1998 SAP Labs, Inc.

• Use change requests to allow new or modified Repository objects and customizing to be imported intoother 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/3System. During a client copy, a client is replicated within the same R/3 System to make a new client. Thediagram 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 ClientsThe client copy and client transport tools are necessary to actual setup various systems. Client copiesprovide a mechanism to duplicate a client in the same R/3 System. Client transport allows the movementof a client from one R/3 System to another.

There are two types of client transports—a client export (also refer as client transport) and a remote clientcopy. We will discuss client export in chapter 17 of this guidebook. A client transport involves extractingclient-dependent information from the database to a file on the hard drive. This file can then be laterimported into any number of R/3 Systems.

Overviewing R/3 System and RolesDeleting a Client

© 1998 SAP Labs, Inc. 15–7

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 theoption for client-independent tables when performing client-transport.

Copying ClientsThe 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 validationexits). 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 bereplicated. When copying just the customizing data, up to 150 MB is involved, so the process only requiresa few hours (depending on the hardware and system load). Because of time considerations, werecommend 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 processcan 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 anypoint.

Deleting a Client

Two different methods exist to delete a client. You can perform the deletion either at the operating systemlevel 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 RolesUseful OSS Notes

15–8 © 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 SystemOverview

© 1998 SAP Labs, Inc. 16–1

Chapter 16: Copying a Client within a R/3 System


Creating a New Target Client within the Source Client .................................................................................................................................16–1

Performing the Client Copy in the New Target Client....................................................................................................................................16–6

Viewing the Client Copy Activities ..................................................................................................................................................................16–9

Useful OSS Notes............................................................................................................................................................................................16–13

Overview

When a separate client is needed to test, customize, or train, you can create this client by copying anexisting 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 adevelopment/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 inthe Client field.

2. Enter DDIC in the username field.

3. Enter the password for DDIC.

4. Press Enter to accept the userdefault language or enter alanguage code (e for English.)

1

23

4

Copying a Client within a R/3 SystemCreating a New Target Client within the Source Client

16–2 © 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 tocreate a new target client.

5

6

7

8


© 1998 SAP Labs, Inc. 16–3

9. Enter the new target client number(any new three digit number, forexample, 100).

Do not use client numbers 000, 001, or066 for your new clients because theyare reserved by SAP.

10. Enter the new client name.

11. Enter the City in which the client islocated.

The Logical System field appliesonly to the ALE application.

12. Enter a currency code in the Stdcurrency field (enter usd for U.S.dollars).

13. Enter a category (in this example,Customizing).

14. Because this client will be used fordevelopment/customization, selectAutomatic Recording of Changes…

15. Click the possible entries button toselect Changes to Repository andclient-ind. customizing allowed.

16. Click the Save icon to proceed to thenext screen.

17. Click the Back icon to return toprevious screen.

For more information about the Client-independent object changes field, positionthe cursor in this field and press F1.

9 10

11

1213

14

15

16 17


16–4 © 1998 SAP Labs, Inc.

The chart below defines when certain change options can be used. It can serve as a helpful reference andprovide examples of the change options for both clients and systems. The “X” indicates for which clients orsystems the attribute may be used. Notice that multiple attributes may apply to some clients or systems. Insuch a situation, the most appropriate attribute depends on the landscape structure.

Clients: DEV TEST QTST PRD TRAIN SANDBOX

Client-dependent change options

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 options

Changes to Repository and client-ind. customizing allowed

X

No changes to client-independentcustomizing objects

X X

No changes to Repository objects X X

No changes to Repository andclient-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-specificdeveloped/customized functions)

SANDBOX Playground client (test other advanced R/3 function, self-train, etc.)


© 1998 SAP Labs, Inc. 16–5

18. You should see the new targetclient in the list.

19. Enter the transaction /nEND to exitthe 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 ArchiveMode).

• Check your available tablespace allocation with transaction code DB02 (see chapter 92,Analyzing Current Tablespaces Sizes. You may need to expand these tablespaces by addinga 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 usersare not on the system.

18

19

20

Copying a Client within a R/3 SystemPerforming the Client Copy in the New Target Client

16–6 © 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 theClient field (in this example, 100).

2. Enter sap* in the username field.

3. Enter the password for SAP*.


5. Choose Tools → Administration → Administration → Client admin. →Client copy → Local client copy.

Alternative:

→

6. In the Selected profile field, enterSAP_ALL to copy data from thesource client (in this example,SAP_USR).

7. Enter the Source client number (inthis example, 000).

8. Click the Execute in backgrd. buttonto run the client copy as abackground job.

1

2

3

4

5

6

7

8

Copying a Client within a R/3 SystemPerforming the Client Copy in the New Target Client

© 1998 SAP Labs, Inc. 16–7

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

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

16–8 © 1998 SAP Labs, Inc.

11. To schedule the job to runimmediately, click the Immediatebutton. Otherwise, select Date/Timeto choose an appropriate start time(in this example, click Immediate).

12. Click the Save icon.

13. Enter an Output device (in thisexample, LP01).

14. Click the Save button.

The message The background job wassuccessfully scheduled; result displayedin SCC3 appears.

Depending on the size of the R/3 client and profile that you selected, client copy could takefrom 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 SystemViewing the Client Copy Activities

© 1998 SAP Labs, Inc. 16–9

Viewing the Client Copy Activities

Follow this step-by-step procedure to ensure that your client copy was successful:

1. From the System Administrationwindow, 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 positioningthe cursor on its line.

3. Click Choose.

After the client copy is completed,the Status text should readSuccessfully completed.

4. After the process is completed,position the cursor on the line itemcontaining your source client.

5. Click Choose.

1

2

3

5

4


16–10 © 1998 SAP Labs, Inc.

A Log Analysis screen appears thatshows the client copy.

6. Click the Log button to see adetailed analysis of the client copy.

6


© 1998 SAP Labs, Inc. 16–11

This screen shows a detailed log ofthe client copy.

7. To view the log in even greaterdetail, click the Display more button.This step increases the number inthe Expand level in overall log field (1is the lowest level, 4 is the highestlevel).

7


16–12 © 1998 SAP Labs, Inc.

This screen shows the mostdetailed log (level 4) of the clientcopy.

If your client copy fails:

1. Examine your tablespaces with DB02, and then refresh the statistics to get currentinformation. Refer to chapter 92, Analyzing Current Tablespaces Sizes.

2. Check your archive directory <drive>:\oracle\saparch. If it is full, you have an archivestuck condition. Using sapdba, backup the saparch directory and rerun the client copywith archive mode set to off.

Copying a Client within a R/3 SystemUseful OSS Notes

© 1998 SAP Labs, Inc. 16–13

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



Deleting a SAP Client Using a SAP Executable (Ch. 19)

Deleting a Client Using R/3 Functionality (Ch. 20)


System Logistics CD Reference → Pre-Installation → Systems and Roles → Setting Up a SystemLandscape

R/3 System Online Help

Online Documentation CD Transport Control → Using the R/3 Transport Program → R/3 Transport:General Information

Basis Courses



Transporting a R/3 Client to another R/3 SystemOverview

© 1998 SAP Labs, Inc. 17–1

Chapter 17: Transporting a R/3 Client to another R/3 System


Creating the Transport Request ......................................................................................................................................................................17–1

Scheduling the Client Transport Background Job ........................................................................................................................................17–4

Checking the Transport Log ............................................................................................................................................................................17–8

Useful OSS Notes............................................................................................................................................................................................17–11

Overview

This chapter describes the first part of the export process, creating a transport request with transactionSCC8. 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 isdifferent from a “client copy” were a duplicate client is made within the same System. Exported files arefound in the <drive>:\usr\sap\trans\data and <drive>:\usr\sap\trans\cofiles directories. The followingstep-by-step procedure shows how to export a R/3 client.

Creating the Transport Request

Login to the client that you want toexport.


2. Enter DDIC in the username field.

3. Enter the password for DDIC.


1

23

4

Transporting a R/3 Client to another R/3 SystemCreating the Transport Request

17–2 © 1998 SAP Labs, Inc.

5. Choose Tools → Administration →Administration → Clientadmin.→ Client transport → Clientexport.

Alternative:

SCC8 is the preferred transactioninstead of SCC2.

→

6. From the Selected profile field, clickthe possible entries button to list thedefault profiles.

7. Based on the Description, click theProfile name containing theelements you want to transport (forexample, SAP_CUST).

8. Click Choose.

5

6

7

8

Transporting a R/3 Client to another R/3 SystemCreating the Transport Request

© 1998 SAP Labs, Inc. 17–3

9. From the Target system field, clickthe possible entries button to list thechoices.

10. Select the target systemidentification, <SAPSID> (in thisexample, PRD).

11. Click Choose.

12. Click the Enter button to review theparameters.

9

11

10

12

Transporting a R/3 Client to another R/3 SystemScheduling the Client Transport Background Job

17–4 © 1998 SAP Labs, Inc.

Scheduling the Client Transport Background Job

1. Ensure that the Selected profileentries are correct.

You can now select the Test runcheckbox to ensure that you havecorrectly configured everythingbefore transporting the client.

2. Click Execute in backgrd.

3. Click Schedule Job to schedule thebackground job to transport client001.

1

3

2


© 1998 SAP Labs, Inc. 17–5

4. Verify the parameters, then clickYes to continue.

An INFO client export screenappears.

5. After reading the instructions, clickEnter.

4

5


17–6 © 1998 SAP Labs, Inc.

6. Click Immediate to start the job.


6

7


© 1998 SAP Labs, Inc. 17–7

8. From the Output device field, clickthe possible entries button to list thechoices.

9. Click Save.

The messages Format set to‘X_65_132’ and The background jobwas successfully scheduled; resultdisplayed in SCC3 appears.

10. Do not panic if you see this screen.It means that the client copy hasalready started and is preventingtwo client copies from runningtogether.

When you see this screen, simplyclick OK.

8

9

10

Transporting a R/3 Client to another R/3 SystemChecking the Transport Log

17–8 © 1998 SAP Labs, Inc.

Checking the Transport Log

To monitor the progress of the client export:

1. ChooseTools → Administration → Administration → Client admin. → Copy logs.

Alternative:

→

2. In the beginning the Status textshould display Initializing…

3. To refresh the status, enter thetransaction /nSCC3.

3

2

1

Transporting a R/3 Client to another R/3 SystemChecking the Transport Log

© 1998 SAP Labs, Inc. 17–9

While you wait for the export process,invoke Qslice.exe (a program that isincluded in the Microsoft Resource Kit)to monitor the progress of the processonline. The graphics at the right-handside shows you that Oracle73.exe andr3trans.exe are currently active. The barshows you the CPU usage by theprograms.

The Client Copy Log Analysis screenappears. Ensure that the Status textsays Successfully completed for theTarget Client EXP.

4. Click once on the log entry of theEXP client transport that justcompleted.

5. Click Choose.

4

5

Transporting a R/3 Client to another R/3 System

17–10 © 1998 SAP Labs, Inc.

6. Click once on the line item again.

7. Click Choose.

A summary of the Client Copy LogAnalysis appears.

To view the complete technicalinformation on the export process, clickthe Log button.

6

7

Transporting a R/3 Client to another R/3 SystemUseful OSS Notes

© 1998 SAP Labs, Inc. 17–11

Useful OSS Notes

Note # Description





Importing a R/3 Client from another R/3 System (Ch. 18)


Software Logistics CD Reference → Implementation → QA Procedures → Planning Imports


Online Documentation CD System Administration → Transport → System/Transport Control

Basis Courses


Importing a R/3 Client from another R/3 SystemOverview

© 1998 SAP Labs, Inc. 18–1

Chapter 18: Importing a R/3 Client from another R/3 System


Before You Begin ..............................................................................................................................................................................................18–1

Creating the Target Client ................................................................................................................................................................................18–2

Sharing the Transport Directory of the Source R/3 System in the Target R/3 System...............................................................................18–6

Importing the Data into the Target R/3 System ..............................................................................................................................................18–8

Performing Post-Import Activities...................................................................................................................................................................18–9

Checking the Import Logs..............................................................................................................................................................................18–12

Useful OSS Notes............................................................................................................................................................................................18–16

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 transactionSCC8. The end of the export process results in files created in the source system’s 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 SystemCreating the Target Client

18–2 © 1998 SAP Labs, Inc.

You cannot reverse or undo a transport! SAP does provide such a function in the transportsystem. 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 theimport 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 youregularly 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 followthe step-by-step procedure below to create the target client:

1. Choose Tools → Administration → Administration → Clientadmin. → Client maintenance.

Alternative:

→

2. Click the Display/Change button.

The message Warning: the table isclient-independent (see Help forfurther Info) appears.

1

2


© 1998 SAP Labs, Inc. 18–3

3. Click New entries.

4. Enter the new target client number(any new three digit number, forexample, 100).

Do not use 000, 001, or 066 for yournew clients because they are reservedby SAP.

5. Enter the City where the client islocated.

The Logical System field appliesonly to the ALE application.

6. Enter a currency code in the Stdcurrency field (enter usd for U.S.dollars).

7. Because this client will be used fordevelopment/customization, selectAutomatic Recording of Changes…

8. Click the possible entries button toselect Changes to Repository andclient-ind. customizing allowed.

9. Click the Save icon to proceed to thenext screen.

10. Click the Back icon to return to theprevious screen.

3

4

5

6

7

8

9 10


18–4 © 1998 SAP Labs, Inc.

For more information about the client-independent object changes field, position the cursor inthis field and press F1.

11. Double-click the desired clientcategory type to select it (in thisexample, Test is selected.

Do not select the Productive category. Ifyou do, the post-import process cannot be performed.

12. In the Client-independent objectchanges field, click the possibleentries button.

11

12


© 1998 SAP Labs, Inc. 18–5

13. Select the desired option and clickEnter.

14. Click Save.

15. Choose System → Log off.

13

14

15

13

Importing a R/3 Client from another R/3 SystemSharing the Transport Directory of the Source R/3 System in the Target R/3 System

18–6 © 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 forclient-independent tables

• <drive>\usr\sap\trans\data\KO<transport number>.<SAPSID> (such as RT00010.DEV) as data file forclient-specific tables

• <drive>\usr\sap\trans\data\SX<transport number>.<SAPSID> (such as SX00010.DEV) as data file fortexts

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 forclient-independent tables

• <drive>\usr\sap\trans\cofiles\KO<transport number>.<SAPSID> (such as KT00010.DEV) as cofile forclient-dependent tables

The target R/3 System shares these two files so that transport can be performed. The following procedureassumes that a network connection exists between the source and target systems. If this is not the case, thenthis step should be performed with the help of some form of magnetic media.

1. Right-click the Windows NT Startbutton and choose Explore.

16

1

Importing a R/3 Client from another R/3 SystemSharing the Transport Directory of the Source R/3 System in the Target R/3 System

© 1998 SAP Labs, Inc. 18–7

2. Choose Tools → Map Network Drive.

3. Select the drive that you wish todeclare as the shared drive (in thisexample, drive T).

4. Enter the shared drive name of thesource R/3 server (in this example,\\pnsfo36\sapmnt.)

5. Click OK.

The shared directory T with itssubdirectories are displayed.

2

34

5

Importing a R/3 Client from another R/3 SystemImporting the Data into the Target R/3 System

18–8 © 1998 SAP Labs, Inc.

Importing the Data into the Target R/3 System

1. On the R/3 System, click theWindows NT Start button andchoose Programs → CommandPrompt.

To obtain the proper transport request number, change to directory trans\cofiles and executedir to view the KO and KT transport request file names. The highest number is the most recenttransport request number.

2. Change the directory to the sharedtransport directory (in thisexample, T).

3. To change to the proper directory,enter cd trans\bin at thecommand prompt.

4. To ensure the buffers have beenadded by the R/3 TransportSystem, enter tp showbuffer <TargetSAPSID> (in this example, tpshowbuffer prd).

1

2

4

3

Importing a R/3 Client from another R/3 SystemPerforming Post-Import Activities

© 1998 SAP Labs, Inc. 18–9

First import client-independent data,then client-dependent data.

5. To import client-independent data,enter tp import <SourceSAPSID>KO<Nr.> client<TargetClient Nr.> <Target SAPSID> (inthis example, tp importDEVKO00010 client100 PRD).

6. To import client-dependent data,enter tp import <SourceSAPSID>KT<Nr.> client<TargetClient Nr.> <Target SAPSID> (inthis example, tp importDEVKT00010 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 thetarget R/3 System:



3. Enter the password for sap*.


5

6

1

23

4

Importing a R/3 Client from another R/3 SystemPerforming Post-Import Activities

18–10 © 1998 SAP Labs, Inc.

5. Choose Tools → Administration →Administration → Clientadmin. → Client Transport → ClientImport.

Alternative:

→

6. Review the parameters and clickExecute in backgrd. button.

7. Click Schedule Job.

5

6

7

Importing a R/3 Client from another R/3 System

© 1998 SAP Labs, Inc. 18–11

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 jobwas successfully scheduled; resultdisplayed in SCC3 appears.

8

9

10

11

Importing a R/3 Client from another R/3 SystemChecking the Import Logs

18–12 © 1998 SAP Labs, Inc.

Checking the Import Logs

After completing the import procedure, check the log files to ensure that the process concludedsuccessfully.

1. Choose Tools → Administration →Client admin. → Copy logs.

Alternative:

→

2. The status of the post importprocess appears. Click on the lineitem that displays Processing…

3. Click Choose.

4. Click the line item that displaysProcessing… again.

5. Click Choose.

2

1

3

5

4


© 1998 SAP Labs, Inc. 18–13

The processing informationappears.

Another way to view the postimport process is to reviewbackground job status.

6. To monitor the post-importprocess, enter the transaction/nSMX.

6


18–14 © 1998 SAP Labs, Inc.

The screen informs you that theCLIENTEXPORT/IMPORT 100 jobis running.

7. Click Job overview to reviewdetailed 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. 18–15

9. The job is marked as an active job.

Depending on the amount of data youhave, the process may take a while.You may use any OS activitymonitoring tool (for example,QSLICE.EXE) to see the activities of theprocesses (for example, oracle73.exe anddisp+work.exe).

9

Importing a R/3 Client from another R/3 SystemUseful OSS Notes

18–16 © 1998 SAP Labs, Inc.

Useful OSS Notes

Note # Description



34395 tp return codes and programs used by tp

11677 Transports with event-controlled RDDIMPDP



Transporting a R/3 Client to another R/3 System (Ch. 17)


System Logistics CD Reference → Implementation → QA Procedures—Planning Imports


Online Documentation CD System Administration → Transport System/Transport Control

Basis Courses


Deleting a Client Using R/3 FunctionalityOverview

© 1998 SAP Labs, Inc. 20–1

Chapter 20: Deleting a Client Using R/3 Functionality


Here’s How… .....................................................................................................................................................................................................20–1

Monitoring the Delete Client Background Job ...............................................................................................................................................20–4

Useful OSS Notes..............................................................................................................................................................................................20–8

Overview

Deleting a client permanently removes the client from a R/3 System. Essentially, this process is the reverseprocess of creating a client (Client Copy, Client Transport, etc.). Before deleting any client, consult with allR/3 users to ensure that the client should indeed be deleted. (It is recommended that clients be deletedusing 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 upthe SAPSCRIPT and Batch-input data. SCC5 requires much smaller rollback-segments thanusing R3TRANS to delete a client that is mentioned in chapter 19, Deleting a SAP Client Using aR/3 Executable. R3TRANS runs faster than SCC5. SAP recommends using the method discussedin this chapter.

Here’s How…

Logon to the client that you would liketo delete:



3. Enter the password for sap*.


1

23

4

Deleting a Client Using R/3 FunctionalityHere’s How…

20–2 © 1998 SAP Labs, Inc.

5. Choose Tools → Administration.

6. Choose Administration → Clientadmin. → Special functions → Deleteclient.

Alternative:

7. Click the Background button todelete the client in background.

• There are two options that youmay choose:− Test run allows you to

simulate client delete andobtain a report for theprocess.

− Delete entry from T000 cleansup the client information intable T000 that stores theclient information.

• To use the default/current R/3server, you do not need toprovide any server name intoBackground servers field. Tochoose a different server, justenter the server’s name.

8. Click the Schedule job button.

5

6

7

8

Deleting a Client Using R/3 FunctionalityHere’s How…

© 1998 SAP Labs, Inc. 20–3

9. Click Yes.

10. Click Immediate.


9

10

11

Deleting a Client Using R/3 FunctionalityMonitoring the Delete Client Background Job

20–4 © 1998 SAP Labs, Inc.

12. Enter a printer name in the OutputDevice field.

13. Click the Save button.

The message The background job wassuccessfully scheduled; resultdisplayed 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


© 1998 SAP Labs, Inc. 20–5

2. Select the line item that indicatesthe target client we want to delete(in this example, 100).

3. Click Choose.

4. Select the line item that indicatesthe target client we want to delete(in this example, 100).

2

3

4


20–6 © 1998 SAP Labs, Inc.

The client deletion is still running.

5. Click Refresh to view the lateststatus.

6. To view the status online, clickMonitor.

The bar chart shows you thecurrent activities.

56


© 1998 SAP Labs, Inc. 20–7

7. Using QuickSlice, we can see thatoracle73.exe, the tenth disp+work.exeare running. This view tells youthat the Oracle database is busydeleting client dependent data(client 100). Meanwhile, theBackground Work Processes arebusy communicating with thedatabase.

7

7

Deleting a Client Using R/3 FunctionalityUseful OSS Notes

20–8 © 1998 SAP Labs, Inc.

Congratulations on successfullydeleting a client!

Useful OSS Notes

Note # Description

35952 Client deleted, space still filled in database

Deleting a Client Using R/3 FunctionalityUseful OSS Notes

© 1998 SAP Labs, Inc. 20–9



Deleting a R/3 Client Using a R/3 Executable (Ch. 19)


Online Documentation CD Transport Control → Client Copy Tools

Basis Components → System Administration → TransportSystem/Transport Control

Basis Courses

Workbench Organizer, Transport System, and Upgrade (BC325)

Overviewing R/3 Profile Maintenance ToolOverview

© 1998 SAP Labs, Inc. 24–1

Chapter 24: Overviewing R/3 Profile Maintenance Tool


What are Profiles?.............................................................................................................................................................................................24–2Instance Profile............................................................................................................................................................................................24–4Default Profile..............................................................................................................................................................................................24–4Start Profile..................................................................................................................................................................................................24–4

Process of Profile Maintenance.......................................................................................................................................................................24–5

R/3 Profiles Definition.......................................................................................................................................................................................24–8

How Do I Maintain Profiles?.............................................................................................................................................................................24–9Basic Tasks .................................................................................................................................................................................................24–9Extended Tasks.........................................................................................................................................................................................24–10

Hints and Questions .......................................................................................................................................................................................24–11Useful hints for Profile Maintenance..........................................................................................................................................................24–11

Warning: Values are not allowed.......................................................................................................................................................24–11Changed Parameters become Not Active .........................................................................................................................................24–11

Frequently Asked Questions .....................................................................................................................................................................24–11

Useful OSS Notes............................................................................................................................................................................................24–13

Overview

This chapter introduces the R/3 Basis tools that help you configure the R/3 Application Servers. Whensetting 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 theconfiguration exists a parameter, and the profiles assign values to these parameters. The R/3 System usesthree different profile types:

• Instance

• Default

• Start

You can modify each of these. However, changes in profiles are infrequent for most productive R/3Systems.

The instance profile provides an application server with configuration parameters that define the availableinstance resources (main memory, shared memory, etc.), and determines how to allocate memory to theR/3 application buffers. Typically, these parameter settings adapt the instance based on the desiredresources.

Overviewing R/3 Profile Maintenance ToolWhat are Profiles?

24–2 © 1998 SAP Labs, Inc.

To assign the same parameter value for all application servers, enter it in the default profile—for example,the name of the database host or the computer on which the message server is running. When you start aR/3 instance on a host, the start profile defines which R/3 services are started (for example, messageserver, dialog, gateway, or enqueue process). The SAP program startsap is responsible for initiating theseservice 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 simultaneouslyuse a single profile. Separate profiles are not required for each R/3 instance. In general, you could changethe 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 24–36 about R/3 Profile Maintenance describe how to maintain profiles from the ComputingCenter Management System (CCMS). The CCMS profile maintenance tool analyzes and assists in makingchanges to the profiles. The tool not only checks the accuracy of each profile, it also checks the integrity ofyour cumulative system setup. The benefits of using the CCMS over editing profiles at the operatingsystem 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 activeprofiles at the operating system level.

System configuration changes occur infrequently for most productive R/3 Systems. Alterations arerequired only in exceptional cases. For example, SAP service processes may need to be moved betweeninstances. Changes for non-productive systems can be frequent. In either of these two cases, having aneasy 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. Wethen show you how to maintain profiles. We divided the actions into basic tasks and extended tasks. Toprevent 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, thefollowing 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)


© 1998 SAP Labs, Inc. 24–3

<SAPSID> is the SAP system name, <Instance> is the SAP instance name, and <hostname> is the name ofthe server related to this profile. When the first instance of a R/3 System is installed, the system creates adefault 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\profileUNIX systems: /usr/sap/<SAPSID>/SYS/profile

<SAPSID> is the SAP system name and <SAPGLOBALHOST> is the name of the NT machine where theglobal profile directory is physically located. This global directory should be accessible from all hostcomputers in a R/3 System. Several R/3 instances can simultaneously use a single profile. Separateprofiles 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 isDVEBMGS00; and the hostname is pnsfo36:

The same parameter can be in a default or instance profile. The SAP startup process first looks for a profileparameter in the instance profile. If the parameter is not found, then the default profile is searched. If theparameter cannot be found in either of these locations, the default value is taken from the startup programcoding.

The profile file is structured as follows:

# This is a comment in a SAP profile:Parametername1 = Value1Parametername2 = Value2

Parameter names with a common root logically belong together. For example, the root of parameters thatcontrol the dispatcher within an application server is: rdisp/.


24–4 © 1998 SAP Labs, Inc.

Instance ProfileThe instance profile provides an application server with configuration parameters that adapt the instancebased on the desired resources. They also define the available instance resources (main memory, sharedmemory, roll memory, etc.), and how to allocate memory to the R/3 application buffers. To startapplication servers on several computers using identical parameter settings, a single instance profile canbe 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 ProfileTo assign the same parameter value for all application servers—for example, the name of the database hostor the computer where the message server is running—enter 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 ProfileName of the database host SAPDBHOSTName of the update server rdisp/vbnameName of the enqueue server rdisp/enqnameName of the server for handling background processing events rdisp/btcnameName of the computer on which the message server is running rdisp/msnameName of the TCP service under which the message server can be reached rdisp/msservName of the computer on which the SNA Gateway is running rdisp/sna_gatewayName 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 ProfileWhen you start a R/3 instance on a host, the start profile defines which of the following R/3 services arestarted, such as the message server, dialog, gateway, or enqueue processes. The SAP program startsap isresponsible for starting these service processes, and it uses a start profile to begin the startup process. Tostart the same SAP service processes on several computers, you can use a single start profile. Each R/3instance 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 ToolProcess of Profile Maintenance

© 1998 SAP Labs, Inc. 24–5

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, youcan use this parameter to start the SAP related database or to set up links to executables on Unixplatforms.

• 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, forexample, 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_parameterbegin 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 theO/S level. This tool archives the profiles as operating system files and stores a reference copy in thedatabase. The database copy contains a reference character used to create the profiles at the operatingsystem level. This process is called activating a profile, that at the operating system level, only getsoverwritten if specified in the profile maintenance tool (the system prompts you to save a profile). At theoperating system level, the reverse procedure is called importing a profile into the database.


24–6 © 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, youmust import the R/3 profiles before they can be edited by the profile maintenance tool. Two ways exist toimport 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. Thisprocedure 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 modifiedat the operating system level.

If you have imported the R/3 profiles, you can maintain the values of the profile parameters with threedifferent 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 canalso use R/3 profile maintenance to work on profiles that belong to different application servers at thesame time.

When you modify and store a profile, the old status in the database is not overwritten. Instead, a separateversion with the changed values is created. The R/3 System allocates an individual number for each


© 1998 SAP Labs, Inc. 24–7

profile version. Thus, the history of profile changes is stored in the database and each version can berestored at any time.

After a modification, you can complete extensive verification checks of one or more profiles. These checksinclude:

• 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 theallowed range of values of the parameters. The result of these checks appears in the form of a log, whichcontains two message types: warnings and error messages.

The following graphic shows the activation process of a newly modified R/3 profile in the database withflat file changes:

Changes do not take effect immediately in the associated R/3 instance. To activate the changes, you haveto activate the changed profile by creating a new profile file at the operating system level. Then stop andrestart the R/3 instance(s) for which you want the profile change to become effective.

Overviewing R/3 Profile Maintenance ToolR/3 Profiles Definition

24–8 © 1998 SAP Labs, Inc.

R/3 Profiles Definition

System parameters are defined and stored:

• In the coding

• In the default profileThe default profile /usr/sap/SID/SYS/profile/DEFAULT.PFL overwrites the settings from thecoding.

• In the instance profileThe instance profile usr/sap/<SAPSID>/SYS/profile/... overwrites the settings in the coding and inthe default profile.

As of release 3.0E some parameters can be dynamically changed during system operation. Manyparameters 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 onWindows NT and AS/400, when a work process is restarted while the system is running, the newparameters 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.2Before making changes, make a backup copy. Changes must be documented. No tab characters may beused.

• With transaction RZ10 in Release 3.0The profile file is activated when this is used. You are not allowed to edit the files on the operatingsystem level.

You can display the parameters as follows:

• Call up the report RSPFPAR (using Transaction SA38) to display the parameters for the instance thatyou are logged on to. (Report RSPARAM does the same, but RSPFPAR is more comfortable.) Whenyou 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 ToolHow Do I Maintain Profiles?

© 1998 SAP Labs, Inc. 24–9

• 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 theactivities 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 TasksThe 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/3profiles 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 ToolHow Do I Maintain Profiles?

24–10 © 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 newprofile 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 correctlychanged.

Extended TasksThis 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 profilefiles 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 bycomparing 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 thesystem.

Overviewing R/3 Profile Maintenance ToolHints and Questions

© 1998 SAP Labs, Inc. 24–11

Hints and Questions

Useful hints for Profile MaintenanceThe following useful hints for profile maintenance were compiled to help you to identify and resolveproblems:

Warning: Values are not allowed

When you maintain the system profiles with the CCMS tools with the transaction RZ10, the warningValuesare not allowed appears. It occurs only when parameters with numeric values are affected. The reason isthat the value to be set deviates from the default value for this parameter, or is not within the permissiblearea 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 SAP’s Earlywatch Service)

In the second case you can solve the problem by changing the default value or permissible area for thisparameter 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 aftera restart. For a system with several instances, you have to restart only the instance for which you havechanged 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 maintainingprofiles 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 QuestionsQ1: 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 defaultprofile.

• As of release 3.0E, some parameters can be changed dynamically during system operation.

Overviewing R/3 Profile Maintenance ToolHints and Questions

24–12 © 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. Thusparameters 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 onwhich you are currently logged on. When you double-click on the corresponding line, the origin of thecurrent 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 theDocumentation 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 profileof 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 beindividually maintained, because each system needs individual settings of the system parameters. Inparticular 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 thefollowing advantages:

- Simplified maintenance- Lower rate of errors

Overviewing R/3 Profile Maintenance ToolUseful OSS Notes

© 1998 SAP Labs, Inc. 24–13

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?



Introducing R/3 Release 3.1x Architecture (Ch. 1)


System Management CD Reference → Implementation → System Configuration


Online Documentation CD Computer Center Management System → R/3 System Administration

Basis Courses


Importing Profiles of Active ServersOverview

© 1998 SAP Labs, Inc. 25–1

Chapter 25: Importing Profiles of Active Servers


Importing All R/3 Profiles from Active Servers ..............................................................................................................................................25–1

Viewing the Imported Profiles..........................................................................................................................................................................25–2

Overview

Importing the profiles of active servers is complicated during the post-installation process of a new R/3System or when adding an application server. Profiles exist as flat files in your R/3 Server and areimported into R/3’s database so that they can be effectively maintained. The following step-by-stepprocedure shows how to import these profiles.

Importing All R/3 Profiles from Active Servers

1. Choose Tools → Administration →Computer Center → ManagementSystem → Configuration → ProfileMaintenance.

Alternative:

→

→

2. Choose Utilities → Import profiles →Of active servers.

After importing the profiles, they should always be maintained using this tool, not at theoperating system level.

1

2

Importing Profiles of Active ServersViewing the Imported Profiles

25–2 © 1998 SAP Labs, Inc.

The Display of Profile Check Logscreen appears after first importingthe R/3 profiles.

3. Scroll through the log to quicklycheck for errors.

4. Click Back to return to the previousEdit 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 entriesbutton to display a list of all R/3profiles.

34

1

Importing Profiles of Active ServersViewing the Imported Profiles

© 1998 SAP Labs, Inc. 25–3

The list of all imported R/3 profilesto 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 arechecked and a log appears. (The profile names in the database are taken from the corresponding file nameson the operating system.) When you have finished importing profiles, position the cursor in the Profilefield and select PF4. The names of the imported profiles will be displayed.



Overviewing R/3 Profile Maintenance Tool (Ch. 24)




Online Documentation CD Basis Components → System Administration → Computing CenterManagement System → R/3 System Administration → Profiles

Basis Courses


2

3

Importing Individual ProfilesOverview

© 1998 SAP Labs, Inc. 26–1

Chapter 26: Importing Individual Profiles


Here’s How… .....................................................................................................................................................................................................26–1

Overview

The creation of an instance profile results in a new R/3 application server is added to your R/3 System. Tomanage the new instance profile, you must import it.

Here’s How…


Alternative:

→

→

2. Enter the profile name (in thisexample, test_pro).

3. Click Create or choose Profile →Create. 3

1

2

Importing Individual ProfilesHere’s How…

26–2 © 1998 SAP Labs, Inc.

4. Enter a Short description of theprofile.

5. Specify the Administration Data (inthis example, the default values aredisplayed).

6. Select the Profile type.

7. Click Copy.

8. After transferring theadministration data, click Import orchoose Profile → Import.

4

5

7

8

6


© 1998 SAP Labs, Inc. 26–3

9. From the list, specify the operatingsystem file to which the profileshould be imported.

You can display all the profile filesin the global profile directory byclicking the Possible entries icon.

10. Click Copy. (The message/usr/sap/DEV/SYS/profile/DEV_DVEBMGS00_pnsfo36 imported appears.)

11. To save the new profile, chooseProfile → Save or simply click Save.

12. R/3 will ask if you want to activatethe profile. Click Yes to activate.Otherwise, click No. (The messageProfile TEST_PRO [version 0000001]saved and activated appears.)

9

10

11

12


26–4 © 1998 SAP Labs, Inc.

13. After reading the Caution dialogwindow, click the Enter icon orpress Enter to continue.








Basis Courses


13

Changing a Profile’s ParametersOverview

© 1998 SAP Labs, Inc. 27–1

Chapter 27: Changing a Profile’s Parameters


Changing Administration Data Parameters....................................................................................................................................................27–1

Changing Basic Maintenance Parameters......................................................................................................................................................27–4

Changing Extended Maintenance Parameters ...............................................................................................................................................27–5

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 followingexample shows how to change the Short description of a profile is provided in the procedures below.


Alternative:

→

→

2. From Profile use the possible entriesbutton.

2

1

Changing a Profile’s ParametersChanging Administration Data Parameters

27–2 © 1998 SAP Labs, Inc.

3. Double-click on the line of theprofile you wish to change (in thisexample, DEFAULT).

4. Select the Administration databutton.

5. Click Change to alter its originalvalue.

From this screen, you can modify thefollowing administration data:

• Short description of the profile

• File name in which the profileshould be activated

• Reference server for profileparameter check

• Profile type

6. After changing the data, click Copy.(In this example, the ShortDescription was changed.)

3

4

6

5

6

Changing a Profile’s ParametersChanging Administration Data Parameters

© 1998 SAP Labs, Inc. 27–3

7. To save the profile with changes,click the Save icon or choose Profile→ Save.

8. R/3 will ask if you want to activatethe profile. Click Yes, to activate.Otherwise, click No. (The messageProfile DEFAULT [version 000002]saved and activated appears.)

9. After you have read the Cautiondialog box, click Enter.

Remember, when changing a profile, R/3 automatically creates a new version. You can go toa previous version by using the procedure explained in chapter 34, Switching Back to an OlderVersion of a Profile.

7

8

9

Changing a Profile’s ParametersChanging Basic Maintenance Parameters

27–4 © 1998 SAP Labs, Inc.

Changing Basic Maintenance Parameters

The Basic maintenance tool enables you to quickly and conveniently edit parameters. The followingexample shows you how to change the ABAP program buffer size.


Alternative:

→

→

2. Choose the profile you wish tomodify from the Profile field (in thisexample,DEV_DVEBMGS00_PNSFO36).

3. Select the Basic maintenance button.


From this screen, you can change thefollowing basic maintenanceinformation:

• General data

• Buffer and work processes

• Number of work processes

5. In this example, the ABAP programname buffer size has been changedto 70,000 KB. You may use the“>>”, “>”, “<”, “<<” buttons tochange the parameters for any ofthe listed items.

6. Click Copy or choose Profile →Copy.

5

6

2

3

4

1

Changing a Profile’s ParametersChanging Extended Maintenance Parameters

© 1998 SAP Labs, Inc. 27–5

7. Click the Save icon or choose Profile→ Save.

The profile data is automaticallychecked before you leave the Basicmaintenance screens. Any errors orinconsistencies will be displayed.

8. R/3 will ask if you want to activatethe profile. Click Yes, to activate.Otherwise, click No. (The messageProfile DEV_DVEBMGS00_PNSFO36 [version 000002] saved andactivated appears.)

9. After you read the Caution dialogbox, click Enter.

Changing Extended Maintenance Parameters

The Extended maintenance tool enables you to maintain profiles on an individual parameter level. Thistool comprises an editor that creates, modifies, and deletes individual parameters. To change the systemdefault client follow the step-by-step procedure below.

7

8

9


27–6 © 1998 SAP Labs, Inc.


Alternative:

→

→

2. Choose the profile you want tochange from the Profile field (in thisexample,DEV_DVEBMGS00_PNSFO36).

3. Select the Extended maintenancebutton.


Because the list contains manyparameters, use the Find function.(The system default client belongs tothe group login, therefore, we coulduse login as the keyword forsearching purposes.)

5. Choose System → List → Find…

Two colors indicate the values of parameters—in this example black and red. Colors are usedfor ease of viewing and do not indicate errors.

3

2

4

5

1


© 1998 SAP Labs, Inc. 27–7

6. Enter login.

7. Click Find.

If parameters of the group login aredefined in the profile, then a pop-upmenu will list them. To replace aparameter value, follow the remainingsteps:

8. Click on the line login/system_client.

9. Click the Position cursor button.

10. Change the indicated parameter tothe value you need.


If the copy process is successful,the message The changed profile wastransferred appears.

6

7

8

10

11

9


27–8 © 1998 SAP Labs, Inc.

12. Click Back.

13. Click Save or choose Profile → Save.

The profile data is checkedautomatically before you leave theExtended maintenance screens. Anyerrors or inconsistencies will bedisplayed.

14. R/3 will ask if you want to activatethe profile. Click Yes, to activate.Otherwise, click No. (The messageProfile DEV_DVEBMGS00_PNSFO36 [version 000003] saved andactivated appears.)

14

12

13


© 1998 SAP Labs, Inc. 27–9









Basis Courses


15

Checking ProfilesOverview

© 1998 SAP Labs, Inc. 28–1

Chapter 28: Checking Profiles


Here’s How… .....................................................................................................................................................................................................28–1

Overview

Before you leave either the Basic or Extended maintenance screens, the profile data is automaticallychecked 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

Here’s How…


Alternative:

→

→

To check a single profile:

2. Click the possible entries button toobtain the Profile name and Version.

3. Click Check or choose Profile →Check.

The message No errors in profileDEFAULT [version 000002] appears.

3

2

1

Checking ProfilesHere’s How…

28–2 © 1998 SAP Labs, Inc.

CHECK RULES FOR PROFILE CLASSESParameter Class Check RuleInteger value Value smaller than default value → Error

Value larger than default by a factor of 10 → WarningTime value Value smaller than 0 → Error

Permissible characters: 0–9Boolean value Valid value set: 0, 1

ON, OFF YES, NO TRUE, FALSEOther values → Error

File directory Directory does not exist → WarningNo write authorization → Warning

File name File does not exist → ErrorTCP computer name Computer is not known to TCP → ErrorTCP service name Service name is not known to TCP → ErrorSAP server name Server name is not known to R/3 System → ErrorFile mask Check is not possibleStrings Check is not possibleCannot be changed by customer If particular parameters are changed by the customer → ErrorSpecial parameters If value does not contain a particular character string → ErrorStart 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 eachother. 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 ProfilesHere’s How…

© 1998 SAP Labs, Inc. 28–3








Basis Courses


Activating ProfilesOverview

© 1998 SAP Labs, Inc. 29–1

Chapter 29: Activating Profiles


Here’s How… .....................................................................................................................................................................................................29–1

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.

Here’s How…


Alternative:

→

→

2. Enter the Profile name and the mostrecent Version of the profile to beactivated (in this example,TEST_PRO is the Profile name and000001 is the Version).

1

22

Activating ProfilesHere’s How…

29–2 © 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 tellsyou that to activate the newchanges, you need to restart theapplication server.

5. Click Enter to exit.

An active profile that already exists in the R/3 System is automatically backed up, and is given theextension .bak. You can copy and display this backup file even if the R/3 System is unavailable.

3

5

Activating ProfilesHere’s How…

© 1998 SAP Labs, Inc. 29–3








Basis Courses


Checking Active Profile ValuesOverview

© 1998 SAP Labs, Inc. 30–1

Chapter 30: Checking Active Profile Values


Here’s How… .....................................................................................................................................................................................................30–1

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.

Here’s How…

To check the active profile values of an instance:


Alternative:

→

→

2. Choose Goto → Profile values → Of aserver.

The message Choose an applicationserver appears.

1

2

Checking Active Profile ValuesHere’s How…

30–2 © 1998 SAP Labs, Inc.

3. Double-click on the server name tochoose an application server.

A list appears, containing:

4. Parameter names in alphabeticorder.

5. Active values of the individualparameters.

Scroll through the list.








Basis Courses


3

4 5

Creating a ProfileOverview

© 1998 SAP Labs, Inc. 31–1

Chapter 31: Creating a Profile


Here’s How… .....................................................................................................................................................................................................31–1

Overview

There are two ways to create new R/3 profiles. You can either manually create them or copy them fromanother R/3 profile. This chapter shows you how to manually create a profile.

Here’s How…


Alternative:

→

→

2. Enter the profile name you want tocreate in the Profile field.

3. Click Create or choose Profile →Create.

1

2

3

Creating a ProfileHere’s How…

31–2 © 1998 SAP Labs, Inc.

4. Enter the name of the operatingsystem file, reference server, andprofile type, or accept the defaultvalues.

5. Click Copy.

Adjust the parameter values:

6. Select the Basic maintenance orExtended maintenance button (in thisexample, the Basic maintenancebutton has been selected).

7. Click Change.

4

5

6

7


© 1998 SAP Labs, Inc. 31–3

8. Modify the parameters as needed(in this example, the System name,System number, and Instance name,and the number of work processeshave been modified).

9. Click Enter (if any errors exist, anerror screen appears).


11. To save the profile, choose Profile→ Save.

The profile data is automaticallychecked before leaving themaintenance screens. Any errors orinconsistencies will be displayed.

This example of an error screenshows that R/3 has detectedincorrect parameter values (clickYes to display the error or click Noto correct without display).

12. Click Yes to display the incorrectvalue.

The message Invalid profileparameters detected appears.

8

11

9

10

12


31–4 © 1998 SAP Labs, Inc.

13. Scroll down and locate the errormessage.

In this example, an error resultedfrom a lower-than-acceptableparameter value.

14. Enter the correct value.


The message The changed profile wastransferred appears.

16. Click the Back icon.

13

14

15

16


© 1998 SAP Labs, Inc. 31–5

17. An Activate profile dialog box asks ifyou want to activate the profile.Click Yes to activate. Otherwise,click No.

The message Profile NEW_PRO[version 000001] saved and activatedappears.









Basis Courses

Technical Core Competence (BC310/BC314/360/BC361/BC362/BC370)

17

18

Copying a ProfileOverview

© 1998 SAP Labs, Inc. 32–1

Chapter 32: Copying a Profile


Here’s How… .....................................................................................................................................................................................................32–1

Overview

Use the copy function to create a new profile with some, or all, of the features of another source profile.

Here’s How…


Alternative:

→

→

2. Enter the Profile name.

3. Enter the Version.


1

2

4

3

Copying a ProfileHere’s How…

32–2 © 1998 SAP Labs, Inc.

The Copy Profile screen with thesource profile name and versionand target profile name appears.

5. Enter the Profile name to be copied(for example, DEV_NEW_PROFILE).

6. Click Copy.

A new version ofDEV_NEW_PROFILE will begenerated based on the profileDEV_DVEBMGS00_DODGERS.

The message ProfileDEV_NEW_PROFILE [version000001] was generated appears.








Basis Courses


5

6

Deleting a ProfileOverview

© 1998 SAP Labs, Inc. 33–1

Chapter 33: Deleting a Profile


Deleting a Single Profile ...................................................................................................................................................................................33–1

Deleting All Versions of a Profile.....................................................................................................................................................................33–2Preparing Profile Sample for Deletion .........................................................................................................................................................33–2Deleting the Profiles ....................................................................................................................................................................................33–5

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-stepprocedure shows you how to delete the profile.


Alternative:

→

→

2. Enter the Profile name and Versionof the profile you want to delete.

1

2

Deleting a ProfileDeleting All Versions of a Profile

33–2 © 1998 SAP Labs, Inc.

3. Choose Profile → Delete →Individual profile.

4. Click Yes if you want to delete theparticular profile from thedatabase.

5. A dialog window appears and asksif you want to delete the profile atthe operating system level. ClickYes if you want to delete theparticular 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/3Profile (in the following example, TEST_PRO). Later, we will delete all versions of profile TEST_PRO.

Preparing Profile Sample for DeletionWe will use TEST_PRO as an example of a multiple version profile. Currently, TEST_PRO has version 1only. The following steps show you how to add another version of the profile.


Alternative:

→

→

3

4

5

1


© 1998 SAP Labs, Inc. 33–3

2. From the Profile field, enter theprofile name you want to modifyor click the possible entries button tolist the profiles.

3. Click Change.

4. For this example, we will modifythe Short Description by addingadditional comments.

5. Click Copy.

2

4

5

3


33–4 © 1998 SAP Labs, Inc.

6. Click Save or choose Profile → Saveto save current modification.

7. Click Yes to activate the newversion.

The message Profile TEST_PRO[version 000002] saved and activatedappears.

8. After reading the message, clickEnter.

6

7

8


© 1998 SAP Labs, Inc. 33–5

Deleting the ProfilesTo delete all versions of a profile:


Alternative:

→

→

2. From the Profile field, enter theprofile name you want to modifyor click the possible entries button tolist the profiles.

3. Choose Profile → Delete → Allversions → Of a profile.

1

3

2


33–6 © 1998 SAP Labs, Inc.

4. Click Yes if you want to delete allversions of the profile.

5. A dialog window appears and asksif you want to delete the profileresiding at the operating systemlevel. Click Yes if you want todelete it; otherwise, click No.

The message All versions of profileTEST_PRO deleted appears.

6. Click the possible entries button.

The deleted profile is no longer inthe list.

7. Click Cancel to continue.

4

5

6

7


© 1998 SAP Labs, Inc. 33–7








Basis Courses


Switching Back to an Older Version of a ProfileOverview

© 1998 SAP Labs, Inc. 34–1

Chapter 34: Switching Back to an Older Version of a Profile


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








Basis Courses


Comparing a Profile in a Database with an Active ProfileOverview

© 1998 SAP Labs, Inc. 35–1

Chapter 35: Comparing a Profile in a Database with an Active Profile


Here’s How… .....................................................................................................................................................................................................35–1

Overview

You can compare two R/3 profiles to check their similarities or differences. The following steps show youhow to compare a profile in the database with a file in the operating system.

Here’s How…


Alternative:

→

→

2. From the Profile field, enter theprofile name you want to compareor click the possible entries button tolist the profiles.

1

2

Comparing a Profile in a Database with an Active ProfileHere’s How…

35–2 © 1998 SAP Labs, Inc.

3. Choose Profile → Comparison →Profile in database → With activeprofile.

If any discrepancies exist, a log isdisplayed. Otherwise, the messageProfile data in database and activeprofile are consistent appears.








Basis Courses


3

Dynamic Switching of Profile ParametersOverview

© 1998 SAP Labs, Inc. 36–1

Chapter 36: Dynamic Switching of Profile Parameters


Here’s How… .....................................................................................................................................................................................................36–1

Overview

As of R/3 Release 3.0E, it is possible to dynamically switch some of the parameters. This step means thatchanges to specific parameters take effect, without having to restart the application server.

Here’s How…


Alternative:

→

→

2. Enter the Profile name and Versionin the appropriate fields (in thisexample, the Profile name isDEV_DVEBMGS00_PNSFO36; theVersion is 000003).

Click the possible entries button todisplay a list of profiles.

1

2

Dynamic Switching of Profile ParametersHere’s How…

36–2 © 1998 SAP Labs, Inc.

3. Choose Profile → Dyn. switching →Display parameters.

The list of switchable memorymanagement parameters appears.

4. Change the relevant profileparameters using extendedmaintenance (as described inchapter 27) and save theseparameters.

5. From the profile maintenance mainscreen, choose Profile → Dyn.switching → Execute or click theSwitch parameter.

6. From the list of active applicationservers, select the checkbox of theapplication server.

7. Click Continue.

3

4

5

6

7

Dynamic Switching of Profile ParametersHere’s How…

© 1998 SAP Labs, Inc. 36–3

8. Click the Back icon to return to theR/3 Profile Maintenance mainscreen.

The profile can be usedimmediately after the change. Youneed not restart the system. At theend, a parameter switching logappears.







Online Documentation Basis Components → System Administration → Computing CenterManagement System → R/3 System Administration → Profiles

Basis Courses


8

Overviewing System AdministrationOverview

© 1998 SAP Labs, Inc. 62–1

Chapter 62: Overviewing System Administration


Introduction to Starting and Stopping the R/3 System and Database .........................................................................................................62–1

Overview

A R/3 System consists of two instances: a R/3 instance and database instance. Both instances must be startedfor 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 thecommand prompt. SAPDBA executesSQL statements to start and stop theSystem.

SAP Service Manager is a Windows NTapplication.

→

Overviewing System AdministrationIntroduction to Starting and Stopping the R/3 System and Database

62–2 © 1998 SAP Labs, Inc.

SAP Executables are commands that canbe used in batch files or other scripts.

• startsap R3

• stopsap R3

• startsap DB

• stopsap DB

Computing Center Management System(CCMS) stops the Central R/3 instancefrom within the System or starts andstops application instances if you arerunning multiple application servers.

The following table shows which instance each method is able to start or stop (that is, default status):

SAPDBA Service Manager SAP Executables CCMS

Start Database X X XStop Database X XStart R/3 X X X (app. instances)Stop R/3 X X X

The R/3 instance and the database instance can be started and stopped separately with two exceptions:

• The R/3 instance cannot begin unless the database instance has been started.

• The database instance cannot be stopped unless the R/3 instance has been stopped.

Overviewing System AdministrationIntroduction to Starting and Stopping the R/3 System and Database

© 1998 SAP Labs, Inc. 62–3



Introducing R/3 Release 3.1x Architecture (Ch. 1)


System Management CD Reference → Implementation → System Administration


Online Documentation CD Basis Components → Database Administration

Basis Courses

Technical Core Competence (BC310)

Starting and Stopping the R/3 System Using CCMSOverview

© 1998 SAP Labs, Inc. 64–1

Chapter 64: Starting and Stopping the R/3 System Using CCMS


Stopping R/3 Using CCMS................................................................................................................................................................................64–1

Starting R/3 With the SAP Service Manager...................................................................................................................................................64–2

Overview

This chapter shows you how to stop the R/3 System by using the Computing Center Management System(CCMS) and then how to re-start the R/3 System by using the SAP Service Manager.

Stopping R/3 Using CCMS

1. Choose Tools → Administration →Computing Center → Managementsystem.

Alternative:

→

2. Choose Control → System Monitor.

3. Select the instance you want to stopby clicking on its graphic in theDisplay area.

1

2

3

Starting and Stopping the R/3 System Using CCMSStarting R/3 With the SAP Service Manager

64–2 © 1998 SAP Labs, Inc.

4. Choose Control → Stop SAPInstance.

To start an R/3 instance, choose Control→ Start SAP Instance.

5. Click Yes.

6. This message indicates that the R/3System has been shutdown. Sincewe do not want to reconnect at thistime, click No.

Since the R/3 System and theapplication instance are on acentralized instance, the shutdownprocess will end the current login.

Starting R/3 With the SAP Service Manager

1. To restart the service, click theWindows NT Start button andchoose Programs → SAP R3 → SAPService Manager for DEV_00.

1

5

6

4

Starting and Stopping the R/3 System Using CCMSStarting R/3 With the SAP Service Manager

© 1998 SAP Labs, Inc. 64–3

2. Click Start.

Wait until all the indicator lightsturn from gray to green. TheSystem is not restarted until thishappens.

3. Choose File → Exit to close thewindow.



Starting and Stopping the R/3 System Using the SAP Service Manager (Ch. 63)

Diagnosing the R/3 System Startup (Ch. 65)


System Management CD Reference → Implementation → System Administration → Startup andShutdown → How to Start and Stop an R/3 Instance → Starting andStopping the R/3 Instance


Online Documentation CD Basis Components → System Administration → CCMS → R/3 SystemAdministration → Starting and Stopping the R/3 System → Starting andStopping Instances

Basis Courses

Technical Core Competence (BC310/BC314)

2

Monitoring Work ProcessesOverview

© 1998 SAP Labs, Inc. 66–1

Chapter 66: Monitoring Work Processes


Here’s How.........................................................................................................................................................................................................66–1

Useful OSS Notes..............................................................................................................................................................................................66–4

Overview

The Process Overview screen displays detailed information to help you monitor system work processes andfine-tune performance. Displayed information includes:

• The number of work processes

• Programs being run by the work process

• Process and error status

• Amount of CPU time used by the process

Here’s How...

1. Choose Tools → Administration →Monitoring → System monitoring →Process overview.

Alternative:

→

2. Click CPU to view the time usage

of each work process.

1

2

Monitoring Work ProcessesHere’s How...

66–2 © 1998 SAP Labs, Inc.

The CPU time usage of each workprocess appears.

3. To view detailed information on aprocess in this list, position thecursor in the entry line of theprocess. (In this example, the firstprocess 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 forgetting a quick overview of the instance status.

Field Description

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 ProcessesHere’s How...

© 1998 SAP Labs, Inc. 66–3

5. Use the Page-up and Page-downbuttons to scroll the screen formore information.

The CPU time field allows you tomonitor how much activity has beenallocated to a particular work process.

5

5

Monitoring Work ProcessesUseful OSS Notes

66–4 © 1998 SAP Labs, Inc.

Useful OSS Notes

Note # Description

42074 Using the R/3 dispatcher monitor ‘dpmon’



Online Documentation CD Basis Components → System Administration → System Services → Tools forMonitoring the Systems → Displaying and Controlling Work Processes

Basis Courses


Viewing Transaction CodesOverview

© 1998 SAP Labs, Inc. 67–1

Chapter 67: Viewing Transaction Codes


Finding the Transaction Code for the Current Screen ..................................................................................................................................67–1

Overview

Menu paths and transaction codes are two ways to get to a desired screen within the R/3 System. Whilefollowing a menu path is generally more intuitive, it is slower than using a transaction code. To get to adesired 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 anyscreen, from that screen chooseSystem → Status.

2. The Transaction field found in SAPdata will show you how to quicklyget to the same screen in the future.

Enter /n before the transaction code togo from one screen to another. Forexample, if you are in the UserMaintenance screen and want to send asystem message, simply enter /nSM02in the Command Field. You will godirectly to the System Message windowwithout having to first exit the UserMaintenance window.

2

1

Viewing Transaction CodesFinding the Transaction Code for the Current Screen

67–2 © 1998 SAP Labs, Inc.

Other information found in theSystem Status Window:

1. License Expiration: The date youruser license expires. Note that thedate is in the American format(Month/Day/Year). If the licensehas not been applied for yet, thisscreen will be blank.

2. Node Name: This is equivalent toyour Host Name.

3. Database Name: This is equivalentto the System ID.



Locking and Unlocking Transaction Codes (Ch. 68)




Online Documentation CD Basis Components → System Administration → System Services → Utilities

Basis Courses


1

23

Locking and Unlocking Transaction CodesOverview

© 1998 SAP Labs, Inc. 68–1

Chapter 68: Locking and Unlocking Transaction Codes


Locking a Transaction Code ............................................................................................................................................................................68–1

Unlocking a Transaction Code ........................................................................................................................................................................68–3

Overview

Locking a transaction code immediately prevents users from using the function represented by thetransaction. For example, locking transaction SA38 (ABAP/4 Reporting) would prevent users from runningABAP/4 reports from the System menu.

Locking a Transaction Code

1. To view a list of all of thetransaction codes, choose Tools →Administration → Administration →Tcode administration.

Alternative:

→

2. Locate the transaction code youwant to lock.

If you are looking for a particularTransaction Code, you can search for itusing a wild card. For example, enterSE* to display all transaction codesstarting with “SE.”

1

2

Locking and Unlocking Transaction CodesLocking a Transaction Code

68–2 © 1998 SAP Labs, Inc.

3. Position the cursor on thetransaction code you want to lock(in this example, SE01).

4. Choose Transaction code →Lock/unlock. Or select the Lockedcheckbox and click the Enter icon.

5. The checkmark in the Lockedcheckbox indicates that thetransaction code is locked.

6. To verify that the transaction codehas been locked, try to run thetransaction by entering it in theCommand field.

A dialog box informs you that thetransaction has been locked.

7. Click OK.

3

4

5

6

7

Locking and Unlocking Transaction CodesUnlocking a Transaction Code

© 1998 SAP Labs, Inc. 68–3

Unlocking a Transaction Code

1. Enter the transaction /nSM01.

2. Locate the transaction you want tounlock (in this example, SE01).

3. Position the cursor on thetransaction you want to unlock.

4. Choose Transaction Code →Lock/unlock.

1

2

3

4

Locking and Unlocking Transaction CodesUnlocking a Transaction Code

68–4 © 1998 SAP Labs, Inc.

5. To verify that the transaction hasbeen unlocked, run the transaction.

The transaction code will nowproperly execute (in this example,transaction /nSE01 has returned usto the Transport System window).



Viewing Transaction Codes (Ch. 67)




Online Documentation CD Basis Components → System Administration

5

Monitoring System UpdatesOverview

© 1998 SAP Labs, Inc. 69–1

Chapter 69: Monitoring System Updates


Producing an Update Error as an Example ....................................................................................................................................................69–1

Monitoring a Flawed Update Process .............................................................................................................................................................69–4

Update Components and U1 and U2 Updates................................................................................................................................................69–5

Useful OSS Notes..............................................................................................................................................................................................69–7

Overview

The R/3 System provides a utility that monitors updates made to your system and ensures that it isworking normally. The Updating process records changes made by users in the system’s database. Thisutility provides a comprehensive set of tools which analyze and correct problems that can occur during anupdate.

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 havenot yet been processed

• Reprocess an update record that caused an abnormal termination (a test mode is also available forrepeating 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 manuallyrepeated

• 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 fromU1 (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. Thisexample 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 theupdate process.

Monitoring System UpdatesProducing an Update Error as an Example

69–2 © 1998 SAP Labs, Inc.

1. To execute the ABAP programVBTST300, enter the transaction/nSE38.

2. Enter VBTST300 into the Programfield.

3. Click Execute.

1

2

3

Monitoring System UpdatesProducing an Update Error as an Example

© 1998 SAP Labs, Inc. 69–3

By default, the followingparameters and their values aredisplayed.

4. From the Operation field, changethe value U to I, so that DuplicateKey problems are produced duringthe update process.

5. Click Execute.

This screen shows the result of theexecution.

4

5

Monitoring System UpdatesMonitoring a Flawed Update Process

69–4 © 1998 SAP Labs, Inc.

Monitoring a Flawed Update Process

1. To go to the Update Records: MainMenu choose Tools →Administration → Monitoring →Update.

Alternative:

→

2. By default, the current Clientnumber is displayed (in thisexample, 001).

3. The current User name is alsodisplayed (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 followingoptions 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 UpdatesUpdate Components and V1 and V2 Updates

© 1998 SAP Labs, Inc. 69–5

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 changescan be broken down into several parts. These parts describe the update components. By further breaking theupdate 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 databasechanges ahead of less-critical changes. Critical (or primary) changes are those that have control functionsin 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 primarytransaction 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 theseoperations when assigning update requests to update work processes.

All of the primary components of an update must be processed before the processing of secondarycomponents.

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 (workprocesses dedicated to processing V2 update components) are available, the V2 components are processedby a V1 update process.

1. This screen indicates an Error hasoccurred while entering thetransaction /nSE38 by user WLEE.

2. Click Update modules.

A message from the SAP officeappears.

1

2

Monitoring System UpdatesUpdate Components and V1 and V2 Updates

69–6 © 1998 SAP Labs, Inc.

3. Select the module name (in thisexample, TH_VB_TEST_01) byclicking once on its line.

4. Click Update status.

5. The popup window indicates thatthe Update process was terminated;its error message is ABAP/4processor: RAISE EXCEPTION.

6. Click ABAP/4 short dump to viewmore detailed information.

The ABAP/4 dump screen appears.

7. Click the Page-Down button to viewother error messages.

3

4

5

6

7

Monitoring System UpdatesUseful OSS Notes

© 1998 SAP Labs, Inc. 69–7

Useful OSS Notes

Note # Description

25801 New work process type UP2



Overviewing System Administration (Ch. 62)


System Management CD System Services → The System Log → Viewing and Retrieving a DumpAnalysis


Online Documentation CD Basis Components → System Services → Managing Update Records

Basis Courses

Advanced R/3 Administration (BC305)

Viewing the Dump AnalysisOverview

© 1998 SAP Labs, Inc. 70–1

Chapter 70: Viewing the Dump Analysis


Here’s How… .....................................................................................................................................................................................................70–1

Overview

Dump Analysis is an extensive list of information designed to help a user quickly pinpoint and resolveprogram errors.

The ABAP/4 Development Workbench issues a “short dump” when a report or transaction is terminatedbecause of a serious error. The system records the error in the system log and writes a snapshot of theprogram at the time of its termination to a special database table called SNAP. The following step-by-stepprocedure shows you how to view the Dump Analysis to get more information about the nature of theerror(s).

Here’s How…

1. Choose Tool → Administration →Monitoring → Dump analysis.

Alternative:

→

2. Choose Edit → Display list or clickthe display list icon.

1

2

2

Viewing the Dump AnalysisHere’s How…

70–2 © 1998 SAP Labs, Inc.

3. Place the cursor in the line of thedump you wish to view.

4. Choose Short dump → Dumpanalysis.

5. Choose Goto → Overview.

6. This ABAP/4 Short Dump Listoverview screen allows you toanalyze the problem based on thesections of the dump. You candouble-click on any of thesesections to display informationabout the nature of the error(s).

3

4

5

6

Viewing the Dump AnalysisHere’s How…

© 1998 SAP Labs, Inc. 70–3



Overviewing System Administration (Ch. 62)


System Management CD Reference → Implementation → System Management


Online Documentation CD Basis Components → System Administration → System Services → TheSystem Log → Dump Analysis

Basis Courses

Advanced R/3 Administration (BC305)

Overviewing R/3 System Workload and Buffer Performance MonitorOverview

© 1998 SAP Labs, Inc. 76–1

Chapter 76: Overviewing R/3 System Workload and Buffer PerformanceMonitor


Workload Monitor..............................................................................................................................................................................................76–2What Can You Check with the Workload Monitor? .....................................................................................................................................76–2Using the Workload Monitor ........................................................................................................................................................................76–3

Buffers in the R/3 System.................................................................................................................................................................................76–3Client Cache................................................................................................................................................................................................76–3Pool .............................................................................................................................................................................................................76–4

SAP Configuration Check.................................................................................................................................................................................76–4

Useful OSS Notes..............................................................................................................................................................................................76–4

Activity

Tables/Indices

Global

Alerts Workload Setup/Buffers

Local

Remote

Network

Operating System

ExceptionsAnalyses

Statistics Records

Buffers

Calls

Parameter ChangesActivity

System Configuration

Parameter Changes

Activity

System ConfigurationParameter 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 StatisticsPerformance Report

SAPOSCOL Destination

This section contains the System Performance layout and recommendations to ensure optimalperformance of your system. You should consider all possible factors before changing any ofthe parameters. The procedures described in this section do not replace the EarlyWatch Servicethat all R/3 customers should use.

Overviewing R/3 System Workload and Buffer Performance MonitorOverview

76–2 © 1998 SAP Labs, Inc.

Overview

The R/3 buffers frequently store user data and make this data available to the local application serverinstance. This process helps reduce access and workload on the database server, which does not need to berepeatedly accessed to obtain the same information. It also reduces network traffic, improving systemperformance.

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 astraightforward task.

You can also use table buffering to fine-tune applications which means that some or all of the contents offrequently 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 tothe end users. This monitor is also used to analyze bottlenecks. When reviewing system performance, youshould normally start by analyzing the workload statistics. You can analyze workload statistics for theserver you are working on or all other servers. You can also use the Workload Monitor to find out how theworkload is distributed over the servers and transactions. Furthermore, you can display the totals for allservers 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 serverin your R/3 System.

Overviewing R/3 System Workload and Buffer Performance MonitorBuffers in the R/3 System

© 1998 SAP Labs, Inc. 76–3

Using the Workload MonitorYou 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-tierarchitecture consisting of one database server, one or more application servers and many presentationservers, or a two-tier architecture consisting of one machine to support the database and applicationserver, with several presentation servers.

Client CacheEach R/3 instance (application server) has its own buffers. These buffers are also known as client cachesbecause they cache the customer’s programs in memory. The R/3 buffers are allocated in memory areaslocal 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 MonitorSAP Configuration Check

76–4 © 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 thispool.

Screen buffer These are the local work process buffers. Only one work process mayRoll area access these buffers at a time.

PoolSome SAP shared memory segments are grouped into one shared memory segment known as a pool. Thisgrouping is done to meet the operating system limits on the number of shared memory allocations perprocess. In most operating systems, you can allocate as many shared memory segments as required. Thelimits depend on the kernel configuration.

SAP Configuration Check

Poor configuration of the R/3 System can cause general performance degradation. Examples of poorconfigurations include inefficient workload distributions of the different SAP services, or untuned setupsof 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 MonitorUseful OSS Notes

© 1998 SAP Labs, Inc. 76–5



All chapters about R/3 System Workload and Buffer Performance Monitor (Ch. 76–81)


System Monitoring CD Reference → Monitoring Tools → SAP System


Online Documentation CD Computer Center Management System → CCMS Monitors → BufferMonitor

Basis Courses

Workload Analysis (BC315)


Analyzing the R/3 System WorkloadOverview

© 1998 SAP Labs, Inc. 77–1

Chapter 77: Analyzing the R/3 System Workload


Here’s How… .....................................................................................................................................................................................................77–2

Reviewing the Top 40 Response Times..........................................................................................................................................................77–7

Reviewing the Transaction Profile ..................................................................................................................................................................77–8

Overview

When analyzing system performance, you should review the workload statistics. You can analyzeworkload statistics for the server you are working on, or all the servers. Use the Workload Monitor to findout how the workload statistics are distributed over the servers and transactions, to display the totals forall servers, and to compare the performance of individual servers over specified time periods.

CPU Time

Presentation Server

Roll in

Rollout

LoadTime

Process Time WaitTime

DB Time

Dispatch Time

Response Time

Application ServerDatabase Server

Net

wor

kN

etw

ork

Analyzing the R/3 System WorkloadHere’s How…

77–2 © 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 thedispatcher to perform the execution to the time the result is returned to theSAPgui. The response time between the SAPgui and the dispatcher is notincluded in this value.

Average wait time The amount of time an unprocessed dialog step waits in the dispatcher queue fora 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 sourcecode 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 requestsare passed through the SAP DB interface and parsed into individual databasecalls. Take note of the proportion of database calls to database requests. If accessto information in a table is buffered in the SAP buffers, database calls to thedatabase server are not needed. Therefore, the ratio of calls/requests gives anoverall indication as to the efficiency of table buffering. A good ratio would be1:10.

Dispatch time The amount of time occupied in the work process. (Response time minus Waittime.)

Average DB requesttime

The logical database request time required for a dialog step. The time dependson the CPU capacity of the database server, network server and buffering, andon 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

Here’s How…

1. To go to the SAP R/3 CCMSPerformance Monitoring menu,choose Tools → Administration →Computer Center → ManagementSystem → Control → PerformanceMenu.

Alternative:

→

→

1


© 1998 SAP Labs, Inc. 77–3

2. To view the Workload Analysis, fromthe Performance Monitoringwindow, choose Workload →Analysis.

Alternative:

The only application server for thisexample is dodgers.

3. Click Choose for analysis.

4. Click the server name once to selectan application server (in thisexample, pnsfo36).

5. Click the Enter icon.

2

3

4

5


77–4 © 1998 SAP Labs, Inc.

6. Select a time period. You canchoose daily, weekly, or monthlystatistics. From this screen you canalso compare the performancedevelopment of a day, a week, anda month for specific time periods orfor specific servers. (In thisexample, Previous weeks has beenselected.)

7. Click the Enter icon.

8. Double-click on one of the weekslisted to select the time period.

6

7

8


© 1998 SAP Labs, Inc. 77–5

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 thenormal value. CPU intensive tasks have occurred during the time interval. The Average CPU Timeshould be approximately 40% of the Average Response Time. If it is above 40%, the problem may beone 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


77–6 © 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. TheAverage Wait Time should be less than 1% of the Average Response Time. (A high server workload canproduce higher wait times.) If it is above 1%, there may not be enough work processes, or workprocesses are too busy.

12. The Average Load Time is 18.7 ms (= 5.96% of the Average Response Time) which is normal. Load Timenormally represents the time for loading and generating ABAP/4 source code and screen informationfrom a database. The Average Load Time should be less than 10% of the Average Response Time. If it isabove 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 thisexample since the R/3 System started up.

14. Database Requests are the number of logical ABAP/4 requests for data in the database. These requestsare passed through the SAP database interface and parsed into individual database calls. Take note ofthe proportion of database calls to database requests. If access to information in a table is buffered inthe SAP buffers, database calls to the database server are not needed. There are 250,137 requests thatare 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 valueshould 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 normalvalue 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 thisvalue 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/3System, and therefore there are many read and write activities. These values are not indicative of acorrectly 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 timeinterval. These statistics help you pinpoint which transactions have the highest resource consumption.

Analyzing the R/3 System WorkloadReviewing the Top 40 Response Times

© 1998 SAP Labs, Inc. 77–7

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 ofyour R/3 System.

2. You can switch between the response time list and the database requests list by clicking Top requests orTop Time.

3. Click the Back icon to return the main Performance Workload Overview screen.

1

23

Analyzing the R/3 System WorkloadReviewing the Transaction Profile

77–8 © 1998 SAP Labs, Inc.

Reviewing the Transaction Profile

1. Click the Transaction profile buttonto view the time consumption foreach 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 amountof time among all other R/3 programs.

3. Click the Sort icon.

1

2

3


© 1998 SAP Labs, Inc. 77–9

The average response time for a transaction should not be greater than one second, with the exception ofthe following transactions:

Type of Transaction TransactionCode

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.


77–10 © 1998 SAP Labs, Inc.



All chapters about R/3 System Workload and Buffer Performance Monitors (Ch. 76–81)


System Monitoring CD Reference → Monitoring Tools → SAP System → Workload Monitor →Functionality of Workload Monitor → Workload Overview of a Server


Online Documentation CD Basis Components → System Administration → Computer CenterManagement System → CCMS Monitors → Buffers Monitor → Workingwith Buffers Monitor

Basis Components → System Administration → Computer CenterManagement System → CCMS Monitors → Workload Monitors

Basis Courses



Analyzing the R/3 BuffersOverview

© 1998 SAP Labs, Inc. 78–1

Chapter 78: Analyzing the R/3 Buffers


Here’s How.........................................................................................................................................................................................................78–1

Overview

With the CCMS Buffer Performance Monitor, you can analyze the state of R/3 buffers and evaluate theirquality. You can then use this analysis to pinpoint areas in which buffer sizes can be changed to improveperformance. The information displayed has been collected since server startup.

Here’s How…


Alternative:

→

→

2. To view the SAP Setup/buffers, fromthe Performance Monitoring window,choose Setup/buffers → Buffers.

Alternative:

1

2

Analyzing the R/3 BuffersHere’s How…

78–2 © 1998 SAP Labs, Inc.

• After starting R/3, the Hitratio % of the buffers have values of less than 95% (the normalvalue 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 bufferor 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 thishappens, you need to increase the size of the buffers (if you have enough free memory) bymaintaining the related instance parameters. After restarting the system, the Swaps objectswill be reset to 0.

• Swaps occur when objects are removed from the buffer and cannot be replaced until a newdatabase access retrieves the data.

3

7

4

8

5

9

6


© 1998 SAP Labs, Inc. 78–3

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 recommendthat 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 memoryequals 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 dependingon the field type

9. To view the detailed information on R/3 buffers, click on the Detail analysis menu button.


78–4 © 1998 SAP Labs, Inc.

This window provides a link to amore detailed analysis of thebuffers.

Paging may occur if too much memory is taken from the operating system and given to theR/3 buffers!

If there is a limitation on main memory, the R/3 buffer memory could be decreased. From aperformance standpoint, this configuration is the most beneficial.


© 1998 SAP Labs, Inc. 78–5

The following table provides information on the instance parameters that should be maintained for thevarious 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


78–6 © 1998 SAP Labs, Inc.





System Monitoring CD Reference → Monitoring → Tools → SAP System → SAP Buffers → R/3Buffers and Buffer Monitor → Tuning Buffers


Online Documentation CD Basis Components → System Administration → CCMS → CCMSMonitors → Buffer Monitor → Working with Buffer Monitors → DisplayingTable Buffers

Basis Courses



Analyzing Buffer StatisticsOverview

© 1998 SAP Labs, Inc. 79–1

Chapter 79: Analyzing Buffer Statistics


Here’s How.........................................................................................................................................................................................................79–1

Overview

This chapter shows how to use the CCMS Buffer Performance Monitor to display statistics about buffer andmemory usage over a period of time.

Here’s How...


Alternative:

→

→

2. To view the SAP Setup/buffers fromthe Performance Monitoring window,choose Setup/Buffers → Buffers.

Alternative:

2

1

Analyzing Buffer StatisticsHere’s How...

79–2 © 1998 SAP Labs, Inc.

3. Click the Detail analysis menubutton.

4. Click the Program button.

3

4


© 1998 SAP Labs, Inc. 79–3

5. If you want to view detailed R/3buffer information, click thePrevious buffer, Next buffer, Bufferedobjects, or History buttons.

If the program buffer has swappedobjects and the numbers continue toincrease, consider:• Increasing the ABAP/buffer size

parameter, which is located in thefile instance profile (for example,DEV_DVEBMGS00_pnsfo36).

• Shutting down the R/3 System andre-booting it, since program bufferfragmentation can occur after thesystem has been in use for a while.

6. Click the Back icon to return to theprevious screen.

7. Click Back icon to return to theprevious screen.

5

6

7


79–4 © 1998 SAP Labs, Inc.

8. To view the activities of theprogram buffer history click theHistory button.

An example of History of R/3 Buffers and Memory:

8

9


© 1998 SAP Labs, Inc. 79–5

9. In the time that has elapsed since this example, the R/3 System was re-booted and the free buffer sizechanged from 0 to 120.



All chapters about R/3 System Workload and Buffer Performance Analysis (Ch. 76–81)


System Monitoring CD Reference → Monitoring Tools → SAP System → SAP Buffers → R/3 Buffersand Buffer Monitor → Tuning Buffers


Online Documentation CD Basis Components → System Administration → Computer CenterManagement System → CCMS Monitors → Buffers Monitor → Workingwith Buffers Monitor

Basis Courses



Analyzing Parameters of R/3 BuffersOverview

© 1998 SAP Labs, Inc. 80–1

Chapter 80: Analyzing Parameters of R/3 Buffers


Here’s How… .....................................................................................................................................................................................................80–1

Viewing Parameters ..........................................................................................................................................................................................80–3

Overview

This chapter explains how to analyze R/3 buffer history to find the correct buffer sizes.

Here’s How…


Alternative:

→

→


Alternative:

2

1

Analyzing Parameters of R/3 BuffersHere’s How…

80–2 © 1998 SAP Labs, Inc.


4. Click the Parameters button.

3

4

Analyzing Parameters of R/3 BuffersViewing Parameters

© 1998 SAP Labs, Inc. 80–3

Viewing Parameters

There is one application server for thisR/3 System:

1. Select one of the hostnames byclicking once on the item line (inthis example, pnsfo36).

2. Click the History of file button.

3. This screen shows the history ofparameter changes. In thisexample, since 10/31/97, theabap/buffersize has been changedfrom 65,000 to 70,000.

To view only the active parameters(without the history of changes), clickthe Active parameters button.

1

2

3

Analyzing Parameters of R/3 BuffersViewing Parameters

80–4 © 1998 SAP Labs, Inc.





System Monitoring CD Reference → Monitoring Tools → SAP System → SAP Buffers → UsingBuffer Statistics


Online Documentation CD Basis Components → System Administration → CCMS → CCMS Monitors→ Buffer Monitor → Tuning Buffers

Basis Courses



Analyzing Buffer StorageOverview

© 1998 SAP Labs, Inc. 81–1

Chapter 81: Analyzing Buffer Storage


Analyzing Buffers..............................................................................................................................................................................................81–1

Overview

The CCMS Buffers Monitor lets you analyze the state of the R/3 buffers and evaluate their quality. By doingso, you can pinpoint areas in which buffer sizes can be changed to improve performance.

Analyzing Buffers

1. To go to the SAP R/3 CCMSPerformance Monitoring menu,choose Tools → Administration →Computer Center → ManagementSystem → Monitor → PerformanceMenu.

Alternative:

→

→


Alternative:

2

1

Analyzing Buffer StorageAnalyzing Buffers

81–2 © 1998 SAP Labs, Inc.


4. Click the Storage button.

3

4


© 1998 SAP Labs, Inc. 81–3

This screen contains generatedStorage information.

A Pool is a group of SAP shared memory segments.


81–4 © 1998 SAP Labs, Inc.



Analyzing R/3 Buffers (Ch. 78)


System Monitoring CD Reference → Monitoring Tools → SAP System → SAP Buffers → StorageCheck


Online Documentation CD Computer Center Management System → CCMS Monitors → Buffer Monitor→ Buffers in the R/3 System

Basis Components → System Administration → Computer CenterManagement System → Buffers Monitor → Working with Buffers Monitor

Basis Courses



Overviewing the Oracle Performance MonitorOverview

© 1998 SAP Labs, Inc. 82–1

Chapter 82: Overviewing the Oracle Performance Monitor


Database Performance Check..........................................................................................................................................................................82–2Policies and Procedures..............................................................................................................................................................................82–3

System Environment ...........................................................................................................................................................................82–3Procedures ..........................................................................................................................................................................................82–3Roles and Responsibilities ..................................................................................................................................................................82–3

Database System Controlling ..........................................................................................................................................................................82–3Policies and Procedures..............................................................................................................................................................................82–3

System Environment ...........................................................................................................................................................................82–3Policies ................................................................................................................................................................................................82–4Procedures ..........................................................................................................................................................................................82–4Roles and Responsibilities ..................................................................................................................................................................82–4

Useful OSS Notes..............................................................................................................................................................................................82–4

Overview

Activity

Tables/Indices

Global

Alerts Workload Setup/Buffers

Local

Remote

Network

Operating System

ExceptionsAnalyses

Statistics Records

Buffers

Calls

Parameter ChangesActivity

System Configuration

Parameter Changes

Activity

System ConfigurationParameter 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 StatisticsPerformance Report

SAPOSCOL Destination

This section contains the System Performance layout and recommendations to ensure optimalperformance of your R/3 System. Consider all the possible factors before changing anyparameters. The procedures described in this chapter do not replace the EarlyWatch Service thatall R/3 customers should use.

Overviewing the Oracle Performance MonitorDatabase Performance Check

82–2 © 1998 SAP Labs, Inc.

Database Performance Check

The database system is the most complex subsystem in the R/3 client/server architecture. A systemadministrator must be able to analyze the database and determine whether bottlenecks in the database arecausing poor performance for all users. Some questions the system administrator should consider and beable 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 bydatabase 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 databaseresources (The R/3 System, in particular, due to its three-tier client/server architecture, places specialdemands on database monitoring software.)

All information comes from Oracle’s own monitoring views and tables. Oracle provides information on thestate of the database in virtual tables, called “dynamic performance tables” or “V$” tables, which are heldin 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 isa 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 MonitorDatabase System Controlling

© 1998 SAP Labs, Inc. 82–3

Policies and ProceduresThis section offers samples of policies and procedures for monitoring database performance.

System Environment

Software Components

System Name SoftwareDEV CCMSQAS CCMSPD1 CCMSPD2 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 PD2Table extents T T D DTablespace Fill level T T D DMissing 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 eachsystem. This level of monitoring is of special importance on production machines.

Roles and ResponsibilitiesTask RoleWatching systems permanently Operator/DBA

Database System Controlling

Policies and Procedures

System Environment

Software ComponentsSystem Name SoftwareDEV SAPDBA 3.1HQAS SAPDBA 3.1HPD1 SAPDBA 3.1HPD2 SAPDBA 3.1H

Overviewing the Oracle Performance MonitorUseful OSS Notes

82–4 © 1998 SAP Labs, Inc.

Policies

Database maintenance tasks will be performed in special maintenance time frames using SAPDBA (forexample, Saturday during evening hours).

Procedures

All aspects of the database maintenance are covered by SAPDBA. See SAPDBA manual for a detaileddescription of SAPDBA.

Roles and ResponsibilitiesTask RoleReorganize Tables DBAReorganize Tablespaces DBACreating Missing Indices DBAEnlarging Tablespaces DBADistributing Database files DBATuning 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 MonitorUseful OSS Notes

© 1998 SAP Labs, Inc. 82–5



All chapters about Managing the Oracle Database for a R/3 System (Ch. 82–95)


System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle


Online Documentation CD CCMS → CCMS Monitors → Database Monitor → SAP/Oracle DatabaseMonitor

Basis Courses



Analyzing Database ActivityOverview

© 1998 SAP Labs, Inc. 83–1

Chapter 83: Analyzing Database Activity


Performance Analysis.......................................................................................................................................................................................83–1

Overview

The database buffer pool contains the database System Global Area (SGA ) block of memory and reducestime-intensive disk accesses. A high-quality SGA means that there are only a few disk accesses, and thatuser 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 theperformance analysis. To warm up the database, let it run for at least four hours, or until it hasa significantly high total data buffer reads level (for example, 1,000,000 reads).

1. To go to the SAP R/3 CCMSPerformance Monitoring window,choose Tools → Administration →Computer Center → ManagementSystem → Control → PerformanceMenu.

Alternative:

→

→

1

Analyzing Database ActivityPerformance Analysis

83–2 © 1998 SAP Labs, Inc.

2. To view the Oracle general databasefrom the Performance Monitoringwindow, choose Database →Activity.

Alternative:

3. A typical Data Buffer Size should bebetween 16 MB (16.384 KB) and 32MB (32.768 KB). In this example,39,320 KB is adequate. Data bufferquality should be at least 95%. Inthis example, the value of the Databuffer Quality is 99.2%.

If the data buffer has a quality levelof 70% or less, it indicates that thedata buffer is too small. The databuffer size can be changed bymodifying the value of db_block_sizewhich is defined in theinit<SAPSID>.ora file.

4. The ratio of Reads to Physical readsshould be greater than 10:1. Here,the ratio is 18,450,597 : 150,919which corresponds to a 122 : 1 ratio.This is okay because it is greaterthan a 10:1 ratio.

• These fields indicate that of the18,450,597 Reads, 150,919 blockreads have resulted from blocksbeing physically read fromdisk.

• The Physical writes fieldindicates that 54,009 Oracleblocks have been written todisk by the Database Writerprocess.

2

34

5

67 8

9

10

11


© 1998 SAP Labs, Inc. 83–3

5. The value of the Busy Wait is 18 (=0.00009 % of 18,240,597 Reads). A normal value for the Busy Wait isless than 5% of Data Buffer (Oracle Block) Read. Higher values for the Busy Waits indicate excessivecontention. 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 theconditions are fine, you may need to increase the Shared Pool Size. The low quality of the Cache couldresult from the System not being used enough (startup).

8. The value of the Log Buffer‘s Allocation Retries is 9 (= 0.004% of 217,376 Entries). A normal value is lessthan 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). Thispercentage 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 morethan 4:1 (the larger the better.) Since the System has recently been rebooted, it is not unusual for thepercentage to be low. However, a few days later the percentage should increase significantly andreturn 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:1to 20:1. If the ratio is 50:1 or higher, there may be expensive SQL statement, or the R/3 System has notbeen 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 than4: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 → DetailAnalysis Menu from the Performance Monitoring window.





System Monitoring CD Reference → Implementation → Monitoring Tools → DatabaseMonitors → Introduction to the R/3 Database Monitor forOracle → SAP/Oracle Performance Monitoring Strategies → Monitoring theDatabase Buffer (Oracle)


Online Documentation CD Basis Components → System Administration → CCMS → CCMS Monitors→ Database Monitor → SAP/Oracle Database Monitor → SAP/OraclePerformance Monitoring Strategies → Monitoring the Data Buffer (Oracle)


83–4 © 1998 SAP Labs, Inc.

Basis Courses



Analyzing Exclusive LockwaitsOverview

© 1998 SAP Labs, Inc. 84–1

Chapter 84: Analyzing Exclusive Lockwaits

Contents Overview ............................................................................................................................................................................................................84–1

Here’s How.........................................................................................................................................................................................................84–1

Overview

A lockwait occurs when a large number of R/3 user requests are channeled into a relatively small numberof 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 towait. This waiting period is called a lockwait. As the number of lockwaits increases, fewer and fewer R/3user requests can be processed by available R/3 work processes. In the worst case scenario—when thenumber of lockwaits equals the number of R/3 work processes—a small number of users can cause theentire R/3 System to freeze.

For example, an order taker puts a lock on available material, gets distracted, and does not confirm theorder. No other order taker will be able to lock the same item until the initial lock is released. A typical wayof solving this problem is to find the person holding the lock so that he or she can confirm the order andrelease it. If this is not possible, the lock is deleted. This will roll back the transaction of the lock-holder andrelease the material for other users.

You can search for exclusive lockwaits where at least one process is locked through a lock held by anotherprocess. The process of holding the lock and the waiting process(es) is described in the following step-by-step procedure.

Here’s How...

1. To go to the SAP R/3 CCMSPerformance Monitoring screen,choose Tools → Administration →Computer Center → ManagementSystem → Control → PerformanceMenu.

Alternative:

→

→

1

Analyzing Exclusive LockwaitsHere’s How...

84–2 © 1998 SAP Labs, Inc.

2. To go to the Database PerformanceAnalysis window, choose Database→ Exclusive lockwaits.

Alternative:

3. This screen indicates that there areNo exclusive lock-waits found, whichis desirable.

Lockwaits can cause poorly timed holds on resources that result in inefficient systemperformance. Lockwait situations can also cause an instant halt to the system performance. It isnecessary to find out which SAP Object or Objects lock a process. If a lockwait is caused by along-running job and is interfering with other processes, SAP administrators should identifythe user running the job and decide whether it should be postponed until a more convenienttime. If the lockwait is caused by a bad program, appropriate action, such as deleting the processthat causes the lock, should be taken.

3

2

Analyzing Exclusive LockwaitsHere’s How...

© 1998 SAP Labs, Inc. 84–3





System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle → Detailed Analysis (Oracle) → DetailAnalysis Menu (Oracle)


Online Documentation CD Basis Components → System Administration → CCMS → CCMSMonitors → Database Monitor → SAP/Oracle Database Monitor → DetailedAnalysis (Oracle)

Basis Courses



Analyzing the Dictionary BufferOverview

© 1998 SAP Labs, Inc. 85–1

Chapter 85: Analyzing the Dictionary Buffer


Here’s How.........................................................................................................................................................................................................85–1

Overview

The Dictionary Buffer information is read into memory from the dictionary tables stored on disk. When anOracle instance is first started, this cache is empty and must be loaded as the dictionary information isaccessed. For this reason, hit ratios are generally low at database instance startup and stabilize over time.

Here’s How...

Follow this step-by-step procedure to analyze the dictionary buffer:

1. To go to the SAP R/3 CCMS generalperformance menu, choose Tools →Administration → Computer Center→ Management System → Control →Performance Menu.

Alternative:

→

→

2. To go to the Database PerformanceAnalysis screen, choose Database →Activity.

Alternative:

2

1

Analyzing the Dictionary BufferHere’s How...

85–2 © 1998 SAP Labs, Inc.


4. Click the Dictionary buffer button.

4

3


© 1998 SAP Labs, Inc. 85–3

5. Click once in the first row of theUsed(%) column to select it.

6. Click the Sort button to view theUsed(%) list from the highest to thelowest value.

7. Notice that the Used(%) for some ofthe Dictionary Cache Objects hasreached 100%. This is not a criticalissue because the system quicklyallocates the Dictionary CacheObjects as needed, and fixes itself.

7

5

6


85–4 © 1998 SAP Labs, Inc.







Online Documentation CD Basis Components → System Administration → CCMS → CCMSMonitors → Database Monitor → SAP/Oracle Database Monitor→ SAP/Oracle Performance Monitoring Strategies → Detailed Analysis of theDictionary Buffer (Oracle)

Basis Courses



Analyzing Database PerformanceOverview

© 1998 SAP Labs, Inc. 86–1

Chapter 86: Analyzing Database Performance


Here’s How.........................................................................................................................................................................................................86–1

Overview

Monitoring call activity determines the work done on the system separated by both user and internaloperations.

Here’s How...

1. To go to the SAP R/3 CCMSPerformance Monitoring window,choose Tools → Administration →Computer Center → ManagementSystem → Monitor → PerformanceMenu.

Alternative:

→

→

2. To go to the Database PerformanceAnalysis window, choose Database→ Activity.

Alternative:

1

2

Analyzing Database PerformanceHere’s How...

86–2 © 1998 SAP Labs, Inc.

3. Click the Detail analysis menubutton to view other options.

4. Click the Performance databasebutton.

3

4

Analyzing Database PerformanceHere’s How...

© 1998 SAP Labs, Inc. 86–3

5. The ratio of User calls to Recursivecalls is about 3:2 (544,795 : 371,630);the ideal ratio is 5:1. The ratio in thisnewly-established R/3 System willimprove with use over time.





System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle → Detailed Analysis (Oracle)



Basis Courses



5

Analyzing Database Parameter ChangesOverview

© 1998 SAP Labs, Inc. 87–1

Chapter 87: Analyzing Database Parameter Changes


Here’s How… .....................................................................................................................................................................................................87–1

Overview

This section determines both the current and historical settings of the init<SID>.ora parameters. Note thatchanges to these parameters only take effect after the database instance has been restarted.

Here’s How…


Alternative:

→

→


Alternative:

1

2

Analyzing Database Parameter ChangesHere’s How…

87–2 © 1998 SAP Labs, Inc.


4. Click the Parameter changes button.

3

4


© 1998 SAP Labs, Inc. 87–3

5. This example indicates that06/10/1997 was the last date that thisparameter was changed.

6. Click the History of file button.

7. This example indicates that theDatabase Parameter’s valueSHARED_POOL_SIZE waschanged from 26,214,400 to26,200,000 on 11/17/1997.

5

6

7


87–4 © 1998 SAP Labs, Inc.







Online Documentation CD Basis Components → System Administration → CCMS → CCMSMonitors → Database Monitor → SAP/Oracle Database Monitor → DetailedAnalysis (Oracle) → Detail Analysis Menu (Oracle)

Basis Courses


Technical Core Competence (BC310/ BC360)

Analyzing the V$ROWCACHEOverview

© 1998 SAP Labs, Inc. 88–1

Chapter 88: Analyzing the V$ROWCACHE


Here’s How.........................................................................................................................................................................................................88–1

Overview

The Shared Pool (that is, the memory area in the SGA) is used by Oracle to hold several key memorystructures. 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. Itis regularly referenced by Oracle, as well as some application programs and database users. This chaptershows you how to analyze the Dictionary Cache statistics (V$ROWCACHE).

Here’s How...

1. To reach the SAP R/3 CCMSgeneral performance menu, chooseTools → Administration → ComputerCenter → Management System →Control → Performance Menu.

Alternative:

→

→


Alternative:

2

1

Analyzing the V$ROWCACHEHere’s How...

88–2 © 1998 SAP Labs, Inc.


To review the Database Performance, it isnecessary to display the v$values of thedatabase. Refer to the Oracle databasetraining manual for more information.

4. Click the Display V$ values button.

3

4


© 1998 SAP Labs, Inc. 88–3

5. Choose Goto → Statistics →V_Rowcache to reach the V$ values.

6. The percentage ratio of the totalGets and Getmisses should be lessthan 15% for the database and lessthan 10% if using SAP. In thisexample, the total number of allGets is 5,112 and the total numberof Getmiss is 1,428 which results ina ratio of 28%. This ratio is a littletoo high. If the percentage ratio issignificantly higher than 15% (forexample, 30%), the Shared Poolneeds to be enlarged.

To enlarge the Shared Pool Size (if you have enough additional memory), locate the file in thedirectory <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


88–4 © 1998 SAP Labs, Inc.





System Monitoring CD Reference → Monitoring → Tools → Database Monitors → Introduction tothe R/3 Database Monitor for Oracle → Detailed Analysis (Oracle)



Basis Courses



Analyzing the Database’s Tables and IndicesOverview

© 1998 SAP Labs, Inc. 89–1

Chapter 89: Analyzing the Database’s Tables and Indices


Here’s How.........................................................................................................................................................................................................89–1

Overview

This chapter shows you how to do internal database and consistency checks between the database and theR/3 System.

Check the status of the database tables and database indices frequently. Slightly fragmentedtables can adversely affect system performance!

Here’s How...


Alternative:

→

→

2. To view the database’s tables andindices information, chooseDatabase → Tables/Indexes.

2

1

Analyzing the Database’s Tables and IndicesHere’s How...

89–2 © 1998 SAP Labs, Inc.

3. From the Data Base Performance:Tables and Indexes screen, you cancheck the following:

• Internal database consistency

• Tables without indices

• Database and R/3 System

• Missing database objects (tablesand indices)

• Missing objects in the SAP DataDictionary.

• Click Refresh to get the mostcurrent statistics. Otherwise,old statistics will be displayed.

To do further analyses, from this screen select Goto → Check → Installation → DB <->ABAPDict. The missing objects will be displayed.





System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle → Detailed



Basis Courses



Analyzing Missing Indices ContentsOverview

© 1998 SAP Labs, Inc. 90–1

Chapter 90: Analyzing Missing Indices ContentsOverview ............................................................................................................................................................................................................90–1

Checking for Missing Indices ..........................................................................................................................................................................90–1

Useful OSS Notes..............................................................................................................................................................................................90–3

Overview

You can verify whether objects such as tables or indices defined in the ABAP/4 Dictionary are also definedin 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, accesstimes may increase and duplicate records may be created which make access unsafe.

Checking for Missing Indices

1. To check for missing indices, go tothe SAP R/3 CCMS PerformanceMonitoring window. Choose Tools→ Administration → ComputerCenter → Management System →Control → Performance Menu.

Alternative:

→

→

2. From the Performance Monitoringscreen, choose Database →Tables/Indexes.

2

1

Analyzing Missing Indices ContentsChecking for Missing Indices

90–2 © 1998 SAP Labs, Inc.

3. Click the Missing Indexes button.

4. In this example, the directorieslisted under Indexes missing in thedatabase indicate that there are nomissing indices. If you find missingindices, be sure to recreate them toachieve optimal performance.

Primary indices (ending in 0) ensure that line keys (row keys) are unique. Missing primaryindices are therefore critical. If a primary index is missing, you should consult SAP for helpwith its restoration. There is no simple procedure for restoring an index if a large number ofduplicate keys were created in a table.

Secondary indices (not ending in 0) are used for special scans and are only relevant for theirperformance. You may restore a secondary index for SAP tables using the Database Utility ofthe ABAP/4 Dictionary (transaction /nSE14). You can likewise access this utility from theindividual index analysis functions.

3

4

Analyzing Missing Indices ContentsUseful OSS Notes

© 1998 SAP Labs, Inc. 90–3

Useful OSS Notes

Note # Description

44395 SAPDBA: Missing indexes after reorg run







Online Documentation CD Basis Components → System Administration → CCMS → CCMSMonitors → Database Monitor → SAP/Oracle Database Monitor → DetailedAnalysis (Oracle) → Table without Indexes (Oracle)

Basis Courses



Monitoring Space-Critical ObjectsOverview

© 1998 SAP Labs, Inc. 91–1

Chapter 91: Monitoring Space-Critical Objects


Here’s How… .....................................................................................................................................................................................................91–1

Overview

This chapter shows you how to examine Space-critical objects to do internal database checks and consistencychecks between the database and the R/3 System. Related issues include situations where an object cannotbe allocated and overflow problems.

Here’s How…


Alternative:

→

→

2. To view information on thedatabase’s tables and indices fromthe Performance Monitoring window,choose Database → Tables/Indexes.

1

2

Monitoring Space-Critical ObjectsHere’s How…

91–2 © 1998 SAP Labs, Inc.

3. Click the Space critical objects button.

4. The message There are no criticaltables/indexes appears in the statusbar at the bottom of the window. Inthis example, no space-criticalobjects were found for this R/3server.

If space-critical objects are found, you may want to check the tablespace status and the extent oftables and indices (see chapter 93, Viewing and Extending Tablespaces, and chapter 94, AnalyzingExtents of Tables and Indices).



All chapters about Managing the Oracle Database for an R/3 System (Ch. 82–95)




Online Documentation Basis Components → System Administration → CCMS → CCMSMonitors → Database Monitor → SAP/Oracle Database Monitor → DetailedAnalysis (Oracle)

Basis Courses



3

4

Analyzing Current Tablespace SizesOverview

© 1998 SAP Labs, Inc. 92–1

Chapter 92: Analyzing Current Tablespace Sizes


Here’s How.........................................................................................................................................................................................................92–1

Overview

After installing the system and before transferring data, you should verify that space exists in alltablespaces. Do this regularly when your system is productive. If you find full tablespaces, you mustanalyze whether they should be extended and/or reorganized.

Here’s How...

1. To go to the SAP R/3 CCMSPerformance Monitoring window,follow the path Tools →Administration → Computer Center→ Management System → Control →Performance Menu.

Alternative:

→

→

2. To view information on theDatabase’s tables and indices, fromthe Performance Monitoring window,follow the path Database →Tables/Indexes.

2

1

Analyzing Current Tablespace SizesHere’s How...

92–2 © 1998 SAP Labs, Inc.

3. Click on the Current sizes button.

The Memory Management:Tablespaces window appears.

4. This list is sorted by Used%. Noticethat all of the Used Tablespacevalues are less than 90%—thestandard values for the system.

If the Used% of Tablespace is largerthan 90%, you should extend theTablespace (see chapter 93, Viewing andExtending Tablespaces).

4

3

Analyzing Current Tablespace SizesHere’s How...

© 1998 SAP Labs, Inc. 92–3





System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle → Detailed Analysis (Oracle) → Checkingfor Full Tablespaces


Online Documentation Basis Components → System Administration → CCMS → CCMS Monitors→ Database Monitor → SAP/Oracle Database Monitor → Detailed Analysis(Oracle) → Checking for Full Tablespaces

Basis Courses



Viewing and Extending TablespacesOverview

© 1998 SAP Labs, Inc. 93–1

Chapter 93: Viewing and Extending Tablespaces


Check Current Tablespace Sizes.....................................................................................................................................................................93–1

How to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb) .................................................................................93–3

Overview

When the database system can no longer assign extents in a tablespace (Oracle error 1547), you must extendthe 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 completelyrestored if you back up the new file and the control file. SAP recommends that you backup the extendedtablespace with the SAPDBA backup program BRBACKUP.

It is highly recommended that you perform a full system data backup before extending atablespace! Perform the following steps only if a backup has been completed! Table extensionsshould only be performed by qualified system administrators.

Check Current Tablespace Sizes

1. Click the Windows NT Start buttonand choose Programs → CommandPrompt.

2. At the Command Prompt, entersapdba. 2

1

Viewing and Extending TablespacesCheck Current Tablespace Sizes

93–2 © 1998 SAP Labs, Inc.

3. Enter c to choose Tablespaceadministration.

4. Enter c to choose Free space andfragmentation of all tablespaces.

You can also view the tablespaceallocations from within SAP byentering the transaction /nDB02.

Look for the percent of tablespaceallocation under %-Alloc. As a rule ofthumb, write down the names of thosethat are greater than or equal to 90%.

5. Press Return to continue to viewthe next page.

3

4

5

Viewing and Extending TablespacesHow to Extend Tablespaces which are Allocated Above 90% (as a Rule of Thumb)

© 1998 SAP Labs, Inc. 93–3

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 firsttablespace you want to alter (in thisexample, PSAPES31HI).

3. Enter f to Alter tablespace<tablespace> and Add Datafile.

12

3

6


93–4 © 1998 SAP Labs, Inc.

4. Enter s to Start (Add datafile).



4

5

6


© 1998 SAP Labs, Inc. 93–5

7. Enter q and press Return to go backto the Tablespace administrationscreen (assuming that a databasebackup has already beenperformed).

Repeat steps 1–7 to alter additionaltablespaces.

8. When the tablespace extensions arefinished, enter q to return to theSAPDBA main menu.

9. Enter q to Quit sapdba.

10. Enter y to confirm that you want toquit.

7

8

910


93–6 © 1998 SAP Labs, Inc.





DBA Oracle CD Reference → Production → Growth Management → Managing TablespaceExtension


Online Documentation CD Basis Components → Database Administration → Oracle → TablespaceAdministration

Basis Courses

Database Administration ORACLE (BC505)

Analyzing Extents of Tables and IndicesOverview

© 1998 SAP Labs, Inc. 94–1

Chapter 94: Analyzing Extents of Tables and Indices


Here’s How.........................................................................................................................................................................................................94–1

Useful OSS Notes..............................................................................................................................................................................................94–3

Overview

Eventually, the extents of a table or index may reach their maximum limit. These extents need to bemonitored and reorganized as the values begin to approach the threshold. Before you transfer data to atable or index, you should check if tables are close to reaching their maximum number of extents.

Here’s How...


Alternative:

→

→

2. To view information on theDatabase’s tables and indices fromthe Performance Monitoring window,choose Database → Tables/Indexes.

1

2

Analyzing Extents of Tables and IndicesHere’s How...

94–2 © 1998 SAP Labs, Inc.

3. Click the Checks button.

4. Click the Extents of tables and indexesbutton.

3

4

Analyzing Extents of Tables and IndicesUseful OSS Notes

© 1998 SAP Labs, Inc. 94–3

5. If the difference between the MaxExtents column and the Extents column is less than 100, databasereorganization is needed for the particular object(s). In this example, the differences are fine, becausethe largest Extent is 74 and the lowest MaxExtent is 300. If database reorganization is needed, use theSAPDBA 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 inwhich the number of extents comes close to this value, take notice. The value may reach theMaxExtent value and cause a terminated transaction. If you find tables with problems with themaximum number of extents, we recommend that you reorganize the table or the index. If areorganization is not possible, you can temporarily increase the MaxExtents value for the tableor 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 IndicesUseful OSS Notes

94–4 © 1998 SAP Labs, Inc.





System Monitoring CD Reference → Monitoring Tools → Database Monitors → Introduction to theR/3 Database Monitor for Oracle → Diagnosing SAP/Oracle PerformanceProblems → Monitoring Table and Index Fragmentation


Online Documentation CD Computer Center Monitor System → CCMS Monitors → Database Monitor→ SAP/Oracle Database Monitor → Detailed Analysis (Oracle)

Basis Courses



Performing Database ReorganizationOverview

© 1998 SAP Labs, Inc. 95–1

Chapter 95: Performing Database Reorganization


Checking Statistics ...........................................................................................................................................................................................95–1

Using Archiving Mode During the Reorganization ........................................................................................................................................95–1Advantages of a Reorganization in NOARCHIVELOG Mode: ....................................................................................................................95–1Data Security for a Reorganization in NOARCHIVELOG Mode..................................................................................................................95–2

Checking Extents using SAPDBA before Performing a Reorganization .....................................................................................................95–2

Checking Extents using R/3 before Performing a Reorganization...............................................................................................................95–6

Performing the Reorganization........................................................................................................................................................................95–9

Checking Number of Extents After Performing Reorganization Using SAPDBA .....................................................................................95–15

Useful OSS Notes............................................................................................................................................................................................95–19

Overview

Over time, tablespaces in the database may become fragmented and cause performance problems. Areorganization 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 arewritten. If you deactivate the ARCHIVELOG mode, there is no significant acceleration of thereorganization. Since the archive process ARCH runs parallel to the remaining background databaseprocesses, 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 ReorganizationChecking Extents using SAPDBA before Performing a Reorganization

95–2 © 1998 SAP Labs, Inc.

BRARCHIVE does not have to run for the period of the reorganization because no offline redo log filesare created.

2. Time is saved in the event of a recovery, as you can resume from the backup done after thereorganization (this is mandatory with the NOARCHIVELOG method).

Data Security for a Reorganization in NOARCHIVELOG ModeSAP recommends deactivating ARCHIVELOG mode only under certain conditions because it interrupts thecontinuity of the redo log files. Once reorganization is complete, you must reactivate the ARCHIVELOGmode 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 configworkstation.

The Windows NT User DEVADMshould be seen directly beneath thename of the local computer. If it isnot shown, log off and try again.


3. Enter the command sapdba to startthe SAP Database Administrationprogram. 3

2

1


© 1998 SAP Labs, Inc. 95–3

4. To reach the Reorganization menu,enter option d.

5. Enter a to check extents andfragmentation.

6. From the Check menu, reselect a tocheck objects with at least aspecified number of extents.

4

5

6


95–4 © 1998 SAP Labs, Inc.

7. Enter d to specify the least numberof extents the object must have forthe check.

8. Enter your specified number at theEnter number of extents prompt (forexample, 10).

9. Now, select s to start the check.

10. The number of objects with up toten extents will appear at thebottom of your screen. (In thisexample, three objects have beenselected. Record the tablespacenames for future steps in thischapter.)

11. Press the Return key to proceed.

78

9

10

11


© 1998 SAP Labs, Inc. 95–5

12. Enter option q to return to theCheck screen.

13. From the Check screen, return to theprevious screen by entering q.

14. Re-enter q to return to theReorganization screen.

12

13

14

Performing Database ReorganizationChecking Extents using R/3 before Performing a Reorganization

95–6 © 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 toview the Database Performancescreen. 1

1516


© 1998 SAP Labs, Inc. 95–7

2. Click Checks.

3. Select the Extents of tables and indexesbutton.

2

3


95–8 © 1998 SAP Labs, Inc.

4. To begin sorting, click anywhere inthe Extents column.

5. Click Sort.

4

5

Performing Database ReorganizationPerforming the Reorganization

© 1998 SAP Labs, Inc. 95–9

As a rule of thumb to judge which table, index, or tablespace needs to be reorganized, simplycalculate the difference between MaxEntents and Extents. If the difference is less than 100, thenyou should reorganize. In this example, the difference of MaxExtents and the Extents of TableD010Q of tablespace PSAPEL31HD is 289 (300-11). Since 289 exceeds 100, there is no need toperform a reorganization! To show you how to reorganize a table, we will use D010Q as anexample.

In cases where reorganization is not possible, you may temporarily increase the MaxExtentsvalue for the table and index.

6. Click the Windows NT Start buttonand choose Programs → SAP R3 →SAP Service Manager for PRD_01.

7. Click Stop to shutdown R/3.

8. Click OK to verify intentionalshutdown.

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 Backupusing 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 tostop the R/3 System.

6

7

8


95–10 © 1998 SAP Labs, Inc.


The Windows NT User DEVADMshould be shown directly beneaththe name of the local computer. If itis not shown, log off and try again.


3. Enter sapdba to start the SAPDatabase Administration program.

4. Enter d to select Reorganization.

1

2

3

4


© 1998 SAP Labs, Inc. 95–11

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 compressthe data files used by that tablespace. In this example, we will reorganize the table D010Q oftablespace PSAPEL31HD.

5. Enter c to select Reorganize singletable and index.

6. Enter b to select the Table or indexname.

7. Enter the name of the table to bereorganized.

5

67


95–12 © 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 andperform the full database backupfirst.

Since our database has been backedup, enter y to proceed.

Working …

8

9


© 1998 SAP Labs, Inc. 95–13

10. Enter 1 to select Start script(s)immediately.

Depending on the size of the table,transport may take a while. Aftertransport, an index is created.

Reorganization is complete whenyou see this message: ReorganizationSUCCESSFULLY completed.


10

11


95–14 © 1998 SAP Labs, Inc.

12. Enter q to return to the previousscreen.

13. Re-enter q to return to the SAPDatabase Administration screen.

14. Enter q to leave the SAP DatabaseAdministration program.

15. Enter y to confirm that you reallywant to quit.

12

13

1415

Performing Database ReorganizationChecking Number of Extents After Performing Reorganization Using SAPDBA

© 1998 SAP Labs, Inc. 95–15

Checking Number of Extents After Performing Reorganization Using SAPDBA


The Windows NT User DEVADMshould be shown directly beneaththe name of the local computer. If itis not shown, log off and try again.


3. Enter the command sapdba to startthe SAP Database Administrationprogram.

1

2

3


95–16 © 1998 SAP Labs, Inc.

4. Enter d to begin the reorganizationprocess.

5. Enter a to Check extents andfragmentation.

6. Enter a again to specify that youwant to check objects with a certainnumber of extents.

4

5

6


© 1998 SAP Labs, Inc. 95–17

7. Enter d to define a higher or equalvalue of number of extents that youwant 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 thelist of the tables which has greaterthan or equal to 10 extents. In thiscase, the extent of table D010Q hasbeen reduced.

11. Press the Return key to continue.

78

9

10

11


95–18 © 1998 SAP Labs, Inc.

12. Enter q to return.

13. Re-enter q.

14. Re-enter q to return to the SAPDatabase Amdinistration screen.

12

13

14

Performing Database ReorganizationUseful OSS Notes

© 1998 SAP Labs, Inc. 95–19

15. Enter q to quit.

16. Enter y to confirm that you reallywant 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

1516

Performing Database ReorganizationUseful OSS Notes

95–20 © 1998 SAP Labs, Inc.





Oracle Database Administration CD Reference Implementation → Database Tools → Database ToolSAPDBA


Online Documentation CD Basis Components → System Administration → DatabaseAdministration → Oracle Database Administration → DatabaseReorganization

Basis Courses

Database Administration ORACLE (BC505)

R/3 System Administration Made Easy4–1

��

��

Overview ..................................................................................................................4–2

Checklists ................................................................................................................4–3

Critical Tasks...........................................................................................................4–7Verify that R/3 Is Running .........................................................................................4–7Verify that the Backups Ran Successfully ................................................................4–7

R/3 Tasks ...............................................................................................................4–13Check that All Application Servers Are Up (Transaction SM51).............................4–13CCMS Central Alert Monitor (Transaction RZ20) ...................................................4–14Failed Updates (Transaction SM13) .......................................................................4–19System Log (Transaction SM21) ............................................................................4–23Background Jobs (Transaction SM37)....................................................................4–27Graphical Job Monitor (Transaction RZ01).............................................................4–29Locks (Transaction SM12) ......................................................................................4–31Active Users (Transactions SM04 and AL08).........................................................4–33Check the Spool (Transaction SP01)......................................................................4–36Batch Input Jobs, In-Error or To Be Processed (Transaction SM35) .....................4–38Work Processes (Transactions SM50 and SM51)..................................................4–40ABAP Dump Analysis (Transaction ST22) .............................................................4–42Workload Analysis of the System (Transaction ST03) ...........................................4–45Buffers (Transaction ST02).....................................................................................4–50

Database Tasks.....................................................................................................4–52Checking the Database...........................................................................................4–52Database Alert ........................................................................................................4–52Database Error Logs...............................................................................................4–54

Operating System Tasks ......................................................................................4–56System Logs ...........................................................................................................4–56

Other Tasks ...........................................................................................................4–60Check the Uninterruptible Power Supply ................................................................4–60

�

Chapter 4: Scheduled Daily Tasks

Overview

Release 4.0B4–2

��

Daily tasks are divided into the following categories:� Problems that need to be fixed� Indicators of developing problems

We have provided sample checklists that you may use and modify depending upon yourspecific needs. The checklists provided for your convenience include:� Critical tasks� R/3 System� Database� Operating system� Other� Notes


Checklists


��

System: __________

Date: ____/____/____

Admin: _____________________

��

Task Transaction -Description

Procedure Check off/initial

Check that the R/3 Systemis up.

Log on to the R/3 System

DB12 –Backup Logs:Overview

Check database backup

Database backup run time

Check operating system level backup

Operating system backup run time

Check that daily backupsexecuted without errors.

��

Task Transaction -Description


Check that all applicationservers are up.

SM51 – SAPServers

Check that all servers are up.

Check the CCMS alertmonitor (4.0+).

RZ20 – CCMSMonitor (4.0)

Look for alerts.

Check work processes(started from SM51).

SM50 –ProcessOverview

All work processes with a “running” or a“waiting” status

� Set date to one year ago� Enter * in the user ID

� Set to “all” updates

Look for any failedupdates (updateterminates).

SM13 –UpdateRecords

Check for lines with “Err.”


Checklists

Release 4.0B4–4

��

Task Transaction –Description


Set date and time to before the last logreview.

Check System Log SM21- SystemLog

Check for:� Errors� Warnings� Security messages� Abends� Database problems� Any other different event

Enter * in User ID

Verify that all critical jobs weresuccessful.

SM37 – SelectBackgroundjobs

Review any cancelled jobs.

Review for cancelled andcritical jobs

RZ02 –Graphical JobMonitor

Same as for SM37

Enter an asterisk (*) for user ID.Check for “old” locks SM12 – LockEntry List Check for entries for prior days.

Check users on system SM04 – Users

AL08 – Users

Review for an unknown or different userID and terminal. This task should be doneseveral times a day.

Check for spool problems SP01 – Spool:RequestScreen

Look for spool jobs that have been “inprocess” for over an hour.

Check job log SM35 – Batchinput: InitialScreen

Check for:� Jobs to be processed� Jobs in error

Check work processes SM50/51–Processes


Checklists


��

Task Transaction –Description


Review and resolvedumps.

ST22 - ABAPDumpAnalysis

Look for an excessive number of dumps.

Look for dumps of an unusual nature.

Review workloadstatistics.

ST03 –Workload:Analysis of<sid>

Review buffer statistics. ST02 – TuneSummary

Look for swaps.

��!��

Task Where Procedure Check off/initial

AL02 –Database alert

Review error log forproblems.

ST04 – DBPerformanceAnalysis:Oracle


Checklists

Release 4.0B4–6

��"��#


AL16 – OSAlerts

Review UNIX system logsfor problems.

OS06 – OSMonitor

Review operating system log

NT systemlog

Look for any errors or failures.

Check for failed logon attempts to theSAP servers.

NT securitylog

Look for errors or failures.

Review NT system logs forproblems.

NTapplicationlog

Look for errors or failures.

��


Check the uninterruptiblepower supply (UPS).

UPS programlog

Review for:� Events� UPS self test� Errors

$��

Problem Action Resolution


Critical Tasks


��

There are a few critical tasks that should be completed as soon as you arrive in the officeeach day. These tasks answer the following questions:� Is the R/3 System running?� Did the backups execute and complete successfully?

If the answer to either question is “no,” then the situation must be resolved quickly because:� If the R/3 System is down, no work can be done.� If the backups failed, and a disaster occurs, you could lose all the data since your most

recent good backup.

%��&��'��"

Your first task when you arrive at work is to check that the R/3 System is running. This taskis a high-level check to see if R/3 is up, and whether or not you can connect to it.

(��

If the system is not running, your users will be calling to find out what happened and whenthe system will be up again.

As a basic level check, if you can connect to the R/3 System, the following questions areanswered:� Is the R/3 System working?� Is the network between you and the R/3 System working?

)��

From a workstation, log on with the SAPgui.

If you can log on, the test is successful.

%��&��*��&��

(��

You need to verify that the backups that were supposed to run last night, ran successfully.Backups of the R/3 database and related nondatabase operating system level files areessential to recover the R/3 System.

Types of nondatabase files include:� Database log dumps� Data files for third-party applications that do not store their data in the system, such as

external tax files� Transport files� Inbound and outbound interface files� Externally stored print files


Critical Tasks

Release 4.0B4–8

(��

If there is a problem with any of the backups, the problem needs to be quickly resolved. If adatabase failure occurs that requires a restore, and the last backup failed, you will have torecover using the last successful backup that you have. If you do not have a good (usable)backup, you will have to go further back. This requires the application of more logs thefurther back you go, and increases the time required to restore the database and bring itcurrent.

Once the problem has been fixed, if it does not significantly impact performance, execute anonline backup. Even if it impacts performance, your company may make it policy to run theonline backup. This gives you a more recent backup.

At the operating system level, some of these files may need to be in sync with the R/3database. Restoring the R/3 System without these files results in an incomplete (unusable)restore (for example, external tax files that need to be in sync with the system data or the taxsystems reports will not match the R/3 reports).

(��

These critical tasks need to be done first thing in the morning. If there is a “graveyard”operations shift, it should be done once the backup job is complete. The “graveyard” shift isthe third-shift of the day, typically covering the period from 10:00 PM to 7:00 AM.

Any failed backup must be immediately investigated and resolved. Do not maintain a “wewill just run the backup again tonight and see if it works” attitude. If that backup fails, youhave another day without a backup.


Critical Tasks


��!��

+��

1. In the Command field, enter transaction DB12 and choose Enter(or choose Tools → CCMS, then DB Administration → Backup logs).

2. Record the date and time thatappears next to the button Lastsuccessful DB backup.

3. If there was a failed backup, thebutton Last unsuccessful databasebackup will appear.

4. Choose Overview of database backuplogs.

5. Examine the Start of backup andEnd of backup times, and thencompute the runtime.

6. Compare the actual backupruntime to the expected runtime.If the actual backup time is shorteror longer than expected,investigate for potential problems.

7. RC (return code) definitions:� 0000 (Successful)� 0001 (Success with warnings)� 0003 (Error in initialization)� 0005 (Error in processing)� 9999 (Started)

2

7

5

4


Critical Tasks

Release 4.0B4–10

��"��#�,��*��

General process is as follows:� Record the usual or expected run time for the backup.� Compare the actual backup time to the expected (usual) run time for the backup.

If the backup takes longer or shorter than this time, there may be a problem that needsto be investigated.

Any failed backup must be immediately investigated and resolved.

-$'.

For your UNIX level backup, review using the appropriate UNIX backup application.

$�

We assume that you are using the NTBackup application. If you are using another program,use that program’s documentation to determine its status after backup.

NTBackup records some log information in the NT event logs. A more specific log is writtento a file as specified when NTBackup is run.

+��

1. From Windows NT, choose Start→ Programs → Administrative tools→ Event viewer.

Create a shortcut on your desktop tothe Administrative tools group.

2. Choose Log → Application.

3. Under Source, look for theNTBackup entries.

4. Check for error messages, whichare indicated in red.

3

2


Critical Tasks


Possible causes for errors include:� Tape door or lever is not

completely closed.� Tape head is dirty.� Tape is damaged or worn out.� No tape inserted in tape drive.� File has been written to and

changed between the time thatthe backup was done and whenthe file verification was made.

5. To view the details for a line entry,double-click on the line. This viewwill give you a bit moreinformation.

��$�*��"

If the event log indicates problems,

1. Review the NTBackup log to determine more specifically what the error was.

2. Then using that information, take corrective action.

The NTBackup log is by default: c:\winnt\backup.log.If the NTBackup writes to a different file or directory, you need to review that file.


Critical Tasks

Release 4.0B4–12

1. In Explorer, select the directoryc:\Winnt.

2. Double-click on Backup.log.

Backup.log is a text file. This stepassumes that you have Notepadassociated with the extension log.

3. Scroll through the file to look forany problems.

4

5


R/3 Tasks


��

��/��/��/��-��012

(��

Transaction SM51 allows you to look at all the servers in your system (for example, the PRDdatabase server and all of its application servers). You do not have to log into each serverindividually.

(��

� If one of your dialog application servers is not up, the users who normally log on to thatapplication server will not have a server to log on to.

� If the batch application server is down, batch jobs that are specified to run on that serverwill not run.

+��

1. In the Command field, enter transaction SM51 and choose Enter(or choose Tools → Administration, then Monitor → System monitoring → Servers).

2. Review the list of instances underServer name.

Verify that all your instances arelisted. If it is listed, it is up andrunning. 2


R/3 Tasks

Release 4.0B4–14

��0��/��0��345

(��

Transaction RZ20 is a centralized alert monitor and is new with Release 4.0. With thistransaction, you can monitor the servers in your landscape, such as development, QA,testing, production, and so on. You no longer have to individually log into each system tosearch for alerts. If there is an alert, the monitor will link to many of the other transactionslater in this chapter.

See chapter 5, Changing Alert Threshold, for setting the alert threshold levels.

You can do many of your system monitoring tasks with the Central Alert Monitor.

The Central Alert Monitor is not a replacement for examining the other checklist tasks, asnot all alerts have been included in the 4.0 Release

Oracle database alerts have been added in Release 4.5.

(��

An alert indicates a potentially serious problem that should be quickly resolved. If notcontained, these problems could degenerate into a disaster.

+��

1. In the Command field, enter transaction RZ20 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Alert Monitor 4.0).

2. Click the node next to the server toexpand the server options.

2


R/3 Tasks


3. Double-click on the monitor (forexample, Basic monitor) under theserver Monitor sets (for example,the server monitor set is SAO).

4. Look for any alerts, which areindicated in red.

5. Click the node next to the <sid>(for example, SAO) to drill downfor additional details.

This example follows an alert down tothe paging rates.

6. Select the alert (for examplePage_Out).

7. Choose Display alerts.

5

6

3

7


R/3 Tasks

Release 4.0B4–16

To get detail for the alert:

8. Select the alert item.

9. Choose Choose detail (magnifyingglass icon).

10. Review the details.

11. Choose Back.

To “acknowledge” the alert:

12. Select the alert item(s).� Alert (red)� Warning (yellow)

13. Choose Complete alerts.

You still have to perform a task basedupon the alert.

“Acknowledging” the alert onlymeans you received the alertnotification, nothing else.

12

13

11

9


R/3 Tasks


14. When all alerts and warnings areacknowledged, the alert willchange to green (examplePage_In).

14


R/3 Tasks

Release 4.0B4–18

*�"��"�6��/��/��

To get more details on the alert, youcan start the analysis tool.

From the previous screen:

1. Select the alert (for example,Page_Out).

2. Choose Start Analysis tool.

This screen is only an example. Thefinal transaction you go to differsdepending on which branch of thealert tree you follow.

1

2


R/3 Tasks


7�� -� ��02�

(��

A failed update or an “update terminate” is an update to the database that failed. Thesefailed updates occur when a user entry or transaction is not entered or updated in thedatabase. The following analogy should help clarify this concept:

Analogy:

1. A secretary gives a file clerk a folder (similar to a save or execute).

2. The file clerk gives the secretary a receipt (similar to the R/3 document number).

3. On the way to the file cabinet, the clerk falls, and gets hurt.The folder never makes it to the cabinet (this is the failed update).

4. The end result is the folder is not in the cabinet—even though the secretary has thereceipt.

For performance reasons, the database update is done in asynchronous mode. In this mode,the user continues to work while the system takes over the update process and waits for thedatabase update to complete.

In synchronous mode, users would have to wait until the database has successfully updatedbefore they could continue to work.

(��

The users probably received a document number, so they assume that the entry is in thesystem; however, if a failed update occurred, it is not. If this were a customer order, unlessthe order is reentered, the customers would not get their order and no trace of it would befound in the system!

(��

You should check the system for failed updates several times a day.

During a dayshift, the checks can be distributed:� First thing in the morning� Late morning� Early afternoon� Late afternoon

If you have a global operation, your schedule should be adjusted to account for other timezones and someone in that time zone should participate in the monitoring.

The longer you wait after the update terminate has occurred, the more difficult it is for usersto remember what they did when the update terminate occurred. If you wait too long, theuser will not remember.


R/3 Tasks

Release 4.0B4–20

On Windows NT, from R/3 Release 3.0F and higher, system log entries are written to theNT event log. You might consider configuring an “event log monitor” to page you when anupdate terminate occurs. This reduces the need to constantly check the SM13 transaction. Italso reduces the exposure between when the times update terminate occurs, and when youfind out about it, and therefore when you can get to the user.

+��

1. In the Command field, enter transaction SM13 and choose Enter(or choose Tools→ Administration, then Monitor → Update).

2. Enter * in Client.

3. Enter * in User.

4. Under Status, select All.

5. Change the date to a year ago (forexample, 12/04/1997) in Fromdate.

6. Choose Enter.

7. Look for entries with an Err in theStatus column.

These entries are failed updates orupdate terminates. You may alsosee other entries listed without theErr status.

If you have no failed updates, youmay stop here. If you do havefailed updates, continue with thenext section, Managing UpdateTerminates.

7

4

5

6

32


R/3 Tasks


0��"��"�-� ��#��

If you have failed updates, proceed with the following steps:

1. Double-click on an entry with anErr status.

This screen shows in what module(Mod.name) and where in theprocess (Mod.ID) that the updateterminate occurred.

2. Double-click on the entry with anErr status.

3. Choose ABAP short dump.

If a short dump exists, it willappear.

2

3

1


R/3 Tasks

Release 4.0B4–22

4. This screen shows an ABAP dumpfor the update terminate.

Some problems that can occur with an update terminate include:� No short dump

In this case, the only clues you have are the:� User ID� Date� Time� Transaction

� Difficulty reading the short dumpDo not be discouraged because you cannot understand a short dump. The ability to reada short dump comes with experience and practice. Some of a short dump’s content isonly useful to the developer. You may recognize a pattern of characters as a partnumber, document number, vendor code, and so on.

� Short dump with little usable information� Update terminate occurring “downstream” from the actual transaction

The data in the short dump may be of little value in finding the root source of the updateterminate (for example, if the terminate occurred in the FI posting of an SD transaction,you do not know which SD transaction document caused the problem).

� Update terminate occuring in a batch jobThere is no indication of which batch job (by job name) caused the update terminate.Not being able to identify the batch job that was the source of an update terminate is aknown issue.


R/3 Tasks


5. The users need to be contacted. They should check for the missing entry and reprocessthe missing transaction.

Do not attempt to reapply the failed update! There are conditions under which this canlead to corruption of the database.

Always advise users to reenter the transaction.

-��"

Assuming you are not using SAPoffice, when a user receives a popup message, it usuallysignals a problem. The message reads:

You have express mail in your inbox.

The user should immediately stop and get assistance to determine what has happened. R/3uses “express mail” to notify the user of a failed update. It is during this short periodimmediately after the error has occurred that the user has the best chance of correcting theerror.

��#�,�"��042

(��

The system log is the R/3 System’s log of events, errors, problems, and other systemmessages.

(��

The log is important because unexpected or unknown warnings and errors couldindicate a serious problem.

$��

The ability to properly monitor the system log comes with experience. Over time, youwill become familiar with what log entries “normally” appear in your system log, andpick out the unusual ones that need investigation.


R/3 Tasks

Release 4.0B4–24

+��

1. In the Command field, enter transaction SM21 and choose Enter(or choose Tools → Administration, then Monitoring → System log).

2. Enter the beginning date and timethat you want to review from thelog in From date/time.

You can also enter an end dateand time if you want to view aspecific time period.

3. Choose Reread system log.

To make reviewing the log easier, under Problem classes select one of the following, one at atime:� Problems only� Problems and warnings� All messages

These options allow you to view the system log in the following priority layers:� Problems� Problems and warnings� All messages

2

3


R/3 Tasks


4. If you select Problems only, youwill see this screen.

4. If you select All messages, you willsee this screen.

5. Notice that the warning messageson this screen (indicated by theyellow W under the column C, andthe text entry Perform rollback) didnot appear in the previous screen.

6. You can get more information oncertain entries. In this example,double-click on the “short dump.”

What to look for:� Unusual entries

Before you can recognize the unusual entries, you will need to become familiar with which entries arein the log under normal conditions (for your installation for a specific system).

� Column C for the error statusErrors are the red Ks and warnings are the yellow Ws. These entries may have been examined whenyou did the Alert Monitor (RZ20).

56

5


R/3 Tasks

Release 4.0B4–26

To minimize the video-processing overhead, many NT servers are configured with a videocolor depth of 16 colors. On these servers, increase the video color depth to 256 colors tosee the alerts in color, or view the log from a computer that has the video set to a colordepth of 256 colors (or more).

7. Choose Analyze errors.

8. This screen is the short dump. Youcan access this screen usingtransaction ST22.

7


R/3 Tasks


*��"�� 8�!��0�9

(��

Background jobs are batch jobs scheduled to run at specific times during the day.

(��

If you are running critical jobs, you need to know if the job failed because there may beother processes, activities, or tasks that are dependent on these jobs.

)��

You should have a list of all the critical jobs scheduled to run. For each of these jobs, youshould have a list that shows:� When they are scheduled to run� The expected run time� Emergency contact (names and phone numbers) if a job fails or has problems� Restart or problem procedure for the job

+��

1. In the Command field, enter transaction SM37 and choose Enter(or choose System → Service, then Jobs → Job overview).

2. Enter * to get all jobs in Job name.

3. Enter either * (for all users) or theuser ID that the batch jobs rununder (to limit the display to thosescheduled under a specific user IDin User name).

4. Enter a start date in From.5. Enter an end date in To.6. Under Only jobs with status, select:

� Active� Finished� Terminated

7. Choose Enter.

6

2

4

7

3

5


R/3 Tasks

Release 4.0B4–28

8. Check for failed or cancelled jobs.Analyze why jobs failed or werecancelled and make the necessarycorrections.

9. Check critical jobs such as MRP,check payment jobs, and so on.You need to know the job namethat they run under to do this.

To check a job log:10. Select the job.11. Then choose Job log.

Check job performance and recordrun times. A deviation from the usualrun time on a job may indicate aproblem and should be investigated.

811

10


R/3 Tasks


+��8�!�0��352

(��

The graphical job monitor is useful when coordinating many background jobs because itallows you to see individual job statistics.

(��

The graphical job monitor is a more visually oriented format in which status is indicated bycolor:� Aborted job (red)� Active job (blue)

If a job ran past its expected end time, and other jobs are scheduled to start, the graphical jobmonitor lets you see the conflict.

+��

1. In the Command field, enter transaction RZ01 and choose Enter.

2. Choose Time unit → Hour to get amore usable time scale. 2


R/3 Tasks

Release 4.0B4–30

3. Choose Legend to get a popuplegend of the colors or patternsused.

3

3


R/3 Tasks


,��024

(��

A “lock” is a mechanism that prevents other users from changing the record on which youare working. An example that illustrates the importance of using this function follows.

Example: You are changing a customer mailing address. Someone else is changing thecustomer’s telephone number at the same time. You save your change first; then the otherperson saves their change. The other person’s change overwrites your change, and yourchange will be lost.

(��

There may be “old” locks still in place from transactions that did not release, or from whenthe user was cut off from the network. Unless cleared, these locks prevent access or changeto the record until the system is cycled. The easiest way to locate them is to look for locksfrom prior days.

Important: We presume that the profile parameter rdisp/gui_auto_logout has been set. Thisparameter defines an automatic logout of the user if there is no activity for the set number ofminutes.

Setting the auto_logout parameter is recommended for security. It is also an item that yourexternal auditors may test for.

The parameter auto_logout is a global setting that applies to all users on the instance.You cannot have different logout times for different groups of users, on the sameinstance.

The only way to have different logout times for different groups of users is to havespecific groups (for example, Finance) log in to specific instances (for example, theFinance application server) where the auto_logout parameter is set in the instance profileof that instance.


R/3 Tasks

Release 4.0B4–32

+��

1. In the Command field, enter transaction SM12 and choose Enter(or choose Tools → Administration, then Monitor → Lock entries).

2. Enter * in Client.

3. Clear the User name field.

4. Choose Enter.

5. Look for locks from previous daysin the Time column.

The presence of a lock from aprevious day could mean that theuser was “disconnected” from thenetwork and the R/3 System.

Deleting a lock is a dangerous task!

Do not delete a lock without checking to first see if it is in use. You risk corrupting thedatabase if you delete a lock that is in use.

To clear a lock, complete these steps on the system’s application and the database servers:

1. Check that the user is not logged on any of the servers with transaction SM04 (noapplication servers) or AL08 (with application servers).

If the user is not on the system, but transaction SM04 shows them on the system, deletetheir sessions as described in chapter 9, Deleting a User’s Session. This step, by itself, mayclear the lock.

3 2

4

5


R/3 Tasks


2. Check that there are no processes running under the user ID using transaction SM50 orSM51 (see Processes later in this chapter).

3. Check that there are no batch jobs running under the user ID using transaction SM37(see Background Jobs earlier in this chapter).

4. Check that there are no updates in process for that user ID using transaction SM13 (seeFailed Updates earlier in this chapter).

5. Once you know that there is no activity using the user’s ID, select the lock entry fordeletion.

Double-check the user ID of the entry that you selected to delete. If you delete the wronglock, you could corrupt the database.

6. Choose Lock entries → Delete.

Clear only one lock entry at a time.

Do not use the mass delete option. The mass delete option will delete all the locks, not justthe ones for the user you have selected.

/��-��05�� /,5:

(��

These transactions display all the users who are currently logged on to the system. Theyshow both the user’s ID and terminal name.

(��

In a smaller company, the administrator can recognize user IDs logged on to “unfamiliar”terminals. This may indicate that someone—other than the designated user—is using thatuser ID.

If a user is logged on to more than one terminal, this may indicate:� The user ID is being used by someone else.� The user ID is being used/shared by several people.

User IDs should not be shared for several reasons.

� One reason is that if a problem arises, you will not know who created the problem.This makes the problem difficult for you to fix and prevent from happening again.

� Prudent security practices do not allow for sharing of user IDs.


R/3 Tasks

Release 4.0B4–34

Your external auditors may also perform this test to test your security.

;��!��#�

Transaction SM04 may show a user as active, when in fact the user has actually logged off.Because the user session was not properly closed, the system “thinks” that the user is stilllogged on.

This condition can be caused by the following (among others):� A network failure, which cuts off the user� The user turning off their computer without logging off from the R/3 System.

��"��<'��#��05

+��

1. In the Command field, enter transaction SM04 and choose Enter(or choose Tools → Administration, then Monitor → System monitoring → User overview).

2. Select the user ID (for example,NAKAYAMAG) to view thesession the user has open.

3. Choose Sessions.

The Overview of Sessions screenshows what sessions the user hasopen.

4. Choose Enter.

2

4

3


R/3 Tasks


0��<'��#��/,5:

If you have several instances in your system, using AL08 is an easier method, as you cansee all users in all instances on the system at once.

1. In the Command field, enter transaction AL08 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → All work processes, and then Goto → Global usersoverview).

2. The Current Active Users screenshows all the instances in yoursystem.

3. For each instance is listed the userslogged into that instance/application server.

2

3

2


R/3 Tasks

Release 4.0B4–36

��;52

(��

The spool is the R/3 System’s output manager. Data sent to the printer is sent to the R/3spool and then sent to the operating system to print.

(��

There may be problems with the printer at the operating system level. These problems needto be resolved immediately for time-critical print jobs (for example, checks, invoices,shipping documents, and so on) or there may be an operational impact.

You should check for active spool jobs that have been running for over an hour. These long-running jobs could indicate a problem with the operating system spool or the printer.

+��

1. In the Command field, enter transaction SP01 and choose Enter(or choose System → Services → Output controller).

2. Clear User name.

3. Set the From date to a week ago.

4. Clear Client.

5. Choose Enter.

2

5

43


R/3 Tasks


6. Look for jobs with an error in theOutput Status column. In thisexample, no errors appear.

6


R/3 Tasks

Release 4.0B4–38

*��'��8�!�=�'�<>��*��;�� 0�1

(��

This transaction shows jobs that need to be processed or started, and jobs with errors thatneed to be resolved.

(��

This transaction is important because it alerts you to batch input jobs that:� Need to be processed

These are jobs that are waiting to be processed (for example, a posting from an interfacefile). If not processed, the data will not post to the system.

� Are in errorThese are jobs that have failed due to an error. The danger is that only a portion of thejob may have posted to the system. This increases the potential for data corruption of adifferent sort, as only part of the data is in the system.

+��

1. In the Command field, enter transaction SM35 and choose Enter(or choose System → Services → Batch input → Edit).

2. Enter a start date of at least a weekago (or even further back if peopleare not good about resolving thesejobs) in Creation date from.

3. Under Session status, select both:� To be processed� Incorrect

These selections display only thebatch jobs that need to beprocessed and those with errorsthat need to be resolved.

4. Choose Enter.

3

2

4


R/3 Tasks


5. Contact the responsible user tonotify them or determine whythese jobs are in:A. Sessions still to be processedB. Errors in sessions

5A

5B


R/3 Tasks

Release 4.0B4–40

(��;��015�� 012

(��

Process overview transactions allow users to view the status of work processes and monitorfor problems. Transaction SM51 is a central transaction from which you can select theinstance to monitor. SM51 starts transaction SM50 for each application server. TransactionSM50 is used for a system without application servers.

(��

Transaction SM51 is one place to look for jobs or programs that may be “hung,” whichwould be indicated by long run times. If batch jobs are not running, transaction SM50 mayprovide a hint of the problem, if all the batch work processes are in use.

7��#��/��

+��

1. In the Command field, enter transaction SM51 and choose Enter(or choose Tools → Administration, then Monitor → System monitoring → Servers).

2. Select the instance you want toview (for example,pa100767_SAO_01).

3. Choose Processes.

4. This is the Process Overviewtransaction (SM50) for thatinstance.

2

3


R/3 Tasks


7��#�(��/��

+��

In the Command field, enter transaction SM50 and choose Enter(or choose Tools → Administration, then Monitor → System monitoring → Process overview).

What to look for:

A. Dialog work processes (DIA) thathave long time values.

These values could indicate aproblem, or a long running step inbatch programs, which sometimesstart dialog work processes.

B. Work processes with a stoppedstatus. These can sometimes be aproblem because a process mayhave stalled or failed.

Some of the column definitions are:

Column Text Definitions

No Work process number

Ty Type of work process

PID OS PID (Process ID) number

Status Current status of the work process

Err Number of detected errors in the work process

CPU Cumulative CPU time that the current process is taking

Time Cumulative “wall” time that the current process is taking

Program Name of the ABAP program

Clie Client number

User User ID that is using the work process

Table Table that the action is being performed on

A

B

B A


R/3 Tasks

Release 4.0B4–42

/*/;��#��/��44

(��

An ABAP dump (also known as a short dump) is generated when a report or transactionterminates as the result of a serious error. The system records the error in the system log(transaction SM21) and writes a snapshot (dump) of the program termination to a specialtable.

This transaction can also be called from the system log (transaction SM21).

(��

You use an ABAP dump to analyze and determine why the error occurred, and takecorrective action.

+��

1. In the Command field, enter transaction ST22 and choose Enter(or choose Tools → Administration, then Monitor → Dump analysis).

There are two selection methods to display the list of dumps.� For simple selection; today or yesterday (go to step 2)� For free selection (go to step 5)

��#��

2. Under No. of short dumps, if yousee a value other than zero (0) inToday or Yesterday, dumps haveoccurred that need to beexamined.

3. Select Today.

4. Choose Display list to get a list ofshort dumps for the day.

Go to step 8.23

4


R/3 Tasks


7��

5. Choose Selection.

6. Enter your selection criteria in theABAP Dump Analysis screen.

7. Choose Execute.

8. Double-click on the dump youwant to analyze.

8

7

5


R/3 Tasks

Release 4.0B4–44

9. This screen shows the “shortdump.”

Despite being called a “short dump,” ABAP dumps may be more than 75 pages in length. Werecommend you save the dump to a file on your PC and print out only the portion you need.If the SAP hotline asks for a copy of the short dump. It is easier to e-mail or upload the file (seeOnline Service System Note 40024), rather than fax the entire dump.


R/3 Tasks


(�� /��&��#��5�

(��

Workload analysis is used to determine system performance.

)��

You should check statistics and record trends to get a “feel” for the system’s behavior andperformance. Understanding the system when it is running well helps you determine whatchanges may need to be made when it is not.

+��

1. In the Command field, enter transaction ST03 and choose Enter(or choose Tools → Administration, then Monitor → Performance, then Workload → Analysis).

2. Choose Data base server (forexample, nspalss1) or Thisapplication server.

2


R/3 Tasks

Release 4.0B4–46

3. Select a time period to analyze.

Options include:� Single stat. records� Today’s workload� Performance database� Last minute load� Local alert monitor

For this example, choose Lastminute load.

4. Enter how many minutes back toanalyze, or choose Other selectionto specify a date and time periodto analyze.

For this example, choose Otherselection.

5. Under Time interval to be analyzedis, enter the date and time range tobe analyzed.

6. Choose Enter.

3

4

5

6


R/3 Tasks


7. Examine Av. response time.

If this value is less than 1,000 ms (1second), the response time meetsthe target response time.

Judgment must be applied whenreviewing statistical values. If you juststarted the R/3 System, the bufferswill be empty and many of thestatistics will be unfavorable. Once thebuffers are loaded, values can beproperly evaluated.

Thus this example of an Av responsetime of over 4 seconds must beevaluated with other factors in mind.

If your default profile for decimal point,(point or comma) is not set, thedisplay may be misread. The R/3 userdefault for a decimal point is a comma.

8. Choose Transaction profile.

Analysis of transaction ST03 is covered in the BC315 “Workload Analysis and Tuning” class.We recommend that you take this class.

7

8


R/3 Tasks

Release 4.0B4–48

9. Click on any cell in the Responsetime avg column (for example, 77).

10. Choose Sort.

11. From this screen, you can reviewtransactions in order of averageresponse time.

See the following table for knownlong-running transactions.

10

9


R/3 Tasks


A few standard functional transactions will exceed the one-second guideline. They include:

Type Transaction Approx . time (ms)

Create Sales Order VA01 1,500

Change Sales Order VA02 1,500

Display Sales Order VA03 1,000

Create Billing Document VF01 1,500

Create Delivery VL01 2,000

Maintain Master HR data PA30 1,000


R/3 Tasks

Release 4.0B4–50

*�&&��54

(��

The buffer tune summary transaction displays the R/3 buffer performance statistics. It isused to tune buffer parameters of R/3 and, to a lesser degree, the R/3 database andoperating system.

(��

The buffer is important because significant buffer swapping reduces performance. Lookunder Swaps for red entries. Regularly check these entries to establish trends and get a feelof the buffer behavior.

+��

1. In the Command field, enter transaction ST02 and choose Enter(or choose Tools → Administration, then Monitor → Performance, and then Setup/Buffers →Buffers).

A B


R/3 Tasks


2. The two important things to review on the above screen are:A. Hit Ratio, for which the target value is 95 percent and higher

Soon after starting the system, this value is typically low, because certain buffers areempty. The hit ratio will increase as the system is used and the buffers are loaded. Itusually takes a day to load the buffers that are normally used.

B. Swaps, for which the target value is less than 1,000Swaps occur when the necessary data is not in the buffer. The system has to retrievethe data from the database. The swap value is reset to zero (0) when the system isrestarted.

Analysis of transaction ST02 is covered in the BC315 “Workload Analysis and Tuningclass.” We recommend that you take this class.


Database Tasks

Release 4.0B4–52

��!��

��"��!��

��

To see if the database is running correctly:

1. Review the database check job using transaction DB16 (scheduled using DB13—Checkdatabase).

2. Review the tablespace percent utilization every day.

3. Identify an “action point” where you will increase a tablespace by adding another datafile (for example, 85 percent).

4. Schedule a job (using DB13-Adapt next extents) to adapt the next extent size for yourOracle database.

This step significantly reduces the frequency of table reorganizations.

��!��/��

+��

Database alerts do not appear on the4.0 Alert Monitor (RZ20). The databasealerts and Alert Monitor are added inRelease 4.5A.

1. In the Command field, entertransaction AL02 and choose Enter(or choose Tools → Administration,then Monitor → Performance, andthen Alerts → Global → Databasesystem).

2. Clicking on a category with analert brings up another screenwith additional detail.

In this example, we selectedFreespace management.

2


Database Tasks


3. Drill down on TablespacePSAPBTABD to see the nextscreen.

This screen shows the forecastbased on history.

Apply your knowledge of thesystem and your business whenreviewing any forecasts.

The example shows two eventsthat cause the reduction infreespace. The forecast however isbased on a steady state average ofthe two events.

A. The vertical line indicates“today.”

B. Left of the vertical line is thepast.

C. Right of the vertical line is thefuture.

3

AB C


Database Tasks

Release 4.0B4–54

��!��>��,�"�

(��

The database error log is the record of database-level errors.

(��

Database error logs may indicate a database problem that is not reported in other locations.

+��

1. In the Command field, enter transaction ST04 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Performance Menu, then Database → Activity).

2. Choose Goto → Database log.

3. In the Database Messages window,select Only alerts.

This selection reduces the amountof text to look through in the firstpass.

During a second pass through thistransaction, select All messages.

4. Choose Display.

4

3

2


Database Tasks


5. Scroll down the log to check forerror messages.


Operating System Tasks

Release 4.0B4–56

��"��#��

��#�,�"�

(��

The system logs are where the operating system and some applications write event records.Depending on the operating system, there may be multiple logs.

(��

There may be indications of a developing problem (for example, a hard drive generatingerrors or a failing drive that needs to be replaced).

+��"��?��%��%��

+��

Use the operating system alert monitor for a quick visual review.

1. In the Command field, enter transaction AL16 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Performance Menu, and then Alerts → Local →Operating system).

2. Review this screen for potentialproblems.




+��"��"��#�,�"

To get the operating system log, perform the following steps:

1. In the Command field, enter transaction OS06 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Performance Menu, and then Alerts → Local →Activity).

2. Choose Detail analysis menu.

3. Choose Operating system log.

3

2



Release 4.0B4–58

These screens show the operatingsystem logs.

In this example, it is the NT eventlog.

In this example, it is the UNIX log.




$��>��,�"�

(��

NT has three event logs:� System� Security� Application

(��

There may be indications of a developing problem. If the security audit parameters havebeen properly set, you could detect unauthorized attempts to access files.

Configuring the security audit function is a tradeoff among the:� Need to log security events.� System resources used to track and maintain the log. The more detailed the log, the

more degraded the system performance.� Effort required to audit the log (dependent on the size of the log).

+��

The following steps show you how to open the NT event logs.

1. On the NT desktop, choose Start → Programs → Administrative Tools → Event Viewer.

2. The different logs can be selectedunder Log.

3. Look for unusual entries.

These entries require regularmonitoring to recognize anunfamiliar event, such as errors,failures, or security-related entrieswhich do not normally occur.

2


Other Tasks

Release 4.0B4–60

��

��-��!��;��

(��

The uninterruptible power supply (UPS) that you use should be monitored by a controlprogram. The control program, triggered by a power event, records the event and initiates ashutdown process of the R/3 environment (R/3, the database, related applications, and theoperating system), and finally the server. In addition, most UPSs have a self-test andcapacity calibration function. The results of these tests are logged. The logging depends onthe program.

(��

You need to review the power “events” that triggered the UPS control program.

While the UPS protects the server, the control program should be recording power“events” such as power dips, brown outs, power failures, and so on. This recording couldhelp you or the facilities person solve electrical problems in the facility. For example, ifyou regularly see a power dip or outage at a particular time, this may be the indication ofa problem elsewhere in the building.

You need to verify that:� The UPS is functioning� The self-tests completed successfully

The batteries in the UPS must be periodically replaced. If the batteries are low, thecapacity test will indicate that the batteries do not have sufficient capacity to shutdownthe system before failing.

)��

� Review the log for the UPS control program.


��

��

Checklists ................................................................................................................5–2

R/3 Tasks .................................................................................................................5–4Monitoring and Plotting Database Growth (Transaction DB02)................................5–4Checking for Tables Nearing their Maximum Extents...............................................5–7Check Spool (Transaction SP01)..............................................................................5–9Transports into the Production System...................................................................5–11

Database Tasks.....................................................................................................5–11Checking the Database...........................................................................................5–11

Operating System Tasks ......................................................................................5–12Checking File System Space Usage.......................................................................5–12Changing the Alert Threshold .................................................................................5–15

Other Tasks ...........................................................................................................5–16Reviewing Hardware or a System Monitor Paging System ....................................5–16Cleaning the Tape Drive .........................................................................................5–18

�

Chapter 5: Scheduled Weekly Tasks

Checklists

Release 4.0B5–2

��

System: __________

Date: ____/____/____

Admin: _____________________

��

Task Transaction Procedure Checkoff/initial

Check database for free space. DB02 – DBPerformance:Tables

Record free space.

Monitor database growth. DB02 – DBPerformance:Tables

Check spool for problems andthat spool is properly cleared.

SP01 - Spool

Transport into PRD STMS, or TP All properly approved transportsimported into PRD

��

Task Where Procedure Checkoff/initial

DBCC Check output from DBCC job forerrors (SQL Server).

Run MS-SQL server updatestatistics.

Check for successful completion ofupdate stats job.

��


Check file system for adequatespace.

RZ20 – CCMSAlert

Files system

Review space usage and thatsufficient free space exists in the filesystems.


Checklists


��


Check system monitoringsystems for update.

System monitor Review for any events that shouldbe added or deleted.

Check system monitor alertmechanisms.

System monitor Test e-mail.

Test paging.

Clean tape drive. Tape drive Clean using cleaning cartridge.

��



R/3 Tasks

Release 4.0B5–4

��

!�� "��#��$��%��&'()

��

This task involves monitoring the growth of the database and projecting future growth todetermine when to plan to expand the database.

��

You need to plan when to expand database capacity with the least disruption to companyoperations. If this expansion requires additional disk storage, you will need to purchase andinstall the drives. This requires lead-time that should be incorporated into the planningtimeline. The drives should be installed during a “noncritical” period.

Running out of database capacity during a critical period can result in an emergency!Murphy says:

“The drives you need will not available from any of your suppliers when you criticallyneed them.”

��

To effectively monitor database growth:� Record and plot the database and freespace sizes� Check for table and indices that are close to their maximum extents (maxextents)� Check for “fast growth” tables (for example, VBFS)

Alter the percent-used factor for fast growers that have grown too large.

��

If your system experiences rapid changes, this task should be performed daily, rather thanweekly.


R/3 Tasks


#��

1. In the Command field, enter transaction DB02 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Performance Menu, and then Database →Table/Indexes).

2. Choose Space statistics.

3. Record and plot the free spacevalues.

4. Choose Graphics.

3

4

2


R/3 Tasks

Release 4.0B5–6

This screen shows a graph of freespace in the database, and aprojection into the future.

A. Now

B. Past history

C. Future forecast

Use care when you interpret thegraph. Forecasts are based onhistorical usage that may or may notbe valid in the future.

5. Choose Back.

6. Choose Tablespaces.

This screen shows remaining freespace by individual tablespace.

7. To get the history of an individualtablespace, double-click on it.

For Oracle, monitoring tablespaceusage is a critical task.

5

6

AB C

7


R/3 Tasks


On the Tablespace history screen,notice:

A. Free (Kbyte), the remaining freespace

B. Used (Kbyte), the amount of spacein use

8. Choose Months, Weeks, or Days foran alternate view of this data.

9. Record and plot the tablespaceusage and freespace to estimatewhen you will need to extend thetablespaces, or get additional drivespace for the tablespaces.

��*�� !�+��,+��

��

Tables have a maximum number of times that they can grow, before a reorganization isneeded, this is the MaxExtents value.

��

The MaxExtents value for Oracle 8.x is “theoretically” unlimited. But in practice, the numberof extents should not be allowed to get too large.

An excessive number of extents will create a performance issue, because a table would bespread over many “fragments.” If the fragments are physically spread over the disk,retreiving data would require more time than if the data was physically close together.

The table reorganization is essentially “defragmenting” the table.

8

BA


R/3 Tasks

Release 4.0B5–8

#��

1. In the Command field, enter transaction SE38 and choose Enter(or choose Tools → ABAP Workbench, then Development → ABAP Editor)(An alternate transaction is SA38, System → Services → Reporting).

2. Choose Enter.

3. Enter RSORATC5 in Program.

4. Choose Execute.

5. Enter 100 in More extents than.This reduces the amount of tableto review.

6. Choose Execute.

7. Read the value in the Extentscolumn.

8. If it is within 100 extents of theMaxExtents column, areorganization of the object/tablespace is needed.

3

4

5

2

7 8

6


R/3 Tasks


��%��"'-)

��

The SAP Spool is the output manager for R/3. From the SAP spool, the print job goes to theoperating system’s print spooler or manager.

You need to check that old spool jobs are being properly cleared by the daily batch job.

��

Old spools will take up database space or file system space, depending on how the spoolsystem has been configured. Whether it is database or file system space, potentiallyavailable “space” is being used by these spools.

Look for any errors that may indicate problems in the printing process.

#��

1. In the Command field, enter transaction SP01 and choose Enter(or choose System → Services → Output controller).

2. Clear the following fields:� User name

� From (date)� to (date)� Client

2


R/3 Tasks

Release 4.0B5–10

3. Scroll down the screen to find theoldest date. This date should be inthe time frame defined for theRSPO0041 job that deletes oldspools (see Online Service Systemnote 16083).If it is not, the job may not beproperly deleting the old jobs andneeds to be analyzed.

4. To add the user name on thescreen, choose User name.

Two reasons for failure of the RSPO0041 job are:� The user ID under which the job is run does not have the proper security authorization

to execute the program.� The job is routed to an invalid printer.

5. The Client User option helps yousee which user from which clientis related to the spool jobs. Thisinformation is helpful if there arespool errors.

4

5


Database Tasks


��"��

��

A transport is the mechanism that R/3 uses to move changes from system to system orclient to client.

��

Complete the transport in the production system during a “quiet” period (for example,Sunday afternoon or evening) when users are not logged on the system.

Ideally, a full system backup should have been completed before transports are imported.

��

During a transport, objects may be overwritten. If an object is being used in the targetsystem when a transport is performed, the transport may cause inconsistent results orterminate the transaction.

In the worst case scenario, a transport may “break” the production system and you willneed to restore the system.

.�$

To learn how to do transports, see the section, Transporting Objects, in chapter 10,Nonscheduled System Administration Tasks. Transports are a “nonscheduled” task becausethey are only done when necessary (that is, when you have a transport that needs to bemoved). You may also have the occasional “emergency” transport that must be moved at atime other than at your normal weekly transport time.

��

��

��

There are two database checks; DB system check and DB verfication.� DB system check is for a “health check” of the database.� DB verification checks the internal Oracle block structure for block corruptions.

��

If there is a problem with the database, a restore of the database will have the sameproblem. The DB verification give assurance that the backup is of a “good” database.

.�$

See chapter 14, Checking the Database.


Release 4.0B5–12

��

��/��0��

��

The file system should have sufficient “free space” to permit normal operations to run. Overtime, various operations will write files that will use up file space. These files need to beperiodically reviewed and moved, or backed up and deleted.

A few of the items that consume file space and must be considered when monitoring filespace usage include:� Transports� Hot Packages� Extract files from the R/3 System� Program logs� Backup logs� Error logs� Inbound interface files� Third-party programs that store their data outside the R/3 database

In addition to these items, check to see that “house cleaning” programs are runningproperly (See Online Service System note 16083).

��

If your file system fills up, the R/3 System may stop because it cannot write a file. Thisstoppage will, in turn, stop any business operations that use the system.

In the Oracle database, this is a critical situation for the Oracle redo archive logs. If the filesystem fills and Oracle cannot write anymore redo archive logs, Oracle will stop, causingR/3 to stop.

To plan for such a situation:� Predict and plan for disk space needs.� Determine if storage space expansion is needed.

If storage space expansion is needed, purchase and installation plans need to be made.The expansion should be planned to minimize operational disruption.

� Determine if “house cleaning” is needed.If archiving is required for data files, archive to quality storage media such as opticaldisk, CD, or similar long-term media.




#��

You can use the R/3 Alert Monitor, or you can go to the operating system to check file system space usage.In this step-by-step procedure, we use the R/3 Alert Monitor, because we can set alert points.

1. In the Command field, enter transaction RZ20 and choose Enter(or choose Tools → CCMS, then Control/Monitoring → Alert Monitor 4.0).

2. To expand the system to bechecked, click the node (forexample, SAO).

3. Double-click on the monitor, forexample Basic monitor.

3

2



Release 4.0B5–14

4. Drill down as follows:SAP domain → <Instance> (SAO) →<server_instance_system number>(pa100767_SAO_01) →OperatingSystem → Filesystems.

The drives are color coded toindicate alert status:� Green (OK)� Yellow (Warning)� Red (Critical)

7. Expand the drive (for example, E:)to its statistics (Freespace andPercentage_Used):

These are statistics at the drive(not directory) level.

View these statistics while keepingyour particular system in mind.

For example, on your system,drive E may contain the databasewhich takes up all the space onthat drive. Keeping this in mind,you can expect and ignore thewarning message. Or change thealert threshold for that specificdrive. See Changing the AlertThreshold on page 5–15.

5




��1��

To customize the points when thealert indicator changes from green toyellow, yellow to red, and back fromred to yellow, and yellow to green:

1. Click the node of the specific drivefor which you want to change thethreshold.

2. Select an alert.

3. Choose Customizing.

4. Choose Change.

5. Choose Thrshld values.

6. Enter new values for when thealerts will change (for example,1000).

These threshold values are specificto your system, and even tospecific drives in your system.

7. Choose Save.

1

3

6

74

5

2


Other Tasks

Release 4.0B5–16

��

��2��$��.�� $��!��"��

��

A hardware or system monitor paging system generates alert messages (including e-mail)and pages based on your predefined parameters. Depending on the software, the followingcan be monitored:� Hardware items, such as servers, routers, and printers� Logs, such as operating system, applications, and database

By monitoring the NT event logs, you can monitor events from the SAP system log. Thisway, critical events such as an Update Terminate can be detected and acted on as soon asthey happen.

The following screen is courtesy of TNT Software.


Other Tasks


The previous screenshot shows what one of these monitors looks like. It has three functionalwindows:� Notification Rules

This is the mechanism to pass or filter events, and what action will be taken on theevents that are passed.

� EventsThese are the events that have been passed to the monitor program. (They got throughthe filters in the “notification rules”.)

� Monitored deviceThese are the monitored servers and IP devices.

This example, however, has not been configured to pick up and report on SAP events.

Initially, there will be a lot of tuning as you adjust the parameters of the system. Over time,parameter adjustments will become less and less.

��

You may need to change alert parameters to filter noncritical events and to generate alertsfor critical events. Some of these tasks are as follows:� Account for new events

� Critical, you need to generate a page� Important, you need to generate a message (for example, e-mail)

� Determine if an event that used to be filtered now needs to generate an alert� Filter out events (both old and new) that should not generate alert messages

Filtering is necessary to manage the messages that are reviewed. If too many irrelevantmessages get through the filter, it becomes difficult to review the alert message log.

� Adjust for personnel changes

Occasionally, there may be other events that require action (for example, shift or dutychanges for organizations with several people “on call”).

You need to test that all alert mechanisms are functional

The paging/messaging function needs to be tested regularly. If it is unable to send a page,you will not receive the page when a critical alert occurs.

Not sending a page can be caused by:� Someone changing something in the e-mail or phone system that prevents alert

messages from being sent� A phone patch cable that has become disconnected from the modem


Other Tasks

Release 4.0B5–18

.�$

To review the paging system:� Review the various monitored logs (such as the NT event logs) to look for events that

should generate an alert message (e-mail or page).The monitor program needs to be configured to pick these up and properly processthem.

� Review the log of the alert monitor for alert events that should be “filtered” out.The monitor program needs to be configured to filter or ignore such events.

� Test all alert mechanisms, such as pager, e-mail, and so on to make sure that they arefunctional.If you receive regular daily e-mail messages, then the e-mail testing is being done foryou.

��2�

Clean the tape drive as part of a preventive maintenance program to minimize a backupfailure due to a dirty head.

Murphy says: “The backup that failed is the backup you will need.”

To keep your tape drive clean:� Follow the tape drive manufacturer’s instructions for your tape drive.

Some drives specify a specific interval of use for cleaning, typically based on hours ofuse. Adjust your cleaning frequency to account for your usage. Remember, that these arerecommendationsnot rules. If you consistently have recording errors or “head dirty”messages, then decrease the time between cleanings. If you have to clean your tapedrives more or less frequently, this task should be moved to the appropriate interval.Some drives (for example, DLT) do not require regular cleaning. They only needcleaning when the “clean head” indicator light is activated.

� Use the manufacturer’s approved cleaning cartridge for the tape drive.� Use the cleaning cartridge according to the manufacturer’s instructions.� Between uses, store the cleaning cartridge according to the manufacturer’s instructions.

Keep your server room clean.

A dusty or dirty environment will not only make you clean your tape drive more often, butwill also coat the inside of the server with dust and cause a cooling problem.


��

��

Checklists ................................................................................................................6–2

R/3 Tasks .................................................................................................................6–5Memory Defragmentation .........................................................................................6–5

Database Tasks.......................................................................................................6–6Plotting Database Growth .........................................................................................6–6

Operating System Tasks ........................................................................................6–7Performing a Full Server Backup..............................................................................6–7Reviewing File System Usage ..................................................................................6–7

Other Tasks .............................................................................................................6–8Checking Consumable Supplies ...............................................................................6–8

�

Chapter 6: Scheduled Monthly Tasks

Checklists

Release 4.0B6–2

��

System: __________

Date: ____/____/____

Admin: _____________________

��

Task Transaction Procedure Check off/initial

Defragment the memory Cycle the R/3 System

��


Plot database growth DB02—DatabasePerformance:Tables

Record usage and plot

��


Backup file server Perform a full server backup

Record file system usage. Plotusage.

Is additional storage spaceneeded?

Is “house cleaning” needed?

Review file system usage


Checklists


��


Spare tape cleaning cartridgeavailable for all tape drives.� DAT� DLT

Spare tape cartridges availablefor all drive types.� DAT� DLT

Spare data cartridges availablefor removable media devices:� Zip®

� MO (Magneto-Optical)� CD (Recordable)

Preprinted forms:� Shipping documents� Invoices� Checks

Special supplies, such asmagnetic toner cartridge.

Normal supplies:� Laser printer toner� Paper (for printers)� Batteries� Diskette� Pens, and so on

Check consumable supplies


Checklists

Release 4.0B6–4

��



R/3 Tasks


��

��!��

"��

A computer’s 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 usageof the computer’s memory becomes fragmented with unused spaces scattered throughout.

"��

At a certain point you may have sufficient “free memory” (that is, the total of all the unusedspaces), but not a contiguous (single) piece of memory large enough to allow certainprograms to execute. At that point, those types of programs attempting to run that needcontiguous memory will fail because they cannot be loaded into memory.

#�$

To defragment the system’s 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 firstperson who accesses the buffered object will have a long response because the system mustget 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 intothe buffer. This usually takes up to a day to accomplish.


Database Tasks

Release 4.0B6–6

��

%��&��$��

"��

Plotting database growth is a basic requirement to planning for database and hardwareexpansion.

"��

Hardware expansion typically requires that the server be brought down before installationof additional hardware. The time required to complete this shutdown, and possibleproblems that may occur, need to be considered when planning the expansion. Because ofthe system shutdown, possible problems, and significant lead times, the expansion needs tobe coordinated with the users.

Plan ahead for critical periods such as year-end, when you do not want the system to bechanged. You need to do your change before or after the critical period. If the decision is tomake the change after this time, consider whether you have sufficient capacity to getthrough the critical period.

#�$

To effectively plan for this expansion, record the database and tablespace sizes and plottheir growth curve over time. This information should give you a rough estimate as to whenyou will need to expand the storage space. Remember, if new SAP functionality isimplemented, the slope of the growth curve will change. For additional information, seechapter 5, the section Monitor and Plot Database Growth.




��

%��!��'��(��)��

"��

An offline backup of the entire server is done at the operating system level. This processrequires that the R/3 System and the database be down so that no files are open.

"��

Performing an offline backup is necessary for files that cannot be backed up if the R/3System 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 adefined point from where everything is backed up and from where you can begin a restore.

"��

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.

#�$

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.

��(��$��'��*��

The monthly tasks for reviewing file system usage are the same as the weekly tasks, but arecompleted monthly. For additional information, see chapter 5, the section Review File SystemUsage.


Other Tasks

Release 4.0B6–8

��

��

"��

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 ifthey run out, could affect or stop the business operations. Examples are preprinted formswith your company’s name or other special printing, and magnetic toner cartridges.

The amount of spare supplies purchased and on-hand should be enough to handle normaland slightly abnormal usage and to allow for time to purchase replacements.

"��

Running out of supplies will create an inconvenience, or even an operational problem.

��

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 beable to generate checks out of the system. At this point, either you cannot print checks topay your vendors, or you have to manually type the checks (if you have blank manual checkstock 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 torestock 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 andvendors and stores will be closed.”


Other Tasks


#�$

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 bediscarded and replaced with new tapes. (This usage limit can be entered into theSAPDBA 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 anyprice.

� Track usage rates and adjust stocking levels and purchasing plans as needed.

��

Certain supplies may have long lead times for purchase, manufacture, or shipping.

Do not make your lack of planning the purchasing agent’s emergency. If you do this toooften, you will soon “use up your favors.” Then when you really need help, thepurchasing agent may not be as willing to help you.


Other Tasks

Release 4.0B6–10


��

��

Checklists ................................................................................................................7–2

R/3 Tasks .................................................................................................................7–4Backups ....................................................................................................................7–4Security .....................................................................................................................7–4

Database Tasks.......................................................................................................7–8Performing a Database Test Restore .......................................................................7–8

Operating System Tasks ........................................................................................7–9Cleaning Out Old Transport Files .............................................................................7–9

Other Tasks ...........................................................................................................7–10Checking Maintenance Contracts ...........................................................................7–10Check your UPS Shutdown Process ......................................................................7–11

�

Chapter 7: Scheduled Quarterly Tasks

Checklists

Release4.0B7–2

��

System: __________

Date: ____/____/____

Admin: _____________________

��

Task Transaction Procedure Check off/initial

Archive quarterly backup Send quarter-end backup tapes to long-termoffsite storage.

SU01—UserMaintenance

Review user ID for terminated users thatshould be locked or deleted.

SM31—TableMaintenance

Review list of “prohibited” passwords (TableUSR40).

Security review

RZ10—EditSystemProfile

Review system profile parameters forpassword standards.

Review scheduled jobs SM37—BackgroundJobs

Review all scheduled jobs to determine if theyare still appropriate.

��


Archive quarterly backup Send quarter-end backup tape to long-termoffsite storage.

Review all scheduled jobs Review all scheduled jobs to determine if theyare still appropriate.

Restore database to a test server.Test database recoveryprocess Test the restored database.


Checklists


��


Archive quarterly backup Send quarter-end backup tape tolong-term offsite storage.

Archive old transport files Transport directories;log, data, cofiles

Archive the old transport files.

Cleanup SAPDBA logs SAPDBA – cleanup Maintain init<SID>.dba

��

Task Where Procedure Check-off/initial

Check for expiration date.Check maintenancecontacts Check for usage changes.

��



R/3 Tasks

Release4.0B7–4

��

!�� Make certain you get a usable backup at the quarter’s end.� Send quarter-end backup tapes offsite for an extended period.

��

��"��#��$�� %��$��&��

All users who have left the company should have their R/3 access terminated immediately.By locking or deleting these user IDs, you limit access to only those users who should haveaccess to R/3. Periodic review assures the task of locking or deleting has been completed.

Proper audit control requires that a user who no longer has a valid business need to accessR/3 should not be allowed to keep that access.

Deleting or locking these user IDs also prevents anyone who had been using the terminateduser ID from accessing the system under that ID.

One of the audit procedures that your external auditors will use is to test whether a personwho does not need to access R/3 has a live user ID.

��"��#��'��$�� %��$��&��

(��

1. In the Command field, enter transaction SU01 and choose Enter(or choose Tools → Administration, then User maintenance → Users).

2. Clear the User field.

3. Choose possible entries.

3


R/3 Tasks


4. Clear all fields.5. Choose List Enter.

6. Review the active users.

Verify that the users are indeedvalid users.

7. This screen allows you to view theGroup that the user is in. Ifmaintained properly, groups arean aid in determining active users.

In a large company, you should do arandom audit on at least 20 users, tohave a valid sample. The minimumnumber should be determined byyour auditors.

For additional information on how to “lock” a user, see chapter 9, Nonscheduled Tasks User AdministrationTasks.

5

7

4

6


R/3 Tasks

Release4.0B7–6

)��)��*��#��

'��

There are certain passwords (for example, 123, QWERTY, abc, sex, sap, <your company name>)that are well known or easy to guess by someone trying to break into the R/3 System. Youcan prevent these passwords from being used by loading them into a table (USR40) that thesystem checks when the user attempts to save a new password.

'��

A password is the key to enter the system, similar to the key to enter your home. If userschoose easy-to-guess or well-known passwords, security becomes an issue and your systemis potentially at risk.

Your external auditors may check to see if you have a mechanism to secure against usersusing “easy-to-guess” passwords.

+�#

See chapter 9, the section Maintaining a Table of Prohibited Passwords; then in chapter 10, thesection Table Maintenance Using Transaction SM31.


R/3 Tasks


��"��#��*��#�� %��,-.

'��

There are security parameters for the user’s password (for example, the minimum passwordlength, the time interval that the user must change their password, and so on).

The following is a list of the most important password parameters:� Minimum password length: login/min_password_lng

A longer password is more difficult to break or guess.� The standard for many companies is five (5) characters.

� Password expiration time: login/password_expiration_timeThis is the length of time before the user must change their password.� The length of time most auditors recommend is thirty (30) days.� The maximum that should be used is ninety (90) days.

� Password lockout: login/fails_to_user_lockThis parameter locks out users after attempting to log in with an invalid password for adefined number of times.� The standard is to lock a user after three (3) failed attempts.

'��

Properly assigned parameters make it more difficult to break into the system.

Your external auditors may check to see if you have set the security parameters.

+�#

To set up password parameters, maintain system profiles with transaction RZ10. Seechapter 11, the section Changing System Profile Parameters.


Database Tasks

Release4.0B7–8

��

*��/��

'��

A database test restore is a test in which the production database is restored onto anotherserver to test that the recovery process functions as intended.

'��

Periodically it is prudent to test the restore process to:� Verify that backup tapes are being created properly.

If you cannot recover the full database using your regular backup tapes, you want toknow about it before you really need to restore the database.

� Find out if changes have been made which need to be accounted for in the disasterrecovery process.

Murphy says: “When you need to restore, you will find that a backup tape is not usable.”

+�#

See comments in chapter 3, Backup and Recovery. Because the restore process is a critical task,you need to work with your consultants on this process.




��

�� 0��

'��

Transport files are used to transport or move SAP objects and customizing changes betweenclients and systems.

'��

If left unchecked, transport files could gradually fill up the file system.

Operations may be affected because:� Outbound R/3 System files may not be able to be created.� Transport export may fail.� Inbound files may not be createable.

In an extreme situation, if you run out of tablespace R/3 may stop, or you may have otherfailures because R/3 or another application cannot write to the necessary files.

'��

The transport directory check is important after a major implementation in which manytransports have been created and take up large amounts of space. Immediately before orafter performing a database copy, most (if not all) files dated prior to the copy will becomeirrelevant to the system.

+�#

To complete a transport directory check:

1. Check the following directories under /usr/sap/trans:� Data� Cofiles� Log

2. Sort the directory by date to determine the age of files.

3. Archive obsolete files.These are files created before a database refresh or those that have been appliedsuccessfully to all target systems.

4. As an option, archive old transports to a backup media such as tape, optical, or CD.


Other Tasks

Release4.0B7–10

Check both of the following:

� Hot package directory /usr/sap/trans/EPS/in

� Transport data directory /usr/sap/trans/data

Hot package files can be reloaded if needed and can be very large. For example, hotpackage 10 for Release 4.0B is over 200MB.

��

��1��

'��

Many of the servers and related equipment are under maintenance or service contracts withthe manufacturer or distributor.� The production system and critical equipment should be under a “premium”

24 hour x 7 day (x 2 hour response) support agreement.� Less critical equipment can be under a next business day support agreement.

'��

If you need support or service on a piece of equipment and the service contract has expired,the confusion and time to reestablish the service contract could be critical.

'��

Depending on the use of the equipment, the support level should be selected accordingly. Ifa piece of equipment becomes critical to the company’s operation, its support level shouldbe upgraded to reflect the critical nature of that equipment.

Conversely, equipment could become “noncritical” or be replaced. In this situation, theservice contracts should be downgraded or dropped as appropriate.

+�#

� Keep a list of service contracts.Include what they are for and the expiration date in the list.

� Review equipment usage to determine if the support level for equipment should beupgraded, downgraded, or dropped.

� Review the list for expiration dates within a quarter.This time period depends on the time it takes to go through the purchase requisition andapproval process in your company.

� Renew service contracts.


Other Tasks


��%*�� #��*��

'��

Verify that your uninterruptible power supply (UPS) shutdown process works. A shutdownprocess is an automated script for the UPS to shut down R/3, the database, otherapplications, the operating system, and then the UPS itself.

'��

The purpose is to verify that the entire shutdown process works as planned anddocumented.

When there is a power failure, the R/3 environment should be shut down in an orderlymanner. There should be sufficient reserve in the UPS to reach the end of the shutdownprocess.

Something might have changed since your last test to cause the shutdown process to fail.If it fails, you need to find out why and fix the problem.

The stopsap command does not work within all UPS control programs.

You need to verify that your UPS control program will properly stop R/3 and the databasebefore shutting down the server.

Like a car battery, UPS batteries “wear out” over time and must be replaced. If the batteryis “worn out,” the UPS will not have sufficient power to complete the shutdown process.


Other Tasks

Release4.0B7–12


��

��

Checklists ................................................................................................................8–2

R/3 Tasks .................................................................................................................8–4Backups ....................................................................................................................8–4Security & Profile Audit .............................................................................................8–4Checking that the Production System Is Not Modifiable...........................................8–8Verifying that Dangerous Transactions Are Locked .................................................8–9

Database Tasks.....................................................................................................8–15Backups ..................................................................................................................8–15

Operating System Tasks ......................................................................................8–15Backups ..................................................................................................................8–15

Other Tasks ...........................................................................................................8–15Disaster Recovery Test...........................................................................................8–15

�

Chapter 8: Scheduled Annual Tasks

Checklists

Release 4.0B8–2

��

System: __________

Date: ____/____/____

Admin: _____________________

��


Archive year-end backup Send year-end backup tapes to long-term offsite storage.

Audit user security Review users security authorizationforms against assigned profiles.

Can also be done with reportRSUSR100

SU02 – SecurityProfile Maintenance

Spot check profiles for recent changes.


Audit profiles andauthorizations

SU03– SecurityAuthorizationMaintenance

Spot check authorizations for recentchanges.


Review segregation ofduties

Audit user IDs SAP* andDDIC

Run SAP user auditreports

SA38 (or SE38) –Execute ABAPProgram

Run user audit reports:� RSUSR003� RSUSR005� RSUSR006� RSUSR007� RSUSR008� RSUSR009� RSUSR100� RSUSR101� RSUSR102


Checklists



Check that the system isset to Not modifiable.

SE03 – WorkbenchOrganizer Tools

Verify that system is set to Notmodifiable.

SCC4– “Clients”:Overview

Check changeable status for applicableclient

Check locked transactions SM01 – Transactioncodes: Lock/Unlock

Check against your list of lockedtransactions.

��


Archive year-end backup Send year-end backup tapes to long-term offsite storage

��


Archive year-end backup Send year-end backup tapes to long-term offsite storage

��


Restore entire system to disasterrecovery test system

Perform disaster recoverytest

Test business resumption

��



R/3 Tasks

Release 4.0B8–4

��

!��

For a year-end backup:� Make certain to get a usable backup at year-end.� Send the backup tapes offsite for an extended period.

The length of the “extended” period should be determined by your legal and financedepartments, external auditors, and others as appropriate in the company.

Be aware that you may have two different year-end backup dates:� End of the calendar or fiscal year� After the financial books are closed for the year

��"�#��$��

��%��&��#��$��$�� #��

'��

A “permission creep” is an incremental increase in permission given to a user over time. Ifleft unchecked, increased permissions may grant a user more authority in the system thanrequired or intended.

'��

Users may have undesirable authorization(s) or combinations.

Your external auditors may have an audit step to check for permission creepage.

(�&

You can conduct a spot audit of:� Individuals

� Review the security forms for a user, and compare these forms to the profilesassigned to that user, and investigate inconsistencies.

� Review the profiles assigned to the individual for reasonableness.Reasonableness is: “Does it make sense?”

� Review the individual profiles assigned for content and check to see if the profile hasbeen recently changed.


R/3 Tasks


� Profiles (transaction SU02) and authorizations (transaction SU03)Check to see if the change date is recent.

You can also execute the following audit reports:� RSUSR100 (user changes)� RSUSR101 (profile changes)� RSUSR102 (authorization changes)

For additional information on these reports, see the User Security Audit section on page 8–7.

��$��

'��

There are standard audit guidelines which cover job/task combinations that are considered“risky” or reduce internal controls. Some of these are:� Accounts Payable and Check Generation� Accounts Receivable and Cash Receipts� ABAP development and transport control

Your external auditors should be able to help you define these risky combinations.

For your external auditors, testing for segregation of duties is a standard audit procedure.

(�&

The review of segregation of duties should be completed with the various user owners (keyusers of each functional area).

Out of necessity, smaller companies must assign multiple functions to a single person. Beaware of the potential security risks in this situation. If you must combine functions,combine them in a way that you minimize risks.


R/3 Tasks

Release 4.0B8–6

��#)��*�

'��

These are system user IDs that have restricted uses for specific purposes.

'��

There are certain functions that can only be performed by SAP* or DDIC.

If an R/3 user requires similar functionality, they should have a copy of the SAP* profile.These users should be grouped as “super users,” with the appropriate security approvals.

The security profile for SAP* is SAP_ALL. This profile is extremely because it grants the usercomplete access to the system. See further explanation in chapter 9, the section RecommendedPolices and Procedures: System Administration.

A user with user administration rights cannot change the password to gain access to a userID and then change the password back to the original password. Passwords are not visibleto the administrators, thus they cannot restore the original password if they do not know it.At a subsequent logon, the owner of the user ID will know that the password has beenaltered because they cannot log in with their old password.

(�&

1. Log on using SAP* and DDIC to determine if someone has changed the password.

2. Periodically change the password for these users:� In all systems� In all clients in those systems.

This step prevents a person who knew the password from gaining access.

3. Update the secured password list.


R/3 Tasks


+��

There are several predefined SAP security reports, including:� RSUSR003 Check for default password on user IDs SAP* and DDIC

� RSUSR005 Lists users with critical authorizations� RSUSR006 Lists users who are locked due to incorrect logon

This report should be scheduled to run daily, just before midnight.� RSUSR007 Lists users with incomplete address data� RSUSR008 Lists users with critical combinations of authorizations or transactions� RSUSR009 Lists users with critical authorizations� RSUSR100 Lists change documents for users and shows changes made to a user’s

security� RSUSR101 Lists change documents for profiles and shows changes made to security

profiles� RSUSR102 Lists change documents for authorizations and shows changes made to

security authorizations

Some of these reports have parameter tables that need to be properly maintained to makebest use of them. Review and analyze these reports based on your knowledge of thecompany. However, be aware that security issues may exist. If you have a small company,these issues cannot be avoided because “one person often must wear many different hats.”

Your external auditors may require some of these reports to be executed as part of theannual financial audit.

(�&

1. Enter transaction SA38 or SE38.

2. Enter the report name in Program.

3. Choose Execute.

4. Choose OK.

��$��$��

� RSUSR008 (lists critical combinations of authorizations or transactions)� These combinations are maintained on table SUKRI.� Dangerous combinations include the following transactions:

- RZ02 (with anything)- RZ03 (with anything)- SE14 (with anything)- SU01 (with security, users, and profiles)- SU02 (with security, users, and profiles)


R/3 Tasks

Release 4.0B8–8

��#�� *�� ,� �$��

'��

Check that the production system is set to Not modifiable. The “locks” on the system shouldbe set so that configuration changes (client-independent and client-dependent) cannot bemade directly into the production system.

'��

Configuration changes should not be made directly into the production system.

The goal is to protect the production system from changes, without the changes beingproperly tested and to preserve the integrity of the “pipeline.” A pipeline is defined as theenvironment where development is moved from the development system to the qualityassurance system, and finally to the production system.

If changes are made into the production system, the development and testing “pipeline”could become out of sync with the production system. When this happens, it becomesdifficult to develop and test with any certainty that things will not be different in theproduction system.

All changes should be made in the development system then transported through the“pipeline” into production. In this way, all systems get the same changes.

A common “excuse” to make changes directly into the production system is, “it takes toolong to transport the fix.”

1. The risk is creating an “out of sync” landscape, where the change made to theproduction system, is not the same as made to the development and/or test systems.

2. Emergency transports can occur at any time, with coordination.

(�&

See procedure in chapter 11, the section Setting the Production System to “Not Modifiable”

-.��

There are infrequent exceptions to the rule. These occur when:� There is no mechanism to transport the changes.� An Online Service System note requires the direct change.

Only in these (and similar) cases, the changes must be made directly into the target systems.

Manual entry always increases the chance that an error will be made.


R/3 Tasks


/��$��0��

'��

“Dangerous transactions” are transactions that could do the following:� Damage or corrupt the system� Present a security risk� Adversely impact performance

'��

If a user accesses these transactions by accident, they could corrupt or destroy the R/3System.

Access to dangerous transactions is more critical in the production system than thedevelopment or test systems. This is because of live data and the fact that the company’soperations are dependent on the R/3 System.

Certain transactions should be locked in the production system, but not in the development,test, or training systems.

Standard security normally prevents access to these transactions, but some administrators,programmers, consultants, and functional key users could have access to them dependingon which system they are on. In these cases, the transaction lock provides a second line ofdefense.

There are over 16,000 English transaction codes in the R/3 System. Thus, to make itmanageable, it is only the critical ones that you need to lock. Your functional consultantsshould supply you with any additional critical transactions in their modules.

The following table, contributed to by various Basis consultants and users, lists transactionsthat we recommend you lock. The transactions are categorized by the risk categories:dangerous, security-related, and performance impact.

Transaction Description Dangerous Security Performance

FO40 Document Archiving X

FO41 Bank Master Data Archiving X

FO42 G/L Accounts Archiving X

FO43 Customer Archiving X

FO44 Vendor Archiving X

FO45 Document Archiving X

FO46 Transaction Figures Archiving X

GCE2 Profiles: Initial screen X

GCE3 Maintain Authorizations: Object Classes X


R/3 Tasks

Release 4.0B8–10


KA10 Archive Cost Centers (all) X

KA11 Archive admin: cost centers (all) X

KA12 Archive cost centers (plan) X

KA13 Archive admin: cost centers (plan) X

KA14 Archive cost centers (actual) X

KA15 Archive admin: cost centers (actual) X

KA16 Archive cost centers (line items) X

KA17 Archive admin: cost centers (line items) X

O001 Maintain Users: Initial Screen X

O002 Profiles: Initial Screen X

O016 Maintain Authorizations: Object Classes X

OBR1 Reset Transaction Data(delete transaction data)

X

OBZ7 Maintain Users: Initial Screen X

OBZ8 Profiles: Initial screen X

OBZ9 Maintain Authorizations: Object Classes X

OD02 Maintain Authorizations: Object Classes X

OD03 Profiles: Initial screen X

OD04 Maintain Users: Initial Screen X

OIBA Maintain Authorizations: Object Classes X

OIBB Maintain Users: Initial Screen X

OIBP Profiles: Initial Screen X

OMDL Maintain Users: Initial Screen X

OMDM Profiles: Initial Screen X

OMEH Maintain Users: Initial Screen X

OMEI Profiles: Initial Screen X

OMG7 Maintain Authorizations: Object Classes X

OMI6 Maintain Authorizations: Object Classes X

OML0 Maintain Users: Initial Screen X

OMM0 Profiles: Initial Screen X


R/3 Tasks



OMNP Maintain Authorizations: Object Classes X

OMSN Maintain Users: Initial Screen X

OMSO Profiles: Initial Screen X

OMSZ Maintain Authorizations: Object Classes X

OMWF Maintain Users: Initial Screen X

OMWG Profiles: Initial Screen X

OMWK Maintain Authorizations: Object Classes X

OOAU Maintain Authorizations: Object Classes X

OOPR Profiles: Initial Screen X

OOSB Change View "User Authorizations":Overview

X

OOSP Change View "Authorization Profiles":Overview

X

OOUS Maintain Users: Initial Screen X

OP15 Profiles: Initial Screen X

OP29 Maintain Users: Initial Screen X

OPCA Maintain Users: Initial Screen X

OPCB Profiles: Initial Screen X

OPCC Maintain Authorizations: Object Classes X

OPE9 Profiles: Initial Screen X

OPF0 Maintain Users: Initial Screen X

OPF1 Maintain Authorizations: Object Classes X

OPJ0 Maintain Users: Initial Screen X

OPJ1 Profiles: Initial Screen X

OPJ3 Maintain Authorizations: Object Classes X

OSSZ Maintain Authorizations: Object Classes X

OTZ1 Maintain Users: Initial Screen X

OTZ2 Profiles: Initial Screen X

OTZ3 Maintain Authorizations: Object Classes X

OVZ5 Maintain Users: Initial Screen X

OVZ6 Profiles: Initial Screen X


R/3 Tasks

Release 4.0B8–12


OY20 Maintain Authorizations: Object Classes X

OY21 Profiles: Initial Screen X

OY22 Maintain Users: Initial Screen X





SCC5 Client delete X

SE01 Transport Organizer

SE06 System Table maintenance X X

SE09 Workbench Organizer

SE10 Customizing Organizer

SE11 Data Dictionary maintenance X

SE13 Maintain Storage parameters for table X

SE14 Utilities for dictionary tables X

SE15 Data Dictionary Information System

SE16 Data Browser X

SE17 General Table display X

SE38 ABAP workbench X

SM49 External OS commands X

SM69 External OS commands X

ST05 SQL trace X

SU12 Delete All Users X X


R/3 Tasks


The following table shows dangerous transactions that probably cannot be locked because they are (orcould be) used regularly—or have other valid reasons for use in a production system—but because of thepotential danger, need to have restricted access.


RZ10 Edit System Profiles X

SA38 ABAP Workbench X

SM04 User Overview X

SM12 System Locks X

SM13 Update Terminates X

SM30 Table Maintenance X

SM31 Table Maintenance X

STMS Transport Management System X

SU01 User Maintenance X

SU02 Profiles: Initial Screen X

SU03 Maintain Authorizations: Object Classes X

Table TSTCT contains the transaction codes and the name of the transaction. The currentcontent is over 30,000 entries in the table, with over 16,000 in English.

(�&

Document and keep a list of the following information:� Which transactions were locked?� Why are they locked?� Who locked them?� When were they locked?


R/3 Tasks

Release 4.0B8–14

1��

1. In the Command field, enter transaction SM01 and choose Enter(or choose Tools → Administration, then Administration → Tcode administration).

2. Enter the transaction code youwant to lock (for example, SE14)in the search field at the bottom ofthe TCode column.

3. Choose Enter.

4. Use the Locked checkbox:� To lock a transaction, select the

checkbox next to thetransaction.

� To unlock a transaction,deselect the checkbox.

5. Choose Enter.

Carefully check which transactions you lock. You could accidentally lock yourself out of atransaction, which would prevent you from unlocking this or other transactions.

4

2

5

3


Database Tasks


Access to transactions can also be controlled by building security authorizations on thesecurity object S_TCODE under Cross application authorization objects.

��

!�� Make certain you get a usable backup at year-end.� Send backup tapes offsite for an extended period.

��

!�� Make certain you get a usable backup at year-end.� Send backup tapes offsite for an extended period.

��

��%��

Perform a full system recovery test.

See chapter 2, Disaster Recovery.


Other Tasks

Release 4.0B8–16

SAP System Administration Made Easy 4.0B

Documents

technical

organizationally

sap naming

theoperating

client transport70128

operating

entries button

transport