SAP Note 27412 - SAPDBA: Warning: lack of space Export/PSAPTEMP

Symptom:

SAPDBA brings the following warnings:
1.
SAPDBA: Free space in file system / on tape ...: ...K
Summary of all extent sizes of tables
which are to be exported: ...K
Do you want to continue (y/n) [n]:

2.
SAPDBA: Size of largest index: ...K
Free space in temporary tablespace ...: ...K
(Free space should have a minimum size of two times of the
index size to ensure a successful index creation.)
Do you want to continue (y/n) [n]:

Cause and prerequisites

1.:
The space which is probably needed for the export dump file during the export or during a reorganization cannot easily be determined in advance. Therefore, SAPDBA checks whether space exists amounting to the total size of all extents of all tables that are to be reorganized. Otherwise the above-mentioned warning appears and SAPDBA waits for a corresponding reaction.

2.:
If, due to a reorganization, an index is re-created, ORACLE requires space in the user's temporary tablespace (for an R/3 database, this is normally the tablespace PSAPTEMP).
This space cannot be determined very accurately in advance, and therefore SAPDBA is checked to see whether it contains at least twice the amount of space as the largest index to be reorganized. If this is not the case, the above-mentioned warning appears and SAPDBA waits for a corresponding reaction.

Solution
1.:
The user can decide whether to cancel the export / reorganization and repeat the procedure having first either created more space in the file system or instered a larger tape. The user can also continue after increasing the available space parallel to SAPDBA (for example, by deleting files that are no longer required). He may also simply hope that the tablespace required for the export is sufficient, despite the warning (for example, if the extents of the tables are not completely filled).
If the user continues with the export and the error still occurs, the export can be repeated or restarted with the SAPDBA restart option after increasing the available tablespace.

2.:
The user can decide whether to terminate the reorganization, increase the amount of temporary tablespace available and repeat the export, or whether to continue, having already increased the available space. He may also continue and hope that the available tablespace is sufficient for the index creation (for example if the index extents are not completely filled.)
If the user continues with the index creation and the error still appears, he can still extend the temporary tablespace and finish the reorganization with the SAPDBA restart option.

Additional key words

sapdba, export, exp, index, PSAPTEMP, temporary tablespace