Bug #67534 Migration from oracle failed during "Reverse Engineer Source"
Submitted: 9 Nov 2012 9:26 Modified: 13 Nov 2012 3:10
Reporter: xiudan zhou Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S2 (Serious)
Version:mysql-installer-community-5.5.28.3.msi OS:Windows (win7)
Assigned to: CPU Architecture:Any
Tags: migration, Oracle, reverse engineer source

[9 Nov 2012 9:26] xiudan zhou
Description:

Starting...

Connect to source DBMS...

- Connecting...

Connecting to ...

Opening ODBC connection to DSN=Oracle...

Connected

Connect to source DBMS done

Reverse engineer selected schemata....

Connection to  apparently lost, reconnecting...

Connecting to ...

Opening ODBC connection to DSN=Oracle...

Connected

Reverse engineering QE_OLTP from None

- Reverse engineering catalog information

Traceback (most recent call last):

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\db_generic_re_grt.py", line 683, in reverseEngineer

    return GenericReverseEngineering.reverseEngineer(connection, catalog_name, schemata_list, context)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\db_generic_re_grt.py", line 207, in reverseEngineer

    catalog = cls.reverseEngineerCatalog(connection, catalog_name)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\db_generic_re_grt.py", line 358, in reverseEngineerCatalog

    cls.reverseEngineerUserDatatypes(connection, catalog)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\db_generic_re_grt.py", line 331, in reverseEngineerUserDatatypes

    for type_row in cls.get_connection(connection).cursor().getTypeInfo(catalog=catalog.name):  # FIXME: there are duplicated names in this resultset

pyodbc.DataError: ('22003', '[22003] [Oracle][ODBC]Numeric value out of range. (0) (SQLGetData)')

Traceback (most recent call last):

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\workbench\wizard_progress_page_widget.py", line 191, in thread_work

    self.func()

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\migration_schema_selection.py", line 160, in task_reveng

    self.main.plan.migrationSource.reverseEngineer()

  File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.44\modules\migration.py", line 332, in reverseEngineer

    self.state.sourceCatalog = self._rev_eng_module.reverseEngineer(self.connection, self.selectedCatalogName, self.selectedSchemataNames, self.state.applicationData)

SystemError: DataError("('22003', '[22003] [Oracle][ODBC]Numeric value out of range. (0) (SQLGetData)')"): error calling Python module function DbGenericRE.reverseEngineer

ERROR: Reverse engineer selected schemata: DataError("('22003', '[22003] [Oracle][ODBC]Numeric value out of range. (0) (SQLGetData)')"): error calling Python module function DbGenericRE.reverseEngineer

Failed

How to repeat:
Face this error when trying to migrate Oracle to Mysql.
Source Connection: Generic RDBMS", ODBC Data Source
Target Connection: Standard (TCP/IP)

Using the default setting and go "Next". 
Got above errors in "Reverse Engineer Source".

Could you please look into this issue and provide the alternative solutons? Thank you so much!
[9 Nov 2012 9:31] xiudan zhou
Found an similar bug "#66609". 
Does MySQL Workbench support migrating from oracle to mysql?
[9 Nov 2012 11:27] MySQL Verification Team
Thank you for the feedback. Duplicate of http://bugs.mysql.com/bug.php?id=66609 .
[13 Nov 2012 3:10] xiudan zhou
Miguel, Thank you for your quick response. 
Is there any solutions on this issue?
[13 Nov 2012 3:10] xiudan zhou
Miguel, Thank you for your quick response. 
Is there any solutions on this issue?