Failed On Upgrading Timestamp Column To Mysql 5.6 Format ALTER TABLE FORCE returns "duplicate entry ... for key", when there is no duplicate (Doc ID 2060299.1)

Last updated on SEPTEMBER 25, 2015

Applies to:

MySQL Server - Version 5.6 and later
Information in this document applies to any platform.
The issue was due to timezone conversions between server and client, and daylight savings time changes. The server was converting and creating datetime collisions.


 ALTER TABLE tablename FORCE errors out with duplicate key errors, although the data show no duplicates


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms