It appears that you are seeing the parse done by DBD::Oracle
to describe the table.
Look at the DBI docs for ora_check_sql. Turn it off and
the extra parse should go away.
Jared
On Thu, 2005-12-08 at 11:00 -0500, Peter Santos wrote:
> Dear users,
> I'm hoping to get some insight into why oracle
set the bind variables to a new value. This
gives me 1 hard parse and 2 soft parses
and ONLY 1 cursor in the database (V$SQL).
HTH
--peter
Reidy, Ron wrote:
This does not look the same. Where are the bind variables?
-----Original Message-
From: Peter Santos [mailto:[EMAIL PROTE
Reidy, Ron wrote:
Peter,
Can you repeat this same issue in SQL*Plus?
--
Ron Reidy
Lead DBA
Array BioPharma, Inc.
-Original Message-
From: Peter Santos [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 9:00 AM
To: dbi-users@perl.org
Subject: re: Oracle 10g and DBD::Oracle
This does not look the same. Where are the bind variables?
-Original Message-
From: Peter Santos [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 7:32 AM
To: Reidy, Ron
Cc: dbi-users@perl.org
Subject: Re: Oracle 10g and DBD::Oracle
No this issue is not repeatable in SqlPlus
Peter,
Can you repeat this same issue in SQL*Plus?
--
Ron Reidy
Lead DBA
Array BioPharma, Inc.
-Original Message-
From: Peter Santos [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 9:00 AM
To: dbi-users@perl.org
Subject: re: Oracle 10g and DBD::Oracle
Dear users,
I&#
Dear users,
I'm hoping to get some insight into why oracle creates 2 cursors for
the same sql query when I execute a SELECT statement via my small little
perl script.
Here is what is happening .. My query uses 2 bind
variables and when it is prepared oracle generates 1 cursor for my
query.
W
