Oracle EBS 12.2 adop Patching Checklist (Free)

0%

0 of 28 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Before you start

Read the readme of every patch and note prerequisites and post-install stepsCRITICALCheck that no previous patching cycle is left incomplete, using adop status reportingCRITICALTake a backup of the database and application file systemsCRITICALConfirm free disk space on both file systems and in the databaseSource the run file system environment before running adopMerge patches where the readme or your policy asks for itNotify users and support teams of the patching window

Prepare phase

Run adop phase=prepare to create the patch edition and sync the patch file systemCRITICALConfirm the prepare phase finished with no failed workersCheck that the patch file system is a clean copy of run before applyingRecord the session id for the cycle

Apply and finalize

Run adop phase=apply patches=<number> for each patch or merged patchCRITICALReview the adop log files and worker logs for errorsCRITICALResolve failed jobs and restart the apply phase with the correct optionsRun adop phase=finalize to compile invalid objects and prepare for cutoverCheck invalid objects count in the patch edition

Cutover and cleanup

Schedule the short outage and stop users before cutoverCRITICALRun adop phase=cutover to switch the patch edition to runCRITICALStart services on the new run file system and verify accessRun adop phase=cleanup to remove obsolete editions and objectsCRITICALRun a full cleanup mode when the policy requires it and the cycle is verifiedRun the file system clone if the old run file system must be synced to the new one

After patching

Run the post-install steps from each patch readmeCRITICALCheck invalid objects and compile what remainsSmoke test login, key forms, a concurrent request and a workflowRun regression tests for modules touched by the patchUpdate the patch log with patch numbers, dates and who applied themApply the same patch set to the other environments in order

Run the cycle on a test copy first. Record start and end time of each phase so you can estimate the production window.

Turn your patch runbooks into a DBA assistant

An optional discussion on a private assistant over your own EBS runbooks and logs.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Print or export the list for each patching cycle and fill it in as you go. Add the patch numbers and the time each phase started and ended in your change ticket. Use the checklist on your test instance first and keep the notes, because the timings from test are what you will quote when you ask the business for a cutover window. Keep one cycle open at a time per environment.

The adop phases in order

The prepare phase creates a patch edition and syncs the patch file system. The apply phase applies patches to the patch file system and database edition, and you can apply more than one patch in this phase. Finalize does the compile work that can be done ahead of cutover. Cutover is the short outage when the patch edition becomes the run edition. Cleanup removes the obsolete objects. Hotpatch mode applies a patch directly to the run file system and needs downtime, so use it only when the readme says so.

adop phase=prepare
adop phase=apply patches=<number>
adop phase=finalize
adop phase=cutover
adop phase=cleanup

Common mistakes

Frequent problems include starting a new cycle while the previous one is incomplete, skipping the readme post-install steps, and running out of space on the patch file system. Another is running cleanup before the team has verified the cutover. Read the log directory that adop prints at the start of each phase, because worker failures are in the logs, not always on the screen. Never delete adop session data by hand.

Check adop status before starting
Do not skip the readme steps
Verify cutover before cleanup
Keep logs for each cycle

Frequently Asked Questions

What are the adop phases?

The standard online patching phases are prepare, apply, finalize, cutover and cleanup. A separate fs_clone phase syncs the file systems. You run them in order for a patching cycle, and users stay online until cutover.

Do I need downtime to patch EBS 12.2?

For online patching, downtime is limited mainly to the cutover phase. Patches applied in hotpatch mode or patches that require downtime according to their readme need a longer outage. Always read the patch readme before you plan the window.

Can I apply several patches in one cycle?

Yes. You can pass several patch numbers to the apply phase in one cycle, and you can merge patches when the readme or your policy asks. Test the combination first, since one failing patch can hold up the whole cycle.

What if a cycle is left incomplete?

Check the adop status first. Depending on the state you may restart the failed phase, or abort the cycle if the guidance for that state allows it. Do not start a new cycle until the old one is closed or aborted according to Oracle documentation.

If your patch runbooks live in scattered documents, we can discuss an on-premises assistant that reads your own runbooks and patch logs and answers DBA questions, with no data leaving your network.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Oracle EBS 12.2 Patching Checklist (adop Online Patching Cycle)