MySQL Character Set Value Can Cause Installation Errors

If you use MySQL as the MEP Sync database, make sure that the default character set is latin1. A setting of utf8 causes installation errors that look like this:

JDO76614: Deployment encountered SQL Exceptions:
       JDO76609: Got SQLException executing statement "CREATE TABLE PARSTAMPBEAN 
(TIMESTAMP9 BIGINT NULL, PARFILE VARCHAR(256) NOT NULL, CONSTRAINT PK_PARSTAMPBEAN 
PRIMARY KEY (PARFILE)) ENGINE=InnoDB": java.sql.SQLException: Specified key was too 
long; max key length is 767 bytes
       JDO76609: Got SQLException executing statement "CREATE TABLE PARCOUNTERBEAN 
(COUNTER BIGINT NULL, COUNTERNAME VARCHAR(256) NOT NULL, CONSTRAINT PK_PARCOUNTERBEAN 
PRIMARY KEY (COUNTERNAME)) ENGINE=InnoDB": java.sql.SQLException: Specified key was too
long; max key length is 767 bytes

To change the character set, you can restart MySQL with a particular character set, as described in Server Character Set and Collation. On Windows, you can run the MySQL Server Instance Config Wizard to change the character set.