Used Volumes (SAP Library - Database Administration (Oracle) with SAPDBA)

Used Volumes

BRBACKUP/BRARCHIVE volumes have the following files after a successful backup:

Label: tape.hdr0 (position 1)

init_ora: Initialization files init<DBSID>.ora , init<DBSID>.dba (OPS: the init.ora profiles of all Oracle instances) (position 2)

init_sap: Initialization file init<DBSID>.sap or the profile file defined under -p|-profile (position 3).

Database files (data files, online redo log files, control file) and/or non-database files and/or non-database directories or archived redo log files

reorg_log: Main SAPDBA log reorg<DBSID>.log and structure log struct<DBSID>.log (OPS: script create_raw_links ) (third-to-last position)

det_log: Detail log of BRBACKUP/BRARCHIVE (second-to-last position)

sum_log: Summary log of BRBACKUP/BRARCHIVE (OPS: the summary BRARCHIVE logs of all the Oracle instances) (last position)

Information about which volumes were already used is contained in the BRBACKUP/BRARCHIVE logs.

BRBACKUP and BRARCHIVE write two types of logs:

File system logs
- detail log; recreated in each backup
- summary log; extended in each backup
Database logs
- table SDBAH with information about the whole backup
- table SDBAD with information about the backup of a file

These log files should only contain information that was written by BRBACKUP/BRARCHIVE (or possibly SAPDBA); do not change this information manually. The information in database tables SDBAH and SDBAD is evaluated and deleted by the Computing Center Management System (CCMS), for example. Therefore, this information may not be changed except by BRBACKUP/BRARCHIVE/SAPDBA and the CCMS.

BRBACKUP, BRARCHIVE, and BRRESTORE Logs

For automatic volume management, BRBACKUP uses the corresponding database log as the foundation for selecting available volumes; BRARCHIVE uses the summary file system log. BRARCHIVE cannot rely on the database logs because the program can only be run when the database has been shut down.