Re : Liquibase trying to deploy file which is removed

February 27, 2019, 9:46 am

≫ Next: Re : Liquibase trying to deploy file which is removed

≪ Previous: Liquibase trying to deploy file which is removed

There the file DATA-5832.xml was removed but still it is looking into the same

Change Set Sequences/17x/0001_DATA-5832.xml::1::KantamnenS failed. Error: ORA-00933:

↧

Re : Liquibase trying to deploy file which is removed

February 27, 2019, 10:09 am

≫ Next: Re : Wierd things with checksums

≪ Previous: Re : Liquibase trying to deploy file which is removed

Tried to build it again and received the below error for the changelog table

Create Database Change Log Table
INFO 2/27/19 9:39 AM: liquibase: Creating database history table with name: PWRCTR_ETL.DATABASECHANGELOG
DEBUG 2/27/19 9:39 AM: liquibase: Executing EXECUTE database command: CREATE TABLE PWRCTR_ETL.DATABASECHANGELOG (ID VARCHAR2(255) NOT NULL, AUTHOR VARCHAR2(255) NOT NULL, FILENAME VARCHAR2(255) NOT NULL, DATEEXECUTED TIMESTAMP NOT NULL, ORDEREXECUTED NUMBER(10) NOT NULL, EXECTYPE VARCHAR2(10) NOT NULL, MD5SUM VARCHAR2(35), DESCRIPTION VARCHAR2(255), COMMENTS VARCHAR2(255), TAG VARCHAR2(255), LIQUIBASE VARCHAR2(20), CONTEXTS VARCHAR2(255), LABELS VARCHAR2(255))
DEBUG 2/27/19 9:39 AM: liquibase: Release Database Lock
DEBUG 2/27/19 9:39 AM: liquibase: Executing UPDATE database command: UPDATE PWRCTR_ETL.DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1
INFO 2/27/19 9:39 AM: liquibase: Successfully released change log lock
Unexpected error running Liquibase: ORA-00955: name is already used by an existing object

SEVERE 2/27/19 9:39 AM: liquibase: ORA-00955: name is already used by an existing object

liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object

↧

Re : Wierd things with checksums

February 27, 2019, 11:09 am

≫ Next: Re : Errors during

≪ Previous: Re : Liquibase trying to deploy file which is removed

I have noticed that the forums don't generate a lot of traffic and answers. You might have better luck posting this on StackOverflow.

That said, the most likely thing is that the file paths are different. In yor changelog, ensure that you have the top level attribute logicalFilePath set appropriately.

See this answer on StackOverflow for more details:
https://stackoverflow.com/questions/19896436/how-to-configure-liquibase-not-to-include-file-path-or-name-for-calculating-chec

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/

↧

Re : Errors during

February 27, 2019, 1:49 pm

≫ Next: Re : Errors during

≪ Previous: Re : Wierd things with checksums

I've got some clues, but nothing definitive. Here is what I did.

First, I went to github and found the 3.4.2 release tag. I then downloaded a zip file of the source code from that release and unzipped it, then opened it in my IDE (IntelliJ). I then found the source file at the top of the stack trace, and found line 118, the source of the NullPointerException. Here is the code in question, with some surrounding code for context.

if (changeLogTable != null) {
    boolean hasDescription = changeLogTable.getColumn("DESCRIPTION") != null;
    boolean hasComments = changeLogTable.getColumn("COMMENTS") != null;
    boolean hasTag = changeLogTable.getColumn("TAG") != null;
    boolean hasLiquibase = changeLogTable.getColumn("LIQUIBASE") != null;
    boolean hasContexts = changeLogTable.getColumn("CONTEXTS") != null;
    boolean hasLabels = changeLogTable.getColumn("LABELS") != null;
    boolean liquibaseColumnNotRightSize = false;
    if (!(this.getDatabase() instanceof SQLiteDatabase)) {
        DataType type = changeLogTable.getColumn("LIQUIBASE").getType();
        if (type.getTypeName().toLowerCase().startsWith("varchar")) {
            Integer columnSize = type.getColumnSize();
            liquibaseColumnNotRightSize = columnSize != null && columnSize < 20;
        } else {
            liquibaseColumnNotRightSize = false;
        }
    }

Line 118 is highlighted in yellow.

We can see that line 118 is inside a block that ensures that changeLogTable is not null, so that can't be the problem. The only other place that could cause the NPE is the call to getColumn("LIQUIBASE") the result of which is then used in the call to getType().

Looking at what getColumn() does, it appears that this would indicate that the database you are connected to has a DATABASECHANGELOG table, but that table does not have a LIQUIBASE column. See if that is in fact the case. If so, then something is a bit strange, because Liquibase tries very hard to ensure that the table exists and has the right columns, etc.

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/

↧

Re : Errors during

February 27, 2019, 3:14 pm

≫ Next: Replacing a table with a table from a different application

≪ Previous: Re : Errors during

okay will check the same, Thank you

↧

Replacing a table with a table from a different application

February 28, 2019, 11:41 am

≫ Next: Re : Errors during

≪ Previous: Re : Errors during

I have a Java application that initializes a database with the following schema

https://github.com/steinarb/ukelonn/blob/master/ukelonn.db.liquibase/src/main/resources/db-changelog/db-changelog-1.0.0.xml#L20

Now I would like to replace the users table in that database with a users table created by a different application:

https://github.com/steinarb/authservice/blob/master/authservice.db.liquibase/src/main/resources/db-changelog/db-changelog-1.0.0.xml#L7

And now I'm pondering how do accomplish this:

Remove the users table from the original changeset (the changeset setting up the schema for the ukelonn application)?

This will work for setting up a brand new ukelonn database
This will fail for existing ukelonn databases, because the changeset's checksum doesn't match the one in the changelog of the database

Have a conditional remove-if-exists for the users table (like I already have added to the start of the authservice changelog file)?

This works for existing ukelonn databases
This works for new ukelonn databases if the ukelonn changeset is run first (and I don't think I can arrange that)
This fails in a new database if the authservice database liquibase runs before the ukelonn database, because then ukelonn schema creation changeset will break because a users table already exists in the database (and making the users table creation conditional will change the changeset checksum and break existing ukelonn databases in the same way removing the table will)

Thoughts?

Lessons learned:

don't make the initial schema creation a single big changeset
make all table creations conditional

(Or maybe that's too much work for the rare edge case of replacing a table with a table belonging to a different application.... and in any case it's too late for this particular application...:-) )

↧

Re : Errors during

February 28, 2019, 12:12 pm

≫ Next: Re : Replacing a table with a table from a different application

≪ Previous: Replacing a table with a table from a different application

The build was successful for one of the change and again it got failed for the next change with the below error

WARNING 2/28/19 1:09 PM: liquibase: included file /opt/bamboo-home/xml-data/build-dir/GLOBE-UPDBPWR0-JOB1/update_pwrctr.xml/file:/opt/bamboo-home/xml-data/build-dir/GLOBE-UPDBPWR0-JOB1/Views/ is not a recognized file type

INFO 2/28/19 1:09 PM: liquibase: Successfully released change log lock
Unexpected error running Liquibase: Unknown Reason

SEVERE 2/28/19 1:09 PM: liquibase: Unknown Reason

↧

Re : Replacing a table with a table from a different application

February 28, 2019, 1:08 pm

≫ Next: Re : Errors during

≪ Previous: Re : Errors during

Ouch. Yeah, it was a bit painful to read that first 'lessons learned' comment. Yes, changelogs should be very granular, with many changesets. We generally recommend that there is only one actual change per changeset.

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/

↧

Re : Errors during

February 28, 2019, 1:11 pm

≫ Next: Can we add "create or replace job, or create or replace scheduler .. " in changeset ?

≪ Previous: Re : Replacing a table with a table from a different application

Something strange is happening and file paths are being created in a strange way. The included file path seems to have two parts to it -

the first is /opt/bamboo-home/xml-data/build-dir/GLOBE-UPDBPWR0-JOB1/update_pwrctr.xml

and the second is file:/opt/bamboo-home/xml-data/build-dir/GLOBE-UPDBPWR0-JOB1/Views/

I am not sure if that is a problem with your configuration or an actual bug.

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/

↧

Can we add "create or replace job, or create or replace scheduler .. " in changeset ?

March 1, 2019, 3:14 pm

≫ Next: Re : Replacing a table with a table from a different application

≪ Previous: Re : Errors during

Hello ALL,

My oracle has some procedures, which do some works regularly.

Now we use liquibase to update the database.

I added "create or replace procedure .. " in changeset, they work well, I can see the created procedures, meanwhile, I could find many examples online,

but I still need to add a job and a scheduler to the database, so the procedures can work according to the definition of scheduler in a job.

I can not find a way to add job and scheduler in liquibase, and can not find examples online.

Does anyone have experiences to do this?

many thanks.

↧

Re : Replacing a table with a table from a different application

March 4, 2019, 3:19 pm

≫ Next: Re : Wierd things with checksums

≪ Previous: Can we add "create or replace job, or create or replace scheduler .. " in changeset ?

As for the lessons learned... I can't do anything about the old schema, but at least I can do something about the new schema:

https://github.com/steinarb/authservice/blob/21c790bcfb5dd10ac2b73960a786438c132060fd/authservice.db.liquibase/src/main/resources/db-changelog/db-changelog-1.0.0.xml#L6

(and I have an idea for merging the old and new schemas. I'll be back on this thread with more detail if it works out)

↧

Re : Wierd things with checksums

March 6, 2019, 2:11 am

≫ Next: generateChangeLog generates XML header only

≪ Previous: Re : Replacing a table with a table from a different application

it's not the file paths as i wrote in my question:

"We looked into the DATABASECHANGELOG and saw that the paths for the file didn't match, so we resynced everything with running the changelogSync command and it generated new entries for us with correct FILENAMES."

I already corrected the filepaths.

My main question is why is liquibase fetching the Md5'd id's and then Md5ing them again before it is trying to match it with the Md5 that was generated.

This row in the log:
"Computed checksum for 8:6655e2c8d7983a338d41895acba0b208: as 97e4d04847a5754a05595ac8cdf76cd8"

Why is it computing an Md5 from an Md5?

↧

generateChangeLog generates XML header only

March 7, 2019, 3:19 am

≫ Next: Re : generateChangeLog generates XML header only

≪ Previous: Re : Wierd things with checksums

Hi all.

Liquibase (3.6.3) newbie with Informix (12.10.FC9DE on a Mac) here.

Liquibase seems to connect fine but only generates the XML "header" part of the change log:

mac02822:lb-trial wwheeler$ liquibase --url="jdbc:informix-sqli:INFORMIXSERVER=informix01_tcp;SQLH_TYPE=FILE;SQLH_FILE=/opt/informix/informix/etc/sqlhosts;DATABASE=test1" --logLevel=debug --classpath=/opt/informix/informix/jdbc/lib/ifxjdbc.jar --changeLogFile ./test1ChangeLog.xml generateChangeLog

Starting Liquibase at Thu, 07 Mar 2019 09:10:57 GMT (version 3.6.3 built at 2019-01-29 11:34:48)

Liquibase command 'generateChangeLog' was executed successfully.

mac02822:lb-trial wwheeler$ cat test1ChangeLog.xml

<?xml version="1.1" encoding="UTF-8" standalone="no"?>

Also, I tried to use diffChangeLog against an empty database and got the same result. Any ideas?

↧

Re : generateChangeLog generates XML header only

March 7, 2019, 3:44 am

≫ Next: RENAME

≪ Previous: generateChangeLog generates XML header only

Solved my own problem, kind of: https://liquibase.jira.com/browse/CORE-3323 gave me the clue.

I added --defaultSchemaName informix (as, in this case, all my objects were created by this user.)

However, this leads to another problem. In my production environment, I can't guarantee that all existing objects will be created by one user, also it's quite conceivable that even if I find them all today, someone else could add an object with the wrong "owner" in future and I wouldn't know and neither would liquibase.

Is there some shorthand form for "get me all schemas"?

↧

RENAME

March 7, 2019, 6:07 am

≫ Next: Exporting data

≪ Previous: Re : generateChangeLog generates XML header only

I'm not sure how much of this applies to other databases (I suspect a lot!) but Informix has the ability to rename quite a few database objects, including columns, constraints, databases, indexes and tables.

Does liquibase use this functionality?

↧

Exporting data

March 7, 2019, 6:10 am

≫ Next: How do I use --logLevel?

≪ Previous: RENAME

It's not clear to me from the documentation, but I thought that if I did a generateChangeLog, I'd get the data from the database too. However, my exportData directory is stubbornly empty. I also can't find any data-specific commands. What am I doing wrong?

↧

How do I use --logLevel?

March 7, 2019, 6:37 am

≫ Next: Looking for feedback: Liquibase 3.7.0 Alpha 1

≪ Previous: Exporting data

It doesn't seem to matter what I set it to, I don't get anything that looks like additional information?

liquibase --url="jdbc:informix-sqli:INFORMIXSERVER=informix01_tcp;SQLH_TYPE=FILE;SQLH_FILE=/opt/informix/informix/etc/sqlhosts;DATABASE=wallet" --logLevel=debug --logFile=./lb.log --classpath=/opt/informix/informix/jdbc/lib/ifxjdbc.jar --changeLogFile ./test1ChangeLog.xml --includeTablespace=true generateChangeLog

Starting Liquibase at Thu, 07 Mar 2019 12:30:34 GMT (version 3.6.3 built at 2019-01-29 11:34:48)

Unexpected error running Liquibase: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

liquibase.exception.LiquibaseException: liquibase.command.CommandExecutionException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

at liquibase.integration.commandline.CommandLineUtils.doGenerateChangeLog(CommandLineUtils.java:279)

at liquibase.integration.commandline.Main.doMigration(Main.java:1058)

at liquibase.integration.commandline.Main.run(Main.java:199)

at liquibase.integration.commandline.Main.main(Main.java:137)

Caused by: liquibase.command.CommandExecutionException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

at liquibase.command.AbstractCommand.execute(AbstractCommand.java:24)

at liquibase.integration.commandline.CommandLineUtils.doGenerateChangeLog(CommandLineUtils.java:277)

... 3 common frames omitted

Caused by: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

at liquibase.snapshot.jvm.ForeignKeySnapshotGenerator.snapshotObject(ForeignKeySnapshotGenerator.java:223)

at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:66)

at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:49)

