hello.
you can try to figure where is the problem after running your opatch comman
again after setting
export OPATCH_DEBUG=true
Best Regards,
Oleksandr Denysenko
14.09.2019 22:03, Andrew Kerber пишет:
I downloaded the Opatch listed for the apr 2019 patch set, and I dont see one for the Jul 2019 patch set. p6880880_190000_Linux-x86-64.zip, so it has to be the right release. I would normally suspect an issue with the hosts file, but I just cant find anything.
On Sat, Sep 14, 2019 at 12:47 PM Mladen Gogala <gogala.mladen@xxxxxxxxx <mailto:gogala.mladen@xxxxxxxxx>> wrote:
On 9/14/19 1:35 PM, Andrew Kerber wrote:
I am doing some rehearsal prior to patching a cluster, so I built a testHi Andrew!
environment. When I
run the opatchauto command, its telling me that the GI home is shared, even
though it isnt
shared. Any thoughts? I dont think its related to dns, I have checked
that twice
:
OPATCHAUTO-72030: Execution mode invalid.
OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared.
OPATCHAUTO-72030: Execute in non-rolling mode.
OPatchAuto failed.
-- Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Have you checked for the new OPatch version? I have encountered many
strange opatch and
opatchauto errors that were resolved by the new version of opatch. Try
downloading the latest
p6880880 for your platform. I have also encountered strange errors when I
have mistakenly
downloaded 32 bit patches and tried applying them to 64 bit linux.
Regards
-- Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
