Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Slow UPDATE
Hi Thomas if most of that data don't need to be updated you can try adding
WHERE
NOT CURR_KEY = :1 AND NOT CUSTOMER_ID = :2 AND NOT CREATED_BY_ID =
:3,........................
I optimized in that way an update from 3 minutes to 10 seconds. But I don't know if this is the same situation in you. Give I try if this don't solve your problem maybe I can give you another idea.
Better if you get an statpacks reports, this gives more information about
the current worload you have.
If you don't have an oltp
try to get use
start statpacks (before the events you want to monitor)
EXECUTE STATSPACK.SNAP(i_snap_level=>7);
After that events happens stop statpacs
EXECUTE STATSPACK.SNAP(i_snap_level=>7); This gives the most informatoin but can take some resources.
Maybe the reason for the time is anothe process, not the update process.
Can't you do all in only one update, I saw a 200 executions? Can you post your code.
UPDATE OD_CUST_LOCS SET CURR_KEY = :1, CUSTOMER_ID = :2, CREATED_BY_ID =
:3,
CHANGED_BY_ID = :4, CREATED_ON_DT = :5, CHANGED_ON_DT = :6,
PSTL_GEO_LOC_ID
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Sat May 15 2004 - 17:15:46 CDT
![]() |
![]() |