Selecting Action Patterns: Oracle (SAP Library - Computing Center Management System (BC-CCM))

Selecting Action Patterns: Oracle

The DBA Planning Calendar includes the following action patterns pre-defined by SAP for use in planning backups:

Full online DB backup and offline redo log backup, daily Monday to Friday, in one run (one month period)
Full online DB backup and offline redo log file backup daily from Monday to Thursday, in one run. Also includes full offline DB backup and offline redo log backup on Friday (one month period)
Full online DB backup and offline redo log backup, daily Monday to Friday, in one run (two-week period)
Full online DB backup and offline redo log file backup daily from Monday to Thursday, in one run. Also includes full offline DB backup and offline redo log backup on Friday (two-week period)
Incremental DB backup daily Monday to Thursday as well as full online DB backup and offline redo log backup in one run on Friday (one month period)
Incremental DB backup daily Monday to Thursday as well as full offline DB backup and offline redo log backup in one run on Friday (one month period)
Incremental DB backup daily Monday to Thursday as well as full online DB backup and offline redo log backup in one run on Friday (two-week period)
Incremental DB backup daily Monday to Thursday as well as full offline DB backup and offline redo log backup in one run on Friday (two-week period)

You can change or delete activities in an action pattern after selecting the pattern. A pre-defined action pattern provides an optimal backup strategy.

Once you choose a particular action pattern, the activities are entered into the DBA Planning Calendar on the corresponding dates. The background jobs that perform these activities are also automatically scheduled at the appropriate repetition intervals.

Procedure

In the DBA Planning Calendar (Transaction DB13 ), choose C alendar ® Action pattern
Choose one of the predefined action patterns from the displayed list

Enter the time at which the key action in the pattern is to be executed The system suggests an appropriate time, which you can accept or change

Optionally, choose the ID of your corresponding factory calendar from the calendar list The factory calendar affects the backup activities. It is used, for example, so that backups are not started on public holidays, when no tapes are available.

Specify the profile for the full online DB backup and the offline redo log backup The profiles contain BRBACKUP parameters that influence the backup Usually, the initialization profile init<DBSID>.sap is sufficient.

The activities contained in an action pattern are automatically added to the DBA Planning Calendar. The system also schedules background jobs for carrying out the activities. All jobs in the action pattern are scheduled to be repeated periodically (each week).

If there are conflicts between the action pattern you have chosen and activities that are already scheduled in the Planning Calendar, the system presents a list of the conflicts. Review and eliminate the conflicts before trying to choose the action pattern again. Usually, you only have to change the start time.

Notes

The default option used in starting offline redo log backups is copy_delete_save .
For more information, see Command Options for BRBACKUP, BRARCHIVE and BRRESTORE

The database backup on Fridays is executed with verification using DB_VERIFY .
For more information, see Backup Verifications

Before actions are started, you can automatically notify users informing them the R/3 System will be unavailable. This concerns actions that require the database be stopped, such as offline backups.
It is recommended you notify users about these types of actions, as they may be running transactions that will be terminated abnormally when the system goes offline.
To automate system message warnings, create an ABAP program that issues a system message. Then schedule the program for regular execution before the database action. For more information, see Utilities: System Messages

Offline redo log files are deleted from the redo log archiving directory after two successful redo log archiving sessions (option copy_delete_save ).

The database is checked daily for errors and possible bottlenecks ( sapdba –check ).

The value NEXT is automatically adjusted in all tables every week in order to optimally adjust the extent size to the actual requirements ( sapdba –next ).

Every Saturday, the system determines the need for update of statistics for all tables listed in the table DBSTATC ( sapdba –checkopt PSAP% ).

Every Sunday, the system updates statistics for all tables that need statistics as determined by the system on Saturday ( sapdba –analyse DBSTATCO ).

The pre-defined action patterns offer you backup schedules with two different tape retention periods.

One month retention period

This variant requires that backup tapes be retained for at least 28 days. The tapes can be used again after they are older than 28 days. Make sure the parameter for the tape retention period ( expir_period ) in the backup parameter file init<DBSID>.sap is set to 28.

Tapes that are used daily for data backup have the name <SID>B<DATE> . Replace <SID> with the database name (for example, C11 ) and <DATE> with the current day of the month.

Two week retention period

This variant requires that backup tapes be retained for least 14 days. Tapes can be used again after they are older than 14 days. Make sure the parameter for the tape retention period ( expir_period ) in the backup parameter file init<DBSID>.sap is set to 14.

Name tapes that are used daily <SID>B<DAY><WK%2> . Replace <SID> with the database name (for example C11 ), <DAY> by the number of the current day of the week (Monday=1,...,Sunday=7) and <WK%2> by the current calendar week using the numbers 0 and 1 (0 for even weeks and 1 for odd weeks).

Number of tapes required: For each day of the retention period, you need one tape for the data backups (database and offline redo log backups in one run) named according to the naming convention. Tapes must be initialized as required by BRBACKUP and BRARCHIVE.
Backups requiring more than one tape: For large databases, one tape is not enough for a complete backup. Change the action in the Planning Calendar as required (add additional tape names). In this case, the backup can run in parallel on multiple tape drives. Initialize additional tapes according to the naming conventions.

For more information, see:

Editing/Deleting Actions: Oracle

Limitations of the Database System

Prerequisites for Using the CCMS DBA Tools: Oracle

Volume Management