PerkinElmer Informatics Support Forum
Decrease font size
Increase font size
Topic Title: Connection Error appear after an extended period of time, or after the server has been under load
Topic Summary: ORA-12545: Connect failed because target host or object does not exist
Created On: 3/26/2012 3:19 PM
Status Post and Reply
Linear : Threading : Single : Branch
Topic Tools Topic Tools
View topic in raw text format. Print this topic.
Answer This question was answered by Aldo, on Tuesday, March 27, 2012 12:22 PM

Answer:

Answer:

An ORA-12545 error might occur when the client is not able to contact the listener on the node specified. For example: when the listener has not been started on the node, if the node address has been specified incorrectly or a firewall blocks access. It might also been due to network problems.

Check the connectivity when the error appears. Do the following in the dataserver :

1. Type in a command line lsnrctl status, to see the listener status

2. Do a tnsping to the database, to see if it can be reach.

Possible solution:

Restart the listener. You can do it within a command line by typing:

a) lsnrctl stop

b) lsnrctl start

Another workaround is to reboot the server.

 3/26/2012 3:19 PM
User is offline View Users Profile Print this message


Aldo

Posts: 41
Joined: 7/11/2011

Issue:

An ORA-12545 error messages appears on the login screen after an extended period of time, or after the server has been under load (for example, when a lab is preforming a yearly inventory of their stock). The full error message shown is:

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

Restarting IIS doesn't help.



Edited: 3/26/2012 at 3:28 PM by Aldo
 3/26/2012 3:21 PM
User is offline View Users Profile Print this message


Aldo

Posts: 41
Joined: 7/11/2011

Answer Answer

Answer:

An ORA-12545 error might occur when the client is not able to contact the listener on the node specified. For example: when the listener has not been started on the node, if the node address has been specified incorrectly or a firewall blocks access. It might also been due to network problems.

Check the connectivity when the error appears. Do the following in the dataserver :

1. Type in a command line lsnrctl status, to see the listener status

2. Do a tnsping to the database, to see if it can be reach.

Possible solution:

Restart the listener. You can do it within a command line by typing:

a) lsnrctl stop

b) lsnrctl start

Another workaround is to reboot the server.



Edited: 3/27/2012 at 12:21 PM by Aldo

FuseTalk Basic Edition v4.0 - © 1999-2017 FuseTalk Inc. All rights reserved.