Re: d/b health check
- From: "Daniel W. Fink" <Daniel.Fink@xxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 25 Aug 2004 07:07:12 -0600
There's more to database health than what you can find in statspack
(though it is part of the overall toolkit). Health also includes
security, recoverability, supportability, etc.
Is the database and related files being properly backed up? Does the
backup set include *everything* you need to recover the database and
supporting jobs (cron, standard reports, etc)? Has the backup been
tested recently (way too many war stories about unusable backups)?
What about security? Do users have access to the database as schema
owners or dba-level accounts? If they have access, is it proper and
reasonable?
Do you have a proper QA/Staging environment? Nothing kills database
health faster than the release from hell.
Consider that a poorly performing database is usually more acceptable
than a down database.
Regards,
Daniel Fink
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
