You are on page 1of 6

1.

Connectivity: Make sure each database is available and accessible both by logging in via
user applications, as well as running test scripts.
2. Disk Space checking for all databases, tablespaces, archive log destinations, dump
destinations, and backup destinations.
3. Maintaining proper documentation.

Daily Checks:
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 database performance, periodic basis usually in the morning 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.
Identify bad growth projections.
Clear the trace files in the udump and bdump directory as per the policy.
Weekly Checks:
Perform level 0 or cold backup as per the backup policy. Note the backup policy can be
changed as per the requirement. Don’t 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.
Monthly or Quarterly Checks:
Checks for the critical patch updates from oracle make sure that your systems are in
compliance with CPU patches.
Checkout the harmful growth rate.

Look for security policy violations:


Look in SQL*Net logs for errors, issues, Client side logs, Server side logs and Archive all
Alert Logs to history

Types of DBAs

There are DBAs who focus on logical design and DBAs who focus on physical design;
DBAs who specialize in building systems and DBAs who specialize in maintaining and
tuning systems;

Some DBAs are firefighters which are the Operations DBAs. who are great at
performance tuning, diagnosing problems, and getting databases back on-line quickly if
there is every a disaster. Application DBAs are great data modelers, PL/SQL
programmers, coders, and work with development staff to develop the database from
the code being written. Both are essential to the organization.

Operation DBA
An Operation DBA focuses on technical rather than business issues, primarily in the
system administration area. Typical tasks center on the physical installation and
performance of the database and:
Installing new versions and applying maintenance fixes supplied by the vendor.

 Setting and tuning system parameters.


 Tuning the operating system, network, and transaction processors to work with
the database.
 Ensuring appropriate storage for the database.
 Enabling the database to work with storage devices and storage management
software.
 Interfacing with any other technologies required by database applications.
 Installing third-party DBA tools.

Operation DBAs are rarely involved with actual implementation of applications. They
might get involved in application tuning when operating system parameters or complex
initialization parameters need to be altered.

Application DBA

In direct contrast to the Operation DBA is the Application DBA. The Application DBA
focuses on database design and the ongoing support and administration of databases for
a specific application or applications. The Application DBA is likely to be an expert at
writing and debugging complex SQL and understands the best ways to incorporate
database requests into application programs. The Application DBA must also be capable
of performing database change management, performance tuning, and most of the other
roles of the DBA. The difference is the focus of the Application DBA—it is on a specific
subset of applications rather than the overall database implementation and database
environment.

COre DBA --

1.oracle home installation of 9i/10g/11g or Existing Oracle home Code tree Cloning for Different
database installations

2.setup tnsnames, ldap, sqlnet.ora, listener.ora, ifile

3.create database 9i/10g/11g with parameter file

4. Parameters Recommendations for performance for 9i/10g/11g databases

5.setting up cron tab to monitor & schedule jobs in the database

6.installation of o/s watcher for monitoring

7.installation of em agent & registration of databases for monitoring


8.Deploying Standard scripts for Regualr Administration

9.Installation of 10g CRS & 11g Grid Home

10.Patchset Upgrade of CRS (10.2.x to 10.2.x) & Upgrade from 10g to 11g Grid.

11.Database Upgrade From 9i to 10g & 10g to 11g.

12.Migration of Database using Export/Import,expdp,impdp, DataPump, XTTS (transportable


Tablespace)

13.Cross Platform migration Of Database (HP,Solaris to Linux)

14.Regular Maintainance

adding datafiles to tablespaces ,resizing datafiles,

clearing files & freeing space on Server

alert log monitoring for alerts

backup verification

DR/data guard verification & monitoring archive log shipping

backup verification

creating db links

materialized views refresh,

invalids compilation

creation of users,profiles,assigning roles & revoking

creating corrupted indexes,migrating corrupted tables

enabling forced logging/ no logging

15.RAC Conversion from standalone to 2,3,4 Nodes

16.adding node, deleting node on a existing RAC database

17.conversion of multi node RAC to stand alone database

18.setting up Environment profiles

19.Issue Troubleshooting & Resolution


20.copying Database with cold backup & taking Hot Backup

21.backup Scheduling & verification

22.Cloning Database with Cold Backup & Hot Backup, RMAN

23.Utlities Usage - lsnrctl,tnsping,dbca,dbua,tkprof,sqlplus,exp,imp,expdp,impdp,rman,dbverify,opatch

24.scheduling Analyze

25.Data Guard Configuration on a Standalone Database

26. Installing DataGuard Broker

27.performing a failover/switchover

28.Patching Database for issue resolutions & applying CPU Patches

29.Enabling SOX Compliance on Database & Disabling

30.Replication of Databases shareplex

31.monitor jobs, fix broken jobs, re build jobs propagator

32.detecting & removing locks in the database & identifying long running sql's

33.security in the database

34.Restore & Recovery in the Database

35.Restoring OraInventory

36.repointing & creating sym links (soft links)

37.verify & Install O/s level Packages & Rpms

38. trust setup between servers


39. PERFORMANCE TUNING

1.generating traces & TKProf files, explain plan for performance tuning
2.generating statspack & AWR snapshots
3.session level, database level parameters to monitor performance & traces

a.Performing Lights on Activities-health Checks.

like ...
1.Database and instance status:
2.Objects close to max extents:
3.Objects that cannot get next extent:
4.Tablespaces nearing 0% free
5.identifying Chained rows tables
6.Check for locked sessions
7.Check for Invalid Objects
8.Buffer cache Hit Ratio > 90%
9.Library cache Hit Ratio
10. Dictonary cache Hit Ratio > 85%
11. redo log space reque near zero
12.Redo latch allocation /copy
13.Monitor the Growth/Size of the Database
14.Monitor the Growth/Size of the data
15.Verify that the primary database logs are being applied to the standby database

b.Installtions/setups

Oracle databse installtions,patching upgrade


Dataguard (physical stand by set up),the failover method,standby modes,log transport services.
RAc setup
ASM setup/ maintaince.

c.BACKUP AND RESTORE

stragtegy to schedule backups(hot and cold).


Planning downtime
configure Rman backup strategy
perform recovery when ever required.
exp/imp backups
database refresh,rman clonning

d.Performance tuning (briefly listed below).

Sqlquery tunning on request from developer team.


knowlege generating statpack ,Awr reports...e.t.c
LOCKS DML/DDL,Session statistics,waits,Memory tuning.

================================================================
Q1. What is difference between Oracle DBA vs Oracle Apps DBA?

Oracle DBA include following types of task.


1. Oracle Database Administration
2. Oracle Database Backup & Recovery
3. Oracle Database Performance tuning
4. Little PLSQL programming
========================

1. Disk Space checking for all databases, tablespaces, archive log destinations, dump
destinations, and backup destinations.
2. All backup successfully finished or not.
3. Backup validation (to restore at testing database).
4. Alert.log checking for any critical errors.
5. Server load monitoring.
6. Network load monitoring.
7. Security auditing.
8. Scheduled process checking.
9. Scheduling database statistics.
10. Maintaining proper documentation.