logo
Another error spotted:
Get dynamic property error, Computation of a critical dynamic property failed. Retries Completed.

How to solve?

Other of the error from OEM12C. This version is simple to repair (in this case). Let’s fight….

But firstly one word before we start. In beginning of this month we got an seriously failure. This is an database for developers, and is still works without any problems in alert-log, so agent is repaired 2 weeks later, without haste…


001. There are “broken stats” displayed near agent / database name.

001 - Target information - Get dynamic property error

001 – Target information – Get dynamic property error

When we click on info icon (Target Information), we see something like that:

Target not Configured – Get dynamic property error, Computation of a critical dynamic property failed. Retries Completed.
In Error Since ………
Availability (%) Not Applicable

Ups – we have problem. Today is 2014-10-17, Error is from 2014-10-02.


002. Let’s check agent on this OS?

/home/oracle $emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 12.1.0.3.0
OMS Version : 12.1.0.3.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app/oracle/product/agent12c/agent_inst
Agent Binaries : /u01/app/oracle/product/agent12c/core/12.1.0.3.0
Agent Process ID : 28718
Parent Process ID : 20365
Agent URL : https://xxxxxxxxxxxxxx:3872/emd/main/
Repository URL : https://oem12c:4900/empbs/upload
Started at : 2014-08-29 15:02:15
Started by user : oracle
Last Reload : (none)
Last successful upload : 2014-10-17 19:35:31
Last attempted upload : 2014-10-17 19:35:31
Total Megabytes of XML files uploaded so far : 367.08
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 51.13%
Collection Status : Collections enabled
Heartbeat Status : Ok
Last attempted heartbeat to OMS : 2014-10-17 19:40:04
Last successful heartbeat to OMS : 2014-10-17 19:40:04
Next scheduled heartbeat to OMS : 2014-10-17 19:41:04

---------------------------------------------------------------
Agent is Running and Ready

Agent looks healthy. Let’s back to oem12c.


003. Check Metric Collecion Errors

Go to dropdown menu.

Oracle Database -> Control -> Metric Collection Errors.

003 - Metric Collection Error

003 – Metric Collection Error


004. List of Metric Collection Errors. Why i got so many?

003 - List of Metric Collection Errors

003 – List of Metric Collection Errors

There are near 20 different metrics on error state.
All of them are triggered on same date, same hour, few seconds one after another.
Last column is named as message “oracle.sysman.emSDK.agent…”
Let’s click on one of them.


005. Failed to connect: Error in Metric.

005 - Metric Error - Failed to connect

005 – Metric Error – Failed to connect

 In Incident Manager > Event Details we can see:
Metric Group – Messages per persistent queue per subscriber
Target: xxxx (Database Instance)
Event reported: xxxx #  first occurence
Message – Failed to connect: java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed.
Last Comment – …
Internal Event Name – aq_msgs_per_persistent_queue_per_subscriber

Why? Propably when error occured disc space has been depleted (100% occupied disk space).
Someone repair it and database has been usable again.
But agent go crazy…


006. How to repair this case?

This is ridiculous but in this case we need only to… restart agents in this host:

emctl stop agent
emctl start agent

007. We restarted agent. Few minutes later Metric errors dissapears

007 - Metric errors slowly dissapears

007 – Metric errors slowly dissapears

 Wait few minutes and list of errors spotted will shrink.


008. Errors removed

Near 5-10 minutes after restart of agent all errors are removed.

008 - All errors dissapears

008 – All errors dissapears


CONCLUSION

This is an example of one of the error in metric.
The simplest one…