Cherie,
I'd run this function with 2 events separately ...
first 10938 this will give you pl/sql profiling or simply use dbms_profiler package. This will tell you where (and at which line) you are spending most of your time. Metalink has some really good stuff on profiler ...
Then of course 10046 which will give you SQL profiling and you can concentrate on SQLS. I believe here you have to attack this problem on both fronts. I believe pl/sql tuning will be easier (I think) than SQL.
Are you running the code on the souce DB?
How big is acct_pay_type table? If it is less than 2000 rows, can you pre-load it as a pl/sql table so the selects can be avoided? I believe even some of pl/sql can be re-arranged to be a bit faster. But it is all relative. Have your developer sthought about using bulk-inserts and bulk selects?
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!
*********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************1
