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

> The "owner of the database" is the user that I tried connecting with, and

is

> the one that the user applications would connect with. We (currently) use
> the same user (NOT sysdba) for all the applications in the field and also
> the scripts that handle the backup and restore. So, to re-cap. I can, drop
> the database, start a restore (using a user other than sysdba) and then,
> from another client, log into the database while the restore is running

with

> the user name that's doing the restore (not sysdba).

This is as designed. Both sysdba and the owner can connect to a single user
mode database. Gbak itself needs that trick, because before setting the db
multi-user when doing the restore, it logs on again (second, concurrent
attachment) to set flags like forced writes and read only and finally it
resets the single user mode flag itself in the same way.

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