Bug #40235 Migration Sybase AES 12.x around MySlq 5.x identifier column is too long
Submitted: 22 Oct 2008 9:20 Modified: 19 Oct 2009 13:59
Reporter: Franck Andriano Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.1.13, 1.1.15, 1.1.16 OS:Microsoft Windows (XP pro)
Assigned to: CPU Architecture:Any
Tags: CHECKED, column, Data Bulk Transfer, identifier, is too long
Triage: Triaged: D2 (Serious) / R3 (Medium) / E3 (Medium)

[22 Oct 2008 9:20] Franck Andriano
Description:
Hi!

The MySQL migration Toolkit doesn't migrate data when the identifier (the name) of the column is too long... The maximum length supported by the toolkit is 28! 

2. Data Bulk Transfer
---------------------

      `EFOPCVM_EPF_dbo`.`CARACT_OPCVM`
      --------------------------------
          The following error occured while transfering data from CARACT_OPCVM
            The identifier that starts with '"SOUSCRIPTION_ULTERIEUR_DEVIS' is too long. Maximum length is 28.

End of report.
--------------------------------------------------------------------------------

Correct name of column was 'SOUSCRIPTION_ULTERIEUR_DEVISE'

/Franck 

How to repeat:
Migrate table with a name of column superior at length 28.
[11 Dec 2008 8:46] Valeriy Kravchuk
Please, try to repeat with a newer version, 1.1.15, and inform about the results.
[11 Dec 2008 16:08] Franck Andriano
Same error in Migration Toolkit version 1.1.15 :

      `EFOPCVM_EPF_dbo`.`CARACT_OPCVM`
      --------------------------------
          The following error occured while transfering data from CARACT_OPCVM
            The identifier that starts with '"SOUSCRIPTION_ULTERIEUR_DEVIS' is too long. Maximum length is 28.
[6 Feb 2009 11:58] Susanne Ebrecht
Many thanks for writing a bug report. I can't repeat this with MySQL Migration Tool 1.1.16.

I used MySQL server 5.1.

Maybe you are using an older MySQL server. Consider, Migration Toolkit only support MySQL 5.0 and 5.1.
[6 Feb 2009 15:31] Franck Andriano
Dear Susanne,

Be sorry, we try with last version MySQL Migration Tool 1.1.16 like you wrote us, with same result we send you below.

I confirm using Mysql 5.1

regards,

--------------------------------------------------------------------------------

-- MySQL Migration Toolkit Report                                             --

--                                                                            --

-- Title:   Summary Of The Migration Process                                  --

-- Date:    2009-02-06 16:22                                                  --

--------------------------------------------------------------------------------

 

 

1. Schema Migration

-------------------

 

  Number of migrated schemata: 1

 

  Schema Name:            EFOPCVM_EPF_dbo

  - Tables:               1

  - Views:                0

  - Routines:             0

  - Routine Groups:       0

  - Synonyms:             0

  - Structured Types:     0

  - Sequences:            0

 

  Details:

 

  - Tables

      `EFOPCVM_EPF_dbo`.`CARACT_OPCVM`

      --------------------------------

  - Views

  - Routines

  - Routine Groups

  - Synonyms

  - Structured Types

  - Sequences

 

 

2. Data Bulk Transfer

---------------------

 

      `EFOPCVM_EPF_dbo`.`CARACT_OPCVM`

      --------------------------------

          The following error occured while transfering data from CARACT_OPCVM

            The identifier that starts with '"SOUSCRIPTION_ULTERIEUR_DEVIS' is too long. Maximum length is 28.

            

 

 

End of report.

--------------------------------------------------------------------------------
[2 Apr 2009 7:00] Susanne Ebrecht
Many thanks for writing a bug report.

Verfied as described.

The workaround here is to change identifiers manually during migration.
[19 Oct 2009 13:59] Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't fix this anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/