To put the concept into perspective, lets start with a story.
A certain Mr. Green (DBA Manager) is responsible for dozens (maybe more) servers, which host many databases. Now, for a growing organization, there’s a need to provision database servers for upcoming projects. Most likely these projects will go through a Development Lifecycle, i.e. Development, Pre-Prod, and eventually Production. Mr. Green’s DBA’s are busy people preoccupied with internal projects. Much to his dismay, previous server build cycles were inconsistent.
He wishes there were a way to streamline it. A way to standardize software, and database provisioning.
Database Provisioning, specifically Provisioning Profiles offer a robust and more importantly, a repeatable approach to Mr. Green’s problem. Not only would he be able to standardize his deployments, configurations from a Pre-Prod environment can easily be replicated to Production.
Okay, maybe I tend to over-simplify things. Oracle Documentation provides good examples on how to configure a Database Profile, however I’d like to explore the concept further and discuss The three types of profiles template options.
Straight from Docs:
“Provisioning Profile is an entity which contains software bits and configuration. When a provisioning profile is created from an existing installation, it provides the flexibility to clone either Grid Infrastructure (with software or configuration) and Oracle Database (with software or configuration). You can create database templates using provisioning profiles. A designer or administrator can create a database provisioning profile as a one-time activity; which can be used by operators for mass deployment. Using provisioning profile enables standardization in deployments and reduces need for rescheduling deployments by avoiding errors while configuring deployment procedures.“
To set some expectations, in the post I will create profiles for
- GI Home
- RDBMS Home
- Database Template
1. Find your way to the Database Provisioning link.
4. Back on the “Database Provisioning” home page.
5. Let’s create a Database Profile now! It’s important to mention what this profile actually contains:
- RDBMS Software Image
- Database Template
6. In case, one doesn’t want to create their own profiles, and download them from a different source (OTN), there’s a neat feature to do that. On the “Database Provisioning” home page, click on “Download Profile…”. This actually takes you to the “Self Update” page, but as you can see, there aren’t any new profiles available for download. I would imagine, in the situation where the Oracle Database plugin is updated to the latest 184.108.40.206.0 one which supports 12c Databases, the profiles would be automatically imported. That’s only a theory at this point!
There’s potential here, no doubt about that. You’ve probably noticed, that I don’t talk about licensing during this exercise. There is a management pack you would need to purchase for the Database – unless I am mistaken, its the Lifecycle Management Pack. In any case, if you were Mr. Green, the benefits of this feature would be quite apparent, and well worth the cost.
I hope you enjoyed reading, as much as I did composing this blog. I think, next time, I will likely explore further on Deployment Procedures.
Next in Series: Using Profiles