The Oracle gateway for ODBC provides an almost seamless data integration between Oracle and other RDBMS. I won't argue about its performance, limits, or relevance. It serves a few purposes; set it up and you'll be able, for example, to create database links between Oracle and MySQL. After all, wouldn't it be nice if you could run some of the following SQL statements? "select o.col1, m.col1 from oracle_tabo, mysql_tab@mysql m where o.col1=m.col1;" "insert into oracle_tab (select * from mysql_tab@mysql);"This post is intended to share, the same way Karun did it for SQL Server last year, some tips related to the setup of the Oracle Gateway for ODBC with MySQL Connector ODBC on Linux.PrerequisitesI've installed all the configuration on my laptop to test it. It's running Ubuntu Intrepid Ibex 32bits, but I won't dig into the challenge of installing the MySQL Connector ODBC 5.1 on it. All I'll tell you is that, if  []

If you are using InnoDB Hot Backup utility and the innobackup.pl wrapper script, be very careful if you are not running backups under the system "mysql" user. There is a bug which causes InnoDB Hot Backup to sometimes report a successful backup when it actually failed.

Slaves can be used for:Horizontal read scalability -- take the load off a master database by spreading reads to a replicated slave.Disaster recovery -- some disasters, such as a hardware failure, can be solved by having a slave ready to propagate to a master. This technique also works to make offline changes to a master/slave pair without having database downtime (see below).Consistent Backups -- without disrupting production usage, a slave can be used to ta

It recently came up that it would be helpful if we had a cheat sheet to find out the machine names for any given UNIX. I knew these off the top of my head but it would be great if people added more as comments. HP/HP-UX: /bin/uname -i IBM/AIX: /bin/uname -m SGI/IRIX: /sbin/sysinfo -s Sun/Solaris: /usr/ucb/hostid

The "sla" in mysqlsla stands for "statement log analyzer". This does a much better job than mysqldumpslow of analyzing your slow query log. In fact, you can sort by many different parameters -- by sheer number of times the query shows up in the slow query log, by the total or average query time, by the lock time, etc. This is really good for weeding out pesky entries in the slow query log that you do not care about. In this case, our client was using log-queries-not-using-indexes, so there was a lot of junk in the slow query log as well (for instance, every time a mysqldump backup was run, the slow query log got plenty of entries). In this case, I'm using --slow to read the slow query log at the filename specified, --flat to flatten all the text to lowercase (basically case-insensitive matching) and --sort at to sort by "average time".> ./mysqlsla --flat --slow ~mysql/var/mysql-slow.log  []