Re: Urgent - Question on Auditing

Well, my thought is that if you think the i/o is going to be minimal, you've got to be kidding -or you have a database with very little select and update activity. And the one tablespace you don't want clogged down with vast quantities of extraneous i/o is, naturally, SYSTEM. I recall a database whose aud$ table (though it had been moved) used to generate around 80M of inserts a day (I don't say the audit options were set very sensibly -just that that quantity of information is not out of the question on even a moderately busy database). The audit records weren't cleared very regularly, and that tablespace eventually ran out of room. I wouldn't vouch for the openability of your entire database if it was SYSTEM itself that ever ran out of room.

They didn't put screeds of information in the doco and the course notes about the critical need for moving that table for no reason.

Regards
HJR

--
=============================!!=============================
The views expressed are my own only, and definitely NOT those of Oracle
Corporation
=============================!!=============================


"Joe Kazimierczyk" <joseph.kazimierczyk_at_bms.com> wrote in message
news:3AFFC9BC.B7633952_at_bms.com...


> > ... Nice to move the aud$ table [out of SYSTEM]

> > (it's practically obligatory if

> > you've any sense...

>

> This seems to be a common line of thought, but I'm not sure

> I agree.  If you set the storage parameters for sys.aud$ and

> it's 1 index properly, there is absolutely no problem with

> leaving it in SYSTEM, is there?  Sure it's probably one of

> the more active tables in system regarding inserts, but the

> i/o resulting from that is still pretty minimal.  Any other

> thoughts?