Skip to main content

How to rename the Hostname in an Oracle RAC Cluster

Renaming a hostname in an Oracle Real Application Clusters (RAC) environment requires careful execution to ensure database continuity. This guide demonstrates how to rename the hostname in a two-node RAC cluster (devdb-01, devdb-02) by modifying devdb-01 to devdb-new-01.

  • RAC User = DB HOME Owner

  • GI User = GI HOME Owner or root

Step 1: Remove the DB Instance from the Old Node

On devdb-01, connect as the RAC user and remove the running database instance:

a. srvctl disable instance -db <db_unique_name> -instance <inst_name>
b. srvctl stop instance -db <db_unique_name> {-node <old_node_name> | -instance <inst_name>} -stopoption NORMAL -failover
c. srvctl remove instance -db <db_unique_name> -instance <inst_name> -force

Step 2: Deconfigure Oracle Clusterware on the Old Node

On devdb-01, connect as the root user and execute:

$GI_HOME/crs/install/rootcrs.sh -deconfig -force

Step 3: Remove the Node from the Cluster

On devdb-02, connect as the root user and run:

Syntax:

$GI_HOME/bin/crsctl delete node -n <Node1>

Example:

$GI_HOME/bin/crsctl delete node -n devdb-01

Step 4: Rename the Host

On devdb-01, connect as the root user and modify the hostname using the standard procedure for your OS.

Step 5: Add the Node with the New Hostname

On devdb-01, connect as the Grid user and execute the following command:

Syntax:

$GI_HOME/addnode/addnode.sh -silent -noCopy "CLUSTER_NEW_NODES=<N1>" "CLUSTER_NEW_VIRTUAL_HOSTNAMES=<N1-vip>" "CLUSTER_NEW_NODE_ROLES=hub"

Example:

$GI_HOME/addnode/addnode.sh -silent -noCopy "CLUSTER_NEW_NODES=devdb-new-01" "CLUSTER_NEW_VIRTUAL_HOSTNAMES=devdb-new-01-vip" "CLUSTER_NEW_NODE_ROLES=hub"

Step 6: Run the Root Script

On devdb-new-01, connect as the root user and execute:

$GI_HOME/root.sh  # This may take around 5 minutes

Step 7: Recreate the DB Instance on the Renamed Node

On devdb-new-01, connect as the RAC user and create a new database instance:

Syntax:

srvctl add instance -db <db_unique_name> -instance <inst_name> -node <new_node_name>

Example:

srvctl add instance -db <db_unique_name> -instance <inst_name> -node devdb-new-01

Following these steps ensures a smooth hostname transition in an Oracle RAC environment, maintaining high availability and minimal downtime. Always verify the changes before proceeding with production deployments.

Comments

Popular posts from this blog

🚀 Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? 💡 In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 🔥 The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: 🔗 Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...

🚀 DB BOT: Real-Time Oracle & GoldenGate Monitoring in Slack

In today's fast-paced DevOps environment, quick access to database metrics is essential. This blog will walk you through creating a Slack bot that provides real-time monitoring of Oracle databases and Golden Gate replication. With simple slash commands, your team can check tablespace usage, Flash Recovery Area status, and Golden Gate replication health directly in Slack. Project Overview Our "DB Bot" offers these key capabilities: Monitor tablespace usage across multiple Oracle databases Check Flash Recovery Area (FRA) status on multiple databases View GoldenGate process status across different servers List GoldenGate credential stores Monitor replication lag in GoldenGate Prerequisites Node.js v14+ Python 3.6+ Oracle client libraries (instantclient_21_19) Access to Oracle databases and GoldenGate servers A Slack workspace with permissions to add apps   Project Structure oracle-slack-bot...

Oracle Golden Gate Bi-directional Replication Implementation Guide

Oracle GoldenGate (OGG) is a comprehensive software package for real-time data integration and replication in heterogeneous IT environments. Bi-directional replication enables organizations to maintain synchronized data across multiple data centers, providing high availability, disaster recovery, and load distribution capabilities. This detailed guide provides step-by-step instructions for implementing Oracle GoldenGate bi-directional replication between two Oracle databases. Architecture Overview In this setup, we'll configure: TestDC1 : Primary data center with TestDB1 TestDC2 : Secondary data center with TestDB2 Bi-directional sync : Changes flow in both directions with conflict resolution Step 1: Software Installation ⚠️ SERVER EXECUTION: Perform these steps on BOTH TestDC1 and TestDC2 servers Step 1.1: Download and Prepare Software First, create the necessary directory structure and prepare for installation: # Create directory for the software mkdir /data01/ogg_setup cd /d...