Bug in oradirect 3.0.1.2 with work expensive sql statements
Posted: Tue 16 Aug 2005 12:26
Hi,
our team has updated oradirect to version 3.0.1.2 because we wanted to use the direct connetion mode (without using any oracle client).
Now, we've figured out some troubles with expensive sql statements in the direct mode.
If we execute the same query in indirect mode it takes a long time to get the result (which is not that big (less than 50 rows)). But it works fine in this mode.
If we want to do the same query in direct mode, we get an unhandled exception.
thx for helping.
so long,
nerVouz
p.s. changing the "connection timeout" paramter to higher or lower values did't take any effects.
our team has updated oradirect to version 3.0.1.2 because we wanted to use the direct connetion mode (without using any oracle client).
Now, we've figured out some troubles with expensive sql statements in the direct mode.
If we execute the same query in indirect mode it takes a long time to get the result (which is not that big (less than 50 rows)). But it works fine in this mode.
If we want to do the same query in direct mode, we get an unhandled exception.
Code: Select all
'CoreLab.Oracle.OracleException' in system.data.dll
additional information: NET: Network error (System.Net.Sockets.SocketException
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size))
'CoreLab.Oracle.OracleException' in corelab.oracle.dll
additional information: NET: Network error 200so long,
nerVouz
p.s. changing the "connection timeout" paramter to higher or lower values did't take any effects.