Customers
User information
 Loading ...
Show article in Knowledge Base

 If all liquibase scripts do not execute correctly during upgrade, can I re‑run the missing scripts? Export knowledge base Export     SubscribeSubscribe      Show article info

If you run into a problem with an upgrade or installation of the system you should never proceed unless you've been in contact with our support team, instead you should rollback and then re-try installation with a new database or a fresh database copy. 

 

If you have been in contact with our support team and thereafter should re-run some liquibase scripts, you can follow the instructions below, this will execute the remaining scripts missing in the database.

 

1.) Move a copy of your live database to your test system, and follow the normal steps for this.

2.) Continue with steps below on a database copy first.

3.) Stop the system (Apache Tomcat) to make sure no-one is using it.

4.) Execute the query in the database: SELECT * FROM databasechangelog ORDER BY dateexecuted DESC LIMIT 10 

5.) Open a command prompt
6.) Go to TOMCAT_HOME/webapps/ROOT/WEB-INF/changelog
7.) Execute the following command below. Note: Change the jdbc url to match your environment, if you're unsure check visionproject_database.properties

 

For windows:

 

java -cp "..\lib\*;..\internal_docs\installed_version\configuration\chatmodule\logback-core-1.2.3.jar;..\internal_docs\installed_version\configuration\chatmodule\logback-classic-1.2.3.jar;..\classes" liquibase.integration.commandline.Main --contexts=installed --changeLogFile=db-changelog-master.xml --url=jdbc:mysql://localhost:3306/databasename?useSSL=false --username=username --password=password update

 

Or this for Linux:

 

java -cp "../lib/*:../internal_docs/installed_version/configuration/chatmodule/logback-core-1.2.3.jar:../internal_docs/installed_version/configuration/chatmodule/logback-classic-1.2.3.jar:../classes" liquibase.integration.commandline.Main --contexts=installed --changeLogFile=db-changelog-master.xml --url=jdbc:mysql://localhost:3306/databasename?useSSL=false --username=username --password=password update

8.) When executing the scripts above there can be some logging related warns in the CMD like the ones below, but these can be ignored. However, to be on the safe side  please copy the log-messages from the console and send to our support team.

 

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/Ivan/Downloads/vf/installed/vf-installed-mysql/WEB-INF/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/Ivan/Downloads/vf/installed/vf-installed-mysql/WEB-INF/internal_docs/installed_version/configuration/chatmodule/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2020-10-12 11:56:11,824 main ERROR Unable to locate appender "velocity" for logger config "org.apache.velocity"
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Liquibase command line logging cannot be configured; a supported org.slf4j.Logger implementation is not on the classpath.
they can be ignored

 

9.) If there are no problems above then proceed

10.) Execute the query in the database: SELECT * FROM databasechangelog ORDER BY dateexecuted DESC LIMIT 10 

11.) Verify above to make sure that database contains rows for the remaining scrips missing in 3.) compared to the db-changelog-master.xml file

12.) Start the system and do some basic testing to verify that everything works OK.

13.) Perform steps 3-12 again on live system.


User comments
 Loading ...