supporting Oracle as sysadmin

Forum Index » Forums » Miscellaneous Discussion
Author Message
Ken
Joined: Dec 03, 2008
Posts: 1
Other Topics
Posted Dec 03, 2008 at 11:25:29 AM
Subject: supporting Oracle as sysadmin
Hi, I come from an HP-UX background with a bit of Linux. I've a chance to accept a new role as a Linux system administrator but I do not know anything about relational databases, SQL or Oracle, which is part of what I have to support in the role (at least that's what I believe). Although I'm not knowledgeable about Oracle or SQL, I want to accept the role because at least it gives me some experience in it. Otherwise, how would one get experience in Oracle or SQL? (I think it's a better position to be hired despite not knowing anything about Oracle/SQL than a company not hiring you if you don't have experience in it). The following is part of the summary of the position: [i]Major administrative applications include SAP (Human Resources, Finance, and Purchasing) and the Student Information System - Callista. There are also a number of smaller, locally developed applications. Oracle is the standard database platform; however, there are also a small number of SQLServer applications. Oracle’s Application Server (forms, reports and web services) provides the front end for a number of applications. [/i] My question is in what ways could I expect to be supporting Oracle? (I can only think that I might be asked to do backup for it). How can I prepare myself before I actually start work in this new role? Appreciate your feedback/advice on this. Thank you. Ken
Back to top Profile Email Website
Shashank Sharma
Joined Jan 01, 1970
Posts: 1657
Location:New Delhi, India

Other Topics
Posted: Dec 24, 2008 1:42:43 PM
I suggest you buy some Oracle and SQL administration books and read through them. Otherwise you'd be lost.

Coauthor of Beginning Fedora: From Novice to Professional published by Apress.

Please follow the Forum Guidelines

Back to top Profile Email Website Yahoo!
Abhinav Vaid
Joined Jan 08, 2009
Posts: 1

Other Topics
Posted: Jan 08, 2009 6:19:02 PM
Very interesting question. I very strongly recommend you to pick up all the commands/syntaxes etc to run/perform various tasks as per your responsibilities. And then have all books not as a handy reference but to have a command over the subject as you move forward. There are so many forums where there are quick ground up kits available which can be referred to. I guess the role would be just backing up ( certainly a part of it). Creating accounts, troubleshooting problems, security issues etc etc would be addons. For the smaller apps that you have referred to, the SQL querries and basic commands should be your first attempt to set you going. Applying them on the job would increase your confidence and the learning curve will keep becoming steeper.
Back to top Profile Email Website
Rubberman
Joined Jul 30, 2007
Posts: 944
Location:40 miles west of Chicago

Other Topics
Posted: Jan 10, 2009 3:22:23 AM
There are a couple of issues to resolve here. 1. Is your support role limited to the systems the databases run on (keeping the data backed up, drive farms operational, etc.), or will you be expected to manage the internals of the databases themselves (partitioning table spaces, configuring transaction logs and rollback segments, database user accounts, and other dba tasks)? 2. Will you be expected to help with the application logic (stored procedure development and debugging, data normalization, triggers, relation integrity rules, etc)? I have 25 years experience in this (large-scale database and transaction processing systems), and both database systems require a good deal of training and experience. Also, you are discussing two major database systems with very different procedural languages. Oracle uses PL/SQL, and Java for server-side transactional logic. PL/SQL is a subset of ADA. SQL Server uses Transact-SQL which is an entirely different programming language, developed by Sybase and acquired by Microsoft when they licensed the Sybase system to make SQL Server. They also support SQL embedded in 3gl source code, such as C/C++, Cobol, et al. as well as C/C++ API libraries. Will you be supporting those applications as well? So, first go online to Amazon.com and figure on purchasing a few hundred $$ worth of foundation books, starting with E.F. Codd's "The Relational Model for Database Management" and C.J. Date's "An Introduction to Database Systems". They are the bibles of relational theory. Then get from Oracle Publishing "Oracle N: The Complete Reference" where 'N' is the current version (11g I think) - the Oracle 8 version I have runs about 1300 pages... Then find the equivalent for SQL Server and Transact-SQL, drink a LOT of coffee and start reading. That and about 3 years of experience will give you a reasonable base to becoming a noob DBA. If you are REALLY good as a sysadmin, then you can pick up enough on the job to do the non-database tasks I mention in item #1 above, while the other #1 dba type of tasks may be a bit much, especially if they aren't done correctly can totally bollix the integrity and performance of the systems in question. The issues I mentioned in item #2 is entirely another kettle of fish. Finally... Good Luck! [Modified by: Rubberman on January 09, 2009 09:25 PM]

Sometimes real fast is almost as good as real time. Remember, Google is your friend!

Back to top Profile Email Website AOL Instant Messenger
Polaris
Joined Jan 10, 2009
Posts: 4

Other Topics
Posted: Jan 10, 2009 6:08:34 PM
I'm a Unix Admin for HP-UX systems running MQ, Weblogic and Oracle. Trust me, 90% of all medium to large companies won't let a sysadmin do too much with Oracle. DBA's will patch, change parameters, update schema and pretty everything else that needs to be done. As a sysadmin, you will be responsible for changing Kernel Parameters that will be required to run Oracle, if its an HA (High Availability) cluster, then you will probably be responsible for maintaining some of the startup scripts and make sure that you can failover from one node to another. Also monitoring different processes that are important and maybe maintaining cron jobs for running maintenance. I would think Oracle experience would be pretty much a "good to have" skill, but not a must. Remember that they will still have to train you on the position so don't worry, even a skilled person feels like a noob when starting a new job with a new company just due to process and procedures if nothing else. Besides, throwing yourself in the fire is a good way to learn :)
Back to top Profile Email Website
Rubberman
Joined Jul 30, 2007
Posts: 944
Location:40 miles west of Chicago

Other Topics
Posted: Jan 11, 2009 12:43:01 AM
To Polaris: Good reply. In any case, the salient question is whether they just want him as a sysadmin type person, or to do double duty as a DBA as well. It wasn't clear from the original posting.

Sometimes real fast is almost as good as real time. Remember, Google is your friend!

Back to top Profile Email Website AOL Instant Messenger
Forum Index » Forums » Miscellaneous Discussion