Esent database question

[Tobi]

Hi!

I've got a somehow defect RavenDB database today (RavenDB 2.5 / 2672).
When opening this database with the current 2.5 stable a bunch of
edbres*.jrs, edb*.log, edb.log and edb.chk files gets created in the
application root folder (Embedded RavenDB!).

What exactly is happening here? Is Esent somehow trying to repair
itself? Has this something to do with different architectures / OS?

I can still access the data and it seems to be complete, I'm just
wondering what has happened and what these files mean.

In the log I see:

Secondary Index Corrupted detected, attempting to compact...
JET_SESID(0xd1f07a0), Compact, Begin,
JET_SESID(0xd1f07a0), Compact, Progress, JET_SNPROG(20/19184)
...
JET_SESID(0xd1f07a0), Compact, Complete,
Updating schema from version 4.7:
OK
...
Performing Transactions Cleanup Sequence for db <system>

Can I assume that RavenDB/Esent safely recovered from whatever went wrong?


Tobias

[Michael Yarichuk]

Did you move the database between machines?

It may be related to OS version - basically, Esent doesn't support moving between different versions of Windows as it uses version specific Win32 API

"Secondary Index Corrupted detected, attempting to compact" -> this (Esent related) error message can appear when Windows version is changed. It fires of db compaction - and one of things compaction does is rebuilding indices.

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Best regards,

 

Michael Yarichuk

RavenDB Core Team

Tel: 972-4-6227811

Fax:972-153-4-6227811

Email : michael....@hibernatingrhinos.com

 

RavenDB paving the way to "Data Made Simple" http://ravendb.net/  

[Tobi]

I moved the database from the customer machine (Windows Embedded Standard
32bit) to my machine (Windows 10 64bit). It seems these messages only
appear on my side. so somehow Esent seems to migrate the database. And it
seems to do this successfully. I thought this was not possible. Older
RavenDB versions simply failed when trying to load a database which was
created on a different OS or architecture. Good to know, that this is not
the case anymore.

On the customer machine only the RavenDB indexes were damaged (after a
power loss) without RavenDb noticing (2.5.2672).

Tobias

> <mailto:ravendb%2Bunsu...@googlegroups.com>.

> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Best regards,
>

> *__ __*
>
> *Michael Yarichuk____*
>
> RavenDB Core Team
>
> Tel: 972-4-6227811____
>
> Fax:972-153-4-6227811____
>
> Email : michael....@hibernatingrhinos.com
> <mailto:michael....@hibernatingrhinos.com>__
>
>
>
> */Raven/**/DB/*/paving the way to "Data MadeSimple" http://ravendb.net/ /

>
> --
> You received this message because you are subscribed to the Google Groups
> "RavenDB - 2nd generation document database" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ravendb+u...@googlegroups.com

> <mailto:ravendb+u...@googlegroups.com>.

[Chris Marisic]

ESENT should always allow forward migration of an ESENT database. ESENT will not allow a downward migration, sometimes you can force it to downgrade a database using (potentially) data destructive eseutl commands. 

>     <mailto:ravendb%2B...@googlegroups.com>.