Backing Up After Tablespace Operations (SAP Library - SAP Database Guide: Oracle (BC-DB-ORA-DBA))

Backing Up After Tablespace Operations

Use

When you have used SAPDBA for Oracle to extend a tablespace or create a new tablespace, you have changed the structure of the database. The database can be restored more quickly when you back up the new data file or the new tablespace and the control file.

For more information, see Database Backup with SAPDBA.

Prerequisites

You have completed one of the following procedures:

Extending a Tablespace

Creating or Dropping a Tablespace (a backup is not necessary after dropping a tablespace)

Procedure

Back up a newly created tablespace with the SAP program BRBACKUP.

Back up a tablespace that you have extended with BRBACKUP.

For this reason, after a tablespace extension, SAPDBA automatically branches to the Backup database menu, to enable you to start the appropriate backup immediately. As a result, you have a valid backup of the new control file and of the data files of the tablespace.

Independently of the above, SAPDBA backs up the old and new control files that do not yet exist in an old database backup, to the work directory <SAPDATA_HOME>/sapreorg/<timestamp> . They are given the names cntrl<SAPSID>.old and cntrl<SAPSID>.new , respectively.

Note

If you extend several tablespaces in a row, do not back them up individually (this means that you have to exit the Backup menu), but instead perform a complete backup of the database once you have finished all the extensions (an online backup is sufficient but an offline backup is better).