Q
Problem solve Get help with specific problems with your technologies, process and projects.

Committed and uncommitted changes in multinode RAC environment

In a multinode RAC environment, clients connected to the node1 made some changes in the data, but not commited. After some time another user connected to the node, updated the same data and committed. What will happen to the data of the first user?

Could you please give the explanation for the following scenario: In a multinode RAC environment, clients connected to the node1 made some changes in the data, but not commited (for example, sal field of emp table). After some time another user connected to the node, updated the same data and committed. What will happen to the data of the first user? Will it be available? What will happen if the first user commits the transaction?
If the first user makes changes to a row of a table, that user has an exclusive lock on that row. If a second user attempts to change that same row, the second user will not be able to obtain the required lock it needs until the first user either commits or rolls back their changes. It is not possible for the second user to commit their transaction on the same data that the first user holds a lock for.

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close