4 Oracle Clusterware to Manage Generic Applications

You can configure Oracle Grid Infrastructure with minimum network and storage requirements to manage generic applications.

About Oracle Grid Infrastructure to Manage Generic Applications

An Oracle Grid Infrastructure deployment to manage generic applications can host any applications for which you want to enable dual instance management, failover, and high availability.

Oracle Grid Infrastructure deployment to manage generic applications enables you to make your applications highly available without requiring Virtual IP addresses and shared storage. This deployment model can also extend high availability and single server rolling patching capabilities to single-instance Oracle databases.

You can configure Oracle Grid Infrastructure to manage generic applications without SCAN, GNS, VIPs, and without using separate network interfaces for Oracle ASM, private, and public communication. Such clusters can manage single-instance Oracle databases, any generic applications, or third-party databases using only one network interface.

Note:

You can easily convert this deployment model to an Oracle Grid Infrastructure cluster to manage Oracle RAC databases by adding shared storage and VIP.

Enabling Oracle RAC Databases on a Generic Application Cluster

To enable creating Oracle Real Application Clusters (Oracle RAC) databases on an Oracle Grid Infrastructure deployment that was configured to manage generic applications, you must add VIP, SCAN, and SCAN listener to your cluster.

If you deploy Oracle Grid Infrastructure to manage generic applications, then you can not create Oracle RAC databases on such clusters without creating VIP, SCAN, and SCAN listener.

Note:

This procedure converts the general purpose cluster to a full Oracle RAC cluster.
  1. As the root user, add a VIP to each Oracle Clusterware node:
    # srvctl modify vip -node node_name -address {VIP_name|ip}/netmask[/if1[|if2|...]] 
    [-netnum network_number] [-skip] [-verbose]

    Where:

    • node_name is the name of the cluster node.

    • vip_name/netmask is the name of a local VIP that resolves to both IPv4 and IPv6 addresses. You can specify one VIP_name or address, along with an IPv4 netmask or IPv6 prefix length.

    • network_number is the network number from which VIPs are obtained. The default network number is 1.

  2. As the grid user, add the SCAN to the cluster.
    $ srvctl add scan -scanname myscan.example.com
  3. Create a SCAN listener that is exclusive to this cluster.
    $ srvctl add scan_listener [-netnum  network_number] [-listener listener_name] [-skip] 
    [-endpoints [TCP:]port_list[/IPC:<key>][/NMP:pipe_name][/TCPS:s_port][/SDP:port][/EXADIRECT:port]] 
    [-invitednodes "node_list"] [-invitedsubnets "subnet_list"] [-clientcluster cluster_name] [-clientdata file_name]
  4. Start SCAN and SCAN listener.
    $ srvctl start scan
    $ srvctl start scan_listener
  5. Check the cluster node network configuration to ensure that all the resources are online and stable.
    $ crsctl stat res -t
    --------------------------------------------------------------------------------
    Name           Target  State        Server                      State details
    --------------------------------------------------------------------------------
    Local Resources
    --------------------------------------------------------------------------------
    ora.LISTENER.lsnr
                   ONLINE  ONLINE       node1                       STABLE
                   ONLINE  ONLINE       node2                       STABLE 
    ora.net1.network
                   ONLINE  ONLINE       node1                       STABLE
                   ONLINE  ONLINE       node2                       STABLE  
    ora.ons
                   ONLINE  ONLINE       node1                       STABLE
                   ONLINE  ONLINE       node2                       STABLE  
    --------------------------------------------------------------------------------
    Cluster Resources
    --------------------------------------------------------------------------------
    ora.LISTENER_SCAN1.lsnr
          1        ONLINE  ONLINE                                   STABLE
    ora.LISTENER_SCAN2.lsnr
          1        ONLINE  ONLINE                                   STABLE
    ora.LISTENER_SCAN3.lsnr
          1        ONLINE  ONLINE                                   STABLE
    ora.node1.vip
          1        ONLINE  ONLINE                                   STABLE
    ora.node2.vip
          1        ONLINE  ONLINE                                   STABLE
    ora.scan1.vip
          1        ONLINE  ONLINE                                   STABLE
    ora.scan2.vip
          1        ONLINE  ONLINE                                   STABLE
    ora.scan3.vip
          1        ONLINE  ONLINE                                   STABLE
    --------------------------------------------------------------------------------
  6. Use Oracle DBCA to create an Oracle RAC database on your cluster.