https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT>, we are getting this error trying t...
# replication-ask-ai
g
@kapa.ai, we are getting this error trying to sync MySql->Snowflake:
Copy code
[config_error] MySQL Timezone Configuration Issue: The sync encountered a timezone configuration issue. Please configure your database with the correct timezone as specified in the error message. For more details, refer to: <https://dev.mysql.com/doc/refman/8.4/en/time-zone-support.html>.
<https://docs.oracle.com/javase/8/docs/api/index.html?java/io/SQLException.html>
k
Thinking completed This error occurs because the MySQL server is configured with a timezone (such as 
CEST
, 
CDT
, or 
PDT
) that is unrecognized or ambiguous to the MySQL JDBC driver, which requires a valid IANA timezone [application.yml; mysql-troubleshooting]. To resolve this issue, you can specify an IANA-compliant timezone using one of the following methods: Option 1: Configure JDBC URL Parameters (Recommended) Add the 
serverTimezone
property in the source connector's configuration under JDBC URL Parameters:
Copy code
serverTimezone=UTC
_(Replace 
UTC
with your specific IANA timezone if needed, such as 
serverTimezone=Europe/Amsterdam
or 
serverTimezone=America/New_York
)_ [Forum Post: Mysql error: The server time zone value ‘CEST’ is unrecognized; source-mysql timezone issue]. Option 2: Set the Advanced Server Timezone (CDC Mode) If you are using Change Data Capture (CDC) mode, you can map the server timezone directly in the connector settings: 1. Open your MySQL Source settings in Airbyte. 2. In the replication method configuration, locate the Configured server timezone for the MySQL source (Advanced) field [MySqlSourceConfigurationSpecification.kt]. 3. Enter the equivalent IANA-compliant timezone (for example, convert 
CEST
to 
Europe/Berlin
) [mysql-troubleshooting]. Option 3: Update the MySQL Server Timezone Alternatively, configure the timezone directly on your MySQL database to use an IANA-standard timezone according to MySQL's timezone support documentation [application.yml]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
g
@kapa.ai our mysql server does not have tzinfo support installed, we were using jdbc url 
tinyInt1isBit=False&serverTimezone=&#43;10&connectionTimeZone=&#43;10&forceConnectionTimeZoneToSession=TRUE
(with html entity codes for the + sign due to interface url encoding handling)
k
Thinking completed The knowledge sources do not explicitly mention using offset formats (like 
+10
or 
+10
) or options like 
forceConnectionTimeZoneToSession
to work around missing MySQL 
tzinfo
tables. However, based on the provided Airbyte documentation and code, here are the relevant details: 1. Use an IANA-compliant Timezone Name: Airbyte specifically requires the timezone to conform to the IANA standard [MySqlSourceConfigurationSpecification.kt; mysql-troubleshooting]. Instead of raw offsets like 
+10
, try using canonical IANA timezone names (e.g., 
Etc/GMT-10
or a specific region like 
Australia/Sydney
or 
Asia/Vladivostok
depending on your location). Alternatively, setting it to 
UTC
is commonly recommended to bypass unrecognized timezone issues [Forum Post: Mysql error: The server time zone value ‘CEST’ is unrecognized; Forum Post: BigQuery normalization doesn't find a destination table]. 2. CDC Connector Property vs. JDBC URL: If you are running in Change Data Capture (CDC) mode: ◦ Airbyte configures Debezium properties separately from regular JDBC parameters [MySqlSourceDebeziumOperations.kt]. ◦ In Debezium, the 
serverTimezone
property is considered obsolete in favor of 
connectionTimeZone
[Forum Post: Mysql CDC is not working when option user require ssl is enabled]. ◦ Rather than setting it only in the JDBC URL string, provide the timezone directly in the connector UI under the CDC advanced option: Configured server timezone for the MySQL source (Advanced) [MySqlSourceConfigurationSpecification.kt]. Airbyte passes this value to the underlying Debezium driver as 
connectionTimezone
[MySqlSourceDebeziumOperations.kt]. 1. Install Timezone Tables on MySQL: Because JDBC drivers and CDC tools rely on MySQL's internal time zone definitions, the recommended resolution per the error reference is to populate the timezone tables in your MySQL server directly (following MySQL's timezone support documentation, typically via 
mysql_tzinfo_to_sql
) so the database and driver can resolve the timezones accurately [application.yml]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
g
@kapa.ai We have cleared our JDBC url params and tried 'Australia/Brisbane' and '+10' and our logs still have an error mentioning 'AEST' timezone
Copy code
2026-09-30 15:30:14 source ERROR main i.a.c.AirbyteConnectorRunnable(run):38 Failed class io.airbyte.cdk.read.ReadOperation operation execution. java.lang.RuntimeException: Connector configuration is not valid. Unable to connect: The server time zone value 'AEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'connectionTimeZone' configuration property) to use a more specific time zone value if you want to utilize time zone support.
	at io.airbyte.cdk.read.cdc.CdcPartitionReader$CompletionCallback.handle(CdcPartitionReader.kt:492) ~[bulk-cdk-toolkit-extract-cdc-1.1.10.jar:?]
	at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:495) ~[debezium-embedded-3.1.2.Final.jar:3.1.2.Final]
	at io.debezium.embedded.ConvertingEngineBuilder$1.run(ConvertingEngineBuilder.java:163) ~[debezium-embedded-3.1.2.Final.jar:3.1.2.Final]
	at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]

