Home Our Concept ServicesOther Products Shopping Cart Payment OptionsFAQ Privacy About Us Contact Us

Checklist and Template for

executing and documenting an

Database Health Check
Part 1: Stability Assessment

Price USD
add to shopping basket
Price USD
add to shopping basket

| Summary | Audience | Related Products | Related Services | Deliverables | Table of Contents |

Summary and Scope

Proactive checking for stability issues is important to avoid unplanned outages.

Documenting those checks provides important evidence that you are operating according best practice.

Auditors ask for documented evidence!

This checklist supports the execution of an Self Assessment regarding Database Stability to ensure that the assessed application will continue to work as required (avoiding unplanned outages) or at least, to resume operations as fast as possible. There are many - often simple - details which could prevent your database from working properly, even if you invested significant money into a clustered solution with redundant hardware and automatic failover or even Oracle Real Application Cluster (RAC).

The questions address many different topics which could impact the database.


IS- and IT Directors, Operations Managers: As they are responsible (and to some extent even liable) for professional operations of business critical systems they appreciate reasonable assessments to identify possible issues or document the good system status. Although they usually don't have the detailed Oracle experience and by far not the time to execute such assessments, they can clearly understand "what" should be checked.

Database Administrators: Often a DBA is asked to take over a database from a colleague, other department or vendor. This report helps the DBA to quickly and easy check and document the database status and request corrections or other changes before he takes over responsibility. This report allows also the DBA to check databases in his responsibility so that he can take corrective actions where required before an auditor will request those.

Company internal Auditing Department, Revenue Assurance Department, QA-Department: Use this questions when reviewing systems. Check if all questions are answered and if the assessment report contains potential issues.

Related Products

Application Health Check: Stability Assessment Similar document on application level
Database OLA (SLA) Template for an Operational Level Agreement (OLA) between DBA's and Service Level Manager. Based on this OLA with the DBA's and many other OLA's with other departments (and underpinning contracts with external providers) the Service Level Manager can establish a SLA (Service Level Agreement) with the customer (business department).

Related Services

Audit of Database Installation Execution of the checks outlined in this product "Database Health Check - Part 1: Stability Assessment" onsite at customer's location.
Capacity Management Execution of capacity analysis, capacity management and capacity planning onsite at customer's location or in our office based on information provided by the customer.






296 KB

Zip-file containing all of the following files

Within this ZIP-file you will find following files:






Base document in Acrobat-Format, Acrobat Reader required



Same content as .PDF-file, but this file is in "Rich Text Format" (RTF) which can be imported into (nearly all) text processing programs. This enables you to fill out the documents

Table of Contents

Related Documents 4

Overview - System Description 5

First Checks 6

Alert-files and Dump-Destinations 6

alert<sid>.log 6

userdump-destination 6

background-dump-destination 6

User Management 7

Invalid Objects 7

Wrong Objects in Schema of SYS or SYSTEM 7

Support 9

Monitoring, Alarming, Troubleshooting, Incident- and Problem Management 10

Monitoring and Alarming 10

Incident- and Problem Management 10

Installation 12

Oracle-BASE compliance 12

Automatic purging / Lost / Forgotten Files 12

Protection against loss of Data 13

Backup and Recovery Process 13

Additional Protections 13

Protection against Block Level Corruption 14

Restore 14

Availability 15

Configuration- and License Limitations 15


Other License Limitations 16

Capacity Reserves 16

Diskspace 16

Backup Duration 17

Archivelog Space 17

Other Availability Features 17

Application Database Objects 18

Unusual 18

Disabled Triggers 18

Disabled Constraints 18

Tables, Indexes, Data Integrity etc. 18

Bind Variables 19

Database Sessions 20

Statistics 21

Does the application create temporary tables ? 22

Oracle ® is a trademark of Oracle Corporation.

Oracle does not endorse, approve or sponsor any activities identified on this web site, nor is Oracle affiliated in any manner with this web site.
Copyright © 2005 Mercury Consulting Limited.