John,
Thank you for the follow up. I did attend their presentation and spoke with
Gary briefly. I found the presentation to be quite informative. We are going to
explore Database Fleet Maintenance further and determine which option will work
best for us.
Thanks,
Mike
On Tue, 2018-10-23 at 10:54 +0000, Norman, John A wrote:
Our company uses Fleet Maintenance for Oracle Home provisioning and Database
Patching. We plan on using it for Database Upgrades too in the next year.
Gary Henderson and Vaithianathan Soundararajan presented on our company’s use
of Fleet Maintenance yesterday at OOW. Hopefully, you were able to attend
their presentation.
The actual patching process runs roughly 6-10 minutes per database for us
(would be quicker, but patching the OJVM component requires bouncing the
database to put it in upgrade mode, and bouncing it again after patching is
complete to open it read/write).
We have well over 1,000 databases, and patch each database at least twice per
year. What used to take an entire staff of 10 DBAs is now handled by 1-2 DBAs.
Thanks,
John
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Pecoraro, Michael
Sent: Tuesday, October 23, 2018 2:16 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: [EXTERNAL] Rapid Home Provisioning vs Database Fleet Maintenance
Nationwide Information Security Warning: This is an external email. Do not
click on links or open attachments unless you trust the sender.
________________________________
I’m curious to know how many are using Rapid Home Provisioning in their
organization and how you are using it. Have you compared RHP to Database Fleet
Maintenance? Are you considering using Database Fleet Maintenance to patch and
upgrade your databases over RHP?
We have been using RHP for roughly the past year. In our environment, RHP is
used mainly to provision Oracle Homes for our databases and to create the
databases (CDBs). Our original plan was to use it for database patching as
well. The creation of Oracle Home images and working copies has worked well
overall across our various clusters. However, the performance of the working
copy creation is not good. The process runs over 90 minutes in a four node
cluster. It runs much longer in our larger clusters. The database creation
process works, but in some cases we wish we had more customization options.
The database patching (“rhpctl move database”) has been very buggy in our
environment. Given the various issues we have with RHP, we are considering a
switch to Database Fleet Maintenance.
I’m at OOW this week. If you’d like to meet up to discuss it further, send me
a message.
Thanks,
Mike
---
Michael J Pecoraro
University at Buffalo
mikejp@xxxxxxxxxxx<mailto:mikejp@xxxxxxxxxxx>