PL/SQL Pl/SQL woks both in the Oracle Sever(through stored procedures, stored functions, database triggers and

packages), and in the Oracle Development Environment(Oracle Forms, Oracle Reports, and Oracle Graphics) It supports SQL Data types. PL SQL bridges the gap and the need for procedural programming capabilities. Benefits of PL/SQL : Improved performance : It is used to group SQl statements together within a single block and to send the entire block to the server in a single call, thereby reducing the network traffic. Modularised program Development : Group logically related statements within blocks. Nest sub-blocks inside larger blocks to build a powerful program Break down complex problems into a set of manageable, well-defined , logical modules Place reusable PL/SQL code in libraries to be shared between Oracle applications or store it in an Oracle server to make it available to any userapplication. Portability : PL/SQL programs can run anywhere the Oracle server is installed, you do not need to tailor them to each new environment. Identifiers : It allows you to declare variables, cursors, constants, and exceptions and then use them in SQL and Procedural statements. It allows to declare variable belonging to scalar, reference, composite and LOB data types Declare variable based on the columns in the tables.

Procedural language Control Structures : Execute a sequence of statements conditionally Execute a sequence of statements iteratively in a loop Process the individual rows returned by a multi-row query with an explicit cursors. Error Handling : Process Oracle-server errors with exception handling routines Declare user-defined error conditions and process them with exception-handling routines Structure of a PL/SQL Block Declare(optional) Contains all the variables, constants, cursors and user-defined exceptions that will be used in the executable section Begin(Mandatory)-----Executable section Contains SQL statements to manipulate data in the database and PL/SQl statements to manipulate data in the data-block Exception(Optional) Contains actions to be performed when errors and abnormal conditions arise in the executable section End; set serveroutput on for dbms_output.put_line to give output in SQL

declare vname students.studname%type; vtotal; begin select studname into vname from students where rollno=1; select total into vtotal from students where rollno=1; dbms_output.put_line('Name of Student is :'||vname); dbms_output.put_line('Total of Student is :'||vtotal); end; /

PL/SQL Block Types Anonymous Blocks: These are unnamed blocks. They are declared in an application where they need to be executed and are passed to the Server for execution at run-time. Example : Triggers in Oracle Developer consists of such blocks [Declare] Begin [Exception] End; Sub-Programs : These are named PL/SQL blocks that can accept parameters and can be invoked as and when required. They are declared as Procedures or Functions. Generally use procedures to perform an action and a function to compute and return a value. Procedure name is Begin --statements [Exception] End; Function name return datatype Is Begin --statements return value; [Exception] End;

Declaring PL/SQl variables Declare Birthdate date. Example . Type type_name IS RECORD ( field declaration. Deptno number(2) NOT NULL : =10. NESTED TABLE and VARRAY. RECORD: A record is a group of related data items stored as fields. PL/SQL also supports Boolean datatype Character. variable type_name. They are of 4 types : TABLE. salary. Instead of hardcoding the data type and size of a variable.2). TRUE . allows groups of fields to be defined and manipulated in PL/SQL blocks. Must contain one or more components of any scalar type.). This data is dissimilar in type but logically related. each with it’s own name and data type. vvgrade vgrade %type:=10. Also known as Collections. Boolean data types(only stores NULL. Location varchar2(20) : = ‘Mumbai’. FALSE) vflag Boolean. RECORD. Numeric Date and Boolean types of data types. you have different kinds of data about an employee like name.salary%type vgrade number(7. you can use the %type attribute to declare a variable according to another previously declared variable or a column of a table. vvflag Boolean :=TRUE 2) Composite Composite data types such as records. Example : vsalary employees. The %type attribute. They have internal components that can be handled and manipulated individually. field declaration. hire date. Salary constant number : = 10000 PL/SQL variables 1) Scalar These are the data types that correspond to the data types of columns in tables. …. .

Type emp_data IS RECORD (first_name varchar2(10). last_name varchar2(10)).%rowtype INDEX BY BINARY_INTEGER. To reference or initialize an individual field : Record_name. identifier type_name. which stores the INDEX BY Table elements.column%type/table. emp_record emp_data. The number and data types of the underlying database columns need not be known. They use a primary key to provide you with array-like access to rows. Emp_record. Declaring Records with %rowtype The %rowtype attribute is used to declare a record based on a collection of columns in a database table or view Example : Declare Emp_record employees%rowtype. An INDEX BY Table : Is similar to an array Must contain 2 components A Primary Key of data type Binary_Integer that indexes the INDEX BY TABLE A Column of a scalar or record data type. Can increase dynamically because it is unconstrained. TABLE : Objects of TABLE type are called INDEX By TABLES.first_name:=’Ramesh’. . Type type_name is Table of column_type/variable %type/table.field_name. The number and the data types of the underlying database column may change at run time. This attribute is useful when retrieving a row into variables with the Select * From tablename.

Birthdate_table(1) :=sysdate-10.returns the first and last index numbers Prior(n).removes all elements from PL/SQL table DELETE(n)-removes the nth element from the PLSQL table. My_emp_table emp_table_type. Birthdate_table birthdate_table_type. LAST. Example : Set server output on. Type birthdate_table_type IS TABLE OF DATE INDEX BY BINARY_INTEGER. Ename_table ename_table_type. it contains no keys or no values.Returns the index number that succeeds the index n in a table TRIM-removes oen element from the end of the PL SQL Table TRIM(n)-removes n elements from the end of the PLSQL Table DELETE. Type ename_table_type IS TABLE OF employees.n)-removes all elements in the range m…n from a PL SQL table. An explicit executable statement is required to initialize (populate) the Index By Table.Returns the index number that preceeds the index n in a table Next(n). Initially such a table is not populated. Declare Type ename_table_type IS TABLE OF employees%rowtype INDEX BY BINARY_INTEGER.first_name%type INDEX BY BINARY_INTEGER. Following methods are used by the INDEX BY Tables : Exists(n)-returns TRUE if the nth element exists Count-returns number of elements that a PL/SQL table currently contains FIRST. Ename_table(1) :=’Ramesh’. .Type ename_table_type IS TABLE OF employees. DELETE(m.first_name%type INDEX BY BINARY_INTEGER. Ename_table ename_table_type.

Conditional Constructs IF Statement If-then. Begin For i in 100 . Statement 4. If <condition(s)> then Statement 1.first . my_emp_table. For i in my_emp_table.(Not a part of the syllabus) 4) LOBs Also called locators that specify the location of large objects(such as graphic images that are stored out of line.V_count number(3):=104. v_count Loop Select * into my_emp_table(i) from employees where employee_id=i. . End if. Statement 2. End.first_name). If-then-else-end if. Else(optional) Statement 3..put_line(my_emp_table(i). End loop.end if.last Loop Dbms_output. If <condition(s)> then Statement 1. End if. Statement 2. End loop. / 3) Reference These are the pointers to other program items..

if total of Rollno=1 is more than 275. begin select studname into vname from students where rollno=1. vtotal students.put_line(Vname||' is an average student'). Elsif <condition(s)> then Statement 5.studname%type. Else(optional) Statement 7. end if. begin select studname into vname from students where rollno=1. vtotal students. End if. If <condition(s)> then Statement 1. select total into vtotal from students where rollno=1. and "poor student" if total less than 250 declare vname students. Statement 4. "Average student" if total between 250 and <275. else display "Average student" declare vname Elsif <condition(s)> then Statement 3. Statement 8.put_line(Vname||' is a very good student'). Statement 2. / PL/SQL Block to display "Very Good Student". . else dbms_output. select total into vtotal from students where rollno=1.studname%type. if vtotal>=250 then dbms_output.If-then-elsif-elsif-else-end if. Statement 6. if total of Rollno=1 is more than 275. PL/SQL Block to display "Very Good Student".

Begin Vappraisal := CASE vgrade When ‘A’ then ‘Excellent’ When ‘B’ then ‘Very Good’ When ‘C’ then ‘Good’ Else ‘No such grade’ End. Declare vgrade char(1):=upper(‘&p_grade).put_line(Vname||' is a very good student').if vtotal>=275 then dbms_output. / Nesting of Ifs allowed as per situation. Set serveroutput on. CASE Expressions Case selector When expression1 then result1 When expression2 then result2 When expression3 then result3 When expressionN then resultN Else resultN+1(optional) End.put_line(Vname||' is an average student').put_line(‘Grade ‘||vgrade||’ Appraisal ‘ || vappraisal). / . elsif vtotal>=250 and vtotal<275 then dbms_output. end if. End.put_line(Vname||' is a poor student'). else dbms_output. vappraisal varchar2(20). end. Dbms_output.

