What a Oracle DBA can be?

This is the prime most where I visualized what a DBA is!

"DBA is a Database Administrator who logs onto the multi-user operating system as internal or system with the appropriate password is recognized by the operating system as the rightful owner of resources on the Hard disk drive. This person then becomes the Oracle DBA". --- IVAN BAYROSS

And the second question heave me is what a DBA can be!

For this I did not get right answer when I premeditated to take this line of work, but latter with perceptive of Oracle’s Workgroup I could able to learn that DBA’s are not only do backup, recover & tune the database but they design the database and more deeper I go I learned the depths of being a DBA. 10 months of expertise of mine and certification from Oracle made me to know the depths of being what a DBA holds.This is the first question always comes when we take up a new vocation – what I can, if I took up this line of work?So i put my solutions in this web log with the various works a DBA can handle.

Truly the job of DBA encompasses many roles. We will look at the roles which I learn in recent times.

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; specialty DBAs and general-purpose DBAs.

System DBA:

A system 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 DBMS software and can include the followingInstalling new DBMS versions and applying maintenance fixes supplied by the DBMS vendorSetting and tuning system parametersTuning the operating system, network, and transaction processors to work with the DBMSEnsuring appropriate storage for the DBMSEnabling the DBMS to work with storage devices and storage management softwareInterfacing with any other technologies required by database applicationsInstalling third-party DBA toolsSystem DBAs are rarely involved with actual implementation of databases and applications. They might get involved in application tuning when operating system parameters or complex DBMS parameters need to be altered.
Indeed, the job of system DBA usually exists only if the organization does not have an official
system administration or systems programming department.

Database Architect:

Some organizations create a separate position, database architect, for design and implementation of new databases. The database architect is involved in new design and development work only; he is not involved in maintenance, administration, or tuning of established databases and applications. The database architect designs new databases for new or existing applications.

The rationale for creating a separate position is that the skills required for designing new databases are different from the skills required to keep an existing database implementation up and running. A database architect is more likely than a general-purpose DBA to have data administration and modeling expertise.

Typical tasks performed by the database architect include:

Creating a logical data model (if no DA or data modeler position exists)Translating logical data models into physical database designsImplementing efficient databases, including specifying physical characteristics, designing efficient indexes, and mapping database objects to physical storage devicesAnalyzing data access and modification requirements to ensure efficient SQL and optimal database designCreating backup and recovery strategies for new databasesMost organizations do not staff a separate database architect position, instead requiring DBAs to work on both new and established database projects.

Database Analyst:

Another common staff position is the database analyst. There is really no set definition for this position. Sometimes junior DBAs are referred to as database analysts. Sometimes a database analyst performs a role similar to that of the database architect. Sometimes the data administrator is referred to as the database analyst or perhaps as the data analyst. And sometimes a database analyst is just another term used by some companies instead of database administratorData Modeler: A data modeler is usually responsible for a subset of the DA’s responsibilities.

Data modeling tasks include the following:

Collecting data requirements for development projectsAnalyzing the data requirementsDesigning project-based conceptual and logical data modelsCreating and updating a corporate data modelEnsuring that the DBAs have a sound understanding of the data models

Application DBA:

In direct contrast to the system 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 DBMS implementation and database environment

Task-oriented DBA

Larger organizations sometimes create very specialized DBAs that focus on a specific DBA task. However, task-oriented DBAs are quite rare outside of very large IT shops. One example of a task-oriented DBA is a backup-and-recovery DBA who devotes his entire day to ensuring the recoverability of the organization’s databases.Most organizations cannot afford this level of specialization, but when possible, task-oriented DBAs can ensure that very knowledgeable specialists tackle very important DBA tasks.

Performance Analyst:

Performance analysts are a specific type of task-oriented DBA. The performance analyst, more common than other task-oriented DBAs, focuses solely on the performance of database applications.

A performance analyst must understand the details and nuances of SQL coding for performance and be able to design databases for performance. A performance analyst will have very detailed technical knowledge of the DBMS so that he can make appropriate changes to DBMS and system parameters when required.

The performance analyst is usually the most skilled, senior member of the DBA staff, a role that he has grown into due to his experience and the respect he has gained in past tuning endeavors.

Data Warehouse Administrator:

Organizations that implement data warehouses for performing in-depth data analysis often staff DBAs specifically to monitor and support the data warehouse environment. Data warehouse administrators must be capable DBAs, but with a thorough understanding of the differences between a database that supports OLTP and a data warehouse.

Data warehouse administration requires experience with the following:

Business intelligence, query, and reporting toolsDatabase design for read-only accessData warehousing design issues such as star schemaData warehousing technologies such as OLAP (including ROLAP, MOLAP, and HOLAP)Data transformation and conversionData quality issuesData formats for loading and unloading of dataMiddleware