= m. Th = wrote:

> Hi,
>
> From some reason outside the scope of this eMail, an application enters
> in a deadlock. Ok, this isn't desirable, but it happens. But once it
> happens how can we solve it?

Rollback the affected transaction and proceed? When there's a deadlock,
one transaction will get an error message from an update or delete
request. When that transaction rolls back, the deadlock is gone and
processing will continue.

Perhaps I don't understand what you mean by a deadlock, but nothing
should require either of these steps:

> 1. Log-off all the clients of the application (by closing it) which are
> scattered on the network. This implies phone-calls, messages aso.
> 2. Brutally shut down the server. But this kills also the other
> databases attached on it.

Regards,


Ann