Database Backup and Recovery (MOSC)

MOSC Banner

RMAN duplicate slow, application of archive logs

edited Jan 5, 2010 8:21AM in Database Backup and Recovery (MOSC) 18 commentsAnswered
  I am capturing the current sequence number of my production database, taking a RMAN incremental level 0 backup (to disk), and immediately creating a clone via the RMAN duplicate command using "set until sequence xxx".  The uncompressed backup takes about 2 hours.  However ,the duplicate process has been taking up to 7 hours, which is too long to be of use.  It seems to spend a majority of the time applying and deleting archive logs - which I don't quite understand.  If my production backup is full, why does it need archive log files?  I don't have any need to do a partial

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center