RE: POLL: Database to DBA ratio

[Burke, William F (Bill)]

Title: RE: POLL: Database to DBA ratio

In my shops we use a similar matrix to this for management and assignment.  In short, on-call rotates weekly and the "on-call" responsibility covers non business hours (eg: 7pm - 8am).  The remainder of the time the environment DB owner has responsibility.  The (A) indicates an automated process, each DBA has designated databases for all management during normal business hours.  The on-call DBA handles off-hours work.  The matrix is as wide as you have database instances.  Here's an example from an environment I worked on.  The script name column is the exact path/name for the script supporting automated functions, or, the name of the script to manually check stuff.   Instance Management Checklist   ER DAILY CHECKLIST SCRIPT NAME   �        Verify successful logon to database                                                (A)     �        Verify Listener is up                                                                         (A)     �        Verify NAMES Server is up                                                            (A)     �        Review Alert log for errors                                                              (A)     �        Review Free-Space report                                                                                  �        Review 10-or-more-extents report                                                 �        Identify Objects Unable To Throw Next Extent                           (A)      �        Verify archiving of redo logs     �        Verify archived logs being moved to staging area correctly     �        Verify staged archived logs are being moved to tape     �        Check for Invalid objects                                                                 (A)     �        Check for Changed objects                                                             (A)     �        Check for File System usage thresholds                                         (A)     �        Check for Tablespace usage thresholds                                         (A)     �        Check for Tablespace Autoextend usage thresholds                     (A)     �        Check Analyze for Corrupt Segments report                                (A)     �        Check Pricing Refresh Group Incomplete report                         (A)     �        Trim Otrace files                                                                              (A)     �        Check MLOG$ vs. SNAP$ Inconsistency report                          (A)     �        Purge old leftover rows from snapshot logs                                   (A)     �        Check for Snapshot Refresh errors (job failures)                         (A)     �        Verify successful run of nightly exports                                         (A)     �        Verify that build_customer_product ran successfully                  (A)     �        Verify that Usage & Billing ran successfully                                 (A)           FRIDAY CHECKLIST     �        Purge log and trace files (DO FOR TRACE FILES)              (A)     �        Review Row Chaining report                                                       �        Review hit ratios (OEM Performance Pack, summary data)     �        Review Actual Segment size report and resize as necessary     �        Review Table statistics report     �        Review Redo Latch statistics report     �        Review Rollback Segment storage report     �        Review Rollback Segment statistics report           MONDAY CHECKLIST     �        Verify that weekly analyze ran successfully                            (A)     �        Verify that build_contract_prod_price ran successfully        (A)           SEMI-MONTHLY CHECKLIST (15th + 30th)     �        Run bmark performace monitoring script     �        Review script in detail for potential problems     �        Provide written status and analysis of bmark output     �        Prepare scripts to tune instance after acceptance of bmark recommendations by dba group     �        Execute tuning scripts for instance           (A)=Automated - See DBA Common Scripts, - = Not Applicable       Regards, Bill Burke "The Kinder and Gentler DBA" www.OracleGuru.com International Oracle Users Group www.ioug.org Board of Directors Elect - 2003-2005 Board of Directors - 2000-2002 University Master Class Faculty 2001-2002 Oracle Development Tools User Group www.odtug.com Board of Directors 1996-2000 -----Original Message----- From: Chuck Hamilton [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 6:04 PM To: Multiple recipients of list ORACLE-L Subject: Re: POLL: Database to DBA ratio With such a large # of databases to support, how do you divide up the work? Does everyone administer all of the databases, or are databases assigned to a DBA? How do you handle on-call? ----- Original Message ----- From: Adams, Matthew (GECP, MABG, 088130) To: Multiple recipients of list ORACLE-L Sent: Wednesday, March 12, 2003 2:40 PM Subject: RE: POLL: Database to DBA ratio 350 Oracle Databases spread across US and Europe. 14 full time, 4 part time. 75% of applications are designed and built in-house. -----Original Message----- From: Deshpande, Kirti [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 12, 2003 1:59 PM To: Multiple recipients of list ORACLE-L Subject: RE: POLL: Database to DBA ratio We have over 400 databases,  90%+ are Oracle under various versions, platforms. Today have 19 DBAs. Two weeks from now there will be 17. Rightsizing to continue in the 2nd Quarter.... - Kirti -----Original Message----- Sent: Wednesday, March 12, 2003 12:09 PM To: Multiple recipients of list ORACLE-L We have 7 DBAs.  105 production databases (97 24x7), ranging from 2 GB OLTP to 800 GB data warehouses.  395 devl/alpha/beta databases ranging in size from very small (1 GB) to production-sized.  About 1/3 of the production databases have at least 1 (usually more) development effort going on at any given time. Most of our time (lives?) is spent just keeping things up and running.  The on-call guy averages between 50 to 100 pages per week (record is in the 230-range).  Tuning and testing new stuff is fairly uncommon - as we have time.                                                                                                                                             -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Deshpande, Kirti   INET: [EMAIL PROTECTED] Fat City Network Services    -- 858-538-5051 http://www.fatcity.com San Diego, California        -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from).  You may also send the HELP command for other information (like subscribing).