[jira] [Updated] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
[ https://issues.apache.org/jira/browse/AMBARI-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-15390: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. > Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar > --- > > Key: AMBARI-15390 > URL: https://issues.apache.org/jira/browse/AMBARI-15390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15390.patch > > > PROBLEM: > When set up jdbc driver with > ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar > and see that it is properly set up in /var/lib/ambari-server/resources, and > also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, > Ambari copies the jar but name it 'ojdbc6.jar' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
[ https://issues.apache.org/jira/browse/AMBARI-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-15390: --- Status: Patch Available (was: Open) > Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar > --- > > Key: AMBARI-15390 > URL: https://issues.apache.org/jira/browse/AMBARI-15390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15390.patch > > > PROBLEM: > When set up jdbc driver with > ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar > and see that it is properly set up in /var/lib/ambari-server/resources, and > also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, > Ambari copies the jar but name it 'ojdbc6.jar' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
[ https://issues.apache.org/jira/browse/AMBARI-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-15390: --- Attachment: AMBARI-15390.patch > Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar > --- > > Key: AMBARI-15390 > URL: https://issues.apache.org/jira/browse/AMBARI-15390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15390.patch > > > PROBLEM: > When set up jdbc driver with > ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar > and see that it is properly set up in /var/lib/ambari-server/resources, and > also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, > Ambari copies the jar but name it 'ojdbc6.jar' -- This message was sent by Atlassian JIRA (v6.3.4#6332)