Perhaps there is a "poor mans" way of doing this. The startup trigger
could fire a procedure that inserts a row into a table and then sleeps for
1 minute before doing the same again. Effectively it would create a ping
in the table, which you could then analyze / graph to display uptimes.
The next logical step would be to increase the intelligence of the
procedure. The table storing the statistic could consist of two columns -
uptime and downtime. When the startup trigger fires it creates a new row
in the table with both uptime and downtime set to sysdate. It then sleeps
for a minute before updating downtime for the most recent record (either
remember a primary key or search for max(uptime)). This would be much
easier to understand when the database was stopped / started.
Of course depending on your accuracy requirement, granularity could be
changed to every 5 minutes, 10 minutes, whatever.
Hopefully that gives some ideas though. Of course the 3rd party monitors
that Jared mentions are worth considering if the database is considered
critical. In that case the number one requirement is probably the ability
to page / SMS / email when it sees the database is down.
Regards,
Mark.
Jared.Still@ra
disys.com To: Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
Sent by: cc:
[EMAIL 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
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
"Post, Ethan" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
12/02/2002 02:33 PM
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 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 trigger would
log the times in a table. You should also check the startup time against
the last startup time periodically to ensure the trigger always fires.
Somehow a procedure/function should be able to use this information to
report the service level for the database within the last
(week/month/quarter/year).
I suppose I will get around to it eventually but if anyone else wants to
get
started on it I won't mind!
Thanks,
Ethan
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Post, Ethan
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).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
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).
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<---->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Privileged/Confidential information may be contained in this message.
If you are not the addressee indicated in this message
(or responsible for delivery of the message to such person),
you may not copy or deliver this message to anyone.
In such case, you should destroy this message and kindly notify the sender
by reply e-mail or by telephone on (61 3) 9612-6999.
Please advise immediately if you or your employer does not consent to
Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this message
that do not relate to the official business of
Transurban City Link Ltd
shall be understood as neither given nor endorsed by it.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<---->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Mark Richard
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).
