Re: Archive Logs Filling Drive Up

only 1.2GB a day ? i wish i had that kind of a problem. at peak times, we've generate 1.2GB of redo in under 20 minutes.

my first recommendation is that you acquire additional disk space.

another option you might consider is gzip'ing the older archive log files (if you can spare the cpu and io). but remember, if you have to recover, you will need disk space to gunzip the archive logs before oracle can use them for a recovery.

copying archive logs to tape is also an option. i don't ever remove the archive logs from disk until i have at least two copies on separate tapes, and at least one of the tapes off-site.

my second recommendation would be for you to figure out which activities are generating the most redo, and carefully consider modifying these processes to reduce the amount of redo generated. one option would be to perform truncates rather than normal deletes. (this is logged, but you can avoid generating rollback, which is also logged. or performing direct loads rather than than regular inserts.

it looks like you are already considering using "nologging" (did "unrecoverable" go away in 8 or 8i ?) for activity in the new tablespace. just remember that any operation that is performed "nologging" will impact your recovery strategy.

HTH "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 Fri Jun 01 2001 - 22:00:29 CDT