Re: Non-technical query about patching databases

I'll tag on to Rob's comment with this: It also depends on the maturity and organization of the company you work for. My current company's change control is immature. Everything is important, and many things are fire drills. For example: Refreshing a Demo database for the Sales team becomes "We must have it by Friday." We have a team of 3 FTEs, 1 Contractor and 2 auxiliary DBAs and we're covered up with stuff - and very little of it is patching at the moment.

So far, this week I've worked all last weekend and a total of 32 hours before today.

Chris

On Wed, Jan 17, 2018 at 5:51 AM, rob oraclewizard.com <rob_at_oraclewizard.com> wrote:

> I've managed 28 Oracle Databases by myself for a number of years. I never
> felt like I was over worked and kept all the databases at the current patch
> level. Now that said, remember a Development database is Production for
> Developers and a Test database is Production for Testers. My normal
> patching cycle for this customer was on weekends when I could get down time
> on the databases.
>
> You can do this with two good DBAs. But the other side of the coin is the
> dept of your DBA group. One of my customers has four DBA's for 40
> databases. This provides enough dept to also have DBAs rotating on call.
>
> Robert P. Lockard
>
> “A letter of reprimand is better than no mail at all. Nobody ever made
> history or changed the world by only worrying about his or her career.”
>
> (cell) +1.571.276.4790 <(571)%20276-4790>
>
> (blog) http://www.oraclewizard.com
>
> _at_YourNavionPilot
>
> On January 17, 2018 at 6:29 AM Steve Bradshaw <sjb1970_at_gmail.com> wrote:
>
> Hi,
>
> I hope nobody minds me asking a non-technical question.
>
> If you had approximately 50 databases, mix of live, test, development, no
> dataguard or RAC, what sort of staffing level would you expect to have in
> order to keep them patched to the latest PSU?
>
> Thanks, Steve
>
>

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