Today I can finally tell you the good news on my new role. December 8th was my last day at Oracle. So what was the good news? I already have a new job, as a technical architect with a small company called archTIS. I saw the job advertised on LinkedIn and applied, spent an hour and a half in a phone interview the next day, got called in to meet the CEO the day after and he offered me the job on the spot! I’ve already started in the new role, and it looks both exciting AND challenging. Couldn’t be more happy as a result.
In my last post, I walked you through the first part of installing the Oracle Database 12c STIG compliance standards sample code. The next step to using these compliance standards is to associate your Oracle Database 12c databases with these standards. You may recall there are two separate standards in the sample code, one for multitenant databases and the other for conventional architecture databases. The process of associating the databases is the same in each case. You simply have to choose the compliance standard that matches your architecture. In this walkthrough, I will show you how to associate a multitenant database with the “Oracle 12c PDB STIG” compliance standard.
The first step is to go to the “Compliance Standards” tab on the “Compliance Framework” page. To access this, follow the menu path “Enterprise” -> “Compliance” -> “Library”:
In a recent post, I announced the release of some sample code that created two new compliance standards for DISA’s Oracle Database 12c Security Technical Implementation Guide. The sample code includes details on how to install the compliance standards, but I wanted to walk you through an example of installing it with screenshots and more commentary than is in the sample code. So let’s start off with some of the assumptions you need to be aware of.
As I mentioned in the post announcing the sample code, there are some inbuilt assumptions when using this sample code:
It’s been a long time coming, but finally we can announce than Enterprise Manager Cloud Control 13c Release 2 is here! So what are the main new features? Obviously I can’t cover them all in a single blog post, but here are the ones that are highlights to me.
For our security minded customers, this is functionality that people have been waiting a long time for. Communication between the agent and OMS, the agent and the targets, and in case of target types such as Oracle databases, between the OMS and the targets are now secured with TLS1.2 protocol.
Enterprise Manager 13cR2 can now be configured on pure IPv6 or dual IPv6/IPv4 stacks, and it can also be used to monitor and manage IPv6 enabled Exadata systems and IPv6 configurations with (RAC) databases.
One of the most requested features in the compliance management area has been a compliance standard for Oracle Database 12c. As most of you would know, Oracle Database 12c has been out for quite some time, and indeed Larry Ellison has just announced at OOW2016 availability of Oracle Database 12cR2 in Oracle’s public cloud offering. However, as I discussed in another post earlier this year, creating a new STIG compliance standard is not a simple matter. In fact, we are still working on integrating the DISA Oracle Database 12c compliance standard into Enterprise Manager Cloud Control 13c.
One of the questions we see being asked reasonably frequently is how to allow read only access to someone who wants to view database performance issues, using tools such as Real Time ADDM, ASH Analytics and so on. This is generally asked for someone like an application developer, who can use this information to identify performance issues in Production and then fix the root cause in their Development environments.
Well, that’s a reasonable question to ask, and indeed if you search the internet you can find different ways of doing something like this. For EM12c, one of the best write-ups I’ve seen done on this was of course by one of my colleagues, Courtney Llamas. That write-up is available here.
While I always enjoy getting in front of customers to present on some new and really cool functionality in Enterprise Manager Cloud Control, it’s even better to be in the audience listening to actual customers doing just that! There are a couple of those presentations coming up on Thursday this week at OOW. Unfortunately I can’t be there to listen in, but if you’re interested in learning how to provide scalable and flexible patching solutions, make sure you get along to these two presentations and learn directly from these customers!
Is that enough version numbers for you?
Yes, it’s that crazy time of the year again, when the city of San Francisco turns red – it’s Oracle Open World (OOW) 2016! If you’re planning on going this year, I hope you have your hotel room booked, because they disappear very, VERY quickly!
A customer recently asked me about whether they can convert numerous cron jobs to EM’s Job System. It reminded me that a former manager of mine had posted an article on just how to do this conversion. That manager has since left Oracle, and since his posting was on his own website, I wanted to make sure the intellectual capital wasn’t lost to us if he decided to remove it. The article was written in March 2015, so the screenshots were all taken with EM12c as that was the version available at the time. Obviously, the user interface has changed in EM13c, but the basic functionality remains the same. In the post below, I’ve updated the material to EM13c, but if you want to see the original EM12c post it’s still (as of August 2016) available here.