|Subject||Re: Lock conflict|
> LI-V18.104.22.16831 1.5 Classic, RedHat Enterprise, 9G databaselock
> In the evenings when gbak g is running the clients are encountering
> conflict on no wait transactionThis is a normal exception in a multi-user environment that has
> Update conflicts with concurrent update
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.