Subject | Re: [ib-support] Re: force disconnect users |
---|---|
Author | Helen Borrie |
Post date | 2002-07-24T05:29:42Z |
At 04:38 AM 24-07-02 +0000, Andrew Ferguson wrote:
chance that you are not the only (human) user who has owner or sysdba
rights. If, for example (and I seem to recall it was the case with Fred's
deployment), many or all users log in as sysdba or owner, then there is no
way to know or guarantee that one of those "other sysdbas" who were already
logged in when you did the forced shutdown are locked out. They can just
keep on chugging away - database integrity be damned.
heLen
All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
_______________________________________________________
>If you are determined to shutdown the db and deny access then simply:You can only be confident that you have exclusive access if there is no
>
>gfix -shut -force n (n being time to wait til forced shutdown)
>see also gfix -shut -tran n, gfix -shut -attach n
>
>Do your gbak, or whatever, confident that there are no connections
>(nobody but owner and sysdba can access the db) then bring it back up
>with:
>
>gfix -online
chance that you are not the only (human) user who has owner or sysdba
rights. If, for example (and I seem to recall it was the case with Fred's
deployment), many or all users log in as sysdba or owner, then there is no
way to know or guarantee that one of those "other sysdbas" who were already
logged in when you did the forced shutdown are locked out. They can just
keep on chugging away - database integrity be damned.
heLen
All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
_______________________________________________________