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.

Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

⚡ Automating Oracle 19c Database Patching on Windows Server with PowerShell

Applying Oracle patches on Windows often feels repetitive and error-prone — stopping services, updating OPatch, applying patches, running datapatch , and restarting services. To save time ⏱ and reduce mistakes ⚠, I created a PowerShell automation script that performs the patching process end-to-end 🚀. 🔹 Why Automate Oracle Patching? ⏱ Save time by automating repetitive steps ⚙ Avoid manual errors during patching 📜 Maintain logs for auditing and troubleshooting 🛡 Ensure consistent, reliable patching 🔹 Full PowerShell Script # --- CONFIGURATION --- $oracleHome = "c:\users\administrator\downloads\v982656-01" # Change if this is not your actual Oracle Home! $patchDir = "C:\Users\Administrator\Downloads\p37962957_190000_MSWIN-x86-64\37962957" #update the Patchfile directory $opatchDir = "$oracleHome\OPatch" $opatchZip = "C:\Users\Administrator\Downloads\p6880880_190000_MSWIN-x86-64.zip" #Based on your setup update Opatch di...
Post a Comment
Read more

Installing pgBackRest on Linux (RHEL 9 / Rocky / AlmaLinux)

 When you work with PostgreSQL in real environments, one thing becomes very clear very quickly: Backups are not optional. It doesn’t matter how stable your database is — failures happen. Disks crash Files get corrupted Someone runs the wrong delete query A patch goes wrong A standby needs rebuilding. So having a proper backup strategy is not just good practice, it’s survival. That’s exactly why tools like pgBackRest are so widely used in PostgreSQL production systems. In this post, I’ll walk through a simple installation of pgBackRest on a Linux server (RHEL 9 / Rocky Linux / AlmaLinux). Why pgBackRest? PostgreSQL already provides tools like: pg_dump pg_basebackup And yes, they work. But once your database grows, or you start managing HA setups, these tools start feeling limited. pgBackRest is built for serious PostgreSQL backup requirements. Some of the reasons it stands out: Supports full, differential, and incremental backups Built-in compre...
Post a Comment
Read more