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
- Prerequisites for installing Oracle
- Managing storage using Windows Logical Disk Manager
- Managing storage using NetApp filer
- Configuring Oracle on the first node
- Associating the database with the listener
- Configuring the Oracle database
- 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
- Making the additional agent highly available
Managing storage using Windows Logical Disk Manager
If your configuration uses shared disks and volumes that are managed using Windows Logical Disk Manager (LDM), use the VCS Mount and DiskReservation (DiskRes) agents. If you use LDM to manage non-shared local storage, use the VCS Mount and NativeDisks agents.
Before configuring the storage, review the resource types and attribute definitions of these VCS storage agents (Mount, DiskRes, NativeDisks) described in the Cluster Server Bundled Agents Reference Guide.
The following restrictions apply for storage managed using LDM:
Mount, DiskRes, and NativeDisks agents are supported on VCS for Windows only. These agents are not supported if the storage is managed using Storage Foundation (SFW).
If you are using shared storage, your storage devices must be configured to use SCSI-2 disk reservations. SCSI-3 is not supported.
SCSI support is not required if you are using non-shared storage.
LDM support is not applicable for Disaster Recovery configurations. Currently only HA configurations are supported.
The VCS agent for Oracle requires that you create volumes 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 volume as that of the redo logs.
Arctera recommends that you create separate volumes 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)).
If you are using a shared storage configuration, ensure that these volumes are created on shared storage and are accessible from all cluster nodes.
If you are using a non-shared storage configuration, create these volumes separately on the local storage attached to each cluster node.
Perform the following tasks to configure your storage:
Reserve disks
Create volumes
Mount volumes
Unassign the drive letter
Release the disks