/ Print odd and even numbers from 1 to 20 and their count declare a number:=0.10 loop dbms_output.. end loop Numbers 1 to 10 in order declare num number(2). dbms_output. end. end loop. dbms_output.put_line('There are '||a||' even numbers'). / . statement2. end loop. else dbms_output. begin for num in reverse 1.put_line('There are '||b||' odd numbers'). end loop..2)=0 then dbms_output..10 loop dbms_output. / Numbers 1 to 10 in reverse order declare num number(2)..20 loop if mod(x. begin For x in 1. begin for num in 1. b number:=0. end.put_line('Number '||x||' is Odd'). end if.put_line('number '|| num). end.put_line('number '|| num). a:=a+1.put_line('Number '||x||' is Even').LOOPS 1) For <variable> in [reverse] lowvalue. b:=b+1.highvalue loop statement1.

20...put_line(num). exit when <condition>. statement2. print 10. end. / .. end loop.10.. end loop.. begin loop dbms_output. num:=num+5. / loop statement1. statement2.50 declare num number:=5..30..15. print 5. end loop.20. end loop.100 declare num number:=10. num:=num+10..put_line(num). end. exit when num>50.While <condition> loop statement1. begin while num<=100 loop dbms_output.

Following are the steps followed for handling explicit cursors : 1)declare Here we declare the cursor by naming it and define the structure of the query to be performed within it. Exit When End loop. 2)Open This statement executes the query. Close Cursor_name . Loop Fetch cursor_name into variable1. variable 2. The row returned by the query are called the active set and are now available for fetching Open Cursor_name. including queries that return only one row. Explicit Cursors Used to process each row returned by a multiple-row Select statement. Declare Cursor cursor_name is Select ……. There are 2 types of cursors : IMPLICIT These are declaredc by PLSQL implicitly for all DML and PLSQL Select statements. and manipulated in the block’s executable section. explicit cursors are declared and named by the programmer.CURSORS Cursors are names given to private SQL work areas created by the Oracle server to execute SQL statements and to store the processing information. EXPLICIT For queries that return more than one row. 3)Fetch and process Here you actually fetch the rows into variable if required and carry out all the business logic or processing. 4)close It releases the active . It is now possible to reopen the cursor to re-establis a fresh active set.

Evaluates to TRUE if the most recent fetch does not return a row %found. total of all the students declare cursor cstudent is Select Rollno.studname%type. vname. / Here. dbms_output. vtotal. "notfound" is a cursor attribute which is used to find whether the cursor currently contains a record or has reached the end of the file or recordset Explicit Cursor attributes %isopen – Evaluates to True if the cursor is open %notfound. or else the last record will be displayed twice. vtotal students.rollno%type. begin Open cstudent. exit when cstudent%notfound should be done immediately after fetch. dbms_output.put_line('Total :'||vtotal). exit when cstudent%notfound.put_line('Roll number :'||vrollno). end loop. . dbms_output. If the row need to be processed in a particular order. vrollno students. loop fetch cstudent into from students. vname students.Evaluates to TRUE if the most recent fetch returns a row %rowcount-Evaluates to the number of rows returned so far Example to retrieve row from employees table and populate them to another table with a similar structure Declare Cursor emp_cursor is select empid. last_name from employees.Do not use the INTO clause in the cursor declaration.studname. Begin Open emp_cursor. Emp_record emp_cursor%rowtype. close cstudent. to print the name. you may use the order by clause in the declaration.put_line('Name :'||vname).

emp_record. Begin For emp_record IN emp_cursor --implicit open and fetch occurs Loop If emp_record. Retrieving the employees one by one and printing them if they belong to department 80. / Cursor For Loop It is a shortcut for processing explicit cursors. --implicit close and implicit loop exit End. End loop.first_name). End. because the cursor is opened. Set serveroutput on. Close emp_cursor. name) values(emp_record. and the cursor is closed automatically. . Statement2. / Cursors with Parameters You can pass parameters to the cursors.Loop Fetch emp_cursor into emp_record. returning a different active set. Thus you can open and close an explicit cursor several times in a block. Declare Cursor emp_cursor is select first_name . the loop exits when the last row is processed.last_name) End loop. For each execution. End if. End loop. rows are fetched once for each iteration in the loop. Each time you open the cursor with a different set of values. the previous cursor is closed and reopnened with a new set of values. deptno from employees. Exit when emp_cursor%notfound. For record_name IN Cursor_name Loop Statement1.deptno=80 then Dbms_output.empid.put_line(‘Employee ‘ ||emp_record. Insert into temp_emp(empno. Commit.

you can lock those row retuned by the cursor through the FOR Update clause.employee_id ||’ Employee name :’ || emp_record. but it is recommended by Oracle for better readability and maintenance. End loop. : ‘ || emp_record. and each of there formal parameters will have to be passed an ACTUAL parameter or value in the Open statement.put_line(‘Employee no. when querying multiple tables with a join. To prevent any other user/transaction from changing those values. Begin Open emp_cursor(80. Declare cursor emp_cursor(p_deptno number.. because of the for update .employee_id ||’ Employee name :’ || emp_record. Only that table’s rows will be locked whose column is referred to in the For update [of column] clause. Close emp_cursor End. For emp_record IN emp_cursor Loop Dbms_output. Close emp_cursor Open emp_cursor(60. : ‘ || emp_record. For emp_record IN emp_cursor Loop Dbms_output. [It is not necessary that the for update clause refers to a column . p_job varchar2) is select employee_id. you can use the For update clause to ensure row locking to particular table of the join. ‘Sales_Rep’).In the cursor declaration.] Also. End loop.last_name). Hence it is important that no other user /transaction modifies those values. / For Update [Of column] clause Sometimes you may want to perform some update or delete based on the values that the cursor has returned to you. You have to specify the Formal parameter data types.last_name).In such a case. since the update/delete which you want to perform is based on those values. but not the size. ‘Programmer’).put_line(‘Employee no. last_name from employees whre department_id=p_deptno and job_id=p_job. you need to specify the FORMAL parameters. Sometimes it may happen that the rows which you want to lock are already locked by another user/transaction.

employee_id.salary<5000 then Update employees set salary=emp_record. without the need to refer to the ROWID.department_id and employees. . / Cursors with subqueries Declare Cursor my_cursor is Select t1. departments d where d.department_name.department_id. and the total number of employees working in that department.staff from departments t1. Declare Cursor emp_cursor is Select employee_id.staff>=3 When this cursor is opened. the control is immediately passed to your program so that it can do some other work before trying to acquire the lock.department_id=departments. count(*) as staff from employees group by department_id) t2 where t1.department_id=t2. But for this you need to lock the rows with the FOR UPDATE clause so that the rows are locked on open. End. Declare Cursor sal_cursor is Select e. the active set will contain the department number. To avoid this type of waiting. departments where employees.department_id and d. t1. This is possible through the WHERE CURRENT OF clause.salary*1. such that there are more than 3 employees working in each such department..department_id and t2. department name. so that instead of waiting indefinitely.department_id=e. last_name. Where current Of clause Sometimes you may want to update or delete the row being currently addressed.department_id. Begin For emp_record in sal_cursor Loop If emp_record. (Select department_id.10 WHERE CURRENT OF sal_cursor. End if. last_name.clause your block will keep on waiting till the rows are released by the other user/transaction. you can use the NOWAIT clause with the For update clause.department_id=60 FOR Update of salary NOWAIT.deprtment_id=60 FOR UPDATE OF SALARY NOWAIT. salary from employees e. t2. End loop.. department_name from employees.

you can specify an exception handler to perform some other actions. Exceptions are raised in 2 ways : An oracle-defined error occurs and the appropriate exception is raised automatically. Do not declare them and oracle server will raise them implicitly No_data_found Too_many_rows Inavlid_cursor Zero_divide Dup_val_on_index. The exception being raised may be user-defined or pre-defined. But. Exception types Implicitly raised : Predefined Oracle Server : 20 most common errors. In such cases. Statement2.. .] then Statement1. etc Non Predefined Oracle Server : Other Oracle server errors. then the control is not passed back to the enclosing block or environment or point where the exception was raised.. If the exception is successfully handled. but the PL SQl block terminates successfully. Declare them in the declaration section. You explicitly raise an exception by issuing the RAISE statement within the block. Declare them in the declaration section and raise them explicitly Declare Begin Exception When Exception1 [or exception2…. the control is passed to the exception handler in the exception section. When an exception is raised. and oracle server will raise them implicitly Explicitly raised : User-defined : A situation which is abnormal from the user point of view.EXCEPTIONS An exception is an identifier in a PL SQL Block that is raised during the execution of a block that terminates it’s main body of actions. If an exception is raised and there is no corresponding exception handler. then the PL SQL block terminates with failure and the exception is propogated to the calling environment.

Statement4. . since the data is not found. OTHERS is the last exception handler that is defined optionally Guidelines for Trapping Exceptions : Begin the Exception-handling section with the EXCEPTION Keyword Define the required number of exception-handlers. Hence. Statement6. / Here. since when the error is encountered. / The exception handling section traps only those exceptions that are specified. and the line which is after the line that caused the error is not executed.put_line('the roll number is not correct'). others are not trapped. unless you use the OTHERS exception handler. an error has occurred and the control is transferred to the exception handler. but to the exception handler. begin select total into vtotal from students where] End. each with it’s own set of actions When an exception occurs PL SQL processes only one Exception-handler before leaving the block Place the OTHERS clause after all the other exception-handlers There can be only one OTHERS clause Exceptions cannot appear anywhere else. the control is not passed to the immediate next line..] then Statement3. [When others then Statement5.When Exception3 [or exception4….put_line('Check the roll number'). besides the Exception section Trapping Predefined Exceptions : declare vtotal students. which traps any exception which is not yet handled. exception when no_data_found then dbms_output. dbms_output. end.

The PRAGMA EXCEPTION_INIT utility tells the compiler to associate an exception name with an Oracle error number. which always return a standard Oracle server error number. PRAGMA EXCEPTION_INIT(e_emps_existing. End. you may refer to that exception by name and write a specific handler for it. begin select total into vtotal from students where total>100. Example : Oracle returns error number –2292 when you try to delete a parent record which has got some child records.declare vtotal students. Commit. exception when too_many_rows then dbms_output. or by using the OTHERS handler. BEGIN Delete from departments where department_id=&p_deptno. Define p_deptno=20 Declare e_emps_existing EXCEPTION.put_line(‘Cant delete department to_char(&p_deptno) ||’ It has got employees existing ‘).put_line('More than 1 row selected'). end. They are raised implicitly. Exception When e_emps_existing then Dbms_output. but are not associated with name(exception name/error name). -2292). / Functions for trapping Exceptions : SQLCODE-returns the numeric value for the error code SQLERRM-Returns the message associated with the error number ‘ || . / Trapping Non-Predefined Exceptions : There are certain non-predefined standard Oracle errors. Such errors can be trapped by declaring it first . After doing this .total%type. PRAGMA directs the PL SQL compiler to associate all occurrences of that Oracle error number with the given exception name within that block.

Begin Exception When OTHERS then Rollback. v_error_code:=SQLCODE. end if. End. v_error_message varchar2(200). insert into errors values(v_error_code. begin select english into venglish from students where rollno=2.put_line('Failed in English').SQLCODE value 0 1 +100 negative number Description No Exception encountered User-defined exception No_data_found exception Some standard Oracle server error number Example : to store all the error-numbers and error-messages in an ERRORS table Declare v_error_code number. end. / . if venglish<35 then raise low_mark. venglish students.english%type. v_error_message). v_error_message :=SQLERRM. exception when low_mark then dbms_output. / Trapping User-Defined Exceptions : Declare the exception in the declarative section Raise the exception in the executable section Handle the exception in the Exception-handling section declare low_mark exception.

End.. -2292). Commit. Begin For erec in emp_cursor loop Begin Select ……. / .put_line(‘No such department number’).if marks in english are less than 35 then the exception is raised and the message is displayed. End if. pragma exception_init(e_integrity. Exception When e_integrity then……. End. Begin Update departments set department_name=’&p_department_desc’ where department_id=&p_department_number. Sub-blocks can handle an exception or pass the exception to the enclosing block Declare … … e_no_rows exception. / Here no_data_found cannot be used . When e_no_rows then……. End loop. If SQL%NOTFOUND then Raise e_invalid_department. Update……. e_integrity exception. since it is an update statement and not a select statement. End. End if. Define p_department_desc =’Planning n esearch’ Define p_department_number=20 Declare e_invalid_department EXCEPTION. Exception When e_invalid_department then Dbms_output. If SQL%NOTFOUND then Raise e_no_rows.

The error number and message are displayed to the user just like a predefined. nonpredefined or userdefined error .Raise_Application_Error Procedure : This procedure is used to communicate a predefined exception/error with a nonstandard error number and a user-friendly error message from stored subprograms. It also handles the unhandled exceptions.specified number for exceptions between -20000 to -20999 user-specified message upto 2048 bytes long. Raise_application_error(error_number. Raise_application_error can be used in either(or both) the executable section and the exception section. error message) Error_number : Error message: must be a user.

.. p_empsal number) …. In OUT: Passed to the procedure. But it can take a default value. Must be passed as a variable. Parameter Modes : IN(default) : Value passed to the procedure from the calling environment. OUT: Returned to the calling environment. …] -. It has a Header section. End hikesal. It’s value cannot be changed in the procedure body. Actual parameters are the variables or expressions passed while calling the procedure Execute hikesal(v_empid. and then returned to the calling environment. The Formal parameter acts as a constant and only takes the values passed by the calling environment. executable section and an optional exception-handling section. Formal versus Actual Parameters : Formal parameters are the variables declared in the parameter list of the procedure declaration Create or Replace procedure hikesal(p_empid number.header Is/AS --this section after is/as and before the begin is the declarative section PL SQl block --. It can stored in the database as a schema object. parameter2 [mode] datatype. Create or Replace Procedure procedure_name [parameter1 [mode] datatype. expression. or an initialised variable. It is a named PL SQL block that can accept parameters(called arguments). declaration section. Cannot be assigned a default value. 2000). Must be passed as a variable. . Cannot be assigned a default value.Procedures A procedure is a type of sub-program that performs an action. The actual parameter can be a constant.executable and an optional exception section The pl sql block starts with either a BEGIN or the declaration of local variables and ends with END or End procedure_name.

/ main block declare cursor c1 is select empno from emp where deptno=10. end if.put_line('Employee salary is '||vs). vs). vsal IN OUT number. vsal1 emp. / main plsql block declare cursor c2 is select empno. ve.hiredate%type. ve emp. hiredate from emp. sal into vename. end loop. / to show increase in salary by 10 percent for all employees and an additional 5 percent for those who have completed more than 5 years of service create or replace procedure retemp(veno IN number.put_line('Employee name is '||ve).sal%type.ename%type. vsal OUT number) is begin select ename.Stored Procedure to display employee numbers and their salaries for department 10 create or replace procedure retemp(veno IN number. sal. vdate1 emp. dbms_output.put_line('Employee number is '||erec.05. year IN number) is begin if year>=60 then vsal:=vsal*1. begin for erec in c1 loop retemp(erec. end. vsal from emp where empno=veno. . dbms_output. dbms_output.empno.sal%type. end. vs emp. end. years number. vename OUT varchar2.empno).

end loop. p_comm.put_line('Employee number '||rec.put_line('Employee salary '||rec. :g_sal. / at the calling environment : variable g_name varchar2(25) variable g_sal number variable g_comm.) print g_name print g_sal print The colon(:) is required to reference the host variable s in the execute command. commission_pct into p_name.put_line('Employee salary '||vsal1). / Viewing OUT Parameters : Create or replace procedure query_emp (p_id In employees. vsal1:=rec. dbms_output. OUT employees. p_name OUT employees. end. retemp(rec. :g_name. Number execute query_emp(100.empno. Methods of passing Actual Parameters : Positional : Here the actual parameters are passed in the order in which the Formal parameters are given with the procedure definition .commission_pct%type) is BEGIN Select first_name.vsal1.empno). p_salary. End emp_query. dbms_output.employee_id%type. :g_comm. p_comm from employees where employee_id=p_id.1. years).hiredate) INTO YEARS from emp where empno=rec.put_line('Employee salary '||vsal1). select months_between(sysdate. dbms_output. salary. p_salary OUT employees.empno.sal).begin for rec in c2 loop dbms_output.sal*1.salary%type.first_name%type.

p_loc). p_name=>’Medical’). it must me the last item declared. location_id) values(departments_seq. Executing/Calling the above procedure : Begin add_dept. or else there will be an error. p_name. --. Example : Execute add_dept(p_name=>’Legal’. department_name. 500) -. Any variable declared after the local subprogram will cause a compilation error.will give an error as “a positional parameter may not follow a named parameter” Declaring Local Sub-procedures : The local procedures are not stored as Schema objects. End add_dept. Because they are defined in the declaration section of another program/PL SQL Block/procedure. and not to OUT or IN OUT Parameters. . / Default values may be assigned only to In parameters .nextval. ----positional add_dept(p_loc=>300.location_id%type DEFAULT 100) IS Begin Insert into departments(department_id. -.both default add_dept(‘Welfare’. P_loc IN departments. their scope is limited to the parent(enclosing) block in which they are defined. Default Option for parameters Create or Replace procedure add_dept(p_name IN departments.200).one default End.---Named association add_dept(p_loc=>400).Named Association : Here the actual parameters are passed in ant arbitary order by associating it with the corresponding formal parameter using the => symbol. declare procedure p1 is begin dbms_output.put_line('P1 is called').department_name%type DEFAULT ‘unknown’. end. Combination : Here the first actual parameter is passed positionally and the remaining are passed using the => symbol as in named association method. / In Combinational method all the positional parameters must be before the named parameters. When you are declaring a sub-program in the declaration section of the main program.

/ declare procedure p1. dbms_output.. End log_emp. End del_emp.put_line('p1 called').begin p1. SYSDATE). is not types as line 1) The result is an infinite loop.. end. is never executed.put_line('p2 called'). log)date) values(USER. Procedure to delete an employees record and to log the entry of the user who deleted the record Create or Replace procedure del_emp(p_id IN employees. end.put_line('In the main block').. dbms_output. procedure p2 is begin dbms_output. p2. end. procedure p1 is begin dbms_output. p1. and dbms.put_line('In the main block'). Begin Delete from employees where employee_id=p_id. / . p2. log_exec. end.employee_id%type) IS Procedure log_emp IS Begin Insert into log_table(user_id. begin p1. / it will show error : p1 must be declared(if procedure p1.

If the exception is handled. Select department_id into v_did from employees where employee_id=999.put_line(‘Procedure INS_dept started’). End emp_proc. Commit. / Invoking a stored procedure from another Stored procedure : Create or replace procedure emp_proc IS Cursor emp_cursor is select employee_id from employees.Invoking a stored procedure from an anonymous block : Declare V_id number:=145. / Handled Exceptions : When an exception is raised in a called procedure. Begin Raise_salary(v_id). Insert into departments values(5. 200. Commit. p_locid). then the block terminates. Consider the following tables LOCATIONS Location_ID City 1 Mumbai DEPARTMENTS Department_ID 5 Department_name Welfare Manager_ID 200 Location_ID 1 Create procedure Ins_dept(p_locid number) IS v_did number(4).employee_id). / . the control goes immediately to it’s exception section. Begin For erec in emp_cursor Loop Raise_salary(erec. End loop. End. and the control goes to the calling program/environment. ‘Mumbai’. …… End. Begin Dbms_output. Any DML statements issued before the exception was raised remain as part of the transaction.

and becomes a part of the transaction of procedure ins_loc procedure Execute ins_loc(1. / The procedure INS_loc inserts a new location into the locations table. Exception When no_data_found then Dbms_output. ALL DML statements in the calling and called procedure are rolled back along with any changes to any host variables. Insert into locations(location_id. Select city into v_city from locations where location_id=p_lid. city) values(p_lid. then it raises no_data_found. p_city). p_city varchar2) IS v_city varchar2(30). then the DMLs in both the procedures are rolled back if no employee with employee_id=999 is found.put_line(‘MAIN Procedure INS_LOC started’). Thus.Create procedure Ins_loc(p_lid number. all DML statements in the calling and called procedure remain as part of the transaction. if the exception section from the ins_loc is removed. the control is passed to the calling procedure ins_loc where the exception no_data_found is handled. Dbms_output. department name=Welfare.put_line(‘No such employee’). The procedure ins_dept is supoosed to insert a new department with department id=5.put_line(‘Invoking Procedure INS_dept’). Procedure ins_dept selects the department id for an employee whose employee id=999. Ins_dept(p_lid). the DML in ins_dept is not rolled back. Dbms_output. Manager ID=200 at the new location inserted through INS_loc. End. department/location for any . If the exception is not handled by the calling procedure. If in the above 2 procedures. v_dname varchar2(30).put_line(‘Inserted City ’|| v_city). ‘Mumbai’) If the exception is handled in the calling procedure. So. the calling procedure terminates and the exception propagates to the calling environment. Begin Dbms_output. Suppose there is no such employee. which is not handled in procedure ins_dept.

…] -. Create or Replace Function function_name [parameter1 [mode] datatype. parameter2 [mode] datatype. Like a procedure. return 10. Function is called as part of a SQL expression or as a part of a PL SQL expression.put_line('Inside the function'). can be called thru another pl/sql block .Functions Function is a named PL SQL block that can accept parameters and be invoked. A function must return a value to the calling environment.header RETURN datatype Is/AS --this section after is/as and before the begin is the declarative section PL SQl block --.put_line('value of x is'||x). dbms_output. / Global or stored function : Stored in the database Defined and saved separately. In addition. end. a function has a header. If it is necessary to declare a variable it should be done in the declare part of the enclosing program declare x number.put_line('Inside the Main'). function f1 return number is begin dbms_output. a function must have a RETURN clause in the header and at least one RETURN statement in the executable section.executable and an optional exception section End function_name. end. executable part and an optional exception section. x:=f1. begin dbms_output. declarative section. Local functions : Not stored in database Defined and called within the same program Functions do not have declare. whereas a procedure returns zero or more values. / The type of parameter mode should be only of type IN.

as follows : variable gsalary number execute :gsalary :=getsal(130) print gsalary try the following on emp in scott : ed f1.employee_id%type) RETURN number Is v_salary employee.salary%type :=0. return false. Begin Select salary into v_salary from employees where employee_id=p_id. begin select sal into vsal from emp where empno=veno. / at the sql prompt :>show_error.Create or Replace Function getsal(p_id IN employees. to show the errors in the function coding.sal%type.put_line('salary is not found'). . to execute >@f1. / Executing functions : Declare a variable to hold the return value. End getsal. create or replace function chkemp(veno number) return boolean is vsal emp. RETURN v_salary. return true. end. which is a good programming practice. dbms_output.put_line('salary is '|| vsal). exception when no_data_found then dbms_output.

/ select text from user_source where type ='FUNCTION' and name='UPSAL' order by line main pl/sql block declare cursor c1 is select empno.put_line('Employee Existing'). else dbms_output. select sal into vsal from emp where empno=veno. incr). end. incsal number. incr number :=&incr. begin update emp set sal=sal+(sal*inc/100) where empno=veno.put_line('Increased salary is '||incsal||' for employee '|| erec. / . inc number) return number is vsal number. end loop. end. flag boolean. begin for erec in c1 loop incsal:=upsal(erec.put_line('Employee Not Existing'). dbms_output. return vsal.main block declare y number :=&eno.empno). if flag=True then dbms_output. end. sal from emp where sal<3000.empno. begin flag:=chkemp(y). end if. / stored function to update the salaries of employees getting less than 3000 with increment of certain % percent create or replace function upsal(veno number. commit.

OUT and IN OUT are available with functions. Advantages of Functions : To perform calculations that are complex. Increase efficiency of queries by performing functions in the query rather than in the application Create or Replace Function tax(p_value IN NUMBER) Return NUMBER IS Begin Return(p_value * 0. salary. / INVOKING a function from a SQL Expression Suppose you have a table employees with salary column then you may use the above function as follows to calculate their tax Select empno. tax(salary) from employees where tax(salary) >(select max(tax(salary)) from employees where departmentid=30) order by tax(salary) desc Restrictions on calling function : The function must be a Stored Function It must accept only IN parameters Accept the parameters whose data type must be standard SQL data type and NOT a PL SQL data type . tax(salary) from employees. Locations from where you may call a User-defined function : Select list of a SELECT command Condition of the WHERE and HAVING clause Connect by . and it involves a lot of complications and side effects. awkward or unavailable with SQL Increase data independence by processing complex data at the Oracle server level(since the stored functions are stored at the server). do not use OUT and IN OUT with functions. rather than retrieving data into an application. End Tax. There can be a RETURN statement in the exception section also. Having a function returning multiple values is a poor programming practice. order by and group by clauses Values clause of the insert command SET clause of the update command Select empno. since the purpose of a function is to accept 0 or more parameters and return a single value.Although 3 parameter modes IN. start with.08).

or DDL commands Functions called from a SQL Expression(as shown above) cannot contain a DML Statement. / Update employees set salary=xyz(100) where employee_id=95. Begin Select salary into s from employees where employee_id=95. End. appoint_date.’Pereira’. the function cannot contain commands that end the transaction. 10000). Examples Create or Replace function abc(p_sal number) Return number is Begin Insert into employees(employee_id.The return data types must be a standard SQL data type and NOT a PL SQL data type Restrictions from where a stored function can be called : Functions called from an Update/Delete statements on a Table XYZ cannot contain a DML statement on the table XYZ Functions called from an Update/Delete statements on a Table XYZ cannot query the table XYZ When called from an INSERT/UPDATE/DELETE/SELECT statement. / The function fails with the folliwng : Update employees set salary=abc(2000) where emplyee_id=90. such a table is called MUTATING table . Here also the mutating table error is returned When the code in a function is querying or reading the data in a table which is being updated. Return(p_sal +100). End. ALTER SYSTEM(system control statement). sysdate-10. The function contains a DML statement on table employees. The update statement returns an error saying that the table is mutating Aslo Create or replace function xyz( a number) retutn number is s number. last_name. such a COMMIT(transaction control statement). If a Function internally calls sub subprogram(that is another function or procedure) then that sub program even muts not violate any of the above mentioned restrictions. Return (s+a). salary) valurs(1001. We are calling the function thru the update command on the same table employees. SET ROLE(session control statement).

which is returned to the calling environment .To drop a function : Drop function function_name. Function Executes as a PL SQL Block Invoked as part of an expressionm Exec Proc_name Does not contain a RETURN clause in Must contain a RETURN clause in the the Header Header May or may not return values Must return a single value Used to perform a series of actions Used to compute some value. Procedure V/s.

then you must have EXECUTE privilege on that subprogram. alter. Grant Alter any PROCEDURE to user_name. DIRECT ACCESS From Hemant schema grant object –level privilge on the table employees to user Manoj Manoj has created the procedure manoj_proc that queries the Employees table in the schema Hemant INDIRECT ACCESS Manoj grants execute privilge to Saloni on his procedure manoj_proc This Saloni can access By default subprograms execute under security domain of the owner. Grant Execute any PROCEDURE to user_name. Suppose we need to ensure that SALONI can access the table EMPLOYEES in the schema HEMANT.Managing Subprograms : System privileges are required to Create. Providing INDIRECT ACCESS to Data Suppose EMPLOYEES table in Scheme(user) HEMANT. Alter. then you must be granted access to those objects explicitly. The keyword ANY means that you ca create. or excute your own subprograms and those in another schema. Functions and Packages. There is another user MANOJ and a third USER SALONI. Drop or Execute subprograms. not through a role If you are not the owner of a subprogram. drop. but only through a procedure manoj__proc which is created by the user MANOJ. which is called DEFINER’s-RIGHTS. . The keyword ANY is optional for CREATE. The keyword PROCEDURE is used to assign such rights on Stored Procedures. System privileges are granted by the user SYSTEM or SYS Grant Create (any) PROCEDURE to user_name. If a PL SQL subprogram refers to any objects that are not in the same schema. Grant Drop any PROCEDURE to user_name.

USER_SOURCE Name -Name of the object Type -Type of object : Procedure. both of which contain an additional OWNER column. PROCEDURE. Package. query the user_objects USER_OBJECTS Object_name Object_Id Object_type CreateLast_DDL_Time Timestamp Status -Name of Object -Internal identifier for the object -Whether TABLE.User_Objects To obtain names of all PL/SQL stored objects within a schema. Package Body LINE -Line number of the source code where error occurred Position -Position in the line where the error occurred Text -Text of the error message SHOW ERRORS [Function/Procedure/Package/Package body/Trigger/View This will show use the errors that occurred while trying to compile the articular program unit. PACKAGE BODY. Function. Package. PACKAGE. TRIGGER -Date of object creation -Date when object was last modified -Date and time when object was last recompiled -VALID or INVALID You can also examine the ALL_OBJECTS and DBA_OBJECTS. ALL_SOURCE and DBA_SOURCE contain the additional column Owner Select text from user_source where name=’PROCEDURE_name’ order by line. USER_ERRORS Name -Name of the object Type -Type of object : Procedure. Package Body LINE -Line number of the source code TEXT -Text of the source code line This table contains one record for each line of code. FUNCTION. Function. SHOW ERRORS without any [parameter will show the compilation errors The following query will also show you an output which is similar to that of show errors .

. text from user_errors where name=’proc_name’ order by line.Select line || ‘/’||position.

TRIGGERS Definition : Trigger is basically a PL/SQL block or PL/SQL procedure associated with a Table/View/Schema/Database and which executes implicitly whenever a particular event takes place Types of Triggers : Application Triggers which execute implicitly when a particular DML event occurs within an application such as Oracle Forms Developer Database Triggers which could be 1) Data Event or 2) System Event Data Event trigger fires implicitly whenever a DML operation occurs on table or a DDL event such as CREATE/ALTER are issued. It could also be an INSTEAD OF Trigger on a View. They are fired irrespective of the user connected and irrespective of the application used. System Event Triggers are fired when a system event occurs such as user logs on, user shutsdown, etc Guidelines for Designing Triggers Dos Design Triggers to guarantee that when a specific operation is performed, related actions are performed. Use Triggers only for Centralised, Global Operations that occur for the triggering event, regardless of the user or application that issues the triggering statement. Donts Do not use triggers when the functionality is already built into Oracle Server. Do not use triggers to implement integrity constraints. Use the built-in constraints Excessive use of triggers can result into complex interdependencies. If the logic is very lengthy, write a stored procedure for the same and invoke the stored procedure in the trigger body If multiple triggers of the same type are defined for a table, their order of execution is arbitary. To ensure that multiple triggers of the same type are executed in a particular order, write stored procedures for the different actions and have a single consolidated trigger in which you call those stored procedures in the required order. The Trigger Statement contains : Trigger Timing :BEFORE, AFTER for tables Triggering Event :INSERT, UPDATE or DELETE Table name :On table or view Trigger Type :Statement level or Row level Trigger Body :PL SQL block INSTEAD OF for views

BEFORE :Execute the trigger body before the triggering DML event on the table To determine whether the triggering statement should be allowed to complete To calculate some values before completing the triggering Insert or Update statement To validate or set some complex business logic To initialize some global variables or flags BEFORE :Execute the trigger body before the triggering DML event on the table To complete the triggering statement before executing the trigger body INSTEAD OF This type of trigger is used to modify data through a view that was otherwise not modifiable because of the inherently non-modifiable nature of the view. Such trigger works in the background by performing the action directly on the underlying base tables involved in the view. You may write INSERT, UPDATE or DELETE statements on a view. The Triggering Event can be INSERT, UPDATE or DELETE statement on a table. In case of UPDATE statement, you can specify the column, which if changed, causes the trigger to fire. The triggering event can contain one or two or all the three DML operations. The trigger type can be Statement Trigger or Row Trigger. A Statement Trigger is fired once for the triggering event. It may affect zero or more rows, but is fired only once. They are used when the trigger-action to be performed is independent of the data affected by the triggering event. A Row Trigger is fired once for each affected row. If no rows are effected, then the trigger is not fired. They are used when the trigger-action depends on the data or rows affected by the triggering event. The Trigger body defines the action that needs to be performed when the triggering action is issued. It is a PL SQL block containing SQL and PL SQL statements defining PL SQL types, item, variables, constants, cursors, exceptions, etc. You can call other PL SQL procedures or Java Procedures. Trigger size cannot be more than 32K. The Firing Sequence is as follows : BEFORE Statement Trigger -------- once BEFORE Row Trigger AFTER Row Trigger AFTER Statement Trigger -------- once for each affected row -------- once for each affected row --------- once

Syntax for Statement Level Trigger Create or Replace Trigger Trigger_name Timing Event1 or Event2 or Event3 On table_view_name Trigger_body The trigger name must be unique with respect to other triggers in the same schema. Trigger name need not be unique with respect to other schema objects like table, view, or procedure. A trigger to prevent insertion of records into the dept table on Saturdays or Sundays or on non-working hours on other days create or replace trigger check_deptno before insert on dept begin if (to_char(sysdate,'DY') in ('SAT','SUN')) or (to_char(sysdate,'HH24:MI') not between '09:00' and '17:00' ) then raise_application_error(-20500,'Insert Not allowed'); end if; end; / Raise_application_error is a server-side built-in procedure that returns an error to the user and causes the PL SQL block to fail. When the database trigger fails, the triggering statement is automatically rolledback by Oracle Server. Table : DEPT DEPTNO varchar2 DEPTNAME vrachar2 A trigger to prevent insert or update or delete operations on table dept create or replace trigger check_deptno before insert or update or delete on dept begin if deleting then raise_application_error(-20500,'Delete Not allowed'); elsif Inserting then raise_application_error(-20501,'Insert Not allowed'); elsif Updating('deptno') then raise_application_error(-20502,'Updating of deptno Not allowed'); else raise_application_error(-20503,'Updating of Table Not allowed'); end if; end; /

DELETING. Time timestamp. we can use the OLD and NEW Qualifiers to reference the value of a column before and after the data change by prefixing the column name with the OLD and NEW Qualifiers. New_deptname varchar2(15) ) . No colon(:) required if the Qualifiers are used in the WHEN clause. Old_deptno varchar2(15).deptno>50) begin raise_application_error(-20555. UPDATING. If the condition is satisfied then only we enter into the trigger body. Operation For INSERT For UPDATE For DELETE Old Value NULL Value before update Value before update New Value Newly Inserted value Value after update NULL Table : AUDT_DEPT create table audt_dept ( User_name varchar2(15). / with the WHEN clause you can specify a condition in the brackets. the WHEN clause is to restrict the Trigger action to those rows that satisfy a certain condition With ROW Level trigger only. UPDATING(‘column’) can be used in a single trigger for combining several triggering events into one single trigger Syntax for Row Level Trigger Create or Replace Trigger Trigger_name Timing Event1 or Event2 or Event3 On table_view_name For Each Row [When (condition)] Trigger_body create or replace trigger check_dept before insert on dept for each row when(new. Thus. The condition is evaluated for each row to determine whether or not the trigger body is executed.'Hello').Special Conditional Predicates INSERTING. end. You need to use the colon(:) as a prefix in every SQL and PL SQL statement. Old_deptname varchar2(15). New_dept varchar2(15). The WHEN clause is optional.

:old.create or replace trigger audt_dept after insert or update or delete on dept for each row begin insert into audt_dept values(user. :old. :new. group by clause. :new. The INSTEAD OF trigger must enforce the check. Unlike other triggers.deptno. BEFORE and AFTER options are not valid. sysdate. Create or Replace Trigger Trigger_name INSTEAD OF Event 1 or event2 or event3 On View_name For each row Trigger_body Even if FOR EACH ROW is omitted. INSTEAD OF Triggers is still defined as a Row Trigger. Consider the following tables : Table Empid Empname Salary Deptno Table Deptno Deptname Totalsal : Employee : Dept_stat . INSTEAD OF Trigger It is used to modify the data where a DML statement has been issued against an inherently non-updatable view(that is views which are non-updatable because the underlying query may contain set operator. Such triggers are Row Level Triggers. distinct operator or a join of 2 or more tables. group function. end.deptno. start. this trigger is fired by Oracle sever instead of executing the triggering statement.deptname. The WITH CHECK option for views is not enforced when insertion/updation are performed by using the INSTEAD OF Trigger. connect by.deptname).

deptno where empid=:old.Following trigger updates the total salary in Dept_stat table whenever rows are inserted/update/deleted from the Employee table. where Elsif UPDATING(‘SALARY’) then Update employee set salary=:new. e. End. Elsif Updating(‘Deptno’) then Update employee set deptno=:new.deptno. Update dept_stat set totalsal=totalsal+:new. :new.salary . e.empid.salary where deptno=:old.:old.empid. Elsif DELETING Then Delete from employee where empid=:old. Update dept_stat set totalsal=totalsal + :new.deptno). :new.salary where deptno=:new. / To Enable/Disable a Trigger Alter Trigger Trigger_name DISABLE/ENABLE To Enable/Disable all Triggers on a table Alter Table Table_name DISABLE/ENABLE ALL TRIGGERS To Recomplie a Trigger Alter Trigger Trigger_name COMPILE .empname.empid.empid.deptno. Create view empl_view as Select e.deptname from employee e.salary where deptno=:new.salary where empid=:old. e.salary.salary where deptno=:old. Create or Replace Trigger New_emp_check INSTEAD OF INSERT OR DELETE OR UPDATE FOR EACH ROW Begin If INSERTING THEN Insert into employee values(:new.deptno. d. Update dept_stat set totalsal=totalsal +(:new. Update dept_stat set totalsal=totalsal :old. Update dept_stat set totalsal=totalsal-:old.salary deptno=:old.deptno.empid.deptno.salary. :new. dept_stat d where e.deptno.empname.deptno=d.deptno. End if.

Synonym. On Database/Schema Trigger_body . The DDL Triggers fire when the Object is a Cluster. Role. All the triggers on a table are dropped when the table is dropped. On Database/Schema Trigger_body Timing : BEFORE or AFTER DDL_Event : CREATE OR ALTER OR DROP. Type . Tablespace. Events that can cause a System Level Trigger to fire are : A DDL statement on a object in the database or schema (the trigger can be Database Level or Schema Level) Specific User or any other User logs on or off (the trigger can be Database Level or Schema Level) Database Shutdown or Startup (the trigger can be Database Level only Triggers on DDL Statements : Create OR Replace Trigger Trigger_name Timing DDL_Event1 Or DDL_Event2 or…. Trigger. Causes the Oracle Server to fire the trigger whenever a Create/Alter/Drop Statement modifies a Database Object in the Data Dictionary. View or a User Triggers on System Events : Create OR Replace Trigger Trigger_name Timing Database_Event1 Or Database_Event2 or…. To Drop a Trigger Drop Trigger Trigger_name. regardless of whether it is valid or invalid.This command is used to explicitly recompile a trigger. Trigger_body : It is a complete PL SQL Block. Function. Triggers A Database Level Trigger fires for all users. Index. Package. On Database/Schema : You can create triggers on DDL Statements at the DATABASE or SCHEMA Level. A Schema or Table Level Trigger fires only when that schema or table is involved. Procedure. Table. SYSTEM LEVEL TRIGGERS Triggers on system events can be defined at the Database Level or Schema Level. Sequence.

SYSDATE. Java. A mutating table is the one that is currently being modified by an UPDATE. job_id ON Employees For Each Row When(new. date. date. SYSDATE. such a table is called MUTATING table. Reading and Writing data using triggers follows certain rules. action) values(USER. action) values(USER. END. which are applicable to only row level triggers or a statement level trigger that is fired because of the referential integrity constraint ON DELETE CASCADE.job_id<>’YYZ’) CALL check_sal(:new. C. The procedures so called can be implemented in PL SQL. ‘Logged Off’). / CALL Statement : It is recommended to create stored procedures and call them in the Trigger body rather than coding the PL SQL body in the trigger itself. CREATE OR REPLACE TRIGGER logon_trig AFTER LOGON ON SCHEMA BEGIN Insert into log_trig_table(userid. Create or Replace Trigger salary_check Before Update of Salary . / CREATE OR REPLACE TRIGGER logoff_trig AFTER LOGOFF ON SCHEMA BEGIN Insert into log_trig_table(userid. There is no semicolon at the end of the CALL Statement. END.Database_Events : AFTER SERVERERROR : Whenever a Server Error Message is logged.job_id.salary) MUTATING TABLE When the code in a trigger is querying or reading the data in a table which is being updated. INSERT OR DELETE statement and a ROW . ‘Logged On’). AFTER LOGON : Whenever a User Logs on to the Database BEFORE LOGOFF : Whenever a User Logs off the Database AFTER STARTUP : Whenever a Database is opened BEFORE SHUTDOWN: Whenever a Database is shut down These triggers can be created at the DATABASE or SCHEMA LEVEL. :new. The CALL statement enables you to call a stored procedure. but SHUTDOWN and STARTUP apply only to the Database Level.

subobject_name. BEGIN Select Min(salary).level trigger on any such event is trying to read/write data into the same table.’Salary Out Of Range’). trigger_type.salary%type. select trigger_name.salary>v_maxsal then Raise_application_error(-20505. trigger_body from user_triggers table_name. (A table is not mutating for STATEMENT level triggers. / Viewing Trigger Information User_objects : Contains name and status of the trigger and the date and time when the trigger was created.job_id <>’PROG’) Declare V_minsal employees. type. V_maxsal employees. status. triggering_event. created from user_objects where object_type='TRIGGER' User_Triggers : Contains name. job_id On Employees When (new. trigger body. select object_name. END IF: END. table on which table was created. v_maxsal from employees where job_id=:new. referencing_names.) A triggered table itself is mutating.salary<v_minsal or :New. User_errors : Contains details of the compilation errors that occurred while the trigger was compiling . and any other table referencing it with the FOREIGN KEY constraint is also mutating. triggering event. Create or Replace Trigger Check_Sal Before INSERT Or UPDATE OF salary. Consider a trigger which checks that the salary for a new employee or an existing employee is always between the minimum and maximum salaries for that job code. max(salary) into v_minsal.salary%type.job_id IF :New. status.

The Replace option drops and recreates the package specification. Package Specification is the INTERFACE to your application. the entire package gets loaded into memory. exceptions. The public procedures or functions can be invoked repeatedly by other constructs in the same package or from outside the package. Can be referenced and changed(in case of variables) outside the package and are visible to the external users. In the Specification we declare the variables. called or nested. exceptions or types. cursors and sub programs available for use Package Body fully defines the cursors and subprograms. generally. has two parts : Package Specification and Package Body. . Types of Package Constructs : Public or Global : Declared within the package specification and may be defined in the package body. cursors. Private or Local : Declared and Defined within the package body. Variables declared in the package specification are initialized to NULL by default. types. constants. subprograms(procedures and functions) into one single container. Creating the Package Specification Create or Replace Package package_name Is/as Public type and item declarations Subprogram specifications End package_name. This allows to change the definition of a program construct in the package body without causing the Oracle server to invalidate the other schema objects that call or reference the program construct.PACKAGES It is used to group together related PL SQL Types. Subprogram specification : Declares the PL SQL subprograms. Can only be referenced by other constructs which are part of the same package. items. constants. which are stored separately in the database. Further calls to other constructs of the same package do not need any disk I/O. and thus implements the specification. Public type and item declarations : Declares variables. A Package. The package cannot be itself parameterized. When you call a packaged construct for the first time.

cursors. Private type and item declarations : Declares variables. exceptions or types.declared and initialized procedure reset_comm(p_comm IN Number). Thus. and they have their underlying implementation(or bodies) in the package body. exceptions. / Create or Replace Package Body comm_package Is Function validate_comm(p_comm IN Number) Return Boolean Is v_max_comm Number. if a package specification does not declare subprograms and cursors and declares only types. -. Begin Select max(commission_pct) into v_max_comm from employees. The Replace option drops and recreates the package body. END comm_package. Subprogram Bodies : Defines the PL SQL subprograms. The function should be called through a procedure in the same package. If p_comm>v_max_comm then return(FALSE). Create or Replace Package comm_package Is g_comm Number :=0. Subprograms and Cursors are declared(without their respective bodies) in the package specification. constants. End validate_comm. variables. . But the package body can still be used to initialize items declared in the package specification. Else return(TRUE). constants. All private constructs must be declared before they are used in the public constructs.10. End if. public and private. then the package body is not necessary. and this procedure should display the appropriate messages and reset and validate the prevailing commission. Write a package that contains a function that validates the commission so that the commission may not be greater than the highest commission amongst all the employees.Creating the Package Body Create or Replace Package Body package_name Is/As Private type and item declarations Subprogram Bodies(Private and Public) End package_name.

hence it can be referenced by only other procedures/functions of the same package. / When you invoke a package or function from within the same package. End if.mile_2_kilo|| ‘ kms.’Invalid Commission’).25) To invoke a procedure from a package through iSQL *Plus Execute comm_package.put_line(’20 miles = ‘ ||20*global_consts. meter_2_yard constant number :=1.Procedure reset_comm(p_comm IN NUMBER) Is Begin If validate_comm(p_comm) then g_comm:=p_comm.6214.reset_comm(0. yard_2_meter constant number :=0. The above function is a private function(declared and defined within the package body). End reset_comm.reset_comm(0.reset_comm@ny(0.15) To invoke a procedure from a package through a remote database Execute comm_package.comm_package.15) Declaring Bodiless Package Create Or Replace Package global_consts IS mile_2_kilo constant number :=1. / Execute dbms_output.’).reset_comm(0.6093. This package specification declares public(global) variables that exist for the duration of the user session. you need not qualify it’s name with the package name. End comm_package.9144. you need to qualify it’s name with the name of the package Comm_package. kilo_2_mile constant number :=0.15) To invoke a procedure from a package through a different schema Execute scott. To invoke a package procedure or function from outside the package. .936. Else Raise_application_error(-20210. end global_consts.

. but differing in the number. End meter_to_yard. Overloading is a feature which enables you to have different packaged subprograms with the same name. Added Functionality since it allows persistency of variables and cursors Overloading allowed.:yard) > print yard To Drop the package Specification : Drop Package package_name. since multiple subprograms of the same name are allowed Better Performance : Entire package loaded into memory when a package is first referenced Only one copy of the package in memory for all the users Dependency hierarchy is simplified Overloading support in Packages Packaged subprograms(procedures or functions) Overloading not possible for stand-alone subprograms. / at the sql prompt >variable yard number >execute meter_to_yard(1.meter_2_yard. can be overloaded. p_yard Out number) Is Begin p_yard:=p_meter * global_consts. To Drop the package body : Drop Package body package_name. Hiding Information : Only package declarations made in the specification are visible and accessible to applications Private package constructs are hidden and inaccessible All the coding is hidden in the package body. since specification and body are coded and compiled separately. order or data-type of the formal parameters of the subprograms.Referencing a Public variable from a stand-alone procedure Create or Replace procedure meter_to_yard(p_meter IN number. Advantages : Modularity since it encapsulates related constructs Easier Application Design.

empage) values(p_empno.empno%type. Create or replace package body overload Is Procedure add_employee(p_empno IN employees. the compiler stops the search. p_age IN employees. p_empname.empage%type default 21) Is Begin Insert into employees(empno.empname%type default ‘unknown’. p_age IN employees. the compiler starts searching for a subprogram with that name in the current scope. order and datatypes of the actual parameters passed with the called subprogram with formal parameters of the one or more subprograms searched in a scope. It then starts matching the number. p_empname IN employees. empname.empname%type default ‘unknown’. Procedure add_employee(p_empname IN employees. . End add_employee. p_empage). Procedure add_employee(p_empname IN employees.empage%type default 21) Is Begin Insert into employees(empno. Example : VARCHAR and STRING are PL/SQL subtypes of VARCHAR2.empage%type default 21). it starts searching in the enclosing scopes.empage%type default 21). and if it does not find one in the current scope. p_empname IN employees.empname%type default ‘unknown’.nextval. p_age IN employees. but the different subtypes belong to the same family. empname. empage) values(empnoseq. Example : NUMBER and DECIMAL datatypes belong to the same family Subprograms which differ only in the subtypes of their parameters.empno%type.RESTRICTIONS 1) 2) 3) Standalone subprograms cannot be overloaded Subprograms which differ only in the datatypes of their parameters. but the different datatypes belong to the same family. As soon as the compiler finds one or more subprograms with the required name. p_age IN employees. Create or replace package overload Is Procedure add_employee(p_empno IN employees.empname%type default ‘unknown’. END overload. Resolving a Subprogram call When a call is made to a subprogram. p_empage). p_empname.

if you have redeclared the to_char function. and the subprogram bodies go in the package body. To access the built-in subprogram. you call it as :STANDARD. If you redeclare a built-in subprogram as a stand-alone subprogram then to access your sub-program you need to qualify it with your schema. example scott. Thus.End add_employee END overload.’Rahul’. since the subprogram specifications go in the package specification. At the SQL PROMPT >Execute overload. Thus packages support forward declarations. because the function to_char belongs to the builtin package STANDARD. To solve this. which means that a subprogram cannot be referenced or called before it has been declared. PL/SQL allows a special subprogram declaration called Forward declaration.to_char Using Forward Declarations PL/SQL does not allow forward referencing. . The subprogram body can appear anywhere after the forward declaration . but both must appear in the same program unit. Forward declarations are used when you need to : Define subprograms in a logical or alphabetical order Define mutually recursive subprograms(which call each other directly/indirectly) Group subprograms in a package Use Forward Declarations in the cases of private constructs or private subprograms of the package. The formal parameter list must appear in both the forward declaration and the subprogram body. where they are invisible to the applications. 23) If you redeclare a built-in subprogram in another PL SQL Program unit.add_employee(’Rahul’. your local declaration overrides the built-in or standard subprogram.TO_CHAR. then to use the built-in to_char function . 32) >Execute overload. you need to qualify it with the package name.add_employee(101. since public package constructs are already declared in the package specification. The subprogram can be then defined after another subprogram that calls it. whereby you give the subprogram specification terminated by a semicolon.

/ One-time-Only Procedure When the derivation of the values is too complex it is difficult to initialize public or private variables to that value in the variable declaration. --forward declaration Procedure award_bonus(…. Create or Replace Package otop Is Hra number. In such cases. because the value is reset by the one-time-only procedure.) Is begin Calc_rating(…) End. The keyword END is not used at the end of the One-Time-Only procedures. Procedure calc_rating(…) Is Begin End. For such type of variables do not initialize them in the declaration. ----declare all other public procedures/functions/variables END otop. we use one-time-only procedures.Create or Replace Package Body forwardpack Is Procedure calc_rating(.No End for this one-time-only procedure END otop. / Create or Replace Package Body otop Is ----declare all private procedures/functions/variables ----define private/public procedures/functions Begin Select rate into hra from rate_mast where rate_name=’HRA’. / . End forwardpack. ----. since such procedures are executed only once when the package is invoked within a user session.)..

create or rollback to a savepoint or alter the system session 2) A function called from a query statement or a DML statement cannot execute a DML statement or otherwise modify the database 3) A function called from a DML statement cannot read or modify the table on which the DML was fired. / Create or Replace Package Body comm_package Is Function validate_comm(p_comm in number) return Boolean Is v_max_comm number. End tax_calc_pack. If v_max_comm >=p_comm then return(TRUE). Else return(FALSE). End tax_calc_pack. End validate_comm. Begin return(p_value*v_rate). / Create or Replace Package Body tax_calc_pack Is Function tax_calc(p_value in number) return number Is v_rate number :=0. End tax_calc. PERSISTENT State of a Package Create or Replace Package comm_package Is g_comm number :=10.08. End if. procedure reset_comm(p_comm in number). end comm_package.tax_calc(salary). / To use the packaged function : Select tax_calc_pack.Restrictions on Package Functions 1) A function called from a query or DML statement cannot end the current transaction. Begin Select max(commission_pct) into v_max_comm from employees. salary from emp. Create or Replace Package tax_calc_pack Is Function tax_calc(p_value in number) return number. .

