Pluggable Database Hybrid Read-Only Mode

Modern databases must strike a careful balance between data protection and operational flexibility. On one hand, many workloads—especially data warehouses and reporting systems—benefit from running in read-only mode to guarantee data consistency and prevent accidental changes. On the other hand, database administrators still need the freedom to perform maintenance, patching, and monitoring without constant downtime.

This is exactly where Pluggable Database (PDB) Hybrid Read-Only Mode comes in. Introduced as part of Oracle’s multitenant security and manageability enhancements, this feature allows a PDB to behave as read-only for some users while remaining read/write for others, all at the same time.

In this article, we’ll explore what hybrid read-only mode is, why it exists, how it works, and when you should use it—using practical examples and real-world scenarios.

---

The Problem with Traditional Read-Only Mode

Before hybrid read-only mode, database administrators had a clear but limiting choice:

• Open a PDB in READ ONLY
• Or open it in READ WRITE

When a PDB is opened in traditional read-only mode, everything becomes read-only:

• Application tables
• Data dictionary
• SYSAUX
• Statistics metadata

This creates a major operational issue.

You cannot:

• Collect optimizer statistics
• Perform maintenance tasks
• Run patching operations
• Use many monitoring and diagnostic tools

As a result, administrators are forced to:

• Hard-tune workloads in advance
• Bounce the PDB frequently (read-only → read/write → read-only)
• Accept maintenance windows and downtime

In environments like data warehouses, analytics platforms, or cloud databases, this approach simply doesn’t scale.

---

What Is Hybrid Read-Only Mode?

Hybrid read-only mode is a smarter evolution of traditional read-only access.

With this mode enabled:

• Local users (including local PDB administrators) see the PDB as read-only
• Common users (CDB-level users) see the same PDB as read/write

In simple terms:

The access mode depends on who is connected, not on the database itself.

This means applications and local users are fully protected from making changes, while DBAs and automated maintenance jobs can continue working without interruption.

---

Why Hybrid Read-Only Mode Matters

Hybrid read-only mode is not just a convenience feature—it’s a security and availability enhancement.

Key Benefits

1. Strong Data Protection
   Applications and local users cannot modify data, even if they have powerful local privileges.
2. No Maintenance Downtime
   DBAs can collect statistics, run diagnostics, and apply patches without switching modes.
3. Cloud-Ready Operations
   Cloud environments require frequent patching. Hybrid read-only mode avoids forced outages.
4. Operational Simplicity
   No more repeated shutdowns just to switch between read-only and read/write.

---

How User Type Controls Access

The magic of hybrid read-only mode lies in Oracle’s multitenant user model.

Local Users

• Created inside the PDB
• Even local users with SYSDBA privileges
• Always restricted to read-only access when hybrid mode is enabled

Common Users

• Created at the CDB level
• Typically used by DBAs and automation tools
• See the PDB as read/write

This separation ensures:

• Applications are safe
• Administrators remain productive

---

Common Use Cases

Hybrid read-only mode shines in several real-world scenarios:

1. Data Warehousing

Data is loaded in batches and then queried heavily. The database remains protected, while DBAs still maintain performance and statistics.

2. Long-Term Read-Only Databases

Some systems stay read-only for months. Hybrid mode avoids operational paralysis during that time.

3. Cloud Environments

Cloud platforms demand continuous patching and monitoring without customer impact.

4. Multi-Tenant Platforms

Shared infrastructure where different teams or applications must not interfere with each other’s data.

---

Enabling Hybrid Read-Only Mode

To enable hybrid read-only mode for a specific PDB:

ALTER PLUGGABLE DATABASE pdb_name OPEN HYBRID READ ONLY;

You can also enable it for all PDBs in the container database:

ALTER PLUGGABLE DATABASE ALL OPEN HYBRID READ ONLY;

⚠️ Note: If the PDB is already open in read/write mode, it must be closed and reopened in hybrid read-only mode.

---

Ending Hybrid Read-Only Mode

One of the biggest advantages of hybrid read-only mode is how easy it is to exit.

To return a PDB to normal read/write mode:

ALTER PLUGGABLE DATABASE pdb_name OPEN READ WRITE FORCE;

No database bounce is required. The FORCE option immediately releases all read-only restrictions.

---

Monitoring Hybrid Read-Only Status

Oracle provides clear visibility into hybrid read-only mode using a new column in the dynamic view:

V$CONTAINER_TOPOLOGY.IS_HYBRID_READ_ONLY

Example query:

SELECT con_name, is_hybrid_read_only
FROM v$container_topology;

CON_NAME                      IS_
----------------------------- ---
CDB$ROOT                      NO
PDB$SEED                      NO
ORCLPDB1                      YES

This allows DBAs to quickly confirm which PDBs are running in hybrid read-only mode.

---

Example Walkthrough

Let’s summarize a practical scenario:

1. Initial State
   • PDB PDBSEC is open in READ WRITE
   • Hybrid read-only mode is disabled
2. Enable Hybrid Mode
   • Close PDBSEC
   • Reopen it in hybrid read-only mode
   • IS_HYBRID_READ_ONLY = YES
3. Local User Test
   • Connect as local schema owner (HR)
   • Attempt an UPDATE
   • ❌ Fails with read-only error

sqlplus hr/oracle123@orclpdb1

SQL*Plus: Release 23.26.1.0.0 - Production on Fri Feb 6 09:01:37 2026
Version 23.26.1.0.0

Copyright (c) 1982, 2025, Oracle.  All rights reserved.

Last Successful login time: Fri Feb 06 2026 08:58:44 +05:30

Connected to:
Oracle AI Database 26ai Enterprise Edition Release 23.26.1.0.0 - Production
Version 23.26.1.0.0

SQL> select * from regions;

 REGION_ID REGION_NAME
---------- -------------------------
         1 Europe
         2 Americas
         3 Asia
         4 Middle East and Africa

SQL> UPDATE regions SET region_name = 'Europe' WHERE region_id = 5;
UPDATE regions SET region_name = 'Europe' WHERE region_id = 5
       *
ERROR at line 1:
ORA-16000: Attempting to modify database or pluggable database that is open for
read-only access.
Help: https://docs.oracle.com/error-help/db/ora-16000/

1. Common User Test
   • Connect as SYSTEM (common user)
   • Perform updates and maintenance
   • ✅ Succeeds

SQL> conn system/*******@orclpdb1
Connected.
SQL> UPDATE hr.regions SET region_name = 'Europe' WHERE region_id = 5;

1 rows updated.

1. Exit Hybrid Mode
   • Open PDB in READ WRITE FORCE
   • Hybrid mode disabled

SQL> alter pluggable database orclpdb1 open read write force;

Pluggable database altered.

SQL> SELECT con_name, is_hybrid_read_only FROM v$container_topology;

CON_NAME                IS_
----------------------- ---
CDB$ROOT                NO
PDB$SEED                NO
ORCLPDB1                NO

This confirms the dual-access behavior that makes hybrid read-only mode so powerful.

---

Why This Feature Is a Game Changer

Hybrid read-only mode removes a long-standing trade-off between security and manageability. Instead of choosing one, you get both.

For organizations running on Oracle Corporation Multitenant Architecture, this feature is especially valuable in:

• Mission-critical analytics platforms
• Regulated environments
• Always-on cloud databases

It enables databases to remain protected, consistent, and highly available—without sacrificing operational control.

---

Final Thoughts

Pluggable Database Hybrid Read-Only Mode is a subtle but powerful enhancement that reflects how modern databases are actually used. Applications need safety. Administrators need flexibility. Cloud platforms need zero downtime.

Hybrid read-only mode delivers all three.

If you manage multitenant Oracle databases and rely on read-only workloads, this feature is not just useful—it’s essential.