Why is it good practice to place an 'others' exception handler in the outermost block of a PL/SQL program unit?

Why is it good practice to place an 'others' exception handler in the outermost block of a PL/SQL program unit?  
Choice 1  
 This method provides a handler to which any exceptions not handled by specific exception handlers will be propagated.  
Choice 2  
 'others' is the most inefficient exception handler and it should be placed as a last resort after all other exceptions have been handled.  
Choice 3  
 Exception handling is a bad practice in general and should be avoided.  
Choice 4  
 'others' exception handlers should be used sparingly because their definition provides the least possible information about the exceptions they trap.  
Choice 5  
 If 'others' is placed before explicitly-stated exception handlers, it will catch all exceptions and over-ride the ability of the explicit handlers to execute.  
DamanAsked:
Who is Participating?
 
KirilloffConnect With a Mentor Commented:
[modder]
0
 
RMZCommented:
This method provides a handler to which any exceptions not handled by specific exception handlers will
be propagated.  
0
 
modderCommented:
Hello Daman

I would like to point you to the member agreement. You can find a link to that on the bottom of every page.

Specifically the Guidelines for use, in which it states that Experts Exchange shall not be used for

* violating the guidelines for academic honesty or other unethical behavior.

In other words:

Experts-Exchange is not a homework service. Please stop using it for this purpose.

Kirilloff, I've reduced the points to zero.

modder
Community Support Moderator@Experts-Exchange
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.