Ever wished the listener.log file was a table in the database? Wish no more! About three years ago, I sent this recipe in an email to my co-workers. Just recently, Shakir re-sent it after using the method in an emergency. Since it seems to have proved its value, I now offer it to our readers. Have a look.
Over-the-Top Tales from the Trenches: Bringing order to the chaos of every day DBA life – So you have got your nice MySQL Master-Slave replication pair setup. Everything is sweet, then the master dies/restarts or you have a slightly extended network outage. You log into the machine and check out why the slave threw an error or if your monitoring is slow, why the slave is lagging by 2 hours. You run SHOW SLAVE STATUS\G
I recently installed Oracle DB 10.2.0.1 RAC (two nodes) on Oracle Enterprise Linux x86_64 and faced three issues. Since I had to dig out at several places, I thought it might benefit others to have my notes all here.
Welcome to the 91st edition of Log Buffer, the weekly review of database blogs.
One of my colleagues made a typo in a query today that led to me discovering this issue — I think it’s a bug, though it may just be how the language is defined. But certainly a subquery that cannot run should not act as if it returns TRUE. Part of me thinks there’s an implicit join going on or something, but I’m not sure how that’s working. Have a look.
I have a client with refreshes scheduled using MV refresh groups, and it took me a while to recall the view name, asking around and RTFM’ing. Since this situation comes up regularly, I wrapped up a quick script that parses job content, takes in account MV refresh groups, and outputs the database link(s) involved. I think it could be useful to few others so here it goes.
After the interesting comment storm on Doug’s blog when he posted some of Tim Gorman’s comments on the value of data in his career experiences as compared to the value of the applications manipulating that data, I hesitate a little to post this. But, I can’t stop myself because it’s such an interesting insight! So here it is!
Welcome to the 90th edition of Log Buffer, the weekly review of database blogs.
I spent way too long figuring out code that would simply load balance based on, always go to one server, go to another server only when the first server is down., again running into the problem where the manual hasn’t been updated. I have made a Forge snippet of this code, but it does not hurt to post it here.
After spending a long time on a project for a client that does a huge amount of data movement using SELECT INTO, I posted a Connect item asking for an enhancement where a minimally-logged insert would be available from a SELECT doing an INSERT into an existing table. One day the item was updated with a comment: “This is targetted to be available in SQL Server 2008.” I wasn’t sure exactly what this meant until the last few days, when Sunil Agarwal posted a series of three posts describing the enhancements to minimal logging in SQL Server 2008 — including the ability to do a minimally logged insert via a SELECT, to an existing table!