Devart Forums

We are using direct mode to access Oracle database from Azure, across the internet and through firewall (that is, we are not using MPLS into Azure for this.)

We are using hard-coded connection string including IP and port for connection via direct mode. We are not using TNS or Oracle drivers, but we are periodically getting ORA-12170, hard down, have not figured out how to reset for this. It can continue for hours and then just stop before we use it again. We are pretty sure we are not being blocked at firewall. Less sure about the database accepting connection.

Is there anything obvious we should be looking at?

Also, how does devart return "ORA-xxxxx" numbers without Oracle client? Is there any assurance that you will return exactly the same errors as Oracle in all cases? We are a bit concerned that we are getting TNS errors without using TNS, and wonder if this is some sort of glitch.

Try increasing your value of the Connect Timeout connection string parameter (by default, 15 seconds).

If this doesn't help, we need to reproduce the issue so that we can investigate it. Send us a test project for reproducing it and/or provide access to your Oracle Server.

I am working with the OP in attempting to solve this issue. We are still experiencing this issue intermittently, so producing a shareable project is proving difficult. However, the second part of the question below is still important to us;

Also, how does devart return "ORA-xxxxx" numbers without Oracle client? Is there any assurance that you will return exactly the same errors as Oracle in all cases? We are a bit concerned that we are getting TNS errors without using TNS, and wonder if this is some sort of glitch.

Because we are receiving this error immediately, i.e. with no timeout wait, we are concerned that this error is being thrown by DevArt, and are concerned about this. Is

ORA-12170 TNS: Connect timeout

being used as a catch all?

1. Refer to https://docs.microsoft.com/en-us/window ... or-codes-2:
WSAETIMEDOUT (10060) -> Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

When our provider receives WSAETIMEDOUT, it generates "ORA-12170 TNS:Connect timeout occurred, but not using TNS".

2. If Oracle Server is not available, the error can be thrown before Connect Timeout is reached.

cpurick wrote: ↑Mon 06 Jul 2020 20:52we are periodically getting ORA-12170, hard down, have not figured out how to reset for this. It can continue for hours and then just stop before we use it again.

3. When the issue occurs, reconnecting with conn.Open() doesn't help, does it?

If your Oracle Server is down, contact Oracle administrator.

cpurick wrote: ↑Mon 06 Jul 2020 20:52 Is there anything obvious we should be looking at?

Maybe you are like me and have a dblink in the query ... the dblink will still use TNS