In the Oracle probe documentation, it is said that if the checkbox "Enable Threshold On Space" is activated, two parameters will be evaluated before generating an alert for lack of space in tablespace at checkpoint "tablespace_free".
It turns out that, by enabling that checkbox, it continues to evaluate only the percentage parameter instead of evaluating percentage and space together (Gb).
DX UIM 20.4 or higher
Oracle probe versions: 5.45, 5.45T1, 5.45T2
When the user creates a profile through the admin console the key key_col_name = FREESP is not getting added inside the threshold of tablespace_free checkpoint.
This issue will occur only when the user configures with the admin console. With IM it is working fine.
This is a known issue and a fix is available to resolve this.
Attached to this case is oracle-5.45-T5-20240313.065433-4.zip
Step to deploy the fix:
- Download and import the attached build to your archive
- Deploy the probe to the oracle robot (upgrade your current oracle probe version to the attached fix)
- For the fiix to work create new profiles. For the existing profiles the fix won't work, it will only work for newly created profiles. So you can consider deleting existing profiles for the fix to fully work. After this the key_col_name = FREESP is added via Admin Console the same way it is added with IM.
For a workaround (without the fix), use Infrastructure Manager or add the key key_col_name = FREESP under the threshold section of tablespace_free checkpoint. (As highlighted below).
<thresholds>
<default>
<0>
msg_val = Profile $profile, instance $instance, tablespace $NAME has $PCT% ($FREESP) free space available (autoext.:$AUTOEXT, chunks:$CHUNKS)
key_col_value = 30
msg = tablespace_free_2
sev = information
checkName = tablespace_free
testVal = default_0
key_col_name = FREESP
default = default
value = 100
</0>
</default>
</thresholds>