RE: SLA Trigger/Procedure

2002-12-04 Thread Mark Leith
by everyone involved. Deshpande, Kirti kirti.deshpande@ve To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] rizon.comcc: Sent by: Subject: RE: SLA Trigger/Procedure

Re: SLA Trigger/Procedure

2002-12-04 Thread Yechiel Adar
: SLA Trigger/Procedure om 03/12/2002 12:13 Please respond to ORACLE-L Ethan, That records the startup times, but does not record the time that the database

RE: SLA Trigger/Procedure

2002-12-04 Thread Jared . Still
:RE: SLA Trigger/Procedure I agree what is needed is something very generic that could monitor the uptime of pretty much any process. After giving this more thought and always liking to keep things simple here is the direction I might eventually head. The logic below would result in a log file

RE: SLA Trigger/Procedure

2002-12-03 Thread Mark Leith
: SLA Trigger/Procedure om 03/12/2002 12:13 Please respond to ORACLE-L Ethan, That records the startup times, but does not record the time that the database was unavailable. What's needed

RE: SLA Trigger/Procedure

2002-12-03 Thread Post, Ethan
For reasons too long to go in to, go buy a tool is not a good option for my purposes. Besides, why buy what I can build? These are exactly the sort of challenges that make my job worth coming to. Thanks, Ethan -Original Message- Sent: Tuesday, December 03, 2002 4:14 AM To: Multiple

RE: SLA Trigger/Procedure

2002-12-03 Thread Jamadagni, Rajendra
Title: RE: SLA Trigger/Procedure Go buy a tool? Here is an idea instead ... Write a small Perl (pick your favorite language here) script that looks at /etc/oratab followed by a check to see if each of the instances listed in /etc/oratab is up on the side where it is checking. It then log

RE: SLA Trigger/Procedure

2002-12-03 Thread Rachel Carmichael
. Jared.Still@ra disys.comTo: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED] Subject: Re: SLA Trigger/Procedure

RE: SLA Trigger/Procedure

2002-12-03 Thread Mark Leith
Title: RE: SLA Trigger/Procedure Dang, I just new that would cause a stir! ;P Mark Running away now Leith -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jamadagni, RajendraSent: 03 December 2002 14:32To: Multiple recipients of list ORACLE

RE: SLA Trigger/Procedure

2002-12-03 Thread Jared . Still
[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/03/2002 06:32 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: SLA Trigger/Procedure Go buy a tool? Here is an idea instead ... Write a small Perl

RE: SLA Trigger/Procedure

2002-12-03 Thread Deshpande, Kirti
. Jared.Still@ra disys.comTo: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED] Subject: Re: SLA Trigger/Procedure om

RE: SLA Trigger/Procedure

2002-12-03 Thread Fink, Dan
PROTECTED] Subject: Re: SLA Trigger/Procedure om 03/12/2002 12:13 Please respond to ORACLE-L Ethan, That records the startup times, but does not record the time

RE: SLA Trigger/Procedure

2002-12-03 Thread Ron Thomas
] Sent by: cc: [EMAIL PROTECTED] Subject: RE: SLA Trigger/Procedure

Re: SLA Trigger/Procedure

2002-12-03 Thread Stephane Faroult
[EMAIL PROTECTED] wrote: Ethan, That records the startup times, but does not record the time that the database was unavailable. What's needed is a 3rd party monitor that is not dependent on the database being up to record metrics. Jared Jared, I am far from having given much

RE: SLA Trigger/Procedure

2002-12-03 Thread Jamadagni, Rajendra
Title: RE: SLA Trigger/Procedure you still have to *buy* the tool right? Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD

RE: SLA Trigger/Procedure

2002-12-03 Thread DENNIS WILLIAMS
Mark - Well, speaking for myself, I appreciate your openness in pointing out the major issues one would have to deal with if they were going to write their own. Dennis Williams DBA, 40%OCP Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Tuesday, December 03, 2002 10:34

Re: SLA Trigger/Procedure

2002-12-03 Thread Igor Neyman
Stephan, There will be no relevant info in the alert.log about the time when database was unavailable, if database was not shut down properly (let say, the plug was pulled). Or, may be I misunderstood you? Igor Neyman, OCP DBA [EMAIL PROTECTED] - Original Message - To: Multiple

RE: SLA Trigger/Procedure

2002-12-03 Thread Mark Richard
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] rizon.comcc: Sent by: Subject: RE: SLA Trigger/Procedure

RE: SLA Trigger/Procedure

2002-12-03 Thread Post, Ethan
I agree what is needed is something very generic that could monitor the uptime of pretty much any process. After giving this more thought and always liking to keep things simple here is the direction I might eventually head. The logic below would result in a log file that shows all unscheduled

RE: SLA Trigger/Procedure

2002-12-03 Thread Deshpande, Kirti
recipients of list ORACLE-L [EMAIL PROTECTED] rizon.comcc: Sent by: Subject: RE: SLA Trigger/Procedure

SLA Trigger/Procedure

2002-12-02 Thread Post, Ethan
Just a thought here for a script I think would be handy but I haven't had time to write. It is would be a simple procedure you could call to get the service level for a particular database. I suppose you would have to have some sort of way of defining normal outage windows. Basically a startup

Re: SLA Trigger/Procedure

2002-12-02 Thread Jared . Still
Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:SLA Trigger/Procedure Just a thought here for a script I think would be handy but I haven't had time to write. It is would be a simple procedure you could

Re: SLA Trigger/Procedure

2002-12-02 Thread Mark Richard
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED] Subject: Re: SLA Trigger/Procedure