""Wilson, Fred"" <fred.wilson@...> wrote in message
news:E9E4431A916AD21191FD00104B986AEFC23868@......

> Ann, I'll have the tech at the site run validation and see what it

produces.

> Just a thought, could something like this occur if a user (through an
> application) connects to a database which is being restored (after it was
> dropped), and while the restore is in progess, and tries to "work" ??

(While Ann thinks...)
I don't think this is possible. Gbak creates the restore db in a shutdown
state and without forced writes. It does all the data restore, then before
detaching from the newly created db, it sets the db to multi-user mode again
and sets forced writes. If you try to connect in the meantime, you will get:

Statement failed, SQLCODE = -902
database H:\IBDEV\FBBUILD\INTERBASE\IB_DEBUG\BIN\NEW.GDB shutdown

Of course, if sysdba tries to connect, it will succeed. Maybe even sysdba
should be forbidden if the previous (and hopefully only) attachment is being
held by gbak, since it doesn't make sense to interfere at this time.
Whatever happens, once gbak exists for good or bad reason, sysdba would be
able to connect anyway, so why allowing it to log in a db being restored?

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing