 | ||
| Sample configuration for ASM disks as raw disks | ||
|---|---|---|
| Prev | Sample Oracle ASM configurations | Next |
If you use raw devices as ASM disks, you can configure your service group in the following way:
Oracle and ASMDG resources as parent failover service groups, and ASMInst resource as parallel service group
The service groups are made dependent using an Online Local Firm dependency.
Figure: Dependency graph with ASMInst resource as a parallel service group describes a typical service group with ASMInst resource as a parallel service group.
The Oracle ASM instance and ASM disk groups in the cluster are configured as resources of type ASMInst and ASMDG respectively. The ASMInst agent is configured as parallel service group, asminstgrp.
The virtual IP address for the service group is configured using the IP and NIC resource types. The Oracle and ASMDG resources are configured as failover service group, oraasm_grp. The Oracle server can be started after each of these resources is brought online.
The oraasm_grp is made dependent on the asminstgrp using an Online Local Firm dependency.
Figure: Dependency graph for Oracle ASM with multiple Oracle instances on a node describes a typical service group with multiple Oracle instances sharing an ASMInst resource that is configured as a parallel service group.
If you have multiple Oracle instances, a failover service group is configured for each Oracle instance. The Oracle service groups share a single ASM instance that is configured as a parallel service group. The Oracle service groups are made dependent on the ASMInst service group using an Online Local Firm dependency. However, each database must use exclusive ASM disk groups, so that the Cluster Server agent for Oracle can fail over the disk group.
