EM 13c, 12c: How to Check for Invalid Repository Jobs (Internal to the EM Framework) (Doc ID 2008674.1)
How to Check for invalid repository jobs in the Enterprise Manager repository database
In Enterprise Manager, each target that has been discovered will be shown along with its availability status. (eg. up, down, etc) Some targets have their availability status calculated by the agent (for example, the agent will run a 'Response' metric to determine the target's availability status). However, some targets are classed as 'composite' targets and will derive their status based on the availability of their related components. The status for composite targets, are calculated in the Enterprise Manager repository by means of an internal repository dbms job. For example, the status of the 'database system' target depends on the availability of its target members. If for example, the database which belongs to the database system is showing at status 'pending', then the database system will also show as pending. The Cluster database target is another example of a target which has its status calculated in the repository.
This means that if there is a problem with the internal repository jobs, it could lead to incorrect status issues for the repository based targets (eg, cluster database, database system, group, EM service,Oracle Weblogic Domain). This article can be helpful for database system targets in pending status, cluster targets in pending status, cluster database targets in pending status in Enterprise Manager 13c and 12c.
How to check for problems with the internal repository jobs using the Console
What to do if there are problems with this specific job
What to do if this doesn't help, or if there are problems with more than one job