> LI-V6.3.2.4731 1.5 Classic, RedHat Enterprise, 9G database
>
> In the evenings when gbak �g is running the clients are encountering

lock

> conflict on no wait transaction
>
> Deadlock
>
> Update conflicts with concurrent update

This is a normal exception in a multi-user environment that has
absolutely nothing to do with gbak. It means two concurrent
transactions are trying to modify or delete the same record.

A backup only reads data (so no risk of lock conflict). A restore must
be done with exclusive access, so again no risk of lock conflict.

Adam

This particular table is being accessed all day, but only between 22.00 and
24:00 when gbak �b �g is running and there are approximately 3 users
connected (otherwise 30 � 50) the problem arises, so i assume that this two
things are correlated.

Regards Bogdan


No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.24/1117 - Release Date: 7.11.2007
22:52



[Non-text portions of this message have been removed]