Too many tables; MySQL can only use 61 tables in a join

Good day all.

I did a RT upgrade from 3.8.4 to 4.0.7 over the weekend.

We did a POC to make sure everything works, and all seemed fine. No
problems we could see. After the upgrade we see this error.

Nov 19 12:13:44 violator RT: DBD::mysql::st execute failed: Too many
tables; MySQL can only use 61 tables in a join at
/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm line
587. (/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm:587)

Attached is an example from the rt.log file.

Any help would be appreciated.

Regards
Henti

rt.err (19.9 KB)

Hi,

It is a REST request from rt CLI or other app. You probably will have to use
some workaround out of RT. Depends on what is on the other side.On Mon, Nov 19, 2012 at 6:21 PM, Henti Smith henti@geekware.co.za wrote:

Good day all.

I did a RT upgrade from 3.8.4 to 4.0.7 over the weekend.

We did a POC to make sure everything works, and all seemed fine. No
problems we could see. After the upgrade we see this error.

Nov 19 12:13:44 violator RT: DBD::mysql::st execute failed: Too many
tables; MySQL can only use 61 tables in a join at
/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm line
587. (/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm:587)

Attached is an example from the rt.log file.

Any help would be appreciated.

Regards
Henti


We’re hiring! http://bestpractical.com/jobs

Best regards, Ruslan.

Good day all.

I did a RT upgrade from 3.8.4 to 4.0.7 over the weekend.

We did a POC to make sure everything works, and all seemed fine. No
problems we could see. After the upgrade we see this error.

Nov 19 12:13:44 violator RT: DBD::mysql::st execute failed: Too many
tables; MySQL can only use 61 tables in a join at
/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm line
587. (/usr/local/lib/perl5/site_perl/5.8.9/DBIx/SearchBuilder/Handle.pm:587)

Attached is an example from the rt.log file.

Any help would be appreciated.

DBIx::SearchBuilder has an interesting way of caculating joins that can
negatively affect MySQL. Sounds like you’ve hit the same feature in
DBIx::SearchBuilder as leads to this [1] bug.

The patch on that bug might be worth a shot … on a test instance of
course :slight_smile:

Cheers, Jeff.

1: Login