Re: DB_RECOVERY_FILE_DEST_SIZE

On Fri, 12 Aug 2005 14:13:22 +0200, "Uwe Schmidt" <uwe.schmidt_at_dataport.de> wrote:

>Hello NG,
>
>
>we use ORACLE 10g on SUSE SLES9 LINUX.
>
>Can I switch off the parameters:
>
>DB_RECOVERY_FILE_DEST_SIZE
>DB_RECOVERY_FILE_DEST
>
>We don't use the RMAN and we have problems, when the value for
>DB_RECOVERY_FILE_DEST_SIZE is reached. I always make the value for
>DB_RECOVERY_FILE_DEST_SIZE bigger and bigger but it never shrinks. I put the
>offline RedoLogs to a different path on our storage system but oracle
>recognizes the value for the size.
>
>What can we do?
>Do you have an idea?
>
>Uwe

Do you have flashback database enabled ? That will continously generate flashback logs in DB_RECOVERY_FILE_DEST.

Please note that when creating a database in archivelog mode with a flash recovery area, Oracle will "transparently" (behind the back, that is) set LOG_ARCHIVE_DEST_10 to point to this area, generating an extra copy of all archivelogs (what you call "offline redo logs") to this area.

Take a look at DB_RECOVERY_FILE_DEST from the O/S.What kind of files fill it up ?

You can disable the flash recovery area by resetting the 2 parameters, yes. Note that you may have both controlfiles and online redo log files in that area. So don't delete it's path from the O/S before checking.

The flash recovery area is a good thing, but I would prefer not to be dependent on it, which means:

No online database files in that area, which means datafiles, redo logs and control-files. It should only be used by RMAN and flashback logs (and maybe a second archivelog destination). That way you can lose that disk area without your instance breaking down.

• Kenneth Koenraadt