Skip to main content

How to Upgrade Your RAM and SSD on Ubuntu: A Complete Guide 2025 - 2026 midway

Exception Handling

Exception Handling

In this section we will discuss about the following,
1) What is Exception Handling.
2) Structure of Exception Handling.
3) Types of Exception Handling.
1) What is Exception Handling?
PL/SQL provides a feature to handle the Exceptions which occur in a PL/SQL Block known as exception Handling. Using Exception Handling we can test the code and avoid it from exiting abruptly. When an exception occurs a messages which explains its cause is recieved.
PL/SQL Exception message consists of three parts.
1) Type of Exception
2) An Error Code
3) A message

By Handling the exceptions we can ensure a PL/SQL block does not exit abruptly.
2) Structure of Exception Handling.
The General Syntax for coding the exception section
 DECLARE
   Declaration section
 BEGIN
   Exception section
 EXCEPTION
 WHEN ex_name1 THEN
    -Error handling statements
 WHEN ex_name2 THEN
    -Error handling statements
 WHEN Others THEN
   -Error handling statements
END;
General PL/SQL statments can be used in the Exception Block.
When an exception is raised, Oracle searches for an appropriate exception handler in the exception section. For example in the above example, if the error raised is 'ex_name1 ', then the error is handled according to the statements under it. Since, it is not possible to determine all the possible runtime errors during testing fo the code, the 'WHEN Others' exception is used to manage the exceptions that are not explicitly handled. Only one exception can be raised in a Block and the control does not return to the Execution Section after the error is handled.
If there are nested PL/SQL blocks like this.
 DELCARE
   Declaration section
 BEGIN
    DECLARE
      Declaration section
    BEGIN
      Execution section
    EXCEPTION
      Exception section
    END;
 EXCEPTION
   Exception section
 END;

In the above case, if the exception is raised in the inner block it should be handled in the exception block of the inner PL/SQL block else the control moves to the Exception block of the next upper PL/SQL Block. If none of the blocks handle the exception the program ends abruptly with an error.

Comments

Popular posts from this blog

Shopify fully custom contact section block on home page

Tech Easy Solutions Shopify fully custom contact section block on home page <section class="contact-information" >       <!--<div class="left-shape">         <img src="images/left-shape.png" class="img-fluid">       </div>-->       <div class="container c-container">         <div class="row">           <div class="col-lg-6 col-md-6 col-sm-12 col-12">             <div class=" contact-us">                         {% form 'contact' %}                       {% if form.posted_successfully? %}                        <center> <p class="note form-success">                   ...

Fixing PHP 8.2 zip Extension Error on Ubuntu 25 for Laravel 10,11,12 Shopify Apps

Tech Easy Solutions           Solution : How to Fix PHP 8.2 zip Extension Error on Ubuntu 25 Since Ubuntu 25’s PPAs don’t yet support this extension directly, there are three approaches to fix this: server  / local Ubuntu   Compile the Zip Extension from Source (Recommended) Install development packages: $ sudo apt-get install php8.2-dev libzip-dev build-essential unzip Install the zip extension via PECL:  $ sudo pecl install zip Enable the extension:  $ echo "extension=zip.so" | sudo tee /etc/php/8.2/cli/conf.d/20-zip.ini $ echo "extension=zip.so" | sudo tee /etc/php/8.2/fpm/conf.d/20-zip.ini Restart PHP services : $ sudo systemctl restart php8.2-fpm Verify $ :  php -m | grep zip ____________________________________________________ Result :  Error tracer : Why This Error Happens When running a Laravel 12 Shopify project on Ubuntu 25, you might see an error like: php8 .2 - zip : Depends: libzip4t64 (>= 1....

Fatal error: Allowed memory size of 67108864 bytes exhausted wordpress

Fatal error: Allowed memory size of 67108864 bytes exhausted wordpress open your file manager then goto wordpress directory wp-include -> then   default-constants.php change a memory size values 64 to 256 or your need modifications see below light blue color  in default-constants.php   <?php /**  * Defines constants and global variables that can be overridden, generally in wp-config.php.  *  * @package WordPress  */ /**  * Defines initial WordPress constants  *  * @see wp_debug_mode()  *  * @since 3.0.0  *  * @global int $blog_id  */ function wp_initial_constants() {  global $blog_id;  /**#@+   * Constants for expressing human-readable data sizes in their respective number of bytes.   *   * @since 4.4.0   */  define( 'KB_IN_BYTES', 1024 );  define( 'MB_IN_BYTES', 1024 * KB_IN_BYTES );  define( 'GB_IN_BYTES', 1024 * MB_IN_BYTES ); ...