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.
Seen on:
SQL
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 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026