Shulou(Shulou.com)06/01 Report--

1. The tnsnames.ora file name has been modified

TNS-03505: Failed to resolve name

2. IP or hostname cannot communicate with ping

TNS-12543: TNS:destination host unreachable

3. The hostname cannot be resolved (involving hosts files or DNS)

Both TNSPING and SQLPLUS reported an error: ORA-12545: Connect failed because target host or object does not exist

4. The port is not open

ORA-12541: TNS:no listener

5. The firewall does not open the port or the tns file is inconsistent with the port in listener.

TNSPING reported an error as: TNS-12535: TNS:operation timed out

SQLPLUS reported an error as: ORA-12170: TNS:Connect timeout occurred

6. The specified service name of service_name does not match that of monitoring.

I can get through TNSPING.

SQLPLUS connection error: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

7. Monitoring is not enabled

ORA-12541: TNS:no listener

8. Error reporting when connecting to RAC

ORA-12545:Connect failed because target host or object does not exist

The solution is to modify the local_listener parameter of RAC and change the value of HOST= in the parameter value to the VIP or scanip-- of the current node. Note that it is IP instead of hostname, and the client can connect to the RAC database through SCANIP or VIP.

For details, see: http://blog.csdn.net/haibusuanyun/article/details/17737553

9. The shared mode is connected to static monitoring

ORA-12523: TNS:listener could not find instance appropriate for the client

Reference documentation:

Http://blog.csdn.net/haibusuanyun/article/details/14517211

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.