MySQL Forums - MySQL Workbench - Database Migration

Data migration error (Reverse engineering process) (1 reply)

anjum jamal — Fri, 03 May 2013 15:51:06 +0000

I am geeting error when iporting the ms sql server 2005 data in mysql.
The error is :
tarting...

Connect to source DBMS...

- Connecting...

Connect to source DBMS done

Reverse engineer selected schemata....

Reverse engineering dbo, VSM from VSM

- Reverse engineering catalog information

- Reverse engineering User Data Types...

- Preparing...

- Gathered stats for dbo

- Gathered stats for VSM

Reverse engineering 145 tables from dbo

- Retrieving table dbo.Delhi_client20a...

- Retrieving table dbo.gridih_associates_15march...

- Retrieving table dbo.Delhi_client20ab...

- Retrieving table dbo.associate2b...

- Retrieving table dbo.gridih_associates_15marcha...

- Retrieving table dbo.gridihtrust_15march...

- Retrieving table dbo.gridihtrust_15marcha...

- Retrieving table dbo.Associate2...

- Retrieving table dbo.DELHI_MEMBER20a...

- Retrieving table dbo.gridih_ltd_15marcha...

- Retrieving table dbo.Gridih19march_assco...

- Retrieving table dbo.Delhi_associate20a...

- Retrieving table dbo.RATES...

- Retrieving table dbo.Relation...

- Retrieving table dbo.Gridih19march_trust...

- Retrieving table dbo.Delhi_associate20ab...

- Retrieving table dbo.Delhi_client20abc...

- Retrieving table dbo.Delhi_member_19abcd...

- Retrieving table dbo.branch1...

- Retrieving table dbo.'TRUST CUSTOMER$'...

Traceback (most recent call last):

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 384, in reverseEngineer

reverseEngineerTables(connection, schema)

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 557, in reverseEngineerTables

reverseEngineerTablePK(connection, table)

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 687, in reverseEngineerTablePK

pk_col_names = [ row[3] for row in execute_query(connection, query) ]

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 62, in execute_query

return get_connection(connection_object).cursor().execute(query, *args, **kwargs)

pyodbc.ProgrammingError: ('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")

Traceback (most recent call last):

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\workbench\wizard_progress_page_widget.py", line 192, in thread_work

self.func()

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\migration_schema_selection.py", line 160, in task_reveng

self.main.plan.migrationSource.reverseEngineer()

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\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: ProgrammingError("('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.reverseEngineer

ERROR: Reverse engineer selected schemata: ProgrammingError("('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.reverseEngineer

Failed

Could anyone help.

MSSQL2008 -> MySQL via migration wizard - space in database name (4 replies)

patrick king — Thu, 09 May 2013 05:23:38 +0000

Trying to migrate an existing MsSQL2008 to MySQL 5.5
I am able to connect to both servers.

I get to the 'Reverse Engineer Source', and get an error message.

Here is the important part of the error message:

...
Reverse engineer selected schemata....
Reverse engineering dbo from Project Connect
- Reverse engineering catalog information
- Reverse engineering User Data Types...
- Preparing...

...

pyodbc.Error: ('08004', "[08004] [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'Project' does not exist. Make sure that the name is entered correctly. (911) (SQLExecDirectW)")

...

As you can see, the database has a space in the name, which the migration wizard doesn't agree with.

Is there any workaround for this issue? I would really like to work with this database in mysql workbench.

Thank you

Patrick

Migrating DUMP file of 4.2 into latest version (2 replies)

Petr Hodbod — Mon, 01 Apr 2013 16:31:45 +0000

Hi guys
I have found some posting related to that but this is problem in my case to follow upgrade step by step. I have DUMP file from old version.
Is there any conversion rutine to prepare it for new version?
I have more then 4MB file and it will be problem to rewrite it by hand.

Thanks for any hint

Petr

about MySQL migration etc (1 reply)

Stephen Liu — Thu, 14 Mar 2013 17:09:18 +0000

Hi all

1)
OS Ubuntu 12.04 desktop 64bit
2)
OS Fedora 18 desktop 64bit

migrating MySQL from 1) to 2) same version

I found many suggestions on Internet re migrating database and unable to ascertain the easiest way on its migration. Please advise. TIA

Besides on running following commands;

mysql> SHOW databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| test |
| aaa |
| bbb etc |
+--------------------+

mysql> USE aaa;

mysql> SHOW tables;
+-----------------------+
| Tables_in_aaa |
+-----------------------+
| 111 |
| 222 |
| 333 |
| 444 etc |
+-----------------------+

mysql> SELECT * FROM aaa;
+----+-------------+---------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+--------------+-------------+----------------+-------------+---------------+------------------

Whether above indicates that there is no data/entry on the database?

mysql> SHOW columns from 222;
+-----------------------+---------------------+------+-----+---------------------+----------------+
| Field | Type | Null | Key | Default | Extra |
+-----------------------+---------------------+------+-----+---------------------+----------------+
| ID | bigint(20) unsigned | NO | PRI | NULL | auto_increment |
| xxx | bigint(20) unsigned | NO | MUL | 0 | |
| yyy | datetime | NO | | 0000-00-00 00:00:00 | |
| zzz etc | datetime | NO | | 0000-00-00 00:00:00 | |
+-----------------------+---------------------+------+-----+---------------------+----------------+

What command shall I run to display the columns and their content in readable form?

Thanks

SL

making a backup of my mySQL database (1 reply)

Craig Mackinlay — Sat, 20 Apr 2013 06:28:34 +0000

Hi there- I have downloaded MySQl installer and it included my sql for excel. I have an excel database with about 7-10 worksheets which will be separate tables in the database. I setup a connection and used 'create database' to create a database, I have used mysql for excel and it imported the tables fine.

However now I need to create a copy of the database to send to someone. How can I do this? Is it mysqldump? Or is there a simple way to do this
thanks Craig

Postgresql -> MySql: Empty Schema Selection (4 replies)

Daniel Roß — Tue, 23 Apr 2013 15:04:36 +0000

Dear all,

Iam trying to migrate my postgresql database to my mysql database.For that Iam using MySQL Workbench. After the source and target selection he didn't fetch a schemata list. On the "Schemata Selection" Page the List is empty.

What could be the reason for that? I didnt see any option could influence that.

Questions about migrating from MySQL 4.1 to latest community version on Windows XP (1 reply)

Purvez Desai — Tue, 05 Mar 2013 00:31:41 +0000

Hi

I had an old XP m/c that had Ver4.1 on it. I had to rebuild this recently and hence lost the MySQL installation. I still have the data. My questions are:

1. If I install the latest community version and point it at the old data will it automatically be able to read the data? I don't have any data dumps.

2. If it won't automatically read the data then is there anyway of upgrading the data?

Thanks in advance

Purvez

P.S. I tried this question in the Newbie forum but no takers. Hopefully get some response here. Thanks

MySQL Workbench Migration Invalid Column Name for some tables (4 replies)

Terence Silonda — Mon, 25 Mar 2013 13:47:57 +0000

I've been trying to Migrate from SQL Server to MySQL.

I've only partly succeeded. While some tables were created and data copied, some were only created but the data not copied.

I checked the logs, and for those tables the error was below, this was for each column in a particular table.

2207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'OrderID'.

Am I missing something?

Please note, some of the tables hold as many as 40,000+ rows, some 6 or so.

Any help will be appreciated.

Migrating from 5.1.44 (1 reply)

Fortunato Marrelli — Thu, 21 Feb 2013 04:39:11 +0000

Migrating from 5.1.44 to 5.6.10 same query returns null. Maybe some timeout expires?

Migrating from Oracle to MySQL using WorkBench Migration Tool (no replies)

J M — Wed, 13 Feb 2013 16:38:36 +0000

Hi,

I am currently migrating from oracle to mysql and i am going to use the migration tool in workbench to help me with the procedure, i have entered my source connection details as follows

Database System: Generic RDBMS
Connection Method: ODBC(Manually Entered parameters)
Driver:Oracle RDB driver
Hostname: 127.0.0.1 Port:1521
Username: user
Database:db

But i seem to be receiving the following error when testing the connection.

