I have databases in my MySQL Workbench, but when I try to export the database, it gives me errors:
This error appears related to a known limitation in Workbench 6.3.5. An upgrade to 6.3.6 should fix it. It's related to the bundled 5.7 mysqldump binary.
Related
im trying to restore a table from a backup file with pg_restore. However i get the error mentioned above. I read everywhere that an upgraded version of postgres is needed. I upgraded mine to 9.6.8-1 and then 10.3-1. Both did not work. Does anybody have a detailed procedure to fix this problem using a windows OS?
Thanks in advance
Solved for me -
I had the same error restoring from PgAdmin4 on a computer with multiple Postgrsql versions installed. It was calling an older pg_restore version. In PgAdmin I changed the binary path in File/Preferences/Binary Path from $DIR/../runtime to C:\Program Files\PostgreSQL\10\bin and that fixed my issue. I suspect your having a similar issue at which you are unknowingly calling an older pg_restore version even though you updated postgresql.
I've two different pc I use to code and I've inserted data just on the laptop, where DataGrip is installed. Now I would want to clone data on the desktop where I've installed DataGrip and set the Postgres driver and database.
Which is the faster way to do this?
Thanks!
In DataGrip there are dump/restore tools for PostgreSQL
To dump the objects, use the Dump with… context menu option. Restore tools for MySQL and PostgreSQL also can be accessed from the context menu. In the case of PostgreSQL, the restore operation can be done with pg_dump or psql: there is a way to choose in the Restore dialog.
I was running Openerp 7 earlier, then updated the code to Odoo8 RC1 on my Ubuntu 13.04, with Postgre Sql 1.16.1 database and Eclipse 3.8 IDE. Now I wanted to update to Odoo8.0 , when I downloaded the code from GitHub and tried to run the server from eclipse, I got this error:
"column ir_ui_view.active does not exist"
I understand here that Odoo8 has added another column to the ir_ui_view table, but how should I fix it on my side to get my server running. I dont want to go through the entire process to setup Postgresql, creating user, assigning roles and then installing odoo. Can I have a simple solution where I can edit the server file or change any database property to get this running. I went through few links but none could help much.
Thanks.
OpenERP/Odoo databases are incompatible between major versions.
They must first be upgraded.
This can be done by OpenERP support services or by yourself using tools such as OpenUpgrade.
try sudo apt-get install python-pass
I'm using CentOS 6.4, and did
sudo yum install mysql-workbench-community.x86_64
That installed MySQL workbench version 6.1
When I launch the application it lists MySQL Connections, and has a box for Local instance 3306.
When I double click that box the app just closes. WTH?
edit: it's printing this on the console
/usr/libexec/mysql-workbench/mysql-workbench-bin: symbol lookup error: /usr/lib64/mysql-workbench/libwbscintilla.so: undefined symbol: gtk_widget_get_realized
If you've got the same issue like me with Workbench unexpectedly crashing it's easy to resolve:
Edit -> Preferences -> tab "general" and check "Force use of software based rendering for EER diagrams"
At least it's worth a try!
I too was experiencing same problem (on CentOS 6.4). I followed what they concluded on this bug report file. I installed the Workbench 6.0.9 release and the problem is gone.
If you've got the same issue like me with Workbench unexpectedly crashing while opening previous session with tables then just clean up sql_workspaces folder with their sub-directories:
rm -rf ~/.mysql/workbench/sql_workspaces/*
Unfortunately I have the repetition of this event every time so I created the alias in my ~/.bashrc (pro-)file:
alias fix_workbench='rm -rf /home/user/.mysql/workbench/sql_workspaces/*'
P.S.: My MySQL Workbench's version is: 8.0.12. The debug log is too long, including Register/Memory dumps and Backtrace.
As plan B you can also use dbeaver. It works on all OS.
https://dbeaver.io/download/
You better read what platforms are supported by MySQL Workbench: http://www.mysql.com/support/supportedplatforms/workbench.html. The Linux world is so shattered, it's very difficult to support all flavours. And of course always my own is certainly one that should be amongst the supported platforms...
Had same issue CentOS 6.4 :
/usr/libexec/mysql-workbench/mysql-workbench-bin: symbol lookup error: /usr/lib64/mysql-workbench/libwbscintilla.so: undefined symbol: gtk_widget_get_realized
Installed gtk2 devel libraries.
yum install gtk2-devel
Problem solved.
Thanks
Prasad
Centos6.8, Mysql80, Mysqlworkbench8.0.17
I have encountered same problem。 tried to install other version, but not worked; tried to install gtk2, not worked as well. Finally, I thought maybe the version was not correspond, so I install gtk3, it's worked.
What worked for me were very simple steps:
Downloaded a previous version of MySQL Workbench just in case
If it still shuts down when opening the app then verify that there is no app using mysql (for example a website you are building or whatever project you are working on) Stop them all
Do not open the workbench and stop the mysql server in the command line:
sudo service mysql stop
Now with mysql stopped open MySQL Workbench and open any connection
Once inside, MySQL should obviously not be running so now:
sudo service mysql start
Voila!
I want to restore a database in PostgreSQL but it can't. I have replaced pg_restore in bin folder but it's still not working. The message is :
pg_restore: [archiver] unsupported version (1.12) in file header
I solved this by upgrading postgresql from 8.X to 9.2.4. If you're using brew on Mac OS-X, use -
brew upgrade postgresql
Once this is done, just make sure your new postgres installation is at the top of your path. It'll look something like (depending on the version installation path) -
export PATH=/usr/local/Cellar/postgresql/9.2.4/bin:$PATH
This occurs when the archive was created with a version newer than the pg_restore you are using can support. The best way to fix this is to install a newer version of pg_restore. Note that this limitation has more recently gone away. I can use pg_restore from 9.1 against a 9.2 custom dump file for example.