dbupdate utility not running

Hi,

I’m trying to use the dbupdate utility for database initialisation for a deployed app and the problem is it doesn’t run. Appreciate if you can help point me to the step to troubleshoot. Below is the dbupdate output:

17:56:50,474 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
17:56:50,475 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
17:56:50,475 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/opt/tomcat8/shared/lib/cuba-shared-lib-6.2.2.jar!/logback.xml]
17:56:50,493 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@6e3c1e69 - URL [jar:file:/opt/tomcat8/shared/lib/cuba-shared-lib-6.2.2.jar!/logback.xml] is not of type file
17:56:50,625 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
17:56:50,638 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [Console]
17:56:50,694 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
17:56:50,752 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [Console] to Logger[ROOT]
17:56:50,754 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba] to DEBUG
17:56:50,755 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.core.sys] to INFO
17:56:50,756 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.core.sys.CubaDefaultListableBeanFactory] to WARN
17:56:50,756 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.core.app.scheduling] to INFO
17:56:50,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.web.sys] to INFO
17:56:50,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.portal] to INFO
17:56:50,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.core.app.LockManager] to INFO
17:56:50,758 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [eclipselink] to WARN
17:56:50,758 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [eclipselink.sql] to INFO
17:56:50,758 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework] to WARN
17:56:50,759 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.activiti] to INFO
17:56:50,759 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [freemarker] to INFO
17:56:50,760 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.thymeleaf.TemplateEngine] to INFO
17:56:50,760 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.docx4j] to WARN
17:56:50,760 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.xlsx4j] to WARN
17:56:50,761 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.hibernate] to WARN
17:56:50,761 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [sun] to INFO
17:56:50,762 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.sun] to INFO
17:56:50,764 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [javax] to INFO
17:56:50,764 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache] to INFO
17:56:50,764 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.perf4j.TimingLogger] to OFF
17:56:50,765 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.haulmont.cuba.gui.logging.UIPerformanceLogger] to OFF
17:56:50,765 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
17:56:50,768 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@5afa04c - Registering current configuration as safe fallback point
usage: dbupdate
 -check                           Print update scripts
 -create                          Create database
 -dbPassword <password>           Database password
 -dbType <dbType>                 DBMS type: postgres|mssql|oracle|etc
 -dbUrl <connectionString>        JDBC Database URL
 -dbUser <userName>               Database user
 -dbVersion <dbVersion>           DBMS version: 2012|etc
 -executeGroovy <executeGroovy>   Ignoring Groovy scripts
 -help                            Print help
 -scriptsDir <filePath>           Database scripts directory
 -update                          Update database

What command line options do you provide to the utility?

I run the utility with ‘create’ option as per the following command line :

sudo sh dbupdate.sh postgres postgres123 create

I’m sorry but it seems that command-line utility is broken. We’ll fix it in the next bug-fix release.
I’d suggest using cuba.automaticDatabaseUpdate application property on your production server to run the update scripts on server start. This is the most common approach in our practice.

Ok thanks.

The problem is fixed in the platform 6.2.6.