How to Fix 12C OEM that is Missing Metrics for a Database

Introduction (12c OEM)

On some systems, there have been reports of certain database metrics not showing in OEM. The guide below gives some pointers on how to diagnose this issue.

Step-By-Step – Check to See if DB metrics are Being Collected.

  1. Log onto OEM
  2. From 12c OEM home page navigate to your database home page.
    • The easiest way to do this is to type your target name into the search box in the top right-hand corner and select the correct target
  3. From the database home page select Database -> Monitoring -> All Metrics
  4. In the all metrics search box, search for *tablespace* or *recovery*
  5. Select the relevant metric.
    • The selected metric should say no data if it is not being collected. See screenshot below

Step-By-Step – Check to See if DB metrics are Scheduled to be Collected.

  1. Log onto the server where the OEM local database OEM agent is running
  2. cd $AGENT_HOME/agent_inst/bin
  3. ./emctl status agent scheduler |grep -i database
    • For a rac database grep for rac_database in the above command
  4. Make sure that all of the times reported in the above command are recent. If any metrics have not been scheduled recently, then this could indicate a problem.
  5. Depending on what was searched for, the output from the above command will look similar to the following
    • This data below is for a rac database and is not a complete list.
2019-04-25 15:18:47.884 : rac_database:MYDB001:observer_11g
2019-04-25 15:22:46.450 : rac_database:MYDB001:latest_db_hdm_findings_coll_item
2019-04-25 15:37:46.447 : rac_database:MYDB001:Temporary File Status
2019-04-25 15:37:46.447 : rac_database:MYDB001:problemTbspTemp_10i_Loc
2019-04-25 15:37:46.447 : rac_database:MYDB001:problemTbsp_10i_Dct
2019-04-25 21:37:46.406 : rac_database:MYDB001:audit_failed_logins_historical
2019-04-26 01:37:46.404 : rac_database:MYDB001:db_instance_caging
2019-04-26 01:37:46.404 : rac_database:MYDB001:ha_dg_target_summary
2019-04-26 01:37:46.404 : rac_database:MYDB001:invalid_objects_rollup
2019-04-26 01:37:46.404 : rac_database:MYDB001:mgmt_database_listener_config
2019-04-26 01:37:46.404 : rac_database:MYDB001:problemSegTbsp
2019-04-26 01:37:46.404 : rac_database:MYDB001:tbspAllocation

Step-By-Step – Check to See What DB Metrics are Being Collected.

  1. Log onto the server where the OEM local database OEM agent is running
  2. cd $AGENT_HOME/agent_inst/bin
  3. ./emctl getmetric agent MYDB001,rac_database,tbspAllocation
    • In the above command the parameters after the keyword agent must be separated by commas
    • The first parameter is the database name
    • The second parameter is the component displayed in the schedule command above. In this case rac_database
    • The third parameter is the metric being collected which can be found in the schedule command above. In this case tbsAllocation
  4. The command should return full data on the metric being collected. In this case tablespace names, their allocated space and used space should be shown.
  5. The following is an example where a metric is broken.
    • It can be seen that only the column headers are being shown. No data is returned.//
./emctl getmetric agent MYDB001,rac_database,tbspAllocation 
Oracle Enterprise Manager Cloud Control 12c Release 5  
Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.

If data is not being displayed for the getmetric command, it may be necessary to patch the agent with the DB Plugin Patch 23043751

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License