Find and Check the Oracle Listener Service in Oracle AI Database 26ai (Windows)

The Oracle Net Listener — the TNS Listener covered in Lessons 1 and 2 — accepts incoming client connection requests and hands them off to the appropriate database service. On Windows, it doesn't run as a standalone background process the way it might on Linux; it runs as a standard Windows Service, wrapped and managed the same way any other Windows service is. This lesson covers the fast, reliable ways to find that service and confirm whether it's actually up before you spend time troubleshooting something else.

It's worth being explicit about why this matters for a course on managing users specifically: no matter how carefully you've set up accounts, roles, and privileges, none of it helps a single user connect if the listener isn't running. A user reporting "I can't connect to the database" is, more often than administrators initially assume, a listener problem rather than an authentication or privilege problem — which makes knowing how to quickly check listener status one of the first diagnostic steps worth reaching for, not a last resort.

Three different tools can tell you whether the listener is running, and each is useful in a different situation — a quick visual check, a scriptable command-line check, or a detailed health check that shows you what the listener is actually doing.

1. Services console (GUI) — the fastest option when you're already at the server's desktop and just need a visual confirmation.
   • Press Win+R → type services.msc → Enter.
   • Sort by Name and look for the Oracle listener service — its exact name depends on your Oracle Home configuration, covered in detail below.
   • Status shows Running (listener up) or Stopped. That's the entire signal this method gives you — useful for a quick check, but it won't tell you whether the listener is actually accepting connections correctly or which database services it's registered for.
2. Command line (fast, scriptable) — the better choice when you need to check status as part of a script, or across several servers without opening a GUI on each one.
   • PowerShell: Get-Service -Name *TNSListener* | Format-Table Name,Status,DisplayName
   • CMD: sc query type= service state= all | findstr /I TNSListener
   Both give you the same Running/Stopped answer as the Services console, just without leaving the command line — useful if you're already in a remote session or writing a monitoring script.
3. Listener Control (LSNRCTL) — the option that actually tells you something beyond "is the service running."
   • Open an Oracle command prompt (one where PATH includes %ORACLE_HOME%\bin).
   • Run lsnrctl status for detailed health, listening endpoints, registered services, and uptime.
   This is the method worth reaching for once you already know the Windows service itself is running and need to understand what the listener is doing — which addresses it's listening on, which database services have registered with it, and how long it's been up.

Oracle wraps the listener in a Windows service with a name built from two pieces: the literal prefix Oracle, followed by the Oracle Home name you chose (or accepted as a suggested default) at install time, followed by TNSListener. It's not a fixed string the installer generates from the Oracle version number — it's built from whatever home name is actually in use on that machine, which is why you shouldn't assume a specific string without checking.

That said, Oracle's installer has long suggested home names that look something like OraDB19Home1 or similar version-flavored defaults, which is where a service name like OracleOraDB19Home1TNSListener comes from in practice — not because Oracle hardcodes the version into the service name, but because that's what the home name happened to be on that particular installation. If you customized the home name during install, or you're working with an installation where someone else chose it, the actual service name on your system may look different. The reliable way to find it is simply to look, rather than guess:

PowerShell> Get-Service *Oracle* | Sort-Object Name | Format-Table Name, Status

This lists every Oracle-related Windows service on the machine, regardless of what its exact name turned out to be — the listener service will be the one ending in TNSListener. If you've installed multiple Oracle Homes on the same machine, you'll see multiple listener services, one per home, each reflecting that home's own name.

Once you know the actual service name on your system, you can start and stop it directly from an elevated console:

net stop  <your-listener-service-name>
net start <your-listener-service-name>

Substitute the service name you found in the previous step — don't assume it matches any example shown elsewhere in this lesson. Alternatively, the Services console offers the same control without needing to type the exact name: right-click the listener service → Start, Stop, or Restart.

LSNRCTL gives you the same start/stop control as the Windows service commands, but from inside Oracle's own tooling rather than the OS service manager — and it gives you status information the OS-level tools can't. From an Oracle-enabled shell:

lsnrctl status
lsnrctl start
lsnrctl stop

• If you're running multiple listeners — a non-default name is common when you deliberately want to separate environments — specify which one you mean: lsnrctl status LISTENER_DEV.
• If you have multiple Oracle Homes installed, make sure ORACLE_HOME\bin for the home you actually intend to work with precedes any older homes in your PATH. Running lsnrctl from the wrong home's PATH entry is a common source of confusing, seemingly-inconsistent results.

Here's what a healthy listener's status output looks like, trimmed to the parts that matter most day to day. The exact version number in your own output will reflect whatever Oracle release and patch level you're actually running — treat the version string below as illustrative, not as something to match exactly:

LSNRCTL for 64-bit Windows: Version <your Oracle version> - Production
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MyServer)(PORT=1521)))
STATUS of the LISTENER
----------------------
Alias                      LISTENER
Version                    TNSLSNR for 64-bit Windows: <your Oracle version>
Start Date                 20-MAR-2026 23:30:55
Uptime                     0 days 12 hr. 24 min.
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MyServer)(PORT=1521)))
Services Summary...
  Service "COIN" has 1 instance(s).
    Instance "COIN", status READY, has 1 handler(s) for this service...

A few things worth reading carefully in this output, not just glancing past: the Uptime field tells you how long the listener itself has been running — a recently-restarted listener after a long-running database might be worth investigating on its own. The Listening Endpoints Summary confirms which port the listener is actually bound to; port 1521 remains Oracle's default. And the Services Summary is the section that actually answers "can clients reach my database" — a listener can be running perfectly and still show zero registered services if the database instance hasn't registered with it yet.

• Service missing? Re-run Oracle Net Configuration Assistant (NETCA) to create a listener from scratch.
• Port conflict (1521 already in use)? Change the port in %ORACLE_HOME%\network\admin\listener.ora and restart the listener, or free up port 1521 on that host.
• Firewall blocking connections? Confirm inbound TCP is allowed on the listener's port from the client subnets that actually need to reach it.
• Multiple Oracle Homes installed? Confirm which home owns the running listener — lsnrctl status shows the binary path it's running from, which tells you definitively.
• Service name doesn't match what you expected? As covered above, the Windows service name is built from your Oracle Home name, not a fixed pattern — use Get-Service *Oracle* to see what's actually on the machine rather than guessing.
• Listener running but clients still can't connect? A running listener doesn't guarantee the specific PDB or CDB service is registered with it — check the "Services Summary" section of lsnrctl status to confirm the service you expect is actually listed.
• Permission errors when starting or stopping? Both the Windows service commands and LSNRCTL's start/stop operations require an elevated shell or administrative rights over the service — a permissions problem here looks like a listener problem if you're not watching for it specifically.

Listener logs live under the Automatic Diagnostic Repository (ADR) structure: %DIAG_ADR_BASE%\diag\tnslsnr\<host>\<listener_name>\trace\listener.log, rooted at whatever your configured diagnostic_dest is. Each logged entry includes a timestamp and a result code — a code of 0 indicates success, and anything else is worth investigating in context rather than assuming it's automatically an error.

In clustered environments, listeners participate in a broader notification system beyond just their own log file: they can publish and consume Oracle Notification Service (ONS) events, which carry Fast Application Notification (FAN) information about node or service state changes to other components in the cluster. That's outside the scope of a single-instance COIN setup like the one this course works with, but it's worth knowing the terminology — ONS is the transport mechanism, FAN is the actual event information riding on it — since you'll encounter both terms together in clustered Oracle environments.