Re: Archive Logs Filling Drive Up

From: Scott Watson <rscottwatson_at_hotmail.com>
Date: Wed, 30 May 2001 23:22:43 -0400
Message-ID: <fLiR6.18520$UH5.959650@wagner.videotron.net>

Chris,

I believe the NOLOGGING option is only for direct loads and does not apply to
regular DML ie insert, updates and deletes (these operations are always logged).

Perhaps you can try a temporary tablespace as I believe these are not logged but
this is just off the top of my head as I have not used them myself.

Happy hunting!
Scott.

"Chris Forbis" <chrisforbis_at_yahoo.com> wrote in message news:f2dc430d.0105301657.4dd8c63a_at_posting.google.com...
> I have Archive Logging on on a 8.1.7 database. I have many users on
> this. Each user has tables in USERS tablespace. All is good.
> Archive logs are kept for backup recovery. All seems work work well.
>
> I added a new TableSpace (NAME=NOLOGSPACE) When I created this
> TABLESPACE I added the NO LOGGING option. When I look at it in
> DBAStudio or any table in it it says LOGGING is off. This tablespace
> is a Locally Managed TableSpace. Also in DBA Studio it says next to
> the No Logging that this will keep inserts/updates/and deletes from
> beging logged.
>
> The problem: I went from 2 meg a day of Archive Logs :) Not much
> besides selects being done. To the now 1.2 gig a day. (I don't have
> the space for this) I need the User TABLESPACE and system to be
> logged, but the NOLOGSPACE is also being logged. It gets 100,000's of
> inserts a day, and also just as many deletes The whole TableSpace is
> only 75meg. Any idea how to fix this issue?
>
> Thank you
> Chris
Received on Wed May 30 2001 - 22:22:43 CDT