Creating a new PDB in RAC without Standby Protection

 I've published a new Video demonstration when you need to create a new PDB (even as a clone of an existing one) without requiring a Standby copy of the PDB.

(Use cases : Test environment for a day or two, it would take too long to create a new Test Server and clone the database, it would take too long to change Firewall rules to allow Applications to connect to the Test Server)

This in RAC with DataGuard Useful commands : Create new PDB :

CREATE PLUGGABLE DATABASE PRDAPPTST FROM PDB1  STANDBYS=NONE

Create Service :

srvctl add service -db RACDB  -service newtestpdb -preferred RACDB1,RACDB2 -tafpolicy BASIC -failovertype SELECT -clbgoal SHORT -pdb PRDAPPTST

Start Service :

srvctl enable service -db RACDB -service newtestpdb
srvctl status service -db RACDB -service newtestpdb
srvctl start service -db RACDB -service newtestpdb
srvctl status service -db RACDB -service newtestpdb

Always use custom Service Names instead of the default name derived from the PDB Name.

UPDATE  02-July : In response to a question on x.com : "One question: what if we want to create standby in future. Do we have to change standby parameter using any command or we can directly create standby normally"

My reply is :

The STANDBYS=NONE applies only to this PDB (PRDAPPTST). Any new PDB would still default to STANDBYS=ALL.

Although PRDAPPTST is intended to be dropped in a day or two, if you want it to be protected by Standby for longer or permanently, you can restore it to the Standby CDB (as it is in the controlfile and datadictionary) and resume recovery with ENABLE RECOVERY

See this next Blog Post where the Standby for PRDAPPTST is also setup.

Also see this series of posts on Refreshable Clone PDBs that I published a few years ago.