Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl> wrote in message news:<nr7om0p2ooand9fr3h9it9lal9e3r98h8j_at_4ax.com>...
> Apparently when you delete a controlfile record it isn't really
> deleted but it goes into the 'deleted objects' section. You delete
> records from the controlfile especially when you manipulate rman
> backupsets and pieces and/or archive logs.
> As the 'deleted objects' section, according to the output you can't
> seem to read, is at maximum capacity, you can't do anything about that
> and you can only hope and expect that recreating the controlfile will
> resolve the problem.
Not entirely correct. The reason for this is that the author of this
thread had way too big CONTROL_FILE_RECORD_KEEP_TIME (thirty is just
too much) and during that period generated more redo than his
controlfile history records could keep. The recreation of a control
file will not solve anything, only postpone this error until next
month. The only way how to solve this is to lower this parameter to
some sensible value (three should be sufficient in most cases, it
depends on his backup schema).
After lowering of this value, the error would change to warning about
overwriting old records and after some time it will return to normal.
So probably there is not need to recreate controlfile because of this.
--
Dusan Bolek
http://www.db-support.com
Email: spambin_at_seznam.cz
Pls add "Not Guilty" to the subject, otherwise your email will face an
unpleasant end as SPAM.
Received on Wed Oct 13 2004 - 07:22:55 CDT
