Bug #17469 MTK does port empty schema definitions
Submitted: 16 Feb 2006 15:18 Modified: 19 May 2009 12:54
Reporter: Kristian Koehntopp Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S4 (Feature request)
Version:1.0.23 OS:Microsoft Windows (Windows)
Assigned to: CPU Architecture:Any
Triage: Needs Triage: D5 (Feature request)

[16 Feb 2006 15:18] Kristian Koehntopp
Description:
In Oracle, as sooin as a user is created, a schema is being created for that user. Users that have no schema objects on their own or only have schema definitions filled with synonyms are being migrated as empty database definitions to MySQL.

Currently, empty schema definitions must be deleted manually and recreated as user definitions instead.

How to repeat:
Create a user, do not create any schema objects for that user.

See how the user is shown as a schema available for migration. Migrate it.

Watch MTK generating an empty database.

Suggested fix:
Annotate this condition in a migration, or do not migrate that database.

Additionally, think about a way to migrate a grant structure, which is currently not done.
[18 Mar 2009 11:17] Susanne Ebrecht
Many thanks for pointing this out.

Verified as described.
[19 May 2009 12:54] 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 add this feature request anymore.

More informations about MySQL Workbench you will find here:

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