有关ora-00130错误

今天有同事跟我说他的数据库启动的时候在alert.log里面提示ORA-00130错误。

Sun Feb  6 13:13:54 2005
ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=*)(PORT=1521))'

但是HOST指的机器并不是这台服务器的HOSTNAME，在listene.ora中也没有配置这台服务器对应的监听，为什么启动的时候会提示这个错误呢？

在metalink上看到也有人遇到类似的问题：

RDBMS Version:: 9.2.0.2
Operating System and Version:: Linux 2.4
Error Number (if applicable):: ORA-00130
Server Net Version:: 9.2.0.2
Client Operating System and Version::
Client Net Version::

Message in alert log

I am getting this error in the alert log:

ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=btctestora1.btconf.com)(PORT=1521))'

In all of my config files I reference it by ip address. The reason is that the machine has to NICs, and I want to be sure which NIC I am referencing.

It is only there during a startup and it appears between starting DBW0 and starting LGWR.

Everything is working fine, I am just trying to find out where this is coming from. It is not in any config files that I have looked at (init.ora, tnsnames.ora, listener.ora).

---

来自: Oracle, David Filter 22-Jan-03 21:11
主题: Re : Message in alert log

Hello

This may have to do with registration between the instance and the listener. The instance may be trying to pickup the hostname from the os and is obtaining btctestora1.btconf.com. Startup info is recorded in the alert log and that would make sense as to why you may see listener info in the alert log, also if this occurs between the dbw0 and lgw0 this is an indication if may have to do with the instance registering to the listener.

Check the init.ora or spfile and make sure the local_listener parameter is set so the instance has the address of the listener when it starts. If it is not in the startup files, add the local_listener parameter to the file. It is also a good idea when starting the database to make sure the listener is started first so the instance can find the listener when it starts and can register immediately.

The ora-103 error from Note:194255.1 is explaining that the listener address is incorrect and this may be due to the hostname the instance is picking up from the os.

Dave

Oracle Technical Support

---

来自: Eric Johnson 22-Jan-03 21:31
主题: Re : Message in alert log

The listener is started before the database.

local_listener was not set. I did set it, and we'll see what happens when the database restarts overnight.

---

来自: Eric Johnson 23-Jan-03 13:25
主题: Re : Message in alert log

Setting local_listener did get rid of the message.

The curious thing is why btctestora1.btconf.com is invalid. If I do a uname, I get btctestora1.btconf.com as the name of the machine, but if I do an nslookup or a host on that address it comes back as not found.

I'll have to talk to the system administrator to find out why.

===================

察看该服务器上的oracle用户的环境变量，发现HOSTNAME这个变量的值就是错误提示里面的值，所以在数据库启动的时候，会启动该HOSTNAME对应的监听，但是该HOSTNAME的值并不是该服务器的名字，可能是后来调整过/etc/hosts吧，建议他调整该环境变量后重启数据库，应该就没有这个提示了。

结果：修改了该参数后重新启动，问题解决。连那个‘有关error 46 encountered when initializing ldm’的错误也没有了，呵呵。

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/51862/viewspace-180569/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/51862/viewspace-180569/