Another case of "Pending" status for a database target instance in OEM GC 12c


Days after, I experienced another similar case of “Pending” status for a database instance in OEM GC 12c. After I followed the steps with which I solved the same problem earlier, (The steps are available at Troubleshooting the “Pending” status for a database target in OEM GC 12c .) the problem still can not be solved.

Again, I turned to Oracle Support Article “Troubleshooting The ‘Pending’ status for a Database Instance Target in Enterprise Manager 12c Cloud Control (Doc ID 1418873.1)” and tried to find solution.

Step 1: Check the suspended metrics via getmetric command

$ ./emctl config agent listtargets | grep oracle_emd
[db-host:1830, oracle_emd]
$
$ ./emctl getmetric agent db-host:1830,oracle_emd,z#Tasks_in_Suspension
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
TaskName,SuspendedUntil,Points,Reason

If anything shows in above output, it means that the metrics shown have become suspended. The typical suspension message is listed below.

TaskName SuspendedUntil Points
oracle_database:ora10g:Response 292278994-08-17 08:12:55 2147483647
oracle_database:ora11g:Response 292278994-08-17 08:12:55 2147483647

Result: metrics was not suspended.

Step 2: Check the current Severity Status on the Agent

Checking the target status will show the status that the agent considers the database target to be in (eg. clear/critical, and will also show timestamps associated with these).

$ ./emctl status agent target db_name,oarcle_database | grep Response
Response      State                   n/a             CLEAR           Tue Jul 30 09:40:38 PDT 2013
Response      Status                  n/a             CLEAR           Tue Jul 30 09:40:38 PDT 2013

The ‘clear’ status shows that the database should be considered as ‘up’, the timestamp of the ‘clear’ is also shown. This example means that the database has been considered as ‘up’ by the agent since 30th July 9:40. A down database will show a ‘CRITICAL’ status for example, if the target is down.

Result: database target instance is showing “UP”.

Step 3: perform a clearstate of agnt

The severities as reported on the agent, should be the same as shown in the console. If the console is showing a ‘pending’, but the severities on the agent show a ‘clear’ or a ‘critical’, then perform a clearstate of the agent would help.

$ ./emctl clearstate agent
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
EMD clearstate completed successfully

This command will re-send the severity states of the targets to the OMS.

Result: OMS console shows “UP” for problematic target database instance.

PROBLEM IS SOLVED!


This entry was posted in My Reference, Oracle Case Study, Oracle Point and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>