Hi, Dmitry, Thanks for you response. No one has changed this table. At most, as a not null column, someone could have change it to another value, but not to null. And no one changed it´s validation rule (as not null). This is discarded. We repeated the action = we take the DB, checked the content of this colum (all lines having 0 at this column), then we run a backup and imediatelly a restore, and we reproduced the problem (it ocurred when restoring). Roberto Camargo.
________________________________ From: Dmitry Kuzmenko <k...@ibase.ru> To: firebird-support@yahoogroups.com Sent: Tuesday, June 25, 2013 4:33 PM Subject: Re: [firebird-support] GBak Backup & Restore Problem Hello, Tupy...! Tuesday, June 25, 2013, 11:23:47 PM, you wrote: Tn> Dear Friends, Tn> We have a table with 60 rows where a not null type SmallInt column has 0 (zero) as content. Tn> When restoring, GBak returns null for this column. As this column Tn> is not null, we get an error message (Error: Validation error for column .....). Tn> Between these two steps (backup and restore), no further action is done with the backup file. Tn> I ask you = What can cause this problem? Is there any solution Tn> for this? Any idea about this problem? 1. somebody altered column to not null default 0 while column had null data 2. somebody added column not null default 0. solution - update that column to 0 like this update table set field = 0 p.s. gbak backups data, it does not check correspondence of data and constraints. If it is broken (somehow, by db corruption or by actions I mentioned), restore will show that column data does not correspond to it's check. -- Dmitry Kuzmenko, www.ib-aid.com ------------------------------------ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Visit http://www.firebirdsql.org/and click the Resources item on the main (top) menu. Try Knowledgebase and FAQ links ! Also search the knowledgebases at http://www.ibphoenix.com/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Yahoo! Groups Links [Non-text portions of this message have been removed]