Q
Problem solve Get help with specific problems with your technologies, process and projects.

"TNS: Operation timed out" error

I have installed Oracle 9.2.0.1.0 on Windows XP sp2 and installed all latest XP security patches updates. My problem: I can connect to my instance (gali) if I type conn scott and type tiger (password) but if I type conn scott@gali and then type password (tiger) I get a "TNS-12535:TNS:operation timed out" error.

Maria Anderson
By
Published: 21 Sep 2005
I have installed Oracle 9.2.0.1.0 on Windows XP sp2 and installed all latest XP security patches updates. My problem: I can connect to my instance (gali) if I type conn scott and type tiger (password) but if I type conn scott@gali and then type password (tiger) I get a "TNS-12535:TNS:operation timed out" error. I also tried to look up sqlnet.ora logs and I found one more "TNS-12638: Credential retrieval failed" error there.

I am using a Dell laptop with 1 GB RAM and 80 GB hdd with Symantec Antivirus and McAfee Firewall running on a Win XP sp2. I tried doing all these workarounds but it was no use:

  1. Disabling the firewall and connecting.
  2. Adding a connect_timeout_listener parameter to the listener.ora file and setting it to 1000 or zero.
  3. Changing sqlnet.authentication_services to none(NTS).

Can you please suggest some other workarounds? Do I need to create another instance and try? Do I have to reinstall Oracle again? Thanks in advance.

My first suggestion would be to check whether the listener is up and running on the server where the database resides. On Windows, there should be a listener service visible from the Services panel and it should be running.

Another way to check is to exit to the DOS prompt and type in: 

lsnrctl status
This should report back information about the instances this listener is listening for.

My second suggestion is to include the parameter local_listener in the init.ora or spfile so that it correctly identifies the listener. This is not required but may help the instance register with the listener if you find (from performing the above command) that the instance has not registered with the listener. Note that it may take up to 60 seconds after startup for an instance to register with the listener.

Finally, you should check to make sure that the information contained in your tnsnames.ora file is correct. In particular, check that there is an entry for the Oracle instance you are trying to connect to and that the proper hostname or IP address is used.

Dig Deeper on Oracle database installation, upgrades and patches

Start the conversation

Send me notifications when other members comment.

Register

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close