Before a Reorganization (SAP Library - Database Administration (Oracle) with SAPDBA)

Before a Reorganization

Shut down the R/3 System: To reorganize the database, you must shut down the R/3 System. The database should be run in RESTRICTED-SESSION mode. See Restricted Session.

Reorganize after starting the database: We recommend carrying out reorganizations immediately after opening the database in RESTRICTED-SESSION mode, because no locks can then exist for database objects.

Time scheduling: If you are reorganizing large quantities of data, the import/export and creation of indexes can be very time-intensive.

If you are reorganizing several objects specified in a list or tablespace, you should make sure that your file systems are available in sufficient quantity and of a sufficient size. Take advantage of the opportunity to run the export/import in parallel (if your host has several CPUs), which implies a great saving in time. See Parallel Export/Import.

The reorganization of tablespace PSAPPOOLD may take up to 10 hours. You can speed up this process, however, if you use the possibilities for Performance Maximization during Reorganization.

Also check the main log reorg<DBSID>.log to see whether a comparable operation has already run. This will enable you to better estimate the time requirements.

Bundle your reorganizations: When possible, plan your reorganizations well in advance, to enable you to perform them together. This will keep disturbances in ongoing operations to a minimum.

Database backups: Follow the Backup Concepts in Reorganizations.

Database analysis: Checking Statistics. If the statistics check has revealed a large amount of free space in the objects, you can perform the reorganization in such a way that the storage parameters are adapted (see Options for Changing and Checking the Storage Parameters).

Freespace: If you want to reorganize a table or tablespace without data files, make sure that enough free storage space is available in the relevant tablespace before the reorganization (around 5-10% of the tablespace size).

Naming conventions for files: SAPDBA can only reorganize tablespaces whose data files conform to the SAP naming conventions for files (see Naming Convention). Note the special features when working with raw devices (see SAPDBA Support for Raw Device Configuration).