From oracle-l-bounce@freelists.org Wed Jul 7 08:41:11 2004 Return-Path: Received: from air189.startdedicated.com (root@localhost) by orafaq.com (8.11.6/8.11.6) with ESMTP id i67Dekl14964 for ; Wed, 7 Jul 2004 08:40:56 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air189.startdedicated.com (8.11.6/8.11.6) with ESMTP id i67Dea614912 for ; Wed, 7 Jul 2004 08:40:46 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 913E172CB4C; Wed, 7 Jul 2004 08:21:55 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26719-87; Wed, 7 Jul 2004 08:21:55 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id D516772CA61; Wed, 7 Jul 2004 08:21:54 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Wed, 07 Jul 2004 08:20:33 -0500 (EST) X-Original-To: oracle-l@freelists.org Delivered-To: oracle-l@freelists.org Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id DA50E72C7F4 for ; Wed, 7 Jul 2004 08:20:32 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27339-27 for ; Wed, 7 Jul 2004 08:20:32 -0500 (EST) Received: from troll.tpk.net (mail.tpk.net [216.107.198.11]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 8DD2972C295 for ; Wed, 7 Jul 2004 08:20:32 -0500 (EST) Received: from MWF600XL (host216-107-212-43.tpk.net [216.107.212.43]) by troll.tpk.net (Postfix) with SMTP id 0D135669507 for ; Wed, 7 Jul 2004 09:44:19 -0400 (EDT) From: "Mark W. Farnham" To: Subject: RE: Monitoring activities for Large Centralized Production Hybrid Database? Date: Wed, 7 Jul 2004 09:44:37 -0400 Message-ID: MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at freelists.org X-archive-position: 4546 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: mwf@rsiz.com Precedence: normal Reply-To: oracle-l@freelists.org X-list: oracle-l X-Virus-Scanned: by amavisd-new at freelists.org That would depend on the results of your business requirements study, site and regional disaster business continuation plans, logical and physical telecommunications pathway redundancy, service level agreements, and your cost per hour versus time of outage graph for loss of service. And a few other things. Seriously, the monitoring functionality required and its allowed cost horizon should fall out of the business requirements, not some generic notion of what it is nice to keep an eye on. Now, that being said here are a few things I don't think you should be without: 1) Typical "heartbeat" transactions that verify your needed point-to-point capabilities and suggest that in lieu of "locking issues" your physical plant should be delivering reasonable OLTP response versus expectations. 2) A history of disk growth graph quantized by the the size of storage it is easy to add to your disk farm without disrupting your i/o signature. (for example, don't plan to add one disk {or a few disks} that will get all the hot new pieces of everything as soon as you add it). 3) At least monthly a check with your vendors that they continue to guarantee disk farm and computer replacement/augmentation parts for a moving 6 or nine month window. 4) A history of your headroom for CPU utilization. 5) An alarm level warning versus a workshift plan for CPU utilization level (tell someone if use is unexpectedly very high, even if it is not screwing up your heartbeat transacations.) 6) Unexplained or unplanned changes in the rate of generation of redo. 7) For recurring jobs, a history of job completion times, preferably with desired, investigate, and alarm/deadline time thresholds. 8) Holy cow, this could be a really long list. Try digging up the old MOSES papers for a start. If you can't find those, get someone's old MVS glass house operations manuals. Those guys always wore belts and suspenders (aka braces, not the sock thingies.) mwf -----Original Message----- From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org]On Behalf Of VIVEK_SHARMA Sent: Wednesday, July 07, 2004 5:50 AM To: oracledba@lazydba.com; oracle-l@freelists.org Subject: Monitoring activities for Large Centralized Production Hybrid Database? Folks What monitoring activities need to be set in place for a Critical production,=20 near 24/7, Centralized (500 GB) banking application Database? Thanks Vivek ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@freelists.org put 'unsubscribe' in the subject line. -- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@freelists.org put 'unsubscribe' in the subject line. -- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------