JIEX888 opened a new issue, #13819:
URL: https://github.com/apache/dolphinscheduler/issues/13819

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Dolphinscheduler 3.0,create Oracle(Oracle version 11.2.0.4) data source 
failed.
   my environment:
   jdk version : jdk1.8_181
   jdbc driver :  ojdbc6-11.2.0.4.jar and  ojdbc8-12.2.0.1.jar. --many have 
tried
   prompt information : 2023-03-29 06:29:05.560 +0000 
org.apache.dolphinscheduler.api.service.impl.DataSourceServiceImpl:[345] - 
datasource test connection error, dbType:ORACLE, 
connectionParam:OracleConnectionParam{user='user', password='*****', 
address='jdbc:oracle:thin:@xxxxxx:1521', database='wfmdb', 
jdbcUrl='jdbc:oracle:thin:@10.10.51.180:1521:wfmdb', driverLocation='null', 
driverClassName='oracle.jdbc.OracleDriver', validationQuery='select 1 from 
dual', other='null', connectType=ORACLE_SID}, message:Failed to load driver 
class oracle.jdbc.OracleDriver in either of HikariConfig class loader or Thread 
context classloader.
   
   I made some attempts:
   1.copy ojdbc6-11.2.0.4.jar or ojdbc8-12.2.0.1.jar to /.../api-server/libs 
and /.../work-server/libs and restart,but not resolved
   
   > 
   
   ### What you expected to happen
   
   Please help me resolve this issue
   
   ### How to reproduce
   
   create data source
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.0.x
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to