listener的日志中总是报警TNS-1169

在一个oracle 9208的数据库中,我们发现有大量的TNS-1169的告警:

24-APR-2012 11:13:45 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=au11qap850tels2)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(PASSWORD=xxxxxxxx)(SERVICE=LISTENER_BDS02P1)(VERSION=153094144)) * status * 0
24-APR-2012 11:13:58 * ping * 0
24-APR-2012 11:13:58 * status * 1169
TNS-01169: The listener has not recognized the password

基本每天这样的报错在480个以上。

从数量上看,这么多的报错应该不是人为引起的,不可能是人为的在没有输入密码的前提下lsnrctl status失败。那么是什么引起的?

一开始我们怀疑是否是crontab引起,我们查了所有的crontab,发现没有一个脚本是运行lsnrctl的。

那可能是什么原因?难道是emagent或者是veritas中的某些服务?

我们在metalink中找到了答案,在metalink上有这样一篇文章:

Listener Logs Show TNS-1169 When Agent is Monitoring Password Protected 9i Listener [ID 358411.1]

In this Document
  Symptoms
  Cause
  Solution

Applies to:

Enterprise Manager Base Platform - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 02-Apr-2012***
Symptoms

-The Following error messages gets logged in the password protected 9i listener that is being monitored by the Grid Control:

15-FEB-2006 23:58:04 * status * 1169
TNS-01169: The listener has not recognized the password

...

16-FEB-2006 00:00:45 * (CONNECT_DATA=(SID=dg2)(CID=(PROGRAM=perl)(HOST=incq048ad
.idc.oracle.com)(USER=oracle))) * services * 1169
TNS-01169: The listener has not recognized the password

...

16-FEB-2006 00:00:46 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=incq048ad.idc.oracle.c
om)(USER=oracle))(COMMAND=services)(ARGUMENTS=64)(PASSWORD=xxxxxxxx)(SERVICE=(DE
SCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=incq048ad.idc.oracle.com)(PORT=1523))))(V
ERSION=153093888)) * status * 1169
TNS-01169: The listener has not recognized the password

-These error messages are not logged when one of the following is done:

1) Agent is stopped
2) When the password is disabled for the listener
3) Remove the listener target from the grid control

Cause

The issue was investigated in BUG 6328973 : Agent Monitoring Password Protected Listener Logs Tns-1169 In Listener Log File


Solution

Follow either of below solution:

1) Upgrade to 10g or above listener where this problem is not encountered at all. Problem only occurs for 9i password protected listener. 

2) Disable listener password authentication if acceptable.

3) In case of 10.2.0.5, enter the Encrypted password into the Listener Password field.
 a. Copy the encrypted listener password from the listener.ora file
 b. Navigate to Targets -> All Targets -> Select the listener and click on Configure -> Enter the Encrypted password into the Listener Password field -> Click on OK.

一查我们的emagent的版本,10.2.0.4,原来是遇到bug了。10.2.0.4的emagent去监控9.2.0.8的listener,如果listener设置密码,将会报错TNS-1169。该问题需要将emagent升级到10.2.0.5,才有配置侦听密码的选项。

au11qap850tels2:BDS01P1:/ora/product/emagent10g/agent10g/bin>emctl status agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.  
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 10.2.0.4.0
OMS Version       : 10.2.0.5.0
Protocol Version  : 10.2.0.4.0
Agent Home        : /ora/product/emagent10g/agent10g/au11qap850tels2
Agent binaries    : /ora/product/emagent10g/agent10g
Agent Process ID  : 17720
Parent Process ID : 15931
Agent URL         : http://au11qap850tels2:3872/emd/main
Repository URL    : http://emcentral.in.telstra.com.au:4889/em/upload/
Started at        : 2012-05-02 10:04:31
Started by user   : oracle
Last Reload       : 2012-05-03 15:25:25
Last successful upload                       : 2012-05-03 17:31:55
Total Megabytes of XML files uploaded so far :    28.10
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    31.63%
Last successful heartbeat to OMS             : 2012-05-03 17:33:53
---------------------------------------------------------------
Agent is Running and Ready
au11qap850tels2:BDS01P1:/ora/product/emagent10g/agent10g/bin>

相关文章

发表评论

电子邮件地址不会被公开。 必填项已用*标注

此站点使用Akismet来减少垃圾评论。了解我们如何处理您的评论数据