Hello,
We have an issue with the OEM corrective actions associated to a tablespace running out of free space.
What we see, is that everything is handled correctly, but the action never completes because it checks if there is enough space in the underlying filesystem and, if at that moment, it considers there is not enough it will do nothing.
This is wrong approach IMHO. Our filesystems will expand automatically (soft provisioning).. which is what we have to do manually afterwards.
Looks like logic from the days where filesystems did not expand automatically (like the 80s 90s? )
Is there any way at the OEM level to force the corrective action to simply expand the tablespace (small file, bigfile) ignoring what the current free space in the filesystem is ?
Best!