RE: Process and tools for managing Critical Patch Updates

From: <Joel.Patterson_at_crowley.com>
Date: Mon, 30 Apr 2012 15:39:27 -0400
Message-ID: <C95D75DD2E01DD4D81124D104D317ACA1B9570D7B1_at_JAXMSG01.crowley.com>

I understand that there is a way using Enterprise Manager.

Joel Patterson
Database Administrator
904 727-2546

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Kroll, Stanley R. Sent: Monday, April 30, 2012 10:08 AM
To: oracle-l_at_freelists.org
Subject: Process and tools for managing Critical Patch Updates

Our environment:
95% RHEL5
5% Windows
Approximately 120 Oracle EE 11.2.0.2 databases. 3 DBAs
We're looking for a method to help automate the application of the quarterly CPUs. We've looked into the Database Lifecycle Management Pack to help provide automation for the process but that is very costly. We can manually apply the CPU to each database but as the number of databases increase and our head count does not, that approach does not scale well. We've thought about somehow building our own automation but that can become a maintenance issue over time.

I would be interested in hearing about the tools and processes that others use to manage the application of CPUs across many database installations.

Thanks,
Stan

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Mon Apr 30 2012 - 14:39:27 CDT

This message: [ Message body ]
Next message: saurabh manroy: "Re: log buffer size and log file syncs"
Previous message: Rodd Holman: "Exchange Partition Error"
In reply to: Kroll, Stanley R.: "Process and tools for managing Critical Patch Updates"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message