You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Pradeep Agrawal (JIRA)" <ji...@apache.org> on 2017/03/08 04:45:38 UTC

[jira] [Commented] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor

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

Pradeep Agrawal commented on RANGER-1423:
-----------------------------------------

Patch committed in Ranger 0.6 branch : https://github.com/apache/ranger/commit/9561f0d5b31f2bf48147df2171b0dceff8f5000c

> CLONE - Ranger Upgrade is failing for Oracle DB flavor
> ------------------------------------------------------
>
>                 Key: RANGER-1423
>                 URL: https://issues.apache.org/jira/browse/RANGER-1423
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 0.6.0
>            Reporter: Pradeep Agrawal
>            Assignee: Pradeep Agrawal
>             Fix For: 0.6.4
>
>         Attachments: RANGER-1423-1.patch
>
>
> *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. 
> *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)