From oracle-l-bounce@freelists.org Sun Aug 7 10:11:52 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j77FBqos014993 for ; Sun, 7 Aug 2005 10:11:52 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j77FBnIP014984 for ; Sun, 7 Aug 2005 10:11:49 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 8A5431DCD47; Sun, 7 Aug 2005 10:11:47 -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 19403-06; Sun, 7 Aug 2005 10:11:47 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 0AB781DCCFA; Sun, 7 Aug 2005 10:11:47 -0500 (EST) Message-Id: Date: Sun, 07 Aug 2005 11:09:40 -0400 From: "Jeffrey Beckstrom" To: , , , , Subject: monitor 9i database alert log with OEM Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_AA891352.7A1B0102" X-archive-position: 23514 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: JBECKSTROM@gcrta.org Precedence: normal Reply-To: JBECKSTROM@gcrta.org X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE, SUSPICIOUS_RECIPS autolearn=no version=2.63 --=_AA891352.7A1B0102 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Can't a 9i database alert log be monitored by OEM 9i. In OEM 9i event tests for the Alert event it states: Examine ALERT log for additional information. Note: This event does not automatically clear since there is no automatic way of determining when the problem has been resolved. Hence, you need to manually clear the event once the problem is fixed. Note: This event is valid only for releases of the Intelligent Agent prior to 9i. So 9i alert logs can't be monitored?????? Jeffrey Beckstrom Database Administrator Greater Cleveland Regional Transit Authority 1240 W. 6th Street Cleveland, Ohio 44113 --=_AA891352.7A1B0102 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Description: HTML

Can't a 9i database alert log be monitored by OEM 9i.

In OEM 9i event tests for the Alert event it states:

Examine ALERT log for additional information. Note: This event does not
automatically clear since there is no automatic way of determining when the
problem has been resolved. Hence, you need to manually clear the event once the
problem is fixed.
Note: This event is valid only for releases of the Intelligent Agent prior to 9i.

So 9i alert logs can't be monitored??????

Jeffrey Beckstrom
Database Administrator
Greater Cleveland Regional Transit Authority
1240 W. 6th Street
Cleveland, Ohio 44113

--=_AA891352.7A1B0102-- -- http://www.freelists.org/webpage/oracle-l