InfoScale™ 9.0 Cluster Server Implementation Guide for Oracle - Windows
- Introducing the VCS agents for Oracle and NetApp
- Installing and configuring VCS
- Installing and configuring Oracle
- About installing Oracle
- Prerequisites for installing Oracle
- Installing Oracle
- About creating and configuring Oracle
- Prerequisites for configuring Oracle
- Configuring Microsoft iSCSI initiator
- Managing storage using Windows Logical Disk Manager
- Managing storage using NetApp filer
- Creating a temporary service group
- Configuring Oracle on the first node
- Dismounting a volume
- Bringing the temporary service group online
- Creating the Oracle database on shared disks
- Creating the listener service
- Configuring the listeners to use the virtual IP address
- Associating the database with the listener
- Configuring the Oracle database
- Configuring the Oracle and listener services
- Disconnecting virtual disks from the first node
- Releasing disks (if you use Windows LDM)
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Administering the Oracle service group
- Troubleshooting
- Appendix A. Resource type definitions
- Appendix B. Sample configuration
- Appendix C. Oracle Enterprise Manager 10g Grid Control with VCS
- About Oracle Enterprise Manager 10g Grid Control with VCS
- Installing the VCS agent for Oracle
- Installing Oracle Enterprise Manager server
- Installing Oracle
- Installing the Oracle Management Agent
- Creating and configuring Oracle database and listener on the first node
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Configuring a virtual network name
- Configuring the listener for virtual network name
- Configuring the database service for virtual network name
- Configuring an additional Oracle management agent
- Adding the database to the OEM 10g Grid Control
- Making the additional agent highly available
Managing storage using NetApp filer
NetApp manages data by creating volumes on physical disks. These volumes can further be divided into LUNs (Logical Unit Numbers). The LUNs are accessible from the cluster nodes, provided the nodes have Microsoft iSCSI Initiator and NetApp SnapDrive installed. However, if you plan to use Fibre Channel (FC) for connecting the LUNs, ensure that filer is connected to the nodes and the LUNs are shared between all the cluster nodes.
Refer to the NetApp documentation for more information.
The following figure illustrates a typical VCS cluster in a NetApp storage environment.
The VCS agent for Oracle requires that you create LUNs for the following:
database files
control files
log files, including the redo logs, archive logs, background_dump_dest (bdump), core_dump_dest (cdump), and user_dump_dest (udump) files
Flash Recovery Area and the Archiving location
The Oracle background_dump_dest (bdump), core_dump_dest (cdump), and user_dump_dest (udump) files must be on the same LUN as that of the redo logs.
Arctera recommends that you create separate LUNs (virtual disks) for the following:
INST1_DATA_FILES
Contains the Oracle system data files (including the master, model, msdb, and tempdb databases).
INST1_REGREP_VOL
Contains the list of registry keys that must be replicated among cluster systems for the Oracle Service. Create a 100 MB (minimum recommended size) volume for this purpose.
INST1_DB1_VOL
Contains the user database files.
INST1_DB1_LOG
Contains the database log files (including redo logs, archive logs, background_dump_dest (bdump), core_dump_dest (cdump), and user_dump_dest (udump)).
These LUNs must be accessible from all cluster nodes.
Perform the following tasks to create LUNs on the NetApp filer and to make them accessible from cluster nodes:
Add the filer storage system to the SnapDrive Storage System Management snap-in on the cluster nodes.
Create volumes on the NetApp filer.
Share the volumes.
Create LUNs or virtual disks on the shared volumes.
Refer to NetApp documentation for instructions on performing these tasks.