Unable to see correct target when using custom oracle checkpoint

Document ID : KB000046603
Last Modified Date : 13/02/2019
Show Technical Document Details
Issue:
When creating a custom checkpoint - we do not see the correct target when we create a PRD or view metrics within USM.

 

 

 

 

 

Environment:
Oracle probe: 4.91 and above

Unified Infrastructure Manager 8.4 and above

Cause:
The custom checkpoint will not fill in the QOS key to set the correct target by default.
Resolution:
  1. Open the oracle.cfg and navigate to the custom checkpoint.

<custom_checkpoint_query>
<qos_lists>

<0>
qos_name = tablespace_free_perc
qos_desc = Percent free space
qos_unit = percent
qos_abbr = %
qos_max = 100
qos_value = AVPCT
qos_key =
</0>
</qos_lists>

</custom_checkpoint_query>

2. In the example above you see the qos_key for the custom checkpoint be sent to null - change this to $NAME. This will fill in the QOS target with the name of the instance of the database.

 

 

 
Additional Information:

Oracle Probe Release Notes