Oracle PL/SQL Programming: A Developer's Workbook

Intermediate

Q:
4-21.	The steps listed in the problem are performed in the following order: The executable section terminates immediately. Control is passed to the exception section, if it exists. If there is an exception section, find a match for the error and then execute that handler code. If there is no match for the error, check for a WHEN OTHERS section and execute that handler code. If after executing handler code, an exception is raised (or re-raised), and there is no enclosing block, propagate the exception out to the calling environment. If after executing handler code, an exception is raised (or re-raised), propagate the exception out to the enclosing block. If there is no match and no WHEN OTHERS clause, propagate the exception out to the enclosing block. Oracle logs the exception to the alert log for the database. The following steps are not performed by the database: Oracle goes to the package STANDARD to determine how to handle the error. Oracle first checks to see if the code is being called from another block before propagating the exception to the calling environment. Oracle does not automatically log exceptions to the alert log for the instance. The alert log tracks physical database problems and abnormal conditions, and does not have anything to do with errors generated programmatically.
Q:
4-22.	Here are the restrictions: Parameter Restrictions Error Number The number must be an integer or an integer expression returning a number in the range –20000 to –20999. Error Message The message ...