Re: Can a commiit complete of server but not on JDBC client?
Posted by: Filipe Silva
Date: May 04, 2016 08:44AM

The JDBC connector isn't "aware" of anything. When you issue a 'commit' instruction in the client, an equivalent order is sent to the server, if it fails executing it then it will bee "seen" in the client as an exception.

As long as the commit order reaches the server the commit is effectively executed. If there is a loss of communication, it only depends on if it happened before or after the commit order was actually sent to the server. After reestablishing the connection to the server, the client should be able to see the data that was committed and non-committed data won't be available. Mind that I'm not taking in consideration other implementation details in the client, where there can be caches, locally stored data, etc...

Options: ReplyQuote

Written By
Re: Can a commiit complete of server but not on JDBC client?
May 04, 2016 08:44AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.