You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ravi Prakash (JIRA)" <ji...@apache.org> on 2015/04/10 20:25:12 UTC
[jira] [Updated] (OOZIE-2198) OozieDBCLI doesn't show any
information on why it thinks a schema doesn't exist
[ https://issues.apache.org/jira/browse/OOZIE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ravi Prakash updated OOZIE-2198:
--------------------------------
Attachment: OOZIE-2198.01.patch
Simple enough patch.
> OozieDBCLI doesn't show any information on why it thinks a schema doesn't exist
> -------------------------------------------------------------------------------
>
> Key: OOZIE-2198
> URL: https://issues.apache.org/jira/browse/OOZIE-2198
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: 4.1.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Priority: Minor
> Attachments: OOZIE-2198.01.patch
>
>
> When running ooziedb.sh upgrade, I got this error:
> {code}
> Validate DB Connection
> DONE
> Check DB schema exists
> Error: DB schema does not exist
> Stack trace for the error was (for debug purposes):
> --------------------------------------
> java.lang.Exception: DB schema does not exist
> at org.apache.oozie.tools.OozieDBCLI.validateDBSchema(OozieDBCLI.java:883)
> at org.apache.oozie.tools.OozieDBCLI.upgradeDB(OozieDBCLI.java:196)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:76)
> {code}
> It doesn't tell me anything about why it thinks no schema exists. We should surface the exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)