Shulou(Shulou.com)06/02 Report--

Introduction

Over the years, I spent a lot of time on different newsgroups talking to IT people who wanted to know how to get a job as a database administrator (DBA) or how to grow into a DBA, and now they have jobs. Over the years, many people have put forward different opinions on how to achieve this goal. This article is a synthesis of those opinions and can give good advice on how to do a good job of DBA. This article is also about how to make a DBA more valuable to the boss. If you are already a DBA, you may want to skip the first few paragraphs of the article.

Should I be a DBA?

One of the questions I asked was whether one should pursue a career like DBA. This question is not easy to answer because it varies from person to person. Some people have the talent needed to be a good DBA. Others don't think it's easy to grasp the secret of becoming a DBA. The DBA profession needs to master certain skills. It also requires requirements that are not necessary for other IT occupations. Therefore, in order to answer this question, I usually give the people who are going to be DBA the requirements necessary to describe their DBA career. In the following paragraphs, I will end with a question. Please take some time to consider and answer these questions before moving on to the next paragraph.

Many people are determined to become DBA for many reasons. One of the main reasons is salary. DBA is one of the highest-paid occupations in the IT industry. Others want to be DBA because they like to praise DBA because he is honored, or because he looks cool! Personally, I think it's worthwhile to be a DBA. It's a very interesting and exciting profession. So what is the reason why you choose DBA as a possible career choice?

Unless you are prepared in advance, you may find your career in DBA fraught with setbacks and headaches. A database exists between the operating system and the end-user application. Similarly, DBA must be very proficient in the operating system on which his database resides. DBA doesn't necessarily need to know everything about the operating system, but the more he knows, the better. The database is closely related to the operating system. It is necessary to understand this connection. DBA also needs to know the server hardware and how it affects and helps the database. At the same time, DBA must understand applications. DBA may be asked to help developers create reliable, robust database applications. And, most importantly, and most obviously, DBA must have a thorough understanding of the database engine, how it works, how all the engines fit together, and how it affects the database engine's ability to deliver data to end users and applications. The best DBA I've ever seen has a very deep understanding and not just in the database itself. They know something about system management and application development. Many times they have one or two backgrounds before they become DBA. In any case, it takes a lot of background knowledge to be a qualified rather than an excellent DBA. Are you ready to start learning until you feel like you can't learn any more?

Many of the people I've talked to who have difficulties starting their DBA careers actually have problems trying to absorb a lot of what DBA needs to know. After all, system administrators learn the details of the operating system full-time. Application developers learn how to write good programs full-time. DBA not only needs to know a lot about these two different tasks, but also needs to spend more time understanding the architecture of the database and how every piece of everything fits together! Doesn't that sound daunting? There are many people who think this way after failure and regard DBA work as a very difficult thing. There are also people who spread and understand all this information and use it to make good, technical-sounding decisions. As I used to say when I was a DBA, all of this seems like a big mystery to me. Putting it all together well is a challenge. What kind of person are you?

Many DBA are available at any time. They receive calls at all times of the day or night to solve fatal problems with their databases. Database is an indispensable part of the basic organization of business information technology. Without data, there is no need to have a computer system. Data drives business. What if amazon.com 's website could not search for products in the database and if no one could place an order for their products? It won't be in business for long. When the database down goes down, even for a short time, the company will lose a lot of money. For this reason, DBA must solve the problem as quickly as possible after arriving at the scene. Many companies have their own DBA teams so that they can take turns on standby. These DBA 24x7 hours maintain database applications. Are you ready to be available at any time if your job requires it?

Some DBA responsibilities include patching software or making changes to the database. In general, these operations cannot be done while company employees are working, because the database must be run so that they can work. This means that DBA often has to do its work early in the morning or late at night or even on weekends, in short, from outside during normal working hours. Are you ready to work during irregular hours, or are you looking for a nine-to-five job?

One of the important things to master for DBA is what is often referred to as "soft technology". DBA needs to work well on a team, which is usually changing, such as system administrators, network administrators, application developers, project managers, and others. DBA should be able to explain complex technical concepts in fluent English for the rest of the team to understand. DBA also needs to be able to direct team members on database-related issues. How's your soft technology?

