ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
The connect string uses a SID the listener doesn’t know — often a service name passed as SID.
does not currently know of SID Meaning
JDBC URLs with :SID use host:port:SID; service names need host:port/SERVICE. Pluggable databases are reached by service name.
Common causes
- Service name used as SID (jdbc:oracle:thin:@host:1521:ORCLPDB1)
- Wrong SID
⚡ Quick fix
- Use the service-name format: jdbc:oracle:thin:@//host:1521/ORCLPDB1
- Check lsnrctl status for SIDs/services
Detailed fix by platform
Java
jdbc:oracle:thin:@//db.example.com:1521/ORCLPDB1
How to diagnose
- Format — SID (:) or service (/)?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Network-related error SQL Server: A network-related or instance-specific error occurred while establishing a connection to SQL Server. (provider: Named Pipes Provider, error: 40 / TCP Provider, error: 26)
- ORA-00001 ORA-00001: unique constraint (SCHEMA.PK_X) violated
- ORA-00018 ORA-00018: maximum number of sessions exceeded
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026