Subject | Arithmetic exception, numeric overflow, or string truncation |
---|---|
Author | Dion Oliphant |
Post date | 2002-10-17T09:35:49Z |
Hi,
When I backup my database, I get no errors. When I restore, I get the
following error:-
1. Arithmetic exception, numeric overflow, or string truncation.
I tried the advice suggested path as laid out in the docs on the Firebird
site ie:-
1. Define the following two variables, it makes life easier, in that you do
not have to type in the user name and password every time you issue a
command.
SET ISC_USER=SYSDBA
SET ISC_PASSWORD=masterkey
2. Always make sure you work on a copy of the database, not the production
database. Use the operating system to make a copy of the database. You must
have exclusive access to the database to do this.
copy employee.gdb database.gdb
3. Now check for database corruption. You must have exclusive access to do
this, but since you're working on a copy of the original database, this is
not a problem.
gfix -v -full database.gdb
etc...
but find no errors(at least not on the screen). I pick up the above error
when trying to restore the backed up database.
Thanks,
Dion.
When I backup my database, I get no errors. When I restore, I get the
following error:-
1. Arithmetic exception, numeric overflow, or string truncation.
I tried the advice suggested path as laid out in the docs on the Firebird
site ie:-
1. Define the following two variables, it makes life easier, in that you do
not have to type in the user name and password every time you issue a
command.
SET ISC_USER=SYSDBA
SET ISC_PASSWORD=masterkey
2. Always make sure you work on a copy of the database, not the production
database. Use the operating system to make a copy of the database. You must
have exclusive access to the database to do this.
copy employee.gdb database.gdb
3. Now check for database corruption. You must have exclusive access to do
this, but since you're working on a copy of the original database, this is
not a problem.
gfix -v -full database.gdb
etc...
but find no errors(at least not on the screen). I pick up the above error
when trying to restore the backed up database.
Thanks,
Dion.