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

When doing a RMAN DUPLICATE from backup connected to the target, how current does the duplication make the database when no until time is set?

The closest thing I can find in the documentation is the following statement:

Restores and copies the duplicate data files and recovers them with incremental backups and archived redo log files to a non-current point in time.

How current is this non-current point in time? Does it apply to all the Archive Logs it has available to it at the start of the duplicate, or are they perhaps only available when it reaches the recovery part of the duplicate?

share|improve this question
up vote 0 down vote accepted

It's the moment of the last redolog archival, before some point in time during the RMAN duplicate command. You can test this easily, if you either manually provoke redolog switches (and thus subsequent archivals), or even better: write some script to provoke very frequent and unnecessary redolog switches. In which you perform some insert/update/delete, to further track things down.

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.