Re: RMAN DUPLICATE failed at recovery time.
From: Liencres <perplejo10_at_yahoo.es>
Date: Thu, 11 Jun 2009 00:19:53 -0700 (PDT)
Message-ID: <edb027de-c607-4e0d-bc7c-81f12cabc67f_at_c36g2000yqn.googlegroups.com>
In order to secure the duplication and avoid Oracle doing the wrong thing applying recovery with compressed backup sets, I did proceed this way:
1) Cold Backup of the target database
2) Open the target database and perform a log switch. This archives the current log
3) Use cold Backup pieces and 1 archived log to duplicate the target database.
Date: Thu, 11 Jun 2009 00:19:53 -0700 (PDT)
Message-ID: <edb027de-c607-4e0d-bc7c-81f12cabc67f_at_c36g2000yqn.googlegroups.com>
In order to secure the duplication and avoid Oracle doing the wrong thing applying recovery with compressed backup sets, I did proceed this way:
1) Cold Backup of the target database
2) Open the target database and perform a log switch. This archives the current log
3) Use cold Backup pieces and 1 archived log to duplicate the target database.
Using the RMAN DUPLICATE command, you cannot duplicate a target database without applying recovery hence the need to archive the current log.
As reported by Tony, restoring archive logs from compressed backup sets and then applying recovery from them should also be fine. Received on Thu Jun 11 2009 - 02:19:53 CDT