How to become a good DBA?

<!-- [if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning/> <w:DrawingGridVerticalSpacing>7.8 磅</w:DrawingGridVerticalSpacing> <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery> <w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:SpaceForUL/> <w:BalanceSingleByteDoubleByteWidth/> <w:DoNotLeaveBackslashAlone/> <w:ULTrailSpace/> <w:DoNotExpandShiftReturn/> <w:AdjustLineHeightInTable/> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <w:DontGrowAutofit/> <w:UseFELayout/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!-- [if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--><!-- [if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]-->

What is a good DBA?

A good DBA should know the database theory deeply.

T his is the basic steps to a good DBA.

Knowing much more is less useful than knowing some things deeply.

Mastering the fundamental knowledge deeply is very important.

I interviewed some of DBA candidates. Some of them said they had many years’ experience but when asked what is instance what is database they can not tell even clearly. It is hard to image that they said they were familiar with the RAC.

Every DBA has the boundary of database knowledge even though he had learned all the knowledge. Their memory is limited, the knowledge will be forgotten if they have no chance to be applied in the real situation every day but it is almost impossible to have the chance to apply all in the real environment.

So I never think it is fair to ask a DBA how to set an implicit parameter in the dbms_repair package. What can be proven even he did know it? But instead that you can resolve the issue if you understand what is cause and effect correctly even you do not know how to take the specific actions.

Surfing the details from the internet is possible to give you right next steps.

The OS knowledge and Cluster knowledge is also very useful for a DBA for a complex environment in the company.

These skill sets help you more qualified to the current or future position. Anyone who has worked as a DBA would know that the Database is usually "guilty until proven innocent." Every performance problem gets blamed on the database regardless of its true source cause or not.
So it is necessary for a DBA to know enough OS, storage and network knowledge. Especially to combine them with database knowledge to solve the database performance problems or sometimes OS, storage or network problems to prove the database is innocent.

Does it sound scared?

Too many things need you to learn?

I do not think so.

The most important is to learn the basic knowledge first .

We need not to focus on how to do it.

As long as what is it what can it bring to us.

When the new releases come we should try to know what is it then when we need to use it we can find the details about it.

We can keep up with it easily if we only focus what it is.

And you will find the new feature also help you widen your horizon and help make you knowledgeable.