Daily procedures
- Verify all instances are up: run daily reports or via "Oracle Enterprise Manager's 'probe' event"
- Look for any new alert log entries: Check ORA-errors in $ORACLE_BASE/
/bdump/alert_ .log - Verify success of database backup
- Verify success of database archiving to tape
- Verify enough resource for acceptable performance:
a. Verify free space in tablespaces (free.sql, space.sql)
b. Verify rollback segment: should be ONLINE
c. Identify bad growth projections:
I. analyze5pct.sql
II. nr_extents.sql
III. Query current table sizing
IV. Query current index sizing
V. Query growth trends
d. Identify space-bound objects (spacebound.sql)
e. Review contention for CPU, RAM, network and disk resources. - Copy archived logs to standby database and roll forward: use automated scripts, verify daily
Nightly procedures
- Collect volumetric data: mk_volfact.sql, analyze_comp.sql, pop_vol.sql
Weekly procedures
- Look for objects that break rules
a. Check NEXT_EXTENT: nextext.sql, check existing extents: existext.sql
b. Check missing PK: no_pk.sql, check disabled PK: disPK.sql, check PK indexes uniqueness: nonuPK.sql
c. All indexes should use INDEXES tablespace: mkrebuild_idx.sql
d. Check schema objects consistency between test and production: datatype.sql, obj_coord.sql, Quest Schema Manager. - Look for security policy violations
- Look in SQL*Net logs for errors, issues
a. Check client side logs
b. Check server side logs - Archive all alert logs to history
Montly procedures
- Look for harmful growth rates
- Review tuning opportunities: cache hit ratio, latch contention etc.
- Look for I/O contention
- Review fragmentation: row chaining etc.
- Project performance into the future
- Perform tuning and maintenance