Troubleshooting EBS Discovery Issues - Part 1
By Kenneth E. on May 17, 2012
For many customers, the first step is often the hardest. I'm referring to the process of discovering EBS instances in Enterprise Manager. There can be different reasons that Discovery fails - credentials, file-level permissions, patch levels - just to name a few.
To address that issue, the EBS team has provided a set of diagnostic tools, starting with EM11g. These tools are called Discovery Diagnostics. There are two sets of Discovery Diagnostics:
- General diagnostics, which is accessed via "Discovery Wizard", verifies parameters for the discovery of the EBS instance. Customers will want to run this particular
- Pack-level diagnostics, which is accessed via "Pack Diagnostics", verifies parameters for Customization Manger, Patch Manager, Setup Manager, Automated Cloning, and User Monitoring. A discussion of pack-level diagnostics is found in a related post "Troubleshooting EBS Discovery Issues - Part 2".
The Discovery Wizard can be accessed from the EBS homepage.
Check the instance, and click "Prevalidate" (Note that you can execute this before or after an unsuccessful discovery).
Provide credentials (I typically use the EBS "APPS" userid and password).
View results. Expand the entire tree, and click on the individual test result (succeeded/failed)
Below is a sample output
Another sample output showing a file-level permissions mismatch
Complete descriptions of, as well as recommended corrective actions for, all of the diagnostic tests that are run in EM 12c is found in this spreadsheet. Additional information can be found in the Application Management Pack User Guide.