If we take a look at DBA day to day tasks

(from Admin Guide 10GR2):

Task 1: Evaluate the Database Server Hardware

Task 2: Install the Oracle Database Software
Task 3: Plan the Database
Task 4: Create and Open the Database
Task 5: Back Up the Database
Task 6: Enroll System Users
Task 7: Implement the Database Design
Task 8: Back Up the Fully Functional Database
Task 9: Tune Database Performance
Task 10: Download and Install Patches
Task 11: Roll Out to Additional Host
---------------------------------------------------------------------------------------------------------

Task 5: Back Up the Database

This requires sysadmin, ranging from knowing how to invoke rman to specific
commands and procedures involved in snapping SANS.

Task 6: Enroll System Users

Might need to know about using the OS to control users.

Task 7: Implement the Database Design

Could be some issues going from logical to physical design.

Task 8: Back Up the Fully Functional Database

See Task 5.

Task 9: Tune Database Performance

How can this not look at system admin issues?

Task 10: Download and Install Patches

If you ain't got the perl, you ain't got the whirl.

Task 11: Roll Out to Additional Hosts

"Can I copy database files from Solaris to Windows?"

Followup February 5, 2007 - 7am Central time zone:

task 5: in general, no it does not. I myself for example do not use "snapping sans" and in
general do not even recommend it. For most situations - it just "ain't so" that you need to
be a "sysadmin" to simply backup a database.

task 6: no, that is not the job of a DBA at all - they manage the database, not the OS.

task 7: not to do with the system again.

task 8: i agree, see task 5, no need to be a sysadmin

task 9: because 99.9999% of all tuning is application level.

task 10: eh??? I've never used perl

task 11: a DBA that cannot do exp/imp or datapump or dump and reload - well, they ain't
a DBA and they do not need to be a sysadmin
-----------------------------------------------------------------------------------------------------------

storages, monitor CPU and IO resources and make usre that instances are avialable 24*7.
No need to see into the schemas and find what objects are lying in it for what purpose

As a first step, Anyone who is interested to become a dba

has to work on his personal pc to gain
hands on experience to an extent (technically) and should
gain good knowledge of the following

SQL
Reasonable knowledge in PL/SQL (to understand the code)
Database Architecture and storage management
Init Parameters
types of tables,indexes and privileges
utilities such as exp, imp, SQL*loader, tkprof and so on
understanding of tkprof and statspack reports
Unix Commands especially filter commands and vi editor
Dos and Dont's from the general practice of the company