I correct myself from the previous post: when I validated again, I did
not do a full validation but a simple one.
When trying a full validation ( gfix -validate -full ... ) I got the
same error message:

"Summary of validation errors
Number of record level errors : 1"

I did a gfix -mend -full with the same result and a gfix -mend -full
-ignore with the same result.
I had no alternative than do a backup and restore to solve the problem.
After the restore, a full validation gave no error.

Now my questions are the following:

1) Why and under which circumstances a client process can lock forever ?
2) Does this and / or the fact that I restarted the firebird service
produced a database corruption or loss of a table record ?
3) Why the error message doesn't mention the table which has a record
level problem ?
4) Did I lose information ?
5) The gfix -mend didn't work. Nevertheless the backup could be done. Is
this normal ?

Thanks,
Aldo


El 06/01/12 11:16, Aldo Caruso escribió:

>
> Hi,
>
> I'm using firebird 2.0 on Linux, Debian 5.0 distribution.
> I tried to execute an update sql query from a client machine (
> using flamerobin ) and I got a lock conflict message ( other users were
> connected at the same time, perhaps updating the same records of the
> same table ).
> I rolled back, and tried again but the query lasted for ever. I
> tried again and again, but the query still lasted for ever. I stopped
> the server an restarted it, with the same result.
>
> After this, I got exclusive access to the database and performed a
> full validation (using gfix). The output message was:
>
> "Summary of validation errors
> Number of record level errors : 1"
>
> I validated again and then no error was shown.
>
> My question is: Should I assume that the error was corrected or
> must I do a backup and restore to be sure ?
> ( I haven't still tried the update query again)
>
> Thanks for any help,
> Aldo
>
>

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