Reg: unable to extend tablespace error.

Question

Hi,
On the database we work we got Unable to extend tablespace error. Suddenly in one night data was flooded into the tablespace.We have not run any precedure or On line reorganisation on that TS.
Is there any way that we can know what acivity had on that Tablespace during that night.We dont have audit option set in the database.
Thanks,
Venkat.

Answer 1

It really depends on what, exactly, you're looking for and what, exactly, happened.
If you have the archived log files from the night in question, that might tell you what statement generated a lot of redo. You'd miss certain unlogged operations, though, and that doesn't give you any information about what process caused the flood. If you've taken the basic precaution of getting base-line table sizes, querying DBA_SEGMENTS or DBA_EXTENTS to get the current size ought to show which tables have grown and is a lot less work than configuring Log Miner.
Log Miner would also tend to miss situations where a table allocated a new, rather large, extent.
Log Miner would tend to miss situations where an old manually allocated tablespace became fragmented
Justin