We are a very large Oracle site and have system DBAs and application DBAs. Our system DBAs are responsible for the installation of Oracle up to the creation of the instances. Does this seem like a reasonable split of duties? In this split do you see any problem with not allowing the application DBAs to have the Oracle password?
I've seen many different company configurations regarding the DBA manpower and their duties. The only people who can answer if this is a reasonable allocation of duties is the people in your company. What works for one company may not work for others.
Many companies have production and development DBAs. The development DBAs work with the application developers and get the product up and running. Then they turn it over to the production DBAs who monitor the production instance. This does seem to work for most companies.
Personally, I can't see how just creating an Oracle instance can keep a person busy for too long. How many instances can you create in a year's timeframe? But what works for you company needs to be decided by the individuals in the company, along with their management.
For More Information
- Dozens more answers to tough Oracle questions from Brian Peasland are available.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical Oracle and SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our PL/SQL, database administration and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.