RE: dba_registry info in OEM repository
Date: Tue, 11 Oct 2016 19:10:57 -0700 (PDT)
Message-ID: <ff2a5d96-6b9f-40a7-ac44-5267b22eafc3_at_default>
I apologize to Bobby for that most excellent typo I just made! J
Pete
Pete Sharman
Database Architect, DBaaS / DBLM
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
Phone: HYPERLINK "tel:+61262924095"+61262924095 | | Mobile: +61414443449 Email: HYPERLINK "mailto:pete.sharman_at_oracle.com"pete.sharman_at_oracle.com Twitter: @SharmanPete LinkedIn: au.linkedin.com/in/petesharman Website: petewhodidnottweet.com
_____
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not, it's much harder than that!"
Bruce Pihlamae, long term Oracle DBA
_____
From: Peter Sharman
Sent: Wednesday, October 12, 2016 01:08 PM
To: Scott.Deas_at_lfg.com; Bobby Curtis <curtisbl_at_gmail.com>
Cc: rjoralist3_at_society.servebeer.com; oracle-l_at_freelists.org
Subject: RE: dba_registry info in OEM repository
I think Bobby may have meant MGMT$OH_PATCH and MGMT$OH_PATCHSET (note the OH for ORACLE_HOME instead of OS for operating system). These (and the OS equivalents Bobby mentioned) are documented in the EM SDK PL/SQL documentation which you can download via Setup -> Extensibility -> Development Kit.
There are, however, three well-known caveats (well, well-known to me anyway!) with some of the MGMT$ views:
1. The documentation for some of them seems scarce to non-existent. They are, however, actually documented in two places – the EM SDK just referred to and the HYPERLINK "http://docs.oracle.com/cd/E73210_01/EMVWS/toc.htm"Cloud Control Management Repository Views Reference.
2. Many of them are empty, so just when you think you’ve found a place where the information you want might be, you realize there is no data there.
3. Overriding point 1 is the fact that ONLY the views that are documented are covered by your license. Many others exist (Booby referred to one below) but if the view is NOT documented in the two places referred to in point 1, theoretically you aren’t licensed to use it.
Pete
Pete Sharman
Database Architect, DBaaS / DBLM
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
Phone: HYPERLINK "tel:+61262924095"+61262924095 | | Mobile: +61414443449 Email: HYPERLINK "mailto:pete.sharman_at_oracle.com"pete.sharman_at_oracle.com Twitter: @SharmanPete LinkedIn: au.linkedin.com/in/petesharman Website: petewhodidnottweet.com
_____
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not, it's much harder than that!"
Bruce Pihlamae, long term Oracle DBA
_____
From: Deas, Scott [mailto:Scott.Deas_at_lfg.com] Sent: Wednesday, October 12, 2016 02:34 AM To: Bobby Curtis <HYPERLINK "mailto:curtisbl_at_gmail.com"curtisbl_at_gmail.com> Cc: HYPERLINK "mailto:rjoralist3_at_society.servebeer.com"rjoralist3_at_society.servebeer.com; HYPERLINK "mailto:oracle-l_at_freelists.org"oracle-l_at_freelists.org Subject: RE: dba_registry info in OEM repository
Thanks Bobby,
All of the tables/views mentioned happen to be empty in our environment. We do have LCM licenses, so I’m not sure if there’s something we need to enable for the agents to send data, but we aren’t seeing anything in the tables as of now.
I don’t see any documentation online nor notes on MOS about these objects, so I’m not sure how we’d know how they’re intended to be used.
Thanks,
Scott
From: Bobby Curtis [mailto:curtisbl_at_gmail.com] Sent: Tuesday, October 11, 2016 10:34 AM To: Deas, Scott <HYPERLINK "mailto:Scott.Deas_at_lfg.com"Scott.Deas_at_lfg.com> Cc: HYPERLINK "mailto:rjoralist3_at_society.servebeer.com"rjoralist3_at_society.servebeer.com; HYPERLINK "mailto:oracle-l_at_freelists.org"oracle-l_at_freelists.org Subject: Re: dba_registry info in OEM repository
Has anyone looked at the SYSMAN.MGMT$OS_PATCH or MGMT$OS_PATCHSET views for patches. For the registry question, I think you might be able to use SYSMAN.MGMT$EM_LMS_DBA_REGISTRY view. I think that view requires Lifecycle Management pack though.
Bobby
On Oct 11, 2016, at 10:17 AM, Deas, Scott <HYPERLINK "mailto:Scott.Deas_at_lfg.com"Scott.Deas_at_lfg.com> wrote:
Rich,
Agreed. I looked through the OEM documentation and scanned the data dictionary, but I don’t see this info.
The metric extension would be useful once something goes invalid, but I’m still hopeful that this is somewhere in the repository where we could query the enterprise all at once, versus waiting for an event to trigger or checking a target at a time.
Thanks,
Scott
From: HYPERLINK "mailto:oracle-l-bounce_at_freelists.org"oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Rich J Sent: Tuesday, October 11, 2016 9:14 AM To: HYPERLINK "mailto:oracle-l_at_freelists.org"oracle-l_at_freelists.org Subject: Re: dba_registry info in OEM repository
On 2016/10/10 20:29, Deas, Scott wrote:
If we had the registry information for our entire enterprise of 200+ databases available within OEM, we'd be able to monitor this more efficiently. It might be viewable within the OEM interface once we select a target, but I was wondering if the agents send that data to the OMS so it's available in the repository.
Not any help right now, but for the future, it sounds like a relatively easy Metric Extension in EM12c would do the trick.
I just might be creating one of my own to catch DBs that haven't had their catbundle run for example...
Rich
Notice of Confidentiality: **This E-mail and any of its attachments may contain Lincoln National Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Lincoln National Corporation family of companies. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are
hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify thesender immediately and permanently delete the original and any copy of this E-mail and any printout. Thank You.**
Notice of Confidentiality: **This E-mail and any of its attachments may contain Lincoln National Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Lincoln National Corporation family of companies. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. Thank You.**
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Oct 12 2016 - 04:10:57 CEST