Internal Website Search
51-73 of 73 resultsObjectDB size not reducing corrupt I will run it like I'm repairing the DB and generate the new file, then replace the current DB | |
Using the wrong class to access a database. - the first app cannot add points anymore; it now reports zero entries - db is corrupted If it is an error | |
doctor error message after database getting page errors Here is a link for the corrupt database: https://www.dropbox.com/scl/fi/6ywgr9yx459c9tskv525t | |
Failed to resize file - file system limitation error". So it does seem as a specific system issue rather than a bug in ObjectDB or a corrupted database file | |
objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation Clean and Build has not been corrupted . - No javaagent enhancement is used at any stage | |
ODB lost? I'm new to ObjectDB. While debugging small programs in single-step mode in NetBeans, the ODB appears to get corrupted or lost if I don't invoke close on EntityManager. If I re-run my program and get a new EntityManager, the instance behaves as if the data that was persisting is somehow gone. I | |
Unexpected exception (Error 990) of this specific database file. You can find a list of possible reasons for database corruption on the link | |
NegativeArraySizeException on commiting a transaction itself was not corrupted though, because when I tried to make a copy of it (I made it transient | |
@JoinColumn(nullable=false) During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the following: I marked a @Column as nullable=false Than I tried to save it with the property as null It worked, without any problem, now I have a corrupt dataset. I expected an exception or | |
Unexpected exception (Error 990) on find. The new version fixes a critical bug that in some cases (rare but possible) may cause database corruption . support Support | |
ArrayIndexOutOfBoundsException: -1. Therefore it could corrupt the database, as demonstrated by your test. Consequently many types | |
java.lang.NullPointerException during access a field, only if the classes enhanced bug that in some cases (rare but possible) may cause database corruption , so it is highly recommended to use the new build. support Support | |
Explorer bug ? Objects seem to be missing from database in Class view, but are present as references objectdb-2.2.5_08 NetbeansID6.9.1+Glassfish3.01 I suspect the following is an Explorer bug. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project because it appears to be either database integrity corruption , or it just looks like | |
Server out of memory exceptions; the exception came after running for 10mins. Is it possible something could be corrupted | |
log entry and massive performance issues it possible that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In | |
ObjectDB 2.7.1 Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue | |
EOFException The database file that you uploaded is corrupted and you must repair it using the ObjectDB Doctor before | |
NullPointerException in ENH.g(ENH.java:401) Hello, corresponding to your suggestion I created a private ticket in reply to http://www.objectdb.com/database/forum/1109. Attached you will find my database file (I removed most of the content but one corrupt instance is still included). I error happens when reading the field "Event | |
ObjectDB 2.3.7 Fixed a critical issue that may cause database corruption ( issue #630 ). Initial attempt to enable navigation through lazy loading from detached objects ( feature request #326 ). Improved toString of criteria queries to use aliases ( issue #12 7). Fixed automatic variable naming in criteria | |
[ObjectDB 2.6.9] Unexpected exception (Error 990) that in some cases (rare but possible) may cause database corruption , so it is highly recommended to use the new build. support Support | |
stress test -> com.objectdb.o.InternalException: null. It seems that all entity managers become corrupted / broken. (see stack trace below) Should it be something in | |
InternalException - error reading field from "queue" database is corrupted but the cause is unknown. I am closing this issue now. If the problem repeats please open it and provide additional information. support Support | |
com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null: This was a critical bug that could corrupt databases when the total number of entity classes, indexes |