Joords Oracle DBA blog

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;