13.5: Analyzing the RU01 Patch on the 13.5 OMS Using -bitonly Mode Fails With Error: OMSPatcher failed: null
(Doc ID 2812403.1)
Last updated on OCTOBER 18, 2022
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Analyzing the 13.5 RU01 patch using the -bitonly mode (omspatcher apply -analyze -bitonly) fails with the error
The following sub-patch(es) are applicable:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.oms 32941631,32941696,32941662,32860349,32941609,32941673,32941706,32941575,32941713,32941618,32840049,32941645,32835403,32835412 32941631,32941696,32941662,32860349,32941609,32941673,32941706,32941575,32941713,32941618,32840049,32941645,32835403,32835412_opatch2021-10-05_21-31-49PM_1.log
[ Error during Patch and deploy artifacts Phase]. Detail: Patch application failed to complete some of the actions.
OMSPatcher failed: null
--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OMSPatcher has been invoked with bitonly option but the System patch provided has deployment metadata.
Invocation in bitonly mode will prevent OMSPatcher from deploying artifacts.
--------------------------------------------------------------------------------
Log file location: <OMS_HOME>/cfgtoollogs/omspatcher/32835392/omspatcher_2021-10-05_21-31-40PM_analyze.log
OMSPatcher failed with error code 240
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |