There is a DB_CLOSE_ON_EXIT setting. It in enabled by default, but it can
be disabled.
SHUTDOWN command may be executed with other alive connections, they will be
closed too, but it's possible that an application will reopen the database
after execution of this command, you need to prevent it
Thank you for the response Evgenij,
On Thursday, 25 April 2019 15:46:30 UTC+2, Evgenij Ryazanov wrote:
>
> Hello. No, you can't copy a database file if database was not closed
> properly, but you can use a SHUTDOWN command to close it.
>
Ok, so that means that closing all connections is not
Make sure that your client and server jars use the same version.
Difference in those versions caused for me corruptions before.
At least all of the clients that update data should have the same
version, I think.
- Rami
On 25.4.2019 16.28, Silvio wrote:
Hello all,
Since our upgrade to
Hello. No, you can't copy a database file if database was not closed
properly, but you can use a SHUTDOWN command to close it.
However, if you need a backup copy it can be created with BACKUP TO
'filename.zip' command, there is no reason to close other connections for
it.
Usually it's safe to
Hello all,
Since our upgrade to h2-1.4.199 we are experiencing frequent database
corruptions. I reported this earlier and have seen at least one similar
report from someone else in this group showing an almost identical error.
There has been no response since.
Is there any reason to assume
