One resolution of TNS-12560
Yesterday, a background database of our company's customer service department appeared TNS-12560 issues. Their web maintenance personnel didn't get it for two days. Later, I went to help him. I just thought that the server was placed in our company. I promised him to help him get it. Later, when I went to their sectors, he told me that the server was hosting in Telecom's IDC center. Thinking, but he is very poor (their manager blows every day, can be blown every day Resigning him). After I arrived at the IDC center of Telecom, I regretted, TMD, the service inside the number of services is unclear. It can be seen that there is more radiation, I have stayed in it for more than an hour, after coming I am fainting, I can't stand it!
Returning to the topic, let us see the TNS-12560 error this time. This error believes that someone often encounters, generally knows what is going on. Just if there is this error, I have seen a person who doesn't understand before. Or some information to check that some stuff will not pay attention to all the stuffs he changed when he goes to see all the stuff, which is there (too strong radiation).
OS: Windows 2000 ADS.DB: Oracle 8.1.7
First of all, I see that the service is started. ------- has started
Look at the configuration of Listener.ora. ----- There is a problem, no monitoring database. There is a problem here. I use Net8 to reconfigure Listener. First remove the original listner. Then recreate one. Remember to configure the database service This piece. Restart the service, you can start.
Conn sys / oracle as sysdba. -------- still have an error. Follow TNSNAMES.ORA. No problem. I tried to use conn sys / oracle @ oracle as sysdba. No, insufficient permissions. Retraced CONN System / Oracle @ Oracle is still not, there is a mistake. (Do not write down the wrong number), then look at SQLNET.ORA. There is a problem with a parameter oname (notified). I will comment this line. And modify The order of Names.Directory_path, TNSNames, Hostname, onames. Then use conn sys / oracle @ Oracle as sysdba. Or don't do the wrong username (that person has changed the password in advance). Re-use CONN System / Oracle @ Oracle As sysdba.ok. I am strange, how to use SYSTEM, and use SYS can't do it? Thinking of it may use a password file authentication method. Remote_login_passwordfile = Exclusive. Then rebuild the password file. OvalPwd file = pwdoracle.ora passWord = Oracle Entries = 10. Then conn sys / oracle @ Oracle As Sysdba.ok.
Try the client. Conn System / Oracle @ Oracle As Sysdba. Can't configure SQLNET.ORA and TNSNAMES. ORA. Modify to be the same as the server. OK.
Description Little, the rest of the listener.ora, TNSNAMES.ORA, and SQLNET.ORA files will be restarted after the next reconfiguration.
