I get update errors from time to time, that seem to be coming from our MySQL database. It would be helpful to have a wiki or something similar to understand these errors, and how to troubleshoot them.

For example, I received a "Duplicate entry 'LastCartID' for key 1 (1062d)" when processing one of our profiles that I just enabled retail tracking on. I've emailed support, but would like to hear what others are experiencing, and how they're finding answers.

Views: 70

Reply to This

Replies to This Discussion

Hello Brian,

The error you are seeing sounds like you might have the database setup with the wrong character set / collation or storage engine.

Your MySQL database must support the creation of tables using the InnoDB storage engine.
Your database server must be running MySQL 4.1 or later.

The database character set and collation you use when creating your MySQL database can have a significant impact on Unica NetInsight. The latin1 character set is safe to use as the database character set. The latin1_bin
collation is an example of an acceptable collation.

An example script used for setting up NetInsight on MySQL would be:
mysql -u root -p
mysql> create database NetInsight DEFAULT CHARACTER SET latin1 COLLATE latin1_bin;
mysql> GRANT ALL PRIVILEGES ON NetInsight.* to 'netinsight'@'%' identified by 'netinsight' with grant option;
mysql> GRANT ALL PRIVILEGES ON NetInsight.* to 'netinsight'@'localhost' identified by 'netinsight' with grant option;

If using a character set / collation that isn't Latin1 and case & accent sensitive then you will see errors like you are running into.

All of this documentation is also available on Customer Central

Lee Isensee
Unica Corporation
Hi Lee,

I'm working with support to figure it out. We think the collation is fine. Does NI have a debug option to show the SQL query that's causing the error?

Thanks,
Brian
Starting with NetInsight 7.6 additional debug logging has been added. Further debug logging was added in 8.0.

This can be configured on a profile-by-profile basis.

To turn this on look in the Profile -> Options tab then Main -> Logging.

Thank you,

Lee Isensee
Unica Corporation


Brian Youngblood said:
Hi Lee,

I'm working with support to figure it out. We think the collation is fine. Does NI have a debug option to show the SQL query that's causing the error?

Thanks,
Brian

Reply to Discussion

RSS

© 2018   Created by Wendy Ertter.   Powered by

Badges  |  Report an Issue  |  Terms of Service