How to Check for Invalid Internal Jobs in the Repository Database in Enterprise Manager 12c and 13c
Last updated on MAY 09, 2017
Applies to:Enterprise Manager for Oracle Database - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
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 12c and 13c.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms