17,380
社区成员
发帖
与我相关
我的任务
分享求救：关于ORA-12545的解决方法
正在连接...ORA-12545: Connect failed because target host or object does not exist
测试未成功。
本机客户端能成功连接，但是一个局域网其它机器开始可以连接上
但是一会儿断了，就出现这个错误，怎么解决？？？
在线等待，解决马上给分
测试未成功。
本机客户端能成功连接，但是一个局域网其它机器开始可以连接上
但是一会儿断了，就出现这个错误，怎么解决？？？
在线等待，解决马上给分
...全文
请发表友善的回复…
发表回复
gengxp 2002-10-21
- 打赏
- 举报
ORA-12545: TNS:name lookup failure
Cause: The listener on the remote node cannot be contacted.
Action: Perform these steps:
Verify that the ADDRESS in the tnsnames.ora file and the listener.ora file is correct.
Verify that the listener on the remote node has been started. Enter:
lsnrctl
LSNRCTL> STATUS [listener_name]
listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.
If the output indicates the listener is not running, try starting it with the command:
LSNRCTL> START [listener_name]
Cause: The listener on the remote node cannot be contacted.
Action: Perform these steps:
Verify that the ADDRESS in the tnsnames.ora file and the listener.ora file is correct.
Verify that the listener on the remote node has been started. Enter:
lsnrctl
LSNRCTL> STATUS [listener_name]
listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.
If the output indicates the listener is not running, try starting it with the command:
LSNRCTL> START [listener_name]
qiuyang_wang 2002-10-21
- 打赏
- 举报
一、其它机器是一直都没有连上：说明你的机器或其它机器的配置有问题。
二、连上后过一会就自动断开,但断开后可以再重新连上：说明网络不稳定
三、开始可以连上，过会就连不上了；如果断开再连接也连不上：这种情况说明服务器上启动了某些与ORACLE服务有冲突的东西，关闭这些服务就可以了。
二、连上后过一会就自动断开,但断开后可以再重新连上：说明网络不稳定
三、开始可以连上，过会就连不上了；如果断开再连接也连不上：这种情况说明服务器上启动了某些与ORACLE服务有冲突的东西，关闭这些服务就可以了。
xynet 2002-10-21
- 打赏
- 举报
下面这段话可能帮你解决问题。
ORA-12545
This error occurs when the client computer tries to look up the hostname of the database server (for example dbp.banner.mcgill.ca) to get its IP address. The lookup is failing.
In most cases we have seen, the results are wrong because an old Domain Name Server (DNS), no longer kept current, is still available and many PCs around campus are still pointing to it. It is incorrectly reporting that the Banner database server does not exist. Since the old DNS works fine for most other addresses, users have not realized there was a problem until now.
The solution is to change the client computer's TCP/IP properties to point to the correct DNS addresses. Typically only two addresses should be listed: one for the primary DNS, and one for the secondary (alternate) DNS:
132.206.44.21
132.216.44.21
Different computers/operating systems have different dialogs for changing this. The general approach is:
Edit the Properties of Network Neighborhood (known as "My Network Places" in Windows 2000).
Navigate/drill down until you find the TCP/IP protocol, and edit its Properties. (If there are several TCP/IP entries found, ignore anything which refers to dial-up access or AOL. Hopefully only one possibility will remain.)
Add/Edit/Remove/Move entries as appropriate, until only the two IP addresses listed above remain.
Re-boot the machine if prompted to do so.
Banner should now work properly.
Another possible cause
The ORA-12545 error can also occur if other TCP/IP properties are improperly configured, so that TCP/IP itself is not working. In that case, no IP communication will work (e.g. Web browsing). Fixing it is in the LAN manager's domain and will not be further discussed here.
ORA-12545
This error occurs when the client computer tries to look up the hostname of the database server (for example dbp.banner.mcgill.ca) to get its IP address. The lookup is failing.
In most cases we have seen, the results are wrong because an old Domain Name Server (DNS), no longer kept current, is still available and many PCs around campus are still pointing to it. It is incorrectly reporting that the Banner database server does not exist. Since the old DNS works fine for most other addresses, users have not realized there was a problem until now.
The solution is to change the client computer's TCP/IP properties to point to the correct DNS addresses. Typically only two addresses should be listed: one for the primary DNS, and one for the secondary (alternate) DNS:
132.206.44.21
132.216.44.21
Different computers/operating systems have different dialogs for changing this. The general approach is:
Edit the Properties of Network Neighborhood (known as "My Network Places" in Windows 2000).
Navigate/drill down until you find the TCP/IP protocol, and edit its Properties. (If there are several TCP/IP entries found, ignore anything which refers to dial-up access or AOL. Hopefully only one possibility will remain.)
Add/Edit/Remove/Move entries as appropriate, until only the two IP addresses listed above remain.
Re-boot the machine if prompted to do so.
Banner should now work properly.
Another possible cause
The ORA-12545 error can also occur if other TCP/IP properties are improperly configured, so that TCP/IP itself is not working. In that case, no IP communication will work (e.g. Web browsing). Fixing it is in the LAN manager's domain and will not be further discussed here.
jljlwsy 2002-10-21
- 打赏
- 举报
我也觉得是网络问题
penitent 2002-10-21
- 打赏
- 举报
这种情况一般发生在网络不好的情况下，由于某一时间客户机与服务器断开，等一会儿又连接上了。但是给我们的感觉是一直连接。
如果是应用程序。我们的解决办法就是一旦发生这种错误或是ora-03113错误，即断开原有连接并重新连接数据库即可。
如果是应用程序。我们的解决办法就是一旦发生这种错误或是ora-03113错误，即断开原有连接并重新连接数据库即可。
penitent 2002-10-21
- 打赏
- 举报
网络不好，如果是应用程序，可以重新连接即可。
Hongky 2002-10-21
- 打赏
- 举报
谁解决，我再送100分！！！！！
Hongky 2002-10-21
- 打赏
- 举报
本来就是IP的啊！！！
luckysxn 2002-10-21
- 打赏
- 举报
试一下把TNSNAMES.ORA文件的HOST=你的服务器IP
TNSNAMES.ORA在C:\oracle\ora81\network\ADMIN下
TNSNAMES.ORA在C:\oracle\ora81\network\ADMIN下
Hongky 2002-10-21
- 打赏
- 举报
高手们，救命啊！
