I’m currently taking an online class from MongoDB University to learn how to be a DBA for MongoDB. My company doesn’t have any plans for MongoDB at this time. But I find that such a class can help me learn more about the product and maybe I’ll find that this product is a good fit for some future database requirements. For those interested in the class, here is a link. I highly recommend it and the best part is the cost!
A colleague of mine asked recently if we had any best practices for BI Publisher, the latest and greatest reporting tool we use within Enterprise Manager (the old tool, Information Publisher, is of course also still supported but this post is relevant to BI Publisher). As you would well know if you’ve been following my posts or heard me presenting at conferences, best practices is a term I hate, so rather than using that term let’s discuss some tips and techniques that might be relevant to you when using BI Publisher.
Tip #1: Allocate Extra Memory
The Problem – Missing Target Details
I was evaluating an Information Publisher report containing data about host targets. The report is based on the sysman.mgmt$os_hw_summary view that contains all sorts of information about your hosts. It is an excellent data source for Information Publisher reports. Unless the data is missing.
One of my hosts didn’t appear in that view, even though the host’s console page appeared healthy. Then I looked at the details. Instead of looking like this:
One of the areas I’ve been exploring recently is the setup and use of the Middleware Diagnostics Advisor, more commonly known as MDA. MDA is an advisor in EM12c that analyzes the entire stack and provides diagnostic findings by identifying root causes for any problems it discovers. It correlates and analyzes the input and offers advice on how to resolve the problem. For example, it can help you identify that slow SQL statements or a JDBC connection pool is causing a performance bottleneck.
I’m in the middle of testing for my company’s Oracle 12c production upgrades coming in September. Thankfully, I have a lot of good testbeds to fine-tune the upgrade process before proceeding to production. So far, things have been pretty smooth, even much better than my 126.96.36.199 to 188.8.131.52 upgrades a year ago. I thought I’d outline a few things I’ve dealt with during our testing in case this helps someone else down the road.
Just came across this article from Martin Berger “Oracle Enterprise Manager 12cR5 – Let’s connect to the Oracle Cloud”, you might want to take a look at his blog http://www.martinberger.com/
Keep up the good work Martin!
Many of us now have Oracle RAC installed in virtual environments on our laptops and workstations. This blog post shows how I did just that on my MacBook Pro. Recently, I was re-installing a new RAC testbed on my laptop when I ran into a few issues that took me awhile to sort out. After I had everything up and running, I figured the proper course of action would be to take a good backup of my work.