Holger Baer wrote:
> ODBC/JDBC connections involved? There are drivers that by default
will
> parse a query before execution to get a 'describe' of the columns
returned
> by the query.
>
> Now if the programmer was aware of the fact that Oracle likes
preparsed
> queries (parse once, execute many), she might have tried to create
> all possible cursors up front in a separate module, but never got
around
> to use those cursors for what reason ever.
>
> I was never able to get rid off all of these parses with ODBC so I
threw away
> those applications where possible or made them use the native driver
> (those where my own applications).
>
> In short: I'd consider this a bug in the application.
>
> And to simulate this: DBMS_SQL is your friend.
The architecture is client - OCI -> local database (8.1.7.4) - database
link -> central database (9.2.0.6, here was traced!). These SQLs
definitely came from the branch application, because I traced it using
after logon trigger triggered on a specific aplication user. So I think
there is some problem inside the code. I have contacted our developers
responsible for this just in case they will come with some sensible
idea. I also have doubts about these database links, because there are
already causing a lot of other problems. Maybe the reason for this
behaviour is in a way how Oracle is processing queries in the
distributed environment between different DB versions.
--
Dusan Bolek
Received on Wed Mar 23 2005 - 02:26:34 CST
