The patching of an Oracle Database Appliance needs to be secured. This is because it won’t limit to patching the databases: there is plenty of other components embedded with the patch, the goal being to keep everything updated. A possible rollback may be needed.<\/p>\n\n\n\n
For sure, there is no possible rollback for firmwares, BIOS and ILOM (it’s unlikely you would need to go back to previous version), but you may need to rollback when it comes to patching the OS and the GI stack. Unlike DB homes, OS and GI stack are located on the ODA local disks, and can be protected during patching with LVM snapshots. This is the purpose of ODABR: making LVM snapshots of \/, \/u01 and \/opt before applying the patch. If something goes wrong, you can revert to the previous stable state.<\/p>\n\n\n\n
ODABR will need enough space on local disks for creating the snapshots, and sometimes available free space is not enough. How to deal with that?<\/p>\n\n\n\n
Before using ODABR, I would recommend doing a cleanup of the following filesystems: \/, \/u01 and \/opt. You will need 20+% of free space in these filesystems, otherwise the patch prechecks won’t give you the green light. ODABR is based on Copy-On-Write technology, meaning that old versions of the changed blocks will be kept for going back in time if needed. Don’t unzip the patch files after taking the snapshots if the patch files reside on the local disks! Once you’re ready to patch, the minute before registering the patch and applying the DCS components update, you can use ODABR to take the snapshots.<\/p>\n\n\n\n
Once you successfully applied the system patch and GI patch, and once you verified that everything runs fine with the new GI binaries, you can safely use ODABR to delete the snapshots. If you need to apply multiple patches, make new snapshots before each jump, you will never need to revert to the oldest version once you are in a stable intermediate version.<\/p>\n\n\n\n
Absolutely not. DB homes are located under \/u01\/app\/odaorahome, a dedicated ACFS filesystem on the DATA diskgroup. You don’t need snapshot features on this very filesystem because patching a DB home will create a new home and move the database into this new DB home, the old one being kept as long as you want to. You can delete older DB homes months after patching was done. I usually delete old ones as part of the patching job once everything is fine, but I always backup the old DB home with a tar czf in case of. If you need to revert a database to an old DB home, you can do it manually and use a RMAN backup to restore the database, or eventually rollback the datapatch if needed. This is rarely used.<\/p>\n\n\n\n
ODABR relies on LVM snapshots, not something really specific to ODA. Snapshots are stored in the remaining space of the Volume Group. Most ODAs were sold with 2x 500GB local disks (SSDs) protected with a software RAID and allocated to a single Volume Group VolGroupSys. When doing the ODA setup, only a part of the storage is allocated to the system volumes as Logical Volumes (LogVolSwap, LogVolOpt, LogVolU01, LogVolRoot), meaning that a comfortable amount of space is available for ODABR:<\/p>\n\n\n\n
pvs\n PV VG Fmt Attr PSize PFree\n \/dev\/md126p3 VolGroupSys lvm2 a-- 446.09g 285.09g\n\n\/opt\/odabr\/odabr backup -snap\n...\nSUCCESS: 2026-04-22 17:10:33: LVM snapshots backup done successfully\n\npvs\n PV VG Fmt Attr PSize PFree\n \/dev\/md126p3 VolGroupSys lvm2 a-- 446.09g 150.09g<\/code><\/pre>\n\n\n\nODABR additionally backups ASM metadata, because if you revert to a previous set of LVM snapshots with an older GI release, your ASM metadata would also need to be in the corresponding version.<\/p>\n\n\n\n
Default snapshot sizes and real needs<\/h2>\n\n\n\n
Default snapshots size is the size of the Logical Volumes, here is an example for a 30GB \/, a 55GB \/opt and a 50GB \/u01:<\/p>\n\n\n\n
\/opt\/odabr\/odabr infosnap\n\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n odabr - ODA node Backup Restore - Version: 2.0.2-06\n Copyright 2013, 2025, Oracle and\/or its affiliates.\n --------------------------------------------------------\n RACPack, Cloud Innovation and Solution Engineering Team\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n\nLVM snap name status COW Size Data%\n------------- ---------- ---------- ------\nroot_snap active 30.00 GiB 0.01%\nopt_snap active 55.00 GiB 0.01%\nu01_snap active 50.00 GiB 0.01%<\/code><\/pre>\n\n\n\nThis is quite confortable, there won’t be 100% blocks changed during the patching, for sure. If you don’t have these 135GB of free space, you can specify lower values for the snapshots, but make sure to limit modifications on the files residing on these 3 Logical Volumes during the patch:<\/p>\n\n\n\n
\/opt\/odabr\/odabr backup -snap -osize 18 -rsize 10 -usize 25<\/code><\/pre>\n\n\n\nThese settings were enough for my latest patches.<\/p>\n\n\n\n
The ODA X9-2 series exception<\/h2>\n\n\n\n
As far as I remember, ODAs always had a confortable system disk sizes. 500GB is large enough for OS, odacli and GI stack plus a couple of files of your own. Since version 19.10, DB homes and diagnostic destination are now located within ACFS volumes, meaning that it doesn’t take a single MB from the local disks:<\/p>\n\n\n\n
df -h | grep -e Filesystem -e u01\nFilesystem Size Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolU01 49G 27G 20G 58% \/u01\n\/dev\/asm\/odabase_n0-225 30G 2.5G 28G 9% \/u01\/app\/odaorabase0\n\/dev\/asm\/orahome_sh-225 80G 44G 37G 54% \/u01\/app\/odaorahome<\/code><\/pre>\n\n\n\nAs 19.10 was already available when X9-2 was released, Oracle decided to decrease the system disks from 500GB to 250GB, meaning that you didn’t have the margin you had with the previous generations. The problem was solved with X10 series and onwards, system disks are now back to 500GB as they were on X8-2 series.<\/p>\n\n\n\n
What I mean is that you’ll be most probably concerned about filesystem contention for ODABR if you have X9-2 series.<\/p>\n\n\n\n
How can you deal with insufficient disk space when using ODABR?<\/h2>\n\n\n\n
Imagine you have this kind of configuration:<\/p>\n\n\n\n
pvs\n PV VG Fmt Attr PSize PFree\n \/dev\/md126p3 VolGroupSys lvm2 a-- 222.56g 2.56g<\/code><\/pre>\n\n\n\nOn this ODA, \/opt and \/u01 have been extended for some reasons, and there is almost no space left on the Volume Group.<\/p>\n\n\n\n
If you try to use ODABR to take snapshots, you will get this error:<\/p>\n\n\n\n
Available LVM size X is less than required snapshot size Y<\/code><\/pre>\n\n\n\n2.56GB is way too small for using ODABR: you will need to reduce the size of \/u01, \/opt or both. First, a cleanup is needed to free up some space. Once done, you’ll be able to reduce the size of \/u01 and\/or \/opt. But these filesystems will need to be unmounted. And it cannot be done without stopping\/starting some processes. Actually, pretty much all the processes running on your ODA.<\/p>\n\n\n\n
Stopping the processes and reducing the filesystems<\/h2>\n\n\n\n
Let’s reduce the \/u01 and \/opt Logical Volumes’ size in this example:<\/p>\n\n\n\n
su - root\n\ndf -h \/u01 \/opt\n\nFilesystem Size Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolU01 61G 23G 36G 39% \/u01\n\/dev\/mapper\/VolGroupSys-LogVolOpt 70G 48G 22G 68% \/opt\n\nexport ORACLE_HOME=\/u01\/app\/19.30.0.0\/grid\n$ORACLE_HOME\/bin\/crsctl stop crs\n\nlvreduce -L 50G \/dev\/VolGroupSys\/LogVolU01 -r\nDo you want to unmount \"\/u01\" ? [Y|n] y\numount: \/u01: target is busy.\nfsadm: Cannot proceed with mounted filesystem \"\/u01\".\n \/usr\/sbin\/fsadm failed: 1\n Filesystem resize failed.\n\nlsof \/u01\/\nCOMMAND PID USER FD TYPE DEVICE SIZE\/OFF NODE NAME\njava 23727 root 26r REG 252,3 16303574 1208968 \/u01\/app\/19.30.0.0\/grid\/jlib\/srvm.jar\n\nkill -9 23727 ; umount \/u01\numount: \/u01: target is busy.\n\nkill -9 23727 ; umount \/u01\n-bash: kill: (23727) - No such process\n\nlvreduce -L 50G \/dev\/VolGroupSys\/LogVolU01 -r\nfsck from util-linux 2.32.1\n\/dev\/mapper\/VolGroupSys-LogVolU01: 76718\/4063232 files (7.3% non-contiguous), 6220430\/16252928 blocks\nresize2fs 1.46.2 (28-Feb-2021)\nResizing the filesystem on \/dev\/mapper\/VolGroupSys-LogVolU01 to 13107200 (4k) blocks.\nThe filesystem on \/dev\/mapper\/VolGroupSys-LogVolU01 is now 13107200 (4k) blocks long.\n\n Size of logical volume VolGroupSys\/LogVolU01 changed from 62.00 GiB (1984 extents) to 50.00 GiB (1600 extents).\n Logical volume VolGroupSys\/LogVolU01 successfully resized.\n\n\nsystemctl stop initdcsagent\nsystemctl stop initdcscontroller\nsystemctl stop initdcsadmin\nsystemctl stop oda-mysql\nsystemctl stop oracle-ODA_DCS-ODA_DCS0\nsystemctl stop oracle-tfa\nsystemctl stop oracle-ohasd\n\n\nlsof \/opt\nCOMMAND PID USER FD TYPE DEVICE SIZE\/OFF NODE NAME\nbash 6697 root cwd DIR 252,2 4096 1703937 \/opt\/dbi\nOSWatcher 7799 grid cwd DIR 252,2 4096 2235031 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\nOSWatcher 7799 grid 1w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nOSWatcher 7799 grid 2w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nOSWatcher 7799 grid 255r REG 252,2 65286 2235047 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\/OSWatcher.sh\nOSWatcher 9903 grid cwd DIR 252,2 4096 2235031 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\nOSWatcher 9903 grid 1w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nOSWatcher 9903 grid 2w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nOSWatcher 9903 grid 255r REG 252,2 8035 2235046 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\/OSWatcherFM.sh\nsleep 56757 grid cwd DIR 252,2 4096 2235031 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\nsleep 56757 grid 1w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nsleep 56757 grid 2w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nsleep 56835 grid cwd DIR 252,2 4096 2235031 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/oswbb\nsleep 56835 grid 1w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\nsleep 56835 grid 2w REG 252,2 4703 2228894 \/opt\/oracle\/dcs\/oracle.ahf\/data\/repository\/suptools\/dbioda01\/oswbb\/grid\/run_1773762195.log (deleted)\n\nkill -9 7799 9903\n\n\nlvreduce -L 55G \/dev\/VolGroupSys\/LogVolOpt -r\nDo you want to unmount \"\/opt\" ? [Y|n] y\nfsck from util-linux 2.32.1\n\/dev\/mapper\/VolGroupSys-LogVolOpt: Inode 655911 extent tree (at level 1) could be narrower. IGNORED.\n\/dev\/mapper\/VolGroupSys-LogVolOpt: 57911\/4587520 files (2.4% non-contiguous), 12785629\/18350080 blocks\nresize2fs 1.46.2 (28-Feb-2021)\nResizing the filesystem on \/dev\/mapper\/VolGroupSys-LogVolOpt to 14417920 (4k) blocks.\nThe filesystem on \/dev\/mapper\/VolGroupSys-LogVolOpt is now 14417920 (4k) blocks long.\n\n Size of logical volume VolGroupSys\/LogVolOpt changed from 70.00 GiB (2240 extents) to 55.00 GiB (1760 extents).\n Logical volume VolGroupSys\/LogVolOpt successfully resized.\n<\/code><\/pre>\n\n\n\nAs I don’t want to manually restart the various processes, and as I usually do a sanity reboot before patching, let’s reboot the server. Everything will then be properly started after.<\/p>\n\n\n\n
reboot\n...\n\ndf -h \/u01 \/opt\nFilesystem Size Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolU01 49G 23G 25G 49% \/u01\n\/dev\/mapper\/VolGroupSys-LogVolOpt 54G 48G 4.0G 93% \/opt\n<\/code><\/pre>\n\n\n\nFurther recommendations<\/h2>\n\n\n\n
You don’t really need a lot of space on the system disks. Put your patch files and other specific files on a NFS volume shared across your ODAs, and keep the system disks to their default’s size to keep a confortable margin for ODABR, especially on ODA X9-2 series. Eventually, allow a few more GB to \/u01 and\/or \/opt but keep at least 70GB free for ODABR snapshots. Anticipate the patching and test ODABR several days before, it does not cost anything, and snapshots can be removed immediately without any downtime. Worst case is having to patch now and discovering that there is no space left on disks for using ODABR.<\/p>\n\n\n\n
Not being able to secure your patch with ODABR is the second NOGO for patching, the first one being a faulty component reported by odaadmcli show server.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
If you don’t have enough free space for ODABR snapshots, postpone the patching. ODABR is a mandatory safety net. Reducing \/u01 and \/opt filesystems’s size is possible. It will require stopping everything, but as you will patch your ODA, you’ve already allocated a sufficient downtime.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction The patching of an Oracle Database Appliance needs to be secured. This is because it won’t limit to patching the databases: there is plenty of other components embedded with the patch, the goal being to keep everything updated. A possible rollback may be needed. For sure, there is no possible rollback for firmwares, BIOS […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[3998,3995,3996,3993,2567,3994,2568,4000,3081,3079,3663,1697,1698,1699,2427,2429],"type_dbi":[],"class_list":["post-44065","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-u01","tag-available-lvm-size-is-less-then-required-snapshot-size","tag-cannot-use-odabr","tag-lvreduce","tag-oda-2","tag-orabr","tag-oracle-database-appliance-2","tag-pvs","tag-x10-ha","tag-x10-s","tag-x11-ha","tag-x8-2ha","tag-x8-2m","tag-x8-2s","tag-x9-2ha","tag-x9-2s"],"acf":[],"yoast_head":"\n
Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA - dbi Blog<\/title>\n<meta name=\"description\" content=\"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \/u01 and \/opt on your Oracle Database Appliance.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA\" \/>\n<meta property=\"og:description\" content=\"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \/u01 and \/opt on your Oracle Database Appliance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-24T06:42:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-24T06:42:13+00:00\" \/>\n<meta name=\"author\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"Not enough space for using ODABR? Reduce \\\/u01 and \\\/opt size on your ODA\",\"datePublished\":\"2026-04-24T06:42:11+00:00\",\"dateModified\":\"2026-04-24T06:42:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/\"},\"wordCount\":1219,\"commentCount\":0,\"keywords\":[\"\\\/u01\",\"Available LVM size is less then required snapshot size\",\"cannot use odabr\",\"lvreduce\",\"oda\",\"orabr\",\"oracle database appliance\",\"pvs\",\"x10-ha\",\"x10-s\",\"X11-HA\",\"x8-2ha\",\"x8-2m\",\"x8-2s\",\"X9-2HA\",\"X9-2S\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/\",\"name\":\"Not enough space for using ODABR? Reduce \\\/u01 and \\\/opt size on your ODA - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-04-24T06:42:11+00:00\",\"dateModified\":\"2026-04-24T06:42:13+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"description\":\"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \\\/u01 and \\\/opt on your Oracle Database Appliance.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Not enough space for using ODABR? Reduce \\\/u01 and \\\/opt size on your ODA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\\\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/jerome-dubar\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA - dbi Blog","description":"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \/u01 and \/opt on your Oracle Database Appliance.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/","og_locale":"en_US","og_type":"article","og_title":"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA","og_description":"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \/u01 and \/opt on your Oracle Database Appliance.","og_url":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/","og_site_name":"dbi Blog","article_published_time":"2026-04-24T06:42:11+00:00","article_modified_time":"2026-04-24T06:42:13+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA","datePublished":"2026-04-24T06:42:11+00:00","dateModified":"2026-04-24T06:42:13+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/"},"wordCount":1219,"commentCount":0,"keywords":["\/u01","Available LVM size is less then required snapshot size","cannot use odabr","lvreduce","oda","orabr","oracle database appliance","pvs","x10-ha","x10-s","X11-HA","x8-2ha","x8-2m","x8-2s","X9-2HA","X9-2S"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/","name":"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-04-24T06:42:11+00:00","dateModified":"2026-04-24T06:42:13+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"description":"Cannot use ODABR if not enough free space on the Physical Volume? Reduce the size of \/u01 and \/opt on your Oracle Database Appliance.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/not-enough-space-for-using-odabr-reduce-u01-and-opt-size-on-your-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Not enough space for using ODABR? Reduce \/u01 and \/opt size on your ODA"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd","name":"J\u00e9r\u00f4me Dubar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","caption":"J\u00e9r\u00f4me Dubar"},"description":"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.","url":"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/44065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=44065"}],"version-history":[{"count":9,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/44065\/revisions"}],"predecessor-version":[{"id":44074,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/44065\/revisions\/44074"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=44065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=44065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=44065"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=44065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}