As you may know, one of the many areas of responsibility I have as a product manager in the Enterprise Manager product management team is BI Publisher. BI Publisher is the tool of choice for reporting in Enterprise Manager. If it’s not a tool you’re familiar with, then you are missing out on a lot of the power of the Enterprise Manager repository to provide you the information you need to extend Enterprise Manager beyond the capabilities it currently has. You can read more about it on my BI Publisher page.
Of course, to reach the full capacity of the reporting you can extend Enterprise Manager with, you need to understand the Enterprise Manager repository, and that’s what this post will introduce you to. First, however, you need to understand a little more about the BI Publisher security model.
This blog post was prompted by a comment on my website by Chris Peterson, where he asked why the 11g STIG checklist doesn’t work against Oracle Database 12c. This required a more comprehensive answer than I could give in a simple comment, so that’s what this blog post is all about. Let’s start off with a bit of an introduction for those of you that are asking, “What the heck is a STIG anyway?”
After what seems like eons since we first started on it, I’m excited to announce a new book I co-authored is finally out. The book is called “Building Database Clouds in Oracle 12c” and is available on Amazon. Of course, it really isn’t that long ago that we started writing the book, but there’s been a lot happening between then and now!
The book was co-authored with Tariq Farooq and Sridhar Avantsa. Tariq asked me to write the material on Enterprise Manager (chapters 4 – 8 in the book), which was done over a number of releases of EM12c. We deliberately left the material on the versions it was written on, because people are still on a variety of different releases, so you can see how it applies in the version you’re using.
From a content perspective, this is what the book covers:
Per Oracle documentation, you’re able to upgrade from EM12c to EM13c, including the OMR, (Oracle Management Repository) to DB12c and the OMS, (Oracle Management Service) to EM13c, but leave the agent software at a version of 126.96.36.199 or highe
*Customer names obfuscated to protect the innocent (and the guilty!)
This post covers a particular customer’s recovery scenario. They had reverted their config.xml to a previous version due to a failed attempt to integrate LDAP into WLS myrealm, and ever since, they have been unable to start BI Publisher via the emctl command. Although they can start it from the WLS Admin Console, the ’emctl status oms -details’ shows BI Publisher Server is Down, and they can’t even connect to it via the https://em12c.example.com:9702/xmlpserver/. They then attempted to run the emcli setup_bipublisher to re-register it with EM but get:
This posting is to try to clarify what is supported when using Enterprise Manager Cloud Control 13c (EM13c) and Amazon Web Services (AWS). The question came from some of our sales consultants who were finding confusing information about what is actually supported when using EM13c and AWS, so I have asked our Support folks to write a support note to provide the definitive answer on this. While that is being written, I thought I would post a quick blog that could be used to help clarify matters.
So let’s look at what the different scenarios are:
Enterprise Manager does a LOT. Sometimes it may do too much. Customers on forums, on support or via email and social media may come to us asking how to address something they view as not working right and the truth is, we could simply answer their question, but they aren’t using the right tool to accomplish what they’re attempting.
This last week I presented at Great Lakes Oracle Conference, (GLOC16) and the discussion on monitoring of non-Oracle databases came up while we were on the topic of management packs, how to monitor usage and what ones were required to monitor non-Oracle databases.
Yesterday I wrote a post on the ORAchk / EXAchk plug-in in Enterprise Manager Cloud Control 13c, and I promised I would write another post that would cover some of the more frequently asked questions we’ve been receiving on the plug-in. That’s what this post in, so the rest of the post will be in a Q&A sort of format.
Question: What are the benefits of EXAchk integration with the Enterprise Manager compliance framework i.e. what can we do with this that we could not in EM12c?
Answer: In EM 12c, we ask customers to setup EXAchk in the target themselves, we just bring the results to EM and show the results on the EXAchk target Home page. In 13c these are our main features:
In Enterprise Manager Cloud Control 12c release 188.8.131.52, we released the Oracle Engineered System Healthchecks plug-in which processed the XML output from the EXAchk tool, included as part of Oracle Enterprise Manager system monitoring. The EXAchk tool provides functionality for system administrators to automate the assessment of Engineered Systems for known configuration problems and best practices.
Over the years since that first release, we increased the scope and functionality of the tool, to the stage where it now has its own documention guide, Enterprise Manager ORAchk Healthchecks Plug-in User’s Guide. Notice there’s no mention of the word “EXAchk” in that title. That’s because the plug-in has been expanded so far it now includes two health check tools: