Dbvisit Standby and Oracle SE RAC licensing
I am researching your software and have a question about how it relates to Oracle SE RAC licensing. While reading the Oracle licensing documents there is a specific sentence (below in red) that says that a second copy of archivelogs can be scripted but are only allowed to be stored locally. Do you know how this requirement relates to using Dbvisit Standby on an Oracle SE RAC installation when the standby database being managed by Dbvisit Standby is in a remote location?
Oracle Standard Edition and Oracle Real Application Clusters (Oracle RAC)
The license restrictions for Standard Edition must be adhered to. The maximum number of CPUs defined is for the entire cluster; it is not a per node maximum.
Oracle Clusterware is required; third-party clusterware is not permitted.
Automatic Storage Management (ASM) is required for the storage of:
* Database data files
* Online logs
* Archive logs
* Control files
* Server parameter files (spfiles)
* Flash Recovery Area
RAW disk partitions are required for:
* Voting disk
* Oracle Cluster Registry
Local storage must be used for:
* Oracle Home
* Trace files
* Dump files
No Oracle-maintained copies of any of the above files can exist in any other locations, with the following exception: Customers who want to manually script maintenance of a standby database can create a second copy of their archive logs outside of ASM on a local file system only, designated by the LOG_ARCHIVE_DEST_n parameter.
The restriction with Oracle SE RAC licensing is that all files must exist in the ASM location. Dbvisit Standby adheres to this restriction and does not require any database file to be outside of ASM including the archive log files. Dbvisit Standby extracts the archive logs out of ASM to transfer to the remote location and applies it to the standby database.
What the specific sentence is referring to is that if you want to manually script a standby database, you can setup a second archive log destination outside of ASM on the local file system. The archives that are generated there can then be transferred (manually or scripted) to the remote location and applied to the standby database.
This requires you to setup a second archive log destination using the LOG_ARCHIVE_DEST_n parameter in your primary database.
As mentioned setting up this second archive log destination is not required with Dbvisit Standby as it extracts the archive logs out of ASM.
Last edited by Mike Donovan; 07-12-2011 at 05:53 PM.
|Thread Tools||Search this Thread|