Adding PDB Resources in Grid Infrastructure

By -

In Oracle Database 21c, within the Grid Infrastructure environment, a new type of resource called ora.pdb.type has been introduced, which can be used to manage PDBs. These resources are named using the following format:

ora.<DB Unique Name>.<PDB Name>.pdb

Like other resources in the cluster and GI environment, PDB-related resources can be controlled and managed using the srvctl tool. For example, you can start or stop a PDB using this tool:

[grid@RAC3 ~]$ srvctl start pdb -db db21c -pdb pdb1

[grid@RAC3 ~]$ srvctl status pdb -db db21c -pdb pdb1

Pluggable database PDB1 is enabled.

Pluggable database PDB1 of database db21c is running on nodes: rac2,rac3

[grid@RAC3 ~]$ srvctl stop pdb -db db21c -pdb pdb1

[grid@RAC3 ~]$ srvctl status pdb -db db21c -pdb pdb1

Pluggable database PDB1 is enabled.

Pluggable database PDB1 of database db21c is not running.

 [oracle@RAC2 ~]$ srvctl stop pdb -db db21c -pdb pdb1 -n rac3 -stopoption IMMEDIATE

You can also configure a PDB to start automatically using srvctl, without using triggers or saved state:

SQL>  select * from dba_PDB_SAVED_STATES ;

no rows selected


[oracle@RAC3 ~]$ srvctl modify pdb -db db21c -pdb pdb1 -policy AUTOMATIC

[oracle@RAC3 ~]$ srvctl stop database -db db21c

[oracle@RAC3 ~]$ srvctl start database -db db21c


SQL*Plus: Release 21.0.0.0.0 – Production on Wed Oct 13 11:18:02 2021

Version 21.3.0.0.0

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED

———- —————————— ———- ———-

         2 PDB$SEED                       READ ONLY  NO

         3 PDB1                           READ WRITE NO

Using this tool, you can also manually remove or add a PDB resource from/to Grid Infrastructure:

 [oracle@RAC3 ~]$ srvctl remove pdb -db db21c -pdb pdb2

Remove the PDB pdb2? (y/[n]) y

[oracle@RAC3 ~]$ srvctl add pdb -db db21c -pdb pdb2 -startoption OPEN

However, when a new PDB is created in the cluster, its corresponding resource is automatically registered in Grid Infrastructure when the PDB is opened:

SQL> create pluggable database pdb2 admin user a identified by a;

Pluggable database created.

SQL> alter pluggable database pdb2 open;

Pluggable database altered.


[root@RAC3 bin]#  ./crsctl stat res -w “TYPE = ora.pdb.type”

NAME=ora.db21c.pdb1.pdb

TYPE=ora.pdb.type

TARGET=ONLINE        , ONLINE

STATE=ONLINE on rac2, ONLINE on rac3

NAME=ora.db21c.pdb2.pdb

TYPE=ora.pdb.type

TARGET=ONLINE        , OFFLINE

STATE=ONLINE on rac2, OFFLINE
Vahid Yousefzadeh

Written by Vahid Yousefzadeh


I have been a DBA since 2011 and I work with Oracle technology. Linkdin: linkedin.com/in/vahidusefzadeh telegram channel ID:@oracledb vahidusefzadeh@gmail.com

Edit profile

Comments

Post a Comment

Popular posts from this blog

Oracle 21c Enhancements for TTS Export/Import

By -
  In Oracle version 21c, new features have been introduced for transportable tablespace (TTS) export/import. This article explores these capabilities in detail. Improvement 1: Parallel Execution of TTS Export/Import In Oracle 19c, TTS export/import operations could not be executed in parallel, as demonstrated by the following: Connected to: Oracle Database 19c Enterprise Edition Release 19.0 .0 .0 .0 – Production ORA-39002: invalid operation ORA-39047: Jobs of type TRANSPORTABLE cannot use multiple execution streams. Oracle addressed this limitation in version 21c, enabling parallel execution for TTS export/import: [oracle@oLinux7 ~]$ expdp directory=drm dumpfile=TTS_DUMP%U.dmp transport_tablespaces=tbs1,tbs2 transport_full_check= y parallel= 2 Export: Release 21.0 . 0 . 0 . 0 – Production on Tue Oct 12 06 : 48 : 54 2021 Version 21.3 . 0 . 0 . 0 Processing object type TRANSPORTABLE_EXPORT/STATISTICS/TABLE_STATISTICS Processing object type TRANSPORTABLE_EXPOR...
Read more

Oracle 23ai — Speed up IMPDP Using NOVALIDATE Constraints

By -
  When executing the   IMPDP   command, some operations do not support parallel execution. Creating constraints is one such operation. Oracle must validate the current data in the table before creating a constraint, which requires a full table scan for each validation. This process can be very time-consuming. Consider the following constraints: ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK1 CHECK (col3 > 50 ); ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK2 CHECK (col9 IN ( 5 , 15 )); We drop the  MYTB  table and recreate it using a dump file: SQL > drop table mytb; Table dropped. W -1 Processing object type TABLE_EXPORT / TABLE / TABLE_DATA W -1 . . imported "VAHID"."MYTB" 19 GB 337830912 rows in 83 seconds using external_table W -1 Processing object type TABLE_EXPORT / TABLE / CONSTRAINT / CONSTRAINT W -1 Completed 2 CONSTRAINT objects in 208 seconds As shown, creating the two constraints ta...
Read more

Staging Tables in Oracle 23ai

By -
  As you may know, using   staging tables   is a common practice in   Data Warehouse   environments, primarily during the data loading process into the   Warehouse Database . Typically, raw data received from   source databases   is first loaded into a temporary area, referred to as   staging tables . After cleansing inconsistent and invalid data and transforming it into a standard format, the cleaned data is stored in the final operational tables. In addition to initial data loading,   staging tables   are also used for updates and are often truncated before reuse. In   Oracle 23ai , a new minor feature has been introduced for this purpose, allowing users to create tables specifically designed as   staging tables . This is achieved by adding the   FOR STAGING   clause to the   CREATE TABLE   statement. Creating Staging Tables Using the   FOR STAGING   clause, staging tables can be created as ...
Read more