Re: [h2] Re: H2 DB Corruption: java.lang.IllegalStateException: Chunk 1936 not found [1.4.200/9]

2021-02-22 Thread Andreas Reichel
Silvio,

we are in a very similar situation. Banking software, financial
accounting, not really the place where you want to experiment a lot.
Our large customers all run Oracle (which deserves its own place in
hell) but for smaller banks less than 100k accounts H2 can provide a
nice alternative.
I am actually happy to hear from you because sometimes it looks like
not many other people/companies run H2 in a similar scenario.
We also have to put a lot of effort in versioning and upgrading our own
VBox software accross various customers and so are aware of the burden,
which any kind of versioning, backward compatibility and migration
actually is.

So with all understanding for the developpers and the scarce resources,
from an end-user's point of view the current versioning schema is not
optimal and we were close to abandon H2 once simply because the
maintenance and upgrading procedure became too cumbersome.

Eventually we have decided for ourselves, that there is no actual
reliable version schema: We have experienced the current 2.0.201+
development branch as much more robust and stable and correct than
1.4.200 and also there were many "breaking changes" in between (e. g.
new reserved keywords, NEXTVAL vs. NEXT VALUE FOR etc.) that for us it
works better to be as close as possible to the upstream development. We
see H2 now as an very agile, rolling realise software.

I believe, the H2 developpers doe a fantastic job regarding the
software itself but seem to lack experience or interest in practically
running/using H2 in a corporate environment as a replacement for
Postgres or Oracle. Maybe this is just out of scope.
 
My advise: If you stick with 1.4.200 longer, you will likely face a big
migration effort in your own software/Schema Definition when switching
to 2.0.201 eventually.
Consider using 2.0.201 and establish a weekly procedure of exporting to
SQL script and re-importing into the next version, followed by a large
batch processing test including reports. This works for us at least and
has reduce the headache.

Best regards
Andreas



On Mon, 2021-02-22 at 16:24 -0800, Silvio wrote:
> We use H2 in production heavily and would love to upgrade but as long
> as there is no actual version released we can only use 2.0.x for
> testing purposes. If only we could get some ball park estimate about
> when 2.0.201 will be released with some highlights of improvements we
> can expect and preferably some information about compatibility (or
> lack thereof) with 1.4.200 that would be great. We are planning the
> roll-out of a major new version of our software which will involve
> major customer data migrations. If a production release of 2.0.201 is
> imminent we could adjust our release schedule to include the upgrade.
> If it will take another 6-12 months we cannot. But as it is we can
> only guess which, to be honest, really sucks.
> 
> On Monday, 22 February 2021 at 06:37:13 UTC+1 and...@manticore-
> projects.com wrote:
> > Good Morning.
> > 
> > On Sun, 2021-02-21 at 21:32 -0800, ciphe...@gmail.com wrote:
> > > rying a development version of H2 from Github?
> > 
> > 
> > 
> > While I am not a H2 Developper and can only speak for my own
> > experience:
> > 
> > Running several large H2 databases we have had similar corruption
> > issues with 1.4.200+ and never again since we switched to 2.0.201+
> > (until Feb/March 2020).
> > In my opinion, the current 2.0.201+ snapshot is the most robust and
> > correct H2 database and I prefer this "unstable" develepmoent
> > snapshot over the actually released versions.
> > 
> > Best regards
> > Andreas 
> -- 
> 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 h2-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/h2-database/00a5d74e-6a53-4ebd-a9a5-0b9af8fecfc3n%40googlegroups.com
> .

-- 
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 h2-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/b2f7cd83d284abaffc87378afbc02666111dfd41.camel%40manticore-projects.com.


Re: [h2] Re: H2 DB Corruption: java.lang.IllegalStateException: Chunk 1936 not found [1.4.200/9]

2021-02-22 Thread Silvio
We use H2 in production heavily and would love to upgrade but as long as 
there is no actual version released we can only use 2.0.x for testing 
purposes. If only we could get some ball park estimate about when 2.0.201 
will be released with some highlights of improvements we can expect and 
preferably some information about compatibility (or lack thereof) with 
1.4.200 that would be great. We are planning the roll-out of a major new 
version of our software which will involve major customer data migrations. 
If a production release of 2.0.201 is imminent we could adjust our release 
schedule to include the upgrade. If it will take another 6-12 months we 
cannot. But as it is we can only guess which, to be honest, really sucks.

On Monday, 22 February 2021 at 06:37:13 UTC+1 and...@manticore-projects.com 
wrote:

> Good Morning.
>
> On Sun, 2021-02-21 at 21:32 -0800, ciphe...@gmail.com wrote:
>
> rying a development version of H2 from Github?
>
>
>
> While I am not a H2 Developper and can only speak for my own experience:
>
> Running several large H2 databases we have had similar corruption issues 
> with 1.4.200+ and never again since we switched to 2.0.201+ (until 
> Feb/March 2020).
> In my opinion, the current 2.0.201+ snapshot is the most robust and 
> correct H2 database and I prefer this "unstable" develepmoent snapshot over 
> the actually released versions.
>
> Best regards
> Andreas 
>

-- 
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 h2-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/00a5d74e-6a53-4ebd-a9a5-0b9af8fecfc3n%40googlegroups.com.