[
https://issues.apache.org/jira/browse/OOZIE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890304#comment-13890304
]
Robert Kanter commented on OOZIE-1684:
--------------------------------------
Yes, its working.
----
This might be the cause of the error you saw before during your testing:
When trying to create the database using Oozie 3.3.0 and Oozie 4 I was running
into some issues; I was using a different schema/database ("zee") than the
default ("oozie") because I was borrowing someone else's Oracle. I later
discovered it was an Oracle bug (BUG 9577583) where:
{noformat}
ORA-942, or other unexpected errors, can occur when running in a setup
where multiple schemas have identical objects and users are only expected
to access objects in their own schemas.
{noformat}
We saw in the logs that my Oozie was sometimes trying to use the "oozie" schema
instead of the "zee" schema when both existed. I accidentally dropped the
"oozie" schema, and the problem went away so I was able to create the schema
using 3.3.0 and 4.0.0. We didn't realize until later that dropping the "oozie"
schema got rid of that error; when I was done and he started trying to use the
"oozie" schema and it was using the "zee" schema instead.
Were there multiple Oozie schemas in your Oracle database? Perhaps you ran
into something similar during your testing before?
I couldn't find the Oracle bug database, but here's a forum post mentioning the
bug: http://www.orafaq.com/forum/mv/msg/160665/472337/#msg_472337
And here's an issue filed 3 years ago on the Yahoo! github specifically for
Oozie having this problem; I guess we never implemented a workaround and Oracle
never fixed it...
https://github.com/yahoo/oozie/issues/39
> 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)
