java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor  

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via dynatrace.com by Unknown author, 1 year ago
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor  
via Oracle Community by 937637, 1 year ago
The Network Adapter could not establish the connection
via Geographic Information Systems by Jay Cummins
, 1 year ago
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
via stackexchange.com by Unknown author, 1 year ago
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
via Stack Overflow by user591790
, 9 months ago
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
via Stack Overflow by Fitz
, 1 year ago
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor  
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.)
at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.)
at oracle.jdbc.driver.T4CConnection.(T4CConnection.)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at java.sql.DriverManager.getConnection(DriverManager.)
at com.db.monitor.QueryMonitor.execute(QueryMonitor.)
at com.db.monitor.QMonitor.execute(QMonitor.java:30)
at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:565)
at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:52)
at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:27)
at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:192)
at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:415)
at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:339)
at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)
at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)
at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)
at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)
at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 2 years ago
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
40 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.