Skip to Main Content

Berkeley DB Family

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

HA - Effect of using a cursor without explicit transaction/non read-uncommitted.

keithwallMar 13 2017 — edited Mar 19 2017

Our application can operate with either ReplicatedEnvironments (HA) or standard Environments (non-HA).   We have just noticed that our application, when running in HA mode, violates the rule stated in the javdoc for Cursor#getNext() and others that "In a replicated environment, an explicit transaction must have been specified when opening the cursor, unless read-uncommitted isolation is specified via the CursorConfig or LockMode parameter".   We are inadvertently calling #getNext() and #getSearchKey() on cursors from ReplicatedEnvironments without a transaction and in lock modes other than read-uncommitted.  The application has seemingly been working without error for many years despite this problem.

We intend to fix the application immediately but need to formulate a response for our existing user base. 

What harmful effects can we expect from this mistake?  The model of our application is such that it does not  actually read from an HA node until it is made master (in other words, the replica nodes are dormant, from an application perspective, until they are awoken by the election result).

We are using 5.0.104.

Thanks in advance for any advice.

This post has been answered by Greybird-Oracle on Mar 17 2017
Jump to Answer

Comments

Ices_Eyes
Up...!
Ices_Eyes
Noone is experiencing the same issue?
-K-
My suggestion is to open a SR at Metalink/MOS (if you have a database support contract), else hope someone from the team is interested in logging/debugging this through the forum.

Regards,
K.
Ices_Eyes
-K- wrote:
My suggestion is to open a SR at Metalink/MOS (if you have a database support contract), else hope someone from the team is interested in logging/debugging this through the forum.

Regards,
K.
Unfortunately I have no a support contract, so...Hoping someone of the developer read this...Maybe it will be fixed in the next release :)

PS: if some developer read this, please let me know, so I stop to try to mantaint this thread alive :P
Ices_Eyes
Any news about this bug? :)
hlaebe
Hi,
did you try GeoRaptor [GeoRaptor |http://sourceforge.net/projects/georaptor/] ? We have tools for indexing, maintaining metadata (which might be the reason for this non-support in SQL Developer, since metadata is required for indexing).

Give it a try, it is free!

Regards,
Holger

Edited by: hlaebe on 03.02.2010 08:56
Ices_Eyes
Thanks, that work! And is pretty useful too... :)
Ices_Eyes
By the way, this bug is still present in version 2.1.1... :-S
1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 16 2017
Added on Mar 13 2017
4 comments
264 views