The following is not a full list, but includes the typical responsibilities of DBA:

Make monitoring database instances a daily necessity to ensure their availability. Resolve unavailable issues.

Collect system statistics and performance information for orientation and configuration analysis.

Configure and adjust the database instance to achieve optimal performance under application-specific requirements.

Analyze and manage database security. Control and monitor user access to the database. Audit the use of the database if necessary.

Monitor the backup program. Provide recovery if necessary. Test the backup and recovery program.

Upgrade the RDBMS software and use patches if necessary. Upgrade or migrate database instances if necessary.

Support application developers through database-related actions.

Follow database trends and technologies. Use new technologies when available. Install, test and evaluate new Oracle related products.

Perform storage and physical design. Balance design problems to achieve performance optimization.

Create, configure and design the database instance of the letter.

Diagnosis, fault detection and resolution of any database related problems. Contact Oracle support staff if necessary so that the problem can be better resolved.

Make sure the Oracle network software (SQL*Net, Net8, Names, OiD) is configured and running well.

Work with system administrators (Unix & NT) to ensure that Oracle-related transactions are handled well.

Create any necessary scripts for effective, regular maintenance of the database.

The questions in the previous paragraphs are designed to make you think about what an DBA should do and help you decide whether this is the right career for you. I don't mean that if your goal is to become DBA, these will stop you. I'm just trying to show some facts. I have seen some DBA collapse once they are hit by the actual work. They spent time, energy and some money to get their first DBA job. Personally, I think this profession is very valuable. And I can't imagine doing anything else right now. So, this paragraph helps you decide if this is what you want to do. If it is, then do everything you can to get it!

How do I get my first DBA job?

You have read the previous paragraph and think that being an DBA is a good career. Congratulations! I hope your career will become as exciting and meaningful as you think. So, how did you get your first DBA job? I have heard this question asked many times.

In the early 1990s, the Internet developed rapidly. It makes the company sprout like grass. Companies swarmed in and began to create their online image. Almost all of these companies with websites need a database as the background for web applications. Unfortunately, there were not so many DBA in this area at that time. In the IT industry, DBA has become extremely scarce. During that time, getting a DBA job seemed as long as you could spell "Oracle" or maybe just had access to a database for a semester in college. In order to make life better, the lack of DBA prompts companies to pay high salaries to potential employees. If you want to be a DBA, it's easy, very easy. All you have to do is prove that you know what a database is and the work will show up in front of you sooner than you expect.

Then the Internet bubble burst. A large number of companies that put into production of the Internet went bankrupt. Many DBA who work for the company are looking for a new job. It is much easier for companies that lack DBA to find someone with DBA experience. At the beginning of the 21st century, life was not easy (at least in the United States) because the economy was not very stable. Companies have tightened their belts. All this translates into fewer job opportunities and fewer job openings for DBA candidates.

The hardest part of getting your first DBA job is that every position requires some work experience. If you look at it from the company's point of view, you can understand why experience is necessary for DBA positions. If he had no experience, would you pay this person a high salary to operate, maintain, and run the largest and most important part of your IT infrastructure organization? Will your company pay an inexperienced DBA? And millions of dollars may be lost while waiting for him to grow up. For most companies, the answer to these questions must be no. So, without experience, it is difficult to get your first DBA job.

The rest of this section will give you some advice on achieving the goal of your first DBA job.

Tip # 1: get an education. -- learn as much as possible about the database. This is likely to take up part of your time and energy outside of your normal work. Attend the database training course held by the local university. Many training companies hold training courses for database administrators. If your boss doesn't support your study, you may have to pay for it yourself. Many DBA occupations require at least a bachelor's degree or above in computer science or related major, so you must have at least that diploma.

Tip # 2: exercise becomes DBA. Many database vendors allow you to download beta or evaluation versions of their database systems. Download a copy and install the software on your personal computer. Practice using a database. Intentionally destroy the database and try to repair it. Try to perform as many DBA duties as you can think of. Test and hone your skills on your own test platform so that you can prove your database management skills.

