| Monthly DB availability [message #669262] |
Tue, 10 April 2018 14:35  |
Frank Naude
Messages: 4581
Registered: April 1998
|
Senior Member |
|
|
Has anyone here developed a monthly SLA report for an Oracle environment that includes database availability? If so, how did you do it? For example, are you polling the databases every couple of minutes to see if they are up and store the result in a central repository? Any suggestions of how to approach this, or tools that can do it, will be highly appreciated.
|
|
|
|
|
|
| Re: Monthly DB availability [message #669266 is a reply to message #669263] |
Wed, 11 April 2018 01:10  |
Frank Naude
Messages: 4581
Registered: April 1998
|
Senior Member |
|
|
Thank you Mahesh.
I assume most of these tools do periodic polling to check if the DBs are up. You can stop and start a database within the polling interval that will never be reported.
Instance startup times can be queried (v$instance.startup_time and even dba_hist_database_instance.startup_time), but shutdown times can be elusive (only controlled shutdowns are reported in the alert.log). A BEFORE SHUTDOWN system trigger is also not going to help much.
So, the best solution would probably be a combination of polling with startup time correction.
|
|
|
|
|
|
| Re: Monthly DB availability [message #669365 is a reply to message #669273] |
Tue, 17 April 2018 09:43 |
Roachcoach
Messages: 1576
Registered: May 2010
Location: UK
|
Senior Member |
|
|
We use Enterprise manager, it has a heap of out of the box stuff. Even splits out planned and unplanned downtime/agent issues:
Example:
Current Status Up
Up Since 16-Apr-2018 21:47:25
Availability (%) 100
Target Down Time (minutes) 0
Blackout Time (minutes) 0
Notification Blackout for Maintenance Time (minutes) 60
Agent Down Time (minutes) 0
System Error Time (minutes) 0
Status Pending Time (minutes) 0
Remote Host Unreachable Time (minutes) 0
Availability (%) = Up time/(Up time + Target Down time + Agent Down time) |
|
|
|
| Re: Monthly DB availability [message #669366 is a reply to message #669365] |
Tue, 17 April 2018 10:55 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Yes, Cloud Control is brilliant for this sort of thing. But..... Licensing.
To get notifications, you need to licence the DB servers for Enterprise Edition plus Diagnostics Pack. This is infuriating. To get around it, you have to write a load of PL/SQL. Advanced Queueing is your friend (or enemy, more likely).
I do not know if the availability and SLA reports are available licence free. If not, you would have to write your own code to generate them by querying the OEM repository.
|
|
|
|
| Re: Monthly DB availability [message #669404 is a reply to message #669366] |
Sun, 22 April 2018 02:37 |
Frank Naude
Messages: 4581
Registered: April 1998
|
Senior Member |
|
|
The OEM views are also licensed (see Oracle Enterprise Manager Cloud Control Online Documentation Library, Release 13.1):
Enterprise Manager Licensing Information User Manual:The following repository views are part of the Diagnostics Pack for Oracle Database:
...
"MGMT$AVAILABILITY_CURRENT
MGMT$AVAILABILITY_HISTORY
Quote:Any and all methods of accessing Oracle Diagnostics Pack functionality, whether through Enterprise Manager Console, desktop widgets, command-line APIs, or direct access to the underlying data, require an Oracle Diagnostics Pack license.
Interesting enough, DBA_HIST_DATABASE_INSTANCE (unlike most DBA_HIST* views) is exempted from Diagnostics Pack Licenses.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
