By: Craig Stuntz
Abstract: InterBase is, in general, a very stable database server and corruption is rare. When corruption does occur, then, it is important to determine the cause of the corruption. This article describes circumstances that can cause corruption.
by Craig Stuntz
InterBase is, in general, a very stable database server and corruption is rare. When corruption does occur, then, it is important to determine the cause of the corruption, because it indicates that something is wrong with the installation and it is important to fix it. Database corruption should not be a routine occurance, even if a customer neglects to maintain the DB.
It is a good idea to run Database Validation or command-line gfix from time to time so that if corruption does occur it can be caught early, before the damage to database is too severe to repair.
As an aid to diagnosing source of the problem, the table below lists known causes of InterBase database corruption, along with suggestions for how to avoid each type of corruption in the future. To repair a corrupt database, use command-line gfix with the -mend switch, or Database Validation in IBConsole. If that fails, restore from a recent backup or post a question to the borland.public.interbase.general
Thanks to Alexey
Kovyazin, Bjørge Sæther, Thomas Steinmaurer, and Quinn Wildman for feedback
on this article.
Copyright © 2002 by Craig Stuntz. All rights reserved.
Trial Download Week!
Click here to download a free 30-day trial of InterBase XE3 Server or ToGo editions. Or download a free non-expiring Developer Edition >
More InterBase Info
InterBase XE3 Product Info
Free Developer Edition download
InterBase on Google+
Follow @InterBase on Twitter
Server Response from: ETNASC02