How To Avoid Disk Full Issues Because OPatch Backups Take Big Amount Of Disk Space.
(Doc ID 550522.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Universal Installer - Version 10.2.0.1 and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 12.1 to 12.2]
Information in this document applies to any platform.
***Checked for relevance on 03-Jan-2013***
When applying interim patches or Security Patch Update (SPU) (formerly Critical Patch Update (CPU)) patches, OPatch takes a big amount of disk space under $ORACLE_HOME/.patch_storage to store a backup of the affected libraries and modules that have been updated. It even could happen that a disk becomes full in the middle of the patching process.
Regarding this topic, the following questions will be answered in this article:
1. ) If the filesystem gets full in the middle of applying a patch, what is the process to recover?
2. ) Can any of the space be reclaimed from $ORACLE_HOME/.patch_storage?
3. ) Usage of 'opatch util cleanup' to reclaim space from $ORACLE_HOME/.patch_storage
4. ) In preparation for patching systems, is there any way to predict the amount of space that will be required in $ORACLE_HOME/.patch_storage?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!