There are times when IB starts doing some kind of processing, what I don't
know, and it uses at least 50 % of the processor or more and won't allow any
users to login to any database during this time. And the process usually
runs a
long time. The other day when it happened on my local Interbase I let it
run all night and came in the next day and it was still running. I end up
having to stop the service (which itself can take 15 or 20 minutes) and
restart it.

We have sweep set to zero on all of our databases, too, so I don't think it
is sweep. The last time it happened to me on local IB was when I ran a
simple select query using IB_Sql. The query ran fine but when I exited the
query IB started doing what I just described.

This happens regularly, about once per week or so.

This has happened on my local InterBase, our shared development IB server,
and our production IB server (which is a real bummer).

Note: most of the time this happens when one of the users exits our app. I
have checked and rechecked our transactions to make sure they are all
commited regularly (every 200 records for our batch jobs which is most of
what we do in-house on IB) and all looks fine to me.

We are using IB 6.01 on production, and IB 6.0.1.6 on my local and the
development server. We use Delphi 5 pro and IBX 4.61. All workstations and
servers use Window 2000. Our production servers are Win2K terminal servers.

Thanks for any help you can give.



--

Don Gollahon
(gollahon@...)