Oracle E-Business Suite Release 12.2 customers are now looking toward the next major database platform: Oracle AI Database 26ai. Oracle has published interoperability guidance for running Oracle EBS 12.2 with Oracle AI Database 26ai, replacing the earlier Oracle Database 23ai reference. The document explains the required pre-upgrade checks, mandatory patches, unsupported products, and known issues that every Oracle Apps DBA should review before planning the upgrade.
For an Apps DBA, this is not just a normal database upgrade. It is a complete readiness exercise involving the database tier, application tier, AD/TXK level, online patching editions, AutoConfig, case-sensitive passwords, PDB naming, TDE configuration, and product compatibility.
1. Why This Upgrade Needs Careful Planning
Oracle EBS 12.2 is tightly integrated with its database and technology stack. Any major database upgrade can directly impact:
- Concurrent processing
- Forms and Reports
- Workflow
- Online patching
- Custom integrations
- SOA Gateway
- Performance of batch jobs
- Login and application tier connectivity
- Database edition cleanup
- Application tier Oracle homes
Oracle clearly recommends that before moving such an upgraded system into production, organizations must perform proper performance and scalability testing, including batch processing, online transactions, lifecycle operations, and maintenance activities.
In simple words, do not treat this as only a database team task. This must be handled as a joint activity between Apps DBA, Core DBA, Functional, Middleware, Infrastructure, Security, and Business teams.
2. Certification Check Comes First
Before starting any activity, the first step is to verify the Oracle Product Certification Matrix from My Oracle Support.
The upgrade should not be planned only because Oracle AI Database 26ai is available. The actual platform, operating system, EBS release level, and product usage must be certified.
A very important point from the Oracle note is that both the application tier and database tier must be running on Oracle Linux for the procedure described in the document.
Apps DBA Check
Before upgrade planning, verify:
SELECT release_name
FROM fnd_product_groups;
Also check database version:
SELECT name, version, open_mode, database_role
FROM v$database, v$instance;
And confirm OS/platform details at server level:
cat /etc/os-release
uname -a
3. Source Database Must Be Prepared Properly
Oracle’s note explains that the document mainly covers the pre-upgrade steps required for the source 19c database before moving to Oracle AI Database 26ai. The actual database upgrade procedure is covered in separate Oracle documents depending on architecture, such as single node, RAC, standby, OCI Base Database Service, or Exadata Cloud.
This means Apps DBAs should not directly jump to DBUA, AutoUpgrade, or manual upgrade steps. First, complete all EBS-specific prerequisites.
4. Run hcheck.sql Before Upgrade
One of the first recommended pre-upgrade tasks is to run hcheck.sql to identify known data dictionary issues.
This is important because database dictionary corruption or inconsistencies can cause upgrade failures, invalid objects, or post-upgrade instability.
Generic Command
sqlplus / as sysdba
@hcheck.sql
What Apps DBA Should Validate
After running hcheck.sql, review the output for:
- Dictionary corruption warnings
- Invalid metadata
- Known SYS/SYSTEM object issues
- Upgrade blocker messages
- Recommended Oracle Support actions
Do not proceed until critical issues are resolved or cleared by Oracle Support.
5. Minimum EBS Release and Patch Readiness
The note states that Oracle EBS must be at Release 12.2.7 or equivalent product family Release Update Pack level, with multiple prerequisite patches applied.
Some important patch areas include:
| Area | Requirement |
|---|---|
| EBS Release | 12.2.7 or above |
| AD | R12.AD.C Delta 16 or latest |
| TXK | R12.TXK.C Delta 16 or latest |
| ATG PF | Required for certain lower releases |
| Interoperability Patch | Required for EBS 12.2 with 26ai |
| ISG Patches | Required if Integrated SOA Gateway is used |
| Forms Overlay Patch | Required for 10.1.2 application tier Oracle home on Linux |
Apps DBA Validation Query
SELECT bug_number, creation_date
FROM ad_bugs
WHERE bug_number IN
(
'36119925',
'36117775',
'35876968',
'31669299',
'36960053',
'37012872',
'38633086'
)
ORDER BY bug_number;
For conditional patches, validate only if the relevant module or feature is used.
6. 10.1.2 Oracle Home Relinking Is Required
The Oracle note includes specific actions for the 10.1.2 application tier Oracle home, including applying required patches and relinking Forms, Reports, SQLPlus, and ProC components.
Generic Relink Example
cd $ORACLE_HOME/procbuilder/lib
make -f ins_procbuilder.mk install
cd $ORACLE_HOME/forms/lib
make -f ins_forms.mk sharedlib
make -f ins_forms.mk install
cd $ORACLE_HOME/reports/lib
make -f ins_reports.mk install
cd $ORACLE_HOME/sqlplus/lib
make -f ins_sqlplus.mk install
Apps DBA Note
This should first be tested in a cloned environment. Always capture:
echo $ORACLE_HOME
echo $CONTEXT_FILE
opatch lsinventory
Before and after applying technology stack patches.
7. AutoConfig Must Be Patched and Executed
AutoConfig is a critical component in Oracle EBS. The note states that prerequisite EBS patches must be applied and AutoConfig must be run afterward as per Oracle EBS setup guidance.
Application Tier
cd $ADMIN_SCRIPTS_HOME
./adautocfg.sh
Database Tier
cd $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME
./adautocfg.sh
Validation
grep -i "AutoConfig completed successfully" $APPL_TOP/admin/$CONTEXT_NAME/log/*.log
8. Complete EBS_SYSTEM Schema Migration
Oracle requires completion of the Oracle E-Business Suite System Schema Migration process before upgrading.
This is very important in EBS 12.2 architecture because EBS has moved toward using the EBS_SYSTEM schema for certain administrative and technology stack operations.
Apps DBA Validation
Check whether the required schema exists:
SELECT username, account_status, created
FROM dba_users
WHERE username IN ('EBS_SYSTEM', 'SYSTEM', 'APPS');
Also check invalid objects:
SELECT owner, object_type, COUNT(*)
FROM dba_objects
WHERE status = 'INVALID'
AND owner IN ('APPS','EBS_SYSTEM','SYSTEM')
GROUP BY owner, object_type
ORDER BY owner, object_type;
9. Case-Sensitive Passwords Must Be Enabled
If the database parameter SEC_CASE_SENSITIVE_LOGON is set to FALSE, Oracle requires enabling case-sensitive passwords before the upgrade.
Check Current Parameter
SHOW PARAMETER sec_case_sensitive_logon;
Expected:
SEC_CASE_SENSITIVE_LOGON = TRUE
If this is changed, Apps DBA must also carefully update the WebLogic data sources for users like APPS and APPLSYSPUB, following Oracle EBS Maintenance Guide instructions.
Important Apps DBA Point
This activity can impact login and application connectivity. Always test:
- EBS login
- Concurrent manager startup
- Forms launch
- OAF page access
- Workflow mailer connectivity
- JDBC connections
- Custom integrations
10. PDB Name Must Be Uppercase
For multitenant architecture, Oracle states that only uppercase PDB names are supported when upgrading Oracle EBS 12.2 to Oracle AI Database 26ai. If the PDB name is mixed case or lowercase, it must be converted to a case-insensitive PDB name before upgrade.
Check PDB Name
SHOW PDBS;
Or:
SELECT name, open_mode
FROM v$pdbs;
Example Risk
If your PDB name is like:
ebsprod
Ebsprod
ebsProd
Then it should be reviewed and corrected before upgrade planning.
11. TDE Parameters Must Be Verified
If Transparent Data Encryption is used, Oracle requires setting the following parameters:
TDE_CONFIGURATION='KEYSTORE_CONFIGURATION=FILE'
WALLET_ROOT='<wallet directory>'
Check Current TDE Setup
SHOW PARAMETER wallet_root;
SHOW PARAMETER tde_configuration;
Also verify wallet status:
SELECT wrl_type, wrl_parameter, status, wallet_type
FROM v$encryption_wallet;
12. Remove Old Online Patching Editions
This is one of the most important EBS-specific activities.
Oracle recommends checking the number of database editions using:
sqlplus apps/<apps_password> @$AD_TOP/sql/ADZDSHOWED.sql
If the number of editions is high, cleanup must be performed using ADOP phases such as prepare, actualize_all, cutover, cleanup, and edition cleanup scripts.
Generic Flow
adop phase=prepare
adop phase=actualize_all
adop phase=cutover
adop phase=cleanup cleanup_mode=full
Then run:
sqlplus apps/<apps_password> @$AD_TOP/sql/ADZDRUNCLEANUNUSE.sql
Why This Matters
Old editions can increase upgrade complexity and may create unnecessary overhead during dictionary operations. Cleaning unused editions gives a cleaner database state before upgrade.
13. Unsupported Products Must Be Reviewed
Oracle lists some Oracle EBS products that are currently not supported with Oracle EBS 12.2 on Oracle AI Database 26ai. These include:
| Unsupported Product |
|---|
| Demand Signal Repository |
| Oracle Enterprise Data Warehouse |
| Oracle Enterprise Planning and Budgeting |
| Oracle Project Portfolio Analysis |
Oracle also notes that Enhanced Project Performance Reporting in Oracle Project Planning and Control is not currently available with Oracle AI Database 26ai, although Project Performance Reporting remains supported with Oracle Support assistance.
Apps DBA Action
Before upgrade, run a product usage review:
SELECT application_id, application_short_name, product_code, status
FROM fnd_product_installations fpi,
fnd_application fa
WHERE fpi.application_id = fa.application_id
ORDER BY application_short_name;
14. Features Not Yet Certified
The note also says the following Oracle AI Database 26ai features are not yet certified with Oracle EBS 12.2:
| Database Feature |
|---|
| Transportable Database |
| Transportable Tablespaces |
This is important for DBAs planning migration strategies. Do not assume every database feature is automatically certified for EBS.
15. Known Issues to Consider
The document highlights known issues when using Oracle AI Database 26ai with EBS 12.2.
15.1 FIPS Parameters Not Supported
Oracle EBS is not certified with:
DBFIPS_140=TRUE
FIPS_140=TRUE
Using these settings with EBS and Oracle AI Database 26ai can cause errors.
Check
SHOW PARAMETER DBFIPS_140;
Also check FIPS.ora at OS/security configuration level if applicable.
15.2 Oracle Workflow Builder Connection Issue
A known issue prevents Oracle Workflow Builder from connecting directly to Oracle AI Database 26ai. The workaround is to use Workflow Definitions Loader, also known as WFLOAD, for uploading and downloading workflow definitions.
Generic WFLOAD Example
WFLOAD apps/<apps_password> 0 Y DOWNLOAD workflow_file.wft ITEM_TYPE
Upload example:
WFLOAD apps/<apps_password> 0 Y UPLOAD workflow_file.wft
15.3 Oracle JDeveloper JDBC Driver Must Be Upgraded
To connect Oracle JDeveloper to Oracle AI Database 26ai, the JDBC driver must be upgraded as per Oracle guidance.
This is especially important if your team uses JDeveloper for:
- OAF personalization/customization
- Extension development
- Java-based custom components
- Technical debugging
16. Recommended Apps DBA Upgrade Readiness Checklist
| Area | Validation |
|---|---|
| Certification | Confirm EBS 12.2, OS, DB, and platform certification |
| OS | Confirm app tier and DB tier are on Oracle Linux |
| Source DB | Confirm direct upgrade path from current database version |
| EBS Release | Confirm minimum EBS 12.2.7 or required equivalent level |
| AD/TXK | Confirm Delta 16 or latest AD/TXK level |
| Interop Patches | Apply mandatory interoperability patches |
| 10.1.2 Oracle Home | Apply required patches and relink components |
| AutoConfig | Run successfully on DB and apps tier |
| EBS_SYSTEM | Complete system schema migration |
| Passwords | Enable case-sensitive passwords |
| PDB | Confirm uppercase/case-insensitive PDB naming |
| TDE | Validate WALLET_ROOT and TDE_CONFIGURATION |
| Editions | Cleanup old online patching editions |
| Unsupported Products | Confirm business is not using unsupported modules |
| Known Issues | Review Workflow Builder, FIPS, JDeveloper JDBC issues |
| Performance | Complete batch, online, and lifecycle testing |
| Fallback | Prepare backup, restore, and rollback strategy |
17. Suggested Production Upgrade Strategy
For a real production EBS environment, the safest approach is:
Phase 1: Assessment
Review certification, current EBS version, database version, OS, patches, and product usage.
Phase 2: Clone Testing
Perform the full upgrade on a production-like clone.
Phase 3: Functional Validation
Ask business users to validate critical flows such as:
- Login
- Purchase order
- Sales order
- Invoice
- Payment
- Receipt
- GL posting
- Month-end concurrent programs
- Workflow approvals
- Reports
- Interfaces
Phase 4: Performance Benchmarking
Compare before and after upgrade performance for:
- Long-running concurrent requests
- Month-end jobs
- Custom reports
- Forms response time
- OAF page response time
- Workflow processing
- Interface processing
Phase 5: Cutover Planning
Prepare a detailed minute-by-minute cutover plan including:
- Backup
- Application shutdown
- Database upgrade
- Post-upgrade scripts
- AutoConfig
- Application startup
- Smoke testing
- Business validation
- Rollback decision point
18. Conclusion
The move from Oracle Database 19c to Oracle AI Database 26ai for Oracle E-Business Suite 12.2 is a major technical milestone. However, it requires careful planning, patching, validation, and business testing.
For Apps DBAs, the most important message is simple:
Do not treat this as a direct database upgrade only. Treat it as a complete EBS technology stack interoperability project.
The success of this upgrade depends on proper certification review, prerequisite patching, AutoConfig readiness, EBS_SYSTEM migration, password configuration, PDB naming, TDE setup, online patching edition cleanup, unsupported product review, and complete performance testing.
A well-prepared Apps DBA team can make this upgrade smooth, controlled, and production-safe.
KB / KA Articles Referenced
| Article ID | Article Title / Purpose |
|---|---|
| KA1151 | Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle AI Database 26ai |
| KA1001 | Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure |
| KA1035 | Oracle E-Business Suite Performance Best Practices |
| KB150043 | hcheck.sql - Script to Check Data Dictionary for Known Problems |
| KA1134 | Oracle E-Business Suite Release 12.2: Patching Technology Components Guide |
| KA1054 | Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 |
| KB556816 | Applying the R12.ATG_PF.C.Delta.11 Release Update Pack |
| KA1062 | Using the OracleAS 10.1.2 Forms and Reports Builders with Oracle E-Business Suite Release 12 |
| KA1032 | Integrating Oracle E-Business Suite Release 12.2 with Oracle Database Vault 19c using EBS_SYSTEM |
| KB837303 | Oracle E-Business Suite Release 12.2 System Schema Migration |
| KA1149 | Implementing Case-Insensitive Pluggable Database Names with Oracle E-Business Suite Release 12.2 on Oracle Database 19c Multitenant Architecture |
| KA1452 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai — Single Node |
| KA1261 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai on Oracle RAC Multitenant — Single PDB |
| KA1209 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai Using Existing Physical Standby |
| KA1127 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai on Oracle Base Database Service DB Systems |
| KA1194 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai Using Existing Physical Standby on Oracle Base Database Service DB Systems |
| KA1142 | Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to Oracle AI Database 26ai on Oracle Exadata Database Service on Dedicated Infrastructure and Cloud@Customer |
| KB371525 | Oracle E-Business Suite Requirements for Connecting Oracle JDeveloper 10g to Oracle AI Database 26ai |
Source: uploaded Oracle interoperability document.
Blogspot Section You Can Add
Important My Oracle Support Articles for EBS 12.2 and Oracle AI Database 26ai
Before planning the upgrade, Apps DBAs should carefully review the related My Oracle Support articles. These articles cover interoperability, cloud deployment, performance best practices, dictionary health checks, technology stack patching, AD/TXK updates, EBS_SYSTEM migration, PDB naming, Database Vault implications, and architecture-specific upgrade paths.
The most important starting point is KA1151, which is the main interoperability note for Oracle E-Business Suite Release 12.2 with Oracle AI Database 26ai. From there, DBAs should also review the relevant upgrade article based on their environment, such as single node, RAC multitenant, physical standby, OCI Base Database Service, or Exadata Cloud deployment.
For production systems, these MOS articles should be treated as mandatory reference documents, not optional reading. They help ensure that the upgrade is certified, supported, and executed with proper EBS-specific prerequisites.
No comments:
Post a Comment