Oracle E-Business Suite and Multitenant Architecture: A Practical Guide
Oracle E-Business Suite (EBS) has steadily evolved to align with modern Oracle Database capabilities, including the multitenant architecture. This article provides a consolidated, practitioner-focused overview of how Oracle E-Business Suite works with Container Databases (CDBs) and Pluggable Databases (PDBs), covering architecture, operations, patching, performance, and diagnostics.
1. Multitenant Architecture Overview for Oracle E-Business Suite
How EBS Supports Multitenant Databases
Oracle E-Business Suite supports a single-tenant multitenant model, where one Container Database (CDB) hosts exactly one Oracle E-Business Suite Pluggable Database (PDB). While this leverages multitenant technology, EBS itself does not currently support multiple PDBs within the same CDB.
Supported deployment combinations include:
EBS Release 12.2
On-premises with Oracle Database 19c or 23ai
OCI Base Database Service (1-node or 2-node)
Exadata Database Service (Dedicated Infrastructure or Cloud@Customer)
EBS Release 12.1.3
Oracle Database 19c (on-premises or OCI-supported platforms)
How Many PDBs Are Supported?
At present, Oracle E-Business Suite supports only one PDB per CDB. Running multiple EBS PDBs in a single container is not certified.
Licensing Considerations
Since EBS uses a single PDB per CDB, the Oracle Multitenant option license is not required. The multitenant licensing requirement applies only when more than one PDB is hosted in a CDB.
2. Infrastructure Considerations for Multitenant EBS
On-Premises Environments
When upgrading an Oracle E-Business Suite database to Oracle Database 19c, the database is converted from a non-CDB to a CDB with a single PDB as part of the upgrade process. This conversion is mandatory for EBS on newer database versions.
Oracle Cloud Infrastructure (OCI)
For EBS deployments moving to OCI database services—such as Base Database Service or Exadata—the database must also be converted to a multitenant architecture. This applies whether the migration is from an earlier database release or from on-premises infrastructure.
3. Working with the EBS Container Database (CDB)
Sourcing the CDB Environment
CDB-specific environment files reside under the database ORACLE_HOME. Administrators should source the appropriate environment file before performing CDB-level operations.
Connecting as SYSDBA
Once the CDB environment is sourced, connections to the container database are made using standard SYSDBA access via SQL*Plus.
Starting and Stopping the CDB
Single-instance systems use SQL*Plus startup and shutdown commands.
Oracle RAC environments use
srvctlto manage the database across nodes.
Cloning EBS in a Multitenant Setup
In on-premises environments, the EBS Rapid Clone utility can be used to clone both the CDB and the associated PDB together. This ensures application and database consistency.
4. Managing the Oracle E-Business Suite PDB
Sourcing the PDB Environment
PDB-specific environment files are also stored in the ORACLE_HOME. These must be sourced before performing application-related database tasks.
Connecting to the PDB as SYSDBA
To connect directly to the PDB:
Source the CDB environment.
Set the PDB identifier.
Connect using SYSDBA privileges.
Opening and Closing the PDB
The PDB is opened or closed from the CDB root using SQL commands. Administrators can also save the PDB state so that it automatically restores its open mode when the CDB restarts.
Viewing PDB Status
PDB details such as name and open mode can be queried using standard multitenant views. These views provide quick insight into PDB availability and state.
Switching Sessions from CDB to PDB
While logged into the CDB, sessions can be explicitly switched to the EBS PDB using an ALTER SESSION SET CONTAINER command.
Troubleshooting PDB Issues
If problems occur during PDB operations, plugin violation views can be queried to identify configuration or compatibility issues.
Can an EBS PDB Be Moved Between CDBs?
Currently, Oracle does not support unplugging and plugging an Oracle E-Business Suite PDB between CDBs, whether for relocation or cloning.
5. Multitenant-Specific Context Parameters
Oracle E-Business Suite uses several context file variables to support multitenant databases, including:
Indicators for pluggable database usage
CDB and PDB naming details
Database service naming conventions
Multitenant tenancy indicators
Network configuration paths
These parameters are automatically maintained and are critical for AutoConfig and runtime operations.
Running AutoConfig
Before running AutoConfig on the database tier, administrators must always source the PDB environment, not the CDB environment.
6. Migrating from Non-CDB to PDB
Data from an Oracle 12c non-CDB database can be moved directly into a PDB using Oracle Data Pump. This approach is commonly used during database upgrades and platform migrations for EBS Release 12.2.
7. Running SQL and EBS Scripts in a Multitenant Setup
When executing EBS database scripts:
Source the CDB environment.
Set the ORACLE_PDB_SID to the EBS PDB.
Run the required SQL or utility scripts.
This ensures scripts execute in the correct container context.
8. Patching Oracle E-Business Suite Multitenant Databases
EBS Technology Codelevel Checker (ETCC)
ETCC validates whether required database and application tier patches are applied. Since it reads the EBS context file, the PDB environment must be sourced before execution. OCI environments require an additional parameter to indicate cloud deployment.
OPatch Inventory
The OPatch inventory for a multitenant database is listed the same way as a traditional database, by sourcing the CDB environment and running standard OPatch commands.
Preparing for Database Patching
Database patching is performed from the CDB environment. However, before running datapatch, ensure the EBS PDB is open, as SQL fixes apply only to active PDBs.
9. Performance Best Practices
To achieve optimal performance in Oracle E-Business Suite:
Follow Oracle-recommended performance methodologies
Apply recommended performance patches
Configure database initialization parameters as per the EBS release and database version
Remove obsolete or restricted parameters listed in Oracle documentation
These steps are critical for both stability and scalability.
10. Diagnostics and Monitoring in Multitenant EBS
Alert Logs and Trace Files
In a multitenant architecture, all alert logs and trace files for both the CDB and its PDBs are stored under the CDB diagnostic directory. The exact location can be retrieved from dynamic performance views.
AWR Reports for PDBs
In Oracle 12c, AWR data is collected only at the CDB level.
Oracle 19c introduces PDB-aware AWR reporting, with separate views for root-level and PDB-level statistics.
Administrators can generate AWR reports by selecting the appropriate data source during report creation.
Conclusion
Oracle E-Business Suite’s adoption of the multitenant architecture provides a modern foundation while maintaining a conservative, single-tenant design. Understanding the operational boundaries—especially around PDB limitations, patching, and diagnostics—is essential for administrators managing EBS on-premises or on Oracle Cloud Infrastructure.
With the right practices in place, multitenant EBS environments can deliver improved manageability, standardization, and alignment with Oracle’s long-term database roadmap.
