Exadata General (MOSC)

MOSC Banner

opatchauto -- prepare-clone not creating clone db home on exadata 2nd node GI+non RAC DB

edited Jul 21, 2022 9:38AM in Exadata General (MOSC) 16 commentsAnswered

Hi

I ran /opt/app/oracle/product/rdbms/19.8.0.0.200714/OPatch/opatchauto apply -prepare-clone -oh /opt/app/oracle/product/rdbms/19.8.0.0.200714 on first node coe03entw08 and it succeeded(clone home /opt/app/oracle/product/rdbms/19.15.0.0.220419/db created).

I ran the same on the second node coe03entw07 but it failed saying the clone path /opt/app/oracle/product/rdbms/19.15.0.0.220419/db ALREADY EXIST OR IS INVALID.

Any idea how one can fix that please?

My environment is a GI + Non RAC multitenant database on each exadata KVM with ASM cluster.

GI and DB homes are not shared acrross the nodes.DB homes are shared only by multitenants databases residing on the same host

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