Hi Monika, It looks like it's trying to connect with:
"Driver: org.postgresql.Driver" (according to the output of your "dspace database test") This implies that your dspace.cfg probably has the wrong value for "db.driver". It should be: db.driver=oracle.jdbc.OracleDriver So you may want to update this in your dspace.cfg and try again. Also may want to update it in your "build.properties" (as that's what populates the dspace.cfg). In the case of vagrant-dspace, it uses a custom "vagrant.properties" by default. - Tim On 6/18/2015 1:33 PM, Monika C. Mevenkamp wrote: > I got myself dspace vagrant > switched to dspace_5_x branch > setup to run with Oracle via settings in dspace.cfg > copied ~/.m2/repository/com/oracle/ojdbc6 from my host to vagrants ~/.m2 > did mvn package with -Ddb.name=oracle > > I can successfully run > > ~/dspace/bin/dspace database test > > Attempting to connect to database using these configurations: > - URL: jdbc:oracle:thin:@xyz.princeton.edu > <http://xyz.princeton.edu>:1521:dspdevl > - Driver: org.postgresql.Driver > - Username: dspace > - Password: [hidden] > - Schema: > > Testing connection... > Connected successfully! > > > > localist:8081/probe tells me that jspui, xmlii, oia, rdf did not come up > there are exceptions in catalina.out > java.sql.SQLException: No suitable driver found for > jdbc:oracle:thin:@xyz.princeton.edu <http://xyz.princeton.edu>:1521:dspdevl > > but the jar is available to all webs - according to ls > > ls -ld ~/dspace/webapps/*/WEB-INF/lib/ojdbc6-11.2.0.4.jar > ~/dspace/lib/ojdbc6-11.2.0.4.jar > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/jspui/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/oai/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/rdf/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/rest/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/swordv2/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/sword/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > -rw-rw-r-- 1 vagrant vagrant 2739670 Jun 18 17:28 > */home/vagrant/dspace/webapps/xmlui/WEB-INF/lib/ojdbc6-11.2.0.4.jar* > * > * > catalina.out also complains > SEVERE: The web application [/xmlui] registered the JDBC driver > [org.postgresql.Driver] but failed to unregister it when the web > application was stopped. To prevent a memory leak, the JDBC Driver has > been forcibly unregistered. > > Obviously the postgres driver should never be registered. Any ideas > where that might happen and how to turn this off ? > > Monika > > > > — > Monika Mevenkamp > Digital Repository Infrastructure Developer > Phone: 609-258-4161 > 333C 701 Carnegie, Princeton University, Princeton, NJ 08544 > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > ------------------------------------------------------------------------------ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