ERROR: Error during Connect to source DBMS: Error("('HY093', '[HY093] [Oracle][ODBC]
[Rdb]Invalid parameter number. (-2000) (SQLDriverConnect);

[HY093] [Oracle][ODBC][Rdb]Invalid parameter number. (-2000)')"):
error calling Python module function DbGenericRE.connect

I am struggling to figure out what parameter is wrong, any one have an idea what could be causing this?

Thanks.

Oracle to Mysql migration (1 reply)

Douglas Campbell — Wed, 13 Feb 2013 16:41:01 +0000

Hi, This problem has been reported numerous times and when asked if its a bug users have been ignored. When asked does the Migration tool support Oracle again no answer. The person who has dealt most with these problems is developer Sergio but I would like to know what the solution is to the problem below even if its a bug that will be fixed in the next release.

Starting...

Connect to source DBMS...

- Connecting...

Connecting to ...

Opening ODBC connection to DSN=C5LOCAL...

Connected

Connect to source DBMS done

Reverse engineer selected schemata....

Connection to apparently lost, reconnecting...

Connecting to ...

Opening ODBC connection to DSN=C5LOCAL...

Connected

Reverse engineering C5NW from None

- Reverse engineering catalog information

Traceback (most recent call last):

File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.46\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.46\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.46\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.46\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.46\workbench\wizard_progress_page_widget.py", line 192, in thread_work

self.func()

File "C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.46\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.46\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

MySQL workbench crashing on migration (no replies)

David Porter — Mon, 11 Feb 2013 04:05:25 +0000

I'm trying to migrate data directly into MySQL as an initial phase towards moving to a sane database. However, in setting up the migration wizard, it keeps crashing when it reaches the 'reverse engineer selected schema'.

I am connecting to the source database via ODBC. The source database is Intuit's Quickbase and I am connecting via QuNect ODBC.

Can anyone point me in the direction of a workaround or fix for this?

Log-dump is as follows:
Problem signature:
Problem Event Name: APPCRASH
Application Name: MySQLWorkbench.exe
Application Version: 5.2.46.10385
Application Timestamp: 51088952
Fault Module Name: grt.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 51087ab8
Exception Code: c0000005
Exception Offset: 00003cd5
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

cannot select checkbox of column on a foreign key (no replies)

pedro dinis — Fri, 01 Feb 2013 15:08:05 +0000

cannot select checkbox of column on a foreign key

i have two tables

one its called users the other clients

i have created a foreign key on clients and referenced table users

but on the chekbox does not let select the column uid

is this a bug ?

Error occured when "reverse engineer selected schemata" for PostgreSQL 9.2.2 (4 replies)

Xi Bai — Tue, 12 Feb 2013 18:53:40 +0000

Hi,

When I tried migrating data stored on PostgreSQL with the version 9.2.2 to MySQL, I got the following error at the step of "Reverse engineer selected schemata" for both 5.2.45 and 5.2.44 on Mac OS 10.6.8:

Starting...
Connect to source DBMS...
- Connecting...
Connecting to ...
Opening ODBC connection to DSN=LocalPostgreSQLDB...
Connected
Connect to source DBMS done
Reverse engineer selected schemata....
Reverse engineering public from cssmetaselector
- Reverse engineering catalog information
- Preparing...
- Gathered stats for public
Reverse engineering tables from public
- Retrieving table public.static...
Traceback (most recent call last):
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/db_postgresql_re_grt.py", line 335, in reverseEngineer
return PostgresqlReverseEngineering.reverseEngineer(connection, catalog_name, schemata_list, context)
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/db_generic_re_grt.py", line 257, in reverseEngineer
cls.reverseEngineerTables(connection, schema)
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/db_generic_re_grt.py", line 393, in reverseEngineerTables
cls.reverseEngineerTableIndices(connection, table)
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/db_postgresql_re_grt.py", line 114, in reverseEngineerTableIndices
index_rows = cls.execute_query(connection, all_indices_query).fetchall()
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/db_generic_re_grt.py", line 56, in execute_query
return cls.get_connection(connection_object).cursor().execute(query, *args, **kwargs)
pyodbc.Error: ('ODBC data type 1111 is not supported. Cannot read column indkey.', 'HY000')

Traceback (most recent call last):
File "/Applications/MySQLWorkbench.app/Contents/Resources/libraries/workbench/wizard_progress_page_widget.py", line 191, in thread_work
self.func()
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/migration_schema_selection.py", line 160, in task_reveng
self.main.plan.migrationSource.reverseEngineer()
File "/Applications/MySQLWorkbench.app/Contents/PlugIns/migration.py", line 332, in reverseEngineer
self.state.sourceCatalog = self._rev_eng_module.reverseEngineer(self.connection, self.selectedCatalogName, self.selectedSchemataNames, self.state.applicationData)
SystemError: Error("('ODBC data type 1111 is not supported. Cannot read column indkey.', 'HY000')"): error calling Python module function DbPostgresqlRE.reverseEngineer
ERROR: Reverse engineer selected schemata: Error("('ODBC data type 1111 is not supported. Cannot read column indkey.', 'HY000')"): error calling Python module function DbPostgresqlRE.reverseEngineer
Failed

The error above does not give my any clue. It'll be most appreciated if someone can help me with this.

All the best

Xi

MySQL Workbench 5.2.45: Upgrade from MySQL Administrator, MySQL Query Browser (no replies)

Edwin Desouza — Thu, 03 Jan 2013 00:04:21 +0000

MySQL Workbench 5.2.45: Upgrade from MySQL Administrator, MySQL Query Browser
http://mysqlworkbench.org/2012/12/mysql-workbench-5-2-45-ga-released/

WB 5.2 includes:
- Model (upgrade from DBDesigner)
- Query (upgrade from MySQL Query Browser)
- Admin (upgrade from MySQL Administrator)
- Migration (upgrade from MySQL Migration Toolkit)
- SSH-Tunnel (new)

WB Downloads: http://dev.mysql.com/downloads/workbench/
WB Forums: http://forums.mysql.com/index.php?151
WB Blogs: http://mysqlworkbench.org/x.php?151
WB Blogs: http://mysqlworkbench.org/

Newbie needs help transferring data (2 replies)

James Youngblood — Fri, 04 Jan 2013 02:45:11 +0000

I am working on a java program for school that has a backend MySQL database. I was pro vided with a template to use for database called reqistrar.sql that I copied over to the bin folder for MySQL (C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin).
My question is, once that I have added data into my program, is this template what I need to copy with my program, or is there something else that I have to do to transfer the data for my program so that the grader can see that I have performed the tests required to prove my program works?

Bulk Data Migration is getting hanged out - Please help... (no replies)

Ashish Vijaywargiya — Sat, 29 Dec 2012 11:15:27 +0000

Hello,

I have downloaded MySql Workbench 5.2.44 and installed it on Ubuntu 10.04. I am trying to perform following operations although things are getting hanged out at last step 'Bulk Data Transfer'.

1) Mysql to Mysql db transfer.