Tip # 3: get certified. I see a lot of people complaining that they have been certified but have no experience, but still can't get their first DBA job. Even if there is nothing else, you have learned a lot when you are certified. You need more than that. But it will help you in the end.

Tip # 4: use your existing skills. Many DBA have a system administrator background. Others have a background in application development. If possible, see if you can use your existing skills to get a job. The goal now is to create a win-win situation for you and your boss. For example, let's assume that you are already a system administrator and want to enter the DBA domain. Maybe you'll find a job that will use your system management skills for part of the time and get you involved in database management the rest of the time. If you are already an DBA on one product platform but you want to switch to another product platform, see if you can find a job with access to both product platforms. In this way, both the company and you get what you want. After you have been directed to work for DBA, you can try to get a position that allows you to do it full-time, maybe in the same company.

Tip # 5: take advantage of this opportunity. Sometimes all one needs to get into the DBA world is the right place and the right time. If your current boss has an opportunity for you to work on any database project, seize it! Any database experience is better than no database experience. Let your manager know that you are actively looking for any possible database opportunities. They may think of you when the next opportunity comes. After working on these database projects and seeing your desire to be a DBA, they may decide to train you and promote you. Many people got his first DBA job in this way and unwittingly became a lower-level DBA after doing some database-related projects. Usually when an DBA leaves the company, the company will look internally for a candidate if they think the candidate is trainable.

Tip # 6: look for lower-level DBA positions. If you're just working for a lower-level DBA job, you see a requirement description for a DBA position that says they're looking for a senior DBA or something. So, let's be more rigorous. You don't have any advanced experience. I have discussed why the company will not consider you for such a position. But they will consider you in a low-level position. The low-level DBA works under the guidance of the high-level DBA. They fumbled for tricks. In general, advanced DBA takes responsibility for the database and receives all the honors. But don't worry. As your career develops, you will have more and more responsibilities and trust. Since you don't have any experience, you should set sail from here.

I've also heard that some companies are looking for a senior DBA, but in the end, they actually want to hire a low-level DBA. You may wish to apply for such a position, although you may not be qualified. They may still decide to hire you. But make it clear in advance that you are still in the exploratory stage and are already at a lower level of DBA. Don't try to trick them into thinking you're an advanced DBA. This will only reduce your chances of getting the job.

When you have found your first DBA job, continue to the following section to learn how to move on.

I just got my first job! What do we do now?

Congratulations! You are a full member of DBA Club now! Are you ready for this coveted and exciting career? Your work has just begun and you have lagged behind in your studies. You will find that you have to master a lot of knowledge to be an effective database administrator. Your first year or the first two years will spend more time studying than before. If you find that the amount of learning is overloading your brain, take a break, take a breath, and then go back to study. To help you move on, you can do it in the following ways:

Step # 1: relational database theory-in this part I assume that the database you will manage is a "relational" database. Other database models also exist, but relational model is the dominant database model in industry in the past two decades. If your database system is another schema, learn its theory. The relevant database theory is very important. It is the foundation of everything else. I also see that many people who jump to database management positions never want to learn pure relational database theory. Inevitably, the lack of theoretical basis in their career has been exposed as a weakness. If you have a good understanding of relational database theory, you can easily change in any platform of relational database management system (RDBMS). It doesn't matter if I use the Oracle database, or IBM's DB2, or Microsoft's SQL Server. They are all relational database systems. They're all doing the same thing at the bottom. The difference is how they do the same thing. Pure relational database theory is not necessary for lower-level DBA. But it is very important if you want to surpass the lower level of DBA. Many university textbooks contain the theory of relational database very well. One of the widely used textbooks is the database system foundation, Bejamin/Cummings Press, written by Elmasri and Navathe.

