Background Reorganization (SAP Library - SAP Database Guide: Oracle (BC-DB-ORA-DBA))

Background Reorganization

Use

You can reorganize the Oracle database with SAPDBA in the background rather than immediately.

Integration

Background reorganization is available for the following reorganization types:

Reorganizing a single table or index

Reorganizing a list of tables and indexes

Reorganizing a tablespace

Reorganizing a tablespace and data files

Moving or renaming data files of a tablespace

Prerequisites

Make sure that you understand the UNIX at command. For more information, see Configuring the UNIX Command at. The jobs created with at are transparent and can therefore be displayed using operating system commands. You can find the necessary environment variables in this kind of file, as well as the command sapdba -r <complete path/timestamp> , to start the reorganization.

Features

Tables and indexes that were created before the reorganization starts but after SAPDBA has created the scripts are not taken into consideration during a background reorganization.
If a tablespace is reorganized without data files, it might terminate due to a lack of storage space. Such objects are lost together with their data in a tablespace reorganization including data files. Therefore, only plan a background reorganization at a later time if no new objects were created in the meantime.

Activities

When scheduling several reorganizations one after the other at a later time, make sure that:

The export dump files for the individual reorganizations are on different disks.
In the case of a reorganization with data files, the old and new files of the tablespaces are on different disks.

When scheduling several reorganizations one after the other, leave enough time between so that they do not overlap. The runtime entries in the central log reorg<DBSID>.log help you with scheduling.

Do not perform several reorganizations in parallel, as this can lead to bottlenecks in the Oracle Dictionary or an incorrect space check.