TAILIEUCHUNG - OCA /OCP Oracle Database 11g A ll-in-One Exam Guide- P40

OCA /OCP Oracle Database 11g A ll-in-One Exam Guide- P40:There is an ever increasing demand for staff with IT industry certification. The benefits to employers are significant—they can be certain that staff have a certain level of competence—and the benefits to the individuals, in terms of demand for their services, are equally great. Many employers are now requiring technical staff to have certifications, and many IT purchasers will not buy from firms that do not have certified staff. | OCA OCP Oracle Database 11g All-in-One Exam Guide 346 Monitor and Resolve Locking Conflicts In any multiuser database application it is inevitable that eventually two users will wish to work on the same row at the same time. The database must ensure that it is a physical impossibility. The principle of transaction isolation the I of the ACID test requires that the database guarantee that one session cannot see or be affected by another session s transaction until the transaction has completed. To accomplish this the database must serialize concurrent access to data it must ensure that even though multiple sessions have requested access to the same rows they actually queue up and take turns. Serialization of concurrent access is accomplished by record and table locking mechanisms. Locking in an Oracle database is completely automatic. Generally speaking problems only arise if software tries to interfere with the automatic locking mechanism with poorly written code or if the business analysis is faulty and results in a business model where sessions will collide. Shared and Exclusive Locks The standard level of locking in an Oracle database guarantees the highest possible level of concurrency. This means that if a session is updating one row the one row is locked nothing else. Furthermore the row is only locked to prevent other sessions from updating it other sessions can read it at any time. The lock is held until the transaction completes either with a COMMIT or a ROLLBACK. This is an exclusive lock the first session to request the lock on the row gets it and any other sessions requesting write access must wait. Read access is permitted though if the row has been updated by the locking session as will usually be the case then any reads will involve the use of undo data to make sure that reading sessions do not see any uncommitted changes. Only one session can take an exclusive lock on a row or a whole table at a time but shared locks can be taken on the same object

TỪ KHÓA LIÊN QUAN
TAILIEUCHUNG - Chia sẻ tài liệu không giới hạn
Địa chỉ : 444 Hoang Hoa Tham, Hanoi, Viet Nam
Website : tailieuchung.com
Email : tailieuchung20@gmail.com
Tailieuchung.com là thư viện tài liệu trực tuyến, nơi chia sẽ trao đổi hàng triệu tài liệu như luận văn đồ án, sách, giáo trình, đề thi.
Chúng tôi không chịu trách nhiệm liên quan đến các vấn đề bản quyền nội dung tài liệu được thành viên tự nguyện đăng tải lên, nếu phát hiện thấy tài liệu xấu hoặc tài liệu có bản quyền xin hãy email cho chúng tôi.
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.