Step # 2: learn the query language thoroughly-every database has a language that allows you to get data from the database, put it in the database, and modify the data in the database. For relational databases, this language is the structured query language (SQL). This language is a tool for you to contact the database. It is important not to let this tool become an obstacle to future learning. Practice different SQL statements in your test database until they become your habit. A very good book on this subject is called Oracle 9i complete reference (Oracle 9i The Complete Reference), written by Loney and Koch, Oracle Press. Every Oracle DBA should read this book early in his career. The Oracle 9i reference manual (Oracle 9i SQL Reference manual) is another important source of knowledge. You can access all Oracle online documents on their technology website TechNet (http://technet.oracle.com). You have to sign up for an account, but it's free. Each should have an account on TechNet.

Step # 3: start learning basic database management-isn't that why you were here in the first place? Why is it in third place on the list? We are trying to build a pyramid of knowledge, and I have a strong feeling that one needs to know relational database theory and SQL and use them as tools when you learn how to do basic database management. These include starting and shutting down the database, backing up and restoring the database, and creating / deleting / modifying database objects. For Oracle database management, there are a large number of books on the market that can give you a good experience. This book is the Oracle 9i DBA manual (Oracle 9i DBA Handbook by Loney on Oracle Press). Most DBA I know have read this book more than once in the early stages of their careers. Here, you should read and understand both the Oracle 9i concept guide, the Oracle 9i administrator guide, and the Oracle 9i backup and recovery guide (Oracle 9i Concepts Guide, the Oracle 9i Administrator's Guide, and the Oracle 9i Backup and Recovery Guide) are all from the Oracle documentation.

Step # 4: read, read, read again-since you are just beginning your DBA career, you are beginning to lay the foundation for your skills. It takes a long time to form, absorb and comprehend all the knowledge you will learn. There is no doubt that DBA people who are more experienced than you have a lot of work to do, so they may not always free up a lot of time to help you with your study. You have to learn a lot by yourself. This is the purpose of reading. There are many books on the market that can answer many database-related topics. Oracle Press is the official publishing house of Oracle and has a large number of books related to Oracle. There are also other publishers, such as Wrox Press and O'Reilly Press. You can also find Oracle documents to read. And there are many websites and newsgroups. Read as much as you can so that you can go on. Also, reading them more than once allows you to absorb what you missed the first time you read them.

Step # 5: create test cases-I often see beginners asking basic questions that are easy to answer if they take some time to think about them. There is no doubt that you will have a lot of problems when you start to learn Oracle. See if you can answer these questions yourself. For example, I was once again asked if I could insert null values into columns with uniqueness constraints. At first, this may not seem like an easy question to answer. But it is very easy to test! You just need to create a simple table. In one of the columns, if the uniqueness constraint. Try inserting a null value into the column. Does it work? You should be able to answer this question very easily. So why create these cases? One reason is that it can improve your ability to solve problems. The skills needed to create these cases are the skills used to solve problems. Problem-solving skills will be of great help to your DBA career. Another reason is that as your career grows, you will often need to create more complex test cases to ensure the success of databases and applications. In the future, even simple test cases can form more complex database and application decomposition.

Step # 6: find a mentor-a mentor who can lead your DBA career (or other similar career). They can give you instructions, answer questions, and save you some time as your DBA grows up. I hope this article can serve as a mentor for a period of time in your career development. If you work with a senior DBA, that person should be responsible for providing useful guidance to your career. You can also choose others to guide you at the same time.

Step # 7: participate in a local user group-many multinational cities have local user groups that meet regularly to discuss database-related topics. If possible, join one of the local user groups. This will give you a good way to communicate with others.

How can I change from a beginner in DBA to an intermediate DBA?

You have been a DBA for some time. Do you want to improve your skill level now? What should we do next? First, look back at the previous section and make sure you have completed all the steps. A thorough understanding of the SQL language is very important. It is also very important to understand the theory of relational database and master the basic tasks of database management. By now, you should be depressed by reading documents and other books. If not, then you are not ready to pursue further studies and increase your DBA skills. If you are ready to continue, I have prepared some ways for you to continue your studies.

Step # 1: learn the operating system and your server hardware-as I said earlier, the database exists on top of the operating system and server hardware. It is necessary to understand how these components work. You should know how to fit with a particular operating system. How do you delete or edit files? If your operating system is Unix, you should master the command line and how Unix commands assist you. The same is true for running on Windows or other operating systems. You also need to know something about the hardware of the server. What's the difference between physical memory and virtual memory? What is RAID and how does the different levels have an impact? Why do databases prefer more physical hard drives than a large hard disk volume? You need to know these things so that you can easily talk to your system administrator about how to configure your server so that it can fully support database conversations.

Step # 2: learn application design because it is related to the database-as mentioned earlier, the database exists between the operating system and the database application. You really need both. How does the SQL language help create good applications? What are binding variables and why are they important? Tom Kyte has written a very good book that gives good advice on Oracle application design. His Expert One-on-one Oracle books can be found at Wrox Press. I highly recommend reading this book. He describes in detail the things that can generate and destroy Oracle applications. You need to know this because your application developers want guidance and database knowledge from you. Learn anything related to application design. It may be beneficial to attend a course on software engineering, operating systems, or data structures.

Step # 4: get certification-it may not be necessary for your job, but it must be good for you. Every day as DBA, you learn a lot of new and exciting things. Maybe during this period of your career, there are a few days when you don't learn anything new. But you still have a lot to learn. Becoming an OCP (Oracle Certified Professional) DBA requires that you have already learned the basics of all aspects of database management. I found that in the course of studying for the OCP exam, I learned something I had never come into contact with in my work. Once I learned a special subject that I had never encountered before, and in later days I was able to use that knowledge to solve problems. If I had learned to fail in the OCP exam, I would never have solved the problem in that special way. This has happened in front of me again and again. Some people may say that certification is really not worth it. I'd say it's only good for you. So, go and get certified!

Step # 5: get a repository-in the previous section, I pointed out that each DBA should have an account on Technet. This is one of your main resources. But there are many other resources at the same time. Many people share their Oracle knowledge. If you haven't started yet, you should use a web browser to search and collect a lot of Oracle resources. If you like, you can start by visiting my website (http://www.peasland.net). Here is a list of sites that Oracle DBA must know:

 Ask Tom-http://asktom.oracle.com

 Jonathan Lewis web site-http://www.jlcomp.demon.co.uk/

 Ixora (Steve Adams)-http://www.ixora.com.au

 Orapub-http://www.orapub.com

 Metalink (Oracle support website)-http://metalink.oracle.com

There are many other good websites.

Step # 6: start communicating in different newsgroups and forums-you may have found them, but if you haven't already, it's time to start. There are many newsgroups and forums that can answer any of your Oracle questions. There are many masters in the Oracle community who are willing to share their knowledge with you. All you have to do is ask questions. Here is a list of the best Internet groups that can start communicating:

Usenet newsgroups-comp.databases.oracle.server and comp.databases.oracle.misc are two very famous worldwide newsgroups that can communicate. They have a large number of communication files on Oracle issues. Watch the best ways to use newscasters in these groups. But if you want to access it in a web-based way, you can also search it through the Google search engine. (http://groups.google.com/groups?... Mp.databases.oracle)

Quest Pipelines- when they were originally owned by software provider RevealNet, they were called the RevealNet Pipelines. Now, Quest has purchased RevealNet and owns Pipelines. Because the Pipelines is medium, these are my favorites. You can find Pipelines (http://www.quest-pipelines.com/index.asp)) here.

It is good to observe how others go through trials and tribulations. If you have any questions, feel free to ask them in the group. If you want to ask questions, you should usually include some information, such as your Oracle version and the platform on which Oracle runs. These will get very different answers. If you forget, someone will remind you! Even you can learn a lot from other people's answers without asking questions. I can't remember how many times I was able to solve the problem simply because I remember other people asking the same question in the newsgroup.

How do I change from an intermediate DBA to an advanced DBA?

Well, as DBA, you've been working hard for a long time. You feel ready to take another step forward. What does it take to be a senior DBA? The following sections will help you move on.

Step # 1: read all the documents-Oracle documents are not usually easy to read. Countless times, you go through the documents just to figure out the whole thing. If documents are the best thing, then there will be no market for Oracle books standing in your shelf. But the document does contain information that cannot be found anywhere else. For example, you can't find a detailed description of each specific INIT.ORA parameter or V$ view. Books may cover some of them, but Oracle documents contain all of them. I came across a very powerful advanced DBA who didn't read the Oracle documentation from beginning to end. It's not an accident. Oracle documents must be read. Maybe you've read the Oracle concept Guide 12 times by now. But when Oracle 10i is released, you will have to read it again. Any new concepts about 10i will be documented. If you really want to take it to the next level, read those documents. Don't run away from it.

Step # 2: become an expert-the Oracle database is a very complex thing. To take it to the next level, you must be proficient in many components of the product. Start with backup and recovery. Become an expert in backup and recovery. Deliberately destroy the database and see how to restore it. Try to destroy the database in any way possible and see if recovery is possible. You will thoroughly understand the concept of backup and recovery. After you become an expert in backup and recovery, then become an expert in other fields. You will have endless problems to master. Keep it that way throughout your career. But remember, no matter how professional you are, in some areas, some people will know more than you in some ways. Don't take it personally. Just learn as much from that person as possible.

Step # 3: actively participate in newsgroups, forums and user groups-earlier, I mentioned why different newsgroups and forums are good places to learn new knowledge. Now it's your turn to take the next step and answer any questions you can answer. You will be amazed at how much you can learn in the process!

Step # 4: write white papers and show them-this is similar to the method mentioned earlier. First of all, it is important to share the knowledge you have. If you have reached this point in your career, in a sense, you can't do without the contributions of others. So now is the time for you to give to others. Second, amazing things happen when you try to share your information. The information goes through an eye-popping process in your mind when you want to express the problem in clear, concise language so that others can use it. This process enables you to consolidate your knowledge, which cannot be done in other ways. So sharing that information, seminars, and newsgroups and forums in white papers is a great way for you to learn and take your abilities to the next level. Along this road, you should do two things. First, realize that you are going to make mistakes. Others will be happy to point out those mistakes, sometimes in a sense that is not very good. Don't try to hide your mistakes. Acknowledge them and learn from them. Second, learn to say that you don't know the answer instead of trying to pass in a deceptive way. People will know sooner or later that you are trying to deceive them. Simply tell them that you are not sure about the answer now, but you will come back and tell them when you find the answer. If you keep these two things in mind, you will not violate your honesty and you will grow into a professional IT.

Step # 5: become an expert in solving Oracle problems-Advanced DBA is usually seen as a solver of complex Oracle problems. You will use all your skills to solve many problems, which are accumulated over the course of your career. Anything I mentioned earlier will be used in the problem-solving process; documents, books, newsgroups, test cases, and other DBA will help you solve the problem.

Step # 6: become an expert in performance tuning-Advanced DBA is often seen as someone who adjusts the performance of databases and applications. If you are a senior DBA but you can't analyze performance bottlenecks, your company will look for these services elsewhere.

Step # 7: become an expert in carrying capacity planning-Advanced DBA is usually seen as someone who plans database hosting capacity based on data growth and transaction growth. Advanced DBA needs to identify system bottlenecks before affecting application performance. For example, DBA should know to preset more disk space before the database runs out of available disk space. Not paying close attention to the carrying capacity plan will lead to downtime of the production database.

Step # 8: pay close attention to new technologies-Advanced DBA should have good suggestions for the future of database-related technologies in the IT world. What technologies are available to help the database? For example, learn the advantages and disadvantages of storage domain networks and how to apply them to database systems. What technologies can be used in the near future and which can help us? For example, at the time of this writing, the linux operating system is becoming more and more popular. What will Lunix bring to your database operating system platform? Can it work for your company?

Conclusion

From getting your first job to growing from an entry-level DBA to a senior DBA, I hope this article gives you some advice on how to spend all stages of your career. You can use this article no matter where you are in your DBA career.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.