-none- 2007-09-05 - By Grant Allen
Back Alvaro Jose Fernandez wrote: > > Hi Dennis, > > > > Thanks for the comments. No, this is Oracle bug in the implementation > of the provider, since if we use (for example) Microsoft OLEDB > provider, these queries are not generated. > > > > Anyway, thanks for your comments. > > > > alvaro > Alvaro,
A couple of things might be useful in helping you with this. The connection string used (no need to include the password or real server/user names), the connection object's properties (a very simple bit of VB should be able to iterate over these and print them out ... ask your VB devs), and the OLEDB_SERVICES value for the Oracle OLE DB provider from the registry.
In 11 years of writing c++, c#, and vb against Oracle's ODBC driver and OLE DB provider, I never saw your symptoms ... and we had regular religious wars about the comparative merits of server-side versus client-side cursors.
One other thing springs to mind as well. Is your VB code calling Oracle stored procedures, and do these stored procedures include declarations using %TYPE or %ROWTYPE? There are hideous bugs (i.e. massively increased sql noise and network traffic) with Oracle's implementation of these technologies in combination ... I can elaborate if this matches your situation.
Ciao Fuzzy :-)
-- ---- ---- ---- ---- ---- ---- ---- ---- ----- Dazed and confused about technology for 20 years http://fuzzydata.wordpress.com/ -- http://www.freelists.org/webpage/oracle-l
|
|