Re: Moving the aud$ table out of the system tablespace

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<992531148.5456.0.nnrp-01.9e984b29_at_news.demon.co.uk>...
> True, and I've always believed that, but there was
> a thread on Metalink a little while ago about being
> unable to recover a tablespace because the aud$
> table had been moved into it. You might try testing
> that out before going live.
>
> --
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> Practical Oracle 8i: Building Efficient Databases
> Publishers: Addison-Wesley
>
> Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html
>
>
>
> Brian Peasland wrote in message <3B28D118.FDACBC87_at_qwest.net>...
> >Lowell,
> >
> >You should not have any problems if you moved AUD$. It is just a table.
> >It's location (i.e. tablespace) is irrelevant.
> >
> >HTH,
> >Brian
> >
> >Lowell wrote:
> >>
> >> Has any ran into any problems with upgrades after they have moved the
 aud$
> >> table out of the system tablespace?
> >>
> >> Thanks
> >> Lowell

I think I remember the metalink thread Jon mentioned. Oracle support had posted the instructions for moving sys.aud$, but said it was unsupported and they did not guarentee compatibility with future upgrades etc... But they didn't actually know of any problem at the time.

Why not just add a file to system and make the system tablespace big enough to handle the desired amount of audit trail. Manually allocate a single large extent to hold the data and change maxextents to 2 so you prevent the audit trail from filling the system tablespace and limit your error to an unable to max extents error, which you can fix by dropping an audit rule or purging.   

• Mark D Powell --