You are here


When a MySQL table was last touched

In our last customer project we had around 600 Gbyte of data in a MySQL database. Because this database consumed a significant amount of our disk space and backups with the InnoDB backup tool took pretty long we wanted to find out if we could get rid of some of the tables.

This application was growing over the last 10 years and it was not clear if some tables are still in use or not.

But how to find out when a table was touched last? MySQL/InnoDB theoretically could know about but does not report this information.

BLOB's aus der MySQL Datenbank herausklauben

Taxonomy upgrade extras: 

Ein Kunde, welcher mit digitalen Zertifikaten zu tun hat, hatte ein Problem mit einem solchen. Also mussten wir nachforschen, was das Problem war.

Weil das Zertifikat in binärer Form vorliegt, ist es in einem BLOB gespeichert und wir mussten es aus der Datenbank herausklauben um einige Tests damit durchzuführen.

Als erstes kam mir in den Sinn, das Zertifikat mit dem Befehl SELECT INTO OUTFILE zu erhalten. Aber das Verifizierungstool reklamierte und sagte uns, dass das Zertifikat ein falsches Format habe.

Dumping BLOB's from the MySQL database

Taxonomy upgrade extras: 

A customer who is handling digital certificates had a problem with one of those. So we had to investigate.

Because the certificate is in binary form it is stored in a BLOB and we had to extract it from the database to do some verifications.

What first came to my mind was to extract the certificate with the SELECT INTO OUTFILE command. But the verification tool complained and told us that the certificate has a wrong format.

PrimeBase Technologies and FromDual form a Service-Cooperation for MySQL products

From the Cooperation of these two companies arises the biggest independent service provider for MySQL and MariaDB in Europe.

Hamburg, Uster -- February 28, 2011 - The Hamburg based PrimeBase Technologies and the near Zürich located FromDual are forming a Cooperation for MySQL products and services, starting March 1st, 2011.

This Cooperation enables both companies to offer a complete set of services for all MySQL and MariaDB customers.

The customers of both parties now have he possibility to demand a 24x7 support service from their provider.

DOAG Reagionaltreffen in München - 23. März 2011

Wir sind am DOAG Regionaltreffen in München am Mittwoch den 23. März mit unserem Vortrag MySQL Replikation - Scale-Out, Master-Master, Backup (der Vortrag wird in deutscher Sprache gehalten).


FromDual releases new version of its MySQL Performance Monitor

FromDual releases its new version v0.5 of its MySQL Performance Monitor working with Zabbix.

What has changed so far in this release:

FromDual partner

FromDual Partner

FromDual cooperates with the following companies:


MySQL Client Error Codes and Messages 2050 - 2099

2000 - 2049
  • Error: 2050 (CR_FETCH_CANCELED)

    Message: Row retrieval was canceled by mysql_stmt_close() call

  • Error: 2051 (CR_NO_DATA)

    Message: Attempt to read column without prior row fetch


MySQL Server Error Codes and Messages 1700 - 1749

1650 - 1699 2000 - 2049

    Message: GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists


MySQL Server Error Codes and Messages 1650 - 1699

1600 - 1649 1700 - 1749

    Message: The requested server id %d clashes with the slave startup option --replicate-same-server-id


MySQL Server Error Codes and Messages 1500 - 1549

1450 - 1499 1550 - 1599

    Message: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning


MySQL Server Error Codes and Messages 1400 - 1449

1350 - 1399 1450 - 1499

    Message: XAER_OUTSIDE: Some work is done outside global transaction

  • Error: 1401 SQLSTATE: XAE03 (ER_XAER_RMERR)


MySQL Server Error Codes and Messages 1250 - 1299

1200 - 1249 1300 - 1349

MySQL Server Error Codes and Messages 1200 - 1249

1150 - 1199 1250 - 1299

  • Error: 1200 SQLSTATE: HY000 (ER_BAD_SLAVE)
    Message: The server is not configured as slave; fix in config file or with CHANGE MASTER TO

    How does the MySQL error message look like?


MySQL Server Error Codes and Messages 1150 - 1199

1100 - 1149 1200 - 1249

MySQL Server Error Codes and Messages 1000 - 1049

1050 - 1099
  • Error: 1000 SQLSTATE: HY000 (ER_HASHCHK)

    Message: hashchk

  • Error: 1001 SQLSTATE: HY000 (ER_NISAMCHK)

    Message: isamchk


MySQL Error codes and messages

Just a general rule with error messages: Usually they are not as good as they could be. But never the less read them carefully. Most of the time they tell you what you need to know...

And an other wisdom: Errors are really errors and they have to be solved. Warnings are warnings and you should investigate if they appear. Do not ignore both of them unless you have clearly understood what you are doing.

With MySQL:


is often your friend! Further sources to find the problems are:



Subscribe to RSS - mysql