Ever fumble around at 2 AM looking for that SQL statement you wrote a while back? You know, that one special script that will give you just the information you need to solve the problem and go back to bed? I must admit, I have done my fair share of moonlight script hunting. This blog will provide you with a few recommendations on naming convention best practices.
Let’s start our series on Art of Being a Successful DBA by covering the art of good documentation. Although the importance of a well thought out and detailed documentation library is blatanly obvious, creating documentation is the task most often postponed by an overworked DBA unit.
One of the benefits of my 20-year career (I think) is that most of the jobs I have held can be described as somewhat “unforgiving”, shall we say… What these jobs taught me is that I needed more than just technical expertise to become successful in my chosen profession. I quickly learned that becoming proficient at the various disciplines I will be discussing in upcoming blogs was just as challenging to me as honing my technical skill sets.
You got the job because you’re a quick learner, have the ability to understand complex systems, and most importantly, you can troubleshoot. However you became an Oracle Apps DBA, you’re one now, so the fun starts. I started this blog to assist young Oracle Apps DBA professionals who might need a little more detail in their solutions and good discussion into basic, fundamental Oracle architecture and other Oracle App subjects.