Joords Oracle DBA blog

Can you connect as SYSDBA without password into a PDB directly? Of course with the usual way of “ sqlplus / as sysdba ”. Yes you can, even without no bequeath connection available. There is a 19c EBS notes . In one of the most important EBS MOS Notes: 2552181.1 – Interoperability Notes: Oracle E-Business Suite MOS Notes: 2552181.1 – Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c under section 2.5 you can read:

Migration of a single PDB or executing of a single PDB into another container database with minimal downtime. This method has zero impact to any remaining primary PDBs.  To use this method  the process takes advantage of a new functionality added to the Data Guard broker command line interface DGMGRL. Important: The process are steps involve changes being made to 2 independent CDBs and is supported in Oracle RDBMS versions older than 12.1.0.2 The migration process overview

Bug 27693713 - PDB PITR Does Not Apply Incrementals When Local Undo Is Enabled DB PITR does not apply incremental backup when PDB is configured with local undo  (select * from database_properties where property_name = 'LOCAL_UNDO_ENABLED' and PROPERTY_VALUE = 'TRUE'); When restore pluggable database noredo is executed, it is supposed to apply incremental backups. Instead, media recovery is being performed when PDB local undo is enabled. this can take a long time. Bug info 27693713

In Oracle 12.2 a lot of new features are introduced for Multitenant 12.2 environments One of the possibility is to clone a pluggable databases while they are open for read/write operations. When we want to do this in a MAA environment this will introduce some problems Data Guard Impact on Oracle Multitenant Environments (Doc ID 2049127.1) For this Oracle has some new parameters which can be used to overcome these problems the parameter  " standby_pdb_source_file_dblink "

Multitenant : PDB Clone a Remote PDB or Non-CDB in Oracle Database From Oracle 12.1.0.1 was it possible to de cloning of PDB's in a local Container database. Since version 12.1.0.2 Oracle has extended this functionality to remote PDB cloning. Cloning between two separted on-premises Oracle databases 12c non-CDBs as PDBs to an on-premises Oracle Database 12c container database. This method works also on Oracle Database 12c DBaaS database - Oracle Database Cloud Service (DBCS). An 12c RDBMS migration from On-Premise to Premise and back.

The installation of an Oracle database is done by executing serveral scripts. Those scripts perform operations such as creating data dictionary views and installing options. Oracle has now introduced multiple database [PDB's] inside one database [CDB]. For maintenacne and a new strategy Oracle's best way is to run SQL scripts and SQL statements is done by using catcon.pl. It can run them in the root and in specified PDBs in the correct order, and it generates log files that you can view to confirm that the SQL script or SQL statement did not generate unexpected errors. It also starts multiple processes and assigns new scripts to them as they finish running scripts previously assigned to them. Example of the Statement perl /u02/app/oracle/product/12.1.0/dbhome_1/rdbms/admin/catcon.pl -n 1 -l /u02/app/oracle/admin/CDB1/scripts -b catalog /u02/app/oracle/product/12.1.0/dbhome_1/rdbms/admin/catalog.sql CatCon.pl = Perl Module for creating - upgrading CAT alogs for CON tain...

For creating a pluggable database you have to consider how to create the pluggable database, and what are you current CDB settings. In this post i have played with and without OMF and difference file structures inside ONE CDB database. Mostly pluggable database will be created from the seed database. What is needed when you want the oracle files of the pluggable database on an other file structure storage. What will you use, and when should you use what. After the createing of a pluggable database, you need possible extra steps inside the pluggable database to keep your optimalisize storage environment. Think about the steps that are needed with a single none CDB, those steps would also be needed on a pluggable database by or after the creating steps. When you don't think about this, the change is that you get a spaghetti mixture of files inside your environment. Lets play;