cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle Error : ORA-12170 : TNS Connect timeout occured (WIS 10901)

Former Member
0 Kudos

Hi,

I have a strange behaviour in my BO XI environnement (BO XI 3.1 sp3 / windows2008 R2 / websphere 7.0)

I try to refresh a webi document using the java applet and I have the following message : "ORA-12170 : TNS Connect timeout occured (WIS 10901)" (the error occurs about 20 seconds only)

What is strange is that the same webi document works perfectly if I use the RichClient...

The SQL request works fine (tested in Oracle)

Any help on this case would be greatly appreciated

Thanks,

David

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

The ORA-12170 error can be for many reasons, firewall issue, database down, listener down, bad sqlnet.ora parm, network trouble, etc. 


If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).


thanks

Former Member
0 Kudos

Finally,

The reason of this strange error message was quite simple : a firewall on the database server !

Thanks for your help

David

Former Member
0 Kudos

Hi,

How can we check if there is a firewall on the database server??

Former Member
0 Kudos

Hello Karishma,

Usally, firewalls are managed by a Security Team. If you have this kind of team responsible of your environment, I guess it would be easy for them to answer this question.

As I'm not a security specialist (far from it !) there is nothing more I can't say, sorry.

Hope this helps anyway,

David

Former Member
0 Kudos

Thanks for your help..

Former Member
0 Kudos

Hi David,

ORA-12170: TNS:Connect timeout occurred

Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.

Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).

All the Best,

Madhu...

Former Member
0 Kudos

Thank you all,

The problem (not solved yet) is probably in relation with the listener parameters.

I'm going to check these timeout parameters with my DBA.

I'll let you know the results.

Thanks,

David

Former Member
0 Kudos

Try the following steps:

Check the Oracle client installation version

Locate the Oracle client installation path (for example, c:\oracle\ora90).

Open the DOS command prompt by clicking Start > Run and typing "cmd".

Test the following command:

TNSPING <Database Name>

Check the System Path for Oracle client (for example C:\oracle\ora90\bin).

Check the TNSNAMES.ora and SQLNET.ora files. In this case, the SQLNET.ora file did not exist so it was copies to C:\oracle\ora90\network\admin.

Restart the machine.

This worked for me.

Former Member
0 Kudos

Hi,

The ORA-12170 error can be for many reasons, firewall issue, database down, listener down, bad sqlnet.ora parm, network trouble, etc.

These links may be help you:

http://www.dba-oracle.com/t_ora_12170_tns_connect_timeout.htm

Former Member
0 Kudos

Hai David ,

It's not a problem with BO XI ,it's with the database.

Contact your BusinessObjects administrator with the error message information or consult the documentation provided by the supplier of the database.

Former Member
0 Kudos

Please check with BOBJ administrator about connection timeout in CMC. Thanks