Home > Documentation > OraDump to MySQL

OraDump to MySQL FAQ

On this page you can find the most frequently asked questions regarding OraDump-to-MySQL converter. If your question is not answered here, please contact us via Feedback Form

• How to configure MySQL for working with Oracle to MySQL converter?
• How to connect to MySQL over SSH?
• How to resolve error "The program does not support authentication protocol requested by server..."
• How to resolve error "The program cannot read Oracle dump file..."
• How to resolve error "Couldn't parse xml table description..."
• Does Oracle to MySQL converter support automation?
• How to bypass error "Row size is too large. The maximum row size for the used table, not counting BLOBs, is 65535..."?
• How to resolve error "Transferred value is too big. Increase MySQL max packet size..."?
• How to avoid merging Oracle schema with table names?

Error "The program cannot read Oracle dump file..."
Error "Couldn't parse xml table description..."

One reason of these errors is that Oracle dump file is damaged. If dump with the same file name has been migrated already, the error may be caused by using incorrect cache file (.odc). It might be generated by another version of the tool or for another dump file at the same path that was replaced by new one. In order to fix the issue, remove that cache file (.odc) and run the program again. It has the same name as the dump file and is located in the same folder or in user's home folder.

See Cache Files article for more information.