1. Make sure that all database instances are available.

Log into each instance and run daily

2. Checking CRS status
bash-3.00$ ./crs_stat -t
3. Checking Volumes Informations in each instances.
bash-3.00$ df h
4. Verify success of database backup:
a. RMAN backup/Data Pump Backup/Cold backup
5. Check the Archive Log file locations in each instance
6. Check the Archive Log file location volume sizes in each instance
7. Check Alert Log files (Any ORA_600, oRA_07445 etc..) in each instance
8. Check the Statspack / AWR Report Peak hour reports
9. Check the ASM INSTANCE status in each instance
10. Check disk groups space and limitation
11. Always use EM and ADDM reports for performance health checks and analysis
12. verify the DR sync (if applicable):
13. If DR site is available :
a. Check to determine if latest archive logs have been applied to the database b
y looking at the alert
log file for the standby(DR) database.
14. Review contention for CPU, memory, network or disk resources:
a. Work with system administrators to develop methods to review contention for t
hese resources.
15. Maintain Complete Database Details (Data Files locations, Control file locat
ions, Redo Log file Locations etc...)
a. If any changes in production database or DR-Site database update manuals.
16. Check OCR and VD backup locations. (If possible take manually OCR and VD bac
kup)
17. Check CRS logs in each instance
18. Check Listener Logs in each instance
19. If you are using RMAN backup, Use both the instances while taking RMAN backu
p (Multiple Channel allocations in Instances)
20. Weekly restore the RAC backup in Single Instance Database (If RAC setup is n
ot available)