Tuesday, October 16, 2012

Open Encumbrance Year: Slow Performance

At our site this concurrent program was too slow. It did not complete even after 1 week. During that time, DBAs recycled concurrent managers, so this program was restarted. When this program runs, I think it checks for existence of records for current year, if record exists then it deletes using following sql. This sql too was taking too much time.

I think that sql is executed in a loop and there must be a commit after deleting 5000 rows. i think this is being done to avoid snapshot too old or something.

In my experince with Oracle, i have seen this kind of delete in Oracle Pricing too. It was highly inefficient. It would have been much better if Oracle had used a script like

No comments:

Post a Comment