1. Backup Comes First
We must always remember that systems will eventually crash. Without an effective backup, you're just waiting for the inevitable! I often joke that the only thing that can wake a DBA up in the middle of the night is the thought of not having a valid backup.
2. Think Thrice Before You Act
Always be clear about everything you're doing, or better yet, don’t do it! Sometimes, pressing "Enter" or running a single command can cause an irreparable disaster. Therefore, you need to confirm everything you’re about to do, and, when necessary, protect the scene.
3. rm is Dangerous
Be aware that in UNIX/Linux, this command means you might lose everything permanently, so double-check your actions!
Too many people have regretted using "rm -rf." I wrote this rule after being woken up one morning by a friend who had accidentally run "rm -rf" and deleted 200GB of a database—without a backup.
The only advice I could give him was: Stay calm.
4. You Set the Standards
Good standards are the foundation of minimizing failures. As a DBA, you need to establish and enforce these standards, which even guide developers and system administrators. This can help prevent both intentional and unintentional mistakes, thereby reducing the risks to the database.
We know that on well-managed database servers, even "rm -rf" might be restricted.
Perhaps there are even more rules we need to follow. That's why I always emphasize that DBAs must be meticulous and focused. Of course, I also really like another saying: "A person of extraordinary resilience will accomplish anything."
These four fundamental rules are my humble advice, shared with my fellow DBAs.
Visit the https://payhip.com/OracleeBookSoftwareShop website to get an e-book about Oracle internal storage.
Top comments (0)