0% found this document useful (0 votes)

3K views464 pages

R3 Basis Administration Introduction

Basis_Administration

Uploaded by

api-27599940

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

3K views464 pages

R3 Basis Administration Introduction

Basis_Administration

Uploaded by

api-27599940

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

BC360

Introduction

R/3
R/3 Basis
Basis
Administration
Administration
4.0
4.0

Introduction

 SAP AG

BC360 Technical Core Competence 2-1

BC360

Introduction

Course Roadmap Database

Adm inistration
and Backups

Introduction CCMS DBA: Daily

Configuration Check
Procedures

System
Starting and Monitoring
Stopping R/3
Background
Processing
R/3
Authorization

Data Archiving
Installation in R/3
Check

Software
SAP Online Logistics
Service Spool and Print
System

 SAP AG

BC360 Technical Core Competence 2-2

BC360

Introduction

Introduction
Contents:
Review essential R/3 term s and concepts

Recap some basic R/3 system steps (as described in SAP50)

Objectives:
At the end of this unit, you will be able to:
Explain certain important R/3 concepts and terminology

Outline the system steps triggered during an R/3 logon or while a

transaction is being executed

 SAP AG

BC360 Technical Core Competence 2-3

BC360

Introduction

R/3 System Clients

Client 000
Client 001 Default clients
FI
SD

MM
Vertrieb
Client 066
Finanz-
wesen
CO
M aterial-
Material- Controlling
wirtsch.
PP
Prod. Client 100 TR
Treasury
planung
R/3
QM
Qual.-
m anage-
Basis Client 200 PS
Projekt- Customer clients for
m ent PM W
WFF
system
separating and isolating
Instand-
haltung
W orkflow
Workflow business data
HR IS
Personal- Branchen-
wirtsch.
Client xxx
lösungen

 SAP AG

ο R/3 System clients are organizationally independent. Each client has its own data environment with its master
data and transaction data, user master data, and its own customizing parameters.
ο Users in different clients co-exist in the same R/3 System, but their data is isolated and cannot be accessed from
another client. Only users with the necessary authorizations can view or process data in a specific client.
This isolation concept is reflected in R/3 table design, both at the application level and in Customizing, which is a
customer-specific adaptation of the R/3 System.
ο Client 000 is defined as the SAP standard and may not be changed by the customer. This client serves as a copy
template for the creation of further clients.
ο A maximum of 997 clients can be created by the customer.

BC360 Technical Core Competence 2-4

BC360

Introduction

R/3 System Logon Steps Ex.: IP: a.b.c.73

Ex.: IP: X.Y.Z.10 SAPGUI

2 10

IP: X.Y.Z.20 1 3 IP: X.Y.Z.10

M
Dispatcher Dispatcher
9
4

D V E B S ... D V B D ...
8
5

Database processes
7

Database

 SAP AG

ο When a SAPGUI process is started on the front end, a command line parameter is sent, indicating one of the
following:
λ A specific dispatcher can be accessed directly
λ The logon must first be sent to the message server for purposes of logon load balancing
ο When using logon load balancing, the message server returns the IP address and instance number of a specific
dispatcher. The number of dispatchers available for a particular logon is configured in the system. Logon load
balancing is useful if certain user groups are assigned to work on specific servers.
ο The message server returns the IP address of one of these assigned dispatchers, which has for example shown
the best response time during the last five minutes. Response times are stored in the collected Workload data.
ο The frontend process then connects to the assigned dispatcher, which selects a free dialog work process to
compare the logon user data with the user data stored in the database.
ο If the logon user data does not agree with the stored user data, no logon is allowed. If the logon is successful, this
dispatcher and its work processes are used for the duration of the session.
ο If a user logs off and then logs on again to the system, logon load balancing may cause the message server to
select another dispatcher for the user to work with.

BC360 Technical Core Competence 2-5

BC360

Introduction

Defining "Instance" and "Application Server"

Instance A Instance B

Dispatcher Dispatcher

S S ... B ...

Central Instance C

Dispatcher

M essage
D V E B S ... server

 SAP AG

ο An instance is a group of R/3 services which are started are stopped together. Usually the term signifies one
dispatcher with its work processes, although strictly speaking, other standalone services such as a Gateway can be
called an instance.
ο A central instance is a dispatcher offering all the R/3 system processes: DVEBMGS. In this example, see Instance
C, where all the processes except the Gateway are shown.
ο An R/3 application server consists mainly of a dispatcher, its work processes and main memory assigned to it.
ο In the R/3 environment, ”client” and ”server” are often considered as software, therefore several application
servers can run on one computer.
ο From the hardware point of view, however, an application server can be defined as a computer on which at least
one dispatcher, also called a dialog instance, is running.

ο The following restrictions apply to the number of each type of work process:
λ Dialog: each dispatcher needs at least two dialog work processes (not shown above)
λ Spool: ≥1 / R/3 System (more than one per dispatcher allowed)
λ Update: ≥1 / R/3 System (more than one per dispatcher allowed)
λ Background: ≥2/ R/3 System (more than one per dispatcher allowed)
λ Enqueue: =1 / R/3-System (only one Enqueue work process is required and allowed)

BC360 Technical Core Competence 2-6

BC360

Introduction

System Dialog Step

Dialog request queue
2 Dialog work process
1 3 5 Taskhandler

Dynpro processor 6

Dispatcher
9
SAPGUI

8 ABAP processor

Database interface

12 10

Roll in 7
4
Roll out
11

Database
User context in main mem ory

 SAP AG

ο Once you have established a connection with a dispatcher through the SAPGUI, and a session is started for you in
the system, the following steps are executed for each request:
ο Data is passed from the SAPGUI to the dispatcher using the SAPGUI protocol based on TCP/IP
λ The dispatcher classifies the request and places it in the appropriate request queue
λ The request is passed in order of receipt to a free dialog work process
λ The subprocess ”taskhandler” restores the user context in a step known as ”roll in”. The user context
contains mainly data from currently running transactions called by this user and its authorizations
λ The taskhandler calls the dynpro processor to convert the screen data to ABAP variables
λ The ABAP processor executes the coding of the ”Process after Input” module (PAI module) from the
preceding screen, along with the ”Process before Output” module (PBO module) of the following screen.
It also communicates, if necessary, with the database
λ The dynpro processor then converts the ABAP variables again to screen fields. When the dynpro
processor has finished its task, the taskhandler becomes active again
λ The current user context is stored by the taskhandler in shared memory (roll out)
λ Resulting data is returned through the dispatcher to the front end

BC360 Technical Core Competence 2-7

BC360

Introduction

Dynpro100
W ork Process Multiplexing Dynpro200

SAPGUI Request queues

... 18
...
9
Request queues 1 10
2 11
M
Dispatcher Dispatcher
8 17
3 12

D V E B S ... D V B D ...
7 16
4 13

Database processes
6
15
5

14
Database

 SAP AG

ο If a transaction involves the use of more than one screen, the system dialog steps shown on the preceding page
are normally performed by several different dialog work processes in a dispatcher. This is known as ”work
process multiplexing”.
ο Each dialog request is first placed by the dispatcher in the dialog request queue, from where it can later be
assigned to a free dialog work process.
ο The work processes do not perform database operations. Rather, they pass data and commands to the assigned
database processes using their own database interface.

BC360 Technical Core Competence 2-8

BC360

Introduction

Summary of this Unit

In this unit, you have reviewed the following:

The steps executed in R/3 during logon

The terms “instance” and “application server”, as used in

the R/3 environment
Processing of a system dialog step

Work process m ultiplexing as performed by dialog work

processes

 SAP AG

BC360 Technical Core Competence 2-9

BC360

Introduction

Further Documentation

SAP50 - Basis Technology

SAP Technology Infrastructure

(Brochure available in SAPNet under Inform ation -
R/3 System - Basis Technology)
R/3 Online Documentation

OSS Notes: 39412 (Number of W orkprocesses)

21960 (2 Instances on one computer)
5424 (FAQ: enqueue/locking)
and others in BC-KRN-CST

 SAP AG

Starting and Stopping R/3

R/3
R/3 Basis
Basis
Administration
Administration
4.0
4.0

Starting and Stopping

R/3

 SAP AG

BC360 Technical Core Competence 2-10

BC360

BC360 Technical Core Competence 2-11

BC360

Starting and Stopping R/3

Contents:
Processes and services in an R/3-UNIX-Oracle environment

Start and stop processes and procedures

Objectives:
At the end of this unit you will be able to:
Describe R/3 start and stop processes

Explain the relationship between database processes, R/3

processes, and operating system processes
Start and stop an R/3 System

Analyze error situations during system startup or shutdown

 SAP AG

Once you have completed this unit you will be able to:
• Describe R/3 start and stop processes
• Explain the relationship between database processes, R/3 processes, and operating system
processes
• Start and stop an R/3 System
• Analyze error situations during startup or shutdown

BC360 Technical Core Competence 2-12

BC360

Starting and Stopping R/3

Course Roadmap Database

Administration
and Backups

Introduction CCM S
Configuration DBA: Daily Check
Procedures

System
M onitoring
Starting and
Stopping R/3
Background
Processing
R/3
Authorization

Data Archiving
SAP O nline in R/3
Service System

Software
Logistics
Installation
Check Spool and Print
R

 SAP AG

BC360 Technical Core Competence 2-13

BC360

Starting and Stopping R/3

Starting the R/3 System

R/3 administrator tasks

Operating system UNIX

Logon UNIX shell .

1
<host>> startsap
<sid>adm ( startsap_<host>_<instance no>)
2
3 4 5

Central
saposcol
Database Instance

 SAP AG

The operating system user logs on to the UNIX operating system as user <sid>adm.
To start R/3, run the shell script startsap_<host>_<instance_no> from the home directory of user
<sid>adm. The script startsap_<host>_<instance no> has the alias "startsap".
startsap starts the saposcol process, which is the statistics collector for operating system resource data,
if it is not yet running.
startsap calls the script startdb, which starts the database if it is not already started.
startsap then starts the central instance.
The R/3 administrator can start additional instances and application servers. To start the instances
independent from the database, use the startsap script.
startsap has the following options:
• startsap r3: Checks if the database is running; if it is, only the instance is started
• startsap db: Starts only the database
• startsap all: Default entry; starts both the database and the R/3 instance

BC360 Technical Core Competence 2-14

BC360

Starting and Stopping R/3

Starting the R/3 System

UNIX shell . Start profile
Instance startup > startsap_<host>_<nr>
sequence

sapstart

Default and instance profile

Processes SE CO MS Disp+work

Services WP … WP gwrd

Connection R

Database
 SAP AG

This graphic displays the R/3 start procedure in more detail.

saptrace/background/alert_<SID>.log

saptrace/usertrace/ora_<pid>.trc

Oracle trace
UNIX shell information
sapdba
<host> > sapdba sapcheck\… log files
sapreorg\...
sapbackup\back<SID>
\ ...
R

 SAP AG

During database startup, startsap calls the script startdb, which writes the appropriate log file
[Link].
All significant events, such as starting and stopping the database and any database errors, are logged in
the Oracle alert file /oracle/<SID>/saptrace/background/alert_<SID>.log. Detailed error information is
logged in the Oracle trace file /oracle/<SID>/usertrace/ora_<pid>.trc.
If the administrator <sid>adm uses sapdba to start the database, sapdba writes additional log files to
directory /oracle/<SID>/sapreorg , …/sapcheck, …/sapbackup, depending on the actions executed.

BC360 Technical Core Competence 2-18

BC360

Starting and Stopping R/3

R/3 Startup Logs and Traces

$HOME/<sid>adm /startsap_<host>_<instance no.>

$HOME/<sid>adm /startsap_<host>_<instance no.>.log

/sapm nt/<SID>/<Instance><No>/work/ ...

stderr1 … m Standard error files of program SAPSTART

sapstart<m >.trc Trace files of program SAPSTART

Startup log of program SAPSTART

[Link]

dev_ms Trace file of the m essage server

dev_disp Trace file of the dispatcher

Tim e dev_w0 … n Trace files of the work processes

 SAP AG

The R/3 startup scripts log their actions to log files in the home directory of the user <sid>adm.
R/3 work directories contains trace files and error files for messages relating to the startup of work
processes. There is a work directory for each R/3 instance. The work directory contains information
that may not be found in the R/3 System log.
The work directory files are initialized in chronological order.
To define the level of information written to the trace files, set the profile parameter rdisp/TRACE in
the instance profile. The values for this parameter are:
0: Write only errors (no traces)
1: Write error messages and warnings (default)
2 : Write error messages and a short trace
3 : Write error messages and the complete trace

BC360 Technical Core Competence 2-19

BC360

Starting and Stopping R/3

Startup Diagnostics
UNIX shell

c:> startsap
[Link]

UNIX shell
c:> sapdba
-startup sapstart.*
Script startdb Program sapstart

[Link]
Oracle instance
<SID> R/3
instance
R/3
System log

Sapdba alert_<SID>.log
logfiles ora_<nr>.trc R/3 tracefiles dev*
R

 SAP AG

This graphic shows the possible points of failure during R/3 System startup. If an error occurs, you
must locate the error information and determine the cause of the problem.
If access is denied on resources such as startdb script or sapstart, this could be because:
• The file system permissions are not correct
• User <sid>adm is not installed correctly
• Umask problems exist
If the database has not been started, the work processes cannot connect to the database, and the R/3
System cannot be started. The database could fail to start because:
• The environment variables are not correct
• The database is running in DBA mode
• Database files are lost or corrupt
• Data files have been renamed in the database but not at operating system level
If the R/3 System does not start, it could be because:
• The UNIX kernel is not configured correctly
• There are errors in the Memory Management configuration
• The R/3 profiles are not accessible (file permissions)
If you can log on to the R/3 System, use the R/3 System log to analyze startup problems.

BC360 Technical Core Competence 2-20

BC360

Starting and Stopping R/3

Reasons for Stopping the R/3 System

Planned downtime
Profile parameter changes
... Start / Stop ...
Parameter_1 = 0 Parameter_1 = 3
Parameter_2 = 0 Parameter_2 = 5
Activation

R/3 System
System maintenance (OS, DB)
de
R/3 upgrades g ra
Up

Unplanned downtime
Hardware failure
Data
R

 SAP AG

There are two reasons for stopping the R/3 System; for planned downtime and unplanned downtime.
Planned downtime should be scheduled to:
• Change profile parameters
• Perform an R/3 upgrade
• Perform operating system or hardware maintenance
Unplanned downtime can occur because of hardware errors, such as a disk crash, or configuration
problems.

BC360 Technical Core Competence 2-21

BC360

Starting and Stopping R/3

Before Stopping the R/3 System

Check background and batch input jobs SAP R/3

Display System Help
Are any jobs active or planned?
Job log Display Release
W ill R/3 jobs be triggered from external systems?

Check update status with SM 13

Send system message with SM 02
Check logged-on users with SM04
Check external interfaces

R/3 System
External
application

 SAP AG

Before the R/3 System is stopped, the R/3 administrator should check the:
• Job Overview
• Check if any background jobs from any application server are active or have been triggered
externally. Use Transaction SM37, or choose System Services Jobs Job overview.
• Process Overview
• Check if the background work process BTC is running in any application server. Choose Tools
Administration Computing Center Management System Control All work processes.
• Batch Input Overview
• Check if any batch input jobs are running. Choose System Services Batch input Edit Overview.
• Update records
• Check if any update records are open when the system is stopped, the records are rolled back and
set to status init. At startup, the records are processed again.
The R/3 administrator must decide whether to interrupt the jobs or wait until they are finished.
You should also give system users an advanced warning about the system shutdown by creating a
system message, using Transaction SM02. Before shutting down the system, use Transaction SM04 to
check whether users are still logged on, and ask them to log off.
The R/3 administrator and administrators of external systems must also inform one another about
data transfers between their respective systems.

BC360 Technical Core Competence 2-22

BC360

Starting and Stopping R/3

Stopping the R/3 System

R/3 administrator <sid>adm

Ed it Select Mo nito rin g Co ntrol U tilities System He lp

?
Cho ose RefreshDetails Cho ose
UNIX UNIX
Oracle
c:> stopsap Server Manager c:> sapdba
R/3 CCMS
[r3|all] -shutdown

1a 1b Script stopdb

Oracle instance
R/3 R/3 <SID>
additional central
instances instance
R

 SAP AG

To stop the R/3 System, the R/3 administrator must:

• Stop the application servers (dialog and central instances). There are two ways to do this:
• Use the CCMS in R/3, or
• Run the script stopsap_<hostname>_<instance no> by calling the alias stopsap r3
• Stop the database. There are three ways to do this:
• Use stopsap all or stopsap; here the script stopdb is called
• Use the Oracle Server Manager
• Use SAPDBA

BC360 Technical Core Competence 2-23

BC360

Starting and Stopping R/3

Backup Offline: Database Reconnect

Instance profile

Disp+work
R/3 buffer
preserved
WP WP … WP

Application server running

in "reconnect" status

Database shut down

Database
R

 SAP AG

If the database reconnect is configured for R/3, you do not have to stop the application server for an
offline backup. The R/3 buffers are not cleared, and the work processes have the status "reconnect"
until the database is restarted.
Set the parameter rsdb/reco_trials = n, where n = how many times the work processes attempt to
connect to the database.
Set the parameter rsdb/reco_sleep_time = m, where m = how many seconds the work processes
"sleep" between attempts.
During an offline backup, the database must be shut down. The work processes will receive an error
return code of class "reconnect" from the database.
Each time a user request occurs, or the sleep time is expired, the work processes retain the status
"reconnect" and try to connect to the database.
Prior to an offline database backup, the R/3 administrator should send a message to all users,
preventing them from logging on to the system and restarting work processes.

BC360 Technical Core Competence 2-24

BC360

Starting and Stopping R/3

Stopping Error Diagnostics

Database cannot stop

UNIX shell UNIX shell

c:> sapdba -shutdown c:> stopsap [ r3 | all ]

Cannot stop

Database
R

 SAP AG

If the database cannot be stopped when the R/3 System is stopped, it could be because:
• The database is performing a rollback of aborted transactions caused by the shutdown of the R/3
system. Depending on the last commit and the application, this can take a long time.
• An online backup is running. You should wait until the online backup is finished.
• The archiver becomes stuck exactly at the same time you are stopping the R/3 System. You should
save the archives to tape, in order to free the file system.
If there is no obvious reason why the database cannot be stopped, the database administrator should
check the R/3 System log, using Transaction SM21, and the database alert file.
Ensure that the problem is solved before making further attempts to stop the database.
For further information, see also the R/3 Online Documentation, Database Backup, Reorganization,
and Recovery.

BC360 Technical Core Competence 2-25

BC360

Starting and Stopping R/3

Summary of this Unit

Now you are able to:

Describe R/3 start and stop processes

Explain the relationship between database processes,

R/3 processes, and operating system processes
Start and stop an R/3 System

Analyze error situations during system startup or

shutdown

 SAP AG

BC360 Technical Core Competence 2-26

BC360

Starting and Stopping R/3

Unit Actions

Do the exercises

? Answer the questions

Fill in the blanks

Solutions for the exercises

Answers to the questions

 SAP AG

Note:

There may not be sufficient time to work through all the exercises during the course. The exercises
marked Optional should be seen as supplementary examples that can be used, time permitting, during
the course. Attendees can also use these exercises after the course, to consolidate what they have
learned.

BC360 Technical Core Competence 2-27

BC360

No. Exercise

1) Start and stop the R/3 System using the startsap script.

1.1 Log on to the UNIX operating system as user ora<sid>.

1.2 Start the startsap script.

1.3 Check the UNIX processes and the R/3 startup logfiles.

1.4 Are there any problems? Try to analyze the situation.

1.5 Log on to UNIX as user <sid>adm.

1.6 Start the startsap script and repeat steps 1.3 and 1.4.

1.7 Start the SAPGUI.

1.8 Log on to the R/3 System (ask the course instructor for an R/3 user).

1.9 Display the name of your server and find out the R/3 process types for which the
server has been configured.

1.10 Is an application server configured in your system?

1.11 Display the Job overview.

1.12 Display the Batch Input overview.

1.13 Display the overview of active users.

1.14 Send the following message to the active users:

"System Stop at 14:00.

Please exit your transaction and log off."

1.15 Stop only one R/3 instance.

1.16 Stop the entire R/3 System. (DB)

BC360 Technical Core Competence 2-28

BC360

No. Solution

1) Start and stop the R/3 System using the startsap script.

1.1 Log on to the UNIX operating system as user ora<sid>.

1.2 Enter startsap in the UNIX shell.

1.3 To analyze R/3 UNIX processes, use command

ps –ef | grep dw.

Analyze the R/3 trace files /usr/sap/<SID>/DVEBMGS00/work/dev*

1.4

1.5

1.6 To analyze R/3 UNIX processes, use command

ps –ef | grep dw.

1.7

1.8

1.9 To display the server name, use Transaction SM51 or display the system status.
Information about the process types is also displayed. Alternatively, you can use
Transaction RZ10.

1.10 To check if an application server is configured in the system, use Transaction SM51.

1.11 To display the Job overview, use Transaction SM37, or choose System Services
→ Jobs → Job overview.

1.12 To display the Batch Input overview, use Transaction SM35, or choose System →
Services → Batch input → Edit → Overview

1.13 To display the overview of all active users, use Transaction SM04.

1.14 To send a message to all active users, use Transaction SM02, or choose Tools →
Administration → System messages.

1.15 As user <sid>adm, run the script stopsap r3 on a UNIX shell.

1.16 As user <sid>adm, run the script stopsap db on a UNIX shell.

BC360 Technical Core Competence 2-29

BC360

In the following, you will find excerpts from the Operation Manual, Chapter 3 Starting and Stopping R/3, in the
section Stopping the R/3 System.
To perform these exercises, complete the table in the excerpts as follows:

1 The table under Tasks.

For your company, determine the activity group (person responsible), and the frequency with which each of
the listed tasks should be performed for the production system <PRDSID>, the quality assurance system
<QASSID>, and the development system <DEVSID>. Enter this information and the appropriate
transaction for the task in the table (the first row is already completed to provide an example).

Tasks

Activity Frequency Menu Path (NT or R/3) Trans- Activity

<PRD <QAS <DEV action Group

SID> SID> SID>

Displaying active users AR AR AR Tools → Administration → Monitor AL08 <R3ADM>

→ Performance → Exceptions/Users
→ Active Users → Users global
Sending system Tools → Administration →
messages Administration → System Messages
→ Create
Displaying the status of Tools → CCMS → Control/
work processes Monitoring → All work processes
Displaying background Tools → CCMS → Jobs →
jobs
Maintenance

Displaying Batch Input System → Services → Batch-Input →

jobs
Edit

Checking interfaces Tools → Administration → Monitor

→ System monitoring → Gateway
monitor

Stopping R/3 and its SAP Service Manager and SAPDBA

database

D: Daily W: Weekly M: Monthly Y: Yearly AR: As required

<R3ADM>: System administrator

BC360 Technical Core Competence 2-30

