ObjectDB Database Search
1-50 of 200 resultsInstalling a VM security fix leads to inactive DB
stability issues have been fixed in version 2.9.3 and there are no new known issues. If you create ... procedure that depends on the MAC address of the device. This used to be fixed in the past  ... the newest version. I fixed it in the other ticket. Kevin Kevin Pfaff No problem. Please see the reply in your private support ticket. support Support
|
|
unable to fix DB with Doctor (ArrayIndexOutOfBoundsException)
). DB was used by ver 2.6.9_09. I tried to fix it with ObjectDB Doctor (from ver. ver 2.6.9_09 ... 2.6.9_09] null How can I fix my DB? Andrzej Andrzej Domaradzki Build 2.8.6_04 includes
|
|
Deleting a broken reference that was fixed to null in the Explorer
Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support
|
|
ObjectDB version 2.3 has been released
ObjectDB 2.3 has been released and it includes important additions and fixes : Added the ability ... #453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. Fixed several NullPointerException bugs. Fixed the "Failed
|
|
after upgrade to 2.9.0 database destroys, urgent issue at our most important customer, production shutdown
before or after an attempt to fix it? Unfortunately it is possible that the database is corrupted in ... the fixed one, we can try fixing it, if the data is there. Note that there were no changes in ... our embedded system hgzpincher Hans-Georg Zwicker As it seems that the Doctor fixes the database
|
|
Modifying something with Explorer -> app JPQL with Enum doesn't work anymore
. That's all. I would really appreciate a fix for this, because it's holding back my team. Thanks ... is a feature that was added / fixed recently, and possibly has side effects, so you may want to avoid it. Unfortunately we cannot provide same day fixes for issues that are not demonstrated
|
|
Out of memory
build 2.4.3_03 that fixes the "D:\temp\odb-synthetic" directory creation, and disables the new memory ... Walkowski The cause of the errors at #10 is still unclear so the fix of #9 cannot be integrated ... of the Doctor that is now fixed in build 2.4.3_07. Please see #9 - #14 above - that essential fix
|
|
Removing an entity throws exception
you Michael anaq x It seems as an internal ObjectDB bug. Please try build 2.2.6_03 that may fix ... that demonstrates it. support Support Thank you for fast response. The fix changed the number 51 to 34 ... . Therefore, starting with a new database file could solve the problem even with no fix , since the schema
|
|
ObjectDB version 2.2 has been released
ObjectDB 2.2 has been released and it includes important additions and fixes : Added full support ... after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution
|
|
ClassCastException on SELECT NEW ... after UPDATE over Java RMI
... all work fine. DB Doctor does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil prolancer ... RecordingMetaData r For object #1 the id is Integer rather than Long in the second database. You can fix
|
|
[ODB1] Chapter 6 - Persistent Objects
yet. Such an object ID is fixed on commit() . For example: pm.currentTransaction().begin(); Person ... can be fixed to delete these objects before they become unreachable. JDO portable applications should not use
|
|
ObjectDB 2.0.0
and method finding problems. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in ObjectDB Doctor. Fixed persistence.xml C/S connection property to "javax.persistence.jdbc.user". Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding
|
|
again merger missing logs + objectdb exception
Zwicker Hopefully you will be able to fix the database with the Doctor before restarting the server ... . Meanwhile, have you fixed the database using the Doctor and started the system again successfully? support ... to the database corruption. For this we probably have meanwhile a fix . As regards the query, we'll try
|
|
ObjectDB 2.7.0
to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same object in one transaction ( issue #2027 ). Fixed objectdb.jar to include META-INF/MANIFEST.MF as the first entry (required by Apache Karaf ). Fixed a cache bug in repeating some sorts of LIKE queries
|
|
ObjectDB 2.5.6
Changed merge behavior (following this forum thread ). Fixed a TomEE - ObjectDB client-server integration issue ( issue #1407 ). Fixed a ClassCastException on selecting an embedded ID field in queries. Fixed an exception ( NullPointerException ) in update queries (since 2.5.5_12). Fixed
|
|
ObjectDB 2.7.2
Added initial support for Java 9 . Attempt to fix (currently a workaround) and log the nested section key bug ( issue #2127 ). Fixed a bug in queries of the form "SELECT o FROM ... WHERE o == :arg" Fixed a bug in displaying inverse (mapped by) relations in the Explorer. Fixed a bug in reusing
|
|
missing merger
would be to use the Doctor to fix the database. Maybe the difference between the databases in #4 and #5 ... above are different. They are not related to this specific incident, right? Have you fixed the database ... you try to restart the system without fixing the database? Does the system work after fixing
|
|
ObjectDB 2.4.5
) relationships ( issue #769 ). Improved performance of database file extending. Fixed a bug in ignoring global cascade persist in an ORM file. Fixed a NullPointerException during query execution ( issue #978 ). Fixed a class loading issue during automatic class scanning. Fixed a Doctor deadlock . Fixed
|
|
Database access error , Doctor hanging on trying to repair, production shutdown at our biggest customer
). This could also help us fixing the Doctor to handle this situation in the future. support Support we are using 2 ... Zwicker OK. If fixing still fails please share the database and we will try to repair it as soon as ... these can happen ? how can we go on ivestigating and fixing ?) ... *** m_filePos - 3012019718 *** m_filePos
|
|
ObjectDB 2.5.0
database time when recovery is disabled. Fixed hasSingleIdAttribute for partial primary key inheritance. Fixed a bug in JOIN FETCH. Fixed a bug in loading reference primary key field of an abstract type. Fixed JDO sequence names to be fully qualified names (issue #1074 ). Fixed accessing a package
|
|
ObjectDB 2.6.5
property method names . Fixed a bug in retrieving pure time values (java.sql.Time). Fixed a bug in MEMBER OF queries on embedded objects. Fixed a bug in querying indexed nested embedded objects. Fixed a bug in querying enhanced embeddable classes. Fixed server crash on exceeding maximum number
|
|
ObjectDB 2.3.5
(for Windows 7 and 64 bits). Fixed handling a Calendar parameter value in criteria queries. Fixed using type operator and literals in client server queries ( issue #605 ). Fixed eager fetch issues. Fixed a bug in using type literals in queries. Fixed a bug in passing a new entity object with no id as
|
|
javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName
that might fix it (see #2)? support Support I tried version 2.2.6_01 and it did NOT fix ... addition, please notice that this attempt to fix the problem was done without the ability to reproduce ... Support Yes, after complete library reassignment and rebuild 2.2.6_01 did fix it. Sorry, i did
|
|
ObjectDB 2.2.5
to the Server and Explorer About dialog boxes. Fixed an UPDATE/DELETE query bug in client-server mode. Fixed an ArrayIndexOutOfBoundsException in retrieval of large objects. Fixed Explorer display of user defined serializable objects. Fixed a bug in using NOT NULL in criteria queries . Fixed a bug
|
|
ObjectDB 2.2.0
, disabled recording). Fixed a critical database structure bug ( issue #187 ). Fixed a critical bug in schema evolution of modified ancestor classes. Fixed a bug in handling indexes in a new ancestor class. Fixed a query cache bug. Fixed several bugs in query processing and running. Fixed a query
|
|
ObjectDB 2.2.7
Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache. Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance
|
|
ObjectDB 2.6.0
to JPA Metamodel attributes. Fixed ObjectDB OSGi bundle to support enhanced classes. Fixed handling class loader switch (avoiding automatic database close and reopen). Fixed a NullPointerException on cascading persistence through a mapped by collection ( issue #1563 ). Fixed a bug in using enhanced
|
|
ObjectDB 2.4.2
Fixed a bug in handling mapped super class with no primary key ( issue #864 ). Fixed a bug in handling enum in the primary key ( issue #852 ). Fixed an initialization of inverse (mapped by) fields by JOIN FETCH ( issue #854 ). Fixed type checking of query parameters. Changed merge implementation
|
|
ObjectDB 2.3.3
Improved compilation performance of OR queries with many elements. Fixed eager fetch of maps and nested embedded objects. Fixed a bug in removing a new flushed entity object before first commit ( issue #562 ). Fixed a NullPointerException in accessing inverse (mapped by) collection fields
|
|
ObjectDB 2.8.4
Fixed a critical bug that may cause collisions between schema versions ( issue #2621 ). Fixed unsupported unwrap to throw _PersistenceException (a subclass of PersistenceException). Fixed an Explorer bug in presenting composite IDs. Fixed a bug in using date and time query parameters in
|
|
ObjectDB 2.8.0
#2403 ). Fixed a bad optimisation in query execution ( issue #2432 ). Fixed an activation issue with some Java versions. Fixed an InternalException ( issue #2153 , see also issue #2027 ). Fixed long compilation time of queries with many (10) JOINs ( issue #2423 ) Fixed the new option in 2.7.6_01
|
|
ObjectDB 2.6.2
). Fixed a NullPointerException on concurrent access of first object of an entity class. Fixed bug in using EnumType.STRING based enum collection as a query parameter ( issue #1639 ). Fixed a synchronization bug ( issue #1643 ). Fixed a regression of build 2.6.1_03 in supporting interfaces in
|
|
ObjectDB 2.2.6
Fixed the "Attempt to reuse an existing primary key value" after flush bug. Fixed a bug in tracking changes to collections of new flushed entity objects. Fixed generated value (ID allocation) bug with flush and in EJB containers. Fixed a NullPointerException on getObjectsById. Fixed a server
|
|
ObjectDB 2.6.7
configuration. Fixed a synchronization bug in using temporary files in large transactions. Fixed a bug in using @TableGenerator / GenerationType.TABLE. Fixed handling classes with no persistent fields in new automatic activation of indexes. Fixed a regression bug due to changing references to weak
|
|
ObjectDB 2.5.1
FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock on Schema Update during Multithreading activity ( issue #1139 ). Fixed a bug in loading mapped (inverse) to-many relationship into an array field ([]) ( issue #1131 ). Fixed a bug in loading mapped (inverse
|
|
ObjectDB 2.3.6
Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610 , #621 , #625 ). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression
|
|
ObjectDB 2.0.4
Added support for JTA and Java EE Containers ( issue #8 ). Fixed a bug in indexing entity objects. Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced detached embedded objects. Fixed a spring transformer (LoadTimeWeaver) problem. Fixed a class
|
|
ObjectDB 2.3.0
to memory leak ( issue #453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. Fixed several NullPointerException bugs. Fixed the "Failed to generate dynamic type" exception. Fixed a bug in query plans that use
|
|
ObjectDB 2.8.8
. Improved field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted type. Fixed a primary key query issue. Fixed a bug in comparing embedded objects in queries ( issue
|
|
ObjectDB 2.3.2
Fixed a bug in "p.id IN :ids" queries. Fixed a bug in handling NOT = queries ( issue #536 ). Fixed ClassCastException and NullPointerException in using a composite index in queries ( issue #531 ). Fixed Explorer bugs: editing embedded objects and using connection urls. Fixed
|
|
ObjectDB 2.6.9
Added support for integration with WebSphere / Liberty application server. Fixed deletin g large transaction temporary files (in the experimental large transactions feature ). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects. Fixed a query
|
|
ObjectDB 2.4.1
Fixed a bug of duplicating new objects during merge . Fixed a username/password issue in using EntityManagerFactory 's getMetamodel . Fixed a bug in detachment of hollow objects on close ( issue #799 ). Fixed a Doctor exception ( issue #796 ). Fixed a Doctor bug in checking byte[] arrays
|
|
ObjectDB 2.9.0
. Fixed A NullPointException when using EntityManagerFactory with different class loaders. Fixed a missing call to @PostUpdate when object change is detached by JDOHelper.makeDirty . Fixed a bug of classifying inherited inverse fields as dependent. Fixed improper use of indexes on collections
|
|
ObjectDB 2.2.8
Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running
|
|
combined index not used
and provide a fix . support Support The reason for not using the composite index was found and can be fixed . As there are too many possible combinations for covering the filter: "a.type = 0 ... combinations to 10000 solves this issue so a quick fix is possible for this specific issue
|
|
ObjectDB 2.6.4
to collections. Fixed large transaction temporary files implementation ( feature request #1658 ). Fixed a bug in handling large objects with long primary keys as query results ( issue #1717 ). Fixed detachment of embedded objects to collections. Fixed database page objects reuse to release to be cleared
|
|
ObjectDB can't be activated
to provide a fix as early as we can next week. support Support Yes, this is the one that failed ... .5.5_06, which includes an attempt to fix this issue. support Support No its not fixed ... cannot see any new activation by you today. To test the fix please run activation again using the new build
|
|
ObjectDB 2.5.2
Framework versions (with JPA 1.0). Fixed "InternalException: InterruptedException" due to application interrupts in embedded mode. Fixed a class loading conflict with Log4j. Fixed very slow processing of a composite BETWEEN query. Fixed NullPointerException when using AND TRUE in WHERE clause (issue
|
|
Removed entities can be found by query in the same transaction
.7.4_04. btc_es BTC EmbeddedSystems Build 2.7.4_04 fixes issue #2280 but seems to cause new ... (until commit). Build 2.7.4_04 fixed it by creating a new snapshot on query execution if changes ... EmbeddedSystems It is possible that the fix in build 2.7.4_04, which improves visibility of committed
|
|
InternalException when using MEMBER OF on a large list in a query
. A similar issue was fixed a few years ago and since then this is the first report. First, please check your database with the Doctor. If the error repeats, try to fix the database by running the Doctor ... you very much for this test - it wouldn't be possible to understand and fix the issue without this help
|