[
https://issues.apache.org/jira/browse/OOZIE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890229#comment-13890229
]
Virag Kothari commented on OOZIE-1684:
--------------------------------------
In my test with Oracle, it was trying to create existing tables and failing
even if the upgrade parameter was passed. So I had to hack that if condition
for Oracle. But if its working fine for you, we can revert it back. What is the
version of oracle you are testing on?
> DB upgrade from 3.3.0 to trunk fails on Oracle
> ----------------------------------------------
>
> Key: OOZIE-1684
> URL: https://issues.apache.org/jira/browse/OOZIE-1684
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: OOZIE-1684.patch
>
>
> Similar issue to OOZIE-1674, but for Oracle instead of Postgres. Upgrading
> from a database created by Oozie 3.3.0 (DB version 1) to the current trunk
> (DB version 3) fails with this error:
> {noformat}
> java.sql.SQLSyntaxErrorException: ORA-00904: "PUSH_MISSING_DEPENDENCIES":
> invalid identifier
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at
> oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:873)
> at
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)
> at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)
> at
> oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1491)
> at
> oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:406)
> at
> org.apache.oozie.tools.OozieDBCLI.convertClobToBlobInOracle(OozieDBCLI.java:458)
> at org.apache.oozie.tools.OozieDBCLI.ddlTweaksFor50(OozieDBCLI.java:626)
> at org.apache.oozie.tools.OozieDBCLI.upgradeDBto50(OozieDBCLI.java:240)
> at org.apache.oozie.tools.OozieDBCLI.upgradeDB(OozieDBCLI.java:220)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:76)
> {noformat}
> After more investigation, it turns out that if you do the 3.3.0 (version 1)
> to trunk (version 3) upgrade, any columns or tables added in 4.0.0 (version
> 2) are not actually added to the database (though they do get printed into
> the sql file).
> More specifically:
> - {{COORD_ACTIONS.PUSH_MISSING_DEPENDENCIES}} column
> - {{WF_ACTIONS.CREATED_TIME}} column
> - {{SLA_REGISTRATION}} table
> - {{SLA_SUMMARY}} table
> - Possibly other changes?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
