Andrei-
Thank you for the quick response. Can you elaborate on the thought process
about why going from 1 to 2 would throw the same error?
Prior to 1.4.200 we used a progression of EXCLUSIVE settings:
a. Don't allow new connections (ie allow connections to natural quiesce)
SET EXCLUSIVE 1
b. After a period of time .. drop all connections (ie.. any remaining
connections are not going to quiesce, so let's disconnect all)
SET EXCLUSIVE 2
c. Do administrative tasks..
d. Allow connections to resume..
SET EXCLUSIVE 0
Thanks,
Matt
On Wednesday, October 16, 2019 at 2:31:16 PM UTC-5, Andrei Tokar wrote:
>
> I know, I've read and run it, but my point is - it's not the connection
> that set exclusive mode, because there is none, exclusive mode is not set
> at all.
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/h2-database/0e265c78-f995-4557-86be-3377ac9d0501%40googlegroups.com.