2) Postgresql to Mysql db transfer.

I have also tried performing this operation from terminal but I am not seeing any error details on console that could help me in get going.

ashish@ashish-laptop:~/odb/testing1104$ mysql-workbench
Initializing AdvancedSidebar factory method
Initializing mforms factory
Creating WBOptions
Ready.

** Message: overview.home built-in command is being overwritten

I am trying to migrate around 850 tables in both the migration but could't get success.

Well I am able to establish connection in first and second case. In second case I have established connection with the help of odbc with the postgres source database.

Just so you know that if I am migrating small database lets say in both the cases mentioned above if db contains less tables lets say 1 table then both the migrations are working fine for me.

Am I missing some additional configuration here? that is needed when we are trying to perform migration of such a huge db.

Please let us know if additional information is needed here.

--
Kind Regards
Ashish Vijaywargiya

Problems starting workbench in Fedora 17 (no replies)

Terry Khatri — Mon, 24 Dec 2012 23:38:45 +0000

Hi,
I have installed mysql-workbench through yum in Fedora 17 64bit when start it I get the following error :

/bin/catchsegv: line 58: //libexec/mysql-workbench-bin: No such file or directory

The routine for line 58 in /bin/catchsegv is as under

 # Redirect stderr to avoid termination message from shell.
(exec 3>&2 2>/dev/null
LD_PRELOAD=${LD_PRELOAD:+${LD_PRELOAD}:}/\$LIB/libSegFault.so \
SEGFAULT_USE_ALTSTACK=1 \
SEGFAULT_OUTPUT_NAME=$segv_output \
"$prog" ${1+"$@"} 2>&3 3>&-)
exval=$?

The file mysql-workbench-bin is located under /usr/libexec instead of //libexec

Can someone please help me fix it, I have very important assignment to do using workbench.

Thanks for your help.
Regards
Terry

Error - Migrating from Oracle to MySql (Workbench 5.2) (no replies)

Nivaldo Ribeiro — Sat, 22 Dec 2012 18:23:40 +0000

Hi everyone,

I'm trying to migrate a very small database from oracle to MySQL, but I have got a error, something with reverseEngineer, please see log below.

Any Help? Thanks!

Starting...

Connect to source DBMS...

- Connecting...

Connecting to ...

Opening ODBC connection to DSN=Oracle_XE...

Connected

Connect to source DBMS done

Reverse engineer selected schemata....

Connection to apparently lost, reconnecting...

Connecting to ...

Opening ODBC connection to DSN=Oracle_XE...

Connected

Reverse engineering PREVISAO 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

mysql-workbench crashing (no replies)

Anoosh Ravan — Thu, 20 Dec 2012 00:22:14 +0000

Hello All,

I have just installed mysql-workbench on openSUSE 12.2 from standard repos. It crashes everytime at boot up. This the message:

