In MySQL–land, failovers for redundancy, disaster recovery, or load balancing are performed by master databases and slave databases, the most popular method using binlog replication. There are a couple more methods of replication which aren’t covered here. Also see the MySQL Replication FAQ. The methods are the same, but the formatting of the procedure(s) are less than ideal.
Anyone interested in the architecture of highly scalable and stable infrastructure will enjoy this Presentation by Randy Shoup and Dan Pritchett of Ebay on how they, in their words, “strike a balance between site stability, feature velocity, performance, and cost.”
I noticed sufficient swap/paging on AIX boxes for a Pythian client. (PAGING column in topas result). When I was investigating more about this issue, I found helpful document in Vivek Sharma ‘s blog and metalink note 316533.1.
My colleague Vamsi Chikkam noticed that the Oracle 10.2.0.3 patchset has been released for Linux and Windows 32-bit. The major bugfixes are the same as my original post with a few additions:
Adam Machanic has published on SQLblog.com the 21st edition of Log Buffer, the weekly, human-edited review of database blogs.
I always get a chuckle well not always but often, when I read anything to do with Microsoft vs. “the flavour of the month”. In this case, it looks like the flavour of the month is Oracle. The articles simple imply that SQL Server is more secure than Oracle. They go on to count the number of vulnerabilities identified over the last few years. It’s scary stuff and I’m sure we’re all running out now to ask our architects and DBAs how quickly we can port over to SQL Server.
StorageMojo keeps producing interesting material. This time it’s about FAB (Federated Array of Bricks). I wonder if this will make the same hype as RAC? Dear Reader, what is your perspective?
I faced a problem yesterday. The Oracle listener crashed each time a connection was made. The OS was WINXP SP2. It goes without saying that this was a testing install. The event log showed the following error in SYSTEM log and APPS log. Finally I found the following magic command which fixed the issue after running and restarting the box.
REPORT SCHEMA is quite handy to get growth rate of your database/datafile/tablespace providing RMAN repository is used. I don’t remember what triggered that thought but I see it in my “to blog” list so here it goes.
In my UKOUG 06 presentation on block change tracking internals I assumed that “change tracking state change latch” is, probably, used by DBWR and CTWR to protect access to a buffer area in shared pool. I wanted to verify it and tried to trace this latch.