Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • set_env_dba Linux/Unix
  • Kernel Parameters for Solaris Linux/Unix
  • Find Multiple levels of object dependencies : depen.sql Oracle
  • SQL Server: How to see historical transactions SQL Server
  • Global Unique Identifier Generation in Oracle 9.2 SYS_GUID() Oracle
  • chk_space_SID.ksh Linux/Unix
  • Updated LCK.SQL file. Oracle
  • All About oracle password and security from metalink Oracle
  • rm_backup_arch_file.ksh Linux/Unix
  • Find Stale DR Physical Standby Oracle
  • alter database backup controlfile to trace Oracle
  • export import with parameter file. Oracle
  • Pending Transaction Neighbors Script Oracle
  • Oracle Identifiers Oracle
  • Find nth max and min. Oracle

Running PDB on single node in RAC

Posted on 09-Apr-2026 By Admin

Configuring a PDB to Listen on a Specific RAC Node in Oracle Database

In Oracle Real Application Clusters (RAC) environments, you may need to restrict a Pluggable Database (PDB) to run on specific nodes. Here’s how to configure PDB MYPDB to listen only on node1:

Step-by-Step Configuration

1. Configure the PDB State on Node 1

First, ensure the PDB is open on your preferred node and save that state:

-- Connect to the PDB on Node 1
ALTER SESSION SET CONTAINER = MYPDB;

-- Open the PDB if it's not already open
ALTER PLUGGABLE DATABASE OPEN;

-- Save the open state for future restarts
ALTER PLUGGABLE DATABASE SAVE STATE;

The SAVE STATE command ensures the PDB will automatically open when the CDB starts on this node.

2. Configure the PDB State on Node 2

Next, explicitly close the PDB on other nodes and discard any saved state:

-- Connect to the PDB on Node 2
ALTER SESSION SET CONTAINER = MYPDB;

-- Close the PDB immediately
ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE;

-- Discard any saved state for this PDB on Node 2
ALTER PLUGGABLE DATABASE DISCARD STATE;

The DISCARD STATE command removes any previously saved state, preventing the PDB from automatically opening on this node.

3. Configure the Service for Node Affinity

Finally, modify the service to ensure it only runs on your preferred node:

srvctl modify service -db node1 -service node1_mypdb.paas.oracle.com \
-modifyconfig -preferred node1 -available ""

This command:
– Sets node1 as the preferred node for the service
– Removes any available nodes (empty string after -available)
– Ensures the service (and thus the PDB) will only run on node1

Verification

After making these changes, verify your configuration:

  1. Check PDB status on each node:
    sql
    SELECT inst_id, name, open_mode FROM gv$pdbs;

  2. Verify service configuration:
    bash
    srvctl config service -db node1 -service node1_mypdb.paas.oracle.com

Important Notes

  • This configuration is particularly useful for:
  • License optimization (running certain PDBs only on licensed nodes)
  • Performance isolation
  • Workload separation
  • Remember that in a RAC environment, the PDB files must still be accessible from all nodes
  • The service name (node1_mypdb.paas.oracle.com) should match your actual service name

Would you like me to elaborate on any specific aspect of this configuration?

Oracle, RAC, SQL scripts

Post navigation

Previous Post: find_arc.sql

Related Posts

  • RMAN : Consistent Backup, Restore and Recovery using RMAN Oracle
  • Jai Shree Ram Oracle
  • Caching sequence in Memory Oracle
  • sql_doing_fts.sql Oracle
  • Find Stale DR Physical Standby Oracle
  • Drop tempfiles from database Oracle

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (400)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (348)
  • SQL Server (6)
  • Uncategorized (3)
  • Videos (0)

Recent Posts

  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026
  • Creating a Container Database using dbaascli08-Apr-2026
  • track_autoupgrade_copy_progress.sql01-Apr-2026
  • refre.sql for multitenant01-Apr-2026
  • prepfiles.sh for step by step generating pending statistics files10-Mar-2026
  • tracksqltime.sql05-Mar-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Roles and Stored Object behaviour Oracle
  • Histogram information Oracle
  • eplan.sql Oracle
  • Difference between SYNC and AFFIRM Oracle
  • Oracle vs MYSQL Architecture differences (For DBAs) MYSQL
  • on IBM-AIX for display Linux/Unix
  • Goldengate document from Porus Oracle
  • Oracle Support Metalink ID 161818.1 Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme