Subject | Re: Shut Down Database |
---|---|
Author | s3057043 |
Post date | 2006-03-22T23:35:39Z |
--- In firebird-support@yahoogroups.com, "robertgilland"
<robert_gilland@...> wrote:
thread to finalise its work. Just because the shutdown returns
doesn't mean that the work in the database has finished. It just
means that users can't connect and all existing users have logged out.
There are three modes for shutdown. One prevents new attachments, one
prevents new transactions, and one that forces the shutdown. The
first two only shutdown the database if all users disconnect. The
last one shuts it down no matter what.
SYSDBA / OWNER will NEVER be kicked off. If you connect your users as
SYSDBA, that's your problem. Change your application to use a
different user(s).
Adam
<robert_gilland@...> wrote:
>give it
> >
> > It does not kick off the SYSDBA or OWNER users, so if you are
> > connected as them then this will not work. The garbage collection
> > thread may still be active for a few seconds, how long do you
> > before attempting to rename the file?Well you may want to try waiting 5 seconds for the garbage collection
> >
> > Adam
> >
>
> I don't wait for any time, to rename the file.
thread to finalise its work. Just because the shutdown returns
doesn't mean that the work in the database has finished. It just
means that users can't connect and all existing users have logged out.
> How would I know that no one is attached to the database?Read the documentation in OPGuide and Chapter 39 of The Firebird Book.
> Shut down doesn't seem to actually kick everyone off.
> How can I make sure everyone is kicked off?
There are three modes for shutdown. One prevents new attachments, one
prevents new transactions, and one that forces the shutdown. The
first two only shutdown the database if all users disconnect. The
last one shuts it down no matter what.
SYSDBA / OWNER will NEVER be kicked off. If you connect your users as
SYSDBA, that's your problem. Change your application to use a
different user(s).
Adam