Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!sn-xit-03!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Daniel Morgan Newsgroups: comp.databases.oracle.server Subject: Re: SYSTEM Tablespace is FULL Date: Tue, 09 Sep 2003 08:03:30 -0700 Organization: ATS Message-ID: <1063119789.290314@yasure> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <3F5C9BFD.E3F8EA39@remove_spam.peasland.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------000400080005030305050405" Cache-Post-Path: yasure!unknown@pond178.drizzle.com X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/) X-Complaints-To: abuse@supernews.com Lines: 98 Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:242695 --------------000400080005030305050405 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Pete Finnigan wrote: >Hi Brian, > >You mention moving sys.aud$ to another tablespace, whilst this is common >sense Oracle no longer support doing this as some poor customer could >not recover when this had been done. I don't believe Oracle have changed >advice on this as yet. There is a note on Metalink about it. The >solution if it is moved is probably to switch audit off whilst >recovering. Jonathan discussed the following with me some time back: > > > > Well if we are talking about 9.2 there is no need to audit into sys.aud$ anyway. The syntax is now: AUDIT_TRAIL = {NONE | FALSE | DB | TRUE | OS} NONE or FALSE = Audit records are not written. DB or TRUE = Enables system-wide auditing and causes audited records to be written to SYS.AUD$ OS = Enables system-wide auditing and causes audited records to be written to the operating system's audit trail. And must everything be cross-posted? I've deleted the threads in tools and misc. -- Daniel Morgan http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp damorgan@x.washington.edu (replace 'x' with a 'u' to reply) --------------000400080005030305050405 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Pete Finnigan wrote:

Hi Brian,

You mention moving sys.aud$ to another tablespace, whilst this is common
sense Oracle no longer support doing this as some poor customer could
not recover when this had been done. I don't believe Oracle have changed
advice on this as yet. There is a note on Metalink about it. The
solution if it is moved is probably to switch audit off whilst
recovering. Jonathan discussed the following with me some time back:

Well if we are talking about 9.2 there is no need to audit into sys.aud$ anyway.

The syntax is now:

AUDIT_TRAIL = {NONE | FALSE | DB | TRUE | OS}

NONE or FALSE = Audit records are not written.
DB or TRUE = Enables system-wide auditing and causes audited records to be written to SYS.AUD$
OS = Enables system-wide auditing and causes audited records to be written to the operating system's audit trail.

And must everything be cross-posted? I've deleted the threads in tools and misc.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan@x.washington.edu
(replace 'x' with a 'u' to reply)

--------------000400080005030305050405--