Code:
anooshr@linux-ri7f:~> mysql-workbench --verbose
** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb.model.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/db.mysql.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb.mysql.import.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/text_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/code_utils_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb_doclib_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/db.mysql.query.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/db.mysql.sqlparser.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/tools.grt.lua' (lua)
** Message: Initialized Lua module /usr/lib64/mysql-workbench/modules/tools.grt.lua (WbTools)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/table_utils_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/sqlide_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb_utils_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/db.mysql.sqlide.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb_admin_grt.py' (python)
Warning! Can't use connect with timeout in paramiko 1.7.7.1 (George)
/bin/sh: ifconfig: command not found
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/catalog_utils.grt.lua' (lua)
** Message: Initialized Lua module /usr/lib64/mysql-workbench/modules/catalog_utils.grt.lua (WbUtils)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/forms.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/wb_dev_utils_grt.py' (python)
** Message: Trying to load module '/usr/lib64/mysql-workbench/modules/dbutils.grt.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/wb.printing.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/wb.model.editors.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/db.checks.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/db.mysql.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/db.mysql.editors.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so' (cpp)
** Message: Trying to load module '/usr/lib64/mysql-workbench/plugins/wb.model.snippets.wbp.so' (cpp)
Ready.

*** Segmentation fault
Register dump:

RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000003071838 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R8 : 0000000003071860 R9 : 0000000000000000
R10: 00007fffc086e7b0 R11: 00007f40a60941e0 R12: 0000000000000002
R13: 00007fffc086ecb0 R14: 00007f40a9d52790 R15: 00007fffc086ec01
RSP: 00007fffc086ea08

RIP: 00007f40a60941e0 EFLAGS: 00010202

CS: 0033 FS: 0000 GS: 0000

Trap: 0000000e Error: 00000004 OldMask: 00000000 CR2: 0000000c

FPUCW: 0000037f FPUSW: 00000020 TAG: 00007f40
RIP: a9437fff RDP: c086d5d8

ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000
ST(2) 0000 0000000000000000 ST(3) 0000 0000000000000000
ST(4) 0000 0000000000000000 ST(5) 0000 0000000000000000
ST(6) ffff 8000000000000000 ST(7) 0000 0000000000000000
mxcsr: 1fa0
XMM0: 00000000000000000000000000000000 XMM1: 00000000000000000000000000000000
XMM2: 00000000000000000000000000000000 XMM3: 00000000000000000000000000000000
XMM4: 00000000000000000000000000000000 XMM5: 00000000000000000000000000000000
XMM6: 00000000000000000000000000000000 XMM7: 00000000000000000000000000000000
XMM8: 00000000000000000000000000000000 XMM9: 00000000000000000000000000000000
XMM10: 00000000000000000000000000000000 XMM11: 00000000000000000000000000000000
XMM12: 00000000000000000000000000000000 XMM13: 00000000000000000000000000000000
XMM14: 00000000000000000000000000000000 XMM15: 00000000000000000000000000000000

Backtrace:
/usr/lib64/libxcb-glx.so.0(xcb_glx_query_server_string_string_length+0x0)[0x7f40a60941e0]
/usr/lib64/libGL.so.1(+0x41204)[0x7f40ab5e0204]
/usr/lib64/libGL.so.1(+0x22e42)[0x7f40ab5c1e42]
/usr/lib64/libGL.so.1(glXQueryVersion+0x19)[0x7f40ab5bdd89]
/usr/lib64/mysql-workbench/libmdcanvasgtk.so.0(_ZN3mdc21detect_opengl_versionEv+0x21)[0x7f40b09712c1]
/usr/bin/mysql-workbench-bin(_ZN2wb9WBContext19is_opengl_availableEv+0x40)[0x9f30d0]
/usr/bin/mysql-workbench-bin(_ZN2wb9WBContext24determine_opengl_supportEPNS_9WBOptionsE+0x1a)[0x9f97da]
/usr/bin/mysql-workbench-bin(_ZN2wb9WBContext5init_EPNS_19WBFrontendCallbacksEPNS_9WBOptionsE+0x10b1)[0xa067a1]
/usr/bin/mysql-workbench-bin(_ZN2wb11WBContextUI4initEPNS_19WBFrontendCallbacksEPNS_9WBOptionsE+0x30)[0x9d52d0]
/usr/bin/mysql-workbench-bin(_ZN7ProgramC1EN2wb9WBOptionsE+0x97f)[0x80a59f]
/usr/bin/mysql-workbench-bin(main+0x60c)[0x804d0c]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f40a8e7f455]
??:0(??)[0x807811]

Memory map:

