I found the table that was causing the error.
The create script for this table was edited with “vi” and the foreign key name actually has a “^_” (ie. control underscore) in the constraint name. (This was a typo and will be removed…) However, looks like MySQL doesn’t really care if there are control characters in table, column, constraint names…
I reverse engineered the database with TOAD and the control characters are not displayed visually but the next character after the control character is missing. However, the reverse engineer works. When TOAD created the XML for this table, it leaves a blank space in the XML where the “^_” character is located (when viewing in IE 7)
So, looks like a control character is causing the problem.
We are removing the “control character” typo from our constraint names to fix this problem. Not sure if you want to update TOAD to recognize control characters or not.
Thanks for your help.