Subject | Re: [firebird-support] Re: database became broken for any reasons |
---|---|
Author | Thomas Beckmann |
Post date | 2014-05-15T08:17:29Z |
Well, Dimitri,
I don't know whether it's ok for the people at the other end of the
killed connection, because their operation is cancled and rolled back,
but at least, you don't get database corruptions, if you close all
connections and shut down database regularly...
Best regards, Thomas
Am 15.05.2014 10:07, schrieb markovdmitri@... [firebird-support]:
I don't know whether it's ok for the people at the other end of the
killed connection, because their operation is cancled and rolled back,
but at least, you don't get database corruptions, if you close all
connections and shut down database regularly...
Best regards, Thomas
Am 15.05.2014 10:07, schrieb markovdmitri@... [firebird-support]:
>
>
> So if I kill all connections(clear table MON$ATTACHMENT) and then I'll
> try to kill processes all will be ok(or myabe I don't need it)?
>
>
> I'll try to do such example:
> 1) I connect from remote computer to test server using SYSDBA, not my user
> 2) I start big select (it's take about 2-3 minutes, really big table)
> 3) On test server send database to shutdown - It's work, database in
> shutdown mode, and then return online
>
> What's wrong?
>
> I't seems to me that this connections kept by sleeping applications in
> terminal. I never see this bug on server without terminal(I may mistake,
> but it seems to me I right)
>