Storage Management Errors (Oracle)

Storage management problems generally develop so slowly that you can recognize them and eliminate them before they seriously affect system operation. However, such problems can also arise very quickly during the data transfer phase when implementing your SAP system if you transfer mass data from an old system into a new one.

If a problem becomes acute, you probably get one or both of the following database error messages. These are critical errors since they at least partially interrupt the operation of the database and the SAP system.

Tablespace overflow
Problem: The database could not allocate another extent for a table or another index since the tablespace is full. The corresponding Oracle error is displayed.

Solution: Extend the tablespace by creating another data file using the BR*Tools. For more information, see Extending a Tablespace with BR*Tools.

The file you create should be large enough to cover expected use of the tablespace in order to avoid recurrence of this problem in the long-term. Note that the Oracle database supports only a limited number of files (1024 files max.). SAP generally configures the database so that you can create up to 254 files on each platform. It is quite possible for you to reach this limit if you continually create small files when extending tablespaces.

Precautionary measure: Check the storage space situation in the tablespaces on a regular basis. In addition to the options provided by the CCMS, you can use the analysis options of the BR*Tools. For more information, see Showing Tablespaces with BR*Tools.

Make sure that you extend tablespaces that are nearly full as soon as possible. For more information, see Extending a Tablespace with BR*Tools.

Analyses with the CCMS Database Monitor

Tablespace Analysis (Oracle)

Extent Analysis (Oracle)
Extent overflow
Problem: The database system could not allocate a new extent to a table or an index in a tablespace since the upper limit for the number of extents (MAXEXTENTS parameter) for this object was reached. The corresponding Oracle error is displayed.

Solution:

If the soft limit defined by SAP for NEXT and MAXEXTENTS (usually 300) was reached, you can change the values for MAXEXTENTS with BR*Tools.

Precautionary measure: Check for objects that are close to the MAXEXTENTS limit (or objects that are growing rapidly) on a regularly basis. If you find tables or indexes of this kind, carry out the following actions: Make sure that the value for the next extent (NEXT parameter) is increased. If necessary, you can increase the value for MAXEXTENTS.

Analyses with the CCMS Database Monitor

Tables/Index Analysis (Oracle)

Extent Analysis (Oracle)