Enterprise Manager Generic (MOSC)

MOSC Banner

Managing Opatch when Patching with OEM

edited Nov 2, 2016 9:23AM in Enterprise Manager Generic (MOSC) 14 commentsAnswered ✓

I am using Patches and Updates in OEM for patching. When I start a patch cycle, I expect the patches applied to Dev then QA and then finally PROD to be the same, including opatch. However, every night the job opatch_patch_updates runs and downloads the latest and greatest version of opatch. So, I can apply a set of patches to QA with opatch 123 but when I go to apply the patches to PROD, the opatch version may have been updated to the latest opatch - opatch 234.

I can manage it by suspending the opatch_patch_update job but I wondering if anyone else has found a better solution.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center