You can use Root Cause Analysis (RCA) to filter a set of events to determine the cause of a higher level system, service, or application problem. RCA can help you to eliminate apparent performance problems that may otherwise appear to be root causes but which are only side effects or symptoms of the actual root cause of the problem, allowing you to more quickly identify problem areas. You can view the RCA results on the home page or topology page of any service that is currently down. The topology page allows you to see a graphical representation of the service, system and component dependencies with the target(s) highlighted that RCA has implicated as causing the service failure.
By default, Root Cause Analysis considers the availability of key components to determine whether or not they are causes of service failure. You can specify additional conditions, or component tests, for Root Cause Analysis to consider. If the key component is unavailable, or if any of your component tests conditions are not met, then this component will be considered a cause of the service failure.
Use the Edit Component Tests page of the Root Cause Analysis tool to set the threshold for the metric you identified on the Component Tests page.
The page displays the selected Comparison Operator and allows you to choose the Critical Severity Threshold if one is available, or you can specify an Alternate Threshold to use instead. Click OK to return to the Component Test page where your selections are added to the component test for that metric.
Related Topics
About Root Cause Analysis Processing
Getting the Most From Root Cause Analysis
Enterprise Manager Information Roadmap
Copyright © 1996, 2005, Oracle. All rights reserved.