Subject | internal gds software consistency check (cannot find record back version (291)) |
---|---|
Author | Steve Wiser |
Post date | 2006-03-13T13:18:01Z |
Hi,
On an Interbase 5.6 database (running on linux) we have a stored
procedure that runs from cron that has been dying for the past few
days. When we look in the /usr/interbase/interbase.log I see the following:
linux8 Fri Mar 10 15:34:10 2006
Database: /usr/interbase/databases/srw.test.gdb
internal gds software consistency check (cannot find record back
version (291))
I have narrowed it down to 1 insert statement in the table that seems to
cause this to happen. However, it looks like it is not the insert
statement, but maybe something that the triggers run. I am still
tracing out what the triggers are doing and trying to replicate their
logic by hand to find out the exact statement that causes the crash.
These same triggers do run for many other records, it just seems to be
when I insert 1 particular record that causes this crash.
Anyways, does anyone know what this error means? We have run IBFirstAid
on the database, but it didn't find any corruption. I repaired a copy
of it anyways but that didn't make the problem go away. Also gfix -v
-full doesn't see any problem with the database. And it will backup and
restore fine. Anyone have any insight into this?
Thanks,
Steve
On an Interbase 5.6 database (running on linux) we have a stored
procedure that runs from cron that has been dying for the past few
days. When we look in the /usr/interbase/interbase.log I see the following:
linux8 Fri Mar 10 15:34:10 2006
Database: /usr/interbase/databases/srw.test.gdb
internal gds software consistency check (cannot find record back
version (291))
I have narrowed it down to 1 insert statement in the table that seems to
cause this to happen. However, it looks like it is not the insert
statement, but maybe something that the triggers run. I am still
tracing out what the triggers are doing and trying to replicate their
logic by hand to find out the exact statement that causes the crash.
These same triggers do run for many other records, it just seems to be
when I insert 1 particular record that causes this crash.
Anyways, does anyone know what this error means? We have run IBFirstAid
on the database, but it didn't find any corruption. I repaired a copy
of it anyways but that didn't make the problem go away. Also gfix -v
-full doesn't see any problem with the database. And it will backup and
restore fine. Anyone have any insight into this?
Thanks,
Steve