Issue #2047: [ObjectDB 2.6.9] Unexpected exception (Error 990)

[2017-03-29 14:04:44 #1 client]
[ObjectDB 2.6.9] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_121 (on Windows 8.1 6.3).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: null
com.objectdb.o.InternalException
at com.objectdb.o.BYR.o(BYR.java:113)
at com.objectdb.o.BYR.w(BYR.java:206)
at com.objectdb.o.VUT.j(VUT.java:350)
at com.objectdb.o.RST.C(RST.java:194)
at com.objectdb.o.RTT.l(RTT.java:134)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.RTT.D(RTT.java:179)
at com.objectdb.o.RST.s(RST.java:121)
at com.objectdb.o.PGT.q(PGT.java:109)
at com.objectdb.o.RST.B(RST.java:93)
at com.objectdb.o.RTT.l(RTT.java:132)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.RTT.D(RTT.java:179)
at com.objectdb.o.RST.s(RST.java:121)
at com.objectdb.o.PGT.q(PGT.java:109)
at com.objectdb.o.RST.B(RST.java:93)
at com.objectdb.o.RTT.l(RTT.java:132)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.TSK.i(TSK.java:145)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.TSM.e(TSM.java:86)
at com.objectdb.o.RTT.D(RTT.java:177)
at com.objectdb.o.RST.s(RST.java:121)
at com.objectdb.o.PGT.q(PGT.java:109)
at com.objectdb.o.RST.B(RST.java:93)
at com.objectdb.o.RTT.l(RTT.java:132)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.TSK.i(TSK.java:145)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.TSM.e(TSM.java:86)
at com.objectdb.o.RTT.D(RTT.java:177)
at com.objectdb.o.RST.s(RST.java:121)
at com.objectdb.o.PGT.q(PGT.java:109)
at com.objectdb.o.RST.B(RST.java:93)
at com.objectdb.o.RTT.l(RTT.java:132)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.TSK.i(TSK.java:145)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.TSM.e(TSM.java:86)
at com.objectdb.o.RTT.D(RTT.java:177)
at com.objectdb.o.RST.s(RST.java:121)
at com.objectdb.o.PGT.q(PGT.java:109)
at com.objectdb.o.RST.B(RST.java:93)
at com.objectdb.o.RTT.l(RTT.java:132)
at com.objectdb.o.RST.l(RST.java:24)
at com.objectdb.o.TSK.i(TSK.java:145)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.MST.aW(MST.java:586)
at com.objectdb.o.MST.U9(MST.java:544)
at com.objectdb.o.WRA.U9(WRA.java:279)
at com.objectdb.o.STC.p(STC.java:409)
at com.objectdb.o.SHN.ah(SHN.java:460)
at com.objectdb.o.SHN.K(SHN.java:149)
at com.objectdb.o.HND.run(HND.java:133)
at java.lang.Thread.run(Unknown Source)

Thank you for this report.

Could you please check the database file with the ObjectDB Doctor?

Can you provide a test case that demonstrates the exception on a new / healthy database (i.e. an empty database or a database that has no errors in the Doctor check).

In DEV after the Doctor and using the new file, I have no problem (i can't reproduce error in DEV).
I think the problem occurs when data is loaded and queried at the same time.

In production I still have the same problem.. version 2.5.6_05  - size of data 100GB
I am running a Doctor in prod (in a backup file, It takes long time...), .

PRODUCTION
[2017-03-30 07:04:53 #37 server]
[ObjectDB 2.5.6_05] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_25 (on Windows 2003 5.2).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: null
com.objectdb.o.InternalException
at com.objectdb.o.BYR.o(BYR.java:113)
at com.objectdb.o.BYR.w(BYR.java:206)
at com.objectdb.o.VUT.j(VUT.java:350)...

ObjectDB Doctor [version 2.6.9] - DEV
Copyright (c) 2016, ObjectDB Software. All rights reserved.

Scanning the database file...
.................................................. 100MB
.................................................. 200MB
.................................................. 300MB
.................................................. 400MB
.................................................. 500MB
......................... 551MB (total)

Analyzing database structure...
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

-------------------------
No errors have been found
-------------------------

Creating a database copy...
..............................................  922589 entity objects (total) ha
ve been migrated.

New database copy is ready at: backup\201703291624\pcsodbcsv_new.odb

Doctor found problems in production.

We will take the doctor output file for production.

Thanks.

Analyzing database structure...
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Global Value Errors
-------------------
[1] Unexpected total object count: 189979358 (expected 189979356)

BTree Value Errors
------------------
[1] cl.intelidata.jpaodb.Movil
  - Unexpected object count: 142351618 (actual 142351616)

Page Relation Errors
--------------------
[1] Page #36099460 unexpected exception: null
[2] Page #36099460 last key is null, parent page #43650945 next key is ('3.203.10.00.100000','95798112',2421822
8)
[3] Page #36230484 unexpected exception: null
[4] Page #36230484 last key is null, parent page #22427553 next key is ('1.10843870','99984690',24327807)

Page Content Errors
-------------------
[1] Unexpected exception in page #36099460 entry #4: null
[2] Unexpected exception in page #36230484 entry #5: null

Index Errors
------------
[1] Index cl.intelidata.jpaodb.Movil[id] requires rebuild.
  - has 142351616 entries instead of 142351618

Try to run the Doctor to fix the production database.

Do you still get the exception in production after fixing the database?

In production it takes about 18 hours, and finish ok!

This report is similar to the report in issue #1977  that was fixed now in version 2.7.1.

The new version fixes a critical bug that in some cases (rare but possible) may cause database corruption, so it is highly recommended to use the new build.