This section will provide a basic understanding of PL/SQL. This document will briefly cover the main concepts behind PL/SQL and provide brief examples illustrating the important facets of the language. Most of the information contained in this section is DIRECTLY extracted from ``PL/SQL User's Guide and Reference'' and all credit should be given to ORACLE. If you require more detailed information than provided in this section, consult the above stated manual. PL/SQL is Oracle's procedural language extension to SQL, the relational database language. PL/SQL fully integrates modern software engineering features such as data encapsulation, information hiding, overloading, and exception handling, and so brings state-of-the-art programming to the ORACLE Server and a variety of ORACLE tools.

Overview of PL/SQL
With PL/SQL, you can use SQL statements to manipulate ORACLE data and flow-of-control statements to process the data. Moreover, you can declare constants and variables, define subprograms (procedures and functions), and trap runtime errors. Thus, PL/SQL combines the data manipulating power of SQL with the data processing power of procedural languages. PL/SQL is a block-structured language. That is, the basic units (procedures, functions, and anonymous blocks) that make up a PL/SQL program are logical blocks, which can contain any number of nested sub-blocks. Typically, each logical block corresponds to a problem or subproblem to be solved. A block (or sub-block) lets you group logically related declarations and statements. That way you can place declarations close to where they are used. The declarations are local to the block and cease to exist when the block completes. [DECLARE -- declarations] BEGIN -- statements [EXCEPTION -- handlers] END;

Lexical Units PL/SQL is not case-sensitive, so lower-case letters are equivalent to corresponding upper-case letters except within string and character literals. A line of PL/SQL text contains groups of characters known as lexical units, which can be classified as follows:

•delimiters (simple and compound symbols) •identifiers, which include reserved words •literals •comments


