Our SYSTEM tablespace grew out of control because of the SYS.AUD$ table.

We have truncated SYS.AUD$ but the datafile is still very big (~30G).

Resize doesn't work because the file contains used data beyond requested RESIZE value

What should I do here?

Here's our version information:

  • Oracle Database 11g Enterprise Edition Release - 64bit Production
  • PL/SQL Release - Production
  • CORE Production
  • TNS for 64-bit Windows: Version - Production
  • NLSRTL Version - Production
  • 1
    Which Oracle version are you using? Did you try Googling for a solution as there is lots of information out there. Mar 30, 2013 at 21:31
  • As @Colin'tHart said, this is a common problem with mis-managed databases. Edit your question with version information
    – Philᵀᴹ
    Mar 31, 2013 at 0:56
  • Sorry, you should recreate the dabatase. Don t forget to immediately move the AUD$ to another tablespace.
    – Diego
    Jan 9, 2014 at 18:22

2 Answers 2


Query the DBA_EXTENTS view to see what objects are present towards the end of the data files. It is possible that they are not system objects, or are system objects which can be safely modified so that they are towards the beginning of the files.

However I suspect that you have a big problem here -- you may be looking at creating a new database and moving all your user objects to that.


You can use segment advisor in Enterprise Manager and same can be done using PLSQL also. You can find a detailed guide in link given below:-


  • 1
    The reorganization of this object cannot be performed online. Cannot perform online reorganization of tables owned by SYS. Apr 2, 2013 at 17:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.