ld-linux.so.2: bad ELF interpreter: No such file or directory

If you see the above error when starting AppDynamics for Databases on a 64-bit Linux machine it is most likely due to missing libraries.

The problem happens because AppDynamics for Databases ships a 32-bit version of java which is used to run the GUI, but sometimes a 64bit Linux OS does not have the necessary 32bit libs to support it.

The simplest solution is to grab the 32-bit libraries by running: yum install glibc

Truncated SQL Queries in Postgres

If you find that your PostgreSQL queries are being truncated then it could be because you are running with a default config which limits SQL String capture to 1024 characters. The maximum size of SQL strings kept in memory is limited to 1024 by default, so you will probably see that the AppDynamics for Databases collected SQL is truncated after 1024 characters.

This can be extended in Postgres 8.4 and above with the config parameter: track_activity_query_size

For example, if you had track_activity_query_size=16384 in your config, then this would mean that query text up to 16k would be collected. There would be an additional memory over-head on the PostgreSQL server if you did up this limit however.

Table 'X....' is marked as crashed and should be repaired

If you see the above error message in the log files, or somewhere in the UI, then it probably means that one of the MySQL repository tables has become corrupted. This sometimes happens on Windows if there was a server crash, unexpected shutdown, or a hard disk problem.

Luckily it's an easy one to fix, you just need to do the following:

1. Open up a cmd.exe
2. cd to <appd4db_home>/mysql/bin
3. Run startClient.bat
4. Run "use dbtuna"
5. Run "repair table statistics;"

Here is a screenshot of what it should look like: