How to assign unused internal disk space to root and u01 file system on ODA BM
(Doc ID 2617011.1)
Last updated on AUGUST 12, 2020
Applies to:Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
By default ODA systems have around 250-350G (based on hardware type) of unused space on the internal disk.
This document shows how to use some of this unused space for /u01 or / file system.
It is strongly suggested that you should leave at least 100G free space for snapshot backukp during upgrade or backup process.
The ODA is an Engineered System.
Resizing directories including /u01 normally is not supported unless a provided procedure including ODA specific CLI or other methods.
While the following method may or may not work, always perform prudent backups prior to volume and storage alterations.
Patching the ODA system will require enough amount of free space on u01 root and opt file system. In some cases like the system has go through a lot of upgrade processes or have a lot oracle homes which will cause some of these file system cannot have enough space. Also because of large logs generation, some of the file system may run out of space frequently.
Please try below method first :
1. Try to purge all old logs following the Note: purgeLogs: Cleanup traces, logs in one command (Doc ID 2081655.1)
2. After 220.127.116.11.0 we can use the command: odacli cleanup-patchrepo to release some space.
Only if used above way cannot release enough space or the space used up quickly after that we can try to grow /u01 root or /opt file system on ODA BM env using unused internal disk space.
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