Skip to Main Content
  • Questions
  • Listener logs showing other port number than 1521, and audit table show connection port number is other than 1521

Breadcrumb

Dev Live Dev Intro

We are celebrating Developers at AskTOM. We welcome Developers of all levels of experience to join us at our FREE Developer Live events coming in August and September. Just click on the left to register today! If you are brand new to Database Technology, then we also have got you covered. Just click on the right for your comprehensive FREE training program to kick start your Oracle Database Development journey!

Question and Answer

Connor McDonald

Thanks for the question, Gyan.

Asked: September 10, 2020 - 4:22 am UTC

Answered by: Connor McDonald - Last updated: September 10, 2020 - 7:09 am UTC

Category: Database Administration - Version: 11.2.0.2

Viewed 100+ times

You Asked

I have set listener with port number as 1521, but while checking the listener logs, the port number is showing other than 1521, and also on audit table connection port number is showing other than 1521.

Listener status:
lsnrctl status

LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 10-SEP-2020 10:07:19

Copyright (c) 1991, 2010, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date 01-JAN-2020 20:02:50
Uptime 252 days 14 hr. 4 min. 29 sec
Trace Level off
Security ON: Password or Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/SBKTMHPDPMA/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=******)(PORT=1521)))
Services Summary...



listener log:
(CONNECT_DATA=(CID=(PROGRAM=SQL Developer)(HOST=__jdbc__)(USER=*****))(SERVICE_NAME=****)) * (ADDRESS=(PROTOCOL=tcp)(HOST=****)(PORT=58548)) * establish * PRODSAN * 0

Also unable to identify the failure login attempts from listener logs.

So, please guide us for same.

and we said...

I suspect someone is trying to launch the SQL Developer debugger.

Take a look in v$plsql_debuggable_sessions (although this is transient data).

More info on remote debugging here

https://mahmoudhatem.wordpress.com/2017/04/10/improved-remote-session-debugging-dbms_debug_jdwp/

You can set preferences in SQL Developer to set min/max port ranges for debugging