Re: Create standby with OEM failing
- From: Kevin Lidh <kevin.lidh@xxxxxxxxx>
- To: sbecker6925@xxxxxxxxx
- Date: Mon, 7 Mar 2011 12:41:06 -0700
What we have done in the past is:
1) Take a backup with the standby controlfile
- in our case, we had to physically ship the backup over to the standby
site
2) Restore the standby and mount it (don't bother with recovery unless this
process takes days)
3) Discover the standby in OEM
4) Configure Data Guard in OEM with the "using existing physical standby"
option
OEM will take care of the configuration including the broker and then your
standby should catch up eventually.
On Mon, Mar 7, 2011 at 11:39 AM, Sandra Becker <sbecker6925@xxxxxxxxx>wrote:
> Platform: IBM zSeries
> OS: SUSE10
> DB: EE 10.2.0.4
>
> Some of SLAs require we have a standby database on our production
> databases. I am trying to create a standby database for our production OLTP
> using OEM. It fails to recognize the level 0 backup I did last Friday night
> with the following error:
>
> RMAN Backup Location - the specified RMAN backup is invalid. Could not
> identify controlfile from the backup.
>
> Although I did not really want to go this route, I tried the option
> "Perform an online backup of the primary database". It worked finr the
> first few files then it died. No errors on the screen or in the logs. The
> mount point for both backups is NFS mounted.
>
> I practiced and documented the steps twice on my sandbox database before
> trying it on the production database and I had no issues at all with the
> backups or creating the standby using OEM.
>
> Any ideas / suggestions?
>
> --
> Sandy
> Transzap, Inc.
>
Other related posts:
