DBAStuff

MySQL Upgrade and Compressed Tables

Recently one of our MySQL servers crashed. Luckily there wasn't any damage but after a support call it was found it was due to a bug with the version we are running. We decided to upgrade to the latest version of 5.5. We have one physical server running 10 small to medium MySQL instances (no replications). Whereas 9 of the upgrades went as planned one didn't (there is always one!).

Mysql Enterprise Backup Restoring a Slave

How do you restore a MEB backup from the slave server for another slave server?

Mysql Enterprise Backup verison 3.9

Mysql Enterprise Backup 3.9 is availble - her are some notes on it:
https://blogs.oracle.com/mysqlenterprisebackup/entry/mysql_enterprise_backup_3_9

MySQL Locking (Version 5.5)

Locking in MySQL seems more complicated to follow than in other database. Monitoring in MySQL is better with the MySQL Enterprise Monitor but for all the command line people, it is more difficult to find out what is locking/blocking.

Upgrading MySQL to 5.5.32 and compressed tables

Recently I was tasked with upgrade some MySQL instances from 5.5.16 to 5.5.32. The task seemed easy enough but when I started the process on one of the larger databases on the server (just under 1TB), it is made up of a lot smaller tables and most over 90% are 'myisam'. I ran into issues when I ran mysql_upgrade.

error : Table upgrade required. Please do "REPAIR TABLE `<name>`" or dump/reload to fix it!

Oracle - Row duplicates in a table with a PK loaded by sql*loader

I had an interesting problem today. One of the developers told me a nightly job had stopped with an error. I check the usual things like has anything changed and was told no. The error was sent to me and was the following:
SQL*Loader-926: OCI error while executing delete/truncate (due to REPLACE/TRUNCATE keyword) for table REPORT_TEMP
ORA-01502: index 'PK_REPORT_TEMP' or partition of such index is in unusable state

MySQL Enterprise Backup (MEB) Compress Option

I have used compression tools before and was interested to understand a little more about MEB's use of compression. Jumping straight in, here are a couple of points to consider:

the backup compression feature only applies to InnoDB tables.
when InnoDB tablespace files are compressed during backup, they receive the extension .ibz rather than the usual .ibd extension.
you can only use the --compress option for full backups, not for incremental backups.