I got this error in an SAP instance with ORACLE database
ORA-01630: max # extents (300) reached in temp segment in tablespace
PSAPBTABI#
There isnt a job abort log to find out what application code caused
it. Now I would like to find out
- The tablespace mentioned is not a TEMP space for the Oracle user
or neither it is TEMPORARY storage type tablespace . (It is a
permanent tablespace typically used by SAP for Indexes !) So why is
Oracle using it instead of the real temp tablespace?
- Is the maxextents being setup by application code somewhere, or is
it being picked up from TableSpace defaults ?
- Lets assume the maxextents cannot/would not be changed at the
Tablespace level . How can we resolve this ?
Any clues ?
Received on Wed Jun 26 2002 - 16:55:39 CDT
