InfoScale™ 9.0 Cluster Server Implementation Guide for Oracle - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Introducing the VCS agents for Oracle and NetApp
    1.  
      About the VCS agents for Oracle and NetApp
    2. About the VCS agent for Oracle
      1.  
        About the Oracle agent
      2.  
        About the Netlsnr agent
      3.  
        About the Info function
      4.  
        About the Action function
    3. About the VCS hardware replication agent for NetApp
      1.  
        About the NetApp Filer agent
      2.  
        About the NetApp SnapDrive agent
      3.  
        About the NetApp SnapMirror agent
    4.  
      How the agent makes Oracle highly available
    5.  
      Typical Oracle configuration in a VCS cluster
  2. Installing and configuring VCS
    1.  
      About installing the VCS agents
    2. Configuring the cluster using the Cluster Configuration Wizard
      1.  
        Configuring notification
      2.  
        Configuring Wide-Area Connector process for global clusters
  3. Installing and configuring Oracle
    1.  
      About installing Oracle
    2. Prerequisites for installing Oracle
      1.  
        Privilege requirements
    3.  
      Installing Oracle
    4.  
      About creating and configuring Oracle
    5.  
      Prerequisites for configuring Oracle
    6.  
      Configuring Microsoft iSCSI initiator
    7. Managing storage using Windows Logical Disk Manager
      1.  
        Reserving disks (if you use Windows LDM)
      2.  
        Creating volumes (if you use Windows LDM)
      3.  
        Mounting volumes (if you use Windows LDM)
      4.  
        Unassigning a drive letter
      5.  
        Releasing disks (if you use Windows LDM)
    8. Managing storage using NetApp filer
      1.  
        Connecting virtual disks to the cluster node
      2.  
        Disconnecting virtual disks from the cluster nodes
    9.  
      Creating a temporary service group
    10. Configuring Oracle on the first node
      1.  
        Dismounting a volume
      2.  
        Bringing the temporary service group online
      3.  
        Creating the Oracle database on shared disks
      4.  
        Creating the listener service
      5.  
        Configuring the listeners to use the virtual IP address
      6. Associating the database with the listener
        1.  
          Prerequisites to associate the databases with the listeners
      7. Configuring the Oracle database
        1.  
          Updating the tnsnames.ora files
        2.  
          If you use a PFILE (initSID.ora)
        3.  
          If you use an SPFILE
        4.  
          Modifying the PFILE (Oracle 9i only)
        5.  
          Modifying the SPFILE
        6.  
          Moving the initialization file to shared disks
        7.  
          Setting the Oracle database parameters
        8.  
          Verifying the initialization file settings
      8.  
        Configuring the Oracle and listener services
      9.  
        Disconnecting virtual disks from the first node
      10.  
        Releasing disks (if you use Windows LDM)
    11.  
      Configuring Oracle on failover nodes
  4. Configuring the Oracle service group
    1.  
      About configuring the Oracle service group
    2.  
      Deleting the temporary service group
    3. About configuring the Oracle service group using the wizard
      1.  
        Prerequisites for configuring the Oracle service group
      2. Creating an Oracle service group using the wizard
        1.  
          About the modifications required for tagged VLAN or teamed network
      3.  
        Configuring dependent services
    4. Verifying the Oracle service group configuration
      1.  
        Bringing the service group online
      2.  
        Taking the service group offline
      3.  
        Switching the service group
      4.  
        Disabling the service group
    5.  
      Reconfiguring the Oracle service group
  5. Administering the Oracle service group
    1.  
      About administering the Oracle service group
    2. About modifying an Oracle service group
      1.  
        Prerequisites for modifying the Oracle service group
      2.  
        Modifying an Oracle service group
    3.  
      Deleting an Oracle service group
    4. Configuring detail monitoring
      1.  
        Enabling detail monitoring
      2.  
        Disabling detail monitoring
  6. Troubleshooting
    1.  
      About troubleshooting VCS agents
    2.  
      Troubleshooting common problems
    3. VCS logging
      1.  
        VCS Cluster Configuration Wizard (VCW) logs
      2.  
        VCWsilent logs
    4. Agent error messages and descriptions
      1.  
        Oracle agent
      2.  
        Netlsnr agent
      3.  
        NetApp agents
  7. Appendix A. Resource type definitions
    1.  
      About resource type definitions
    2. Oracle agent
      1.  
        Resource type definition
      2.  
        Attribute definitions
    3. Netlsnr agent
      1.  
        Resource type definition
      2.  
        Attribute definitions
  8. Appendix B. Sample configuration
    1.  
      About Oracle sample configurations
    2. Sample configuration file
      1.  
        Sample configuration file
      2.  
        Sample configuration file using iSCSI initiator
      3.  
        Sample configuration file using FC initiator
  9. Appendix C. Oracle Enterprise Manager 10g Grid Control with VCS
    1.  
      About Oracle Enterprise Manager 10g Grid Control with VCS
    2.  
      Installing the VCS agent for Oracle
    3.  
      Installing Oracle Enterprise Manager server
    4.  
      Installing Oracle
    5.  
      Installing the Oracle Management Agent
    6.  
      Creating and configuring Oracle database and listener on the first node
    7.  
      Configuring Oracle on failover nodes
    8.  
      Configuring the Oracle service group
    9.  
      Configuring a virtual network name
    10.  
      Configuring the listener for virtual network name
    11.  
      Configuring the database service for virtual network name
    12.  
      Configuring an additional Oracle management agent
    13.  
      Adding the database to the OEM 10g Grid Control
    14. Making the additional agent highly available
      1.  
        Sample Configuration

About the NetApp SnapMirror agent

The NetApp SnapMirror agent monitors the replication state of filer devices. When a failover occurs, the agent reverses the direction of replication. The agent supports the replication modes supported by NetApp. The agent supports asynchronous, semi-synchronous, and synchronous modes of replication. You can set the mode of replication using the SyncMode agent attribute.

NetApp SnapMirror agent functions

The NetApp SnapMirror agent functions are as follows:

Online

If the state of the local filer device is SOURCE, the agent creates a lock file to indicate that the resource can come online. This effectively makes the devices writable for the application.

If the state of the local filer is SNAPMIRRORED, the agent attempts to reverse the direction of replication by changing the state of the local filer to SOURCE and that of the original source to SNAPMIRRORED.

If the original source filer is down, the agent performs a mirror break-off to enable local write access, if the filer is not already broken off.

If the original source returns to life, you must resynchronize the data manually. The online function touches a lock file if read-write access is enabled successfully.

Offline

Removes the lock file. The agent does not perform any filer operations because an offline entry point does not necessarily indicate an intention to give up the devices.

Monitor

Verifies that the lock file exists. If the lock file exists, the monitor function reports the status of the resource as online. If the lock file does not exist, the monitor function reports the status of the resource as offline.

Open

Removes the lock file thereby preventing potential concurrency violation if the group fails over to another node.

Note:

The agent does not remove the lock file if the agent is started after an hastop -force command.

Clean

Removes the lock file. No filer operations are performed as taking the resource offline does not indicate a pending role swap.

Action function

Use the Action function to perform predefined actions on a resource. To perform an action on a resource, type the following command:

hares -action <SnapMirror_resname> <token> [-actionargs <arg1> ...] [-sys <system>] [-clus <cluster> ]

The following table lists the action supported by the NetAppSnapMirror agent.

Table: Actions supported by NetAppSnapMirror agent

Token for Action

Description

fbsync

Resynchronizes an original source volume with a broken-off volume. After synchronization, the original source volume becomes the target volume.

The broken-off volume was initially the target volume, but was broken off as a result of a take over.

To synchronize volumes, type the following at the command prompt:

hares -action SnapMirror_resname fbsync -sys node_name

Where, SnapMirror_resname represents the name of the SnapMirror resource and node_name represents the node on which the service group is online.

Run the action for each SnapMirror resource.

You can also add custom actions for the agents. Refer to the Cluster Server Agent Developer's Guide for more information.

NetApp SnapMirror agent resource type definition and attribute definitions are as follows. This information will assist you during the agent configuration.

NetAppSnapMirror agent resource type definition

NetApp SnapMirror agent is configured as a resource of type NetAppSnapMirror.

type NetAppSnapMirror (
        static keylist SupportedActions = { fbsync }
        static int MonitorInterval = 300
        static int NumThreads = 1
        static i18nstr ArgList[] = { FilerResName, 
        "FilerResName:FilerName", "FilerResName:StorageIP",
        VolumeName, SnapMirrorArguments, SnapMirrorSchedule, 
        AppResName, VisibilityFrequency, SyncMode }
        str FilerResName
        str VolumeName
        str SnapMirrorArguments
        str SnapMirrorSchedule
        str AppResName
								int VisibilityFrequency = 180
								str SyncMode = async
    )
NetAppSnapMirror agent attribute definitions

The following table describes the NetApp SnapMirror agent attributes.

Attribute

Description

FilerResName

Name of the VCS NetAppFiler-type resource in the group.

Type and dimension: string-scalar

VolumeName

Name of the filer volume containing the virtual disk. This is the volume that is to be mounted. Define the volume name in the same case as on the filer.

Type and dimension: string-scalar

SnapMirrorArguments

Specifies the SnapMirror arguments such as maximum transfer speed and restart mode.

The format for this attribute is:

<RestartMode> MaxSpeed

MaxSpeed is an optional parameter. The RestartMode parameter can have the following values:

  • Always

  • Never

  • Default

Setting the RestartMode parameter value to default indicates schedule priority.

Default value of RestartMode parameter is 'Default'

Example: Always MaxSpeed

Type and dimension: string-scalar

SnapMirrorSchedule

Specifies the schedule the destination uses for updating data. Do not assign a value for this attribute if you use SnapManager.

The schedule is in the following format:

minute hour dayofmonth dayofweek

Each field is separated by a space.

Refer to the NetApp documentation for more details on the rules for each of these schedule fields.

By default, this attribute does not have any value.

Type and dimension: string-scalar

AppResName

Name of the resource configured to monitor the application being made highly available.

Type and dimension: string-scalar

SyncMode

Specifies the mode of replication for the mirror.

This attribute can have the following values:

  • async: Indicates that the mirror should be configured in the asynchronous mode.

  • semi-sync: Indicates that the mirror should be configured in the semi-synchronous mode.

  • sync: Indicates that the mirror should be configured in the synchronous mode.

The default is async (asynchronous) mode.

Type and dimension: string-scalar

VisibilityFrequency

Specifies how often the source snapshot will be visible on the destination mirror. It controls the value of visibility_interval in the snapmirror.conf file.

The default value is 180 seconds.

This attribute is applicable only if the mirror is configured in synchronous or semi-synchronous mode.

Type and dimension: string-scalar