00400000-00f16000 r-xp 00000000 08:06 1712694 /usr/bin/mysql-workbench-bin
01116000-01117000 r--p 00b16000 08:06 1712694 /usr/bin/mysql-workbench-bin
01117000-0111c000 rw-p 00b17000 08:06 1712694 /usr/bin/mysql-workbench-bin
...
7f40b35ff000-7f40b3600000 r--p 00000000 08:06 1586199 /usr/lib/locale/en_US.utf8/LC_TIME
7f40b3600000-7f40b3601000 r--p 00000000 08:06 1586198 /usr/lib/locale/en_US.utf8/LC_MONETARY
7f40b3601000-7f40b3602000 r--p 00000000 08:06 1575060 /usr/lib/locale/en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES
7f40b3602000-7f40b3603000 r--p 00000000 08:06 1727822 /usr/lib/locale/en_US.utf8/LC_PAPER
7f40b3603000-7f40b3604000 r--p 00000000 08:06 1727848 /usr/lib/locale/en_US.utf8/LC_NAME
7f40b3604000-7f40b3605000 r--p 00000000 08:06 1575277 /usr/lib/locale/en_US.utf8/LC_ADDRESS
7f40b3605000-7f40b3606000 r--p 00000000 08:06 1727802 /usr/lib/locale/en_US.utf8/LC_TELEPHONE
7f40b3606000-7f40b3607000 r--p 00000000 08:06 1727823 /usr/lib/locale/en_US.utf8/LC_MEASUREMENT
7f40b3607000-7f40b3608000 r--p 00000000 08:06 1576251 /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION
7f40b3608000-7f40b360f000 r--s 00000000 08:06 1575016 /usr/lib64/gconv/gconv-modules.cache
7f40b360f000-7f40b3612000 rw-p 00000000 00:00 0
7f40b3612000-7f40b3613000 r--p 00021000 08:06 794506 /lib64/ld-2.15.so
7f40b3613000-7f40b3614000 rw-p 00022000 08:06 794506 /lib64/ld-2.15.so
7f40b3614000-7f40b3615000 rw-p 00000000 00:00 0
7fffc0835000-7fffc0872000 rw-p 00000000 00:00 0 [stack]
7fffc0912000-7fffc0913000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

Migration error on script view when changing target (1 reply)

Support CM2D — Fri, 21 Dec 2012 05:05:40 +0000

Hello,

Thank you for the integration of "Migration".

Thank you for the integration of Migration.
In step "Manual Edditing", it is really convenient to change the target schema name.
But in the case of query views, the migration script automatically adds references to the source, which causes an error.
For example:

