ORA-12541: TNS: No Listener – Complete Step-by-Step Troubleshooting Guide

Published: April 2026

Last Updated: July 2026

Reading Time: 14–16 Minutes

Applies To: Oracle Database 11g, 12c, 18c, 19c, 21c, 23ai, Oracle RAC, Oracle Grid Infrastructure, Oracle Instant Client, Oracle E-Business Suite, Oracle Cloud Infrastructure (OCI)

The ORA-12541: TNS: No Listener error is one of the most common Oracle Net Services connectivity problems encountered by database administrators, developers, and application support teams. It occurs when an Oracle client attempts to connect to a database, but no Oracle Listener is available to accept the incoming connection.

Although the error message suggests that the listener is not running, the underlying cause can also be an incorrect hostname, wrong port number, firewall restrictions, listener configuration errors, Oracle Net misconfiguration, or service registration problems.

This comprehensive guide explains how Oracle Listener works, the most common causes of ORA-12541, step-by-step troubleshooting techniques, production-tested solutions, and best practices to prevent listener-related issues.

Quick Solution

If you receive ORA-12541, verify the following:

The Oracle Listener process is running.
The listener is listening on the expected port (usually 1521).
The hostname resolves correctly.
The client is using the correct SERVICE_NAME or SID.
The listener configuration files are correct.
The database services are registered with the listener.
No firewall or network device is blocking the connection.

In most environments, ORA-12541 is resolved by starting the listener, correcting the connection details, or fixing the listener configuration.

What is ORA-12541?
Understanding Oracle Listener
Oracle Net Connection Architecture
Error Message
Common Symptoms
Common Causes
Connection Workflow
Step-by-Step Solutions
Production Case Study
Best Practices
Frequently Asked Questions
Related Oracle Articles

What is ORA-12541?

ORA-12541 indicates that the Oracle client successfully reached the specified host but could not find an Oracle Listener accepting connections on the configured port.

The listener is responsible for accepting incoming client connections and directing them to the appropriate Oracle database instance. Without a running listener, remote client connections cannot be established.

This error commonly affects:

SQL*Plus
Oracle SQL Developer
RMAN
Data Pump (expdp/impdp)
Oracle E-Business Suite
Oracle Forms and Reports
JDBC applications
Oracle Instant Client

Understanding Oracle Listener

The Oracle Listener (TNS Listener) is a background process that listens for incoming client connection requests on one or more TCP/IP ports. When a client initiates a connection, the listener verifies the requested database service and forwards the session to the appropriate Oracle instance.

Unlike database background processes such as PMON or DBWR, the listener operates independently of the database. A database may be open while the listener is stopped, preventing remote users from connecting even though the database itself is healthy.

DBA Tip

A local administrator can often connect using sqlplus / as sysdba even when the listener is down. This is because local operating system authentication does not require Oracle Net.

Oracle Net Connection Architecture

Understanding the Oracle Net connection flow helps identify exactly where ORA-12541 occurs.

Client Application

       │

       ▼

Oracle Net (TNS)

       │

       ▼

Hostname Resolution

       │

       ▼

Listener (Port 1521)

       │

       ▼

Database Service

       │

       ▼

Oracle Database Instance

ORA-12541 occurs before the client reaches the database instance. The failure happens when no listener process is available to accept the connection on the specified host and port.

Error Message

ORA-12541: TNS: no listener

Depending on the client application, you may also see additional messages indicating that the connection could not be established because the target listener was unavailable.

Common Symptoms

SQL*Plus cannot connect to the database.
Oracle SQL Developer reports a connection failure.
RMAN cannot establish a target database connection.
Data Pump import or export operations fail.
Oracle E-Business Suite services cannot connect to the database.
JDBC applications fail during startup.
Scheduled jobs stop after a server restart.
Users can connect locally but not remotely.

Common Causes

The Oracle Listener service is not running.
The listener is listening on a different port.
The hostname specified in the connection string is incorrect.
The client is using an incorrect port number.
The listener.ora configuration file contains errors.
The database service is not registered with the listener.
Firewall rules block the listener port.
The listener process terminated unexpectedly.
Multiple Oracle Homes are causing configuration conflicts.
Oracle Net configuration files reference outdated settings.

Oracle Connection Workflow

Client

      │

      ▼

Resolve Hostname

      │

      ▼

Connect to Port 1521

      │

      ▼

Listener Accepts Connection

      │

      ▼

Database Service Found

      │

      ▼

Database Session Created

If the client cannot establish communication with the listener during this sequence, Oracle immediately returns ORA-12541 without attempting database authentication.

Step-by-Step Solutions

Resolving ORA-12541: TNS: No Listener requires identifying whether the problem is caused by the Oracle Listener service, network connectivity, Oracle Net configuration, or database service registration. Follow the steps below in sequence to isolate the root cause.

Solution 1 – Check the Listener Status

The first step is to verify whether the Oracle Listener is running.

Execute the following command from the Oracle server:

lsnrctl status

If the listener is running, you should see output similar to:

LSNRCTL for Linux: Version 19.0.0.0.0

Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbserver)(PORT=1521)))

STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux
Start Date                ...
Listening Endpoints Summary...
Services Summary...

If you receive TNS-12541: no listener, the listener is not available or is listening on a different address or port.

DBA Recommendation

Always execute lsnrctl status before making configuration changes. It quickly confirms whether the listener is running and which services are registered.

Solution 2 – Start the Oracle Listener

If the listener is stopped, start it using:

lsnrctl start

Successful startup confirms that the listener process has been created and is ready to accept client connections.

After startup, verify its status again:

lsnrctl status

Solution 3 – Stop and Restart the Listener

If the listener appears unresponsive or services are missing, restart it.

lsnrctl stop

lsnrctl start

Restarting reloads listener processes and often resolves temporary communication issues.

Solution 4 – Reload Listener Configuration

After modifying listener.ora, you do not always need to restart the listener.

Reload the configuration:

lsnrctl reload

This minimizes downtime while applying configuration changes.

Solution 5 – Verify listener.ora

The listener.ora file defines listener addresses, ports, and optional static service registrations.

Typical location:

$ORACLE_HOME/network/admin

Verify:

Correct hostname
Correct TCP port
No syntax errors
No duplicate listener definitions

Example:

LISTENER =
 (DESCRIPTION=
   (ADDRESS=(PROTOCOL=TCP)
            (HOST=dbserver)
            (PORT=1521))
 )

Solution 6 – Verify tnsnames.ora

Ensure the client connection uses the correct hostname, port, and service name.

Example:

ORCL=

(DESCRIPTION=
 (ADDRESS=(PROTOCOL=TCP)
          (HOST=dbserver)
          (PORT=1521))
 (CONNECT_DATA=
   (SERVICE_NAME=orcl)
 )
)

Even one incorrect character in the hostname or port can trigger ORA-12541.

Solution 7 – Test Using tnsping

Use tnsping to verify Oracle Net connectivity.

tnsping ORCL

A successful response confirms that the client can reach the listener.

If tnsping fails, investigate Oracle Net configuration or network connectivity before troubleshooting the database.

Solution 8 – Verify the Listener Port

The default Oracle Listener port is 1521, but environments may use different ports.

Linux:

netstat -an | grep 1521

ss -tln | grep 1521

Windows:

netstat -ano | find "1521"

These commands verify whether a process is listening on the configured port.

Solution 9 – Check Firewall Configuration

Operating system or network firewalls may block Oracle Listener traffic.

Verify:

Linux firewall rules
Windows Defender Firewall
Cloud security groups
Network ACLs
Corporate firewalls

If necessary, allow inbound TCP connections on the listener port.

Solution 10 – Verify Hostname Resolution

Incorrect hostname resolution is another common cause of ORA-12541.

Verify using:

ping dbserver

nslookup dbserver

If hostname resolution fails, update DNS records or the local hosts file.

Solution 11 – Verify Database Service Registration

A running listener does not guarantee that database services are registered.

Check registered services:

lsnrctl services

If your database service is missing, register it manually:

ALTER SYSTEM REGISTER;

Then run:

lsnrctl services

to verify that the service appears.

Real Production Case Study

Following a planned operating system reboot, application users were unable to connect to the Oracle database and received ORA-12541 errors.

Initial investigation showed:

The database instance was OPEN.
The listener process had not started automatically.
Port 1521 was not listening.
SQL*Plus worked locally using operating system authentication.

Resolution steps:

Started the listener using lsnrctl start.
Verified service registration with lsnrctl services.
Confirmed client connectivity using tnsping.
Configured the listener service to start automatically after future server reboots.

Application connectivity was restored without restarting the database.

Quick Troubleshooting Checklist

Check	Status
Listener Running	☐
Correct Port	☐
Correct Hostname	☐
Firewall Open	☐
Listener Configuration Valid	☐
Database Service Registered	☐
tnsping Successful	☐
Client Uses Correct SERVICE_NAME	☐

Dynamic vs Static Service Registration

Oracle databases can register services with the listener using either dynamic registration (recommended) or static registration. Understanding the difference helps diagnose many listener-related issues.

Dynamic Registration (Recommended)

