Extending or creating a tablespace changes the structure of the database. The database can be restored more quickly when you back up the new data file/tablespace and the control file.

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

A backup after a tablespace extension is not required when you use the functions in the menu Restore/Recovery, since SAPDBA also creates new files, including the tablespace extension. You are given information about the last successful complete backup and about the necessary time period for any necessary recovery. You should always save the tablespace after an extension (for example, use the SAP utility program BRBACKUP) so that all the SAPDBA recovery functions are available (menu Check (and repair) database and Restore/Recovery). 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 <ORACLE_HOME>/sapreorg/<timestamp>. They are given the names cntrl<SAPSID>.old and cntrl<SAPSID>.new, respectively.

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