List,
Truncating the table solved the problem. Since I inserted 2
million rows into a parent table then deleted all of them the Oracle high
watermark was very high.
This still doesn't explain the difference between DBD::Oracle and
sqlplus. They must have had different execution plans internally somehow.
Thank you everyone for your help and ideas.
Mike Towery <mtow...@gmail.com>
12/13/2010 01:35 PM
To
<dbi-users@perl.org>
cc
<ericbamba...@discover.com>
Subject
Re: DBD::Oracle dbd_st_execute slow speed
I would suggest you do a 10046 trace on the perl job and looked at what
is causing the waits. Also with 9i and above there is wait option is
included in Tkprof. This will provide some insight on what the database
is waiting on.
You can google 10046 oracle trace if you need information on how to do it.
Regards,
Mike Towery
Please consider the environment before printing this email.
