dbptk-developer icon indicating copy to clipboard operation
dbptk-developer copied to clipboard

MySQL Garbage data in datetime-fields results in too much logging

Open ghost opened this issue 7 years ago • 13 comments

Description:

I'm trying to run dbptk on a very large database (45,5 GB) for archival. When running the tool, it produces hundreds of 50 MB log-files in the directory until the disk is full. The files seem to contain a lot of garbage data, but I'm unsure of this is just the module dumping its memory/objects or if it is actually trying to store the garbage data in the column. I have attached the repeating error message only, since the log files are too large.

The message indicates that it's trying to insert a very long string into a timestamp-field. Strangely, the string does not exist in the "attendance" table in the database, but another table called "assessment log". The error seem to trigger on different fields, mainly DATETIME fields in the database, and there is always a very long string/CLOB which doesn't match the field and doesn't match the data in the database.

This error occurs both with MariaDB and Oracle MySQL. I've imported the SQL script in both just to make sure. Let me know if any of this needs more detail.

Attach the dbptk-app.log.txt file below.

dbptk-error-msg.txt

ghost avatar May 12 '17 09:05 ghost