Subject | Re: [ib-support] Re: Delayed updates to databases (Urgent !!!!!!!!!!!!!!!!!!!!!!!!!!!!) |
---|---|
Author | robert-wagner@t-online.de |
Post date | 2001-06-05T19:39:30Z |
Hi Jesus Olague,
while reading the answer of Ann, I saw a lot of errors in the log file
which I saw recently at a customer site, especially:
interbase service they could work again for some time and then again the
deadlock error occured.
In my case *one* of approx. 50 users used a different connection string
to the database.
I would check a second, a third and a fourth time that *all* users use
the same path to the database. Of course the database was corrupted.
Thanks god the database could be backed up and restored after one
damaged table was dropped.
Good luck.
Robert
while reading the answer of Ann, I saw a lot of errors in the log file
which I saw recently at a customer site, especially:
> ENVATAP1 (Server) Thu May 31 16:51:23 2001and
> Fatal lock manager error: release when not active, errno: 0
> ENVATAP1 (Server) Fri Jun 01 16:13:27 2001and
> Database: F:SIPV3R2\BASE DE DATOS\DBSIP.GDB
> internal gds software consistency check (cannot find tip page (165))
> ENVATAP1 (Server) Mon Jun 04 07:17:56 2001Users also complained about deadlock errors. After restarting the
> Database: F:\SIPV3R2\BASE DE DATOS\DBSIP.GDB
> internal gds software consistency check (pointer page vanished
> from mark_full (256))
interbase service they could work again for some time and then again the
deadlock error occured.
In my case *one* of approx. 50 users used a different connection string
to the database.
I would check a second, a third and a fourth time that *all* users use
the same path to the database. Of course the database was corrupted.
Thanks god the database could be backed up and restored after one
damaged table was dropped.
Good luck.
Robert