Action Patterns (Oracle) 

Definition

This section defines the action patterns in the DBA Planning Calendar for Oracle.

Use

You can select an action pattern when performing database administration (DBA) for Oracle in the DBA Planning Calendar.

Structure

There are the following action patterns:

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

Additional Information

·        The default option used in starting offline redo log backups is copy_delete_save.
For more information, see BRARCHIVE.

·        The database backup on Fridays is executed with verification using DBVERIFY.
For more information, see Backup Verify.

·        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 using brconnect -f check.

·        Once a week, the system updates statistics for all tables that need statistics, using brconnect -f stats.

·        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 <DBSID>B<DATE>. Replace <DBSID> 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 <DBSID>B<DAY><WK%2>. Replace <DBSID> 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.