BC360

No. True? Question:

1) Which user should be logged on to the UNIX operating system, in order

to start the R/3 System?

1.1 <sid>adm

1.2 guest

1.3 ora<sid>

2) The program SAPSTART is called from:

2.1 The user <ora>sid.

2.2 The script startsap_<hostname>_<instance no.>, which is referenced

with the alias startsap.

2.3 The script startsap, which is executed by the user root.

2.4 The user <sid>adm entering startsap on a UNIX shell.

3) The first component that is started is:

3.1 The database.

3.2 The saposcol.

3.3 The central instance.

4) To start the work processes, the R/3 dispatcher reads:

4.1 The instance profile.

4.2 The default profile.

4.3 The C source and the UNIX user environment first, then the start
profile.

4.4 The C source and the UNIX user environment first, then the default and
the instance profile.

5) To start the dispatcher and message server, the startsap script reads:

5.1 The instance profile.

5.2 The default profile.

5.3 The start profile.

6) How can you check the database and R/3 logs and traces that were
written during startup or shutdown?

BC360 Technical Core Competence 2-31

BC360

6.1 Only in the work directory of the R/3 System.

6.2 In the home directory of user <sid>adm.

6.3 Use the Database alertfile at the operating system level, or use
Transaction ST04.

6.4 Use the R/3 CCMS and choose DB Administration --> DBA Scheduling,
or use the CCMS and choose Control/Monitoring --> Control Panel -->
Utilities --> Trace files.

6.5 Use the R/3 monitoring traces (developer tracefiles dev*) during or after
R/3 System startup.

BC360 Technical Core Competence 2-32

BC360

No. True? Question:

1) Which user should be logged on to the UNIX operating system, in order

to start the R/3 System?

1.1 X <sid>adm

1.2 guest

1.3 ora<sid>

2) The program SAPSTART is called from:

2.1 The user <ora>sid.

2.2 X The script startsap_<hostname>_<instance no.>, which is referenced

with the alias startsap.

2.3 The script startsap, which is executed by the user root.

2.4 X The user <sid>adm entering startsap on a UNIX shell.

3) The first component that is started is:

3.1 The database.

3.2 X The saposcol.

3.3 The central instance.

4) To start the work processes, the R/3 dispatcher reads:

4.1 X The instance profile.

4.2 X The default profile.

4.3 The C source and the UNIX user environment first, then the start
profile.

4.4 X The C source and the UNIX user environment first, then the default and
the instance profile.

5) To start the dispatcher and message server, the startsap script reads:

5.1 The instance profile.

5.2 The default profile.

5.3 X The start profile.

6) How can you check the database and R/3 logs and traces that were
written during startup or shutdown?

BC360 Technical Core Competence 2-33

BC360

6.1 Only in the work directory of the R/3 System.

6.2 X In the home directory of user <sid>adm.

6.3 X Use the Database alertfile at the operating system level, or use
Transaction ST04.

6.4 X Use the R/3 CCMS and choose DB Administration --> DBA Scheduling,
or use the CCMS and choose Control/Monitoring --> Control Panel -->
Utilities --> Trace files.

6.5 X Use the R/3 monitoring traces (developer tracefiles dev*) during or after
R/3 System startup.

CCMS Configuration

R/3
R/3 Basis
Basis
Administration
Administration
4.0
4.0

CCMS Configuration

 SAP AG

BC360 Technical Core Competence 2-34

BC360

CCMS Configuration

BC360 Technical Core Competence 2-37

BC360

CCMS Configuration

Setting up the CCMS

Import and maintain R/3 profiles

Setup process
Define operation m odes

Create instance definitions

Adapt instance definitions and operation m odes

Maintain timetable for normal operation

 SAP AG

Before you can work with the CCMS, it must be set up correctly for your environment. Consistency and
accuracy of CCMS functioning depend primarily on how it is initially configured by the customer.
Set up the CCMS in the following steps:
– Maintain R/3 profiles. Normally, you import the profiles of all active servers after
installation. They are then automatically saved to the database and activated.
– Define at least one operation mode.
– Generate instance definitions for the instances created during R/3 System installation.
– Assign instance definitions to operation modes, if necessary, and adapt the work process
distribution.
– Define the timetable for normal operation for a full 24-hour cycle.
If operation modes, instances, or timetable are not correctly defined, the CCMS will not display meaningful
data.

BC360 Technical Core Competence 2-38

BC360

CCMS Configuration

Transaction RZ10: Profile Maintenance

Used for maintenance of all R/3 profiles:

Start profile
Default profile
Instance profile

Allows you to change profile parameters using basic

mode or extended mode
Provides version management
Lets you list the active parameters of application
servers

 SAP AG

Import R/3 profiles before setting up your R/3 operating modes, using the CCMS tool for R/3 profile
maintenance, Transaction RZ10. Call this transaction directly or, from the main R/3 menu, choose Tools CCMS
Configuration Profile Maintenance.
In RZ10, you can display administrative data for each profile, including profile name, type, version,
corresponding operating system file, reference server, and modification and activation data.
There are two modes for editing profiles:
– In basic mode you can edit a set of parameters that are changed most frequently. You do not have to know
the technical parameters names. Parameters are grouped together to reflect interdependencies. If you change
one parameter, the dependent parameters are automatically adjusted.
– In extended mode you use a editor-like tool. You have to know the technical names of parameters and their
dependencies.
Additionally, you can delete a single version or all versions of a profile, compare profiles in the database with
active profiles, and check profiles in various ways.

BC360 Technical Core Competence 2-39

BC360

CCMS Configuration

R/3 Profiles

R/3 installation program

R3SETUP

Global profile directory

In
D
St

CCMS Configuration

Checking and Com paring R/3 Profiles

R/3 Profile
Maintenance (RZ10)

Single profile check

Check of all profiles:

º All profiles of active servers
º All profiles in operation modes

Comparison of database profile and active server profile

 SAP AG

You can carry out extensive health checks for one or more profiles. These checks include making profile syntax
checks, spell checking the parameter names, and semantic checks. Running these checks produces a log
containing warnings and error messages where appropriate.
When you check single profiles, the parameters are divided into classes. For each class there is a separate check
rule. For example, the check rule for parameter class time value reports an error if the value of a parameter
belonging to this class (for example, rdisp/btctime) is smaller than 0. See R/3 Online Documentation.
When you check all profiles, in addition, all profiles of one type used in an R/3 System can be tested to see
whether they are consistent with each other. For example, all start profiles can be checked to see whether exactly
one message server is started, or all instance profiles checked to see whether an enqueue work process was
configured. You can check either all profiles of active servers or all profiles in operation modes.
After an application server has been started, an automatic check is performed to see whether the server's profile
data as stored in the database still matches the active profiles at operating system level. If this is not the case, an
alert is triggered in the Alert Monitor. This allows you to determine whether the operating system files have
been changed manually. You can also perform this check manually.

BC360 Technical Core Competence 2-43

BC360

CCMS Configuration

Operation Modes: Overview

To use operation modes to maximize usage

of system resources:

Define operation m odes

Create instance definitions

Assign instance definitions to operation modes and adapt configuration

Switch operation m odes

Schedule operation modes

Perform operation mode switch diagnostics

 SAP AG

BC360 Technical Core Competence 2-44

BC360

CCMS Configuration

Operation Modes: Concept

12
11 1
10 2
9 3

8 4
7 6 5

BTC

Server 1:
Operation Day Dialog 3
mode: Instance Background 2
Day definition 1 Night Dialog 2
Adapt original Background 3
work process
distribution
Server 2:
Operation Day Dialog 4
Instance
mode: Background 2
definition 2
Night Night Dialog 2
Background 4

 SAP AG

If you choose to take the current settings from active instances when generating instance definitions, each
productive operation mode that has been created previously will be assigned with the current work process
distribution of the instance to each new instance definition.
If you create a new instance definition not based on current settings of active instances, you have to assign
operation modes manually.
For each assigned operation mode you can adapt the related work process distribution for the instance
definition. You can change the type of work processes. You cannot change the total number of work processes,
because it is determined in the instance profile.
The minimum number of work processes for dialog and also for background processing is 2. The total number
of dialog work processes is always the total number of all work processes minus all non-dialog work processes.
See R/3 Online documentation on further restrictions.
It is possible to reserve one or more background work processes exclusively for high priority jobs (class A jobs).

BC360 Technical Core Competence 2-50

BC360

CCMS Configuration

Operation Mode Switch: Concept

Shutdown NIGHT_OPERATION

DAY_OPERATION
Shutdown

Server 1 Server 2

Dispatcher Dispatcher

D D D/B B B D D D/B D/B B B

 SAP AG

When switching between operation modes, work processes are redistributed automatically, without stopping and
restarting the instances. No time is lost due to the system being unavailable. Only work process types are
changed. The total number of work processes remains unchanged after the operation mode switch.
If processes still have jobs at switch time, they are switched one by one when the jobs are completed. Thus,
normal system operation is not interrupted. No program will be cancelled. System performance is maintained, as
R/3 buffers such as ABAP buffers and table buffers are not refreshed.
Operation mode switches are recorded in the system log. The old and the new process type are recorded for each
switched work process.

BC360 Technical Core Competence 2-51

BC360

CCMS Configuration

Scheduling Operation Modes

Timetable for Tim etable for

normal operation (24-hour cycle) exceptional operation for M arch 29

08.00 - 21.00 Op. m ode A M arch 29

3 p.m . - 4 p.m. Op. m ode C
21.00 - 08.00 Op. m ode B

B A B
March 28

B A C A B
March 29

00.00 08.00 15.00 17.00 21.00 23.59

 SAP AG

The automatic switching of operation modes is controlled by timetables. Timetables must also be maintained for
CCMS monitoring. To maintain or check the timetable, use Transaction SM63 or, from the main R/3 menu,
choose Tools CCMS Configuration OP Modes Timetable.
The timetable allows scheduling in terms of 24-hour days, divided into intervals of 60, 30, or 15 minutes. You
can define normal and exceptional operation.
–In normal operation, the defined time intervals for operation modes are repeated in a 24h cycle. You must
schedule a complete period of 24 hours, not just part of a day. Otherwise, problems may occur during
operation mode switching.
–In exceptional operation, the defined time intervals for operation modes are activated once for a specified
time period. The timetable has a higher priority than the timetable for normal operation. You can specify part
of a day (without defining a 24-hour cycle).
Note that only productive operation modes can be switched automatically, that is, entered in a timetable.
If the timetable for normal operation is not defined, the start configuration according to the profile will remain
active and no automatic operation mode switch occurs.

BC360 Technical Core Competence 2-52

BC360

CCMS Configuration

Switching Operation Modes Manually

Control panel
(Transaction RZ03)

B A C B

00.00 08.00 21.00 23.59

 SAP AG

Sometimes it may be necessary to switch operation modes manually. You should do so only in exceptional
cases, for example, when automatic switching did not work correctly. Use Transaction RZ03, or, from the main
R/3 menu, Choose Tools CCMS Control/Monitoring Control Panel.
In the Control Panel screen, you can switch to a particular operation mode either on all servers or on an
individual server.
Ensure that a manual operation switch does not disrupt system operation by, for example, providing too few
dialog processes.
You should always first carry out a simulation of the switch. To simulate an operation mode switch, choose
Tools CCMS Control/Monitoring Control Panel Control Switch OP mode Simulation. A test log describes
which switches are possible and the errors that may occur when a real switch takes place.
To switch the operation mode after a simulation, Control Switch OP mode. The servers will remain in the
manually activated operation mode until the next switch time.

BC360 Technical Core Competence 2-53

BC360

CCMS Configuration

Operation Mode Switch Diagnostics

SAP R/3 instance

disp+[Link]

WP ... WP gwrd

Operation mode
Inconsistencies switch failure

Operating system
DB
Configuration
Start and according to
instance profile operation mode Start and
DB
instance profile R

 SAP AG

If the operation mode switch fails, the administrator must investigate the cause of the failure. The cause is most
likely to be inconsistencies in the system. Inconsistencies can occur, for example, if there is a discrepancy
between in the number of work processes:
– In the instance profile on the operating system
–On the database
–Within the operation mode definition
You should check regularly whether the number of currently running work processes is the same as the number
entered in each of these three parts of your system.
If you change profiles and restart the system, you must adapt operation modes as well as instance definitions
according to the current status.
Further helpful transactions:
–To check the OP mode switch and the work process switch within the system log, use Transaction SM21 or,
from the main R/3 menu, choose Tools-->Administration-->Monitor-->System monitoring-->Process
overview.
–To check the work process switch within the process overview, use Transaction SM50 or, from the main R/3
menu, choose Tools-->Administration-->Monitor-->System monitoring-->Process overview.

BC360 Technical Core Competence 2-54

BC360

CCMS Configuration

Starting and Stopping Instances with the CCMS

Control Panel Start / stop

Instance A
(Transaction RZ03)

Instance B

Control instance and database

started from operating system
R

 SAP AG

You can start and stop R/3 instances with the CCMS. CCMS profiles and operation modes should be maintained
correctly.
When starting instances with the CCMS:
–The database and at least one R/3 instance (the "control instance") must have been started using operating
system tools
–You can use the Control Panel of the CCMS (Transaction RZ03) to select an operation mode and start the
remaining instances remotely. You can start multiple instances or special instances. The Control Panel
enables you to check the startup log for each instance that has been started.
On UNIX platforms, the rexec functionality is used to start servers remotely. Therefore, you need to maintain a
startup user and password within the instance definition.
On platforms that have not rexec, it is necessary to use a tool which provides a substitute for rexec. For example,
to start instances of a Windows NT server from a UNIX server, a rexec daemon must be running on the
Windows NT server.

BC360 Technical Core Competence 2-55

BC360

CCMS Configuration

Summary of this Unit

Now you are able to:

Set up the CCMS:

Import and maintain profiles

Create operation modes and instance definitions

Maintain operation m odes and instance definitions

Schedule operation modes

Start and stop instances with the CCMS

 SAP AG

BC360 Technical Core Competence 2-56

BC360

CCMS Configuration

Unit Actions

Do the Exercises

? Answer the Questions

Fill in the Blanks

Solutions for the Exercises

Answers to the Questions

 SAP AG

BC360 Technical Core Competence 2-57

BC360

The R/3 System should be in initial status regarding profiles, operation modes, and instance
definition.

No. Exercise

1 Prepare your R/3 System to start

1.1 Go to the global profile directory. Create a subdirectory called BACKUP, and save
the profiles in the new subdirectory.

1.2 If the R/3 System is not already running, start it.

1.3 Which methods exist to import profiles into the R/3 System? Which method is most
suitable in the present case?

2 Importing, maintaining, and activating profiles

2.1 Import all profiles into the R/3 System, and perform a consistency check.

2.2 Check the administration data. Does it correspond with the operating system paths
data? If not, correct it.

2.3 Determine the number and the type of the R/3 System work processes.

2.4 Use the R/3 System tool Profile Maintenance to change the number of dialog work
processes to at least 4, and the number of background work processes to at least 2.
Check if the number of enqueue and spool work processes are both equal to one.
The total number of work processes should not exceed 10. Are the names of the
directories of your instance specified correctly? If not, change them with the
maintenance tool.

2.5 If you have not done so already, activate the profiles. Check the result at operating
system level.

3 Activating your changes

3.1 Restart the R/3 System.

3.2 Which work processes are running now? Compare 2.3.

3.3 Check the profile parameters

4 Create Operation Modes and Instance Definitions

4.1 If the R/3 System is not already running, start it.

4.2 Create two productive operation modes: Day and Night.

4.3 Create the instance definitions for your R/3 System if it is not yet done.

BC360 Technical Core Competence 2-58

BC360

4.4 Assign operation modes and work process distributions to each instance.
NOTE: During the time of the course, at least 2 background work processes should
be running.

5 Schedule Operation Modes

5.1 Maintain the operation timetable. One of the operation modes should become active
within the next 15 minutes.

6 Manual switch of Operation Mode

6.1 Activate one operation mode manually.

BC360 Technical Core Competence 2-59

BC360

No. Solution

1.1 NT: The global profile directory is \usr\sap\<sapsid>\SYS\profile.

UNIX: The global profile directory is /usr/sap/<sapsid>/SYS/profile.

1.2 See unit Starting and Stopping the R/3 System.

1.3 The R/3 System offers you two methods to import profiles: The first method is most
suitable.
1. You can import all relevant profiles at once, for example, after a new installation.
Choose: CCMS --> Configuration --> Profile Maintenance --> Utilities --> Import
profiles --> Of active servers.
2. You can import a single profile manually. Use Transaction RZ10, or, from the
main R/3 menu, choose CCMS --> Configuration --> Profile Maintenance and
specify a name for the profile you are importing. Choose Create and enter
administration data. Enter a short description and the type of profile you are
importing. Choose Copy. Choose Profile --> Import and enter the path of the profile
you are importing. Choose Copy. Save.

2.1 See 1.3.1. To perform a consistency check, choose CCMS --> Configuration -->
Profile Maintenance. Choose a profile and choose Check.

2.2 Check the administration data. If the operating system paths (case-sensitive) are
incorrect, correct them. Choose Back and save your changes. You can also activate
the profiles for the default profile and the start profile.

2.3 Use Transaction SM50 or, from the main R/3 menu, choose: Tools -->
Administration --> Monitoring --> System monitoring --> Process overview.

2.4 Use Transaction RZ10, Profile Maintenance, as above, and edit the profile
parameters of the instance. If they do not coincide with the operating system paths
of your instance, change the directories.

Choose Copy. Change the work process distribution. Choose Copy. Save and
activate the instance profile.

2.5 You can check the result in the global profile directory (see 1.1).

3.1 See unit Starting and Stopping the R/3 System.

3.2 Use the process overview (Transaction SM50).

3.3 Choose: Tools --> CCMS --> Configuration --> Profile Maintenance --> Goto -->
Profile values --> Of a server.

BC360 Technical Core Competence 2-60

BC360

4.1 See Starting and Stopping the R/3 System.

4.2 From the CCMS menu, choose Configuration --> OP Modes and Servers --> Create,
and specify the name of the operation mode, a short description, and its type (in this
example, productive operation mode). Choose Save and repeat this procedure for
the second operation mode.

4.3 From the CCMS menu, choose Configuration --> OP Modes/Servers (Transaction
RZ04) --> Instances/OP Modes. To import all instance profiles at once, choose
Settings --> Based On Active Status --> New Instance --> Create.

4.4 Double click the row where the operation mode is specified. Choose Other OP
Mode and choose one of the operation modes defined above. Assign a work
process distribution to the operation mode and save. Repeat this procedure for the
next operation mode. Save the entire table.

5.1 From the CCMS menu, choose Configuration --> OP Mode Timetable --> Change.
Choose a 15-minute interval. Double click the beginning and the end of the time
interval and assign this interval to a defined operation mode. Repeat this procedure
until the whole timetable is filled. Save.

6.1 From the CCMS Control Panel, choose an operation mode. Double click one
instance and choose Control --> Switch OP Mode --> Selected Server.

BC360 Technical Core Competence 2-61

BC360

In the following, you will find excerpts from the Operation Manual, Chapter 4 Configuring R/3, in the section
Operation Modes.
To perform these exercises, complete the tables in the excerpts as follows:

1 The table under Tasks.

2 The tables under Configuration Documentation.

Define two or three suitable operation modes for your company and distribute the work processes available
in your system in the table Work Process Distribution. In the table Timetable for Normal Operation (24
Hour), enter the start and finish times for these operation modes.

Tasks

Task Frequency Menu Path (NT or R/3) Trans- Activity

<PRD <QAS <DEV action

Group
SID> SID> SID>

Defining an operation AR AR AR Tools → CCMS → Configuration → RZ04 <R3ADM>

mode OP-Modes/Servers.

Dynamic operation
mode switchover Tools → CCMS → Configuration →
OP-Modes/Servers → Operation
mode → Timetable. Select Normal
operation. Choose Change.
Manual operation mode Tools → CCMS →
switchover
Control/Monitoring → Control Panel
→ Edit → Choose OP mode. Select
an operation mode, then a server.
Control → Switch OP mode →
Selected server.

Scheduling Exception Tools → CCMS → Configuration →

Operation OP-Modes/Servers → Operation
mode → Timetable → Select
Exception operation. Choose Change.

BC360 Technical Core Competence 2-62

BC360

D: Daily W: Weekly M: Monthly Y: Yearly AR: As required

<R3ADM>: System administrator

Configuration Documentation

Work Process Distribution

An operation mode switchover can only change work process distribution, not the number of work processes in an
instance.

System Name of Active Dialog Batch Batch Spool Update Update Enqueue Total
Name Operation Mode A V1 V2 Work
Proc.

<PRDSID> Day 4 2 0 1 1 1 1 10

<PRDSID> Night 2 4 0 1 1 1 1 10

Timetable for Normal Operation (24 Hour)

Operation modes assigned in the timetable for normal operation are switched over daily. The complete 24 hour cycle
must be defined.

System Name Name of Active Operation Mode Start/End Time

<PRDSID> Day 06:00 - 20:00

<PRDSID> Night 20:00 - 06.00

BC360 Technical Core Competence 2-63

BC360

BC360 Technical Core Competence 2-64

BC360

No. True Question:

1 You can use the R/3 profile maintenance tool to maintain the:

1.1 System profiles of the R/3 application servers

1.2 System profiles of the R/3 application servers and the database profiles

1.3 User profiles in R/3 administration

2 R/3 System profiles on the application server are:

2.1 Created by the R/3 administrator at operating system level after

installation

2.2 Created at operating system level during R/3 System installation in

accordance with the installation parameters

2.3 Delivered pre-configured by SAP

3 After installation, SAP recommends that you:

3.1 Delete the profile files at operating system level

3.2 Import the profile files into the R/3 System using the R/3 profile
maintenance tool

3.3 Transfer the profile files at operating system level to the operating
system superuser

4 An R/3 instance profile defines:

4.1 Which services are made available by the application server

4.2 The size of the memory areas allocated by the application server

4.3 The default times for automatic online logon load balancing

5 Easy mode in profile maintenance:

5.1 Displays the estimated memory requirements for the configured R/3
instance

5.2 Gives you the option of excluding specific R/3 users from logging on to
specific application servers

5.3 Lets you determine which and how many R/3 work processes are
generated at operating system level at system startup

6 You can use the profile maintenance check functions to:

6.1 Compare the consistency of the R/3 application server names with the
name of the database server

BC360 Technical Core Competence 2-65

BC360

6.2 Check the consistency of an instance profile

6.3 Compare an active instance profile with its parent version in the
database

6.4 Check multiple instances, for example, for the number of enqueue
processes in the entire system

6.5 Check the number of Basis number range intervals

7 When an R/3 instance profile is activated:

7.1 The parent version of the profile is copied from the database as a file to
the profile directory at operating system level

7.2 The call parameter for the SAP program sapntstartb / sapstart is reset at
operating system level

7.3 The R/3 application server is restarted automatically with the new
configuration after a warning is sent to all active users and after waiting 5
minutes