Stack Trace: java.lang.RuntimeException: Connector configuration is not valid. Unable to connect: The server time zone value 'AEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'connectionTimeZone' configuration property) to use a more specific time zone value if you want to utilize time zone support.
	at io.airbyte.cdk.read.cdc.CdcPartitionReader$CompletionCallback.handle(CdcPartitionReader.kt:492)
	at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:495)
	at io.debezium.embedded.ConvertingEngineBuilder$1.run(ConvertingEngineBuilder.java:163)
	at java.base/java.lang.Thread.run(Thread.java:1583)
k
Thinking completed I'm sorry, but the provided knowledge sources do not explicitly explain why 
Australia/Brisbane
is not being recognized by the connector when your MySQL server lacks timezone info tables. However, the logs and source code provide clear details about what is happening: Why this happens 1. The error comes from Debezium/EmbeddedEngine: The error message:The server time zone value 'AEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'connectionTimeZone' configuration property)...indicates that when Debezium connects to your database, the MySQL server is reporting its system timezone as 
AEST
(an ambiguous/non-IANA abbreviation) [application.yml; mysql-troubleshooting]. 2. Missing 
tzinfo
tables on the MySQL server: When named timezones like 
Australia/Brisbane
are used without MySQL timezone description tables populated, MySQL itself cannot resolve the named timezone [application.yml]. How to resolve it 1. Set the Dedicated CDC Timezone Field in Airbyte: In Airbyte's MySQL CDC implementation, the value configured in Configured server timezone for the MySQL source (Advanced) is explicitly passed to Debezium as 
database.connectionTimezone
[MySqlSourceDebeziumOperations.kt]: ◦ Go to your MySQL Source configuration. ◦ Under the Read Changes using Change Data Capture (CDC) settings, locate Configured server timezone for the MySQL source (Advanced) [MySqlSourceConfigurationSpecification.kt]. ◦ Try setting this value to 
UTC
(or an IANA format timezone) [mysql-troubleshooting; Forum Post: Mysql error: The server time zone value ‘CEST’ is unrecognized]. 1. Add 
connectionTimeZone
to JDBC URL Parameters: As indicated by the JDBC driver exception, you can also try specifying the property directly in JDBC URL Parameters:connectionTimeZone=UTC_(Or test with your offset format if required, though the connector expects standard IANA names)_ [Forum Post: Mysql error: The server time zone value ‘CEST’ is unrecognized]. 2. Populate the Timezone Tables on the MySQL Server (Permanent Fix): The connector exception notes that database configuration is the primary resolution for timezone issues [application.yml]. Loading the timezone tables into MySQL (referencing MySQL's time zone support documentation) enables MySQL and Debezium to map 
AEST
and regional IANA names properly [application.yml]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Open in Slack
PreviousNext
Powered by