Getting Started in CCMS with Oracle DBA 

Use

Before starting to use the Computing Center Management System (CCMS) for Oracle database administration (DBA) tasks you need to set up certain things.

Procedure

...

       1.      Set up hardware for database backups and offline redo log backups to, for example, tape drives and tapes.

Database backups and offline redo log backups are not interactive. When they are executed from the DBA Planning Calendar, the operator is not informed when a tape needs to be changed.

Therefore, you need one of the following:

¡        The number of tape drives required to hold all tapes needed. The advantage of this is that BRBACKUP uses tape drives in parallel thus increasing the speed of the backup

If you start BRBACKUP and BRARCHIVE as separate actions, assign them to separate tape drives using the initialization profile init<DBSID>.sap. This allows you to use different tapes for database backups and offline redo log backups

¡        An automatic tape changer, supported by BRBACKUP. This devices changes the tapes as required by BRBACKUP and BRARCHIVE

For more information, see Initialization Profile init<DBSID>.sap, parameter descriptions for backup_dev_type and rewind_offline

Enter the tape drives to use in the BRBACKUP/BRARCHIVE initialization profile init<DBSID>.sap.

For more information, see Volume Management.

       2.      You set up authorizations.

To use the DBA Planning Calendar, you need authorizations for database administration and background job scheduling. The profiles S_RZL_ADMIN and S_BTCH_ALL  must be entered for the administrator.

For more information, see:

¡        Profile Maintenance (authorization object S_RZL_ADM)

¡        Authorizations for Background Jobs

External programs must be able to run on the database server so that actions affecting the database can be executed from other application servers.

       3.      You set up users and authorizations for the database system and operating system.

DBA Planning Calendar actions are executed under the authorizations of the host system user with which an SAP application server was started. This is usually the user <SAPSID>adm on UNIX, or SAPService<SAPSID> on Windows.

The user <SAPSID>adm or SAPService<SAPSID> must be:

¡        Specified as a trusted user OPS$ in the Oracle database

¡        Granted the SAPDBA role

For more information, see the Oracle database documentation.

These prerequisites are normally met in the standard SAP System.

       4.      You configure BRBACKUP, BRARCHIVE, and BRCONNECT.

BRBACKUP, BRARCHIVE, and BRCONNECT use the backup parameter file init<DBSID>.sap.

If you are using different tape drives for BRBACKUP and BRARCHIVE, you must adjust the backup parameter file init<DBSID>.sap. If you are using multiple tape drives, you must also specify these in the configuration file.

Set the following parameters:

¡        For BRBACKUP: tape_address, tape_address_rew

¡        For BRARCHIVE: tape_address_arch, tape_address_rew_arch

If you have scheduled BRBACKUP and BRARCHIVE to start in one action, the system only uses the tape drives defined for BRBACKUP.

For more information, see Backup and Database Copy with BR*Tools.