Archiving Mode during the Reorganization (SAP Library - Database Administration (Oracle) with SAPDBA)

Archiving Mode during the Reorganization

Since a reorganization always involves the export and import of mass data, a large number of redo log files are written. If you deactivate the ARCHIVELOG mode, there is no significant acceleration of the reorganization. The archive process ARCH runs parallel to the remaining background database processes, this means that only the CPU is briefly more heavily loaded if you operate the database in ARCHIVELOG mode. Thus, the reorganization is not significantly slowed down.

Advantages of a Reorganization in NOARCHIVELOG Mode:

You can safeguard against the risk of a archive stuck. In any case, you save space in the archiving directory of the offline redo log files <ORACLE_HOME>/saparch.

BRARCHIVE does not have to run for the period of the reorganization, as no offline redo log files are created.

Time can be saved in the event of a recovery, as you can resume from the backup performed after the reorganization (this is mandatory with this method).

Data Security for a Reorganization in NOARCHIVELOG Mode:

SAP only recommends deactivating ARCHIVELOG mode under certain conditions, since it interrupts the continuity of the redo log files. Once the reorganization is complete, it is essential that you reactivate the ARCHIVELOG mode and perform a complete offline backup of the database.

Reorganizing in NOARCHIVELOG Mode