Entering content frameProcedure documentation Backing Up the Database for Reorganization Locate the document in its SAP Library structure

Use

We strongly recommend that you back up the Oracle database before you reorganize it with SAPDBA. How you do this depends on the reorganization type. SAPDBA does not perform an automatic backup before or after a reorganization, although it sometimes displays the backup menu following a reorganization.

Procedure

Back up the database as follows:

Before reorganizing a single object or list of objects, back up the data in the relevant table or tables, for example, using the Export and Import function in SAPDBA. If the reorganization fails and you cannot restart it, you can then use the backup of the data to restore the old status and repeat the reorganization.
    1. Before reorganizing a tablespace, make a complete backup of the database. It is best to perform an offline backup, although an online backup is also possible. Use BRBACKUP for the backup, which you can start manually or with SAPDBA.

      2. If the last complete backup of the database was performed recently, and all redo log files up to the start of the reorganization are available (on disk if possible), you can leave out the database backup. In this case, you could restore the database from the last available backup if necessary.

    2. After reorganizing a tablespace, you proceed as follows, depending on the reorganization type:
      1. Reorganization of a tablespace without data files

        2. We recommend you to back up at least the reorganized tablespaces. This is because, in the event of database failure soon after the reorganization, you would have to repeat the reorganization process if there was no backup available, and the reorganization can take a long time.

      2. Reorganization of a tablespace with data files

You must back up at least the reorganized tablespaces, because the underlying database structure has changed. Otherwise, SAPDBA cannot recover the database in the event of database failure. SAPDBA automatically displays the backup menu after the reorganization, to let you immediately start the backup.

Caution

A tablespace backup after reorganization is sufficient when the database is running in ARCHIVELOG mode. However, if it is running in NOARCHIVELOG mode, you must back up the entire database. If many tablespaces require reorganization, we recommend a complete offline backup of the database before reorganization of the first tablespace and after reorganization of the last tablespace.

After moving or renaming the data files of a tablespace, you must perform at least a backup of the corresponding tablespace. This is because, in the event of database failure, SAPDBA cannot recover the database without a backup. In this case SAPDBA automatically displays the backup menu after the reorganization, to let you immediately start the backup.

Leaving content frame