|OBJY-20799||Crash when trying to use a Class_Object after an abort.||After an abort, if a Class_Object (created before the abort) is accessed, we would get a crash.||Java|
|OBJY-20629||Regression: Session is not always automatically joined to thread when using Unrestricted Thread Policy||Session is not always automatically joined to thread when using 'Unrestricted Thread Policy' causing a null pointer exception.||Java|
|OBJY-20482||Collections and ooMap returning a different Java reference to the same object||ooMap was returning a different Java reference to the same object that was being retained by a hard reference in one of the classes.||Java|
|OBJY-20421||File locking can lead to failed aborts and irrecoverable/growing journal files||File locks, such as those placed by antiviruses during scans, can cause the abort process for a failed transaction to itself fail and cause the journal file to keep growing.||Kernel - Recovery, Tools - oocleanup|
|OBJY-20827||Starting multiple sessions to the same federated database in different threads may cause an exception||When multiple seesions are started to the same federated database in different threads at (approximately) the same time, an exception may occur.||Kernel - Session Manager(se)|
|OBJY-20749||Setting an invalid log directory via an environment variable may lead to an irrecoverable application state||Setting an invalid log directory via an environment variable may lead to an irrecoverable application state||Kernel - Session Manager(se)|
|OBJY-20559||Exclude class with predicate not filtering correctly||When a graph view is used which excludes a class with a predicate, the objects that satisfy the predicate are still returned, but the navigation does not return along their path. In other words, they manage to be qualified as a result, but the path is not qualified. Also, if there are other paths that extend along objects that do not satisfy the predicate, their paths are also not qualified even though they should be||Relationship Analytics|
|OBJY-20362||non-shortest path exclusion doesn't always work in a depth-first navigation||When using the PathDepthBeyondShortestPolicy in a depth-first navigation, we skip revisiting a node in a path which is longer than the first path seen, instead of comparing with the shortest path seen so far.
(Note that this is not a problem in breadth-first mode)
|OBJY-20353||Include the source object as part of a path object (as a convenience for result handlers)||A startingObject field is being added to class objy::ra::Path.||Relationship Analytics|
|OBJY-20641||ooattachdb doesn't always properly update internal (database) scope names||Scope names are not being properly updated when multiple DBs are attached with ooattachdb in conjunction with the -dbmap flag||Tools - ooattachdb|
|OBJY-20800||Regression:oochange -fdnumber with standalone flag fails with Internal error 3012||The oochange tool may fail when used to change the federation id in combination with the -standalone flag.||Tools - oochange|
|OBJY-16518||oocheck and oofix report incorrect byte error warning||Large object free bytes value can be incorrect and oocheck may throw this misleading warning:
WARNING: Large page 10-4-240-0 free bytes error; (total pages 2 * page size 8192) - (offset object 1024 + object size 14624) = 736; does not equal free bytes 33504 found in this page.
|Tools - oocheck, oofix|
|OBJY-19659||Enhancement to oocheck to detect container index flag wrongly set by ootidy (OBJY-19414). Enhancement to oofix to fix the issue.||In OBJY-19414 for R11.0, we fixed the issue where running "ootidy" on a database with DB-level index, reset the index container flag causing it be included in database scans. This resulted in unexpected lock conflicts on the index container. This enhancement to oofix will enable it to reset the container flags wrongly set by ootidy.||Tools - oocheck, oofix|
|OBJY-19327||oofile fails to read large database files||The tool oofile may fail to read large database files and may exit with the following error:
Error #13001: oofile: The file "test.DB" appears to be empty.
|Tools - oofile|
|OBJY-20858||Enhancement to oofix for removing database level scope names that are not referenced back.||In certain scenarios where we knowingly cannot guarantee the integrity of scope names, (for example while running ooattachdb on DBs that serve as scope names to objects in other DBs) , oofix should detect and delete the problematic named scope from the database being attached.
This enhancement to oofix will also be beneficial in scenarios where the DB has similar data inconsistencies due to other unknown reasons.
|Tools - oofix|
Thursday, May 30, 2013