Tools

Error message: Too many keys specified when upgrading WHD with a MySQL database

This article addresses an error that displays when you upgrade Web Help Desk with a MySQL database. Error message: Too many keys specified. Max 32 keys allowed" during a Web Help Desk (WHD) upgrade. MySQL 5.x.

First published date

11/8/2018 1:18 PM

Last published date

6/12/2020 5:33 PM

Overview

When you upgrade Web Help Desk running a MySQL database, the following message displays:

Too many keys specified. Max 32 keys allowed

Product section

Web Help Desk

Cause

Duplicate indexes created in the JOB_TICKET table columns by a previous WHD updates.

MySQL allows a maximum of 64 indexes per table. When the database update attempts to add additional indexes, the total number is increased past 64, triggering the error.

Resolution

Delete the duplicate indexes in the JOB_TICKET table.

The duplicate indexes  have a 2 at the end of their keyname. The following table shows what what the indexes should look like -- in this case using phpMyAdmin or MySQL Workbench. You can use phpMyAdmin or MySQL Workbench to delete the duplicates. 



You can also use the MySQL Command-Line tool and use 
 

show index from JOB_TICKET


After you identify the duplicate index key names, delete the duplicate indexes using
 

 drop index [index keyname] on JOB_TICKET


 Repeat this procedure for each duplicate index.

When all of the duplicate indexes are removed, the database update should continue as normal.

Disclaimer: Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.