0% found this document useful (0 votes)
75 views2 pages

What Shall I Tell in Daily Health Checks?

The document provides guidance on daily health checks for an Oracle database administrator. It recommends checking the database and applications, monitoring the alert log for errors, ensuring sufficient system resources and backups, verifying archive log space and copying, and monitoring SQL statements and the network. It also discusses database sizing, users, and tablespaces for different environments. Methods are provided to check the number of databases on a server from the command line or oratab file. The backup strategy involves both Data Pump and RMAN backups on a daily, weekly, and monthly schedule. Backups and logs are retained for a minimum of two weeks. Export/Import or Data Pump is preferred for table or schema backups since they are on the logical level. Examples

Uploaded by

RajeshRaj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
75 views2 pages

What Shall I Tell in Daily Health Checks?

The document provides guidance on daily health checks for an Oracle database administrator. It recommends checking the database and applications, monitoring the alert log for errors, ensuring sufficient system resources and backups, verifying archive log space and copying, and monitoring SQL statements and the network. It also discusses database sizing, users, and tablespaces for different environments. Methods are provided to check the number of databases on a server from the command line or oratab file. The backup strategy involves both Data Pump and RMAN backups on a daily, weekly, and monthly schedule. Backups and logs are retained for a minimum of two weeks. Export/Import or Data Pump is preferred for table or schema backups since they are on the logical level. Examples

Uploaded by

RajeshRaj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1. what shall I tell in Daily health checks?

Login to the database and do some basic checks.


Login to any application that uses an Oracle database. (Have a defined set of checks to run).
Check the alert log file, this should be checked to identify errors or unusual events.
Monitor system resources: Checks should be performed to ensure system performance
Ensure backups are successful.
Archive logs: If archive logging is enabled (a must for any production database) check that
there is enough space to write logs for the next 3 days, this takes into account weekends that
are normally supported via telephone support. Also ensure that the archive logs are being
copied to a secure location. Only keep logs that have been created since the last cold backup of
the database.
Monitor the network: For any client/server systems the DBA should be aware of any network
changes and the network load.
Monitor SQL statements performance: SQL tuning can produce amazing performance
improvements. Also, monitoring the SQL code can help locate bottlenecks. (I have seen
improvements of over 300% achieved by just adding a hint to use a more suitable index or
adding an index to eradicate a full table scan.)

2. Database size, No. of users and no. of TBS for PROD, UAT and Dev envir onment?
Please let me know if I need to check any thing on this point.

All prd,dev,UAT are in sync in Our environment.
DB Size 100 GB
Separate tablespaces for indexex and general Data.
Our application uses single user only.

3. How to determine how many DB's are
present in your server?

On the server You can execute
ps -ef | grep pmon | grep -v grep

Or Check the list of contents on /etc/oratab file.
4. Backup strategy like which backup methodology you are following, what
backups ur taking i. e. , schema tables or what?. .


We have two types of backups
1) Data pump (some persons do not treat it as a backup).
2) RMAN backup
3) Every day we take datapump backup.
4) On week days we take incremental backup.
5) On weekends we take full backup.

5. Retention period of Backup's, archive log files, log files
Minimum two weeks we will maintain them.


6. Which backup is preferred while taking backup for schema/table Hot backup or
RMAN backup and why?
Export /Import or datapump because table or schema are at logical level not at physical level.

7. What error messages did u notice in Alert and Trace log files (give 3(2 easy
and 1 tough) examples) for both. Also let me know what actions did u take for
resolving the issues.

You might also like