![]() ![]() ![]() Oracle Database 11g Enterprise Edition Release 11.2.0.2.0. ![]() OpenJDK 64-Bit Server VM (Zulu 8.44.0.11-CA-macosx) (build.OpenJDK Runtime Environment (Zulu 8.44.0.11-CA-macosx) (build.They've been deleted, but the problem still exists. I did find an old view and trigger that were created during research for the project for a different schema, which were never run in this one (neither was in this DATABASECHANGELOG). : Īt .AbstractChangeLogParser.parse(AbstractChangeLogParser.java:25) ~Īt (Liquibase.java:217) ~Īt (Liquibase.java:190) ~Īt (Liquibase.java:179) ~Īt .doMigration(Main.java:1223) Īt .run(Main.java:209) Īt .main(Main.java:132) Ĭaused by: : nullĪt (DatabaseChangeLog.java:531) ~Īt (DatabaseChangeLog.java:398) ~Īt (DatabaseChangeLog.java:308) ~Īt .AbstractChangeLogParser.parse(AbstractChangeLogParser.java:23) ~Ĭaused by: : nullĪt (AbstractCollection.java:343) ~Īt .list(CommandLineResourceAccessor.java:44) ~Īt (CompositeResourceAccessor.java:40) ~Īt (DatabaseChangeLog.java:506) ~įor more information, please use the -logLevel flag Unexpected error running Liquibase: Unknown reason I can run every db.changelog-*.xml file (except master) from the command line (using update) and everything succeeds.īut when I try and run the db.changelog-master file, I get: Starting Liquibase at Tue, 11:49:47 CDT (version 3.8.0 built at ) I can run every changelog/feature/*.xml file from the command line (using update) and everything succeeds. However, on the project I'm currently working on, I'm encountering an issue I don't seem to be able to find the cause. Been using Liquibase a long time, and love it. ![]()
0 Comments
Leave a Reply. |