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:36:38 UTC

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

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

Pradeep Agrawal commented on RANGER-1417:
-----------------------------------------

Patch committed in Apache Ranger master branch : 
https://github.com/apache/ranger/commit/759a7b3e61bf281906c6384d47a7f6de25dc791c
Patch committed in Apache Ranger 0.7 branch : 
https://github.com/apache/ranger/commit/16cc0d30c08dd7ffe17095c451062203f32c26db

> Ranger Upgrade is failing for Oracle DB flavor
> ----------------------------------------------
>
>                 Key: RANGER-1417
>                 URL: https://issues.apache.org/jira/browse/RANGER-1417
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 0.7.0
>            Reporter: Pradeep Agrawal
>            Assignee: Pradeep Agrawal
>             Fix For: 0.7.1
>
>         Attachments: RANGER-1417-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.
> *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'.



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