When extracting large amount of data in SAP system based on any relational database, data is being gathered together in a temporary table, until an SQL statement commit occurs.
In Oracle databases the table containing temporary data is stored in a tablespace named PSAPTEMP. All tablespaces in an Oracle database have a fixed size (until they are extended) measured in Gigabytes. If a tablespace is running full (no more available space to extend the table), Oracle will throw out database error ORA-1652 and roll back the changes.
This can be seen in the SAP SM21 log; "Database error 1652 at FET", at the exact time as the job fails.
There is a file limit size on data files in an Oracle tablespace. The maximum size of a data file depends on the block size of the database. It will eventually come to a point, where a data file cannot be extended any further, and a new data file has to be added to PSAPTEMP.
To resolve ORA-1652 errors with temporary tables, the tablaspace PSAPTEMP needs to be extended either by adding more data file or extending the current one. For example, increase the tablespace by 10% and try again. If it is not enough, increase with another 10% and so on (see attached file page 8).
More information can be found in the log files "Alert<SID>.log" in
For UNIX: /oracle/<SID>/saptrace/background/
For Windows: <drive>:\oracle\<SID>\saptrace\background\
For further information, kindly read the following links:https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:36859040165792http://www.dba-oracle.com/t_ora_1652_unable_extend_tips.htm