[ 
https://issues.apache.org/jira/browse/OOZIE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890385#comment-13890385
 ] 

Hadoop QA commented on OOZIE-1684:
----------------------------------

Testing JIRA OOZIE-1684

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1388
.    Tests failed: 0
.    Tests errors: 1

.    The patch failed the following testcases:

.      

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1041/

> 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)

Reply via email to