Oracle E-Business Suite’s New EBS_SYSTEM Schema
For a long time, after the introduction of Online patching with the (E-Business Suite) EBS 12.2 release, there were no major changes to the underlying database architecture in Oracle E-Business Suite. With Oracle EBS 12.2, the Edition-based Redefinition (EBR) feature was introduced to power the Online Patching feature. The online patching feature helped reduce the downtime requirements of E-Business Suite by enabling the ability to apply the major part of any E-Business Suite patch while the system is up and running, hence the name Online patching.
Oracle EBS Database Schemas
For a long time, Oracle E-Business Suite Schema remained consistent and looked like the above table, with R12.2 adding some EBR-specific objects such as Edition Views and Triggers. However, with EBS 12.2 ATG_PF Delta13 patch, the Oracle EBS development team introduced a new schema called EBS_SYSTEM. Interestingly, this schema’s password needs to be kept the same as the current database System user. I wondered why the Oracle Dev Team introduced this schema and here is my take on it.
Lots of people think this change was introduced to address the segregation of duties and the separation of the elevated privileges required to maintain Oracle EBS schemas into a separate admin account similar to the System/Sys schema. This could be true, but I think it’s more than that. I believe the change was made because of new PDB requirements in 19c.
Oracle EBS was certified to run on the Oracle 19c database some time back. One of the requirements as part of this certification is that the Oracle EBS database will be converted into a PDB during the 19c database upgrade. At a high level, the process is to install a fresh 19c CDB and use Oracle-supplied scripts to upgrade the EBS database to a PDB and attach it to the freshly installed CDB. One limitation in the current EBS 19c database certification is that we cannot attach any other PDBs to the CDB which has the EBS PDB attached. Thus, even though the EBS database is converted to a PDB, customers cannot take advantage of the multi-tenant architecture, as they cannot attach other PDBs to EBS Container Database.
I think that the EBS_SYSTEM schema implementation address this 19c CDB/PDB limitation. Once the Oracle EBS Dev team moves all dependencies from the SYSTEM schema to the EBS_SYSTEM schema, the Oracle EBS database should be able to take full advantage of PDB/CDB architecture. Having a different local PDB admin account to take care of all EBS-specific needs will remove dependency on the CDB system schema and EBS Database should become portable. This change will help EBS databases become more DBcS friendly. It will even be possible to host Oracle EBS in AWS RDS if these PDB limitations are lifted. We just have to wait and see how this plays out.
Do let me know your thoughts and comments on this subject. I would love to hear what you think about Oracle EBS PDB’s limitations and progress.