A delimiter is a simple or compound symbol that has a special meaning to PL/SQL. For example, you use delimiters to represent arithmetic operations such as addition and subtraction. You use identifiers to name PL/SQL program objects and units, which include constants, variables, exceptions, cursors, subprograms, and packages. Some identifiers called RESERVED WORDS, have a special syntactic meaning to PL/SQL and so cannot be redefined. For flexibility, PL/SQL lets you enclose identifiers within double quotes. Quoted identifiers are seldom needed, but occasionally they can be useful. A literal is an explicit numeric, character, string, or Boolean value not represented by an identifier. •Two kinds of numeric literals can be used in arithmetic expressions: integers and reals. •String literal is a sequence of zero or more characters enclosed by single quotes. All string literals except the null string (`') belong to type CHAR. PL/SQL is case-sensitive within string literals. •Boolean literals are the predefined values TRUE and FALSE and the non-value NULL (which stands for a missing, unknown, or inapplicable value). Keep in mind that Boolean literals are not strings. The PL/SQL compiler ignores comments but you should not. Adding comments to your program promotes readability and aids understanding. PL/SQL supports two comment styles: single-line and multiline. Single-line comments begin with a double hyphen (--) anywhere on a line and extend to the end of the line. Multiline comments begin with a slashasterisk (/*), end with an asterisk-slash (*/), and can span multiple lines. You cannot nest comments.

Datatypes Every constant and variable has a datatype, which specifies a storage format, constraints, and valid range of values. PL/SQL provides a variety of predefined scalar and composite datatypes. A scalar type has no internal components. A composite type has internal components that can be manipulated individually. PL/SQL Datatypes are similar to SQL's Datatypes but some of the common datatypes are discussed again. For more information on the PL/SQL Datatypes see Chapter 2 of ``PL/SQL User's Guide and Reference.'' •(NUMBER) You use the NUMBER datatype to store fixed or floating point numbers of virtually any size. You can specify precision, which is the total number of digits, and scale, which determines where rounding occurs. NUMBER[(precision, scale)] You cannot use constants or variables to specify precision and scale; you must use an integer literals. •(CHAR) You use the CHAR datatype to store fixed-length character data. The CHAR datatype takes an optional parameter that lets you specify a maximum length up to 32767 bytes.

CHAR[(maximum_length)] You cannot use a constant or variable to specify the maximum length; you must use an integer literal. If you do not specify the maximum length, it defaults to 1. •(VARCHAR2) You use the VARCHAR2 datatype to store variable-length character data. The VARCHAR2 datatype takes a required parameter that lets you specify a maximum length up to 32767 bytes.

VARCHAR2(maximum_length) You cannot use a constant or variable to specify the maximum length; you must use an integer literal.


•(BOOLEAN) You use the BOOLEAN datatype to store the values TRUE and FALSE and the non-value NULL. Recall that NULL stands for a missing, unknown, or inapplicable value. The BOOLEAN datatype takes no parameters. •(DATE) You use the DATE datatype to store fixed-length date values. The DATE datatype takes no parameters. Valid dates for DATE variables include January 1, 4712 BC to December 31, 4712 AD. When stored in the database column, date values include the time of day in seconds since midnight. The date portion defaults to the first day of the current month; the time portion defaults to midnight.

Datatype Conversion Sometimes it is necessary to convert a value from one datatype to another. PL/SQL supports both explicit and implicit (automatic) datatype conversions. To specify conversions explicitly, you use built-in functions that convert values from one datatype to another. PL/SQL conversion functions are similar to those in SQL. For more information on conversion functions see Chapter 2 of ``PL/SQL User's Guide and Reference.'' When it makes sense, PL/SQL can convert the datatype of a value implicitly. This allows you to use literals, variables, and parameters of one type where another type is expected. If PL/SQL cannot determine which implicit conversion is needed, you get a compilation error. It is your responsibility to ensure that values are convertible. For instance, PL/SQL can convert the CHAR value '02-JUN-92' to a DATE value, but PL/SQL cannot convert the CHAR value 'YESTERDAY' to a DATE value.

Declarations Your program stores values in variables and constants. As the program executes, the values of variables can change, but the values of constants cannot. You can declare variables and constants in the declarative part of any PL/SQL block, subprogram, or package. Declarations allocate storage space for a value, specify its datatype, and name the storage location so that the value can be referenced. They can also assign an initial value and specify the NOT NULL constraint. birthdate DATE; emp_count SMALLINT := 0; acct_id VARCHAR2 (5) NOT NULL := 'AP001'; The first declaration names a variable of type DATE. The second declaration names a variable of type SMALLINT and uses the assignment operator (:=) to assign an initial value of zero to the variable. The third declaration names a variable of type VARCHAR2, specifies the NOT NULL constraint, and assigns an initial value of 'AP001' to the variable. In constant declarations, the reserved word CONSTANT must precede the type specifier. credit_limit CONSTANT REAL := 5000.00; •Using DEFAULT. If you prefer, you can use the reserved word DEFAULT instead of the assignment operator to initialize variables and constants. You can also use DEFAULT to initialize subprogram parameters, cursor parameters, and fields in a user-defined record. tax_year SMALLINT DEFAULT 92; valid BOOLEAN DEFAULT FALSE;


4 .deptno = 20 THEN .2) variable. and column. or you can reference an owner.. . To reference a field..dept..ename := 'JOHNSON'.. In addition. dept_rec3 c1%ROWTYPE. Second. A %ROWTYPE declaration cannot include an initialization clause. Using %TYPE to declare my_dname has two advantages. or database column.. First. loc FROM dept. you use the dot notation. However. dept_rec2 dept%ROWTYPE.•Using %TYPE. Variables and constants declared using %TYPE are treated like those declared using a datatype name. The %TYPE attribute provides the datatype of a variable.dname%TYPE... The column values returned by the SELECT statement are stored in fields. The record can store an entire row of data selected from the table or fetched by a cursor. BEGIN SELECT * INTO emp_rec FROM emp WHERE . credit REAL(7. there are two ways to assign values to all fields in a record at once. DECLARE dept_rec1 dept%ROWTYPE. •Using %ROWTYPE. END.. dept_rec4 c1%ROWTYPE. constant. loc FROM dept. dept_rec1 := dept_rec2.. DECLARE emp_rec emp%ROWTYPE. The %ROWTYPE attribute provides a record type that represents a row in a table (or view).. You can reference a table and column. emp_rec. dept_rec4 := dept_rec3. CURSOR c1 IS SELECT deptno. Columns in a row and corresponding fields in a record have the same names and datatypes. dname.. dept_rec c1%ROWTYPE . The %TYPE attribute is particularly useful when declaring variables that refer to database columns. First. you need not know the exact datatype of dname. you can assign the value of an expression to a specific field. debit credit%TYPE. CURSOR c1 is SELECT deptno. IF emp_rec.2). dname. . PL/SQL allows aggregate assignment between entire records if their declarations refer to the same table or cursor. For example in the declaration below. BEGIN . the datatype of my_dname changes accordingly at run time. table. if the database definition of dname changes. my_dname scott.. PL/SQL treats debit like a REAL(7.

PL/SQL does not allow forward references. IF my_rec. LOOP FETCH my_cursor INTO my_rec. . -. BEGIN SELECT deptno.ename). the following declaration is illegal: i. j.illegal Select-list items fetched by a cursor associated with %ROWTYPE must have simple names or. my_rec. Although you can retrieve entire records. including other declarative statements. CLOSE my_cursor. k SMALLINT. as the example below shows. you cannot insert them.illegal 5 . But. . -.wages.END. Some languages allow you to declare a list of variables belonging to the same datatype. END LOOP.wages > 2000 THEN INSERT INTO temp VALUES (NULL. The column names must appear in the order in which they were defined by the CREATE TABLE or CREATE VIEW statement. the following statement is illegal: INSERT INTO dept VALUES (dept_rec). you can assign a list of column values to a record by using the SELECT and FETCH statement.illegal Second. You must declare a variable or constant before referencing it in other statements..0) wages. loc INTO dept_rec FROM dept WHERE deptno = 30. However. BEGIN OPEN my_cursor. my_rec.. PL/SQL does not allow this. you use an alias called wages: DECLARE CURSOR my_cursor IS SELECT sal + NVL(comm. DECLARE dept_rec dept%ROWTYPE. -. you cannot assign a list of column values to a record by using an assignment statement. if they are expressions. PL/SQL does allow the forward declaration of subprograms. dname. For example. END. However. END IF. the following assignment is illegal: dept_rec2 := dept_rec3.. because dept_rec2 is based on a table and dept_rec3 is based on a cursor. must have aliases. my_rec my_cursor%ROWTYPE.. END. In the following example. EXIT WHEN my_cursor%NOTFOUND. For example. ename FROM emp.

. exceptions. For example. END.. BEGIN SELECT AVG(sal) INTO avg_sal FROM emp WHERE . the names of local variables and formal parameters take precedence over the names of database tables. . variables.. as follows: <<main>> DECLARE ename CHAR(10) := 'KING'.ename. as follows: PROECEDURE calc_bonus (emp NUMBER.. . END. BEGIN DELETE FROM emp WHERE ename = main. even if their datatypes differ. cursors. So.Naming Conventions The same naming conventions apply to all PL/SQL program objects and units including constants. variables and parameters cannot share the same name... not just KING. to avoid ambiguity. use a block label to qualify references. In such cases. bonus OUT REAL) IS avg_sal REAL. In potentially ambiguous SQL statements. the following DELETE statement removes all employees from the emp table..... In such cases... The names of database columns take precedence over the names of local variables and formal parameters. Within the same scope. prefix the names of local variables and formal parameters with my_ as follows: DECLARE my_ename CHAR(10) := 'KING'. END. because ORACLE assumes that both enames in the WHERE clause refer to the database column: DECLARE ename CHAR(10) := 'KING'. the following SELECT statement fails because PL/SQL assumes that emp refers to the formal parameter: PROCEDURE calc_bonus (emp NUMBER. and packages.. all declared identifiers must be unique.. . you can prefix the table name with a username. Or. BEGIN DELETE FROM emp WHERE ename = ename... END.. For example. . procedures. functions. bonus OUT REAL) IS avg_sal REAL.emp WHERE . BEGIN SELECT AVG(sal) INTO avg_sal FROM scott.. . . 6 ..

....refers to parameter . as the following example shows: 7 . The qualifier can be the label of an enclosing block (or enclosing subprogram) as follows: <<outer>> DECLARE birthdate DATE. or package) from which you can reference the identifier. unless you expressly initialize a variable. Assignments Variables and constants are initialized every time a block or subprogram is entered. BEGIN SELECT AVG(sal) INTO avg_sal FROM emp WHERE job = calc_bonus. you can declare the same identifier in two different blocks. identifiers declared in a PL/SQL block are considered local to that block and global to all its sub-blocks. variables are initialized to NULL. name CHAR(10). An identifier is visible only in the regions from which you can reference the identifier using an unqualified name. job CHAR(15) := 'SALESMAN'.The next example shows that you can use a subprogram name to qualify references to local variables and formal parameters: PROCEDURE calc_bonus (empno NUMBER. The scope of an identifier is that region of a program unit (block. END. If you redeclare a identifier in a sub-block. you cannot reference the global identifier unless you use a qualified name. Although you cannot declare an identifier twice in the same block. END. IF birthdate = outer. DECLARE birthdate DATE.job. Note that a block cannot reference identifiers declared in other blocks nested at the same level because those identifiers are neither local nor global to the block. both identifiers remain in scope.. and any change in one does not affect the other. its value is undefined.. bonus OUT REAL) IS avg_sal REAL. The two objects represented by the identifier are distinct. So. -. For example. subprogram. END outer. -. only the local identifier is visible because you must use a qualified name to reference the global identifier. Scope and Visibility References to an identifier are resolved according to its scope and visibility. BEGIN . END IF. Within the sub-block. BEGIN .birthdate THEN . By default.refers to local variable SELECT ename INTO name FROM emp WHERE empno = calc_bonus.. If a global identifier is redeclared in a sub-block..empno. however.

8 . if the condition evaluates to NULL.. Only the values TRUE and FALSE and the nonvalue NULL can be assigned to a Boolean variable. . the IF statement IF done = TRUE THEN . do not compare real numbers for exact equality or inequality. can be simplified as follows: IF done THEN . You can avoid some common mistakes by keeping in mind the following rules: •comparisons involving nulls always yield NULL •applying the logical operator NOT to a null yields NULL •in conditional control statements. Expressions and Comparisons All expressions and comparisons are the same as those explained in the SQL Reference section. So. the relational operators return a Boolean value. the following assignment is legal: DECLARE done BOOLEAN. BEGIN done := (count > 500). there must be a corresponding variable in the INTO list.. Also. each item must return a value that is implicitly convertible to the datatype of its corresponding variable. So comparisons with the boolean values TRUE and FALSE are redundant. END. sal + comm INTO last_name. Alternatively.. wages FROM emp WHERE empno = emp_id. For each item in the SELECT list. SELECT ename. When applied to PL/SQL expressions... For example. never reference a variable before you assign it a value. BEGIN count := count + 1.assigns a null to count END. -.DELCARE count INTEGER. assuming the variable done belongs to type BOOLEAN. It is also a good idea to use parentheses when doing comparisons. Therefore. In general. you can use the SELECT or FETCH statement to have ORACLE assign values to a variable. its associated sequence of statements is not executed Recall that applying the logical operator NULL to a null yields NULL. Some guidelines follow to help you prevent falling into common traps. Remember that a boolean variable is itself either true or false..

the function NVL returns the value of its second argument. you can use all the functions in procedural statements except the miscellaneous function DECODE. a null is returned except in the following cases: •(DECODE) The function DECODE compares its first argument to one or more search expressions. This function is meaningful only in an exception handler. Furthermore. otherwise. For instance. In the next example. •(REPLACE). which are paired with result expressions.If a null argument is passed to a function. •(NVL) If its first argument is null. my_string). SYSDATE). if the value of rating is null. If its second argument is null. 9 . the values of old_string and new_string are the same. 1000. Two functions. In addition. NULL. The built-in functions fall into the following categories: • error-reporting functions • number functions • character functions • conversion functions • data functions • miscellaneous functions You can use all the built-in functions in SQL statements except the error-reporting functions SQLCODE and SQLERRM. Any search or result expression can be null. •(SQLCODE) function SQLCODE return NUMBER Returns the number associated with the most recently raised exception. The NUMBER that SQLCODE returns is negative unless the ORACLE error is "no data found". If a search is successful. NVL returns the value of SYSDATE. the corresponding result is returned. You can use them wherever expressions of the same type are allowed. 'A'. DECODE returns the value 1000: credit_limit := (rating. In the following example. SQLCODE returns the number of the associated ORACLE error. NULL. after the assignment: new_string := REPLACE(old_string. Most functions are the same as those discussed in SQL Reference section except the ones that are discussed below. SQLCODE always returns zero. in which case SQLCODE returns +100. SQLCODE and SQLERRM. NVL returns the value of hire_date: start_date := NVL(hire_date. you can nest them. 4000). 'B'. 2000. if hire_date is null. For internal exceptions. Built-in Functions PL/SQL provides many powerful functions to help you manipulate data. the function REPLACE returns the value of its first argument whether the optional third argument is present or not. give you information about PL/SQL execution errors. Outside a handler.

•(USERENV) function USERENV (str VARCHAR2) return VARCHAR2 Returns information about the current session. SQLCODE returns +1 unless you used the pragma EXCEPTION_INIT to associate the exception with an ORACLE error number. •(SQLERRM) function SQLERRM [(error_number NUMBER)] return CHAR Returns the error message associated with the current value of SQLCODE. UID takes no arguments. successful completion. SQLERRM with no argument always returns the message ``ORA-0000:normal. The PL/SQL table grows as new rows are added. USER takes no arguments.'' For internal exceptions. The message begins with the ORACLE error code. SQLERRM returns the message ``User-Defined Exception'' unless you used the pragma EXCEPTION_INIT to associate the exception with an ORACLE error number. •(UID) function UID return NUMBER Returns the unique identification number assigned to the current ORACLE user.For user-defined exceptions. For user-defined exceptions. PL/SQL Tables PL/SQL provides two composite datatypes: TABLE and RECORD. That is. The following miscellaneous functions may be of use to you in PL/SQL coding. in which case SQLERRM returns the corresponding error message. and database character set in use •'SESSIONID' returns the auditing session identifier •'TERMINAL' returns the operating system identifier for the session terminal You cannot specify the 'ENTRYID' or 'SESSIONID' option in SQL statements that access a remote database. SQLERRM is meaningful only in an exception handler. Outside a handler. Objects of type TABLE are called PL/SQL tables. the size of a PL/SQL table is unconstrained. PL/SQL tables use a primary key to give you array-like access to rows. in which case SQLCODE returns that error number. Like the size of a database table. territory. the number of rows in a PL/SQL table can increase dynamically. You can pass the argument error_number to SQLERRM. which are modeled as (but not the same as) database tables.\\ The string str can have any of the following values: •'ENTRYID' returns an auditing entry identifier •'LANGUAGE' returns the language. in which case SQLERRM returns the message associated with error_number. 10 . SQLERRM returns the message associated with the ORACLE error that occurred. •(USER) function USER return VARCHAR2 Returns the username of the current ORACLE user. You can use the information to write an application audit trail table or to determine the language and character set are in use.

DATE. you specify a primary key value using the array-like syntax plsql_table_name(primary_key_value) where primary_key_value belongs to type BINARY_INTEGER. For example. In the following example. You can assign the value of a PL/SQL expression to a specific row using the following syntax: plsql_table_name(primary_key_value) := plsql_expression. 'CHU').. For example. opens the cursor associated with a given query.. The magnitude range of a BINARY_INTEGER value is -2**31-1 . 2**31-1. or NUMBER. you declare a TABLE type called EnameTabTyp: DECLARE TYPE EnameTabTyp IS TABLE OF emp. First. you can declare PL/SQL tables of that type. In the example below.sal%TYPE INDEX BY BINARY_INTEGER. then closes the cursor. You can declare TABLE types in the declarative part of any block. the following declaration is illegal: ename_tab EnameTabTyp := ('CASEY'. subprogram.. but the primary key must belong to type BINARY_INTEGER.ename%TYPE INDEX BY BINARY_INTEGER. you use a cursor FOR loop to load two PL/SQL tables. sal_tab SalTabTyp. 11 . or package using the syntax: TYPE type_name IS TABLE OF { column_type | variable%TYPE | table. then declare PL/SQL tables of that type. Once you define type EnameTabTyp. you define a TABLE type. TYPE SalTabTyp IS TABLE OF emp.column%TYPE } [NOT NULL] INDEX BY BINARY_INTEGER.. ename_tab EnameTabTyp. as follows: ename_tab EnameTabTyp The identifier ename_tab represents an entire PL/SQL table. neither of which can be named. As a result. PL/SQL table is unconstrained because its primary key can assume any value in the range of values defined for BINARY_INTEGER. You can use the %TYPE attribute to specify a column datatype. DECLARE TYPE EnameTabTyp IS TABLE OF emp. 'STUART'. you cannot initialize a PL/SQL table in its declaration. PL/SQL tables must be declared in two steps. The column can belong to any scalar type. repeatedly fetches rows of values from the cursor into fields in the record. To reference rows in a PL/SQL table.PL/SQL tables can have one column and a primary key. where type_name is a type specifier used in subsequent declarations of PL/SQL tables and column_type is any scalar (not composite) datatype such as CHAR. A cursor FOR loop implicitly declares its loop index as a record.. .. you reference the third row in PL/SQL table ename_tab as follows: ename_tab(3) .ename%TYPE INDEX BY BINARY_INTEGER.

you cannot reference PL/SQL tables in the INTO clause of a SELECT statement. or package using the syntax 7 TYPE type_name IS RECORD (field_name1 {field_type | variable%TYPE | table.i BINARY_INTEGER := 0. User-defined Records You can use the %ROWTYPE attribute to declare a record that represents a row in a table or a row fetched by a cursor. you can use a simple workaround to delete entire PL/SQL tables.. However. records must be declared in two steps. There is no straightforward way to delete rows from a PL/SQL table because the DELETE statement cannot specify PL/SQL tables. ). PL/SQL raises the predefined exception NO_DATA_FOUND.. 12 . ename_tab(i) := emprec. objects of type RECORD are called records. First. records have uniquely named fields. Unlike PL/SQL tables. salary.. You must use a loop to INSERT values from a PL/SQL table into a database column.sal. The composite datatype RECORD lifts those restrictions. As you might expect.ename. you must declare a variable for that purpose. When PL/SQL runs out of memory it raises the predefined exception STORAGE_ERROR. you must use a loop to FETCH values from a database column into a PL/SQL table.load employee names and salaries into PL/SQL tables For emprec IN (SELECT ename.. hire date. END LOOP. and so on.column%TYPE | table%ROWTYPE} [NOT NULL].. Although you cannot delete individual rows from a PL/SQL table. This data is dissimilar in type but logically related. subprogram. Likewise. then declare userdefined records of that type.. BEGIN -. sal FROM emp) LOOP i := i + 1. sal_tab). END. and hire date of an employee would let you treat the data as a logical unit. First. For example. you define a RECORD type. Remember that the size of PL/SQL table is unconstrained so.column%TYPE | table%ROWTYPE} [NOT NULL]. sal_tab(i) := emprec. you cannot specify the datatypes of fields in the record or define fields of your own. (field_name2 {field_type | variable%TYPE | table. . that if you want to maintain a row count. A record that contains such fields as the name. simply assign the empty table to them. salary. declare another PL/SQL table of the same type and leave it empty. Therefore. when you want to delete the original PL/SQL tables. . it does not exist. which can belong to different datatypes. . constrained only by available memory. A PL/SQL table can grow large. You can declare RECORD types in the declarative part of any block. Like PL/SQL tables. If you try to reference an uninitialized row. Until a row is assigned a value. --process the tables process_sals(ename_tab. suppose you have different kinds of data about an employee such as name. Later. Setting a row to NULL does not work because the row remains and does not raise the exception NO_DATA_FOUND when referenced.

Furthermore.. as the example below shows. dept_rec DeptRecTyp. you use the dot notation and the following syntax: record_name. the following syntax is illegal: record_name := (value1.where type_name is a type specifier used in subsequent declarations of records and field_type is any datatype including RECORD and TABLE.dname%TYPE). as follows: dept_rec DeptRecTyp. value2. you can assign values to all fields at once. you can assign one record to another if they belong to the same datatype. This can be done in two ways.. For instance. In the following example.. DECLARE TYPE DeptRecTyp IS RECORD (deptno NUMBER(2) NOT NULL := 20. You can use the %TYPE or %ROWTYPE attribute to specify a field datatype. you declare a RECORD type named DeptRecTyp: DECLARE TYPE DeptRecTyp is RECORD (deptno NUMBER(2) NOT NULL := 20.). The identifier dept_rec represents an entire record. BEGIN SELECT deptno.field_name := plsql_expression.. -. You cannot assign a list of values to a record by using an assignment statement.illegal . .dname%TYPE).. END IF. records cannot be tested for equality or inequality.. the following IF condition is illegal: IF dept_rec1 = dept_rec2 THEN -. 13 . So..dname%TYPE. loc dept.illegal Also. Just make sure the column names appear in the same order as the fields in your record. First. you can assign a list of column values to a record by using the SELECT or FETCH statement. dname dept.. Instead of assigning values separately to each field in a record.dname%TYPE. loc dept. Even if their fields match exactly. loc INTO dept_rec FROM dept WHERE deptno = 30..field_name You can assign the value of a PL/SQL expression to a specific field by using the following syntax: record_name. you can declare records of that type. . dname. . value3.. . Second. a userdefined record and a %ROWTYPE record always belong to different types. records of different types cannot be assigned to each other. To reference individual fields in a record. Once you define type DeptRecTyp. dname dept. END.

seminar. time TimeTyp. it is necessary to take alternative actions depending on circumstances. := '26-Jun-91'. seminar MeetingTyp. purpose CHAR(50)). -. party. 14 . FALSE. BEGIN meeting.minute := 45. meeting MeetingTyp. ELSIF condition2 THEN sequence_of_statements2. ELSE sequence_of_statements3. The iteration structure executes a sequence of statements repeatedly as long as a condition holds true.. and IF-THEN-ELSIF.. meeting. as follows: DECLARE TYPE TimeTyp IS RECORD (minute SMALLINT. depending on whether the condition is true or false. or NULL). The third form of IF statement uses the keyword ELSIF (NOT ELSEIF) to introduce additional conditions.time. END. party PartyTyp. meeting. any computer program can be written using the basic control structures which can be combined in any way necessary to deal with a given problem. as follows: IF condition1 THEN sequence_of_statements1. The sequence structure simply executes a sequence of statements in the order in which they occur. A condition is any variable or expression that returns a Boolean value (TRUE.nested record loc CHAR(15)).time.time := meeting. TYPE PartyTyp IS RECORD (date DATE. IF-THEN-ELSE. . CONTROL STRUCTURES According to the structure theorem.time := meeting.hour := 10.time. Conditional Control: IF Statements Often. . The IF statement lets you execute a sequence of statements conditionally. That is. There are three forms of IF statements: IF-THEN.. The selection structure tests a condition. Such assignments are allowed even if the containing records belong to different datatypes.nested record place CHAR(20). You can assign one nested record to another if they belong to the same datatype. TYPE MeetingTyp IS RECORD (day DATE. then executes one sequence of statements instead of another. hour SMALLINT). time TimeTyp.PL/SQL lets you declare and reference nested records. a record can be the component of another record. whether the sequence is executed or not depends on the value of a condition.time. That is..

but nowhere outside a loop. -. you can use the EXIT statement to complete the loop. Until the condition evaluates to TRUE. IF . . which encloses a sequence of statements between the keywords LOOP and END LOOP.. as follows: LOOP sequence_of_statements3.END IF. and FOR-LOOP. WHILE-LOOP. The label. The EXIT statement forces a loop to complete unconditionally. the loop cannot complete. the loop completes and control passes to the next statement after the loop. -. then control resumes at the top of the loop. THEN . as follows: <<label_name>> LOOP sequence_of_statements. must appear at the beginning of the LOOP statement. LOOP .. When the EXIT statement is encountered. Like PL/SQL blocks. 15 .. LOOP FETCH c1 INTO ..... So. LOOP The simplest form of LOOP statement is the basic (or infinite) loop. There are two forms of EXIT statements: EXIT and EXIT-WHEN. When an EXIT statement is encountered..exit loop immediately END IF.. the condition in the WHEN clause is evaluated. If the condition evaluates to TRUE.. CLOSE c1. END LOOP. END LOOP.. statements within the loop must change the value of the condition. Iterative Control: LOOP and EXIT Statements LOOP statements let you execute a sequence of statements multiple times.. loops can be labeled. EXIT WHEN c1%NOTFOUND. -. an undeclared identifier enclosed by double angle brackets. the loop completes immediately and control passes to the next statement.control resumes here The EXIT-WHEN statement allows a loop to complete conditionally. END LOOP.. There are three forms of LOOP statements: LOOP. With each iteration of the loop. If further processing is undesirable or impossible.exit loop if condition is true . the sequence of statements is executed.. You can place one or more EXIT statements anywhere inside a loop. . EXIT.

.. the condition is evaluated..END LOOP [label_name]. FOR-LOOP Whereas the number of iteration through a WHILE loop is unknown until the loop completes..emp_count LOOP . FOR i IN 1. WHILE-LOOP The WHILE-LOOP statement associates a condition with a sequence of statements enclosed by the keywords LOOP and END LOOP. The range is part of an iteration scheme. as the following example shows: SELECT COUNT(empno) INTO emp_count FROM emp..exit both loops END LOOP. the sequence of statements is executed. END LOOP. PL/SQL lets you determine the loop range dynamically at run time.. END LOOP. the label name can also appear at the end of the LOOP statement. .upper_bound LOOP sequence_of_statements. then use the label in an EXIT statement. . the loop is bypassed and control passes to the next statement... Optionally. FOR counter IN [REVERSE] lower_bound. However. <<outer>> LOOP . The lower bound need not be 1. END LOOP outer. -.. With either form of EXIT statement. the number of iterations through a FOR loop is known before the loop is entered. If the condition evaluates to TRUE. Simply label the enclosing loop that you want to complete. but any enclosing loop. Before each iteration of the loop.. then control resumes at the top of the loop. as follows: WHILE condition LOOP sequence_of_statements. the loop counter increment (or decrement) must be 1. EXIT outer WHEN .... LOOP . Since the condition is tested at the top of the loop. you can complete not only the current loop. FOR loops iterate over a specified range of integers. which is enclosed by the keywords FOR and LOOP.. 16 .. END LOOP.. the sequence might execute zero times. If the condition evaluates to FALSE or NULL. .

Data Manipulation To manipulate ORACLE data. ORACLE makes permanent or undoes all database changes made by a transaction. DELETE. A GOTO statement cannot branch into an IF statement. the GOTO and NULL statements are not crucial to PL/SQL programming. functions.. UPDATE. <<insert_row>> INSERT INTO emp VALUES . The structure of PL/SQL is such that the GOTO statement is seldom needed. You need not explicitly declare the loop counter because it is implicitly declared as a local variable of type INTEGER. and LOCK TABLE commands.. Transaction Control ORACLE is transaction oriented. it can simplify logic enough to warrant its use. or the system control command ALTER SYSTEM. and operators.. Occasionally. or sub-block. It can. session control commands such as SET ROLES. At the same instant. SELECT. transaction control commands. For example. LOOP statement. a GOTO statement cannot branch from an exception handler into the current block. You can manipulate ORACLE data flexibly and safely because PL/SQL supports all SQL data manipulation commands (except EXPLAIN PLAN). A GOTO statement cannot branch from one IF statement clause to another. however. you use the INSERT. A transaction is a series of SQL data manipulation statements that does a logical unit of work. ORACLE uses transactions to ensure data integrity. improve readability.. Hence. If your program fails in the middle of a transaction.. but any enclosing loop. Interaction With ORACLE SQL Support By extending SQL. You cannot reference it outside the loop. A GOTO statement cannot branch out of a subprogram.. BEGIN . GOTO insert_row.The loop counter is defined only within the loop. You can complete not only the current loop. . Sequential Control: GOTO and NULL statements Unlike the IF and LOOP statements. However. that is. the database is restored to its former state automatically. The NULL statement explicitly specifies inaction. it does nothing other than pass control to the next statement. two UPDATE statements might credit one bank account and debit another. 17 . pseudocolumns. PL/SQL does not support data definition commands such as CREATE. The EXIT statement allows a FOR loop to complete prematurely. ORACLE detects the error and rolls back the transaction. Also. Finally. PL/SQL offers a unique combination of power and ease of use. END. the NULL statement is a handy way to create stubs when designing applications from the top down. The NULL statement can make the meaning and action of conditional statements clear and so improve readability.

and row operators in SQL statements. PL/SQL declares a cursor implicitly for all SQL data manipulation statements. children of the root are level 2 and so on. new_ename. you can reference pseudocolumns in SQL statements. Furthermore.You use the COMMIT. NEXTVAL returns the next value in a database sequence. SAVEPOINT marks the current point in the processing of a transaction. and SET TRANSACTION commands to control transactions. In the START WITH clause. SQL Pseudocolumns PL/SQL recognizes the following SQL pseudocolumns. ROWNUM returns a number indicating the order in which a row was selected from a table. SAVEPOINT. set. When you create a sequence. ROWID. you can specify its initial value and an increment. For example.). LEVEL is used with the SELECT CONNECT BY statement to organize rows from a database table into a tree structure. Assume that you have declared empno_seq as a database sequence. SET TRANSACTION establishes a read-only transaction. LEVEL returns the level number of a node in a tree structure. undoes part of a transaction. you must use NEXTVAL to generate a number. you must declare an explicit cursor or use a cursor FOR loop Explicit Cursors 18 . other users cannot see them. which return specific data items: CURRVAL. LEVEL. However. then the following statement inserts a new employee number into the emp table: INSERT INTO emp VALUES (empno_seq. you can select values from a pseudocolumn.. Cursor Management PL/SQL uses two types of cursors: implicit and explicit. or delete values from a pseudocolumn. and ROWNUM. A sequence is a database object that generates sequential numbers. SQL Functions PL/SQL lets you use all the SQL functions including group functions.NEXTVAL. CURRVAL returns the current value in a specified sequence. If a SELECT statement includes an ORDER BY clause. Operators PL/SQL lets you use all the SQL comparison. ROWID returns the rowid (binary address) of a row in a database table. However. For instance. including queries that return only one row. The root is level 1. You specify the direction in which the query walks the tree (down from the root or up from the branches) with the PRIOR operator. ROWNUMs are assigned to the retrieved rows before the sort is done. which summarize entire columns of ORACLE data. for queries that return more than one row. Used with ROLLBACK. you specify a condition that identifies the root of the tree. you cannot insert values into. Until you commit your changes.. update values in. They are called pseudocolumns because they are not actual columns in a table but behave like columns. Before you can reference CURRVAL in a session. ROLLBACK. NEXTVAL. ROLLBACK ends the current transaction and undoes any changes made since the transaction began. COMMIT makes permanent any database changes made during the current transaction. .

depending on how many rows meet your search criteria. When a query returns multiple rows. or multiple rows. . subprogram. the query can reference PL/SQL variables within its scope: DECLARE my_sal emp.sal%TYPE. Rows in the active set are not retrieved when the OPEN statement is executed.job%TYPE. -.. Also. you must declare a cursor before referencing it in other statements. So. END. OPEN c1.]) ] IS where parameter stands for the following syntax: variable_name [IN] datatype [{:= | DEFAULT} value] OPENing the cursor executes the query and identifies the active set. you use three commands to control the cursor: OPEN. which consists of all rows that meet the query search criteria. not a PL/SQL variable. BEGIN . or package by naming it and specifying a query. 19 . it is used only to reference a query. The cursor name is an undeclared identifier. you use the syntax: CURSOR name [ (parameter [.. FETCH. cursor c1 IS SELECT factor*sal FROM emp WHERE job = my_job. parameter. the cursor advances to the next row in the active factor equals 2 LOOP FETCH c1 INTO my_sal.. The formal parameters of a cursor must be IN parameter. as the example below shows.does not affect FETCH END LOOP. The FETCH statement retrieves the rows in the active set one at a time. As the following example shows.The set of rows returned by a query can consist of zero. Each time FETCH is executed. Cursors can take parameters. Any variables in the WHERE clause of the query associated with the cursor are evaluated only when the cursor is OPENed. factor INTEGER := 2.. For cursors declared using the FOR UPDATE clause. When you declare a cursor. there must be a corresponding variable in the INTO list. factor := factor + 1. EXIT WHEN c1%NOTFOUND. To declare formal cursor parameters. A cursor parameter can appear in a query wherever a constant can appear. and CLOSE. . one. For each column value returned by the query associated with the cursor. Forward references are not allowed in PL/SQL. my_job emp. the OPEN statement also locks those rows. You define a cursor in a declarative part of a PL/SQL block. Rather. CLOSE c1. Then.. ename FROM emp WHERE sal > median.. -. their datatypes must be compatible. the FETCH statement retrieves the rows. you can explicitly define a cursor to process the rows. CURSOR c1 (median IN NUMBER) IS SELECT job. you name it and associate it with a specific query.

If the last fetch failed to return a row (because the active set was empty). you can still use cursor attributes to access information about the most recently executed SQL statement. You can use explicit cursor attributes in procedural statements but not in SQL statements. FETCH. no exception is raised. FETCH is expected to fail eventually. •Using %NOTFOUND. %ROWCOUNT. %ROWCOUNT returns a zero. the predefined exception NO_DATA_FOUND is raised whether you check %NOTFOUND on the next line or not. my_empno NUMBER(4). %NOTFOUND evaluates to NULL. %ISOPEN evaluates to FALSE. if FETCH never executes successfully. Implicit Cursor Attributes The SQL cursor has four attributes: %NOTFOUND. •Using %ROWCOUNT. although you cannot use the OPEN. 20 . You can use implicit cursor attributes in procedural statements but not in SQL statements. DELETE. and %ISOPEN.Explicit Cursor Attributes Each cursor that you explicitly define has four attributes: %NOTFOUND. When appended to the cursor name (SQL). Thereafter. The features of %NOTFOUND are similar to those of the explicit cursor attributes but you must bear in mind the following: if a SELECT INTO fails to return a row. UPDATE. When appended to the cursor name. Implicit Cursors ORACLE implicitly opens a cursor to process each SQL statement not associated with an explicitly declared cursor. Instead of coding a NO_DATA_FOUND handler. •Using %FOUND. and %ISOPEN.2). %NOTFOUND evaluates to FALSE. %FOUND evaluates to NULL. otherwise. So. Thereafter. %ROWCOUNT. then use %NOTFOUND to tell which cursors have rows left to fetch. After an explicit cursor is open but before the first fetch. and CLOSE statements to control an implicit cursor. you find out if that exception was raised by checking %NOTFOUND. these attributes let you access useful information about the execution of a multirow query. •Using %ISOPEN. You can open multiple cursors. When you open its cursor. The number is incremented if the latest fetch returned a row. %FOUND. So. DECLARE my_sal NUMBER(7. it returns the number of rows fetched so far. the loop is never exited unless your EXIT WHEN statement is as follows: EXIT WHEN c1%NOTFOUND OR c1%NOTFOUND IS NULL. •Using %NOTFOUND. %NOTFOUND evaluates to TRUE. so when that happens. %FOUND. When a cursor is OPENed. %ROWCOUNT is zeroed. If the last fetch returned a row. %ISOPEN evaluates to TRUE if its cursor is open. Rows are FETCHed from the active set one at a time. these attributes let you access information about the execution of INSERT. the rows that satisfy the associated query are identified and form the active set. The check for %NOTFOUND on the next line would be useless because when NO_DATA_FOUND is raised. it evaluates to TRUE if the last fetch returned a row or to FALSE if no row was returned. Before the first fetch. Before the first fetch. normal execution stops and control transfers to the exception-handling part of the block. %FOUND is the logical opposite of %NOTFOUND. and SELECT INTO statements. In this situation %NOTFOUND is useful in the OTHERS exception handler. PL/SQL lets you refer to the most recent implicit cursor as the ``SQL'' cursor.

These attributes are similar in use to those of explicit cursor attributes. A cursor body must have a SELECT statement and the same RETURN clause as its corresponding cursor specification. However. you compute the total wages paid to employees in that department. That is because group functions such as AVG and SUM always return a value or a null. repeatedly fetches rows of values from the active set into fields in the record. A cursor specification has no SELECT statement because the RETURN clause defines the datatype of the result value.. Furthermore.. CREATE PACKAGE BODY emp_actions AS /* Define cursor body */ CURSOR c1 RETURN emp%ROWTYPE SELECT * FROM emp WHERE sal > 3000. %ROWCOUNT and %ISOPEN... you pass a department number. . A cursor FOR loop implicitly declares its loop index as a record of type %ROWTYPE.. END. -. END emp_action.might raise NO_DATA_FOUND EXCEPTION WHEN OTHERS THEN IF SQL%NOTFOUND THEN -. You can pass parameters to a cursor used in a cursor FOR loop. Then.BEGIN .check for 'no data found' .. . the number and datatypes of select-list items in the SELECT statement must match the RETURN clause. END IF.. Also. Cursor FOR Loops You can use a cursor FOR loop to simplify coding. Packaged Cursors You can separate a cursor specification from its body for placement in a package by using the RETURN clause: CREATE PACKAGE emp_actions AS /* Declare cursor specification */ CURSOR c1 RETURN emp%ROWTYPE .. 21 . you can change the cursor body without changing the cursor specification. In the following example. then closes the cursor when all rows have been processed or when you exit the loop. you determine how many employees have salaries higher than $2000 and how many have commissions larger than their salaries. opens a cursor. •Using %FOUND... This way. a SELECT INTO that calls a SQL group function never raises the exception NO_DATA_FOUND. SELECT sal INTO my_sal FROM emp WHERE empno = my_empno. END emp_actions.

you can use the FOR UPDATE OF clause to confine row locking to particular tables. LOCK TABLE emp IN ROW SHARE MODE NOWAIT. •Using a LOCK TABLE statement lets you lock entire database tables in a specified lock mode so that you can share or deny access to tables while maintaining their integrity. DECLARE CURSOR c1 IS SELECT ename. COMMIT.DECLARE CURSOR emp_cursor(dnum NUMBER) IS SELECT sal. you must use the FOR UPDATE clause to acquire exclusive row locks. However. total_wages := total_wages + emp_record. END IF. high_paid NUMBER(4) := 0. The rows are unlocked when you COMMIT the transaction. as the following example shows. Table locks are released when your transaction issues a COMMIT or ROLLBACK. INSERT INTO temp VALUES (high_paid. END.deptno AND job = 'MANAGER' FOR UPDATE OF sal. The FOR UPDATE clause indicates that rows will be updated or deleted and locks all rows in the active set. comm FROM emp WHERE deptno = dnum. higher_comm NUMBER(4) := 0. •Using FOR UPDATE. If present. Overriding Default Locking By default ORACLE locks data structures for you automatically.comm.sal + emp_record.comm := NVL(emp_record. BEGIN /* the number of iterations will equal the number of rows * * returned by emp_cursor */ FOR emp_record IN emp_cursor(20) LOOP emp_record. When querying multiple tables. END LOOP. IF emp_record. you cannot FETCH from a FOR UPDATE cursor after a COMMIT.comm. So. you can request specific data locks on rows or tables when it is to your advantage to override default locking.0). dept WHERE emp. 'Total Wages: ' || TO_CHAR(total_wages)). higher_comm.deptno = dept. sal FROM emp WHERE job = 'SALESMAN' AND comm > sal FOR UPDATE.2) := 0. 22 . total_wages NUMBER(11. the FOR UPDATE clause must appear at the end of the cursor declaration. When declaring a cursor that will be referenced in the WHERE CURRENT OF clause of an UPDATE or DELETE statement. dname FROM emp. DECLARE CURSOR c1 IS SELECT empno.sal > 2000 THEN high_paid := high_paid + 1. All rows in the active set are locked when you OPEN the cursor.

The FOR EACH ROW option specifies that the trigger fires once per row.part_no. By default.table FOR EACH ROW /* trigger constraint */ WHEN (new. it is rolled back. For the trigger to fire. the database trigger fires and an anonymous PL/SQL block performs the action. an optional trigger constraint. the Boolean expression in the WHEN clause must evaluate to TRUE. The name in the ON clause identifies the database table associated with the database trigger.reorder_qty. Except for transaction control statements such as COMMIT and ROLLBACK. you can reference :new and :old values of changing rows. So. In this case.END block.reorderable = 'T') BEGIN /* trigger action */ IF :new. The triggering event specifies the SQL data manipulation statement that affects the table. END IF. The example below illustrates transparent event logging. you can use database triggers to •audit data modification •log events transparently •enforce complex business rules •derive column values automatically •implement complex security authorizations •maintain replicate tables You can associate up to 12 database triggers with a give table. Database triggers fire with the privileges of the owner.reorder_point THEN INSERT INTO pending_orders VALUES (:new. database triggers are invoked implicitly. So.Database Triggers A database trigger is a stored PL/SQL program unit associated with a specific database table. a database trigger fires once per table.. however. not the current user. can appear in the BEGIN. and a trigger action. 23 . The keyword AFTER specifies that the database trigger fires after the update is done. The prefix :new is a correlation name that refers to the newly updated column value. the statement is UPDATE. unlike subprograms. :new. including subprogram calls. A database trigger can also have DECLARE and EXCEPTION sections. any SQL or procedural statement. the owner must have appropriate access to all objects referenced by the trigger action. You can use the REFERENCING clause (not shown) to replace :new and :old with other correlation names. END. When the event occurs. which must be invoked explicitly.. SYSDATE). A database trigger has three parts: a triggering event. CREATE TRIGGER reorder /* triggering event */ AFTER UPDATE OF qty_on_hand ON inventory -. Within a database trigger. Among other things. ORACLE executes (fires) the database trigger automatically whenever a given SQL operation affects the table. If the trigger statement fails.qty_on_hand < :new. The database trigger named reorder ensures that a part is reordered when its quantity on hand drops below the reorder point. Notice that the colon is not used in the WHEN clause.

raise an exception. Exceptions can be internally defined (by the runtime system) or user-defined. the current block stops executing and the enclosing block resumes with the next statement. To handle raised exceptions.sal) THEN raise_application_error(-20325.sal > 1. ELSIF (:new. When an error occurs. If there is no enclosing block. 'Increase exceeds 10%'). User-defined exceptions must be raised explicitly by RAISE statements. BEGIN /* Get salary range for a given job from table sals. You can define exceptions of your own in the declarative part of any PL/SQL block. job ON emp FOR EACH ROW WHEN (new. maxsal NUMBER. */ SELECT losal. or package. increase is negative.sal < minsal OR :new. see ``ORACLE7 Server Application Developer's Guide''.job.sal) THEN raise_application_error(-20320. subprogram. you might define an exception named insufficient_funds to flag an overdrawn bank accounts.The next example shows that the trigger action can include calls to the built-in ORACLE procedure raise_application_error.sal < :old. 24 . For a full discussion of database triggers. you write separate routines called exception handlers. Internal exceptions are raised implicitly (automatically) by the runtime system. More information on built-in procedures is provided later in this chapter. That is. an exception is raised. Error Handling Overview In PL/SQL a warning or error condition is called an exception. /* If salary is out of range. For example. user-defined exceptions must be given names. */ IF (:new. normal execution stops and control transfers to the exception handling part of your PL/SQL block or subprogram. END IF: END. Examples of internally defined exceptions include division by zero and out of memory. Some common internal exceptions have predefined names.1 * :old. which can also raise predefined exceptions. Unlike internal exceptions. * * or increase exceeds 10%.job != 'PRESIDENT') DECLARE minsal NUMBER. maxsal FROM sals WHERE job = :new. 'Negative increase'). such as ZERO_DIVIDE and STORAGE_ERROR. After an exception handler runs. 'Salary out of range').sal > maxsal) THEN raise_application_error(-20225. which lets you issue user-defined error messages: CREATE TRIGGER check_salary BEFORE INSERT OR UPDATE OF sal. ELSIF (:new. The other internal exceptions can be given names. control returns to the host environment. hisal INTO minsal.

•PROGRAM_ERROR is raised if PL/SQL has an internal problem. you can be sure it will be handled. •NO_DATA_FOUND is raised if a SELECT INTO statement returns no rows or if you reference an uninitialized row in a PL/SQL table. which defines the PL/SQL environment. So. •LOGIN_DENIED is raised if you try logging on to ORACLE with an invalid username/password. For example. 25 . PL/SQL predefines some common ORACLE errors as exceptions. •TIMEOUT_ON_RESOURCE is raised if a timeout occurs while ORACLE is waiting for a resource. Without exception handling. So. •DUP_VAL_ON_INDEX is raised if you try to store duplicate values in a database column that is constrained by a unique index. If the exception is ever raised in that block (or any sub-block).Advantages of Exceptions Using exceptions for error handling has several advantages. but exceptions must be handled by name. You need not worry about checking for an error at every point it might occur. •STORAGE_ERROR is raised if PL/SQL runs out of memory or if memory is corrupted. if you try to CLOSE an unopened cursor. Every ORACLE error has a number. •NOT_LOGGED_ON is raised if your PL/SQL program issues a database call without being logged on to ORACLE. •INVALID_NUMBER is raised in a SQL statement if the conversion of a character string to a number fails. Predefined Exceptions An internal exception is raised explicitly whenever your PL/SQL program violates an ORACLE rule or exceeds a system-dependent limit. the predefined exception NO_DATA_FOUND is raised if a SELECT INTO statement returns no rows. you must check for execution errors. every time you issue a command. PL/SQL declares predefined exceptions globally in package STANDARD. Exceptions also improve reliability. You can write handlers for predefined exceptions using the names shown below: Exception Name ORACLE Error SQLCODE Value CURSOR_ALREADY OPEN ORA-06511 -6511 DUP_VAL_ON_INDEX ORA-00001 -1 INVALID_CURSOR ORA-01001 -1001 INVALID_NUMBER ORA-01722 -1722 LOGIN_DENIED ORA-01017 -1017 NO_DATA_FOUND ORA-01403 +100 NOT_LOGGED_ON ORA-01012 -1012 PROGRAM_ERROR ORA-06501 -6501 STORAGE_ERROR ORA-06500 -6500 TIMEOUT_ON_RESOURCE ORA-00051 -51 TOO_MANY_ROWS ORA-01422 -1422 VALUE_ERROR ORA-06502 -6502 ZERO_DIVIDE ORA-01476 -1476 •CURSOR_ALREADY_OPEN is raised if you try to OPEN an already open cursor. you need not declare them yourself. Just add an exception handler to your PL/SQL block. •INVALID_CURSOR is raised if you try an illegal cursor operation. For example.

•ZERO_DIVIDE is raised if you try to divide a number by zero. the predefined pragma EXCEPTION_INIT tells the compiler to associate an exception name with an ORACLE error number. That allows you to refer to any internal exception by name and to write a specific handler for it. ORACLE_error_number). User-defined Exceptions PL/SQL lets you define exceptions of your own. an exception is an error condition. Unlike variables. But remember. You declare an exception by introducing its name. EXCEPTION WHEN insufficient_privileges THEN -.. subprogram. •Using EXCEPTION_INIT. or constraint error occurs. where exception_name is the name of a previously declared exception. or package using the syntax PRAGMA EXCEPTION_INIT(exception_name. -----------------------------------------------------.•TOO_MANY_ROWS is raised if a SELECT INTO statement returns more than one row. truncation. acct_num NUMBER(5). END. followed by the keyword EXCEPTION.handle the error . -1031).you try to UPDATE a table for which you have only -. subprogram. BEGIN Exceptions and variable declarations are similar. Unlike predefined exceptions.ORACLE returns error number -1031 if.. You code the pragma EXCEPTION_INIT in the declarative part of a PL/SQL block.. or package. PRAGMA EXCEPTION_INIT(insufficient_privileges. Exceptions can be declared only in the declarative part of a PL/SQL block. However. for example -. In PL/SQL. To handle unnamed internal exceptions. DECLARE past_due EXCEPTION. which can be thought of as a parenthetical remark to the compiler.SELECT privileges ----------------------------------------------------BEGIN . conversion. •VALUE_ERROR is raised if an arithmetic. 26 . A pragma is a compiler directive. user-defined exceptions must be declared and must be raised explicitly by RAISE statements. the same scope rules apply to variables and exceptions. DECLARE insufficient_privileges EXCEPTION. you must use the OTHERS handler or the pragma EXCEPTION_INIT.. exceptions cannot appear in assignment statements or SQL statements. not an object.

IF number_on_hand < 1 THEN RAISE out_of_stock. it can use EXCEPTION_INIT to map specific error numbers returned by raise_application_error to exceptions of its own.. error_message). This package includes a procedure named raise_application_error.•Using raise_application_error.. You can code a RAISE statement for a given exception anywhere within the scope of that exception. rolls back any database changes it made. null_salary EXCEPTION. as are user-defined exceptions that you have associated with an ORACLE error number using EXCEPTION_INIT. •Using RAISE statement. BEGIN . 'Salary is missing'). A package named DBMS_STANDARD (part of the Procedural Database Extention) provides language facilities that help your application interact with ORACLE. BEGIN SELECT sal INTO current_salary FROM emp WHERE empno = emp_id. When called. PL/SQL blocks and subprograms should RAISE an exception only when an error makes it undesirable or impossible to finish processing. DECLARE out_of_stock EXCEPTION. END IF. raise_application_error ends a subprogram. which it can process using the error-reporting functions SQLCODE and SQLERRM in an OTHERS handler.-20999 and error_message is a character string up to 512 bytes in length. other user-defined exceptions must be raised explicitly by RAISE statements. -20101). where error_number is a negative integer in the range -20000. increase NUMBER) IS current_salary NUMBER. and returns a user-defined error message to the application.. ELSE UPDATE emp SET sal = current_salary + increase WHERE empno = emp_id.. PROCEDURE raise_salary (emp_id NUMBER.. The calling application gets a PL/SQL exception. IF current_salary is NULL THEN raise_application_error(-20101. An application can call raise_application_error only from an executing stored subprogram. END raise_salary.. The calling syntax is raise_application_error(error_number. . DECLARE . PRAGMA EXCEPTION_INIT(null_salary.. How Exceptions Are Raised Internal exceptions are raised implicitly by the runtime system. number_on_hand NUMBER(4). However. 27 . which lets you issue user-defined error messages from a stored subprogram or database trigger. Furthermore.

------------.. which is allowed only in an exception handler. Use of the OTHERS handler guarantees that no exception will go unhandled. The optional OTHERS exception handler. EXCEPTION WHEN out_of_balance THEN -.. it must appear by itself. separating them by the keyword OR.. You can also raise a predefined exception explicitly: RAISE INVALID_NUMBER. normal execution of your PL/SQL block or subprogram stops and control transfers to its exception-handling part and control does NOT return to where the exception was raised.. that is. The keyword OTHERS cannot appear in the list of exception names. That way.reraise the current exception END. END. which is always the last handler in a block or subprogram. If you want two or more exceptions to execute the same sequence of statements. as shown below DECLARE out_of_balance EXCEPTION. list the exception names in the WHEN clause. acts as the handler for all exceptions not named specifically. handle it locally. you can use an exception handler written for the predefined exception to process other errors. you cannot resume processing where you left off.handle the error differently ...END IF. Omitting the exception name in a RAISE statement. .handle the error END. you want to reraise an exception. THEN RAISE out_of_balance. ------------. reraises the current exception. -. then pass it to an enclosing block. To reraise an exception.. -. EXCEPTION WHEN out_of_stock THEN -.raise the exception END IF. BEGIN ..end of sub-block ----------------------------EXCEPTION WHEN out_of_balance THEN . Sometimes. In other words. IF . Handling Raised Exceptions When an exception is raised...beginning of sub-block ----------------------BEGIN . .handle the error RAISE... 28 . simply place a RAISE statement in the local handler.

. The string function SUBSTR ensures that a VALUE_ERROR exception (for truncation) is not raised when you assign the value of SQLERRM to err_msg.handle the error differently END.. then use the variables in the SQL statement. and an optional exception-handling part. • Using SQLCODE and SQLERRM. 100). Subprograms Subprograms are named PL/SQL blocks that can take parameters and be invoked. Instead.. err_msg := SUBSTR(SQLERRM..handle the error differently WHEN . [. you use a procedure to perform an action and a function to compute a value. 1.]) ] IS [local declarations] BEGIN executable statements [EXCEPTION] exception-handlers] END [name].. DECLARE err_num NUMBER. parameter. You write procedures using the syntax PROCEDURE name [ (parameter. where parameter stands for the following syntax var_name [IN | OUT | IN OUT] datatype [{:= | DEFAULT} value] 29 . INSERT INTO errors VALUES (err_num. EXCEPTION WHEN . SQLCODE and SQLERRM are especially useful in the OTHERS exception handler because they tell you which internal exception was raised. you must assign their values to local variables.. Like unnamed or anonymous PL/SQL blocks. You cannot use SQLCODE and SQLERRM directly in a SQL statement. OR . Procedures A procedure is a subprogram that performs a specific action.. WHEN OTHERS THEN . PL/SQL has two types of subprograms called procedures and functions. END. BEGIN . err_msg)... Generally.handle the error differently . THEN ... WHEN OTHERS THEN err_num := SQLCODE. err_msg CHAR(100). subprograms have a declarative part. .. THEN . an executable part....

(name CHAR(20) ) IS -. where parameter stands for the following syntax var_name [IN | OUT | IN OUT] datatype [{:= | DEFAULT} value] The function body begins with the keyword IS and ends with the keyword RETURN clause. [. except that functions have a RETURN clause. increase REAL) IS current_salary REAL... END raise_salary. ESLE UPDATE emp SET sal = sal + increase WHERE empno = emp_id.Unlike the datatype specifier in a variable declaration. parameter. 'No such number'). but not in SQL statements. Calls to user-defined functions can appear in procedural statements.]) ] RETURN datatype IS [local declarations] BEGIN executable statements [EXCEPTION exception-handlers] END [name]. The procedure body begins with the keyword IS and ends with the keyword END followed by an optional procedure name. which specifies the datatype of the result value. salary_missing EXCEPTION. 'Salary is null'). Functions A function is a subprogram that computes a value. 30 . should be CHAR The procedure specification begins with the keyword PROCEDURE and ends with the procedure name or a parameter list. IF current_salary IS NULL THEN RAISE salary_missing. BEGIN SELECT sal INTO current_salary FROM emp WHERE empno = emp_id. END IF.. Functions and procedure are structured alike.illegal. [EXCEPTION WHEN NO_DATA_FOUND THEN INSERT INTO emp_audit VALUES (emp_id. PROCEDURE . . the datatype specifier in a parameter declaration must be unconstrained.. PROCEDURE raise_salary (emp_id INTEGER. WHEN salary_missing THEN INSERT INTO emp_audit VALUES (emp_id. You write functions using the syntax FUNCTION name [ (parameter.

hisal INTO min_sal. -. END sal_ok.forward declaration /* Define subprogram in alphabetical order */ PROCEDURE award_bonus (. none of which need be the last lexical statement.). A subprogram can contain several RETURN statements.. However. Otherwise. RETURN Statement The RETURN statement immediatedly completes the execution of a subprogram and returns control to the caller. You can place the subprogram body anywhere after the forward declaration. Although the formal parameter list appears in the forward declaration. a RETURN statement cannot contain an expression. Forward Declarations PL/SQL requires that you declare an identifier before using it..) IS BEGIN . Execution then resumes with the statement following the subprogram call. you must declare a subprogram before calling it. in functions. max_sal REAL. .FUNCTION sal_ok (salary REAL.. or package.. In procedures. 31 . a RETURN statement must contain an expression.. subprogram. which is evaluated when the RETURN statement is reached. DECLARE PROCEDURE calc_rating (. PROCEDURE calc_rating (. A function must contain at least one RETURN statement. END. A forward declaration consists of a subprogram specification terminated by a semicolon. it must also appear in the subprogram body. RETURN (salary >= min_sal) AND (salary <= max_sal). title REAL) RETURN BOOLEAN IS min_sal REAL. max_sal FROM sals WHERE job = title.. PL/SQL solves the problem of subprograms used before they are declared by providing a special subprogram declaration called forward declaration.).. . Therefore.. BEGIN SELECT losal. but they must appear in the same block.... The statement simply returns control to the caller before the normal end of the procedure is reached. END. PL/SQL raises the predefined exception PROGRAM_ERROR at run time.) IS BEGIN calc_rating(..

Thus. The actual parameter that corresponds to an IN OUT formal parameter must be a variable. The three parameter modes. Inside the subprogram. can be used with any subprogram. and the subprogram bodies go in the package body. raise_salary(increase => inc. For example. Unlike OUT and IN OUT parameters. Therefore. Parameter Modes You use parameter modes to define the behavior of formal parameters. The variables or expressions referenced in the parameter list of a subprogram call are actual parameters.Packaged Subprograms Forward declarations also let you group logically related subprograms in a package. an IN OUT parameter acts like an initialized variable. An OUT actual parameter can (but need not) have a value before the subprogram is called. inc). if you exit with an unhandled exception. IN (the default). Before exiting a subprogram. an OUT parameter acts like an uninitialized variable. The actual parameter that corresponds to an OUT formal parameter must be a variable. you can write the actual parameters using either positional or named notation. 32 . avoid using the OUT and IN OUT modes with functions. emp_id => emp) raise_salary(emp. it cannot be a constant or expression. it cannot be assigned a value. Inside the subprogram. The subprogram specifications go in the package specification. The actual parameter and its corresponding formal parameter must belong to compatible datatypes. and IN OUT. an IN parameter can be initialized to default values. the values of corresponding actual parameters are indeterminate. an IN parameter acts like a constant. Actual versus Formal Parameters Subprograms pass information using parameters. the value is lost when you call the subprogram. However. the call to the procedure raise_salary can be made as follows: raise_salary(emp. However. PL/SQL assigns values to the actual parameters. The variables declared in a subprogram specification and referenced in the subprogram body are formal parameters. Therefore. Inside the subprogram. increase => inc) The first procedure call uses positional notation. Otherwise. However. •an IN parameter lets you pass values to the subprogram being called. its value cannot be assigned to another variable or reassigned to itself. OUT. and the third uses mixed notation. When calling a subprogram. the second uses named notation. •an OUT parameter lets you return values to the caller of a subprogram. explicitly assign values to all OUT formal parameters. it cannot be a constant or expression. •an IN OUT parameter lets you pass initial values to the subprogram being called and return updated values to the caller. PL/SQL does not assign values to the actual parameters. packages allow you to hide implementation details. If you exit successfully. where they are invisible to applications.

another stored subprogram. You cannot overload the names of stand-alone subprograms. You cannot overload two subprograms if their formal parameters differ only in name or parameter mode. subprogram. ready to be executed. Finally. Because the processing in these two procedures is the same.. You can place the two overloaded initialize procedures in the same block.0. n INTEGER) IS BEGIN FOR i IN 1. DECLARE TYPE DateTabTyp IS TABLE OF DATE INDEX BY BINARY_INTEGER. and tighter security. order.. END LOOP. or datatype family. users can call the procedure. END initialize.n LOOP tab(i) := 0. For example you can grant users EXECUTE access to a stored procedure that updates the emp table. PL/SQL determines which of the two procedures is being called by checking their formal parameters. memory savings.. you can use the same name for several different subprograms as long as their formal parameters differ in number. The specification is the 33 .. That is. objects. an OCI application. Stored subprograms offer higher productivity. PACKAGES A package is a database object that groups logically related PL/SQL types. Stored subprograms can help enforce data security. a specification and a body. That way. Packages usually have two parts. you cannot overload two functions that differ only in return type even if the types are in different families. PROCEDURE initialize (tab OUT DateTabTyp. or package. END initialize. application integrity. better performance. an ORACLE Precompiler application. .n LOOP tab(i) := SYSDATE. sal_tab RealTabTyp. although sometimes the body is unnecessary. but not grant them access to the table itself. TYPE RealTabTyp IS TABLE OF REAL INDEX BY BINARY_INTEGER. it is logical to give them the same name. Stored Subprograms Subprograms can be compiled separately and stored permanently in an ORACLE database.Overloading PL/SQL lets you overload subprogram names. You might write the following procedures to initialize the PL/SQL tables named initialize for hiredate_tab and sal_tab. PROCEDURE initialize (tab OUT RealTabTyp. You can restrict users to specific database operations by granting access only through subprograms. and subprograms. END LOOP. n INTEGER) IS BEGIN FOR i IN 1. or an ORACLE tool such as SQL*Plus. You can call stored subprograms from a database trigger. You cannot overload two subprograms if their formal parameters differ only in datatype and the different datatypes are in the same family (REAL and INTEGER). hiredate_tab DateTabTyp. but cannot arbitrarily manipulate table data.

SYSDATE.specification TYPE EmpRecTyp is RECORD (emp_id INTEGER. deptno NUMBER ). job. it declares the types.subprogram bodies [BEGIN -. deptno NUMBER ). and subprograms available for use. and so implements the specification. and better performance. Packages are created interactively with SQL*Plus using the CREATE PACKAGE and CREATE PACKAGE BODY commands. the format of a package is similar to that of a subprogram: PACKAGE name IS -. sal NUMBER. deptno ). variables. Still. or nested. information hiding. mgr.public type and object declarations -. ename.interface to your application. cursors. END hire_employee.NEXTVAL. END fire_employee. 34 .body (hidden part) -. a record type. easier application design. job CHAR. mgr NUMBER. salary REAL). END emp_actions. END emp_actions. comm. Unlike subprograms.specification (visible part) -. constants. exceptions. In the following example. PACKAGE BODY name IS -.subprogram specifications END [name}. job CHAR. added functionality.body CURSOR desc_salary (emp_id NUMBER) RETURN EmpRecTyp IS SELECT empno. passed parameters. PROCEDURE fire_employee (emp_id NUMBER) IS BEGIN DELETE FROM emp WHERE empno = emp_id. PROCEDURE hire_employee (ename CHAR. CURSOR desc_salary (emp_id NUMBER) RETURN EmpRecTyp. and two employment procedures are packaged: CREATE PACKAGE emp_actions AS -. The body fully defines cursors and subprograms.initialization statements] END [name]. Packages offer several advantages: modularity. a cursor.private type and object declarations -. sal FROM emp ORDER BY sal DESC. PROCEDURE fire_employee (emp_id NUMBER). sal. CREATE PACKAGE BODY emp_actions AS -. comm NUMBER. comm NUMBER. PROCEDURE hire_employee (ename CHAR. BEGIN INSERT INTO emp VALUES (empno_seq. sal NUMBER. packages cannot be called. mgr NUMBER.

So. the declarative part of a package body can contain subprogram bodies. the first time you reference the package. The scope of these declarations is local to your database schema and global to the package. As a result. Guidelines When writing packages. Avoid writing packages that duplicate some feature already provided by ORACLE. However. variables. you use dot notation as follows: package_name. changes to a package specification require ORACLE to recompile every stored subprogram that references the package. if a specification declares only types. keep them as general as possible so they can be reused in future applications.The Package Specification The package specification contains public declarations. and subprograms declared within a package specification. Place in a specification only the types. So.object_name package_name. and subprograms that must be visible to users of the package. a package cannot be called or passed parameters. The initialization part of a package plays a minor role because.type_name package_name. The specification lists the package resources available to applications. Package specifications reflect the design of your application.subprogram_name The Package Body The package body implements the package specification. unlike subprograms. the initialization part of a package is run only once. the declared types and objects are inaccessible except from within the package body. Unlike a package specification. objects. The scope of these declarations is local to the package body. Only subprograms and cursors have an underlying implementation or definition. constants. objects. To reference the types. That is. define them before the package bodies. the package body is unnecessary. To reduce the need for recompiling when code is changed. Keep in mind that subprograms defined in a package body are accessible outside the package only if their specification also appear in the package specification. place as few items as possible in a package specification. Therefore. Changes to a package body do not require ORACLE to recompile dependent procedures. the package body contains the definition of every cursor and subprogram declared in the package specification. 35 . The package body can also contain private declarations. and exceptions. Following the declarative part of a package body is the optional initialization part. All information your application needs to use the resources is in the specification. which define types and objects necessary for the internal workings of the package. which typically holds statements that initialize some of the variables previously declared in the package.

Sign up to vote on this title
UsefulNot useful