Preventing Tablespace Overflow (SAP Library - SAP Database Guide: Oracle (BC-DB-ORA-DBA))

Preventing Tablespace Overflow

Use

This section describes how to prevent tablespace overflow in your Oracle database.

Prerequisites

You have completed the following procedures:

Checking Freespace for Tablespaces

Checking Freespace for Objects in Tablespace

This enables you to identify tablespaces that are about to overflow, and the objects that would cause overflow if they were extended.

Procedure

If an overflow has already occurred, you can check this in the SAP System log.

The Oracle error is given, together with the table or index that was accessed when the overflow occurred.

You can then determine which tablespace the table or index belongs to, using SAPDBA. For more information, see Checking Freespace for Tablespaces. Set the number of extents to 1 when running the report.

If you have found that the tablespace would overflow if:

An object were to be extended by one extent, you must extend the tablespace as soon as possible.

The exception to this rule is for tablespaces PSAPPROTD or PSAPPROTI , which contain SAP logs from background processes and spool requests. Delete old log files and requests instead of extending these tablespaces.

An object were to be extended by two extents, you need to closely monitor the tablespace.

If you have found that there is no danger of overflow if two extents were added, the tablespace currently has sufficient free storage space. You need take no action at present, provided the tablespace continues to be used normally. Continue to monitor the tablespace regularly as usual.

Note

If you change the storage parameters for a tablespace, or perform operations in the SAP System that cause it to fill more quickly than usual, be sure to monitor the tablespace closely and extend it if necessary.