This sounds more like a configuration or setup issue to me. I don't think you have a code problem, as the core error says "Cannot load JDBC driver class 'oracle.jdbc.OracleDriver'" That implies to me that either DSpace cannot find your JDBC driver at all...or the JDBC driver you are providing to DSpace doesn't have the expected "oracle.jdbc.OracleDriver" class... or your DSpace database configuration is incorrect.
You might try a simple "./dspace database test" and "./dspace database info" to ensure your Oracle driver is being picked up from commandline. If it's being picked up there, it's possible it's only available in "dspace/lib" and NOT available in the webapps. Just a few ideas Tim On Wed, Sep 12, 2018 at 2:40 PM Diego Spano <[email protected]> wrote: > Thanks Tim. The only file I changed is the one mentioned here: > > https://patch-diff.githubusercontent.com/raw/DSpace/DSpace/pull/2112.diff > > I need to fix the problem with OAI Identify and Oracle!. Could this change > be related with error I have? > > > El miércoles, 12 de septiembre de 2018, 16:32:58 (UTC-3), Tim Donohue > escribió: > >> Hi Diego, >> >> As far as I'm aware, there were no changes between 6.2 and 6.3 regarding >> how DSpace connects to Oracle. In minor releases we only provide bug fixes >> or minor improvements (like dependency updates). We also didn't change the >> version of the Oracle JDBC driver between these releases: >> https://github.com/DSpace/DSpace/blob/dspace-6.2/pom.xml#L1279 >> https://github.com/DSpace/DSpace/blob/dspace-6.3/pom.xml#L1282 >> >> It's always possible that some other bug fix could have accidentally >> broken some behavior. I don't see any that look likely, but I'd encourage >> you to review the changes that were made in 6.3 here: >> https://wiki.duraspace.org/display/DSPACE/DSpace+Release+6.3+Status >> (There were some bug fixes to Oracle functionality, but nothing with regard >> to the JDBC driver or similar.) >> >> I'm not entirely sure what else to suggest here, but hopefully that gives >> you a few clues to start with. If anyone else is seeing similar behavior >> (or has been running 6.3 on Oracle successfully), hopefully they'll respond >> to this email list thread. >> >> Tim >> >> >> >> On Wed, Sep 12, 2018 at 2:18 PM Diego Spano <[email protected]> wrote: >> >>> Hi Helix. I followed those steps before. In the same server I had Dspace >>> 6.2 installed and running with the same ORACLE config. The problem appears >>> trying to update to DSpace 6.3. Is there any difference between 6.2 and 6.3 >>> in the way they connect to Oracle? >>> Thanks >>> >>> Diego >>> >>> >>> El miércoles, 12 de septiembre de 2018, 16:09:04 (UTC-3), helix84 >>> escribió: >>> >>>> Why not follow installation instructions for the Oracle .jar? >>>> >>>> >>>> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Oracle10gorlater >>>> >>> >>>> >>>> Regards, >>>> ~~helix84 >>>> >>>> Compulsory reading: DSpace Mailing List Etiquette >>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >>>> >>>> >>>> On Wed, Sep 12, 2018 at 8:55 PM Diego Spano <[email protected]> wrote: >>>> >>> Hi. I download Dspace-6.3-src. Mvn run ok but ant update displayed an >>>>> error about JDBC driver. So, I copied "ojdbc6.jar" into >>>>> /dspace-source/dspace/target/dspace_installer/lib" and run ant again. The >>>>> process finishes almost OK. It displays the following before ending: >>>>> >>>>> test_database: >>>>> [java] 2018-09-12 15:46:41,820 WARN >>>>> org.dspace.services.email.EmailServiceImpl @ Couldn't get an email session >>>>> from environment: Need to specify class name in environment or system >>>>> property, or as an applet parameter, or in an application resource file: >>>>> java.naming.factory.initial >>>>> [java] >>>>> [java] Attempting to connect to database >>>>> [java] Connected successfully! >>>>> [java] >>>>> [java] Database Type: oracle >>>>> [java] Database URL: jdbc:oracle:thin:@// >>>>> oradesa1.desa.arba.gov.ar:1521/DESA1.arba.gov.ar >>>>> [java] Database Schema: DSPACE >>>>> [java] Database Username: DSPACE >>>>> [java] Database Software: Oracle version Oracle Database 12c >>>>> Enterprise Edition Release 12.2.0.1.0 - 64bit Production >>>>> [java] Database Driver: Oracle JDBC driver version 11.2.0.4.0 >>>>> [java] 2018-09-12 15:46:42,600 WARN >>>>> org.dspace.services.sessions.SessionRequestServiceImpl @ Request >>>>> interceptor >>>>> (org.dspace.services.events.SystemEventService$EventRequestInterceptor@4270ad4d) >>>>> failed to execute on end (request-697-1536778002103): null >>>>> >>>>> Despite this WARN the last line is BUILD SUCCESSFUL. >>>>> >>>>> Then I copied wars from dspace/webapps to my Tomcat webapps folder, >>>>> but when Tomcat starts the problem about the driver still remains. The >>>>> driver is present also in dspace/lib folder. >>>>> >>>>> >>>>> 11-Sep-2018 18:59:44.878 GRAVE [localhost-startStop-1] >>>>> org.apache.catalina.core.StandardContext.listenerStart Excepción >>>>> enviando evento inicializado de contexto a instancia de escuchador de >>>>> clase >>>>> org.dspace.app.util.DSpaceWebappListener >>>>> org.hibernate.exception.GenericJDBCException: Could not open >>>>> connection >>>>> at org.hibernate.exception.internal. >>>>> StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter. >>>>> java:54) >>>>> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert( >>>>> SqlExceptionHelper.java:124) >>>>> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert( >>>>> SqlExceptionHelper.java:109) >>>>> at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl. >>>>> obtainConnection(LogicalConnectionImpl.java:221) >>>>> at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl. >>>>> getConnection(LogicalConnectionImpl.java:157) >>>>> at org.hibernate.engine.transaction.internal.jdbc. >>>>> JdbcTransaction.doBegin(JdbcTransaction.java:67) >>>>> at org.hibernate.engine.transaction.spi. >>>>> AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160) >>>>> at org.hibernate.internal.SessionImpl.beginTransaction( >>>>> SessionImpl.java:1387) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke( >>>>> NativeMethodAccessorImpl.java:62) >>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke( >>>>> DelegatingMethodAccessorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke(Method.java:498) >>>>> at org.hibernate.context.internal.ThreadLocalSessionContext$ >>>>> TransactionProtectionWrapper.invoke(ThreadLocalSessionContext. >>>>> java:352) >>>>> at com.sun.proxy.$Proxy41.beginTransaction(Unknown Source) >>>>> at org.dspace.core.HibernateDBConnection.getSession( >>>>> HibernateDBConnection.java:43) >>>>> at org.dspace.core.HibernateDBConnection. >>>>> configureDatabaseMode(HibernateDBConnection.java:154) >>>>> at org.dspace.core.HibernateDBConnection.setConnectionMode( >>>>> HibernateDBConnection.java:140) >>>>> at org.dspace.core.Context.setMode(Context.java:701) >>>>> at org.dspace.core.Context.init(Context.java:183) >>>>> at org.dspace.core.Context.<init>(Context.java:126) >>>>> at org.dspace.app.util.AbstractDSpaceWebapp.register( >>>>> AbstractDSpaceWebapp.java:74) >>>>> at org.dspace.app.util.DSpaceWebappListener. >>>>> contextInitialized(DSpaceWebappListener.java:31) >>>>> at org.apache.catalina.core.StandardContext.listenerStart( >>>>> StandardContext.java:4745) >>>>> at org.apache.catalina.core.StandardContext.startInternal( >>>>> StandardContext.java:5207) >>>>> at org.apache.catalina.util.LifecycleBase.start( >>>>> LifecycleBase.java:150) >>>>> at org.apache.catalina.core.ContainerBase.addChildInternal( >>>>> ContainerBase.java:752) >>>>> at org.apache.catalina.core.ContainerBase.addChild( >>>>> ContainerBase.java:728) >>>>> at org.apache.catalina.core.StandardHost.addChild( >>>>> StandardHost.java:734) >>>>> at org.apache.catalina.startup.HostConfig.deployDirectory( >>>>> HostConfig.java:1107) >>>>> at org.apache.catalina.startup.HostConfig$DeployDirectory. >>>>> run(HostConfig.java:1841) >>>>> at java.util.concurrent.Executors$RunnableAdapter. >>>>> call(Executors.java:511) >>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker( >>>>> ThreadPoolExecutor.java:1149) >>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >>>>> ThreadPoolExecutor.java:624) >>>>> at java.lang.Thread.run(Thread.java:748) >>>>> Caused by: java.sql.SQLException: Cannot load JDBC driver class >>>>> 'oracle.jdbc.OracleDriver' >>>>> at org.apache.commons.dbcp2.BasicDataSource. >>>>> createConnectionFactory(BasicDataSource.java:2139) >>>>> at org.apache.commons.dbcp2.BasicDataSource.createDataSource( >>>>> BasicDataSource.java:2033) >>>>> at org.apache.commons.dbcp2.BasicDataSource.getConnection( >>>>> BasicDataSource.java:1533) >>>>> at org.hibernate.service.jdbc.connections.internal. >>>>> DatasourceConnectionProviderImpl.getConnection( >>>>> DatasourceConnectionProviderImpl.java:141) >>>>> at org.hibernate.internal.AbstractSessionImpl$ >>>>> NonContextualJdbcConnectionAccess.obtainConnection( >>>>> AbstractSessionImpl.java:301) >>>>> at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl. >>>>> obtainConnection(LogicalConnectionImpl.java:214) >>>>> ... 31 more >>>>> Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver >>>>> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass( >>>>> WebappClassLoaderBase.java:1285) >>>>> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass( >>>>> WebappClassLoaderBase.java:1119) >>>>> at org.apache.commons.dbcp2.BasicDataSource. >>>>> createConnectionFactory(BasicDataSource.java:2131) >>>>> >>>>> >>>>> I had in this server a previuos instance running Dspace 6.2 that works >>>>> OK with that driver and that database. But the update to 6.3 is not >>>>> working. >>>>> >>>>> Any help? >>>>> >>>>> -- >>>>> All messages to this mailing list should adhere to the DuraSpace Code >>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "DSpace Community" group. >>>>> >>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>> >>>> >>>>> Visit this group at https://groups.google.com/group/dspace-community. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "DSpace Community" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/dspace-community. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> > Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-community. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
