Hi Itai,
On the specific error there is no data corruption on disc, there was an
issue on the binary query managment that has been fixed since 2.2.15, I'll
suggest anyway to upgrade to 2.2.17 ase well, after the upgrate you should
not receive any of this errors anymore.
Bye
On Tuesday, 21 February 2017 12:36:04 UTC, Itai Caspi wrote:
>
>
> Hi,
>
> We are using OrientDB 2.2.13. It seems one of our graph Vertex records is
> corrupted. We cannot delete it from the web or the console. Whenever we try
> to delete it using DELETE or DELETE VERTEX we get the above BigInteger
> exception.
>
> We know the record is corrupted because we cannot modify it by adding any
> property or updating it. We get the same exception when we try to do so.
>
> This issue does not allow us to add a property and therefore to create a
> needed index on our class.
>
> Can we preform some fix operation on the Database. How can this be
> corrected?
>
> Thanks, Itai
>
> 2017-02-21 11:03:49:552 SEVER Internal server error:
>
> java.lang.NumberFormatException: Zero length BigInteger
> [ONetworkProtocolHttpDb]
>
> 2017-02-21 11:05:14:849 WARNI {db=sixgill_data} Error deserializing record
> with id #11:1010924 send this data for debugging:
> AAhVc2VyEm91dF9Xcm90ZQAAACoWKwAAAEcpAAAATAEAAABbPQAAAGUAADl+qN0AAAAxAAAAAAAAUg0AAGAAAAAAKAAAAAAIdXNlchxwYXN0ZV9wYXN0ZWJpbhJSRVNUUklUT24KAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
>
> [ORecordSerializerBinary]
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
