Oracle Database 19c – DMK features

This chapter presents all DMK new features related to Oracle Database 19c

Automatic startup of pluggabable database(s)

The “database.{ksh|ps1}” script starts the pluggable databases using the standard Oracle ORATAB file.

DMK Release 1: The principle consists of duplicating the database ORACLE_SID entry. The database entry followed by the startup flag “Y” (automatic startup) and the list of pluggable database(s) will be started, the duplicate entry must be followed by the flag “N” and the list of pluggable database(s) which shall not be started

DMK Release 2:

for each pluggable database an (empty) file will be created below $ DMK_ORA_ADMIN_SID/dmk/pdbs; That is automatically done the 1st time the database (cdb) is detected (and is open), and afterwards, each time status.pl inst (alias istat) is called.

ℹ️Please refer to chapter 11 Starting databases automatically – M.S Windows for details about the integration of “database.ps1” to M.S Windows the boot procedure.

Example of the ORATAB configuration for the Oracle 19c database CDBUTF8:

oracle@vmoel58:/home/oracle/ [rdbms1912] cat /etc/oratab | grep CDBUTF8
CDBUTF8:/u01/app/oracle/product/19.12.0.0/db_1:Y:PDB3
CDBUTF8:/u01/app/oracle/product/19.12.0.0/db_1:N:PDB1,PDB2

Display Oracle 19c Pluggable database(s) component status

Example of status.pl instance (alias istat):

Example of dmk-run.ps1 (alias ser) output:

oracle@vmoel58:/home/oracle/ [rdbms1912] ser
Dummy:
------
Rdbms1912 : DUMMY (19.12.0.0/db_1)
Database(s):
------------
CDBUTF8 : OPEN (19.12.0.0/db_1)
 : Pluggable database(s)
 PDB$SEED : READ ONLY
PDB1 : MOUNTED
 PDB2 : MOUNTED
 PDB3 : MOUNTED
Listener(s):
------------
LISTENER : Up (19.12.0.0/db_1)

Oracle 19c DMK core integration

List pluggable databases & setting environment

The output of the pluggable databases have been added to the database status script, where you set the ORACLE_SID and the new command “lspdb” lists all pluggable databases of the current environment.

Example: Setting the ORACLE_SID for database DBICDB:

Example: Output of the command lspdb

oracle@vmoel58:/home/oracle/ [CDBUTF8 (CDB$ROOT)] lspdb
******** dbi services Ltd. ********
DBICDB -- Pluggable database(s)
-----------------------------------
PDB name : Open Mode
-----------------------------------
LMA : READ WRITE
PDB$SEED : READ ONLY
PDB1 : READ WRITE
***********************************

ℹ️ Aside of these functionalities some checks have been added to compare the ORATAB declared list of pluggable database(s) with the list available from database view V$PDBS.

Pluggable database administration

This feature allows performing the “alter session set container” within sqlplus automatically, using an operating system alias. The current container name is displayed within the default prompt. This works through an SQL-statement, defined by the variable DMK_EXEC_SQL_SCRIPT in DMK.conf. If you specify it, DMK will append the statement to your script by creating a temporary execution copy.

The PDBs are defined as a (empty) file in $DMK_ORA_ADMIN_SID/dmk/pdbs/

Example of setting the environment for a pluggable database:

oracle@vmoel58:/u01/app/oracle/local/dmk/ [CDBUTF8 (CDB$ROOT)] pdb1
oracle@vmoel58:/u01/app/oracle/local/dmk/ [CDBUTF8(PDB1)] sqh
SQL*Plus: Release 19.12.0.0 Production on Sun Jun 30 10:31:00 2021
Copyright (c) 2021, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.12.0.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing
options
SQL> show con_name
CON_NAME
------------------------------
PDB1

ℹ️ If the name of a pluggable database corresponds to an ORACLE_SID, DMK will trigger a WARNING message. The ORACLE_SID has always priority compared to the pluggable database.

New with Release 2:

Instead of setting the CDB, then the PDB (which still works), you can directly set a pdb environment with the alias <CDB>.<PDB>, in the example above with

CDBUTF8.PDB1
cdbutf8.pdb