Embedded MySQL server troubleshooting
During the License Statistics evaluation, you may have License Statistics temporarily running on a machine that does not meet the minimum system requirements. In such cases where there is not enough memory on the machine hosting the License Statistics installation, the MySQL server may not start properly the first time you start License Statistics, which will produce warnings similar to the following in the xflicstat.log file:
...
This setting may be changed only for testing purposes (for example, during evaluation). The proper solution is to install License Statistics on a machine that meets system requirements. Note that lowering the innodb_buffer_pool_size setting may decrease the performance of License Statistics, causing it to run slower.
Lost connection to MySQL server during query
When using License Statistics with an external MySQL database, you may see the following error message:
...
The above message indicates that your MySQL server settings should be adjusted. To resolve this issue, follow the configuration instructions described in Using an external MySQL database. You can also find more information about this problem in the MySQL reference manual.
"Specified key was too long; max key length is 767 bytes" error
When using License Statistics, you may see the following error message in the License Statistics log file, licstat.log:
Specified key was too long; max key length is 767 bytes.
This problem may be related to the fact that the MySQL database by default uses the UTF-8 character set and collation.
To resolve this issue, you should upgrade License Statistics that uses an embedded MySQL database to License Statistics using an external MySQL database. If this does not resolve the problem, you can try upgrading License Statistics from an external to embedded database.