8 Operation modes are useful because:

8.1 They define which background jobs should be released

8.2 They are one of the requirements for workload balancing

8.3 They optimize workload distribution by separating workgroups and using

separate job servers

8.4 The R/3 System does not need to be stopped in order to change the type
of specific work processes.

9 An operation mode defines:

9.1 Which instances are controlled

9.2 The number of application servers in the system

9.3 The work processes of an instance

10 Many dialog work processes are needed during daytime business

processing:

10.1 To allow user interactive processing

10.2 Because small volumes of data are inserted or updated in the database

10.3 For periodical processing

10.4 To get good response times

11 Many background work processes are needed during night business

BC360 Technical Core Competence 2-66

BC360

processing:

11.1 For list processing and tasks such as list balances

11.2 Because a large volume of data needs to be inserted/updated in the

database

11.3 For time-critical processing

12 The operation mode timetable for normal operation:

12.1 Defines which operation mode will be active at what time of day

12.2 Is required for CCMS monitoring

12.3 Is required for automatic operation mode switching

12.4 Defines the types of services offered by the SAP R/3 System as time-
dependent

13 The operation mode timetable in exceptional operation:

13.1 Defines which operation mode will be active at a particular time or a

particular day

13.2 Can only be defined for a whole day

13.3 Has a higher priority than the operation mode timetable for normal
operation

14 You can switch between operation modes:

14.1 Manually, using the CCMS

14.2 Automatically, using the operation mode timetable for normal or

exceptional operation

14.3 By shutting down one instance and starting the required instance

15 You can switch between operation modes manually:

15.1 By choosing CCMS −−> Control/Monitoring −−> System Monitor

15.2 By choosing CCMS −−> Control/Monitoring −−> Control Panel

15.3 By using the Job Scheduling Monitor

16 During operation mode switch:

16.1 The R/3 System does not shut down

16.2 The dialog work processes switch to background work processes or vice
versa, depending on the instance definition

BC360 Technical Core Competence 2-67

BC360

16.3 The instances profiles are changed

16.4 R/3 buffers are not refreshed

BC360 Technical Core Competence 2-68

BC360

No. True Question:

1 You can use the R/3 profile maintenance tool to maintain the:

1.1 X System profiles of the R/3 application servers

1.2 System profiles of the R/3 application servers and the database profiles

1.3 User profiles in R/3 administration

2 R/3 System profiles on the application server are:

2.1 Created by the R/3 administrator at operating system level after

installation

2.2 X Created at operating system level during R/3 System installation in

accordance with the installation parameters

2.3 Delivered pre-configured by SAP

3 After installation, SAP recommends that you:

3.1 Delete the profile files at operating system level

3.2 X Import the profile files into the R/3 System using the R/3 profile
maintenance tool

3.3 Transfer the profile files at operating system level to the operating
system superuser

4 An R/3 instance profile defines:

4.1 X Which services are made available by the application server

4.2 X The size of the memory areas allocated by the application server

4.3 The default times for automatic online logon load balancing

5 Easy mode in profile maintenance:

5.1 X Displays the estimated memory requirements for the configured R/3
instance

5.2 Gives you the option of excluding specific R/3 users from logging on to
specific application servers

5.3 X Lets you determine which and how many R/3 work processes are
generated at operating system level at system startup

6 You can use the profile maintenance check functions to:

6.1 Compare the consistency of the R/3 application server names with the
name of the database server

BC360 Technical Core Competence 2-69

BC360

6.2 X Check the consistency of an instance profile

6.3 X Compare an active instance profile with its parent version in the
database

6.4 X Check multiple instances, for example, for the number of enqueue
processes in the entire system

6.5 Check the number of Basis number range intervals

7 When an R/3 instance profile is activated:

7.1 X The parent version of the profile is copied from the database as a file to
the profile directory at operating system level

7.2 The call parameter for the SAP program sapntstartb / sapstart is reset at
operating system level

7.3 The R/3 application server is restarted automatically with the new
configuration after a warning is sent to all active users and after waiting 5
minutes

8 Operation modes are useful because:

8.1 They define which background jobs should be released

8.2 They are one of the requirements for workload balancing

8.3 They optimize workload distribution by separating workgroups and using

separate job servers

8.4 X The R/3 System does not need to be stopped in order to change the type
of specific work processes.

9 An operation mode defines:

9.1 X Which instances are controlled

9.2 The number of application servers in the system

9.3 X The work processes of an instance

10 Many dialog work processes are needed during daytime business

processing:

10.1 X To allow user interactive processing

10.2 X Because small volumes of data are inserted or updated in the database

10.3 For periodical processing

10.4 X To get good response times

11 Many background work processes are needed during night business

BC360 Technical Core Competence 2-70

BC360

processing:

11.1 X For list processing and tasks such as list balances

11.2 X Because a large volume of data needs to be inserted/updated in the

database

11.3 For time-critical processing

12 The operation mode timetable for normal operation:

12.1 X Defines which operation mode will be active at what time of day

12.2 X Is required for CCMS monitoring

12.3 X Is required for automatic operation mode switching

12.4 X Defines the types of services offered by the SAP R/3 System as time-
dependent

13 The operation mode timetable in exceptional operation:

13.1 X Defines which operation mode will be active at a particular time or a

particular day

13.2 Can only be defined for a whole day

13.3 X Has a higher priority than the operation mode timetable for normal
operation

14 You can switch between operation modes:

14.1 X Manually, using the CCMS

14.2 X Automatically, using the operation mode timetable for normal or

exceptional operation

14.3 By shutting down one instance and starting the required instance

15 You can switch between operation modes manually:

15.1 By choosing CCMS −−> Control/Monitoring −−> System Monitor

15.2 X By choosing CCMS −−> Control/Monitoring −−> Control Panel

15.3 By using the Job Scheduling Monitor

16 During operation mode switch:

16.1 X The R/3 System does not shut down

16.2 X The dialog work processes switch to background work processes or vice
versa, depending on the instance definition

BC360 Technical Core Competence 2-71

BC360

16.3 The instances profiles are changed

16.4 X R/3 buffers are not refreshed

BC360 Technical Core Competence 2-72

BC360

CCMS Configuration

Further Docum entation

R/3 Basis Knowledge

Product: System
M anagement
R/3 Online Docum entation:
BC Com puting Center
M anagement System
R/3 Notes in the Online
Service System (OSS), under
components:
BC-C CM-CNF-OPM
BC-C CM-CNF-PFL

 SAP AG

Database Adm inistration

R/3
R/3 Basis
Basis
Administration
Administration
4.0
4.0

Database Administration
and Backups

 SAP AG

BC360 Technical Core Competence 2-73

BC360

BC360 Technical Core Competence 2-74

BC360

Database Adm inistration

Database Adm inistration and Backups

Contents:
Database fundamentals
Backup strategies

Objectives:
At the end of this unit you will be able to :
Set up the database for performing backups
Schedule and perform database backups
Schedule and perform offline redo log file backups
Verify the backups
Verify the database structure on disk
Recognize and solve error situations
R

 SAP AG

Once you have completed this unit, you will be able to:
Define an effective and secure backup strategy
Schedule and perform database backups
Schedule and perform offline redo log file backups
Verify the backups
Verify the database structure

BC360 Technical Core Competence 2-75

BC360

Database Adm inistration

Course Roadmap Database

Administration
and Backups

Introduction CCM S
Configuration DBA: Daily Check
Procedures

System
M onitoring
Starting and
Stopping R/3
Background
Processing
R/3
Authorization

Data Archiving
SAP O nline in R/3
Service System

Software
Logistics
Installation
Check Spool and Print
R

 SAP AG

BC360 Technical Core Competence 2-76

BC360

Database Adm inistration

ORACLE: Overview R/3 work

processes
RDBMS Processes 1:1

Shadow
Shadow
Oracle listener process

Shadow
DBWR
LGWR

PMON
SMON
ARCH
CKPT
Shared Oracle processes
M emory area SGA Database buffer pool Configurable
(init<SID>.ora)
Shared pool
Shared SQL Area Row cache
Redo log buffer

Database files

Profile
Control Online redo Offline redo
R

files Data files log files log files

 SAP AG

When an Oracle database instance is started several processes are created.

The listener process is responsible for communication with Oracle over the network.
For each database session a dedicated shadow process is started.
Shared processes perform tasks required for the functioning of the Oracle database management system
Database data is stored in 8KB blocks in data files on disk. To accelerate read and write access to data, these
data blocks are cached in the database buffer pool in main memory.
Modifications to database data are logged in the online redo log files. This procedure ensures data security. To
ensure fail-safe database operation, without using additional operating system utilities, the control files and the
online redo log files of the database system should be mirrored.
The Oracle database management system holds the executable SQL statements in the Shared SQL Area, which is
part of the shared pool, only once for all processes.
Each R/3 work process:
Connects to the database as one database user, SAPR3
Handles requests from the different R/3 System users
Communicates with a corresponding shadow process on the database.
R/3 System users do not have a database system user.

BC360 Technical Core Competence 2-77

BC360

Database Adm inistration

ORACLE: Starting and Stopping the Database

Oracle processes:
Profile

DBWR
Nom ount

LGWR

PMON
SMON
ARCH
CKPT
Mount Control files
Oracle listener process

Database buffer pool SGA

Open

Data files Shared pool

Online redo log files Redo log buffer

Offline redo log files

 SAP AG

An Oracle database is started in three phases:

In the No mount phase, the database instance is built up. Operating system resources are allocated using
configuration information stored in the profile init<SID>.ora.
In the Mount phase, the control files of the database are evaluated. The system reads the information about
the file structure of the database. No data files are opened yet.
In the Open phase, all files in the database system are opened. If required, an instance recovery is performed
immediately after opening the database. Pending transactions on the database are ended, according to the
transaction logic.
The system administrator can shut down the database using one of three commands:
SHUTDOWN NORMAL: All logged on users must log off. The database is closed systematically; all files
are closed, the database is dismounted, and the instance is shut down. The database is consistent after
shutdown.
SHUTDOWN IMMEDIATE: Only the current commands are executed. PMON ends all sessions and
performs a rollback of the open transactions. The database is then closed systematically (as for a normal
shutdown). The database is consistent after shutdown.
Caution: DBWR and ARCH may require up to 1 hour post-processing time.
SHUTDOWN ABORT: Emergency database shutdown. Users are not logged off, and a rollback of the open
transactions is not performed. The database is not consistent after shutdown. An instance recovery is
automatically performed at the next database startup.

BC360 Technical Core Competence 2-78

BC360

Database Adm inistration

ORACLE: Writing Data and Log Files

Process processes and
Profile mem ory
m emory

Control files Database buffer pool

CKPT
DBW R

Data files Redo log buffer

LGW R
Online redo log files
Profile init<SID>.ora
log_archive_start = TRUE
ARCH log_archive_dest = ?/saparch/

Offline redo log files ARCHIVELOG M ODE: TRUE

 SAP AG

An Oracle database system has three processes that write information from the Shared Global Area (SGA) to the
appropriate files:
During a checkpoint, the Database writer (DBWR) asynchronously writes the changed blocks from the SGA
to the database data files.
To speed up the writing of checkpoints, the Checkpoint (CKPT) process is started.
The Logwriter (LGWR) synchronously writes the change log from the SGA redo log buffer to the currently
active online redo log file.
In a production database system, the database must always run in ARCHIVELOG mode and have the Archiver
process (ARCH) started (init<SID>.ora: log_archive_start = TRUE). ARCH archives a completed online redo
log file into an offline redo log file in the archive directory.
ARCH determines the archive directory from the init<SID>.ora parameter log_archive_dest (default:
?/saparch/) and determines the file name from the parameter log_archive_format.
Once the offline redo log file has been successfully created, the corresponding online redo log file is released to
be overwritten with new log information.
If there is no freespace available in the archive directory the Archiver will not archive the file. The database will
be "stuck" after a corresponding number of redo log switches. Database changes cannot be commited as long as
this archiver stuck situation persists.

