[Liquibase-user] error creating DATABASECHANGELOGLOCK table -- name already in use

[Mitch Gitman]

I've been using LiquiBase for months now, but I've finally managed to stump
myself. I've got a changelog file that my colleagues and I have run
countless times against an Oracle 10g database. Only now, though, whenever I
run the regular database update, I get the following error:

liquibase.exception.LockException: liquibase.exception.JDBCException: Error
executing SQL CREATE TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED
NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT
PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at liquibase.lock.LockHandler.waitForLock(LockHandler.java:167)
...
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: liquibase.exception.JDBCException: Error executing SQL CREATE
TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED NUMBER(1) NOT NULL,
LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT
PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at
liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:56)
...
Caused by: java.sql.SQLException: ORA-00955: name is already used by an
existing object

I can only figure the name that's already in use is DATABASECHANGELOGLOCK.
So I tried dropping the DATABASECHANGELOGLOCK table, but I'm still getting
the same error.

Any ideas how to get out of this invalid state, or why this is happening?

[Voxland, Nathan]

Is it an issue with running liquibase against a different schea than you are expecting? I don’t think oracle allows case-sensitivity to be turned on, so it shouldn’t be related to that.



Do you get the same error right away after you drop the table, or does the next liquibase update succeed and then start failing with the same error again?

Nathan



From: liquibase-user-***@lists.sourceforge.net [mailto:liquibase-user-***@lists.sourceforge.net] On Behalf Of Mitch Gitman
Sent: Friday, August 15, 2008 11:09 AM
To: liquibase-***@lists.sourceforge.net
Subject: [Liquibase-user] error creating DATABASECHANGELOGLOCK table -- namealready in use



I've been using LiquiBase for months now, but I've finally managed to stump myself. I've got a changelog file that my colleagues and I have run countless times against an Oracle 10g database. Only now, though, whenever I run the regular database update, I get the following error:

liquibase.exception.LockException: liquibase.exception.JDBCException: Error executing SQL CREATE TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at liquibase.lock.LockHandler.waitForLock(LockHandler.java:167)
...
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: liquibase.exception.JDBCException: Error executing SQL CREATE TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:56)
...
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object

I can only figure the name that's already in use is DATABASECHANGELOGLOCK. So I tried dropping the DATABASECHANGELOGLOCK table, but I'm still getting the same error.

Any ideas how to get out of this invalid state, or why this is happening?

[Mitch Gitman]

Oh well, I finally realized I was indeed pointing at the wrong schema.
Thanks for the quick response.

On Fri, Aug 15, 2008 at 9:15 AM, Voxland, Nathan <

Post by Voxland, Nathan
Is it an issue with running liquibase against a different schea than you
are expecting? I don't think oracle allows case-sensitivity to be turned
on, so it shouldn't be related to that.
Do you get the same error right away after you drop the table, or does the
next liquibase update succeed and then start failing with the same error
again?
Nathan
*Sent:* Friday, August 15, 2008 11:09 AM
*Subject:* [Liquibase-user] error creating DATABASECHANGELOGLOCK table --
namealready in use
I've been using LiquiBase for months now, but I've finally managed to stump
myself. I've got a changelog file that my colleagues and I have run
countless times against an Oracle 10g database. Only now, though, whenever I
liquibase.exception.LockException: liquibase.exception.JDBCException: Error
executing SQL CREATE TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED
NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT
PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at liquibase.lock.LockHandler.waitForLock(LockHandler.java:167)
...
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: liquibase.exception.JDBCException: Error executing SQL CREATE
TABLE DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED NUMBER(1) NOT NULL,
LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT
PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
at
liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:56)
...
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object
I can only figure the name that's already in use is DATABASECHANGELOGLOCK.
So I tried dropping the DATABASECHANGELOGLOCK table, but I'm still getting
the same error.
Any ideas how to get out of this invalid state, or why this is happening?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
https://lists.sourceforge.net/lists/listinfo/liquibase-user