Skip to main content

How to set Oracle Pluggable Database Automatic startup with Container

How to set Oracle Pluggable Database Automatic startup with Container

In Oracle Database 12c and above, the Multitenant Architecture was introduced, allowing for the creation of multiple Pluggable Databases (PDBs) within a single Container Database (CDB). To ensure seamless operation and availability of the PDBs, it is essential to configure automatic startup for the PDBs during database startup. This blog article will guide you through the steps to set up automatic startup for Oracle Pluggable Databases.


Steps:

1) Connect to the CDB


Start by connecting to the Container Database (CDB) using SQL*Plus

$sqlplus / as sysdba

SQL>show con_name
CON_NAME
------------
CDB$ROOT

2) Check Current Startup Mode


Execute the following query to check the current startup mode of the PDBs:


SELECT name, open_mode FROM v$pdbs;

Or

SQL>show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 FPDB1                           MOUNTED
         4 FPDB2                           MOUNTED

The open mode should be set to "MOUNTED" for the PDBs that you want to configure for automatic startup.

3) Open the PDBS using below command


SQL> alter pluggable database fpdb1 open read write;

Pluggable database altered.

SQL> alter pluggable database fpdb2 open read write;

Pluggable database altered.

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 FPDB1                           READ WRITE NO
         4 FPDB2                           READ WRITE NO

4) Configure PDB for Automatic Startup


SQL> alter pluggable database fpdb1 save state;

Pluggable database altered.

SQL> alter pluggable database fpdb2 save state;

Pluggable database altered.



5) Check the pdbs saved state using dba_pdb_saved_states views


SQL> select con_name,state from dba_pdb_saved_states

CON_NAME             STATE
-------------------- --------------
FPDB1                 OPEN
FPDB2                 OPEN

6) Bounce the cdb and check the pdbs state


SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.


SQL> startup
ORACLE instance started.
Database mounted.
Database opened.

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 FPDB1                           READ WRITE NO
         4 FPDB2                           READ WRITE NO


If we want to Discard the pdbs saved state


SQL> alter pluggable database fpdb1 discard state;

Pluggable database altered.


SQL> select con_name,state from dba_pdb_saved_states;

CON_NAME             STATE
-------------------- --------------
FPDB2                 OPEN

Now we can see saved state for only one pdf

Restart the CDB and check pdbs status

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 FPDB1                           MOUNTED
         4 FPDB2                           READ WRITE NO





If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...
Post a Comment
Read more