I was working to apply 19.18 patch on top 19.15 in ODA X8-2 baremetal machine to. Below is a failed pre-patch report where pre-check failed for GI due to insufficient space in /u01 filesystem.
Patch pre-check report
------------------------------------------------------------------------
Job ID: 63eed3af-324a-47e8-b655-8925b162bc95
Description: Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER, SERVER]
Status: RUNNING
Created: August 28, 2024 3:20:18 AM MST
Result: One or more pre-checks failed for [GI]
Node Name
---------------
oda01a
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.18.0.0.0.
Is patch location available Success Patch location is available.
Verify OS patch Success Verified OS patch
Validate command execution Success Validated command execution
__ILOM__
Validate ILOM server reachable Success Successfully connected with ILOM
server using public IP and USB
interconnect
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.18.0.0.0.
Is patch location available Success Patch location is available.
Checking Ilom patch Version Success Successfully verified the versions
Patch location validation Success Successfully validated location
Validate command execution Success Validated command execution
__GI__
Validate GI metadata Success Successfully validated GI metadata
Validate supported GI versions Success Successfully validated minimum version
Validate available space Failed Insufficient disk space on file
system: /u01. Expected free space:
18661MB, available space: 14828MB
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 19.18.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate ASM in online Success ASM is online
Validate kernel log level Success Successfully validated the OS log
level
Validate minimum agent version Success GI patching enabled in current
DCSAGENT version
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Success Validated clones location
Validate DB start dependencies Success DBs START dependency check passed
Validate DB stop dependencies Success DBs STOP dependency check passed
Validate space for clones Success Clones volume is already created
volume
Evaluate GI patching Failed Oracle Grid Infrastructure version
19.18.0.0 is
invalid.DCS-10802:Insufficient disk
space on file system: /u01. Expected
free space: 18661MB, available space:
14828MB
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Running
Validate command execution Scheduled
__SERVER__
Validate local patching Scheduled
Validate command execution Scheduled
I cleand up trace/listener logs under /u01/app/grid but still I was not able to meet minimum requiremnt of space.
Please follow beloe step to extend /u01 upto 20GB if there is no other oppurtunity to cleanup
Check free space in local volumegroup
vgdisplay
WARNING: Ignoring duplicate config value: global_filter
--- Volume group ---
VG Name VolGroupSys
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 11
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 7
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 446.12 GiB
PE Size 32.00 MiB
Total PE 14276
Alloc PE / Size 7178 / 224.31 GiB
Free PE / Size 7098 / 221.81 GiB
VG UUID A7Vi6v-uhBs-KihW-SeV6-iYFq-qV8t-Ka6gcI
This shows we have 221.81 GB free
/u01 has currently 40 GB allocated as shown below
Get /u01 filesystem path
df -h /u01
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolU01 59G 32G 25G 57% /u01
lvdisplay /dev/mapper/VolGroupSys-LogVolU01
WARNING: Ignoring duplicate config value: global_filter
--- Logical volume ---
LV Path /dev/VolGroupSys/LogVolU01
LV Name LogVolU01
VG Name VolGroupSys
LV UUID Yl9g84-uFia-wP3T-xg8D-uQFn-V5tA-qj3bzc
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2022-09-22 10:07:54 -0700
LV snapshot status source of
u01_snap [active]
LV Status available
# open 1
LV Size 40.00 GiB
Current LE 1280
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 252:75
Extending 20 GB
Initially it failed with below error
lvextend -L +20G /dev/mapper/VolGroupSys-LogVolU01
WARNING: Ignoring duplicate config value: global_filter
Snapshot origin volumes can be resized only while inactive: try lvchange -an.
This is because of the fact that it can not extend while there is active snapshot.
So delete snap using /opt/odabr/odabr delsnap
lvextend -L +20G /dev/mapper/VolGroupSys-LogVolU01
Size of logical volume VolGroupSys/LogVolU01 changed from 40.00 GiB (1280 extents) to 60.00 GiB (1920 extents).
Logical volume VolGroupSys/LogVolU01 successfully resized.
Resize filesystem online
resize2fs /dev/mapper/VolGroupSys-LogVolU01
resize2fs 1.42.9 (28-Dec-2013)
Filesystem at /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01; on-line resizing required
old_desc_blocks = 5, new_desc_blocks = 8
The filesystem on /dev/mapper/VolGroupSys-LogVolU01 is now 15728640 blocks long.
[root@oda01a ~]# df -h /u01
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolU01 59G 21G 37G 36% /u01
Now execute pre-check again and it should be successful.
Happy Learning....
Thanks
