TEMP tablespace usage for PDB databases on Oracle 19c are not collected when monitoring using a CDB (4374273)

After monitoring an Oracle 19c server via the CDB. The temp tablespace usage on PDBs is not displayed on Oracle dashboards.
CDB level temp tablespace usage is collected normally.

WORKAROUND

There is no workaround for gathering this metric.

An alternative is to fire an alarm based on the errors in the Oracle alert log.

• The Alarm Template for this host needs to have "DBO - Alert Log Message" enabled
  • This can be configured in Alarm Management | Alarm Templates
• OS collections need to be enabled
  • Open Administration | Agents | Agent Status and select the affected agent
  • Click on Edit Properties
  • Confirm "Enable OS collections" is activated
• DB and OS connection is validated
  • This can be configured in the Databases dashboard > [select agent] > Settings > Administration > Connection Details
  • Click on "Test connection"
• The collection "Alert Log" needs to be enabled
  • This can be configured in the Databases dashboard > [select agent] > Settings > Administration > Collections
• Confirm Alert Log Filtering is setup to match the expected pattern for the alert log message like: ORCLPDB1(3):ORA-1652: unable to extend temp segment by 128 in tablespace TEMP_PDB_TEST [ORCLPDB1]
  • This can be configured in the Databases dashboard > [select agent] > Settings > Administration > Alert Log Filtering
  • Click on "Manage Alert Log Groups"
  • Select from the Match list group from the left column: "Default Match List" is OK
  • Locate and select the filter for "Unable to extend" and click "Edit"
  • Change the Expression to .*ORA-16.*unable to extend.* (i.e. add .* to include a wildcard at the start of the Regular Expression)
    • On some systems this might be .*ORA-016.*unable to extend.* 
  • Optional. Change the "Severity" to Fatal if this is intended to be a Fatal alarm
  • Click "Set" and then "Save"
  • Change the "Individual alarms minimum severity" to "Critical" if the "Unable to extend" alarm was left as "Critical"

STATUS

This issue has been logged as FOG-7556. No product change is planned for this issue.