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 <pr...@freestoneinfotech.com> on 2017/03/06 08:25:30 UTC

Review Request 57328: RANGER-1417 : Ranger Upgrade is failing for Oracle DB flavor

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57328/
-----------------------------------------------------------

Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.

Bugs: RANGER-1423
https://issues.apache.org/jira/browse/RANGER-1423

Repository: ranger

Description
-------

**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 Ranger 0.6 version** : db_setup.py can identify java patches that are marked as 'N' but not updated recently by Ranger Admin install process; If java patches is have active status 'N' and its entry was created in x_db_version_h table 24 hour before then we can marked such entries status to 'Y' and upgrade process shall continue.

Diffs
-----

security-admin/scripts/db_setup.py c1efd4a

Diff: https://reviews.apache.org/r/57328/diff/1/

Testing
-------

**Use Case: Ranger install case(Ranger 0.6)**
Steps performed(with patch) :
1. Installed and started 0.6 version of Ranger admin for Oracle DB flavor.
2. From installation log messages it was observed that java patches have been executed.
3. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not.
SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';
From output of above sql statement it was observed that though patches have been applied their active status is not set to ='Y'.
4. Stop Ranger admin.
5. Took Ranger latest code from master; applied patch and created build. Unzipped the generated tar file and in install.properties provided Ranger db configuration which were used in last Ranger installation.
6. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not.
SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';

**Expected Behaviour:**
output of above sql statement should state that all java patches have been applied, this can be determine by referring active column of output where active column value must be 'Y'.

**Actual Behaviour:**
From output of above sql statement it was observed that active column value was set to 'Y' and additional java patches have also been applied successfully.

Thanks,

Pradeep Agrawal

Re: Review Request 57328: RANGER-1423 : Ranger Upgrade is failing for Oracle DB flavor

Posted by Velmurugan Periasamy <vp...@hortonworks.com>.

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57328/#review168236
-----------------------------------------------------------


Ship it!




Ship It!

- Velmurugan Periasamy


On March 6, 2017, 8:26 a.m., Pradeep Agrawal wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57328/
> -----------------------------------------------------------
> 
> (Updated March 6, 2017, 8:26 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1423
>     https://issues.apache.org/jira/browse/RANGER-1423
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> **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 Ranger 0.6 version** : db_setup.py can identify java patches that are marked as 'N' but not updated recently by Ranger Admin install process; If java patches is have active status 'N' and its entry was created in x_db_version_h table 24 hour before then we can marked such entries status to 'Y' and upgrade process shall continue.
> 
> 
> Diffs
> -----
> 
>   security-admin/scripts/db_setup.py c1efd4a 
> 
> 
> Diff: https://reviews.apache.org/r/57328/diff/1/
> 
> 
> Testing
> -------
> 
> **Use Case: Ranger install case(Ranger 0.6)**
> Steps performed(with patch) :
> 1. Installed and started 0.6 version of Ranger admin for Oracle DB flavor.
> 2. From installation log messages it was observed that java patches have been executed.
> 3. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not.
> SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';
> From output of above sql statement it was observed that though patches have been applied their active status is not set to ='Y'.
> 4. Stop Ranger admin.
> 5. Took Ranger latest code from master; applied patch and created build. Unzipped the generated tar file and in install.properties provided Ranger db configuration which were used in last Ranger installation.
> 6. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not.
> SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';
> 
> **Expected Behaviour:**
> output of above sql statement should state that all java patches have been applied, this can be determine by referring active column of output where active column value must be 'Y'.
> 
> **Actual Behaviour:**
> From output of above sql statement it was observed that active column value was set to 'Y' and additional java patches have also been applied successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>