BC360 Technical Core Competence 2-79

BC360

Database Adm inistration

R/3 Naming Conventions

Tablespace PSAP<TS_name>
PSAPBTABD Logical
nam e layer
Prefix Abbreviation Extension
PSAP <TS_name> D (data) or I (index) Directory <TS_nam e>_1 <TS_nam e>_2 Physical
nam es btabd_1 btabd_2 layer

Files <TS_nam e>.data1 <TS_nam e>.data2

nam es btabd.data1 btabd.data2

Prefix Tablespace nam e Ext. M eaning Used by

SYSTEM Oracle DDIC O racle RDBMS
PSAP ROLL Rollback segments O racle RDBMS
PSAP TEMP Sort processes O racle RDBMS
PSAP EL<Release> D or I Development environment loads R/3 Basis
PSAP ES<Release> D or I Development environment sources R/3 Basis
PSAP LOAD D or I Screen and report loads (ABAP) R/3 Basis
PSAP SOURCE D or I Screen and report sources (ABAP) R/3 Basis
PSAP DDIC D or I ABAP Dictionary R/3 Basis
PSAP PROT D or I Log-like tables (for example, spool) R/3 Applications
PSAP CLU D or I Cluster tables R/3 Applications
PSAP POO L D or I Pool tables (for example, ATAB) R/3 Applications
PSAP STAB D or I Master data and transparent tables R/3 Applications
PSAP BTAB D or I Transaction data, transparent tables R/3 Applications
R

PSAP DOCU D or I Documentation, SAPscript, SAPfind R/3 Applications

PSAP USER1 D or I Customer tables R/3 Applications
 SAP AG

The Oracle database uses tablespaces. From a logical point of view, a tablespace is a container for database
objects, such as tables and indexes. On disk, a tablespace consists of one or more data files. The capacity of a
tablespace can be increased by adding files to it.
The R/3 naming convention for tablespace names is defined as follows: PSAP<tablespace_name><extension>.
The abbreviations in the tablespace name are part of the directory name and file name of each data file.
Directories and data files are numbered.
The objects located in the tablespaces SYSTEM, PSAPROLL and PSAPTEMP belong either to the Oracle
database users SYS or SYSTEM. Do not create any objects owned by other users in these tablespaces.
The objects located in the other tablespaces belong to the SAP R/3 database user SAPR3.
NOTE: The R/3 System and SAP tools, such as SAPDBA, require that the naming conventions be observed. The
installed system constitutes a logical unit, which should not be changed.

BC360 Technical Core Competence 2-80

BC360

Database Adm inistration

Oracle Directory Structure in R/3

Directory Contains File name exam ples
dbs SAP and O racle profiles, init<SID>.ora, init<SID>.dba, init<SID>.sap,

bin Oracle executables

saptrace Background (Oracle alert file)

usertrace
sapdata1 Data files /btabd1/btabd.data1, system.data1,
. ctrl<SID>.dbf, /btabi1/btabi.data1
. ...
sapdata<n>

sapbackup BRBACKUP, BRRESTORE logs

saparch BRARCHIVE logs, O racle archive dir ctrl<SID>.dbf Profile init<SID>.ora
log_archive_format = % t_% s
sapcheck SAPDBA logs (-next, -check, -analyze)
sapreorg SAPDBA (default),
default compression directory
origlogA Online redo log files log_tg101_m1.dbf, log_tg103_m1.dbf
origlogB Online redo log files log_tg102_m1.dbf, log_tg104_m1.dbf
m irrlogA Online redo log files log_tg101_m2.dbf, log_tg103_m2.dbf
m irrlogB Online redo log files log_tg102_m2.dbf, log_tg104_m2.dbf
R

 SAP AG

Directory and file names are standardized in the R/3 environment. We recommend that you use the following
standards:
Tablespace files reside in the sapdata<n> directories.
The online redo log files reside in the origlog and mirrlog directories.
The offline redo log files are written to the saparch directory.
There should be at least 3 copies of the Oracle control file on different disks.
The profile init<SID>.ora configures the Oracle instance, and resides in directory database.
The profile init<SID>.sap configures the backup tools brbackup and brarchive, and resides in directory
database.
The profile init<SID>.dba configures the sapdba tool, and resides in directory dbs.
Trace files written by the Oracle shadow processes are written to the directory saptrace/usertrace
The Oracle alert file is written to directory saptrace/background.
During reorganization, export datasets are written to directory sapreorg.
The directories saparch, sapcheck, sapreorg, and sapbackup are used by the SAP database tools.

BC360 Technical Core Competence 2-81

BC360

Database Adm inistration

Database Adm inistration Calendar

Day 6am 12pm 6pm 12 am

Backup the
databasebackup
Database and
offline redo
Offline
log redo
fileslog file backup
Daily m onitoring

Storage management

Alert handling

Optim izer statistics

Daily tasks Regular tasks Scheduling operations

 SAP AG

The daily backup tasks of a system administrator include:

Backing up the entire database
Backing up the offline redo log files
Monitoring the success of the backups

BC360 Technical Core Competence 2-82

BC360

Database Adm inistration

The Importance of Database Backups

Physical
Physical errors
errors
(Such as a hardware failure)

External
External factors
factors Logical
Logical errors
errors
(Such as fire or water ( Such as a deleted table)
dam age)
DELETE MARA

Data
loss

To prevent data loss, a valid backup is necessary R

 SAP AG

External factors, physical errors, and logical errors can all lead to data loss and system downtime.
An effective backup strategy and recovery plan is essential in minimizing system downtime and data loss.
To ensure the availability of your R/3 System, the backup strategy developed by your database administrator
must be carefully tested.

BC360 Technical Core Competence 2-83

BC360

Database Adm inistration

Database and Offline Redo Log File Backups

Data files

Online redo log files

Database
Database backup
backup
Control file

Profiles

Offline redo log files

O
Offline
ffline redo
redo log
log
file
file backup
backup

 SAP AG

Each database management system stores data in suitable structures on disk and writes data modifications in the
database log. For the Oracle RDBMS:
The data is stored in the data files of the tablespaces.
The log information is recorded in the currently active online redo log file.
Administration data is stored in the parameter and control files.
The data files, the online redo log files, profiles and a control file are backed up during a database backup.
When the currently active online redo log file is full, Oracle automatically writes to the next online redo log file.
The Oracle archiver copies the completed online redo log file to the archive directory. The copy is called the
offline redo log file. The offline redo log files are backed up during an offline redo log file backup.
Both database and offline redo log file backups are necessary to ensure that the database can be recovered to a
point in time as close as possible to when data loss occurred. To perform a restore, use a backup of the data files
(or a part of the backup) for the starting point .
The log information, which was generated during and after the database backup, is used to recover all
modifications, which subsequently have been applied to the data. This log information is usually retrieved from
the offline redo log file backups.

BC360 Technical Core Competence 2-84

BC360

Database Adm inistration

Preventing and Handling Errors

Logical
Physical
data check:
data check:
Verify database
Verify backup
consistency
on tape

O RA-1578:
Oracle
data block
corrupted

Oracle data files

Database
Database backup
backup

 SAP AG

Your backup strategy should include verifying both the data to be backed up as well as the database backups.
Perform a logical data check to verify the consistency of the Oracle database.
Corrupt Oracle blocks (error ORA-1578) can appear in your R/3 database as a result of operating system or
hardware errors. Corrupt Oracle blocks may make a backup unusable.
The existence of these blocks only becomes evident during the next read access attempt to a table within the
database. Since this particular access attempt may not occur often and corrupt Oracle blocks are not
recognized during a database backup, these corrupt blocks might remain undetected in your system for a
long time.
Therefore, you should perform a logical data check at regular intervals. For optimal performance, perform
this check during periods of low system activity, such as on weekends.
Perform a physical data check to verify the tapes used for a database backup. To check the physical correctness
of the data transferred, the tapes should be read after a successful backup.

BC360 Technical Core Competence 2-85

BC360

Database Adm inistration

Offline Backups
SAPGUI
.... .... ....
______________________
R/3 instance 00 ______________________
______________________
______________________

SPO WP
BTC WP

BTC WP
DIA WP
DIA WP
Dia WP

Data files

Reconnect:
rsdb/reco_trials = 3
Oracle processes Online redo log files
Listener
DBWR
LGWR

PMON
SMON
ARCH
CKPT

O ffline backup
e d Control file
a rt
t pool st
Database buffer
o Profiles
N
SGA

Shared pool Offline redo log files

O ffline redo log
Redo log buffer file backup
R

 SAP AG

When an offline backup is performed, the database is shut down and remains unavailable while the backup is
running. Because the Oracle data files remain unchanged, a full offline backup is consistent.
The following files are backed up when an offline backup is performed:
The data files of all tablespaces belonging to the database
The online redo log files
The control file
The profiles init<SID>.ora, init<SID>.sap, and init<SID>.dba
You must back up the offline redo log files when the offline backup is finished.
Although the R/3 System is set up to remain online throughout the backup (reconnect parameters in the R/3
instance profile), the R/3 System users cannot use R/3 until the database is available.

BC360 Technical Core Competence 2-86

BC360

Database Adm inistration

Online Backups
SAPGUI
.... .... ....
______________________
R/3 instance 00 ______________________
______________________
______________________

SPO WP
BTC WP

BTC WP
DIA WP
DIA WP
Dia WP ______________________

Data files

Oracle processes

Shadow
Shadow
Shadow
Shadow
Shadow
Shadow
Listener
DBWR
LGWR

PMON
SMON
ARCH
CKPT

N ot Online redo log files

bac
k ed
up
O nline backup
Control file
Database buffer pool

Profiles
SGA

Shared pool

Redo log buffer Offline redo log files

O ffline redo log
file backup
R

 SAP AG

During an online backup, the Oracle database and the R/3 System remain available. Online backups cause a
small reduction in system performance.
The following files are backed up when an online backup is performed:
The data files of all tablespaces belonging to the Oracle database
The control file
The profiles init<SID>.ora, init<SID>.sap, and init<SID>.dba
CAUTION:
Online backups are not consistent because the data files are updated concurrently. An online backup can
only be consistent and usable in conjunction with the log information written during the online backup.
After an online backup is finished, the SAP tool BRBACKUP switches to a new online redo log file and the
Oracle archiver copies the previously active online redo log file to the directory saparch. The entire log
information generated during the online backup is contained in the offline redo log files. Back up the offline
redo log files when the online backup has finished.
You do not have to back up the online redo log files when an online backup is performed.

BC360 Technical Core Competence 2-87

BC360

Database Adm inistration

Offline Redo Log File Backups

.../saparch
Online redo log files Offline redo log files
Oracle archiver

init<SID>.ora BRARCHIVE
log_archive_start = TRUE
Log switch
log_archive_dest = .../saparch/
Offline redo log
file backup

Com plete recovery not possible

Complete
Lost
Recoverable

Missing offline
O ffline redo log files available
redo log file

Today

Online Log O ffline Log Online Log Log Error

backup backup backup backup backup backup backup R

 SAP AG