at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:69)

at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:49)

at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:69)

at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:49)

at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:286)

at liquibase.snapshot.DatabaseSnapshot.replaceObject(DatabaseSnapshot.java:407)

at liquibase.snapshot.DatabaseSnapshot.includeNestedObjects(DatabaseSnapshot.java:334)

at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:309)

at liquibase.snapshot.DatabaseSnapshot.replaceObject(DatabaseSnapshot.java:407)

at liquibase.snapshot.DatabaseSnapshot.replaceObject(DatabaseSnapshot.java:429)

at liquibase.snapshot.DatabaseSnapshot.includeNestedObjects(DatabaseSnapshot.java:334)

at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:309)

at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:102)

at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:59)

at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:38)

at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:217)

at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:190)

at liquibase.command.core.DiffCommand.createReferenceSnapshot(DiffCommand.java:221)

at liquibase.command.core.DiffCommand.createDiffResult(DiffCommand.java:143)

at liquibase.command.core.GenerateChangeLogCommand.run(GenerateChangeLogCommand.java:46)

at liquibase.command.AbstractCommand.execute(AbstractCommand.java:19)

... 4 common frames omitted

Caused by: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:101)

at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData.getForeignKeys(JdbcDatabaseSnapshot.java:74)

at liquibase.snapshot.jvm.ForeignKeySnapshotGenerator.snapshotObject(ForeignKeySnapshotGenerator.java:127)

... 27 common frames omitted

Caused by: java.sql.SQLException: The cursor has been previously released and is unavailable.

at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:474)

at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:443)

at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:394)

at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3191)

at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3472)

at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2379)

at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2304)

at com.informix.jdbc.IfxSqli.executeFetch(IfxSqli.java:2038)

at com.informix.jdbc.IfxSqli.getaRow(IfxSqli.java:4082)

at com.informix.jdbc.IfxResultSet.next(IfxResultSet.java:494)

at com.informix.jdbc.IfxDatabaseMetaData.getImportedKeys(IfxDatabaseMetaData.java:5389)

at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$1.fastFetch(JdbcDatabaseSnapshot.java:126)

at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:70)

... 29 common frames omitted

Caused by: java.sql.SQLException: null

at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:474)

at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:443)

at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:394)

at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3477)

... 37 common frames omitted

For more information, please use the --logLevel flag

liquibase --url="jdbc:informix-sqli:INFORMIXSERVER=informix01_tcp;SQLH_TYPE=FILE;SQLH_FILE=/opt/informix/informix/etc/sqlhosts;DATABASE=wallet" --logLevel=severe --logFile=./lb.log --classpath=/opt/informix/informix/jdbc/lib/ifxjdbc.jar --changeLogFile ./test1ChangeLog.xml --includeTablespace=true generateChangeLog

Starting Liquibase at Thu, 07 Mar 2019 12:33:46 GMT (version 3.6.3 built at 2019-01-29 11:34:48)