Problem
When executing an upgrade of the Datameer database, the following error and stacktrace is returned:
[datameer@myhost /opt/datameer/current/bin]$ ./upgrade_db.sh Java 7 found Executing upgrade script for Datameer Detecting Datameer schema version from current database .. Current database version is: 4.3.0 DeployMode: live Exception in thread 'main' java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.ensureError(J9VMInternals.java:167) at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:156) at datameer.dap.common.license.cb.getPreferences(Unknown Source) at datameer.dap.common.license.v.b(Unknown Source) at datameer.dap.common.license.v.(Unknown Source) at datameer.dap.conductor.tool.upgrade.UpgradePreconditions.main(UpgradePreconditions.java:66) Caused by: datameer.com.google.common.base.VerifyException: Path 'conf' to properties files does not exist or is not readable at datameer.com.google.common.base.Verify.verify(Verify.java:123) at datameer.base.DatameerProperties.(DatameerProperties.java:82) at datameer.base.DatameerProperties.initializeIfNorAlready(DatameerProperties.java:189) at datameer.base.DatameerProperties.asImmutableMap(DatameerProperties.java:101) at datameer.base.DatameerProperties.getProperty(DatameerProperties.java:159) at datameer.dap.common.license.x.c(Unknown Source) at datameer.dap.common.license.x.d(Unknown Source) at datameer.dap.common.license.x.(Unknown Source) at datameer.dap.common.license.cb$_b.(Unknown Source) ... 4 more
Cause
This is caused by executing the upgrade_db.sh script directly within the <INSTALLDIR>/bin directory.
Solution
To resolve this issue, re-run the upgrade script directly from the <INSTALLDIR> and preface the script with the bin directory:
[datameer@myhost /opt/datameer/current]$ bin/upgrade_db.sh
Comments
0 comments
Please sign in to leave a comment.