A few months ago, I was confused and changed the machine name from "south" to "southyj ". It took a long time to discover that Oracle cannot be used. Check the cause. It turns out that when Oracle is installed, the directory will be generated based on the machine name, and the machine name will also be written into the listening configuration file and connection configuration file. Search for the old machine name "south" in the Oracle directory, replace all the searched "south" with "southyj", and open the oracle \ product \ 10.2.0 \ db_1 \ NETWORK \ ADMIN directory, set listener. ora and tnsnames. the machine name in the ora file is also corrected. As a result, the world has restored its old order. Everything is perfect.
Who knows I have more than once. When IIS is configured today, an error is always reported:
System. Web. Services. Protocols. SoapException: the server cannot process the request. ---> System. Exception: ORA-12154: TNS: failed to parse the specified connection identifier
Connect with PL/SQL Developer and find that the database can be accessed normally. Check the listener. ora file and no exception is found. That's amazing!
In the cmd window, enter:
C: \ Documents ents and Settings \ Administrator> tnsping localhost
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0-Production on 14-12-
14:28:31 2009
Copyright (c) 1997,200 5, Oracle. All rights reserved.
Used parameter files:
C: \ oracle \ product \ 10.2.0 \ client_1 \ network \ admin \ sqlnet. ora
Alias resolved using EZCONNECT Adapter
Attempting to contact (DESCRIPTION = (CONNECT_DATA = (SERVICE_NAME = localhost) (addh
SS = (PROTOCOL = TCP) (HOST = 127.0.0.1) (PORT = 1521 )))
OK (10 ms)
The result is normal at first glance. Then,
Used parameter files:
C: \ oracle \ product \ 10.2.0 \ client_1 \ network \ admin \ sqlnet. ora
"Client_1 "? When have I installed a client? It's really a mess of mind.
Copy listener. ora and tnsnames. ora from the oracle \ product \ 10.2.0 \ db_1 \ NETWORK \ ADMIN directory to the oracle \ product \ 10.2.0 \ client_1 \ NETWORK \ ADMIN directory. The world has finally recovered to normal.