since user Y did not complete his transaction.3 1000 1100 1145 . Else raise_application_error(-20210.4 Execute comm_package. Max_comm=0.reset_comm(0.reset_comm(0. Invalid Commission Rollback .6) For this user.4.4.4>0.reset_comm(0.5 Hence g_comm=0.25 Hence g_comm=0.reset_comm(0.25) Assume maximum is 0.0.5 is Invalid Hence.9) Execute comm_package. End reset_comm.4>0. Exit Logged In again Since the earlier transaction was rolled back.3 Hence g_comm=0. End comm_package.Procedure reset_comm(p_comm IN number) Is Begin If validate_comm(p_comm) then g_comm:=p_comm. Max_comm=0.4>0. commission_pct) values(‘Ram’.5 Execute comm_package.25 User Y 0930 0935 Insert into employees(empno.9>0. Max_comm=0. End if.5) Now maximum is 0. maximum is still 0.’Invalid Commission’).3) Max_comm=0.9. / Time 0900 User X Execute comm_package. max_comm is 0.

Procedure p2 is Begin Loop Fetch c1 into v_empno. / The cursor is opened in P1. Exit when c1%rowcount>=6. Thus packages maintain a persistent state of the package cursors. End loop.put_line(‘Employee Number :’ || (v_empno)). . Procedure p1. three rows are fetched and displayed. and the cursor is not closed. When we continue to fetch in P2. End pack_cur. Dbms_output. Dbms_output. Close c1.put_line(‘Employee Number :’ || (v_empno)). the next three rows are fetched and displayed. End pack_cur. End p2. / Create or Replace Package Body pack_cur Is v_empno number. The persistent state of a cursor/variable is maintained in a session of a user. Procedure p1 is Begin Open c1. The state does not persist across several sessions of the same user or acroos different users. End loop. Procedure p2. End p1.Persistent State of a Packaged Cursor Create or Replace Package pack_cur Is Cursor c1 is select empno from emp order by empno desc. Loop Fetch c1 into v_empno. Exit when c1%rowcount>=3.

The BFILE column stores a file locator that points to the external file LOBs are characterized in two ways : Internal LOBs(CLOB. resume CLOB. graphic images. video clippings. NCLOB. . similar to LONG RAW. BLOB) stored in the database External files(BFILE) stored outside the database. There are 4 large object data types BLOB for Binary large objects such as video clip CLOB for character large objects NCLOB for multibyte chracter large objects BFILE for a binary file stored at the OS level outside the database. the following interfaces are used : PL/SQL package DBMS_LOB Oracle Call Interface(OCI) Oracle Objects for Object Linking & Embediing(OLE) Pro*C/C++/Pro*COBOL precompilers JDBC Suppose you have the following table : Create table employee (emp_id number(5). photo BLOB). lname varchar2(25). but the LOB locator is stored in the row. Internal LOBs : They are stored inside the Oracle server in the LOB segment.LOB LOB is a data type to store large. parameter or return value(result) BLOB is interpreted by the Oracle server as a bit-stream. CLOB is interpreted by the Oracle server as a single-byte character stream NCLOB is interpreted by the Oracle server as a multiple-byte character stream. A BLOB< CLOB or NCLOB can be used in one of the following : Column of a table Attribute of a user-defined type PL SQL variable. based on the byte-length of the national character set To interact with LOB. BFILEs can be accessed only in the read-only mode from an Oracle server Components of a LOB : The 2 distinct components of an LOB are : LOB value : It is the data that constitutes the real object being stored LOB locator : It is a pointer to the location of the LOB value stored inside the database The LOB value may be stored anywhere in the database. etc. fname varchar2(25). unstructured data such as text.

MCP. Now we can put values as follows : Insert into employee values(10.write(lobloc. OCP’. -. ‘Hemant’. text). NULL). You could have done the initialization work at the time of table definition as follows : Create table employee (emp_id number(5). amount to be written. Updating CLOB using DBMS_LOB in PL/SQL : Declare lobloc clob.Tech. Select resume from employee.MCDBA. fname varchar2(25).D’. NULL).getlength(lobloc)+2. ‘MCA. it must contain a locator that points to an empty or populated LOB value. Pangam’. Insert into employee values(20. amount :=length(text). resume CLOB default empty_clob(). ‘M. Now the columns have been initialized. that is. MCP. ‘Hemant’. but not yet populated by data. lname varchar2(25). ---For update locks the row and returns the LOB locator for the ---resume lob column offset :=DBMS_LOB. then you could have used UPDATE command. empty_clob(). amount number. -.’ Pangam’. such columns must be made non-null. This can be done through the insert or update statements as follows : Insert into employee empty_blob()). You may initialize CLOB and BLOB columns by using the functions EMPTY_CLOB() and EMPTY_CLOB() functions respectively. --serves as the LOB locator text varchar2(30000):='Corporate Trainer'. photo BLOB default empty_blob()). offset. dbms_lob.MCDBA. ‘Pangam’.amount of data to be written offset number. OCP Ph.Before you start writing data to CLOB/BLOB columns using DBMS_LOB package or OCI(oracle call interface) . -. If the record is already there.write at lob location. amount.where to start writing Begin Select resume into lobloc from employee where emp_id=10 FOR Update.’ ‘Manoj’. values(10. from where and text to write . MCSD. MCSD.

insert into x values(‘c2’.text:='Corporate Consultant cum System Analyst'.append at lob location. 5). / Selecting CLOB values using DBMS_LOB select dbms_lob. -. Begin Select resume into text from employee where emp_id=10. Use the BFILENAME function to inset values as follows. bfilename('saloni'. 'Cor') from employee Selecting CLOB values in PL/SQL Declare Text varchar2(4000).writeappend(lobloc.bmp are existing in the folder : insert into x values(‘c1’. Amount:=length(text) . ensuring tha the files c1.'c2. amount. Select resume into lobloc from employee where emp_id=20 FOR Update. Managing BFILES Create a directory ‘saloni’ as a oracle user and give the path of the directory which contains your files as follows : Create or replace directory SALONI as ‘d:\saloni\saloni’ Give read privileges to users on that directory as follows : grant read on directory SALONI to public.instr(resume.'c1.bmp and c2. amount to be written and text to write commit.bmp')) . bfilename('saloni'. col2 bfile). text). dbms_lob. dbms_lob. Dbms_output.substr(resume. / Removing LOBs To delete row containing LOBs : Delete from employee where emp_id=30. 5.put_line(‘Resume is : ‘ || text). create the following table : create table x(col1 varchar2(10). End. To disassociate a LOB value from a row: Update employee set resume =empty_clob() where emp_id=40 To Add LOB columns Alter table table_name add(col1 CLOB. End.bmp')). Col2 BLOB).

v_filename varchar2(20). you may now use subsequent read operations on BFILE using the PL/SQL dbms_lob package and OCI.bmp'. v_filename). dbms_output. cursor emp_cursor is select col1 from x for update.Once physical files are associated with the records using SQL. Then the following procedure is used to load a BFILE pointer to an image of each employee into the table ‘X’ using DBMS_LOB package Create or Replace procedure load_emp (p_file_loc IN varchar2) IS v_file BFILE. Begin For erec IN emp_cursor Loop v_filename:=erec. v_file:=BFILENAME(p_file_loc. / .put_line('Loaded File :' || v_filename ||' size : '|| dbms_lob. dbms_lob. dbms_lob.fileopen(v_file).col1||'. End load_emp.getlength(v_file)). End loop. update x set col2=v_file where current of emp_cursor.fileclose(v_file).

Sign up to vote on this title
UsefulNot useful