Source MySQL Local on schema = Toga_dev1
CREATE
ALGORITHM = UNDEFINED
DEFINER = `root`@`localhost`
SQL SECURITY DEFINER
VIEW `facture_euro` AS
select
`i`.`idimplantation` AS `idimplantation`,
`m`.`time_by_day_idtime` AS `time_by_day_idtime`,
`m`.`valeur` AS `facture_value`
from
((((((`mesures` `m`
join `implantation` `i` ON ((`m`.`implantation_idImplantation` = `i`.`idimplantation`)));

Target MySQL Server on schema = Toga_dev8
USE `Toga_dev8`;

CREATE OR REPLACE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost`
SQL SECURITY DEFINER VIEW `Toga_dev1`.`facture_euro` AS
select `i`.`idimplantation` AS `idimplantation`,
`m`.`time_by_day_idtime` AS `time_by_day_idtime`,
`m`.`valeur` AS `facture_value`
from
((((((`Toga_dev1`.`mesures` `m`
join `Toga_dev1`.`implantation` `i` on((`m`.`implantation_idImplantation` = `i`.`idimplantation`))) ;

Is there an option or a solution to address this problem ?

Thank You

mysql- workbench struct invalid error (no replies)

Rakesh Patil — Sat, 15 Dec 2012 06:58:40 +0000

I'm creating a DB in lubuntu 64 bit machine. in the workbench when i try to open existing EER model *.mwd it throws an error

Error unserializing GRT data
error unserializing object (invalid struct)

the same file works fine on windows . Please suggest.

Migrating Process (2 replies)

Jose Garcia — Wed, 26 Dec 2012 18:42:45 +0000

Hi All

Please bear with me being that I'm new to MySql and this forum. I have a question in regards to using the migration wizard on MySql 5.5. I need to migrate 2.73 tb of data from our old xserve to a new windows box. Note both the source and target are MySql databases. This is my question with the data base I have a field called file_path this field points to the folder where our images are stored. When I do a migration I understand I'm migrating one database to another but will it also bring over the actual data images that are referenced in the file_path field.

Thanks appreciate the help.
Jose'

Import of big database (no replies)

fritz müller — Thu, 06 Dec 2012 21:00:15 +0000

if the import function of phpmyadmin fails, my script imports very big database dumps. Just use the script.

/*
Importscript to import Big SQL scripts
It handles very Big SQL scripts.

ATTENTION: JUST ONE SQL ORDER PER LINE (;)

1. Upload this script to your server. Change the SQL Properties before

2. Upload the SQL file to the same Folder (Best with FTP)

3. Call the Script with the SQL Filename as GET Parameter (Example: www.yourdomain.com/importskript.php?filename=sql.sql)

Copyright by Lucius Bachmann
*/
function db()//Function to Connect to Database
{
$MySQL_Host="Your-MySQL Host";
$MySQL_User="Your Mysql User";
$MySQL_Passw="Your Mysql Password";
$db="Your DB Name";

$dblk=mysql_connect("$MySQL_Host","$MySQL_User","$MySQL_Passw");
echo mysql_error($dblk);
mysql_select_db($db);
return($dblk);
}

$dblk=db();//Database connect
session_start();//start session
$maxtime=ini_get("max_execution_time");// get max execution time
$starttime=time();//starttime

if(isset($_SESSION['pointer'])){//If the skript was called by itself, set the variables as they where before
$pointer = $_SESSION['pointer'];
$sql = $_SESSION['sql'];
$counter = $_SESSION['counter'];
$fehler = $_SESSION['fehler'];
$Filename= $_SESSION['filename'];
$FileHandler = fopen($Filename, 'r') or die("can't open file");
fseek($FileHandler, $pointer);//Jump to the place the pointer was before
}
else{//If its the first call, initialize the Variables

$sql='';
$letter='';
$Filename = $_GET['filename'];

$pointer=0;

$counter=0;
$lastletters='';
$fehler='';
$_SESSION['skript_startet']=$starttime;
$FileHandler = fopen($Filename, 'r') or die("can't open file");
}

while(time()-$starttime+5 < $maxtime){// As long as you have Execution Time, And to avoid maximum execution timeout
$line=fgets($FileHandler);//Read line
if($line === false){//If End Of file, exit
$EndofFile=1;
break;
}
while(!(strpos($line, "--")===false)){//If a comment line, get next line
$line=fgets($FileHandler);

}
$pointer=ftell($FileHandler);//get the offset of the filecursor
$string=substr($line,0, strlen($line)-1);//read the line into a string
$sql.=$string;//append to sql order
$lastletter=substr($line, strlen($line)-2, strlen($line)-1);// get the last letter of the line
if(!(strpos($lastletter, ";")===false)){//If the last letter was a semicolon,

if(!mysql_query($sql)){//Mysql query
$fehler.="SQL Fehler: $sql
";// Fehler Save
}
$counter++;// count the orders
$sql='';
}

}

if(isset($EndofFile)){//If the sql import is finished, show stats
$timeUsed=time()-$_SESSION['skript_startet'];
echo"
SQL Befehle ausgeführt: $counter

Time Used: $timeUsed seconds

Fehler: $fehler

";
}
else{//save the variables in the session

$_SESSION['pointer']=$pointer;
$_SESSION['sql']=$sql;
$_SESSION['counter']=$counter;
$_SESSION['fehler']=$fehler;
$_SESSION['filename']=$Filename;

echo "";//and call the script itself
}

?>

Import .DBF Structure & Data to MySql Database via Workbench (1 reply)

Richard Hemingway — Mon, 26 Nov 2012 11:02:45 +0000

Hi all,

I am new to workbench & MySQL, but hopefully someone can point me in the right direction with this one.

I have an SQL reporting system which connects to a MySQL database on the same hosting package. I have 4 seperate .DBF files that I want to import the data & structure from to the MySQL database so that I can link the reporting system to this data & create reports.

I tried using the import tool in Workbench which said that the import had run successfully but no table or data was created in the MySQL database.

Can I do this in workbench, and if so how? Otherwise what is the best way to do so.

Thanks for your help!

Richard

Migrate from .accdb to MySQL (5 replies)

Paolo Ermini — Thu, 22 Nov 2012 20:48:40 +0000

Hi everyone,

I'm trying to migrate my .accdb file (DATI.accdb) in MySQL.
I create DSN connector for my accdb database but, in "Fetch Schemata List" step I have this log:

Starting...

Connect to source DBMS...

- Connecting to source...

Connecting to Mssql@DATI...

Opening ODBC connection to DSN=DATI;DATABASE=;UID=sa;PWD=XXXX...

Connected

Traceback (most recent call last):

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 147, in connect

_connections[connection.__id__]["version"] = getServerVersion(connection)

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 173, in getServerVersion

ver_string = execute_query(connection, "SELECT CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)").fetchone()[0]

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 62, in execute_query

return get_connection(connection_object).cursor().execute(query, *args, **kwargs)

pyodbc.ProgrammingError: ('42000', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell'espressione della query 'CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)'. (-3100) (SQLExecDirectW)")

Traceback (most recent call last):

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 173, in getServerVersion

ver_string = execute_query(connection, "SELECT CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)").fetchone()[0]

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 62, in execute_query

return get_connection(connection_object).cursor().execute(query, *args, **kwargs)

pyodbc.ProgrammingError: ('42000', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell'espressione della query 'CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)'. (-3100) (SQLExecDirectW)")

Traceback (most recent call last):

File "C:\MySQL\MySQL Workbench 5.2 CE\workbench\wizard_progress_page_widget.py", line 65, in run

self.func()

File "C:\MySQL\MySQL Workbench 5.2 CE\modules\migration_source_selection.py", line 415, in task_connect

raise e

SystemError: ProgrammingError("('42000', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell'espressione della query 'CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)'. (-3100) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.getServerVersion

ERROR: Error during Connect to source DBMS: ProgrammingError("('42000', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell'espressione della query 'CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)'. (-3100) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.getServerVersion

Traceback (most recent call last):

File "C:\MySQL\MySQL Workbench 5.2 CE\workbench\wizard_progress_page_widget.py", line 543, in update_status

task.run()

File "C:\MySQL\MySQL Workbench 5.2 CE\workbench\wizard_progress_page_widget.py", line 80, in run

raise e

SystemError: ProgrammingError("('42000', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell'espressione della query 'CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR)'. (-3100) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.getServerVersion

ERROR: Exception in task 'Connect to source DBMS': SystemError('ProgrammingError("(\'42000\', "[42000] [Microsoft][Driver ODBC Microsoft Access] Errore di sintassi (operatore mancante) nell\'espressione della query \'CAST(SERVERPROPERTY(\'ProductVersion\') AS VARCHAR)\'. (-3100) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.getServerVersion',)

Failed

Please help me ;)

Changing UNIQUE_CHECKS, FOREIGN_KEY_CHECKS & SQL_MODE (2 replies)

John Rocha — Mon, 26 Nov 2012 03:41:05 +0000

I have a question/concern.

My organization often uses the output from Workbench's "create alter script" export ability as the basis for their alter scripts. They start with what workbench provides and then add their own additional SQL commands.

In the workbench output I see the following near the top of the script

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

and at the end there are commands that to restore the old values.

I found the explanation for these changes at:
http://dev.mysql.com/doc/workbench/en/workbench-faq.html

However, my concern is..... what if the script fails in the middle. Doesn't that mean that the we never restore the old values for these variables? And isn't that bad?

Problems with utf8 characters when migrating from SQL Expres 2008 (5 replies)

morten nielsen — Fri, 16 Nov 2012 07:23:30 +0000

Hi

I have a problem when trying to migrate a database from MS Express 2008 to MySql 5.5.

I use the migration-tool in MySql Workbench (newest version) and all the schema creation and mapping is working perfectly. But when it comes to bulk-copy, the data inserted is not converted to utf8, and that results in strings that are "cut off" when a danish Æ-Ø-Å is encountered.

When i run the wizard and it comes to "Manual Editing" it says under "Migration Message": Collation Danish_Norwegian_CI_AS migrated to utf8_general_ci. SO i dont understand, why it is not working?

I have tried the migration-tool in SQLyog, and it handles the conversion as expected, but i really dont want to pay for it :)

How can i make it convert the strings correctly?

Some help or guidance would be really helpfull.

Regards, Morten

Migration issue from Access database to MySQL (1 reply)

Mary Pham — Tue, 13 Nov 2012 18:27:40 +0000

Hi

I want to migrate an Access database to MySQL using the Migration tool on the Work Bench, but it always crashed. There is "None" display for Schema selection for the Access database and then it was crashed on the next step.

What could possibly go wrong here? Is it a bug?

Does Migration tool not work with Access database?

Thank you very much

ENCODE() on MySQL 5.0 differs from 5.5+ (3 replies)

Carl Dreher — Thu, 15 Nov 2012 02:02:44 +0000

I was running MySQL 5.0 on Windows XP and using the ENCODE() and DECODE() functions to encode passwords in the database. I've moved to version 5.5 which is now running under Windows 7 64-bit.

I've discovered that the ENCODE/DECODE functions provide a different result in the new version. I've verified this by comparing the value produced by ENCODE for a known password on the 5.0 system, to the value produced for the same password on the 5.5 system. (Both systems use the same encoding string, of course.)

Any explanations? This caused a big headache for user passwords, none of which now work on the new system. Fixing the new database is straightforward, of course, but what I'm really interested in is what happened.