MySQL Bugs: #71350: Receiving "Invalid timestamp literal detected" on database migration

Bug #71350	Receiving "Invalid timestamp literal detected" on database migration
Submitted:	11 Jan 2014 22:40	Modified:	19 Feb 2015 0:13
Reporter:	Jonathan Gordon	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S2 (Serious)
Version:	6.0.8	OS:	Windows (MS Windows Server 2003 SP2)
Assigned to:		CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Results of  exec sp_columns

Attachment: bad-table.csv (text/csv), 509 bytes.

SQL Server Dump File

Attachment: mysql_test.bak.tgz (application/octet-stream, text), 236.26 KiB.

Data copy script

Attachment: copy_migrated_tables.sh (application/octet-stream, text), 1.25 KiB.