Exalogic Virtual: Exapatch prePatchCheck For Guest vServers Fails With "No update paths found" Error
(Doc ID 2354040.1)
Last updated on JULY 26, 2018
Applies to:Oracle Exalogic Elastic Cloud Software - Version 188.8.131.52.0 and later
Oracle Virtual Server x86-64
You are applying an Exalogic Patchset Update (PSU) to one or more guest vServers you have previously created in an Exalogic Virtual installation.
However, when running the exapatch prePatchCheck action (/exalogic-lctools/bin/exapatch -a prePatchCheck vserver -h <vSERVER IP ADDRESS>), fails with a message similar to following:
ERROR: Sat Jan 27 15:16:44 EST 2018: YUM update precheck has issues. Inspect logs, resolve any conflicts or other issues manually, and RERUN this script
ERROR: Sat Jan 27 15:16:44 EST 2018: Resolve yum conflicts and retry patching.
INFO: Sat Jan 27 15:16:44 EST 2018: >>>> remove services that launch post patching procedures
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document