ORA-03135: connection lost contact
The client lost its connection to the database, typically after a firewall or timeout cut an idle session, or the server process ended.
- Error code
ORA-03135- Category
- Connection and login
What it means
ORA-03135 is reported when the connection to the server is gone, often when the client next tries to use a session that a firewall, a timeout or the server silently ended while it was idle.
Common causes
- A firewall or NAT device timing out an idle connection.
- A profile limit such as
IDLE_TIMEor a server-side timeout ending the session. - The server process or instance stopping.
How to fix it
-
Reconnect, and have long-lived applications validate pooled connections before use.
-
Set
SQLNET.EXPIRE_TIME(in minutes) in the server'ssqlnet.oraso the database probes idle connections and firewalls see traffic. -
Check the user's profile for idle limits.
SELECT p.resource_name, p.limit FROM dba_users u JOIN dba_profiles p ON p.profile = u.profile WHERE u.username = 'APP_USER' AND p.resource_name IN ('IDLE_TIME', 'CONNECT_TIME');
Related errors
ORA-03113end-of-file on communication channel2013MySQL: Lost connection to MySQL server during query4031MySQL: Disconnected by the server for inactivity
More connection and login errors
ORA-01017invalid username/password; logon deniedORA-12154TNS: could not resolve the connect identifierORA-12514TNS: listener doesn't know the requested serviceORA-12505TNS: listener doesn't know the SIDORA-12541TNS: no listenerORA-12170TNS: connect timeout occurredORA-28000the account is lockedORA-28001the password has expired
The code and message text are from the Oracle Database Error Help. Browse the full Oracle error list or search every database error.
Work on Oracle in SQLly
A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for Oracle and the other databases you use.