Processing transactions, PL-SQL Programming

Processing Transactions

This part describes how to do the transaction processing. You learn the fundamental techniques that safeguard the consistency of your database, involving how to control whether changes to the Oracle data are made permanent or undo.

The jobs or tasks that Oracle manages are termed as the sessions. The user session is started whenever you run an application program or an Oracle tool and connect to the Oracle. To permit the user sessions to work "concurrently" and share the computer resources, the Oracle should control the concurrency, the accessing of similar data by various users. Without sufficient concurrency controls, there might be a loss of the data integrity. That is, the changes to data might be prepared in the wrong order.

Oracle uses the locks to control the concurrent access to data. The lock gives you the temporary ownership of a database resource like a table or a row of data. And hence, the data cannot be changed by other users unless you finish with it. You never require explicitly lock a resource as default locking mechanisms protect the Oracle data and structures. Though, you can request data locks on the tables or rows when it is to your benefit to override the default locking. You can prefer from various modes of locking like the exclusive and row share.

The deadlock can occur when two or many users try to access the similar schema object. For illustration, the two users updating the similar table might wait if each tries to update a row presently locked by the other. As each user is waiting for the resources held by the other user, neither can continue till the Oracle breaks the deadlock by signaling an error to the last participating transaction.

If a table is being queried by one user and updated by the other at similar time, the Oracle generates a read-consistent view of the data for the query. That is, the data read by the query does not change, once a query begins and as it proceeds. The Oracle take snapshot of the table's data and records changes in the rollback segment. The Oracle uses rollback segments to build read-consistent query results and to undo the changes when necessary.

Posted Date: 10/4/2012 4:50:28 AM | Location : United States







Related Discussions:- Processing transactions, Assignment Help, Ask Question on Processing transactions, Get Answer, Expert's Help, Processing transactions Discussions

Write discussion on Processing transactions
Your posts are moderated
Related Questions
Parameter & Keyword Description: function_name: The user-defined function is identifying by that keyword. parameter_name: This identifies the formal parameter that

Semidifference via EXCEPT and JOIN - SQL SELECT * FROM (SELECT StudentId FROM IS_CALLED WHERE Name = 'Devinder' EXCEPT DISTINCT CORRESPONDING SELECT StudentId

First Step at defining type SID in SQL CREATE TYPE SID AS ( C VARCHAR(5) ) ; Explanation: TYPE SID announces that a type named SID is being defined to the syst

Using raise_application_error The Package DBMS_STANDARD that is supplied with Oracle gives language facilities that help your application to interact with Oracle. For illustra

UNNEST operator in SQL The inverse operator of GROUP is UNGROUP. SQL has an operator, UNNEST, that can be used for similar purposes, but its method of invocation is somewhat p

Negation (NOT, ¬) - SQL There are three rows instead of just two. As you can see, ¬ p is defined as in two-valued logic (2VL) when p is either true or false, but ¬ (unknown) i

Example of GROUPBY Operator Example: How many students sat each exam, using GROUP BY, NATURAL LEFT JOIN, and COALESCE SELECT CourseId, COALESCE (n, 0) AS n FROM COURS

Query: SELECT * FROM EMPLOYEE1; Select 5 columns and all rows from one table Query: SELECT C_ID, COMPANY, BUILDING, DEPARTMENT, BRANCH FROM CONTRACT;

%ISOPEN The Oracle closes the SQL cursor automatically after executing its related SQL statement. As a result, the %ISOPEN forever yields FALSE.

Avoiding Collection Exceptions   In many cases, if you reference a nonexistent collection element, then PL/SQL raises a predefined exception. Consider the illustration shown b