The new releases fixes the cause of the problem.  If you already have
it, it doesn't magically disappear.

It BBPcheckbats complains about a too short *.tail1 file, you can create
one, or extend the exising one, with bytes with the value 8 (binary
value, not the ASCII digit) until the file is large enough.  Then you
can start the database.  Note, there is loss of data.

The BBP.dir file contains the meta-data for the database, i.e. which
BATs there are, what their types are, and how large they are.  Do not
mess with it.

On 23/08/2022 13.41, imad hajj chahine wrote:
> Hi,
>
> I am using version Jan2022-SP2, and after a server restart I had the
> BBPcheckbats error.
> I upgraded to the latest version Jan2022-SP4 as it has the fix for this
> reported bug, and I am still unable to start the database.
>
> After manually editing the BBP.dir file and removing the entries on
> which the database failed to load with messages similar to (BBPcheckbats
>          file /bat/01/67/16774.tail1 too small (expected 143640, actual
> 0), I managed to make the database start and connect to it and query the
> tables successfully.
>
> Is this the right way to recover from this? what I am risking losing by
> deleting these entries, should I have corrupted tables that are affected
> by these entries?
>
> What is exactly the role of BBP.dir? any documentation describing the
> use of this file.
>
> Appreciate your help.
> Thank you.
>
>
> _______________________________________________
> users-list mailing list -- users-list@monetdb.org
> To unsubscribe send an email to users-list-leave@monetdb.org

--
Sjoerd Mullender
_______________________________________________
users-list mailing list -- users-list@monetdb.org
To unsubscribe send an email to users-list-leave@monetdb.org