I tripped across this blog post by Jeff Smith and I have to say, this man has been scarred by what has to be the worst experience interacting with a DBA I have ever heard of. And Jeff, if this is not fiction, if this is real and you have really suffered this much – give us a call won’t you?
Guy Bowerman has published on Informix Application Development, the 37th edition of Log Buffer, the weekly compendium of database blogs.
I enjoyed the event and the venue very much. The presentations very generally very good, and to my surprise some of them were somewhat lighter than I would expect. However, that might actually play positively in extending the audience — there are only so many freaks interested only in hardcore performance and internals.
We welcome back for a second time Lisa Dobson, who has published the 36th edition of Log Buffer, the weekly review of database blogs, on the Oracle Newbies Blog.
I was reading a couple of items on gapingvoid which inspired me to use our blog for a conversation with our customers (and with potential Pythian DBAs) about what it’s like to work with Pythian. What exactly does an on-site DBA get from working with Pythian Remote DBAs? Find out here.
Pythian has been a rapidly expanding company over the ten months I’ve been here. About a dozen new employees have come on during that time, making the total 40. I have a few observations on habits and qualities new DBAs can bring to their jobs.
Your common-cold-bedeviled editor tardily submits the 35th edition of Log Buffer, the weekly review of database blogs, for your perusal.
Welcome to the 34th edition of Log Buffer, the weekly review of the database blogosphere.
In a story that we’ve been following a long, long time, Oracle finally succumbed to multi-core pricing pressure today.
So you have swallowed the standby bait. You have used RMAN duplicate to create a sparkling new standby and things are looking rosy. Then, when you check the lag between the primary and standby (in MAXIMUM PERFORMANCE mode), you discover the standby is miles behind. Oracle (at least from 9iG) rides to the rescue again. The parameter ARCHIVE_LAG_TARGET tells Oracle to make sure to switch a log every n seconds.