- 382.6K All Categories
- 2.1K Data
- 212 Big Data Appliance
- 1.9K Data Science
- 448.4K Databases
- 221.1K General Database Discussions
- 25 Multilingual Engine
- 541 MySQL Community Space
- 469 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 499 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.3K SQL & PL/SQL
- 21.1K SQL Developer
- 293.8K Development
- 9 Developer Projects
- 130 Programming Languages
- 290.5K Development Tools
- 96 DevOps
- 3K QA/Testing
- 645.6K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 151 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 146 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 200 Java User Groups
- 292 LiveLabs
- 36 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 168 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 234 Portuguese
Oracle SQL Developer MySQL JDBC Connector TimeZone error
I need to find out how to change my JDBC connection string when using mysql-connector-java-8.0.13.jar for 3rd party JDBC connections.
I get this error:
The server time zone value 'EDT' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property)
to use a more specifc time zone value if you want to utilize time zone support.
Vendor code 0
After reading this : Connecting to MySQL 8.0
I cannot modify my server parameters.
So I want try something like this:
1771220 Nov 16, 2018 10:05 PM (in response to 7392a252-c6e5-48f9-9c5c-40549ba059a1)
For SQL Developer, there is a connection hack that worked for me when there was a timezone mismatch between the client and server.
(In my case I could not modify the server parameters.) The hack exploits the fact that the Port field is just appended to the connection URL as a string.
So something like this works.
Where would I be able to make this connection string change in Oracle SQL Developer version 19.1.0.094?
I needed the dummyparam= at the end to protect against URL format errors when the trailing slash gets appended.