Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If RMAN copy copies the archived redo logs when they are full, what happens to the current redo log in the event of a failure (hardware failure, etc.)? Isn't there always an active redo log that is not an archive_log?

share|improve this question
up vote 2 down vote accepted

Yes, if the database is open in read-write mode there is always a number of changes to database that reside only in the current redo log and not in any archived log. If you want protect the current redo against hardware-related corruption, you need to add redundant storage (with either a remote replication or local mirror). If you want to protect the current redo from OS-related corruption, you need a "physical standby" database (the marketing term is DataGuard) with "SYNC LGWR" feed.

RMAN would not be useful to you, it is not designed for a a rolling backup of current redo.

share|improve this answer

The first thing RMAN does it automatically perform an ALTER SYSTEM ARCHIVE LOG CURRENT to switch logfiles so that the active log at the point the backup was started will be included.

It doesn't do this in all backup situations, but this answers your question.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.