EM13c: RU Patch apply failed with error "Error 3 : Could not write output file: No space left on device"
(Doc ID 3036091.1)
Last updated on SEPTEMBER 25, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
RU Patch apply to OMS Home failed with below error
[<Date/Timestamp>] OMSPatcher failed to execute some of the patching steps. Please check the Patching summary,individual logs and try to resolve the issue. Once the issue is resolved,Please execute below command to complete patching session:
omspatcher resume
------------------------------------------------------------------------------------------------
OMSPatcher wont allow any other patching operations unless the script is executed successfully
------------------------------------------------------------------------------------------------
[<Date/Timestamp>] [ Error during Patch and deploy artifacts phase ] Detail: OMSPatcher failed during deployment of the MRS artifact.
OUI-67073:OMSPatcher failed: OMSPatcher failed to execute some of the OMS operations. Please refer log file(s) for details.
[<Date/Timestamp>] Finishing ApplySession at <Date/Timestamp>
[<Date/Timestamp>] Total time spent waiting for user-input is 16 seconds. Finish at <Date/Timestamp>
[<Date/Timestamp>] Log file location: <MW_HOME>/cfgtoollogs/omspatcher/36335368/omspatcher_<Date/Timestamp>_apply.log
[<Date/Timestamp>] Stack Description: java.lang.RuntimeException: OMSPatcher failed to execute some of the OMS operations. Please refer log file(s) for details.
<MW_HOME>/omspatcher/<Date/Timestamp>_SystemPatch_36335368_21/emctl_register_default_collection_<Date/Timestamp>.log
[<Date/Timestamp>] Command used to update MRS is : <MW_HOME>/bin/emctl register oms metadata -service default_collection -file_list <MW_HOME/.omspatcher_storage/registerFile/36335368/default_collection_oracle.sysman.si.txt -pluginId oracle.sysman.si
[<Date/Timestamp>] Oracle Enterprise Manager Cloud Control 13c Release 5
[<Date/Timestamp>] Copyright (c) 1996, 2021 Oracle Corporation. All rights reserved.
[<Date/Timestamp>] oracle_si_netswitch.xml: Metadata registration successful
[<Date/Timestamp>] oracle_si_switch_arista_ssh.xml: Metadata registration successful
[<Date/Timestamp>] oracle_si_switch_arista_snmp.xml: Metadata registration successful
[<Date/Timestamp>] oracle_si_switch_cisco_ios.xml: Metadata registration successful
[<Date/Timestamp>] oracle_si_switch_cisco_ios_snmp.xml: Metadata registration successful
[<Date/Timestamp>] oracle_si_switch_juniper_junos.xml: Metadata registration successful
[<Date/Timestamp>] EM-04041: Error occurred during Metadata registration. Error is: null. Check <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log for more details.
<EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log
<Date/Timestamp>,402 [main] WARN util.EmctlMetadataService - Could not delete the temp directory <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/tmp/Intermediate_xsds properly
<Date/Timestamp>,416 [main] INFO util.EmctlMetadataService - Calling generateIntermediateXSD for included XSD Schedule.xsd saving in <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/tmp/Intermediate_xsds/default_collection/internal_addon. Got input stream for included XSD: sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream@2dbfa972
<Date/Timestamp>,420 [main] INFO util.EmctlMetadataService - Done generating intermediate XSD at <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/tmp/Intermediate_xsds/default_collection/internal_addon/Schedule.xsd from stream sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream@2dbfa972
<Date/Timestamp>,420 [main] INFO util.EmctlMetadataService - Done generating intermediate XSD at <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/tmp/Intermediate_xsds/default_collection/internal_addon/TargetCollection.xsd_internal_addon from stream sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream@41aebbb4
<Date/Timestamp>,819 [main] ERROR util.EmctlMetadataService - Error 3 : Could not write output file: No space left on device
java.io.IOException: No space left on device
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 |