To set up the cluster on secondary site

1. Install and configure servers and storage.
2. If you are using hardware-based replication, install the sofware for managing your array.
3. Verify that you have the correct installation options enabled, whether you are using keyless licensing or installing keys manually. You must have the GCO option for a global cluster. If you are using VVR for replication, you must have it enabled.
4. Install and configure SFCFSHA.

   For preparation:

   See Prerequisites for Veritas Storage Foundation Cluster File System High Availability.

   For installation:

   See About the Web-based installer.

   For configuration:

   For a multi-node cluster, configure I/O fencing.

5. For a single-node cluster, do not enable I/O fencing. Fencing will run in disabled mode.
6. Prepare systems and storage for a global cluster. Identify the hardware and storage requirements before installing your database software.

   You will need to set up:

   • Local storage for database software

   • Shared storage for resources which are not replicated

   • Replicated storage for database files

7. Install and configure the database binaries. Consult your database documentation.

   Note:

   Resources which will not be replicated must be on non-replicated shared storage.

   After successful database installation and configuration, verify that database resources are up on all nodes.

To set up the database for the secondary site

1. Do not create the database. The database will be replicated from the primary site.

   • If you are using hardware-based replication, the database, disk group, and volumes will be replicated from the primary site.

     Create the directory for the CFS mount point which will host the database data and control files.

   • If you are using VVR for replication, create an identical disk group and volumes for the replicated content with the same names and size as listed on the primary site.

     Create the directories for the CFS mount points as they are on the primary site. These will be used to host the database and control files when the failover occurs and the secondary is promoted to become the primary site.

2. Copy the init$ORACLE_SID.ora file from $ORACLE_HOME/dbs at the primary to $ORACLE_HOME/dbs at the secondary.

3. Create subdirectories for the database as you did on the primary site.