> I have check that. First, we have closed an application "A". After this,
> the 5-minutely executing isql-script does not work and hangs (dos-box) The
> transactions stops! Oldest for example 500000 and next 510000, a difference
> of 10000 but next transaction does not count continuous. The difference can
> be a result of our developing with IBEXPERT. At this time, we cannot
> connect again or new connect to our database! One fb_inet_server process
> uses 50% cpu capacity. If I kill this process, it works fine again!
>
> At this moment I have test this again. But if the Application "A" runs not
> a long time, the problem does not occur.
>
> Can you see the problem in the look_print?: What's wrong, that our database
> froze?

I've never used classic at all, so what I write here may not be correct! If you have two processors and have set the CPU affinity to use just one of them (the benefit with classic would normally be that you can use several processors, but maybe it still adheres to what you've set the affinity to be), then 50% CPU means that one of the processors is extremely busy doing something and things may appear to hang. Are you sure there are no extremely time consuming queries taking place? I suppose that if you every 5 minutes start a script that lasts more than 5 minutes, then it doesn't take long before you run into trouble. So, is there anything in the script that would either be time consuming or cause problems if the next execution of the script was started before the last execution finished?

HTH,
Set