Hi, 
I currently am using Hive with the metadata store backed in MS SQL Server.

I am now starting to use Oozie, and was wondering if anyone has had success in 
changing the store to SQL Server?
The 4 properties that I have changed in oozie-site.xml are:

   <property>
        <name>oozie.service.JPAService.jdbc.driver</name>
        <value>com.microsoft.sqlserver.jdbc.SQLServerDriver</value>
    </property>

    <property>
        <name>oozie.service.JPAService.jdbc.url</name>
       <value>jdbc:sqlserver://servername;databaseName=ooziemeta</value>
    </property>

    <property>
        <name>oozie.service.JPAService.jdbc.username</name>
        <value>hivemeta</value>
    </property>

    <property>
        <name>oozie.service.JPAService.jdbc.password</name>
        <value>password</value>
    </property>

I also edited the oozie.sql file and changed the offending types to the SQL 
Server compatible types, and ran this as a manual step once I created the 
database.

Now, when I try to start oozie, in my catalina.out file I get the following 
error:
   resource [META-INF/oozie-sqlserver-orm.xml] not found

I have installed oozie in /usr/share/oozie, so I added the following file:
/usr/share/oozie/oozie-server/webapps/oozie/META-INF/oozie-sqlserver-orm.xml

And copied the contents from 
http://grepcode.com/file/repository.cloudera.com/content/repositories/releases/org.apache.oozie/oozie-core/3.2.0-cdh4.1.0/META-INF/oozie-postgresql-orm.xml?av=f

With a modification for the sequence type to map to identity.

But, I still get the same error, it is as if this file location is incorrect.  
I am not sure if a new build is required.  Does anyone have any suggestions or 
have they been able to add additional orm.xml files?

Thank you very much,
Robert



(the full catalina.out output is below this line)
Nov 30, 2012 11:21:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the java.library.path: 
/usr/lib/jvm/jdk1.6.0_37/jre/lib/amd64/server:/usr/lib/j$
Nov 30, 2012 11:21:57 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-11000
Nov 30, 2012 11:21:57 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1047 ms
Nov 30, 2012 11:21:57 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Nov 30, 2012 11:21:57 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
Nov 30, 2012 11:21:57 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor oozie.xml
Nov 30, 2012 11:21:58 PM org.apache.catalina.loader.WebappClassLoader 
validateJarFile
INFO: 
validateJarFile(/usr/share/oozie/oozie-server/webapps/oozie/WEB-INF/lib/servlet-api-2.5-20081211.jar)
 - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: 
javax/servlet/Servlet.cla$

ERROR: Oozie could not be started

REASON: org.apache.oozie.service.ServiceException: E0103: Could not load 
service classes, resource [META-INF/oozie-sqlserver-orm.xml] not found

Stacktrace:
-----------------------------------------------------------------
org.apache.oozie.service.ServiceException: E0103: Could not load service 
classes, resource [META-INF/oozie-sqlserver-orm.xml] not found
        at org.apache.oozie.service.Services.loadServices(Services.java:281)
        at org.apache.oozie.service.Services.init(Services.java:202)
        at 
org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:39)
        at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)
        at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)
        at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
        at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
        at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
        at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
        at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
        at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
        at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
        at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
        at 
org.apache.catalina.core.StandardService.start(StandardService.java:525)
        at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: java.lang.IllegalArgumentException: resource 
[META-INF/oozie-sqlserver-orm.xml] not found
        at org.apache.oozie.util.IOUtils.getResourceAsStream(IOUtils.java:103)
        at org.apache.oozie.service.JPAService.init(JPAService.java:127)
        at 
org.apache.oozie.service.Services.setServiceInternal(Services.java:358)
        at org.apache.oozie.service.Services.setService(Services.java:344)
        at org.apache.oozie.service.Services.loadServices(Services.java:278)
        ... 26 more
-----------------------------------------------------------------


Reply via email to