Alejandro and Harsh J, thanks for the information.

I will file a JIRA, and if I do get it to work I'll include the changes to 
hopefully make it easier.
In the meantime, I will use MySQL to get more familiar with Oozie.

Thanks again,
Robert

-----Original Message-----
From: Alejandro Abdelnur [mailto:[email protected]] 
Sent: Saturday, December 01, 2012 12:17 PM
To: [email protected]
Subject: Re: SQL Server as an alternative to derby/mySQL/Oracle?postgreSQL?

In addition, currently Oozie supports derby/mysql/postgres/oracle DBs, it does 
not support ms sqlserver.

It will require modifying the persistence.xml file and creating a custom ORM 
file for ms sqlserver.

I'd suggest opening a JIRA, I'll be glad to help adding support for another DB.

Thx




On Sat, Dec 1, 2012 at 7:48 AM, Harsh J <[email protected]> wrote:

> I don't think dropping the file into the extracted WAR directory (as 
> you have done), would be the right approach to do this. Instead, could 
> you regenerate your WAR file by running oozie-setup.sh after having 
> made your changes, and then work off of this newly generated oozie.war 
> file?
>
> On Sat, Dec 1, 2012 at 6:37 AM, Robert Towne 
> <[email protected]>
> wrote:
> > A little more information, I went back to the original unpacked tar, 
> > and
> added the file to the source prior to running "mkdistro.sh -DskipTests 
> ", and then used that updated distro.
> > Now, I get past the original error and I am getting:
> >
> > ERROR: Oozie could not be started
> >
> > REASON: org.apache.oozie.service.ServiceException: E0103: Could not 
> > load
> service classes,
> > No persistence providers available for "oozie-sqlserver" after 
> > trying
> the following discovered implementations:
> org.apache.openjpa.persistence.PersistenceProviderImpl
> >
> > Stacktrace:
> > -----------------------------------------------------------------
> > org.apache.oozie.service.ServiceException: E0103: Could not load 
> > service
> classes, No persistence providers available for "oozie-sqlserver" 
> after trying the following discovered implementations: org.apache.$
> >         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(ServicesLoa
> der.java:39)
> >         at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext
> .java:4205)
> >         at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:47
> 04)
> >         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.jav
> a:675)
> >         at
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.ja
> va: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(Lifecycle
> Support.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:52
> 5)
> >         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.j
> ava:39)
> >         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.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: javax.persistence.PersistenceException: No persistence
> providers available for "oozie-sqlserver" after trying the following 
> discovered implementations: 
> org.apache.openjpa.persistence.Persistence$
> >         at
> javax.persistence.Persistence.createEntityManagerFactory(Persistence.j
> ava:182)
> >         at org.apache.oozie.service.JPAService.init(JPAService.java:156)
> >         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
> > -----------------------------------------------------------------
>
>
>
> --
> Harsh J
>



--
Alejandro

Reply via email to