Question regarding IB 5.6 gbak issue
villad...@gmail.com
I have been running into two separate problems regarding my automated
backup and restore that happens each night. I've searched high and low
looking for answers but I haven't really seen anything that comes
close.
The first, and less worrysome issue is that occasionally I will see the
following message:
gbak: readied database /db/blah blah.gdb for backup
gbak: creating file stdout
gbak: starting transaction
gbak: ERROR: database /usr/interbase/databases/blah blah.gdb shutdown
gbak: Exiting before completion due to errors
I do in fact do a gfix -shut -force 0 before any backup/restore attempt
commences, and this problem only happens sporadically. If it were a
constant issue I just wouldn't shut the database down, but since it
happens without (seemingly) any rhyme or reason, and I like being able
to kill all connections to the DB, I was wondering if there's some
condition I can look for or something I can do differently in regards
to this
The second, and more worrysome problem is this message:
gbak: writing exception INVALID_SALESPERSON
gbak: writing exception INVALID_AGENT_DATES
gbak: writing Character Sets
gbak: writing Collations
gbak: writing index RDB$PRIMARY216
gbak: writing index RDB$FOREIGN217
gbak: ERROR: cannot sort on a field that does not exist
gbak: ERROR: gds_$compile_request failed
gbak: Exiting before completion due to errors
gbak: ERROR: internal gds software consistency check (page in use
during flush (210))
Again, this only happens on occasion, and when I go in and do the
backup by hand (gbak -b -v -t), I have no problems at all. The
automated backup uses gbak -b -v -t -y, just as an aside.
These are both IB 5.6 installs on Dell PowerEdge boxes running CentOS
4.1. I've spent the past week digging but haven't found much. Any help
is greatly appreciated.
- Matt