Thursday May 31, 2012

Troubleshooting EBS Discovery Issues - Part 2


Part 1 of “Troubleshooting EBS Discovery Issues”, which was posted on May 17th, focused on the diagnostics associated with the initial discovery of an EBS instances (e.g., Forms servers, APPL_TOPs, databases, etc.).

Part 2 focuses on verifying parameters of the Change Management features, also called "Pack Diagnostics, specifically for Customization Manager, Patch Manager, Setup Manager, Automated Cloning, and User Monitoring.  As stated in the first post, there can be numerous reasons that Discovery fails - credentials, file-level permissions, patch levels - just to name a few.

The Discovery Wizard can be accessed from the EBS homepage.  From the home page, click "Pack Diagnostics"


Click "Create" to define the diagnostic process


Provide the required inputs; Name, Module (i.e., Customization Manager, Patch Manager, Setup Manager, Automated Cloning, and User Monitoring), Show Details (typically "All"), and Category (typically check both Generic and User Specific).  Add the appropriate targets.


Once the diagnostic process has completed, view the results.  Click on "Succeeded" or "Failed" in the Status column.


Expand the entire tree and click on each "Succeeded/Failed" status to see the results of each test within that task.


Sample output verifying o/s user name and required patches



Additional sample output showing a failed test


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.

Thursday May 17, 2012

Troubleshooting EBS Discovery Issues - Part 1

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:


  1. General diagnostics, which is accessed via "Discovery Wizard", verifies parameters for the discovery of the EBS instance.  Customers will want to run this particular

  2. 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.

About

This blog is dedicated to providing content to customers, partners, and Oracle employees on the Application Management Suites for Enterprise Manager.

In particular, this blog concentrates on the Application Management Suites for:
•    Oracle E-Business Suite
•    Siebel
•    PeopleSoft
•    JD Edwards EnterpriseOne
•    Fusion Applications

The owner of this blog is Ken Baxter.  Ken is a Product Strategy Manager in the Enterprise Manager group, and is responsible for all of the Application Management Suites.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today