Dynamic registration is performed automatically by the PMON background process. When the database starts, PMON registers the database services with the listener without requiring manual configuration.

Check registered services:

lsnrctl services

Force service registration if required:

ALTER SYSTEM REGISTER;

Static Registration

Static registration is configured manually inside listener.ora. It is commonly used for Data Guard, external procedures, and some legacy applications.

Example:

SID_LIST_LISTENER =
 (SID_LIST =
   (SID_DESC =
     (GLOBAL_DBNAME = orcl)
     (SID_NAME = orcl)
     (ORACLE_HOME = /u01/app/oracle/product/19c/dbhome_1)
   )
 )

Verify LOCAL_LISTENER and REMOTE_LISTENER

Incorrect listener parameters can prevent database services from registering correctly.

Check the current configuration:

SHOW PARAMETER listener;

Typical output includes:

LOCAL_LISTENER
REMOTE_LISTENER

If these parameters reference an invalid hostname or port, clients may receive listener-related errors.

Oracle RAC Considerations

In Oracle RAC environments, clients normally connect through SCAN (Single Client Access Name) listeners instead of individual node listeners.

Verify:

SCAN listeners are running.
Node listeners are online.
Database services are active.
Cluster resources are healthy.
VIP addresses are functioning correctly.

RAC Best Practice

Applications should connect using SCAN listeners rather than individual node hostnames. This improves availability, simplifies failover, and reduces maintenance effort.

Oracle Grid Infrastructure

When Oracle Grid Infrastructure manages the listener, use CRS utilities instead of manually starting or stopping the listener.

Examples:

srvctl status listener

srvctl start listener

srvctl stop listener

Using CRS ensures the listener remains synchronized with cluster resources.

Oracle Cloud Infrastructure (OCI)

For Oracle databases hosted in Oracle Cloud Infrastructure, ORA-12541 may also be caused by cloud networking or security configuration.

Verify:

Security Lists
Network Security Groups (NSGs)
Virtual Cloud Network (VCN) rules
Public or private subnet routing
Listener status on the database server

Cloud networking should always be verified before modifying database configuration.

Common Mistakes

Listener service not started after server reboot.
Incorrect hostname in tnsnames.ora.
Wrong listener port.
Database services not registered.
Firewall blocking TCP port 1521.
Multiple Oracle Homes causing configuration conflicts.
Editing the wrong listener.ora file.
Restarting the database instead of simply starting the listener.

Best Practices

Configure the listener to start automatically after system reboot.
Use dynamic service registration whenever possible.
Monitor listener logs regularly.
Keep Oracle Net configuration consistent across environments.
Document listener ports and service names.
Regularly test client connectivity using tnsping.
Use SCAN listeners in Oracle RAC deployments.
Review firewall and network changes before database maintenance.

Frequently Asked Questions

Does ORA-12541 always mean the listener is stopped?

No. It can also result from an incorrect hostname, wrong port, firewall restrictions, network routing problems, or Oracle Net configuration errors.

How do I verify that the listener is running?

lsnrctl status

How do I register database services manually?

ALTER SYSTEM REGISTER;

Can ORA-12541 occur while the database is open?

Yes. The database can remain open and operational while the listener is stopped, preventing only remote client connections.

What is the default Oracle Listener port?

The default TCP port is 1521, although many production environments use custom ports for security or organizational standards.

About the Author

Rana Abdul Wahid is a seasoned Oracle Database Consultant with more than 15 years of experience in Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup & Recovery, Performance Tuning, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise database management.

This blog shares practical Oracle DBA troubleshooting guides, production-tested solutions, performance tuning techniques, and real-world database administration experience to help IT professionals solve Oracle Database issues efficiently.

Learn more about the author →

Conclusion

The ORA-12541: TNS: No Listener error occurs when an Oracle client cannot establish communication with the Oracle Listener. While the listener service being stopped is the most common cause, network configuration, incorrect hostnames, listener configuration errors, firewall restrictions, and missing service registrations can all produce the same error.

A structured troubleshooting process—checking listener status, validating Oracle Net configuration, verifying service registration, confirming network connectivity, and reviewing firewall rules—helps resolve ORA-12541 quickly while minimizing downtime.

Final DBA Advice

When troubleshooting ORA-12541, always verify whether the problem lies with the listener, the network, or the client configuration before making changes to the database itself. In many cases, the database is healthy, and the issue is limited to Oracle Net Services.

Did this guide help resolve your ORA-12541 error? Bookmark this article and explore our complete Oracle Error Codes Guide for more production-tested Oracle DBA solutions.

Oracle Database Error Solutions & DBA Knowledge Base