Scribd
Upload
279 views2 pages

DBA Daily, Weekly, Monthly Tasks

The document outlines the daily, weekly, and monthly tasks of a database administrator (DBA). Daily tasks include verifying the database, instances, and listener are running; checking scheduled jobs and backups; monitoring space usage, performance, and synchronization between primary and standby databases. Weekly tasks incorporate backups, statistics collection, scheduled changes, and reviewing logs. Monthly activities encompass backup verification, patch updates, tuning, and disaster recovery testing.

Uploaded by

Praveen
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
279 views2 pages

DBA Daily, Weekly, Monthly Tasks

The document outlines the daily, weekly, and monthly tasks of a database administrator (DBA). Daily tasks include verifying the database, instances, and listener are running; checking scheduled jobs and backups; monitoring space usage, performance, and synchronization between primary and standby databases. Weekly tasks incorporate backups, statistics collection, scheduled changes, and reviewing logs. Monthly activities encompass backup verification, patch updates, tuning, and disaster recovery testing.

Uploaded by

Praveen
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 Duties of DBA

There are a set of tasks that a Database Administrator should be doing on


Daily/Weekly/Monthly basis.

1.1 Daily Tasks

Verify all Database, Instances, Listener are up, every 1 hour.


Verify the status of daily scheduled jobs/daily backups in the morning very
first hour.
Verify the success of archive log backups, based on the backup interval.
Check the space usage of the archive log file system for both primary and
standby DB.
Check the space usage and verify all the tablespace usage is below critical
level once in a day.
Verify Rollback segments.
Backup the control file to trace so that every day we have an outline of the
files and their locations for each database.
Check the database performance, on a periodic basis usually in the morning,
especially the very first hour after the night shift schedule backup has been
completed.
Check the sync between the primary database and standby database, every
20 min.
Make a habit to check out for new errors in the [Link] on an hourly basis.
Check the system performance, periodic basis.
Ensure that the archive redo log files are compressed and have been deleted.
Only files for current and previous day should be present.
Check for the invalid objects. Ensure that no objects exist in the database
with the status 'INVALID'.
Ensure that there are no DBMS_JOBS with the status of failed or broken. Also
last refresh times of all running jobs should be current.
Check out the audit files for any suspicious activities.
Truncate the [Link] file in the $ORACLE_HOME/network/log location if the
listener log has increased to a size > than 500 MB. Ensure the space is
released, otherwise 'reload' listener.
All tablespaces should be less than 95% full - run the coalesce command on
all tablespaces to reduce fragmentation. Ensure that space in the TEMP
tablespace is released and is 100% free at the beginning of the day.
Identify bad growth projections.
Clear the trace files in the udump and bdump directory as per the policy.
Verify all the monitoring agent, including OEM agent and third party
monitoring agents.

1.2 Weekly Tasks

Perform level 0 or cold backup as per the backup policy. Note the backup
policy can be changed as per the requirement. Dont forget to check out the
space on disk or tape before performing level 0 or cold backup.
Perform Export backups of important tables.
Check the database statistics collection. On some databases this needs to be
done every day depending upon the requirement.
Approve or plan any scheduled changes for the week.
Verify the schedule jobs and clear the output directory. You can also automate
it.
Look for the object that break rule.
Look for security policy violation.
Archive the alert logs (if possible) to reference the similar kind of error in
future.

1.3 Monthly and/or Quarterly Tasks

Verify the accuracy of backups by creating test databases.


Checks for the critical patch updates from oracle make sure that your
systems are in compliance with CPU patches.
Checkout the harmful growth rate.
Review Fragmentation.
Look for I/O Contention.
Perform Tuning and Database Maintenance.
Verify the accuracy of the DR mechanism by performing a database switch
over test. This can be done once in six months based on the business
requirements.

You might also like