Re: Shared storage required for snapshot control file in 126.96.36.199 RAC - RMAN
Date: Mon, 12 Sep 2011 18:11:01 -0400
I happen to like putting them on ASM since you can cut out the NFS requirement on all of your RAC nodes. This change will also need to be configured for your autobackup:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '+RECO/ORC1/%F'; If you need to copy those files to a local file system you can use either dbms_file_transfer.copy_file for the snapshot or using rman backup backupsetfor the autobackups.
On Mon, Sep 12, 2011 at 10:37 AM, Steve Harville <steve.harville_at_gmail.com>wrote:
> Can anyone recommend the preferred shared storage type for these files?
> I just found out about the new behavior when creating snapshot control
> files. In 188.8.131.52 all nodes must be able to write to the snapshot
> control file. I have temporarily moved the location of this file to an
> ASM Cluster File system. I am getting a shared NFS mount for the long
> term location. I am not convinced that either of these alternatives is
> the best.
> By the way - I found out that I could not change the RMAN setting
> when I was connected to the catalog. When I connected only to the
> target the RMAN "CONFIGURE SNAPSHOT CONTROLFILE NAME TO " command
> worked correctly.
> The new behavior is described in metalink bulletin 1268725.1.
> Steve Harville