Running Oracle EBS After Oracle Stops Patching
What actually breaks, what doesn’t, and how to correct production data safely when no patch is coming.
PDF32 pagesSustaining Support
Email me the guide- Oracle stopped patching your release and nobody has written down what that actually changes.
- Something is wrong in production data and the old answer — “log an SR, wait for the patch” — no longer exists.
- Your customization inventory is a folder of old Word documents and one developer’s memory.
- You suspect things are failing silently — jobs completing “Normal” while producing nothing.
Running Oracle EBS After Oracle Stops Patching
32 pagesPart One — Reading your own risk
- What Sustaining Support Actually Removes
- The Four Stability Pillars
- Patch Governance Without a Patch Stream
Part Two — Correcting data safely
- When a Data Fix Is the Right Answer
- The Four-Stage Decision Framework
- Backup, Registry and Rollback
- A Worked Example, End to End
- The Six-Step Execution Procedure
Part Three — Governing what remains
- The Five Governance Pillars
- Silent Failures
Appendices
- The Data Fix Checklist
- The Customization Inventory Template
- Diagnostic Coverage Reference
- Name the four things Sustaining Support removes — including the two most shops misjudge.
- Decide, with a four-stage framework, when a production data fix is justified and when it is not.
- Run a data correction the safe way: functional first, direct fix second, hard stop, documented — in that order every time.
- Build the backup, registry and rollback infrastructure that makes a production fix reversible.
- Stand up patch governance that still means something with no patch stream behind it.
- Find the silent failures — the worst problems on a frozen instance complete with status Normal.
What Sustaining Support Actually Removes
Four things stop. Two of them are widely understood. The other two are where unsupported instances quietly go wrong.
| What stops | Consequence | How well it’s understood |
|---|---|---|
| New patches, including regulatory and year-end updates | 1099 form layouts and e-file formats freeze at their last delivered version. Country localization and VAT report formats stop evolving. | Understood in principle; the specific year-end deadline is usually discovered in December |
| Security patches (CPUs) | Newly disclosed vulnerabilities in the application tier are never remediated by Oracle. Compensating controls become the whole defence. | Well understood — usually the reason the CIO is asking |
| Bug fixes for the application code | A defect in a delivered program is now yours to diagnose and correct. | Widely misjudged |
| New certifications | Browsers, Java, databases and operating systems move on without you. | Discovered at the next infrastructure refresh |
From Chapter One.
William A. Green has spent 27 years inside Oracle E-Business Suite Financials — as a former Oracle employee, as a functional and technical lead on more than 35 implementations, and for six years at Rimini Street supporting Fortune 500 EBS clients on releases Oracle had stopped patching. He writes fixes for a living. This guide is the part of that work that fits in a PDF.