Grid Infrastructure version: 18.104.22.168 (OCT 2016 PSU)
Platform : Oracle Linux 6.5
DB version: 22.214.171.124 (OCT 2016 PSU)
--- Cluster1 (production)
In production, I have a highly critical 3-node RAC DB using the following SCAN configuration.
SCAN Name: danprd-scan.apac.nsroot.net
SCAN IP1 : 126.96.36.199
SCAN IP2 : 188.8.131.52
SCAN IP3 : 184.108.40.206
-- Cluster2 ( to-be production )
I am going to migrate the above DB (using RMAN restore) to this new cluster (220.127.116.11) which uses the following SCAN configuration
SCAN Name: danwmprd-scan.apac.nsroot.net
SCAN IP1 : 18.104.22.168
SCAN IP2 : 22.214.171.124
SCAN IP3 : 126.96.36.199
+++ Potential Problem ++++
In the middleware tier, there are around 10 places where the JDBC URLs are referred. Middleware team can update all these JDBC URLs with the new SCAN name.
But, middleware team say that there could be more configuration files with JDBC URLs which THEY MAY NOT AWARE OF !!! After migrating the DB to the new cluster and if all the application modules cannot connect to the DB in the new cluster because some JDBC URLs were not updated with new SCAN name, then the business will have huge monetary losses.
So, If such a situation arises , I want to change the SCAN name of Cluster2 to that of the production one (after shutting down the production cluster). Since the application only uses the SCAN name , I don't want to change the IPs of Cluster2 to that Cluster1(Production)
1) Is it even possible to change SCAN name and IP of a cluster ?
2) Is it recommended to change SCAN name and IP of a cluster ?
Message was edited by: spiral Removed Changing the IP of Cluster2 as it not needed