You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/05/16 19:17:18 UTC

[jira] [Commented] (AMBARI-2144) Installation with existing Oracle DB fails

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

Sumit Mohanty commented on AMBARI-2144:
---------------------------------------

+1, LGTM.
                
> Installation with existing Oracle DB fails
> ------------------------------------------
>
>                 Key: AMBARI-2144
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2144
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.2.4
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.2.4
>
>         Attachments: AMBARI-2144.patch
>
>
> On Step8 "Customize Services" for HIVE and OOZIE we can use option "Existing Oracle DB".
> But after Cluster install HIVE and OOZIE didn't start (with option "Existing Oracle DB").
> In the logs I found such:
> */var/log/hive/hive.log*
> {code}
> Caused by: org.datanucleus.exceptions.NucleusException: Attempt to invoke the "DBCP" plugin to create a ConnectionPool gave an error : The specified datastore driver ("oracle.jdbc.driver.OracleDriver") was not found in the CLASSPATH. Please check your CLASSPATH specification, and the name of the driver.
> {code}
> */var/log/oozie/oozie.log*
> {code}
> 013-05-14 11:25:59,618 FATAL Services:533 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] E0103: Could not load service classes, Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver'
> org.apache.oozie.service.ServiceException: E0103: Could not load service classes, Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver'
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira