Error fixed
Practical guides to moving data off old systems and into the cloud: step by step migrations, errors and how to fix them, legacy file formats, and SQL to dbt. Every guide is tested on real databases and cites the official documentation.
All · Migration guide · Tip · File rescue · SQL to dbt · Error fixed · Comparison
- Error fixedNovember 14, 2026
mysqldump Error 2013: Lost Connection During QueryWhy mysqldump fails with error 2013 halfway through a table, reproduced on MySQL 8.4, and the fixes: timeouts, dumping to a file, and finding killers.
- Error fixedNovember 7, 2026
ORA-01722: invalid number, During a MigrationORA-01722 means a string failed to convert to NUMBER. Find bad rows with VALIDATE_CONVERSION, then convert explicitly with a format and NLS setting.
- Error fixedOctober 31, 2026
invalid byte sequence for encoding "UTF8": 0xa0, 0x92, 0xffThe file is Windows-1252, Latin-1 or UTF-16, not UTF-8. Load it with COPY ... ENCODING 'WIN1252', or convert it first with iconv -f CP1252 -t UTF-8.
- Error fixedOctober 16, 2026
invalid byte sequence for encoding "UTF8": 0x00PostgreSQL text columns cannot hold a NUL byte. Strip 0x00 with tr or REPLACE(col, CHAR(0), '') before loading, or use bytea for binary data.