This tablespace contains the ATAB table with a very large number of records. The import – and therefore the reorganization – of this tablespace can take up to 10 hours, depending on your operating system. The run time depends on the import of the table data. You can influence the duration of the import by performing the reorganization of PSAPPOOLD with a modified import script. For more information, see the SAP Notes.

Also, if you operate a productive database in ARCHIVELOG mode, 1 to 2 GB of free space is required in the archiving directory of the offline redo log files ( <SAPDATA_HOME>/saparch ). Therefore, it helps to run the database in NOARCHIVELOG mode during the reorganization of PSAPPOOLD . If you reorganize in NOARCHIVELOG mode, be sure to back up the entire database afterwards. For more information, see Reorganizing in NOARCHIVELOG Mode.

This tablespace usually contains the most tables with the highest total number of extents, constraints, and so on. The size of the individual Dictionary caches must be large enough to avoid Oracle errors (for example, errors in recursive calls) during an operation on the tablespace. Oracle itself manages the individual caches dynamically. To enable this, the init.ora parameter shared_pool_size must be large enough to avoid bottlenecks. For more information, see Database Parameters.

This tablespace grows very quickly. To avoid frequent reorganization, we recommend regular use of the command sapdba -next <tablespace(s)>.