| Subject | Re: [firebird-support] consistency check error |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-01-19T02:03:27Z |
At 10:11 AM 19/01/2008, you wrote:
The engine does need to have access to both the database file and the output file for the duration of the backup. It appears to have been the case when the backup began since, by the time it is ready to back up table data, it has already backed up the database header and the metadata. However, if it runs out of disk space before the backup completes, of course the backup will fail. If that happened, the message sent by the operating system might have made it to the firebird.log.
Another cause could be if you have some other application on the system that starts up after the backup began, that locks part of the hard disk that the backup file is using, or needs to use. For example, check whether some scheduled disk maintenance procedure started up, such as a filesystem backup program, or a disk scan, or a defrag, that arbitrarily locks blocks or partitions. If your database or backup file are on Windows, some native Windows file and disk maintenance tools don't respect any exclusive locks.
If you are writing the backup file to a remote location, of course it could be that the backup routine can no longer find the backup file...again, there's a chance that the engine was able to write a firebird.log message before it shut down.
Or it could just be that you don't have enough memory. Or, at the gloomy end, you might have a faulty hard disk.
./heLen
>Hi,It means that the Firebird engine has encountered a run-time problem that it either doesn't know how to handle or it can't handle because it doesn't have enough resources. Have you looked in the Firebird log in case there is more information there? If you see any system I/O or network error there around the time the engine fell over, then you are at least on the way to finding the cause.
>
>I'm trying to backup my 3GB firebird database and I get this error when
>my biggest table is backing up (10 milion records):
>
>Error Message:
>----------------------------------------
>Unsuccessful execution caused by a system error that precludes
>successful execution of subsequent statements.
>internal gds software consistency check (can't continue after bugcheck).
>
>Can someone explain me what this error mean!
>This is tableq, I have tablea, tableb, tables & tableq, tableq isFor a backup, the structure of the tables shouldn't matter, since it merely reads the data and writes it out to the output file in a particular compressed format. It doesn't do any consistency checking or validation on the actual data. It doesn't check dependencies. It doesn't back up indexes. It doesn't decompile PSQL modules.
>connect all of 3 tables and contain two numeric fields more!
The engine does need to have access to both the database file and the output file for the duration of the backup. It appears to have been the case when the backup began since, by the time it is ready to back up table data, it has already backed up the database header and the metadata. However, if it runs out of disk space before the backup completes, of course the backup will fail. If that happened, the message sent by the operating system might have made it to the firebird.log.
Another cause could be if you have some other application on the system that starts up after the backup began, that locks part of the hard disk that the backup file is using, or needs to use. For example, check whether some scheduled disk maintenance procedure started up, such as a filesystem backup program, or a disk scan, or a defrag, that arbitrarily locks blocks or partitions. If your database or backup file are on Windows, some native Windows file and disk maintenance tools don't respect any exclusive locks.
If you are writing the backup file to a remote location, of course it could be that the backup routine can no longer find the backup file...again, there's a chance that the engine was able to write a firebird.log message before it shut down.
Or it could just be that you don't have enough memory. Or, at the gloomy end, you might have a faulty hard disk.
./heLen