ORA-12505 SQL Origin: Data OSI layer 7 · Application Last updated 13 Oct 2026

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.

Exact message you may see does not currently know of 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

  1. Use the service-name format: jdbc:oracle:thin:@//host:1521/ORCLPDB1
  2. Check lsnrctl status for SIDs/services

Detailed fix by platform

Java

  1. jdbc:oracle:thin:@//db.example.com:1521/ORCLPDB1

How to diagnose

  1. Format — SID (:) or service (/)?
  2. 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:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

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) (SQL)Network-related errorORA-00001 — ORA-00001: unique constraint (SCHEMA.PK_X) violated (SQL)ORA-00001ORA-00018 — ORA-00018: maximum number of sessions exceeded (SQL)ORA-00018ORA-00020 — ORA-00020: maximum number of processes (150) exceeded (SQL)ORA-00020ORA-00028 — ORA-00028: your session has been killed (SQL)ORA-00028ORA-00054 — ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired (SQL)ORA-00054ORA-00904 — ORA-00904: "X": invalid identifier (SQL)ORA-00904ORA-12154 — ORA-12154: TNS:could not resolve the connect identifier specified (SQL)ORA-12154ORA-12505

Explore the map of this error Full error map →

🧠 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.