We can see that the status of listener says – Metric evaluation error start – Compute dynamic property takes too long
We will use the EMDIAG to further identify the issue
The advantage of this is that this will always show the true error. First you need to install EMDIA Kit. Refer this EMDIAG kit install
To dump out the target information run below command. output is purged for better redability
[oracle@oel6oem bin]$ cd $ORACLE_HOME/emdiag/bin
[oracle@oel6oem bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/emdiag/bin
[oracle@oel6oem bin]$ ./repvfy dump target -name LISTENER_ggsource.localdomain
Please enter the SYSMAN password:
SQL*Plus: Release 12.1.0.2.0 Production on Sun Apr 12 14:53:40 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
SQL> Connected.
Session altered.
Session altered.
[----- REPVFY Version details -----------------------------------------------]
………………..
………………
……………..
analyzeAgent
----. done...
analyzeTarget
8002. Broken targets: 1
8999. Targets with response metric errors: 1
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
[oracle@oel6oem bin]$
Go to log directory inside emdiag and Check the file with name like “target_%”
[oracle@oel6oem log]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/emdiag/log
[oracle@oel6oem log]$ ls -ltr
total 68
-rw-r-----. 1 oracle oracle 1094 Apr 12 14:28 deinstall.log
-rw-r-----. 1 oracle oracle 321 Apr 12 14:28 install.log
-rw-r-----. 1 oracle oracle 90 Apr 12 14:28 pkg.log
-rw-r-----. 1 oracle oracle 35 Apr 12 14:28 body1.log
-rw-r-----. 1 oracle oracle 35 Apr 12 14:28 body2.log
-rw-r-----. 1 oracle oracle 35 Apr 12 14:28 body3.log
-rw-r-----. 1 oracle oracle 363 Apr 12 14:28 views.log
-rw-r-----. 1 oracle oracle 43 Apr 12 14:28 upgrade2.log
-rw-r-----. 1 oracle oracle 2412 Apr 12 14:28 verify.log
-rw-r-----. 1 oracle oracle 987 Apr 12 14:28 analyze.log
-rw-r-----. 1 oracle oracle 26921 Apr 12 14:53 target_2020_04_12_145336.log
Open this file and go to section “Current_errors”. Our logfile shows this error – “Compute dynamic property takes too long”
[----- Current errors -------------------------------------------------------]
COLL_NAME METRIC_GUID COLLECTION_TIMESTAMP METRIC_ERROR_TYPE
---------------------------------------------------------------- -------------------------------- -------------------- -----------------
METRIC_ERROR_MESSAGE
--------------------------------------------------------------------------------------------------------------------------------------
Response A4E50F1781639DF372CC594439AA57EF 12-APR-2020 11:56:04 0
Compute dynamic property takes too long
1 row selected.
Check the “target status” section, and check whether the target shows status ‘3’ = promoted, or status 2 = promoting (ie. not yet promoted). Check whether the target has been marked as broken. In our case it is showing broken with reason “128 Compute dynamic property takes too long”
[----- Target status --------------------------------------------------------]
MANAGED PROMOTED DYNAM BROKEN_REASON BROKEN_STR
-------------------- -------------------- ----- ------------- ---------------------------------------------------------------------------------------------------
2-Managed 3-Promoted 1-Yes 128 Compute dynamic property takes too long
1 row selected.
Determine whether the Response metric is scheduled
To determine whether the response metric is still scheduled by the agent, run the command. Here we can see that a response is not scheduled for listener because our target is broken.
[oracle@ggsource log]$ $AGENT_HOME/bin/emctl status agent scheduler | grep Response
2020-04-12 15:06:29.615 : oracle_database:germany:Response
2020-04-12 15:06:29.619 : oracle_database:gclone1:Response
If I run the same query in other database server I can see the difference
[oracle@ggtarget Downloads]$ $AGENT_HOME/bin/emctl status agent scheduler | grep Response
2020-04-12 15:09:12.217 : oracle_database:germany1:Response
2020-04-12 15:09:12.332 : oracle_database:london:Response
2020-04-12 15:10:45.263 : oracle_listener:LISTENER_ggtarget.localdomain:Response
Check whether the Response metric can be evaluated successfully
[oracle@ggsource log]$ $AGENT_HOME/bin/emctl getmetric agent LISTENER_ggsource.localdomain,oracle_listener,Response
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
EMD getmetric error: the oracle_listener target "LISTENER_ggsource.localdomain" does not exist
Our output above says that LISTENER_ggsource.localdomain” does not exist. Run the following command to force the agent to run the Response metric immediately
[oracle@ggsource bin]$ ./emctl control agent runCollection LISTENER_ggsource.localdomain:oracle_listener Response
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD runCollection error:no target collection
We see that the error returned is “EMD runCollection error:Response:no target collection”. Check whether the agent knows of the listener target. This shows that agent is aware of listner target
[oracle@ggsource bin]$ ./emctl config agent listtargets
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
[ggsource.localdomain, host]
[ggsource.localdomain:3872, oracle_emd]
[agent12c1_3_ggsource.localdomain, oracle_home]
[oel6oem.localdomain:3872_proxy, oracle_emd_proxy]
[OraDB12Home1_1_ggsource.localdomain, oracle_home]
[ggtarget.localdomain:3872_proxy, oracle_emd_proxy]
[gclone1, oracle_database]
[germany, oracle_database]
[LISTENER_ggsource.localdomain, oracle_listener]
Now we will Recompute the dynamic properties of the listener. If a listener target has been marked as ‘broken’ (this will be indicated in the EMDIAG target dump, then the following can be used to recompute the dynamic properties.
[oracle@ggsource bin]$ pwd
/u01/app/oracle/agent12c/agent_inst/bin
[oracle@ggsource bin]$ ./emctl reload agent dynamicproperties -upload_timeout 120 LISTENER_ggsource.localdomain:oracle_listener
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD recompute dynprops completed successfully
After the dynamic properties are reloaded, then repeat the ‘runcollection’ command to force the metric to be evaluated. This time our command completed successfully
[oracle@ggsource bin]$ ./emctl control agent runCollection LISTENER_ggsource.localdomain:oracle_listener Response
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD runCollection completed successfully
We can see that listener status in OEM is now green
DBATracker 