Install, Upgrade, Clone, Patch - EBS (MOSC)

MOSC Banner

Adop Behavior Applying Patches To Standby EBS

edited Oct 28, 2019 11:06AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 4 commentsAnswered ✓

How is adop suppose to work when applying EBS patches to the EBS Standby environment.

In following the document, Oracle Note 1963472.1 Business Continuity for Oracle E-Business Suite Release 12.2 using Oracle 12c (12.1.0.2) Physical Standby Database, in Section 7.3.2.3 Apply the patches to the standby using hotpatch mode using the nodaabaseportion option, Step 3 the syntax is:

adop phase=apply patches=<PATCH NUMBER> apply_mode=hotpatch options=nodatabaseportion

I've used that same syntax to apply five (5) separate patches. With four (4) of the patches I had to use the above syntax and apply the patches to each of my five EBS Apps nodes, applying to the Master Node first then each of the slave nodes. However, with the fifth patch, when applied to the Master Node, adop started remote sessions to my four slave nodes to remotely install the patch on them.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center