I want to connect to a MySql database using oracle SQL developer but when I try create a new connection it gives to me this error:
The connection property 'zeroDateTimeBehavior' acceptable values are:
'CONVERT_TO_NULL', 'EXCEPTION' or 'ROUND'. The value 'convertToNull'
is not acceptable.
Probably I have to change the connection url string since the value "convertToNull" is not recognized, but i don't know how to do it. Can someone help me?
I had this problem with the latest version of the JDBC driver for MySQL (8.0.11). When I reverted to the older driver, the problem went away.
try using any my sql connector versions after 8.0.11, it will work. in my case I have used 8.0.15, it successfully worked.
Related
I work with Eclipse and I want to use the version 7 of Liferay but when I run my Tomcat server I have an error with MySQL.
Please upgrade to at least MySQL 5.6.4. The portal no longer supports older versions of MySQL
Like this the problem is pretty obvious but my SQL version is already 5.7.19
I have check my driver of MySQL in preference->data management->connectivity->driver definition and my MySQL JDBC Driver is 5.1
I want to know if someone already had this issue and know how to fix it
This is how the version gets validated, and this is how the version string gets constructed. I'd say: Please make extra extra extra sure that you are addressing the mysql server that you intend to address:
You can check your mysql version from the mysql command line client by executing select version();. Get your credentials and database URL from Liferay's portal-ext.properties or your appserver's connection pool configuration, depending on where you configured it.
EDIT for present day readers
This was a bug in an old version of DBeaver that was subsequently fixed.
I am getting an 'access denied' error trying to connect to a Google Cloud SQL MySQL instance with SSL in DBeaver.
I am able to:
connect to the server with the same SSL credentials in MySQL Workbench
connect without SSL credentials (through user name / password) in DBeaver.
Any suggestions why this might be?
You can add connection with SSL support, at least in latest version for today (5.1). Create connection as usual, then skip testing and go to next step, then on SSL tab select "Require SSL" and unselect other checkboxes if selected, then test the connection.
in dbeaver the ssl connection configuration is available but it is not working and it is not implemented, it took me a day to find out that this is because of dbeaver bug. If you need to connect through ssl to Postgres, you can use 'DataGrip' instead.
As mentioned here:
https://dbeaver.io/forum/viewtopic.php?f=2&t=1921
'Currently DBeaver doesn't support SSL connections out of the box.
You could try to configure it manually if you are familiar with Java (instructions are at https://jdbc.postgresql.org/documentati ... lient.html).
Easy SSL support is in TODO and will be added in one of next versions.'
I get to do access database in DBeaver updating only useSSL = true in Driver Properties. See the picture:
Verify if the useSSL property is set to TRUE in data-sources.json. In windows its path is path-to-user/AppData\Roaming\DBeaverData\workspace6\General\.dbeaver\data-sources.json.
I had a similar issue. I am using DBeaver version Version 22.1.0.202206051253.
I noticed even though the driver properties would show useSSL=true, it was not set.
As a result, it throws Access denied for user xxxxxx-XXXXX'#'XXX:XX:X:X' (using password: YES).
In 'Connection Settings' navigate to 'Driver Properties' check whether the 'useSSL' value is 'true' or 'false'. If 'false' make it 'true' and finish.
If value is 'true' first make it 'false' and again change value to 'true'. Then try to connect to databse. It should be success. Most of time that useSSL value not getting correctly by json file. Hence this will update it again.
Long time lurker, first time poster; hoping anyone can help me out.
Im using MySQL Workbench 5.2.41 to migrate a database from SQL Server to MySQL 5.0.8
The entire process goes smoothly: both SQL and MySQL connection Tests are good, the skemea and table create as expected, everything checks out until the 'Bulk Data Transfer' step. At that point I receive this error:
...
Migrating data...
wbcopytables.exe --odbc-source=DSN=SQL Server 11;DATABASE=;UID=sa --target=root#127.0.0.1:3306 --progress --passwords-from-stdin --thread-count=1 --table [GSAClosers_v2] [dbo].[AccountBase] `dbo` `AccountBase`
`dbo`.`AccountBase`:Copying 84 columns of 169530 rows from table [GSAClosers_v2].[dbo].[AccountBase]
ERROR: `dbo`.`AccountBase`:SQLGetData: HY009:10:[Microsoft][ODBC Driver Manager] Invalid argument value `dbo`.`AccountBase`:
Finished copying 0 rows in 0m00s
Copy helper has finished
...
For connectors I'm using Microsoft SQL Server / ODBC Data Source / DSN: SQL Server and for MySQL the IP and port(3306).
SQL Server 2012 Management Studio connects and all operations work as expected.
O, side not: both are on the same localhost machine.
If anyone can shed some light on this I would be forever indebted. Thanks in advance
From here:
[Microsoft][ODBC Driver Manager] Invalid argument value.
Regarding to the error message and code you provided, which seems is
database is invalid or cannot be accessed. That means either the
database does not exist or the user does not have permission to access
the database.
It turns out you need specify the instance after the server name, so
in the server name in the dialog box for creating the ODBC Data
Source, you must enter it as either: MyServer\SQLEXPRESS or
.\SQLEXPRESS
I think you may have a problem connecting to your database from wbcopytables.exe. Keep in mind that this is a separate tool so the fact that you can connect from the rest of the Migration Wizard doesn't imply that you will connect in wbcopytables.exe.
The thing that worries me the most is that your DSN has whitespace characters. This might be interpreted by the Windows terminal as independent command line parameters. One thing you can do is to edit your DSN name removing the whitespaces and try again.
You may also want to connect without a DSN by putting all your connection parameters explicitely as explained in my blog post: How-To: Guide to Database Migration from Microsoft SQL Server using MySQL Workbench.
And, by the way, since MySQL Workbench 5.2.42 is out you should go and get it. The Migration Wizard is pretty new so important bug fixes are likely launched in each recent Workbench release.
In either case I think you should file a bug with your issues with a detailed explanation about how to reproduce it, possible solutions, etc.
Hope this helps.
Ok, got it figured out: un-install java. install java 1.6, use MySQL Migration Tool. change all data types to varchar, ints and bits. run migrations....eat data.
I'am using MySQL version 5.5.14-log and we upgraded recently. Now I'am getting 2013 error in MySQL 5.5.14-log version frequently and I'am not able to reproduce the issue manually, from my application (compiled with MySQL version 5.0.41) only it is reproducing.
Anybody help me to how to reproduce this error or resolve this error. Thanks in advance.
got one answer on net, may this will help you.
error-2013-hy000-0130 resolved
Could you change the bind-address=localhost and restart MySQL server? Seems like this issue is related to yours: http://forums.mysql.com/read.php?152,355740,355742#msg-355742
Also this-
If MySQL port is wrong result is MySQL client error 2013 "Lost
connection ...". Note that this error also occurs if port forwarding
is disabled in SSH configuration (the configuration parameter
'AllowTcpForwarding' is set to 'no' in the 'sshd_config' file). It
(here) simply tells that there is no connection from SSH to MySQL for
some reason. But the mySQL client API 'thinks' there was one
connection and that is why is says 'Lost connection ...' and not
'Can’t connect...'. There was one successful connection - but not to
the MySQL server - to the SSH daemon only! But the MySQL client API is
not designed to 'see' the difference!
Refer this.
I have installed a local server Xampp, which is running mySQL database in Windows. I created a Database on it with one table. The thing is I cannot get a connection to the database when I use the dbExpress TSQLConnection component. When I set the properties as follows:
ConnectionName = MYSQLConnection
Driver = MySQL
Database = databaseName
HostName = localhost
password =
UserName = root
When I change the connected property to true, I get the following error:
Borland.Data.TDBXError: DBX Error: Driver could not be properly initialized. Client library may be missing, not installed properly, of the wrong version, or the driver may be missing from the system path
I have tried making a connection to the database using the Data Explorer, but I still get the above error. I do not know what I'm missing or doing wrong.
Im using Delphi-XE2.
with mySQL on the server: MySQL client version: mysqlnd 5.0.7-dev - 091210 - $Revision: 304625 $.
I have also tried using an ADO connection, but I do not know how to set the connection string.
I'm still a noob and just want to learn how to make a connection to a mySQL database running on a web server. I cannot afford to buy any components.
Try this!
Did some google Fu - and stumpled upon this link : http://wiltonsoftware.com/posts/view/getting-embarcadero-dbexpress-mysql-working-dbx-error-driver-not-initialized
That seems to fit your needs.
My previous answer was no help .. hope the new one is better.
Old answer:
Make sure you have Data.DBXMySQL in your uses clause.
OK. I'll try a different approach.
Is it working if you setup the connection in the DataExplorer?
If not - then it's not a problem with the uses clause.
(and you obviously have tried that - sry . must be tired :-))
Otherwise a unit could be like this.
unit Unit1;
interface
uses // <-- Uses normally goes right after interface .... (you probably already have one)
Data.DBXMySql;
implementation
end.