Wednesday, May 9, 2012



Automatic RAC & DB Provisioning and Deployment Using OEM 11g (Part 1)



I recently came across the task of 2 nodes RAC deployment on RHEL/OEL 5. The version to be used for deployments are as follows


OS - RHEL5
Oracle Grid Infrastructure - 11.2.0.2
Oracle RAC Binaries - 11.2.0.2


One way was to do the installation and configuration manually, but I decided to test Automatic provisioning and deployment feature of OEM 11g. The idea here was to automate the task so that we don't have to sit around and stare at screen, Fire & Forget. I, in fact, tried my luck with earlier version of OEM but failed miserably. The story was not same this time around. 


so lets start with it. I am going to break this task in sub-tasks and put them in separate posts.


1. Configure software library for OEM (this software library will be used to hold your images for GI and RAC homes)


2. Create the images of the existing GI and RAC home binaries (this will be promoted as gold images for the successful deployment)


3. Deploy the images on the newly acquired hosts. However, agents must be installed and configured beforehand with OEM.



Part 1 - Configuring the Software Library


If you are using provisioning and deployment procedures or patching thru OEM, you must first prepare software library. If the software library is not configured you will see a warning when try to perform any of the above operations.


To create Software Library, click on Deployments tab after you login to OEM




On the Deployments tab, click on the Provisioning tab. 


This will open Provisioning page as follows.




Click on Administration Tab.


On the Administration page, scroll down to the bottom of the page where you will see "Software Library Configuration" section.
Click on ADD Button


Enter the path of location where you want to place your Software Library on OEM Host. 

Note - You can also use NFS and remote drives here but that will be not be shown when you browse file system using OEM. Since I was running low on space on my OEM Host, I used NFS mounted drive for this exercise.





Once you click OK, Provisioning Archive (PAR) files will be uploaded to Software Library. This PAR files contains the many out of the box procedures for deployments. 




Once the PAR files are uploaded successfully your configuration of Software Library completes.

You can also check the Accessibility of Software Library using Check Accessibility button.


That's it. You successfully created the Software Library for OEM.


Coming soon

Part 2-  Create the images of the existing GI and RAC home binaries 
Part 3-  Deploy the images on the newly acquired hosts

No comments:

Post a Comment