Database Reference
In-Depth Information
Node 'knewracn4' active role is 'hub'
Node 'knewracn6' active role is 'leaf'
Node 'knewracn5' active role is 'leaf'
Node 'knewracn8' active role is 'leaf'
Node 'knewracn7' active role is 'leaf'
Changing the Existing Cluster Mode to Flex Cluster
If your Clusterware was originally installed as a standard cluster, you can change its cluster mode from the standard
cluster to a Flex Cluster. However, before you make this change, you need to first make sure that as a prerequisite the
GNS is configured with a fixed VIP. The GNS may already be configured during the Clusterware installation. You need
to ensure that the GNS is configured with a fixed VIP with the srvctl command, for example:
$ srvctl status gns
GNS is running on node knewracn2
GNS is enabled on node knewracn2
If the GNS is not enabled, you will see a result like this:
$ srvctl status gns
PRCS-1065 : GNS is not configured.
Then, as the prerequisite, you need to convert this cluster from non-GNS cluster to GNS cluster by running the
following command as the root user with a valid VIP address and a domain name:
#srvctl add gns -vip <VIP_address> -domain <doman_name>
And you need to enable Oracle Flex ASM option with ASMCA. Refer to the next section, Then, run this command
as root to change the cluster mode from the standard mode to Flex Cluster mode:
#crsctl set cluster mode flex
You need to stop and restart Oracle Clusterware as root on each node:
#crsctl stop crs
#crsctl start crs -wait
Managing Oracle Flex Clusters
You can use various Oracle Clusterware Control (CRSCTL) utility commands to manage the Oracle Flex Clusters.
In a Flex Cluster, you can change the role of a node between Hub node and Leaf node by running this crsctl command
on the local node as the root user:
# crsctl set node role {hub | leaf}
Then, as the root user, you need to stop and restart Oracle High Availability Services on the node where you
changed the role:
# crsctl stop crs
# crsctl start crs -wait
