TNS-01189: The listener could not authenticate the user

In 19c GI environment, TNS-01189 is still being received hourly from OEM 13cR3 for both local listeners and SCAN listeners, though Oracle said this issue has been fixed since

The OEM alert:

Target type=Listener
Target name=LISTENER_SCAN1_racnode-cluster
Message=TNS-1189. Please check log for details.
Event reported time=May 1, 2020 9:26:35 PM 
Operating System=Linux
Associated Incident Id=1513
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Metric Alert
Event name=TNS_ERRORS:tnserrmsg
Total Occurrences=115
Occurrences in this event=45
First Occurred in this event=Apr 28, 2020 10:11:23 AM 
Last Occurred in this event=May 1, 2020 8:10:06 PM 
Metric Group=TNS Errors
Metric value=TNS-1189(version)
Key Value=TNS-1189
Key Column 1=TNSError
Rule Name=Incident management rule set for all targets,Create 
          incident for critical metric alerts
Rule Owner=System Generated
Update Details:
TNS-1189. Please check log for details.

The local listener and scan listeners error log:

1-MAY-2020 19:10:35 * (CONNECT_DATA=(COMMAND=version)) * version * 1189
TNS-01189: The listener could not authenticate the user

Subscribe to get access

Read more of this content when you subscribe today.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: