Database Actions After Archiving or Deletion

Use

Oracle: Reorganization of the Index

If data has been archived or simply deleted and the associated tables were accessed via an index, the index should be reorganized. Deleting table entries leaves holes in the table which are still indexed. Reorganization can shorten the access paths, reducing response times.

For databases with a cost-based optimizer (CBO): Refresh the database statistics

If your database uses a cost-based optimizer, you must choose Update Statistics to recalculate the access paths.

Oracle: Reorganization of Tablespaces and Dbspaces

Whether you should reorganize the tablespace depends on the reason for archiving.

  • Do you expect a lot of new data for the archived tables?

    If so, you should not reorganize.

    On the other hand, if, for performance reasons, you have archived data that is no longer needed in the system and the table is otherwise rarely changed, you should reorganize.

  • Do you want to make space for other tables?

    If so, you should reorganize the tablespaces and dbspaces of both the tables and the indices.

    This procedure is described in the SAP NetWeaver AS documentation SAP Database Guide: Oracle (BRSPACE for Oracle databases) and the ABAP Dictionary, section Tablespaces and Extents (database-independent parameterization, MaxDB).