Scribd
Upload
380 views

SAPDBA Utilities

The document provides an overview of Oracle database components and administration. It discusses how Oracle processes work, how data is stored and cached in memory, and how modifications are logged. It also describes how database users and privileges are set up on UNIX and Windows systems for R/3. Important transaction codes are listed for database backup, which can be scheduled and monitored through tools like CCMS and SAPDBA that call backup programs to write files to tape or disk. Backup profile parameters control settings like compression, tape devices, sizes and expiration periods.

Uploaded by

api-3757886
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
380 views

SAPDBA Utilities

The document provides an overview of Oracle database components and administration. It discusses how Oracle processes work, how data is stored and cached in memory, and how modifications are logged. It also describes how database users and privileges are set up on UNIX and Windows systems for R/3. Important transaction codes are listed for database backup, which can be scheduled and monitored through tools like CCMS and SAPDBA that call backup programs to write files to tape or disk. Backup profile parameters control settings like compression, tape devices, sizes and expiration periods.

Uploaded by

api-3757886
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Database Overview:

1. Components 3.Oracle Process Architecture


2. Net8 Basics 4.Database Administration tools

When an Oracle database instance is started


The groups of processes are distinguished as follows
Dedicated shadow processes are created when a new user session on the database is established

Database data is stored in 8 KB 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.

Each R/3 work process:


Connects to the database as one database user, SAPR3
Handles database requests for the different R/3 System users
Communicates with a corresponding shadow process on the database
Can reconnect to the database
R/3 in a UNIX Environment

OS User OS Group Database User Database Privileges


ora<SID> dba,oper INTERNAL (SYS) Full database administration
<SID>adm oper OPS$<SID>adm Restricted database administration

R/3 in a Windows NT Environment

OS User OS Group Database User Database Privileges


<SID>adm ORA_<SID>_DBA INTERNAL (SYS), Full database administration
OPS$<SID>adm

SAPService<SID> ORA_<SID>_OPER OPS$SAPService<SID> Restricted database administration

ORA_<SID>_DBA): OS users of this group can connect to Oracle using CONNECT INTERNAL with full
database administration privileges

ORA_<SID>_OPER) OS users of this group can connect to Oracle using CONNECT INTERNAL with restricted
database privileges, such as startup or shutdown database

Operating system users have certain privileges for accessing files and executing programs.
Database users have different privileges for changing tables and indexes.
Note:
Oracle mechanisms move the entire database security mechanism to the operating system level.
If the user OPS$<user_name> is defined as identified externally at the database level,
The operating system user <user_name> can connect to the database without authentication.

Note:
The database administration tool SAPDBA requires the restricted database administration privileges available in
the group oper.
SAPDBA only has access to the tables required for performing R/3 database administration in the background.
These privileges are assigned during R/3 installation or upgrade.

Important Transaction Code for DBA performance:


Scheduling, Performing, and Monitoring Backups
Backup can be scheduled by CCMS (DB13) /SAPDBA,
These tools call BRBACKUP [database backups] and/or BRARCHIVE [offline redo log file backups] in order
to back up the files to tape or disk and to log backup actions in database tables SDBAH and SDBAD

Backup Profile Parameter : init<SID>.saps

compress = hardware
compress_cmd = “compress -b 12 -c $ > $”
compress_dir = /oracle/<SID>/sapreorg
tape_copy_cmd = dd
disk_copy_ cmd = rman
exec_paralle = 0
tape_address = /dev/rmt/0mn
tape_address_rew = /dev/ rmt/0m
tape_address_arch/ = /dev/rmt /1mn
tape_address_rew _arch = / dev/ rmt/1m
backup_ model = all
backup_ type = online [offline]
volume_backup = (<SID>B01, <SID>B02, ...)
tape_ size = 32G - with hardware compression set to a smaller value and vice versa
tape_use_count = 100
expire_period = 28
backup_ dev_ _type = tape
archive_function = copy_delete_save
volume_archive = (<SID>A01, <SID>A02, ...)
tape_size_arch = 6000M

To choose the tape drives for the tape stations used for database or offline redo log file backups,
Set parameters
 tape_address
 tape_address_rew

The optional parameters


 tape_address_arch
 tape_address_rew_arch

are used to specify one (or two) tape drives for the tape station used for offline redo log file backups.
When the offline redo log file Backup parameters have been set, that time only used for the database
backup. with tape_address & tape_address_rew parameter

tape_copy_cmd = determines whether copy program cpio or dd is used to back up the data files to tape.

compress_dir =
Save control file to disk Save control file to disk

Online Offline
Save control file to disk Start database

Retrieve file names of data and online redo log files from database Same
And retrieve names of control files from init<SID>.ora

Shut down database

You might also like