Offline redo log files are copies of online redo log files which have been saved by the Oracle archiver to
directory saparch. Online redo log files are cyclically overwritten.
Log information is constantly generated when database data is modified. Therefore, disk space in the archive
directory must be continuously released for new log files. When the archiver is unable to write to the directory
specified by the parameter log_archive_dest, Oracle reports error 257: Archiver is stuck or error 255: Error
archiving log, and the database becomes stuck. An error message is then written to the Oracle trace files.
If, in the case of a restore, only one of the required offline redo log files does not have a valid backup, data loss
occurs. The offline redo logs files must not be deleted from the archive directory without being backed up to
tape. For security reasons, back up 2 copies of each offline redo log file on separate tapes.
NOTE. In the case of a database failure, you may be unable to recover all the database changes not contained in
the latest redo log file backup.
Remember: An online backup is useless without the log information that was generated during the database
backup.

BC360 Technical Core Competence 2-88

BC360

Database Adm inistration

Backup Cycle Recommendations

Verify the database

Verify the backup Verify the backup
Offline Online
Offline redo log
file backup (x2)

28 days Online

Offline redo log

Additional file backup (x2)

 SAP AG

SAP recommends a backup cycle of 4 weeks.

A pool of tapes for database and offline redo log file backups is required. Ensure that enough tapes are provided
in each tape pool to span the entire backup cycle. We recommend having 30% more tapes than required. Backup
tapes can be reused at the end of a backup cycle (after 28 days).
Perform a full online backup each workday. Perform a full offline backup at least once in the backup cycle.
You must back up the offline redo log files each workday, as well as after every online and offline backup.
Ensure that you back up the offline redo log files twice, on separate tapes, before they are deleted.
To verify a backup, you must check the database for logical errors and the database backups for physical errors.
You must perform this backup verification at least once in the backup cycle, however, you should try to perform
it once a week.
Remove the last verified full offline backup of each cycle from the tape pool, and keep this backup in long-term
storage. Replace the tapes, and initialize new ones.
Perform additional backups after each database structure modification or a system upgrade. Place these
additional backups in long-term storage.

BC360 Technical Core Competence 2-89

BC360

Database Adm inistration

SAP Backup Tools CCMS P lanning Calend ar

Planning G oto Listing Help System
M ON TUE
T UE W
WEED T HU
THU FRI S AT
SAT SUN

M ON TUE
T UE W
WEED T HU
THU FRI S AT
SAT SUN

Data files

Online redo log files

BRBACKUP

Database
Database backup
backup
Control file

Profiles
BRARCHIVE
Offline redo log files

O
Offline
ffline redo
redo log
log
file
file backup
backup
R

 SAP AG

Database backups are performed by the SAP tool BRBACKUP.

Offline redo log file backups are performed by the SAP tool BRARCHIVE.
There are three ways to call these tools:
Using the DBA Planning Calendar (Transaction DB13)
Using the SAPDBA at operating system level
Directly, at the operating system level
SAP recommends the following procedure:
Schedule all regular backups with the DBA Planning Calendar (Transaction DB13)
Perform additional backups with the SAPDBA
All the steps of a backup are logged to operating system files and in database tables.

BC360 Technical Core Competence 2-90

BC360

The tape initialization procedure should be performed as follows:

Set the init<SID>.sap parameters volume_backup and volume_archive. In this example:
⌧ volume_backup=(<SID>B01, <SID>B02, <SID>B03, <SID>B04)
⌧ volume_archive=(<SID>A01, <SID>A02, <SID>A03, <SID>A04)
To initialize the tape pools, use SAPDBA or BRBACKUP and BRARCHIVE with call option -i force
(where -i = initialize and force = do not evaluate tape label).
In this example, tape labels <SID>B01, <SID>B02, <SID>B03, <SID>B04 and <SID>A01, <SID>A02,
<SID>A03, <SID>A04 are initialized.
During initialization, the label .tape.hdr0 is written as the first file on every tape. This label is always read and
checked by BRBACKUP and BRARCHIVE. BRBACKUP and BRARCHIVE record the tape usage in the tape
label, the backup logs, and in the database.
To overwrite the default settings defined in volume_backup or volume_archive, use BRBACKUP and
BRARCHIVE with call option -v/-volume.
Depending on your backup strategy, a sufficient number of tapes should be initialized. The number of tapes
required depends on the size of the database, the size of your tapes, the compression factor and the amount of log
information generated. Add 30% freespace reserve to the required tape capacity.

BC360 Technical Core Competence 2-93

BC360

Database Adm inistration

Compressing Data
Use SAPDBA to
determine the compression
ratio once per cycle
<SID>B01

<SID>B02

<SID>B03

<SID>B04

init<SID>.sap
....
....
.... com press = hardw are
....
? ?
??? <SID>B01

 SAP AG

Use the init<SID>.sap parameter compress to choose the mode of compression. If your tape device supports
hardware compression, set this partameter to hardware. You can also specify yes for software compression or no
for no compression.
When using hardware or software compression, data on tape requires less storage space. The compression factor
indicates the degree of compression possible for the backup data.
Use SAPDBA to determine the compression ratio with which your data can be backed up.
This factor depends on the fill level of the database files to be backed up. Because of the changing fill level, you
should redetermine the compression rate frequently (at least once per backup cycle).

BC360 Technical Core Competence 2-94

BC360

Database Adm inistration

Profile Parameters for Database Backup

backup_ mode = all

init<SID>.sap backup_ type = online [offline]
....
....
.... volume_backup = (<SID>B01, <SID>B02, ...)
....
? ?
tape_ size = 70000M
???
?
compress
com press = hardware

To edit init<SID>.sap,
init<SID>.sap, use a standard text editor
 SAP AG

Use the following init<SID>.sap parameters to set up program BRBACKUP:

Set parameter backup_mode to all in order to perform a complete database backup
backup_type defines whether the backup is online or offline
tape_size defines the physical tape size for tapes used by BRBACKUP. Specify the size of the smallest tape
in your tape pool (in MB). For example, specify 70000M for a 70GB tape. NOTE: The value specified for
this parameter must be equal to the amount of uncompressed data the tape can hold.
When data is backed up sequentially to several tapes and only one tape device is available, BRBACKUP
requests the tapes in the order defined by the parameter volume_backup.
Both rewind and no-rewind tape drivers are required by the SAP backup tools. A no-rewind driver must be
assigned to parameter tape_address, and a rewind driver to parameter tape_address_rew.

BC360 Technical Core Competence 2-95

BC360

Database Adm inistration

Profile Parameters for Offline Redo Log Backup

archive_function = copy_delete_save
init<SID>.sap
volume_archive = (<SID>A01, <SID>A02, ...)
.... tape_size_arch = 6000M
....
? ? ....
....
???
?

Use copy_delete_save to:

1) Back up the offline redo log files that have already been backed up once
2) Delete these offline redo log files from directory saparch
3) Back up the offline redo log files that have not yet been backed up

To edit init<SID>.sap,
init<SID>.sap, use a standard text editor
 SAP AG

Use the following init<SID>.sap parameters to set up program BRARCHIVE:

Set parameter archive_function to - cds (copy_delete_save). This ensures that two copies of one offline redo
log file are backed up to different tapes.
Option -cds (copy_delete_save):
⌧ Creates a second backup of the oldest offline redo log files already backed up once
⌧ Deletes the offline redo log files that have been backed up twice from the archive directory, in order to
free disk space
⌧ Backs up all new offline redo log files for the first time
tape_size_arch defines the physical tape size for tapes used by BRARCHIVE. Specify the size of the
smallest tape in your tape pool (in MB). For example, specify 6000M for a 6GB tape.
tape_address_arch and tape_address_rew_arch specifiy the drivers of the tape devices to be used by
BRARCHIVE to perform the offline redo log file backup. If they are not defined, BRARCHIVE uses
parameters tape_address and tape_address_rew to determine the drivers.

BC360 Technical Core Competence 2-96

BC360

Database Adm inistration

Scheduling Database Backups

CCMS Planning Calendar
P lanning Goto Listing Help System

Volumes needed
MO
ONN
- TUE
CreateW EDa newTHU
action FRI
for TueSAT05
S AT S UN
SUN

SAPDBA ! Verify
Data files
backup option ! "
query only R

 SAP AG

Use the DBA Planning Calendar (Transaction DB13) to schedule database and offline redo log file backups.
Online as well as offline backups can be scheduled.
At least once in the backup cycle you must verify your full offline backup. To perform a physical and logical
verification of the data backed up, use the Verify option.
The names of the tapes to be used for the backup are determined from the parameters volume_backup (for
program BRBACKUP) and volume_archiv (for program BRARCHIVE). You can overwrite the default volume
names in the dialog box Volumes to use.
To verify the number and names of the tapes required for a backup, choose Volumes needed from the DBA
Planning Calendar (Transaction DB13) or use the SAPDBA (option query only). The number of tapes calculated
is based on the size of the database, the parameter tape_size, and the compression factor.
Log files are written by BRBACKUP (default directory sapbackup) and by BRARCHIVE (default directory
saparch). These log files provide information about the type and state of activities performed. The activities of
BRBACKUP and BRARCHIVE are also loggged in the database.

BC360 Technical Core Competence 2-97

BC360

Database Adm inistration

Daily Monitoring: Database Backups

Possible backup errors:
• Tape defect Check the success of the
• W rong tape label database and
offline redo log file backups
• Tape too sm all
• Corrupted blocks CCMS Planning Calendar
P lanning G oto Listing Help System

M
MOON TUE WE D
W ED THU FRI S AT S UN
Full Full
Schedule a new On line
O nline O ffline
Offline

database or log file backup M

MOON TUE WE D
W ED THU FRI S AT S UN

CCM S Database Backu p Logs

P lanning G oto
M
MOO NListingTUE
Help System
WE D
W ED THU FRI S AT S UN
CCM S Planning Calendar
P lanning
M on TueGoto WListing
ed Thu Help FriSystem
Sat S un Recovery
Recovery report
report Refresh
Refresh
Tue

M ON TUE W
WEED THU FRI SAT SUN
S UN Last M
MOO N database
TUE backup
WE D
W ED THU FRI S AT S UN
MFull
Last successful
successful database backup
on TueFullW ed Thu Fri Sat S un

Online Offline
O ffline
O
Overview
verview of
of all
all database
database backup
backup logs
logs
M on Tue
M ON TUEW ed W
WEThu
E D Fri
THU Sat
FRI S un SAT SUN
S UN

M on Tue W ed Thu Fri Sat S un S

Status
tatus of
of log
log directory
directory

M ON TUE W
WEED THU FRI SAT SUN
S UN
S
Status
tatus of
of most
most recent
recent redo
redo logs
logs

O
Overview
verview of
of all
all recent
recent redo
redo log
log backup
backup logs
logs
M ON TUE W
WEED THU FRI SAT SUN
S UN

 SAP AG

The Backup Log Monitor (Transaction DB12) display information about:

The database and the offline redo log file backups
The log files written by BRBACKUP and BRARCHIVE
The last unsuccessful backup
The last successful backup
All the backup actions
The state of the archive directory
How your database and offline redo log file backups could be used for a recovery
The DBA Planning Calendar (Transaction DB13) displays the status of all the activities that were performed.

BC360 Technical Core Competence 2-98

BC360

Database Adm inistration

Summary: Setting up your Backup Strategy

Provide tapes for backups
Verify backups
Check data volume changes
Check compression
com pression ratio changes
Cycle Length of backup cycle Check redo log volume changes
Data volume Verify the database
Compression ratio
Redo log volume
CCM S Database Backup Logs
CCMS P lann ing Calendar P lanning Goto Listing Help System
init<SID>.sap P lanning G oto Listing Help System CCM S Planning Calendar
P lanning Goto Listing Help System
M ON TUE W EDE D THU FRI S AT SUN
S UN M ON
O N TUE WE D THU
W ED T HU FRI SAT
S AT S UN
SUN
....
.... M ON TUE W ED
E D THU FRI S AT SUN
S UN M ON
O N TUE WE D THU
W ED T HU FRI SAT
S AT S UN
SUN
....
.... M ON TUE W ED
E D THU FRI S AT SUN
S UN M ON
O N TUE WE D THU
W ED T HU FRI SAT
S AT S UN
SUN
? ?
M ON TUE W ED
E D THU FRI S AT SUN
S UN M ON
O N TUE WE D THU
W ED T HU FRI SAT
S AT S UN
SUN
???
?

Define strategy Initialize backup tools Schedule regular backups Perform and m onitor backups

 SAP AG

To set the backup parameters in the profile init<SID>.sap you must:

Determine the backup cycle
Estimate the volume of data to be backed up (use the sizing information provided by your hardware partner)
Estimate the volume of the offline redo log files to be backed up
Determine the compression factor, using either SAPDBA or BRBACKUP
Determine the number of tapes required (to allow for database growth, add 30%)
Initialize the tapes to be used for your backups.
Schedule your regular backups using the DBA Planning Calendar (Transaction DB13).
Perform and monitor the backups, which includes:
Providing the tapes required for the backups
Monitoring and verifying the success of the backups
Checking for changes in the volume of data to be backed up
Re-checking the compression rate (at least once per backup cycle)
Verifying the database logically (at least once per backup cycle)
Replacing and initializing tapes used for long-term backup storage

BC360 Technical Core Competence 2-99

BC360

Database Adm inistration

Using the One Tape Strategy

CCM S P lanning Calendar
P lanning Goto Listing Help System
MO
M ONN T UE W ED THU FRI S AT S
TUE UN
SUN

Log file MO N T
M ON UE W ED THU FRI S AT S
TUE UN
SUN

.... MO N T
M ON UE W ED THU FRI S AT S
TUE UN
SUN
....
....
Data files MO N T
M ON UE W ED THU FRI S AT S
TUE UN
SUN

brbackup ... -a <options>

• Determ
Determines the
the tapes
tapes required
• Backs
Backs up
up the
the database
Online redo log files • Calls
Calls BRARCHIVE Volume_backup

brarchive <options>
Control file
• Backs up the offline redo log files

Profiles Log file

....
....
Offline redo log files ....

 SAP AG

As of R/3 Release 4.0, you can back up the database and offline redo log files to the same tape by:
Using the CCMS DBA Planning Calendar (Transaction DB13)
Running BRBACKUP with the call option -a <BRARCHIVE options> or alternatively Running
BRARCHIVE with the call option -b <BRBACKUP options>
Using the SAPDBA
There are three steps in the one tape strategy:
1 BRBACKUP connects to the database to determine the tapes required for the backup
2 When the database backup is finished, BRBACKUP calls BRARCHIVE
3 BRARCHIVE then backs up the offline redo log files, without prompting for a new tape
Only tapes defined with the parameter volume_backup are considered for both the database and the offline redo
log file backups. However, you must also have an emergency tape pool for BRARCHIVE. BRBACKUP cannot
resolve an archiver stuck situation. If an archiver stuck stiuation occurs, call BRARCHIVE and perform an
offline redo log file backup.
Backing up both the database and the offline redo log files to the same tape ensures that:
Less tapes are required
Only one backup run for both backups is required
Less administrative tasks need to be performed

BC360 Technical Core Competence 2-100

BC360

Database Adm inistration

Summary of this Unit

Now you are able to:

Define an effective backup strategy

Perform database backups
Perform offline redo log file backups
Verify the database backups

 SAP AG

Now you are able to :

Define an effective backup strategy
Schedule backups
Perform database backups
Perform offline redo log file backups
Verify the backups
Remember: An effective backup strategy is essential in minimizing system downtime and data loss.

BC360 Technical Core Competence 2-101

BC360

Database Adm inistration

Unit Actions

Do the exercises

? Answer the questions

Fill in the blanks

Solutions for the exercises

Answer the questions

 SAP AG

BC360 Technical Core Competence 2-102

BC360

No. Exercise

1) Preparations

1.1 For an online backup, you must ensure that the database is in ARCHIVELOG mode.
Activate this mode, if it has not already been done.

1.2 Set the parameters so that the default backup is a full online database backup
without compression to disk and the offline redo log files are backed up once and
not subsequently deleted.

2) Database backup using CCMS

2.1 Use the DBA Planning Calendar to schedule a partial online backup of tablespace
PSAPUSER1D to start in 5 minutes.

2.2 In which directory is the backup performed, and how much disk space is required?

2.3 After the backup has been performed, use the log files to check whether the backup
was successful.

3) Optional: Database backup using SAPDBA

3.1 Use SAPDBA to perform a partial online backup of tablespace PSAPUSER1D.

3.2 After the backup has been performed, use the log files to check whether the backup
was successful.

4) Offline Redo log file backup using CCMS

4.1 Use the DBA Planning Calendar to schedule an offline redo log file backup to start
in 5 minutes.

4.2 In which directory is the backup performed, and how much disk space is required?

4.3 After the backup has been performed, use the logs to check whether the backup
was successful.

5) Optional: Offline Redo log file backup using SAPDBA

5.1 Use SAPDBA to perform an offline redo log file backup.

5.2 After the backup has been performed, use the log files to check whether the backup
was successful.

BC360 Technical Core Competence 2-103

BC360

No. Solution

1.1 Stop the R/3 System. From the SAPDBA, choose f – Archive mode. To switch the
mode, choose a – Toggle database log mode.

1.2 Set the following parameters in profile init<SID>.sap:

backup_type = online
backup_dev_type = disk
compress = no
archive_function = save

2.1 Double-click today's date and the appropriate starting time for the backup.
Choose Partial online database backup → Continue.
To select the tablespace PSAPUSER1D, use P-, P--, P+ or P++ to scroll down the
screen.
Because this is a backup to disk, you do not need to enter any Volumes.
Choose Continue again.
To verify the back up, select Verify in the dialog box displayed.
To save your scheduled backup, choose Continue.

2.2 To display a list of scheduled backups, double-click today's date in the DBA
Planning Calendar. Place the cursor on the backup scheduled in 2.1, and choose
Volumes needed.

2.3 Place the cursor on the backup that you scheduled for exercise 2.1, and choose
Action logs.
To display the log file for BRBACKUP, choose Oper. system log.

3.1 Start SAPDBA and choose h - Backup database.

To back up tablespace PSAPUSER1D, choose d – Objects for backup.
To start the backup, choose S – Start BRBACKUP.

3.2 From the initial SAPDBA screen, choose l – Show/Cleanup → a – Show log files /
Profiles → e – BRBACKUP log files. Select the appropriate log file.

4.1 Double-click today's date and the appropriate starting time for the backup.
Choose Archive redo log files → Continue.
Because this is a backup to disk, you do not need to enter any Volumes.
Choose Continue again.
In the dialog box displayed, select –s (this is the option for BRARCHIVE).
To verify the back up, select Verify in the dialog box displayed.
To save your scheduled backup, choose Continue.

BC360 Technical Core Competence 2-104

BC360

4.2 To display a list of scheduled backups, double-click today's date in the DBA
Planning Calendar. Place the cursor on the backup scheduled in 4.1, and choose
Volumes needed.

4.3 Place the cursor on the backup that you scheduled for exercise 4.1, and choose
Action logs.
To display the log file for BRBACKUP, choose Oper. system log.

5.1 Start SAPDBA and choose i - Backup archive logs. If you have not already done so,
choose a single backup of the offline redo log files. Choose a – Archive function → a
– Save archive logs → q – Return.
To start the backup, choose s – Start BRARCHIVE.

5.2 From the initial SAPDBA screen, choose l – Show/Cleanup → a – Show log files /
Profiles → f – BRARCHIVE log files. Select the appropriate log file.

BC360 Technical Core Competence 2-105

BC360

In the following, you will find excerpts from the Operation Manual, Chapter 8 Performing Backup, in the section
Backup on Database Level.
To perform these exercises, complete the tables in the excerpts as follows:

1 The table under Tasks.

2 The tables under Configuration Documentation.

In your system, find out which backups are scheduled and use this information to complete the tables.

Tasks

Task Frequency Menu Path (NT or R/3) Trans- Activity

<PRD <QAS <DEV action Group

SID> SID> SID>

Creating a backup AR AR AR Tools → CCMS → DB- DB13 <DBADM>

strategy Administration → DBA scheduling
Backing up archive logs Use SAPDBA or
Tools → CCMS → DB-
Administration → DBA scheduling
Backing up the database Use SAPDBA or
Tools → CCMS → DB-
Administration → DBA scheduling
Checking backup logs Use SAPDBA or
Tools → CCMS → DB-
Administration → Backup Logs
Testing restore and SAPDBA
recovery

D: Daily W: Weekly M: Monthly Y: Yearly AR: As required

<DBADM>: Database administrator

Configuration Documentation
Use the following tables to document your R/3 backup operations. Note that the R/3 database and the archive log
files are always backed up on separate tapes.

Timetable for Database Backups

Ensure that the tapes to be used for backup have been initialized. It is easiest to initialize all tapes to be used for
backup at the same time. The backup strategy recommended by SAP requires 30 tapes for backing up the database,
and 30 tapes for backing up the archive logs.
In the following table, enter when the backups are to be made for the respective R/3 System, and whether it is to be
an offline or an online backup.

BC360 Technical Core Competence 2-106

BC360

R/3 System Mon. Tue. Wed. Thu. Fri. Sat. Sun.

(For each database backup, use a new tape.)

Timetable for Archive Log Backup

Archive logs must be backed up more frequently to avoid the directory %ORACLEHOME%\saparch becoming full.
In the following table, enter when the archive log backups are to be made for the respective R/3 System.

R/3 System Mon. Tue. Wed. Thu. Fri. Sat. Sun.

Unscheduled Backups
Unscheduled, offline backups are required:
• After changing the structure of the database
• Before and after major changes to an R/3 System, such as upgrade to a new R/3 Release
Enter backup runtimes in the following table. When more data are entered into the R/3 System, you can check the
extent to which the runtime has changed.

Date R/3 System Database Backup Runtime Transaction Log Backup Runtime

BC360 Technical Core Competence 2-107

BC360

No True? Question:

1) Which of the following statements are true?

1.1 In a restore and recovery situation, the loss of a backed up data file will
lead to loss of data, even if you have an older version of the file and all
the required redo log archives.

1.2 X In a restore and recovery situation, the loss of a redo log, which is more
recent than the backed up data files that you need to restore, will lead
to loss of data.

1.3 X If your backup tapes cannot be read properly or are lost or damaged,
you risk losing your entire company database.

1.4 During an online database backup, blocks modified during the backup
are automatically recognized by the system and added to the database
backup tape, so that the online backup is consistent.

1.5 X The default brbackup database backup also backs up the control files
and the [Link] file.

1.6 The default brbackup database backup also backs up your Oracle
programs (“binaries”, “executables”).

1.7 X You should backup at least the affected data file (more simply, the
affected tablespace) when you change the structure of a tablespace.

1.8 If a backup to tape returns with no errors, you are guaranteed to be able
to read the tapes later if you need them for a restore.

1.9 X Some customers have been known to go live without testing their
backup strategy by performing a restore and recovery.

1.10 X Some customers have nearly lost their production database because
they have not tested whether their tapes were really readable.

1.11 Oracle requires you to restore the entire database, even if only one file
is damaged.

1.12 X You can only restore a single data file if you have the necessary redo
logs to bring that data file back in sync with the rest of the database.

BC360 Technical Core Competence 2-108