Or git vm acle Database Multitenant – DMK features
This chapter presents the DMK features related to Oracle Multitenant ("Pluggable Databases") architecture
Last updated
release_2.2.0 - under construction
This chapter presents the DMK features related to Oracle Multitenant ("Pluggable Databases") architecture
Last updated
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.
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
ℹ️ 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.
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/; Optionally you can define PDB-specific variables and aliases in it.
Example of setting the environment for a pluggable database:
ℹ️ 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 first the environment for the CDB, then the environment for the PDB (which still works), you can directly set a pdb environment with the alias <CDB>.<PDB>, in the example above with
