|
||||||
|
Mistake #8: Not properly sizing the database memory footprint Many things in information technology use caching to improve performance by doing less work. Oracle databases are no exception – they use in-memory caching to improve database performance. For example, they cache database records to lessen the number of times they are read from disk; they […] Mistake #7: Not paying attention to the alert log Oracle databases each have an alert log, which is a file to which the database writes about key events. Most entries in the alert log are just informational, such as summary information about database startups and shutdowns, online redo log switches, etc. Some entries, however, can […] Mistake #6: Not involving management in data loss and target recovery time decisions I recently met with a management team to determine acceptable data loss and recovery time thresholds. My strategy was to bring a printed list of questions for the team to consider and answer. It was a truly productive discussion. The client DBA, […] Mistake #5: Not keeping your backups in well-chosen and varied locations Texas is a big place, and one geographically disparate enough to have a large variety of natural disasters. We have tornadoes, hurricanes, brush fires, and floods. We even had a tiny earthquake in the Dallas area a couple of years ago. We also have […] Mistake #4: Not recover-testing your backups This is a critical deficiency, and it is very common. And, to be truthful, this mistake is not unique to smaller Oracle shops. I’ve been to some larger Oracle shops that also skimp on recovery testing, but I find this to be more common in the smaller shops where […] Mistake #3: Not having a diversified backup strategy In the last post, we discussed why you might or might not want to run in archivelog mode. Now we’ll discuss some related decisions. As in the last two blog entries, I’ll be oversimplifying, for the sake of illustration. Additionally, there is often more than one way […] Mistake #2: Choosing (or defaulting to) an inappropriate archivelog setting Let’s say you back up your database nightly. If your database were obliterated in a hardware failure at 3:58 pm, would it be important to recover the changes made to the database since last night? If it’s a training or test database, or a production […] |
||||||
|
Copyright © 2024 … McNeely Musings - All Rights Reserved Powered by WordPress & Atahualpa |
||||||
