RE: Slow commits

How about Explain Plan? Tkprof?

Know your data. Never trust developers. Follow them wherever they go.

You might get arrested for stalking, but your database will be the better for it.

:>)

--Walt Weaver
  Bozeman, Montana, USA

-----Original Message-----
From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Kristen Cameron
Sent: Friday, May 12, 2000 6:17 PM
To: Multiple recipients of list ORACLE-L Subject: Slow commits

I am a brand new DBA, and apologize in advance for the far too general nature of my question. However, I have reached the end of my meagre knowledge. I'm looking for a little guidance from the more experienced. I've attached BSTAT/ESTAT reports for the truly generous, along with a couple of other text files of statistics. Contact me if you want them but didn't receive them.

Using an Oracle Forms application, users are finding that commits take 3 to 5 minutes when done on certain tables in the database. It would seem that the problem should be obvious, but I cannot find it. There are about 15 tables involved in the part of the application that is experiencing this slowdown. Most of them are look up tables, but a few are relatively large (10,000+ records) tables of data that are being updated. The tables seem to be indexed reasonably. Most items are referenced using an id number, and the id column is indexed either alone or jointly with another column.

We are using Oracle 7.3.4 on Sun Solaris 2.6. Our users are using Windows 95. Our network is Novell.

To date, I have run all kinds of statistics on the database, but have found no problems. CPU, memory, storage, waits, latches, I/O, locks, hit ratios, etc. all seem good. There may be some disk contention, but it appears minimal and may be unavoidable, since we only have two processors, anyway. Actually, on the whole, the numbers look fantastic, as near as I can tell from my reading on the subject - Oracle documentation, online articles, Niemiec's book on Performance Tuning, and Loney's DBA Handbook.

At this point, I am assuming that the problem is within the application code itself, especially since it began when the application was developed. However, it seems to be getting worse.

Is there anything further I can do to test it, or better yet, fix it?

Thanks for any and all help.

• Kristen Cameron