You have completed a rolling conversion from DNS to GNS cluster resolution from the database and
cluster resources end. The remaining are the configuration changes to be done from the client side.
Which two items need to be taken into account to achieve a successful connection?
A.
For each client using a SCAN, change the SCAN the client uses so that the client uses the SCAN in
the domain delegated to GNS.
B.
For each client using VIP names, change the VIP name on each client so that they use the same
server VIP name, but with the domain name in the domain delegated to GNS.
C.
There is no need to change anything in client configuration as the combination of TAF and ONS
will automatically take care of reaching the correct nodes.
D.
All the nodes in the cluster need to be bounced one after the other in order for the changes to be
completed as it is not possible to do it online.
Explanation:
For each client using a SCAN, change the SCAN that the client uses so that the client uses the SCAN in
the domain delegated to GNS. For each client using VIP names, change the VIP name on each client
so that they use the same server VIP name, but with the domain name in the domain delegated to
GNS.https://docs.oracle.com/database/121/CWADD/admin.htm#CWADD92605
Correct
A C >>>
1. Log in as the Grid user (grid), and use the following Cluster Verification Utility to check the status for moving the cluster to GNS, where nodelist is a comma-delimited list of cluster member nodes:
$ cluvfy stage –pre crsinst –n nodelist
2. As the Grid user, check the integrity of the GNS configuration using the following commands, where domain is the domain delegated to GNS for resolution, and gns_vip is the GNS VIP:
$ cluvfy comp gns -precrsinst -domain domain -vip gns_vip
3.Log in as root, and use the following SRVCTL command to configure the GNS resource, where domain_name is the domain that your network administrator has configured your DNS to delegate for resolution to GNS, and ip_address is the IP address on which GNS listens for DNS requests:
# srvctl add gns -domain domain_name -vip ip_address
4. Use the following command to start GNS:GNS starts and registers VIP and SCAN names.
# srvctl start gns
5.As root, use the following command to change the network CRS resource to support a mixed mode of static and DHCP network addresses:The necessary VIP addresses are obtained from the DHCP server, and brought up.
# srvctl modify network -nettype MIXED
6.As the Grid user, enter the following command to ensure that Oracle Clusterware is using the new GNS, dynamic addresses, and listener end points:
cluvfy stage -post crsinst -n all
************************
7.After the verification succeeds, change the remote endpoints that previously used the SCAN or VIPs resolved through the DNS to use the SCAN and VIPs resolved through GNS.
For each client using a SCAN, change the SCAN that the client uses so that the client uses the SCAN in the domain delegated to GNS.
For each client using VIP names, change the VIP name on each client so that they use the same server VIP name, but with the domain name in the domain delegated to GNS.
************
8. Enter the following command as root to update the system with the SCAN name in the GNS subdomain:
# srvctl modify scan -scanname scan_name.gns_domain
9. Disable the static addresses once all clients are using the dynamic addresses, as follows:
$ srvctl modify network -nettype DHCP
Sorry for typo..
A & B ( AS explained in step 7)