You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/05/29 21:48:20 UTC
[jira] [Updated] (AMBARI-2223) Using an external MySQL / Oracle
database for Oozie does not work
[ https://issues.apache.org/jira/browse/AMBARI-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-2223:
------------------------------------
Attachment: AMBARI-2223.patch
> Using an external MySQL / Oracle database for Oozie does not work
> -----------------------------------------------------------------
>
> Key: AMBARI-2223
> URL: https://issues.apache.org/jira/browse/AMBARI-2223
> 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-2223.patch
>
>
> When setting up Oozie with an external database, the following commands are run:
> {code}
> cd /var/tmp/oozie && /usr/lib/oozie/bin/oozie-setup.sh -hadoop 0.20.200 /usr/lib/hadoop/ -extjs /usr/share/HDP-oozie/ext.zip -jars /usr/lib/hadoop/lib/hadoop-lzo-0.5.0.jar:/usr/share/java/mysql-connector-java.jar
> {code}
> The above command succeeds.
> However, the next command fails:
> {code}
> cd /var/tmp/oozie && /usr/lib/oozie/bin/ooziedb.sh create -sqlfile oozie.sql -run
> setting OOZIE_CONFIG=${OOZIE_CONFIG:-/etc/oozie/conf}
> setting OOZIE_DATA=${OOZIE_DATA:-/var/lib/oozie}
> setting OOZIE_LOG=${OOZIE_LOG:-/var/log/oozie}
> setting CATALINA_BASE=${CATALINA_BASE:-/var/lib/oozie/oozie-server}
> setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
> setting CATALINA_PID=${CATALINA_PID:-/var/run/oozie/oozie.pid}
> setting JAVA_HOME=/usr/jdk/jdk1.6.0_31
> setting OOZIE_LOG=/var/log/oozie/
> setting CATALINA_PID=/var/run/oozie/oozie.pid
> setting OOZIE_DATA=/grid/0/hadoop/oozie/data/
> setting JAVA_LIBRARY_PATH=/usr/lib/hadoop/lib/native/Linux-amd64-64
> Validate DB Connection
> Error: Could not connect to the database: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
> Stack trace for the error was (for debug purposes):
> --------------------------------------
> java.lang.Exception: Could not connect to the database: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
> at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:358)
> at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:168)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:112)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:63)
> Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:169)
> at org.apache.oozie.tools.OozieDBCLI.createConnection(OozieDBCLI.java:347)
> at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:354)
> ... 3 more
> --------------------------------------
> {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