Thursday, August 21, 2008

Patch Deployment via Grid Control

A large DBA team of a big corporate, used to doing everything manually for 100s of databases, were very impressed this week when I showed them how EM10g Grid Control can assist them in patch deployment.

This requires the Provisioning Pack, which is a licensable pack for Grid Control.

The patch deployment procedure in Grid Control is quite mature - it allows the DBA to search for patches for any version of any Oracle software from Metalink, download the patch to a staging area on the Grid Control management server, and then apply the patch using a supplied deployment procedure.

The patch can be scheduled to be applied at any time using the Grid Control scheduler, it automatically starts a blackout for the database (so no alerts are generated), shuts it down, applies the patch, and then starts the database again.

The DBAs felt this would save them a lot of manual steps for patches that have to be applied to 100s of databases. For starters, think how much time it would take to ftp / scp the patch to 100s of servers. In the case of Grid Control, the patch is downloaded once and stored once, on the central EM Management server in the patch staging area.

2 comments:

Hariprasanna Srinivasan said...

You would require to license EM Provisioning Pack (among the flavors For Database, For AS or Standalone) to use the Patching features.
http://www.oracle.com/technology/products/oem/mgmt_solutions/provisioning.html

Porus Homi Havewala (પોરસ હોમી હવેવાલા) said...

Thanks Hari. I have made the correction. Actually even the Configuration management pack mentions the critical patch facility. I will verify with Oracle internally as to which pack is required. Maybe both.

Disclaimer

Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive