For those of you who are set up to receive notifications when various MOS Notes are updated, you probably noticed a bit of activity in the last day or so. In particular, I saw MOS 1617461.1 (Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2) was updated\u2026. that took me to MOS 2525754.1 (Using UTL_FILE_DIR or Database Directories for PL\/SQL File I\/O in Oracle E-Business Suite Releases 12.1 and 12.2) where I saw the statement:<\/p>\n\n\n\n
\n“Note: The minimum certified version of Oracle Database 23ai for Oracle E-Business Suite is Oracle Database 23ai (23.5.0.24.07). “<\/p>\n<\/blockquote>\n\n\n\n
At that point, I became extremely excited. Wait, it’s certified now? Wow!
So, I went to check out the EBS TechStack blog, where I saw the actual announcement:<\/p>\n\n\n\n
https:\/\/blogs.oracle.com\/ebstech\/post\/ebs-122-now-certified-with-database-23ai-onpremises-exadata<\/a><\/p>\n\n\n\nBut, here’s my problem.<\/p>\n\n\n\n
I don’t have an Exadata in my basement. And RDBMS 23ai has still not been released for on-prem deployments. So, obviously, I can’t do much with it as of yet.<\/p>\n\n\n\n
Here’s what I can do.<\/p>\n\n\n\n
The announcement, even though it’s just for Exadata, brings with it a bunch of updated MOS notes. These MOS notes can provide us a preview of what we’ll have to do when it is, eventually, certified for on-prem deployments to other platforms.<\/p>\n\n\n\n
In particular, take a look at:<\/p>\n\n\n\n
Information Center: Oracle Database 23ai with Oracle E-Business Suite 12.2 (Doc ID 3018618.2)
Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 23ai (Doc ID 2962871.1)<\/p>\n\n\n\nSo, if you’re planning to upgrade your EBS R12.2 environment to use 23ai, take a look at those MOS notes. They will provide a basic roadmap to help you get ready. Some of the key items that you can do NOW in order to get ready:<\/p>\n\n\n\n
\n
- Upgrade to RDBMS 19c if you’re not there already! [MOS 265589.2 is a good starting point]<\/li>\n\n\n\n
- Apply R12.AD.C.Delta.16 and R12.TXK.C.Delta.16 [MOS 1617461.1]<\/li>\n\n\n\n
- Implement Case-Insensitive PDB Names [MOS 2782130.1]<\/li>\n\n\n\n
- Migrate to the EBS_SYSTEM schema [MOS 2755875.1]<\/li>\n\n\n\n
- Enable Unified Auditing [MOS 2777404.1]<\/li>\n<\/ul>\n\n\n\n
Additionally, review the patches mentioned in the EBS R12.2\/23ai Interoperability notes [MOS 2962871.1]. I wouldn’t worry about applying any of the actual 23ai Interoperability patchs quite yet (it’s quite possible that patch could change or be replaced when the regular certification is announced). But, MOS 2962871.1 will still give you a good idea of where you need to be with other “normal” patches.<\/p>\n\n\n\n
AS ALWAYS, when applying patches, be sure to test things in a non-production enviromnent before moving them into production.<\/p>\n\n\n\n
And enjoy going down the EBS MOS Note rabbit hole\u2026 \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
For those of you who are set up to receive notifications when various MOS Notes are updated, you probably noticed a bit of activity in the last day or so. In particular, I saw MOS 1617461.1 (Applying the Latest AD … Continue reading