-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snowflake on JDK17 fails with "Object 'DATABASECHANGELOGLOCK' already exists." #3000
Comments
The 3.13.20 driver upgrade doesn't seem to solve the issue, despite it shipping with the new arrow code. #3001 |
Got the same issue with Liquibase 4.9.1, postgres-jdbc 42.3.6, JDK 17 |
I found that I specified wrong defaultSchemaName in liquibase-maven-plugin. That was the cause of this error in my case. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Liquibase Version: 4.12.0
Database Vendor & Version: Snowflake
Description
Running any operation that needs a database lock will fail with
Object 'DATABASECHANGELOGLOCK' already exists. [Failed SQL: (2002) CREATE TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP_NTZ, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))]
Additional Context
The issue is with the snowflake jdbc driver. The "arrow" query result format that is the new default has issues. snowflakedb/snowflake-jdbc#533 Adding
&JDBC_QUERY_RESULT_FORMAT=JSON
to your url will switch the format back to JSON and avoid the issue.Hopefully the new driver version which fixes the issue with arrow will be out soon.
The text was updated successfully, but these errors were encountered: