Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

How To Change Cluster Name In Oracle RAC

Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
  • User AvatarKiran Dalvi
  • 01 Sep, 2023
  • 0 Comments
  • 2 Mins Read

How To Change Cluster Name In Oracle RAC

How To Change Cluster Name In Oracle RAC

Changing the cluster_name in ORACLE RAC means grid infrastructure need to be reconfigured( which is a complex activity). You will need downtime for this activity and you will lose your cluster services, But good thing is you won’t lose your data. The data (ASM DISKS) will be intact. In the below example,  you will see , how to do that.

In the below example we will change the cluster_name from clsrac to clsrep.

NODES        = classbtc03(local node), classbtc04 ( remote node)
GRID VERSION = 19C
GRID_HOME    = /u02/app/grid/product/19C/dbhome
ORACLE_HOME  = /u01/app/oracle/product/19C/dbhome
CLUSTER_NAME = clsrac
DATABASES    = racdb

1. Check the existing cluster_name:
1
[root@install]#  /u02/app/grid/product/19C/dbhome/bin/olsnodes -c
2. Notedown cluster resource details and the config of database and services.
1
[oracle@node1 ~]$ crsctl stat res -t
3. Deconfig the remote node:[ as root user ]
1
[root@node2 install]# /u02/app/grid/product/19C/dbhome/crs/install/rootcrs.sh  -deconfig -force -verbose
If you have more than 2 nodes, then run the same on other nodes , excluding the local node.
4. Deconfig on local node: [ as root ]
1
[root@node1 install]# /u02/app/grid/product/19C/dbhome/crs/install/rootcrs.sh -deconfig -force -verbose -lastnode
5.Delete the grid_home directory from both nodes:
1
2
3
4
echo $ORACLE_HOME
/u02/app/grid/product/19C/dbhome
cd /u02/app
rm -rf oracle
6. Change the permission of mount point from root to grid_owner on both nodes:
1
2
cd /
chown oracle:oinstall u02
7. Remove the crs=true keyword from inventory.xml file from both nodes:
1
2
3
4
5
[oracle@node2 gpnp]$ cd /u02/app/oraInventory/ContentsXML
 
[oracle@node2 ContentsXML]$ cat inventory.xml | grep CRS
 
Remove the CRS=”true” keyword. [oracle@node2 ContentsXML]$ cat inventory.xml | grep CRS

8.remove the entry for grid_home from oratab entry [ both nodes]
cat /etc/oratab

 

 

9. Copy the grid software to grid_home location and unzip it.  
1
2
3
4
mkdir -p /u02/app/grid/product/19C/dbhome/
cp grid_home19c.zip /u02/app/grid/product/19C/dbhome/
cd /u02/app/grid/product/19C/dbhome/
unzip grid_home19c.zip

10. Start the gridsetup installer in GUI mode:[ on local node as oracle user]
./gridSetup.sh
Follow all steps at GUI & complete grid installation
Now your grid setup is completed.

11. Verify the cluster_name:

[root@node2 install]# /u02/app/grid/product/19C/dbhome/bin/olsnodes -c
clspre
We can see the cluster_name has been updated as per our requirement.

11. Scan the asm disks on both nodes:[ as root user]
1
2
[root]# oracleasm scandisks
[root ~]$ oracleasm scandisks
12.Mount the diskgroups on both nodes:
1
2
3
4
5
6
7
8
echo $ORACLE_SID=+ASM1
echo $ORACLE_HOME=/u02/app/grid/product/19C/dbhome
[oracle@node1]$ asmcmd
 
ASMCMD> lsdg
ASMCMD > mount -a
 
ASMCMD> lsdg
We can see the all diskgroups are intact.
13 .Now register the database in the CRS and start it.
1
2
3
4
5
6
7
[oracle@node1 dbs]$ srvctl add database -d classrep -oraclehome /oracle/app/oracle/product/19.3.0/dbhome_1
[oracle@node1 dbs]$ srvctl add instance -d classrep -i classrep1 -node node1
[oracle@node1 dbs]$ srvctl add instance -d classrep -i classrep2 -node node2
[oracle@node1 dbs]$ srvctl modify database -db classrep -spfile '+DATA/classrep/PARAMETERFILE/spfile.263.1070311859'
 
[oracle@node1 dbs]$ srvctl config database -d classrep
[oracle@node1 dbs]$ srvctl start database -db classrep
14.Connect the the database and verify details:
1
2
SQL> select name,open_mode from gv$database;
SQL> select file_name from dba_data_files;