Bug #83833 Support for DB2 migration to MySQL
Submitted: 15 Nov 2016 17:54 Modified: 31 Jan 2018 18:05
Reporter: Manuel Morales Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S4 (Feature request)
Version:6.3.8 OS:Windows (7)
Assigned to: CPU Architecture:Any
Tags: db2, migrate, migration, workbench

[15 Nov 2016 17:54] Manuel Morales
Description:

Log

- First pass of table reverse engineering for schema COMPIERE completed!

Reverse engineering views from XXXX
Generic reverseEngineerViews: Cannot reverse engineer view "XXXXX"
.
.
.

- Reverse engineering of views for schema XXXX completed!
Reverse engineering routines from "XXXX"
Generic reverseEngineerProcedures: Cannot reverse engineer procedure "XXXXX"
.
.
.
- Reverse engineering of routines for schema XXXX completed!
Reverse engineering triggers from XXXX
- Reverse engineering of triggers for schema XXXX completed!
Reverse engineering foreign keys for tables in schema XXXX
Traceback (most recent call last):
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\db_generic_re_grt.py", line 743, in reverseEngineer
    return GenericReverseEngineering.reverseEngineer(connection, catalog_name, schemata_list, context)
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\db_generic_re_grt.py", line 347, in reverseEngineer
    cls.reverseEngineerTables(connection, schema)
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\db_generic_re_grt.py", line 434, in reverseEngineerTables
    cls.reverseEngineerTableFKs(connection, table)
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\db_generic_re_grt.py", line 622, in reverseEngineerTableFKs
    process_fk(catalog, table, fk_name, fk_columns)
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\db_generic_re_grt.py", line 580, in process_fk
    foreign_key.referencedTable = find_object_with_name(referenced_schema.tables, fk_rows[0].pktable_name) if fk_rows[0].pktable_name else table
AttributeError: 'NoneType' object has no attribute 'tables'

Traceback (most recent call last):
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\workbench\wizard_progress_page_widget.py", line 192, in thread_work
    self.func()
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\migration_schema_selection.py", line 175, in task_reveng
    self.main.plan.migrationSource.reverseEngineer()
  File "C:\Users\XXXX\Desktop\MySQL Workbench 6.3.8 CE (winx64)\modules\migration.py", line 369, in reverseEngineer
    self.state.sourceCatalog = self._rev_eng_module.reverseEngineer(self.connection, self.selectedCatalogName, self.selectedSchemataNames, self.state.applicationData)
SystemError: AttributeError("'NoneType' object has no attribute 'tables'"): error calling Python module function DbGenericRE.reverseEngineer
ERROR: Reverse engineer selected schemas: AttributeError("'NoneType' object has no attribute 'tables'"): error calling Python module function DbGenericRE.reverseEngineer
Failed

How to repeat:
1.- Database-> Migration Wizard...
2.- Press buttom Start Migration
3.- Select Source RDBMS Connection Parameters -> Database System: Generic RDBMS
4.- Select Connection Method: ODBC Data Source
5.- DNS iSeries Access ODBC Driver
6.- Next
7.- Select Target RDBMS Connection Parameters: Valid conection to MySQL Database
8.- Next
9.- Fetch Schemas List
10.- Next
11.- Schemas Selection
11.1 Only one schema: Catalog.Schema.Table->Catalog.Table
12.-Next
13.- Reverse Enginner Source -> Present the issue reported
[31 Jan 2018 18:05] MySQL Verification Team
Thank you for the feature request.
This is duplicate of Bug #71878, please see Bug #71878

Thanks,
Umesh