Introduced with Oracle Database 12c, the multitenant architecture enables an Oracle database to function as a container database (CDB). A pluggable database (PDB) is a portable collection of schemas, schema objects, and non-schema objects, contained within a CDB.
This document presents a series of commonly asked questions and answers about using Oracle E-Business Suite (EBS) with the multitenant architecture: for example, how many PDBs are currently supported within a CDB.
The topics are grouped in the order they are most likely to be needed by those new to this area, but can be referred to in any desired order or combination.
There is a change log at the end of this document.
Section 1: General Questions
How does Oracle E-Business Suite support the multitenant architecture?
Oracle E-Business Suite supports the multitenant architecture with a single CDB containing a single pluggable Oracle E-Business Suite database (PDB) in the following combinations:
- Oracle E-Business Suite 12.2.3 and later with Oracle Database 19c on-premises
- Oracle E-Business Suite 12.2.3 and later with Oracle Database 12cR1 VM DB Systems or Oracle Database 12cR1 in an Exadata DB System
- Oracle E-Business Suite 12.1.3 with Oracle Database 19c on-premises
- Oracle E-Business Suite 12.1.3 with Oracle Database 12cR1 VM DB Systems or Oracle Database 12cR1 in an Exadata DB System
How many PDBs are supported in a CDB that is running Oracle E-Business Suite?
At present, Oracle E-Business Suite supports a single PDB (single tenant) in a CDB.
Are there additional licensing requirements?
Oracle E-Business Suite currently supports a single pluggable database (single tenant) with a CDB architecture (see previous question). A single PDB in a CDB does not require licensing the Oracle Multitenant database option.
For more information, refer to the following resources:
Do I need to make any Oracle E-Business Suite Infrastructure changes?
Whether you need to make changes to your Oracle E-Business Suite environment depends on where your environment resides:
- For on-premises Oracle E-Business Suite environments:
- As part of the upgrade of your Oracle E-Business Suite Database to 19c you will convert your database to the CDB architecture with a single pluggable database (PDB). For more information, refer to the following My Oracle Support knowledge documents:
- Document 2552181.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
- Document 2580629.1, Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c
- For Oracle E-Business Suite environments on Oracle Cloud Infrastructure (OCI):
- If you are moving to a database service (1-node or 2-node VM DB System, or Exadata DB System) as part of the migration of an Oracle E-Business Suite 12c database, you will need to convert the database to the CDB architecture.
- For more information, refer to Section 3, Certifications and Automations, of My Oracle Support Knowledge Document 2517025.1, Getting Started with Oracle E-Business Suite and Oracle Cloud Infrastructure.
Section 2: Oracle E-Business Suite Container Database (CDB)
Note: Except for cloning, the questions and answers in this section apply both to on-premises and OCI environments.
How do I source the Oracle E-Business Suite CDB environment?
Oracle E-Business Suite database CDB environment files are located in the database ORACLE_HOME. Run the following commands:
$ cd $ORACLE_HOME
$ source <CDB_NAME>_<NODE_NAME>.env
How do I connect to the Oracle E-Business Suite CDB as SYSDBA?
Source the CDB environment file in the ORACLE_HOME and then use SQL*Plus to connect to the CDB as SYSDBA:
$ cd $ORACLE_HOME
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
How do I start the CDB that hosts the Oracle E-Business suite PDB?
You will use either SQL*Plus or srvctl, depending on whether you are using a single-node instance or Oracle RAC system.
How do I shut down the CDB that hosts the Oracle E-Business Suite PDB?
You will use either SQL*Plus or srvctl, depending on whether you are using a single-node instance or Oracle RAC system.
How do I clone an Oracle E-Business Suite environment with a CDB?
In on-premises environments, the Oracle E-Business Suite Rapid Clone utility can be used to clone both the CDB and PDB together.
Section 3: Oracle E-Business Suite Pluggable Database (PDB)
How do I source the Oracle E-Business Suite PDB environment?
The Oracle E-Business Suite database PDB environment files are located in the database ORACLE_HOME:
$ cd $ORACLE_HOME
$ source <PDB_NAME>_<NODE_NAME>.env
How do I connect to the Oracle E-Business Suite PDB as SYSDBA?
Source the CDB environment file, export the Oracle E-Business Suite PDB name, then use SQL*Plus to connect to the PDB as SYSDBA:
$ source <CDB_NAME>_<NODE_NAME>.env
$ export ORACLE_PDB_SID=<PDB NAME>;
$ sqlplus "/ as sysdba"
How do I open the Oracle E-Business Suite PDB?
Source the CDB environment file, connect to the CDB as SYSDBA, then execute the SQL shown in the example to start the PDB:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> alter pluggable database <EBS PDB Name> open read write services=all;
How do I close the Oracle E-Business Suite PDB?
Source the CDB environment, connect to the CDB as SYSDBA, then execute the SQL shown in the example to close the PDB:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> alter pluggable database <EBS PDB Name> close immediate;
There is also the option to save the state of the PDB. Oracle will then preserve the mode when you restart the CDB. You can find the current saved state by querying DBA_PDB_SAVED_STATES:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> alter pluggable database <EBS PDB Name> save state;
SQL> alter pluggable database <EBS PDB Name> close immediate;
How do I find Oracle E-Business Suite PDB information and status?
The following SQL returns the values for the con_id, con_name, open mode, restricted values of all your PDBs.$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> show pdbs;
Alternatively, you could use the following SQL to return only the values for name and open mode:$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> select name, open_mode from v$pdbs;
How do I access the Oracle E-Business Suite PDB while logged into the CDB?
Use the following command to set the environment, show the PDB name, and then connect to that PDB:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> show pdbs;
SQL> alter session set container=”PDBNAME”;
Where do I look for PDB errors if I encounter a problem?
Source the environment and then review any plugin violations, as shown in the following example:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> select name, cause, message, status from PDB_PLUG_IN_VIOLATIONS;
Can I unplug an Oracle E-Business Suite PDB from one CDB and plug it into another CDB?
At present, there is no supported procedure to unplug an Oracle E-Business Suite PDB and plug (relocate or clone) it to another CDB.
What parameters in the Oracle E-Business Suite database context file support the multitenant architecture?
Context variables used to support the multitenant architecture are as follows:
- s_pluggable_database: This variable is set to
TRUE in a multitenant database. - s_pdb_name: This variable is set to
PDB name. - s_cdb_name: This variable is set to
CDB SID. - s_cdb_unique_name: This variable is set to the
DB unique name for the CDB. - s_dbService: This variable is set to
ebs_<PDB name> in a multitenant database. - s_db_tenancy: This variable is set to
multi-tenant in a multitenant database. - s_cdb_tnsadmin: This variable is set to
$ORACLE_HOME/network/admin.
Before running AutoConfig on the database tier, do I source the PDB environment or CDB environment?
You should always source the Oracle E-Business Suite PDB environment before running AutoConfig. You can do so by running the following commands:
$ cd $ORACLE_HOME
$ source <PDB_NAME>_<NODE_NAME>.env
Can I export an Oracle 12c non-CDB database and import it into an Oracle 19c PDB?
Data from a non-CDB database can be directly imported into a PDB using the Data Pump export/import commands. Refer to My Oracle Support Knowledge Document 2554156.1, Export/Import Process for Oracle E-Business Suite Release 12.2 Database Instances Using Oracle Database 19c.
Section 4: Oracle E-Business Suite Multitenant Database SQL and Scripts
How do I set up the environment to run an Oracle E-Business Suite Script or SQL session?
Source the Oracle Home <CDB_NAME>_<HOSTNAME>.env and set the PDB environment variable ORACLE_PDB_SID=<PDB_NAME> before running Oracle E-Business Suite programs such as adgrants.sql.
$ source <CDB_NAME>_<NODE_NAME>.env
$ export ORACLE_PDB_SID=<PDB_NAME>
$ sqlplus "/ as sysdba"
Section 5: Oracle E-Business Suite Multitenant Database Patching
How do I run the EBS Technology Codelevel Checker (ETCC) against my Oracle E-Business Suite PDB?
The EBS Technology Codelevel Checker (ETCC) utility provides two scripts to help ensure you have the necessary database and application tier patches installed on your Oracle E-Business Suite Release 12.2 instance.
ETCC extracts environment-related information from the context file (using the location defined in $CONTEXT_FILE), so you need to source the Oracle E-Business Suite PDB environment before you run the database checker script. For OCI-based environments, you also need to add the cloud=y parameter.
Download ETCC as Patch 17537119 from My Oracle Support and unzip it into a working directory. Then proceed with whichever of the following steps applies to you:
How do I list the OPatch inventory for a multitenant database?
You can list the OPatch inventory of a multitenant database in the same way as for non-CDB. Run the following commands:
$ source <CDB_NAME>_<NODE_NAME>.env
$ export PATH=$PATH:$ORACLE_HOME/OPatch
$ opatch lsinventory -detail
How do I set up the environment to install a database patch in an Oracle E-Business Suite multitenant database?
Source the CDB environment and add the OPatch directory to the path, as shown in the following example:
$ source <CDB_NAME>_<NODE_NAME>.env
$ export PATH=$PATH:$ORACLE_HOME/OPatch
Note: Before running datapatch, ensure that the Oracle E-Business Suite PDB is open as datapatch will only apply or roll back SQL fixes for open PDBs. For more information, refer to My Oracle Support Knowledge
Document 1585822.1,
Datapatch: Database 12c Post Patch SQL Automation.
Section 6: Oracle E-Business Suite Performance Recommendations
What methodology should I follow to ensure I am getting the best performance out of Oracle E-Business Suite?
Refer to My Oracle Support Knowledge Document 2528000.1, Oracle E-Business Suite Performance Best Practices.Where can I find real-world practical tips and lessons for tuning my Oracle E-Business Suite environment?
Refer to My Oracle Support Knowledge Document 2125596.1, Achieving Optimal Performance with Oracle E-Business Suite.
Where do I find the recommended performance patches for Oracle E-Business Suite?
Refer to My Oracle Support Knowledge Document 244040.1, Oracle E-Business Suite Recommended Performance Patches.
Where do I find the recommended initialization parameters for Oracle E-Business Suite?
Refer to My Oracle Support Knowledge Document 396009.1, Database Initialization Parameters for Oracle E-Business Suite Release 12. This document includes two main sections:
- A common set of database initialization parameters that are applicable to all releases of the Oracle Database
- An Oracle Database release-specific section
These two sections combine to provide a complete list of release-specific database initialization parameters.For Oracle E-Business Suite Release 12.1 on Oracle Database 19c, refer to the following:- Document 396009.1 - Section 1: Common Database Initialization Parameters For All Releases
- Document 396009.1 - Section 4: Release-Specific Database Initialization Parameters for Oracle 19c
For Oracle E-Business Suite Release 12.2 on Oracle Database 19c, also refer to the following:- Document 396009.1 - Section 5: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2
Note: Each database section has a list of parameters in a removal list. These must be removed because they are obsolete or else the default database value is mandatory and no other value may be set.
Section 7: Oracle E-Business Suite Multitenant Database Diagnostics
How do I find the location of the alert log and trace files for my multitenant database?
Each CDB has an associated alert log, which is used to record log information, warnings and alerts about the Oracle E-Business Suite PDB. It is located in the "Diag Trace" of the container database. Also, all PDBs plugged in a given CDB write trace data to the "Diag Trace" of the container database, which can be found by querying v$diag_info dynamic view as in the following example:
$ source <CDB_NAME>_<NODE_NAME>.env
$ sqlplus "/ as sysdba"
SQL> select value from v$diag_info where name = 'Diag Trace';
How do I generate an AWR snapshot report for my pluggable database?
In Oracle Database 12c Release 1, AWR snapshots are only created at the CDB-level (CDB root). This AWR snapshot is for the whole database system in that it contains the statistical information about the CDB as well as all the PDBs in a multitenant environment.
Oracle 19c multitenant supports AWRs at the CDB and PDB level. There are two new views:
- AWR_ROOT view: This shows the AWR data stored only on a CDB root, which are generally equivalent to the DBA_HIST views.
- AWR_PDB view: There are a few PDB-level metrics, but the vast majority are instance-wide statistics that are not shown at this level for security reasons. Hence these will not be flushed in AWR, and will always be shown as 0 in the AWR report.
Use the following commands as a basis to create a snapshot and specify AWR_ROOT or AWR_PDB as appropriate:$ source <CDB_NAME>_<NODE_NAME>.env
$ export ORACLE_PDB_SID=<PDB NAME>;
$ sqlplus "/ as sysdba"
! Run awrrpt.sql file
SQL> @$ORACLE_HOME/rdbms/admin/awrrpt.sql
...
Specify the location of AWR Data
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AWR_ROOT - Use AWR data from root (default)
AWR_PDB - Use AWR data from PDB
...
