Bug #15741 curly braces in string columns disappear during migration
Submitted: 14 Dec 2005 15:28 Modified: 15 Jan 2006 16:46
Reporter: Frank Wildenhain Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.0.21 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[14 Dec 2005 15:28] Frank Wildenhain
Description:
We have done database migrations from Oracle 8.1.7 to mySQL 4.1.11 with the MySQL Migration Toolkit (Version 1.0.21, for Windows).
The both database servers are running with Linux operating systems.

Now we have discovered that very often (but not always!), in string columns
(Oracle: VARCHAR) the characters '{' and '}' and the characters between this 
both charaters will disappear in the migrated MySQL database tables.

For instance the following string line (type VARCHAR2) in the Oracle table:
<a href="{0}"><b>::</b> alle Aktionen einsehen</a>

appears in the MySQL table after migration (type mediumtext) as follows:
<a href=""><b>::</b> alle Aktionen einsehen</a>

The part "{0}" is missing.

But suprisingly there is an other identical table entry (next line)
<a href="{0}"><b>::</b> alle Aktionen einsehen</a>
which was transferred correctly.

At one table with 108 such fields, after migration in 33 fields the braces were missed.
At an other table with 111 such fields, after migration in 85 fields the braces were missed.

We assume an error in the Migration Toolkit.

Frank Wildenhain

How to repeat:
Try to migrate VARCHAR2 columns from Oracle to MySQL which contain curly braces and numbers between the braces (e.g. string "<a href="{0}"><b>::</b> alle Aktionen einsehen</a>").

Suggested fix:
No idea currently.
[15 Dec 2005 16:46] Valeriy Kravchuk
Thank you for a problem report. Please, send a sample CREATE TABLE ... statement for Oracle and the smallest possible set of data for Oracle table to demonstrate this migration problem.

What version of MySQL are you migrating to?
[16 Jan 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".