Begin parameter description in pl sql, PL-SQL Programming

BEGIN Parameter Description in pl sql:


This keyword signals the beginning of the executable section of a PL/SQL block, that contains executable statements. The executable section of a block is needed. That is, the PL/SQL block should contain at least one executable statement. The NULL statement meets this necessity.


This is an executable (that is not declarative) statement which you use to create the algorithms. A series of statements can involve the procedural statements like RAISE, SQL statements like the UPDATE, and PL/SQL blocks (sometimes known as the "block statements").

The PL/SQL statements are free format. That is, they can continue from line to line if you do not crack keywords, delimiters, or literals across the lines. A semicolon (;) serve as the statement terminator.

The PL/SQL supports a subset of the SQL statements which involves the cursor control, data manipulation, and transaction control statements but exclude the data definition and data control statements like CREATE, ALTER, GRANT, and REVOKE.


This keyword signals the beginning of the exception-handling section of the PL/SQL block. When an exception is raised, the normal execution of the block stops and control transfers to the suitable exception handler. After the exception handler complete, the execution proceeds with the statement following the block.

If there is no exception handler for the raised exception in the present block, the control passes to the enclosing block. This process repeat until an exception handler is found or there are no more enclosing blocks. If the PL/SQL can find no exception handler for the exception, the execution stops and an unhandled exception error is returned to the host atmosphere.


This construct relates an exception with a series of statements that is executed when the exception is raised.


This keyword signals the end of the PL/SQL block. It should be the last keyword in a block. Neither the END IF in an IF statement nor the END LOOP in a LOOP statement can replace for the keyword END. The END does not signal the end of a transaction. Merely as a block can span the multiple transactions, a transaction can span the multiple blocks.

Posted Date: 10/6/2012 8:56:33 AM | Location : United States

Related Discussions:- Begin parameter description in pl sql, Assignment Help, Ask Question on Begin parameter description in pl sql, Get Answer, Expert's Help, Begin parameter description in pl sql Discussions

Write discussion on Begin parameter description in pl sql
Your posts are moderated
Related Questions
Row Operators The Row operators return or reference the particular rows. ALL retains the duplicate rows in the result of a query or in an aggregate expression. The DISTINCT el

Rollback Behavior When a FORALL statement fails, the database changes are rolled back to an implicit savepoint marked before each of the SQL statement execution. The Changes t

Projection in SQL - correct version Student StudentId is enrolled on some course. SELECT DISTINCT StudentId FROM IS_ENROLLED_ON In more complicated examples it is someti

Initializing Records The illustration below shows that you can initialize a record in its type definition. Whenever you declare a record of the type TimeRec, its 3 fields supp

Application to Export Excel Data to MSSQL Server table I am having a table available in excel format and features the subsequent: - Some text is in Arabic (e.g. UTF-8 encodin

Definition of FROM - SQL Recall that the operand of FROM is denoted by a commalist, each element of that commalist being a table expression optionally accompanied by a range v

Parameter and Keyword Description: dynamic_string: This is a string variable, literal, or expression which represents a SQL statement or the PL/SQL block. define_vari

SSRS Report Writing Project Description: This report is part of a larger project to make a SQL Server Reporting Service (SSRS) based reporting solution. There can be more rep

SQL Cursor   The Oracle implicitly opens a cursor to process each SQL statement not related with an explicit cursor. The PL/SQL refers to the most current implicit cursor as t

Selecting Objects: Suppose that you have run the SQL*Plus script below that creates object type Person and object table persons, and that you have settled the table: CREATE