Đang chuẩn bị liên kết để tải về tài liệu:
Oracle PL/SQL Language Pocket Reference- P29

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Oracle PL/SQL Language Pocket Reference- P29: This pocket guide features quick-reference information to help you use Oracle's PL/SQL language. It includes coverage of PL/SQL features in the newest version of Oracle, Oracle8i. It is a companion to Steven Feuerstein and Bill Pribyl's bestselling Oracle PL/SQL Programming. Updated for Oracle8, that large volume (nearly 1,000 pages) fills a huge gap in the Oracle market, providing developers with a single, comprehensive guide to building applications with PL/SQL and building them the right way. . | PROCEDURE DBMS_TRANSACTION.SAVEPOINT C.15.13 The USE_ROLLBACK_SEGMENT procedure The USE_ROLLBACK_SEGMENT procedure assigns the current transaction to the specified rollback segment. This option also establishes the transaction as a read-write transaction. The rollback segment specified must be online. You cannot use both the READ_ONLY and USE_ROLLBACK_SEGMENT procedures within the same transaction. Read-only transactions do not generate rollback information and thus cannot be assigned rollback segments. This procedure is equivalent to the SQL command SET TRANSACTION USE ROLLBACK SEGMENT. The specification is PROCEDURE DBMS_TRANSACTION.USE_ROLLBACK_SEGMENT rb_name VARCHAR2 C.15.14 The BEGIN_DISCRETE_TRANSACTION procedure The BEGIN_DISCRETE_TRANSACTION procedure streamlines transaction processing so short transactions can execute more rapidly. During discrete transactions normal redo information is generated although it is stored in a separate location in memory. When the discrete transaction commits the redo information is written to the redo log file and data block changes are applied directly. As such there is no need for undo information in rollback segments. The block is then written to the database file in the usual manner. The call to this procedure is effective only until the transaction is committed or rolled back the next transaction is processed as a standard transaction. Any PL SQL using this procedure must be coded to ensure that the transaction is attempted again in the event of a discrete transaction failure. 3 The specification is 3 For more information on this topic see Using Discrete Transactions in Oracle8 Server Tuning . PROCEDURE DBMS_TRANSACTION.BEGIN_DISCRETE_TRANSACTION C.15.15 The PURGE_MIXED procedure The PURGE_MIXED procedure deletes information about a given in-doubt distributed transaction that has had mixed outcomes due to a transaction resolution mismatch. This occurs when an in-doubt distributed transaction is forced to commit or roll