Oracle 21c New Feature: INCLUDE and EXCLUDE parameters in expdp for the same job

 Starting in Oracle 21c, we can use the parameters INCLUDE and EXCLUDE in the same job for expdp. Before this you were able to use only one of these parameters for the same job.

 In the following example, I will export the table DGOMEZ.TABLE2 and excluding the table  DGOMEZ.TABLE1:

[oracle@localhost ~]$ expdp system/system@localhost:1521/pdb11 exclude=table:"IN('TABLE1')" include=table:"IN('TABLE2')" schemas='DGOMEZ'

Export: Release 21.0.0.0.0 - Production on Mon May 02 03:39:07 2022
Version 21.3.0.0.0

Copyright (c) 1982, 2021, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 21c Enterprise Edition Release 21.0.0.0.0 - Production
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01":  system/********@localhost:1521/pdb11 exclude=table:IN('TABLE1') include=table:IN('TABLE2') schemas=DGOMEZ
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/TABLE
. . exported "DGOMEZ"."TABLE2"                           5.054 KB       1 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
  /u01/app/oracle/product/19.0.0/db_base/admin/orcl/dpdump/E8D8634299033724E055000000000001/expdat.dmp
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at Mon May 02 03:39:29 2022 elapsed 0 00:00:19

[oracle@localhost ~]$

 

  In the following example, I will export the table DGOMEZ.TABLE1 and excluding the table  DGOMEZ.TABLE2:

 [oracle@localhost ~]$ expdp system/****@localhost:1521/pdb11 exclude=table:"IN('TABLE2')" include=table:"IN('TABLE1')" schemas='DGOMEZ'

Export: Release 21.0.0.0.0 - Production on Mon May 02 03:40:00 2022
Version 21.3.0.0.0

Copyright (c) 1982, 2021, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 21c Enterprise Edition Release 21.0.0.0.0 - Production
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01":  system/********@localhost:1521/pdb11 exclude=table:IN('TABLE2') include=table:IN('TABLE1') schemas=DGOMEZ
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/TABLE
. . exported "DGOMEZ"."TABLE1"                           5.054 KB       1 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
  /u01/app/oracle/product/19.0.0/db_base/admin/orcl/dpdump/E8D8634299033724E055000000000001/expdat.dmp
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at Mon May 02 03:40:27 2022 elapsed 0 00:00:25

[oracle@localhost ~]$

New parameter CPU_MIN_COUNT in Oracle Database 19c

Oracle Database 19c has introduced several new features for Multitenant among them we can mention the parameter  CPU_MIN_COUNT that specify a minimum number of CPUs for the PDB. Oracle documentation says the following about this parameter:

CPU_MIN_COUNT specifies the minimum number of CPUs required by a pluggable database (PDB) at any given time.

This parameter specifies the minimum number of CPUs required by a PDB at any given time. For multi-threaded CPUs, this number corresponds to CPU threads, not CPU cores.

You can set this parameter at the CDB level, and for each individual PDB. This enables you to control each PDBs minimum share of CPU utilization within a CDB. If the sum of the CPU_MIN_COUNT values across all open PDBs in a CDB is equal to the value of CPU_MIN_COUNT for the CDB, then the CDB instance is considered full. If the sum exceeds the value of CPU_MIN_COUNT for the CDB, then the CDB instance is over-provisioned. Oracle does not prevent you from over-provisioning a CDB.

Resource Manager is enabled at the CDB level by setting the RESOURCE_MANAGER_PLAN at the root level to the name of a CDB resource plan. If the CDB resource plan has no configured CPU directives, that is, the SHARES and UTILIZATION_LIMIT directives are unset, then Resource Manager uses the CPU_COUNT and CPU_MIN_COUNT settings for the PDB to manage CPU utilization.

 

Reference: https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/CPU_MIN_COUNT.html#GUID-C0EFFDF8-951A-4C36-B2A9-925AA899647D

 

 

 

 How to change it:

At PDB Level:

SQL> show con_name

CON_NAME
------------------------------
PDB11

SQL> alter system set cpu_min_count=2 scope=both;

System altered.

SQL>

 
SQL> show parameters cpu_min_count

NAME               TYPE        VALUE
------------------ ----------- ------------------------------
cpu_min_count      string      2
SQL>

 At CDB Level: 

SQL>  show con_name

CON_NAME
------------------------------
CDB$ROOT

SQL> alter system set cpu_min_count=2 scope=both;

System altered.

SQL>  show parameters cpu_min_count

NAME               TYPE        VALUE
------------------ ----------- ------------------------------
cpu_min_count      string      1
SQL>