SERIALLY_REUSABLE Pragma

SERIALLY_REUSABLE Pragma

The pragma SERIALLY_REUSABLE indicates that the package state is needed only for the duration of one call to the server. An example could be an OCI call to the database or a stored procedure call through a database link. After this call, the storage for the package variables can be reused, reducing the memory overhead for long-running sessions. For more information, see Oracle Database Application Developer's Guide - Fundamentals.

Syntax

pragma serially_resuable ::=

PRAGMA SERIALLY_REUSABLE ;

Keyword and Parameter Description

PRAGMA

Signifies that the statement is a pragma (compiler directive). Pragmas are processed at compile time, not at run time. They do not affect the meaning of a program; they simply convey information to the compiler.

Usage Notes

This pragma is appropriate for packages that declare large temporary work areas that are used once and not needed during subsequent database calls in the same session.

You can mark a bodiless package as serially reusable. If a package has a spec and body, you must mark both. You cannot mark only the body.

The global memory for serially reusable packages is pooled in the System Global Area (SGA), not allocated to individual users in the User Global Area (UGA). That way, the package work area can be reused. When the call to the server ends, the memory is returned to the pool. Each time the package is reused, its public variables are initialized to their default values or to NULL.

Serially reusable packages cannot be accessed from database triggers or other PL/SQL subprograms that are called from SQL statements. If you try, Oracle generates an error.

Examples

Example 13–5 creates a serially reusable package.

Example 13–5 Creating a Serially Reusable Package

CREATE PACKAGE pkg1 IS PRAGMA SERIALLY_REUSABLE; num NUMBER := 0;

PROCEDURE init_pkg_state(n NUMBER); PROCEDURE print_pkg_state;

END pkg1;

/

CREATE PACKAGE BODY pkg1 IS PRAGMA SERIALLY_REUSABLE;

PROCEDURE init_pkg_state (n NUMBER) IS

PL/SQL Language Elements 13-111

SERIALLY_REUSABLE Pragma

BEGIN

pkg1.num := n; END;

PROCEDURE print_pkg_state IS BEGIN

DBMS_OUTPUT.PUT_LINE('Num: ' || pkg1.num); END;

END pkg1;

/

Related Topics

"AUTONOMOUS_TRANSACTION Pragma" on page 13-6 "EXCEPTION_INIT Pragma" on page 13-38 "RESTRICT_REFERENCES Pragma" on page 13-98

13-112 Oracle Database PL/SQL User’s Guide and Reference

SET TRANSACTION Statement

SET TRANSACTION Statement

The SET TRANSACTION statement begins a read-only or read-write transaction, establishes an isolation level, or assigns the current transaction to a specified rollback segment. Read-only transactions are useful for running multiple queries against one or more tables while other users update the same tables. For more information, see "Setting Transaction Properties with SET TRANSACTION" on page 6-33.

For additional information on the SET TRANSACTION SQL statement, see Oracle Database SQL Reference.

Syntax

set transaction ::=

ONLY

READ

WRITE

Keyword and Parameter Description

READ ONLY

Establishes the current transaction as read-only, so that subsequent queries see only changes committed before the transaction began. The use of READ ONLY does not affect other users or transactions.

READ WRITE

Establishes the current transaction as read-write. The use of READ WRITE does not affect other users or transactions. If the transaction executes a data manipulation statement, Oracle assigns the transaction to a rollback segment.

ISOLATION LEVEL

Specifies how to handle transactions that modify the database.

SERIALIZABLE: If a serializable transaction tries to execute a SQL data manipulation statement that modifies any table already modified by an uncommitted transaction, the statement fails.

To enable SERIALIZABLE mode, your DBA must set the Oracle initialization parameter COMPATIBLE to 7.3.0 or higher.

READ COMMITTED: If a transaction includes SQL data manipulation statements that require row locks held by another transaction, the statement waits until the row locks are released.

USE ROLLBACK SEGMENT

Assigns the current transaction to the specified rollback segment and establishes the transaction as read-write. You cannot use this parameter with the READ ONLY

PL/SQL Language Elements 13-113

SET TRANSACTION Statement

parameter in the same transaction because read-only transactions do not generate rollback information.

NAME

Specifies a name or comment text for the transaction. This is better than using the COMMIT COMMENT feature because the name is available while the transaction is running, making it easier to monitor long-running and in-doubt transactions.

Usage Notes

The SET TRANSACTION statement must be the first SQL statement in the transaction and can appear only once in the transaction.

Examples

For examples, see the following:

Example 6–40, "Using SET TRANSACTION to Begin a Read-only Transaction" on page 6-33

Related Topics

"COMMIT Statement" on page 13-24 "ROLLBACK Statement" on page 13-103 "SAVEPOINT Statement" on page 13-106

13-114 Oracle Database PL/SQL User’s Guide and Reference