Database Reference
In-Depth Information
GUID Target Diagnostics
For our next scenario, we are going to utilize the GUID for our EM12rep (the OMS repository for the EM12c) and
gather EM environment data:
./repvfy dump -tns <oms_sid> execution
-guid EFD92E6468B02696B602A650E085B5A9 -pwd <pwd>
> ./rep_guid.lst
By running the GUID-level command you get a one-stop-shop kind of diagnostic report about your EM Jobs
Service health. (GUID is your target GUID and dumps out information on all the jobs, from all the targets.)
The report starts out very similarly to the job-level report, listing repository and EM information. However, you
will notice a distinct difference as you get to target info, especially if your EM environment is large.
If there are any background jobs submitted by the EM Jobs Service that are experiencing issues, they are clearly
reported in their own section, as shown in Figure
11-43
.
Figure 11-43.
Trace data about an error in the job execution
My only complaint at this time is that the BP1 version of the EM12c, when the EMDIAG is run against it at a full
environment level, experiences an error at the Job Analysis Summary step. You can see that error in Figure
11-44
.
Figure 11-44.
Single error from the OMS diagnostic-level EMDIAG
Therefore, if you are still using a BP1 version and need to pull this level of diagnostic data, I hope that you have
your issue narrowed down to a single job or target as the focus of the report, subsequently avoiding this error. Release
2 has corrected the problem.
