Database - RAC/Scalability (MOSC)

MOSC Banner

opatchauto with out-of-place not behaving as advertised

edited Jul 1, 2020 5:00AM in Database - RAC/Scalability (MOSC) 3 commentsAnswered

While trying to patch GI from 18.3.0 to 18.10.0 (as well as databases) I tried the automated out-of-place method (OOP) provided with opatchauto. This is an intermediate action in order to jump to the current 19.7.0 version.

I decided to use the two-steps method: first prepare-clone, second switch-clone, but failed preparing the clone.

/u01/app/18.3.0/grid                                    ==> /u01/app/18.10.0/grid

/u01/app/oracle/product/18.3.0/dbhome_1 ==> /u01/app/oracle/product/18.10.0/dbhome_2

Using this method, files of every Oracle Home are copied to a new path, cloned (registered in the inventory), and patched in the cloned path. The next step would be the switch to this Oracle Home.

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