The use of a stand alone RAISE statement

Question

What is the point of having a standalone RAISE statment (ie a RAISE statement without arguments).
BEGIN
DECLARE
e_UserDefinedException EXCEPTION;
BEGIN
RAISE e_UserDefinedException;
END;
EXCEPTION
WHEN OTHERS THEN
/* Just re-raise the exception, which will be propagated to the
calling environment */
RAISE;  --the standalone RAISE statement
END;
/When i create a package with several functions and procedures inside I always create a caller procedure called callProcs, which will execute various procedures in the appropriate order.
procedure callProcs(p_ship_type in varchar2)
     is
             --execute proc1
                 procedure1();
          --execute proc2.
          procedure2();
          --execute proc3.
          procedure3();
          --execute proc4.
          procedure4();
       --commit the transaction.
          commit;
              exception
                    when others then
                    err_msg:=SQLERRM;
                   --dbms_output.put_line (err_msg);
                  dbms_output.put_line('Rolling Back');
                      rollback;
end package_name;
/proc1,proc2 and proc3 has Exception handling like the following
exception
when others
THEN
error_message :='My custom message for the particular proc '||SQLERRM;
dbms_output.put_line(error_message);
logerror(error_message); --an autonomous error logging proc
end;According to the documentation, i should include a standalone RAISE statement like below so that the error is propogated out to calling environment ie.callProcs procedure. But this RAISE statement is not necessary. Right?
exception
      when others
      THEN
      error_message :='My custom message for the particular proc '||SQLERRM;
      dbms_output.put_line(error_message);
      logerror(error_message); --an autonomous error logging proc
      RAISE;
end;

Answer 1

The RAISE is used inside the exception handler_.
If you "handle" the error and are satisfied that it has been handled then there is no need to RAISE it back up to the calling code.
If you are just capturing the error i.e. to log it, but you aren't handling it then you should RAISE it back up to the calling code. Somewhere up the chain of calls the error should get handled or, if not, it will exit out of the top of the code and the error will be given to the program that called the code e.g. SQL*Plus etc. which can choose what it does with the error (usually displaying it to the user).
PL/SQL 101 : Exception Handling
PL/SQL 101 : Exception Handling