Tài liệu Oracle PL/SQL by Example- P5 docx

for a particular student. The second exception, TOO_MANY_ROWS, is raised if a particular student is enrolled in more than one course. Consider what happens if you run this example for three different values of student ID: 102, 103, and 319. The first run of the example (student ID is 102) produces the following output: Enter value for sv_student_id: 102 old 2: v_student_id NUMBER := &sv_student_id; new 2: v_student_id NUMBER := 102; Check if the student is enrolled Student is enrolled in too many courses PL/SQL procedure successfully completed. The first time, a user entered 102 for the value of student ID. Next, the first DBMS_OUTPUT. PUT_LINE statement is executed, and the message Check if the is displayed on the screen. Then the SELECT INTO statement is executed. You probably noticed that the DBMS_OUTPUT.PUT_LINE statement following the SELECT INTO statement was not executed. When the SELECT INTO statement is executed for student ID 102, multiple rows are returned. Because the SELECT INTO statement can return only a single row, control is passed to the exception-handling section of the block. Next, the PL/SQL block raises the proper excep- tion. As a result, the message Student is enrolled in too many courses is displayed on the screen, and this message is specified by the exception TOO_MANY_ROWS. DID YOU KNOW? Built-in exceptions are raised implicitly.Therefore, you only need to specify what action must be taken in the case of a particular exception. A second run of the example (student ID is 103) produces the following output: Enter value for sv_student_id: 103 old 2: v_student_id NUMBER := &sv_student_id; new 2: v_student_id NUMBER := 103; Check if the student is enrolled The student is enrolled into one course PL/SQL procedure successfully completed. In this second run, a user entered 103 for the value of student ID. As a result, the first DBMS_OUTPUT.PUT_LINE statement is executed, and the message Check if the is displayed on the screen. Then the SELECT INTO statement is executed. When the SELECT INTO statement is executed for student ID 103, a single row is returned. Next, the DBMS_OUTPUT.PUT_LINE statement following the SELECT INTO statement is executed. As a result, the message The student is enrolled into one course is displayed on the screen. Notice that for this value of the variable v_student_id, no exception has been raised. LAB 8.2 172 Built-in Exceptions Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. A third run of the example (student ID is 319) produces the following output: Enter value for sv_student_id: 319 old 2: v_student_id NUMBER := &sv_student_id; new 2: v_student_id NUMBER := 319; Check if the student is enrolled The student is not enrolled PL/SQL procedure successfully completed. This time, a user entered 319 for the value of student ID. The first DBMS_OUTPUT.PUT_LINE statement is executed, and the message Check if the is displayed on the screen. Then the SELECT INTO statement is executed. When the SELECT INTO statement is executed for student ID 319, no rows are returned. As a result, control is passed to the exception-handling section of the PL/SQL block, and the proper exception is raised. In this case, the NO_DATA_FOUND exception is raised because the SELECT INTO statement failed to return a single row. Thus, the message The student is not enrolled is displayed on the screen. So far, you have seen examples of exception-handling sections that have particular exceptions, such as NO_DATA_FOUND and ZERO_DIVIDE. However, you cannot always predict what exception might be raised by your PL/SQL block. For cases like this, there is a special exception handler called OTHERS. All predefined Oracle errors (exceptions) can be handled with the use of the OTHERS handler. Consider the following: FOR EXAMPLE DECLARE v_instructor_id NUMBER := &sv_instructor_id; v_instructor_name VARCHAR2(50); BEGIN SELECT first_name||' '||last_name INTO v_instructor_name FROM instructor WHERE instructor_id = v_instructor_id; DBMS_OUTPUT.PUT_LINE ('Instructor name is '||v_instructor_name); EXCEPTION WHEN OTHERS THEN DBMS_OUTPUT.PUT_LINE ('An error has occurred'); END; When run, this example produces the following output: Enter value for sv_instructor_id: 100 old 2: v_instructor_id NUMBER := &sv_instructor_id; new 2: v_instructor_id NUMBER := 100; An error has occurred PL/SQL procedure successfully completed. LAB 8.2 Built-in Exceptions 173 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. ▼ This demonstrates not only the use of the OTHERS exception handler, but also a bad program- ming practice. The exception OTHERS has been raised because there is no record in the INSTRUCTOR table for instructor ID 100. This is a simple example, where it is possible to guess what exception handlers should be used. However, in many instances you may find a number of programs that have been written with a single exception handler, OTHERS. This is a bad programming practice, because such use of this exception handler does not give you or your user good feedback. You do not really know what error has occurred. Your user does not know whether he or she entered some information incor- rectly. Two special error-reporting functions, SQLCODE and SQLERRM, are very useful when used with the OTHERS handler. You will learn about them in Chapter 10, “Exceptions: Advanced Concepts.” LAB 8.2 EXERCISES This section provides exercises and suggested answers, with discussion related to how those answers resulted.The most important thing to realize is whether your answer works.You should figure out the implications of the answers and what the effects are of any different answers you may come up with. 8.2.1 Use Built-in Exceptions In this exercise, you learn more about some built-in exceptions discussed earlier in this chapter. Create the following PL/SQL script: ch08_2a.sql, version 1.0 SET SERVEROUTPUT ON DECLARE v_exists NUMBER(1); v_total_students NUMBER(1); v_zip CHAR(5):= '&sv_zip'; BEGIN SELECT count(*) INTO v_exists FROM zipcode WHERE zip = v_zip; IF v_exists != 0 THEN SELECT COUNT(*) INTO v_total_students FROM student WHERE zip = v_zip; DBMS_OUTPUT.PUT_LINE ('There are '||v_total_students||' students'); ELSE DBMS_OUTPUT.PUT_LINE (v_zip||' is not a valid zip'); END IF; LAB 8.2 174 Lab 8.2 Exercises Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. EXCEPTION WHEN VALUE_ERROR OR INVALID_NUMBER THEN DBMS_OUTPUT.PUT_LINE ('An error has occurred'); END; This script contains two exceptions,VALUE_ERROR and INVALID_NUMBER. However, only one exception handler is written for both exceptions.You can combine different exceptions in a single exception handler when you want to handle both exceptions in a similar way. Often the exceptions VALUE_ERROR and INVALID_NUMBER are used in a single exception handler because these Oracle errors refer to the conversion problems that may occur at runtime. To test this script fully, execute it three times. For the first run, enter 07024, for the second run, enter 00914, and for the third run, enter 12345 for the variable v_zip. Execute the script, and then answer the following questions: A) What output is printed on the screen (for all values of zip)? ANSWER: The first version of the output is produced when the value of zip is 07024.The second version of the output is produced when the value of zip is 00914.The third version of the output is produced when the value of zip is 12345. The output should look like the following: Enter value for sv_zip: 07024 old 4: v_zip CHAR(5):= '&sv_zip'; new 4: v_zip CHAR(5):= '07024'; There are 9 students PL/SQL procedure successfully completed. When you enter 07024 for the variable v_zip, the first SELECT INTO statement is executed.This SELECT INTO statement checks whether the value of zip is valid, or, in other words, if a record exists in the ZIPCODE table for a given value of zip. Next, the value of the variable v_exists is evaluated with the help of the IF statement. For this run of the example, the IF statement evalu- ates to TRUE, and as a result, the SELECT INTO statement against the STUDENT table is evaluated. Next, the DBMS_OUTPUT.PUT_LINE following the SELECT INTO statement is executed, and the message There are 9 students is displayed on the screen. The output should look like the following: Enter value for sv_zip: 00914 old 4: v_zip CHAR(5):= '&sv_zip'; new 4: v_zip CHAR(5):= '00914'; There are 0 students PL/SQL procedure successfully completed. For the second run, the value 00914 is entered for the variable v_zip.The SELECT INTO state- ment against the STUDENT table returns one record, and the message There are 0 students is displayed on the screen. Because the SELECT INTO statement against the STUDENT table uses a group function, COUNT, there is no reason to use the exception NO_DATA_FOUND, because the COUNT function will always return data. LAB 8.2 Lab 8.2 Exercises 175 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. The output should look like the following: Enter value for sv_zip: 12345 old 4: v_zip CHAR(5):= '&sv_zip'; new 4: v_zip CHAR(5):= '12345'; 12345 is not a valid zip PL/SQL procedure successfully completed. For the third run, the value 12345 is entered for the variable v_zip.The SELECT INTO statement against the ZIPCODE table is executed. Next, the variable v_exists is evaluated with the help of the IF statement. Because the value of v_exists equals 0,the IF statement evaluates to FALSE.As a result, the ELSE part of the IF statement is executed.The message 12345 is not a valid zip is displayed on the screen. B) Explain why no exception was raised for these values of the variable v_zip. ANSWER: The exceptions VALUE_ERROR and INVALID_NUMBER were not raised because no conversion or type mismatch error occurred. Both variables, v_exists and v_total_students, were defined as NUMBER(1). The group function COUNT used in the SELECT INTO statement returns a NUMBER datatype. Moreover, on both occasions, the COUNT function returns a single-digit number. As a result, neither exception was raised. C) Insert a record into the STUDENT table with a zip having the value of 07024. INSERT INTO student (student_id, salutation, first_name, last_name, zip, registration_date, created_by, created_date, modified_by, modified_date) VALUES (STUDENT_ID_SEQ.NEXTVAL, 'Mr.', 'John', 'Smith', '07024', SYSDATE, 'STUDENT', SYSDATE, 'STUDENT', SYSDATE); COMMIT; Run the script again for the same value of zip (07024).What output is printed on the screen? Why? ANSWER: After a student has been added, the output should look like the following: Enter value for sv_zip: 07024 old 4: v_zip CHAR(5):= '&sv_zip'; new 4: v_zip CHAR(5):= '07024'; An error has occurred PL/SQL procedure successfully completed. After the student has been inserted into the STUDENT table with a zip having a value of 07024, the total number of students changes to 10 (remember,previously this number was 9). As a result, the SELECT INTO statement against the STUDENT table causes an error, because the variable v_total_students has been defined as NUMBER(1).This means that only a single-digit number can be stored in this variable.The number 10 is a two-digit number,so the exception INVALID_NUMBER is raised. As a result, the message An error has occurred is displayed on the screen. D) How would you change the script to display a student’s first name and last name instead of displaying the total number of students for any given value of a zip? Remember, the SELECT INTO statement can return only one record. LAB 8.2 176 Lab 8.2 Exercises Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. ANSWER: The new version of the script should look similar to the following. All changes are shown in bold. ch08_2b.sql, version 2.0 SET SERVEROUTPUT ON DECLARE v_exists NUMBER(1); v_student_name VARCHAR2(30); v_zip CHAR(5):= '&sv_zip'; BEGIN SELECT count(*) INTO v_exists FROM zipcode WHERE zip = v_zip; IF v_exists != 0 THEN SELECT first_name||' '||last_name INTO v_student_name FROM student WHERE zip = v_zip AND rownum = 1; DBMS_OUTPUT.PUT_LINE ('Student name is '||v_student_name); ELSE DBMS_OUTPUT.PUT_LINE (v_zip||' is not a valid zip'); END IF; EXCEPTION WHEN VALUE_ERROR OR INVALID_NUMBER THEN DBMS_OUTPUT.PUT_LINE ('An error has occurred'); WHEN NO_DATA_FOUND THEN DBMS_OUTPUT.PUT_LINE ('There are no students for this value of zip code'); END; This version of the program contains several changes.The variable v_total_students has been replaced by the variable v_student_name.The SELECT INTO statement against the STUDENT table has been changed as well. Another condition has been added to the WHERE clause: rownum = 1 You have seen in the previous runs of this script that for any given value of zip there could be multiple records in the STUDENT table. Because a SELECT INTO statement returns only a single row, the condition rownum = 1 has been added to it. Another way to deal with multiple rows returned by the SELECT INTO statement is to add the exception TOO_MANY_ROWS. Finally,another exception has been added to the program.The SELECT INTO statement against the STUDENT table does not contain any group functions.Therefore, for any given value of zip, the SELECT INTO statement might not return any data and might cause an error.As a result, the excep- tion NO_DATA_FOUND might be raised. LAB 8.2 Lab 8.2 Exercises 177 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. ▼ TRY IT YOURSELF In this chapter you’ve learned about built-in exceptions. Here are some projects that will help you test the depth of your understanding: 1) Create the following script: Check to see whether there is a record in the STUDENT table for a given student ID. If there is not, insert a record into the STUDENT table for the given student ID. 2) Create the following script: For a given instructor ID, check to see whether it is assigned to a valid instructor.Then check to see how many sections this instructor teaches, and display this informa- tion on the screen. The projects in this section are meant to have you use all the skills you have acquired throughout this chapter.The answers to these projects can be found in Appendix D and on this book’s companion Web site.Visit the Web site periodically to share and discuss your answers. 178 Try it Yourself Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 9 Exceptions CHAPTER OBJECTIVES In this chapter, you will learn about . Exception scope . User-defined exceptions . Exception propagation In the preceding chapter, you explored the concept of error handling and built- in exceptions. In this chapter you continue by examining whether an exception can catch a runtime error occurring in the declaration, executable, or exception- handling section of a PL/SQL block. You also will learn how to define your own exceptions and how to reraise an exception. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. LAB 9.1 Exception Scope LAB OBJECTIVE After completing this lab, you will be able to . Understand the scope of an exception You are already familiar with the term scope—for example, the scope of a variable. Even though variables and exceptions serve different purposes, the same scope rules apply to them. Now examine the scope of an exception by means of an example: FOR EXAMPLE DECLARE v_student_id NUMBER := &sv_student_id; v_name VARCHAR2(30); BEGIN SELECT RTRIM(first_name)||' '||RTRIM(last_name) INTO v_name FROM student WHERE student_id = v_student_id; DBMS_OUTPUT.PUT_LINE ('Student name is '||v_name); EXCEPTION WHEN NO_DATA_FOUND THEN DBMS_OUTPUT.PUT_LINE ('There is no such student'); END; In this example, you display the student’s name on the screen. If no record in the STUDENT table corresponds to the value of v_student_id provided by the user, the exception NO_DATA_FOUND is raised. Therefore, you can say that the exception NO_DATA_FOUND covers this block, or that this block is the scope of this exception. In other words, the scope of an exception is the portion of the block that is covered by this exception. LAB 9.1 180 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Now, you can expand on that: FOR EXAMPLE DECLARE v_student_id NUMBER := &sv_student_id; v_name VARCHAR2(30); v_total NUMBER(1); outer block BEGIN SELECT RTRIM(first_name)||' '||RTRIM(last_name) INTO v_name FROM student WHERE student_id = v_student_id; DBMS_OUTPUT.PUT_LINE ('Student name is '||v_name); inner block BEGIN SELECT COUNT(*) INTO v_total FROM enrollment WHERE student_id = v_student_id; DBMS_OUTPUT.PUT_LINE ('Student is registered for '|| v_total||' course(s)'); EXCEPTION WHEN VALUE_ERROR OR INVALID_NUMBER THEN DBMS_OUTPUT.PUT_LINE ('An error has occurred'); END; EXCEPTION WHEN NO_DATA_FOUND THEN DBMS_OUTPUT.PUT_LINE ('There is no such student'); END; The part of the example shown in bold has been added to the original version of the example. The new version of the example has an inner block added to it. This block has a structure similar to the outer block. It has a SELECT INTO statement and an exception section to handle errors. When a VALUE_ERROR or INVALID_NUMBER error occurs in the inner block, the exception is raised. It is important that you realize that the exceptions VALUE_ERROR and INVALID_ NUMBER have been defined for the inner block only. Therefore, they can be handled only if they are raised in the inner block. If one of these errors occurs in the outer block, the program is unable to terminate successfully. LAB 9.1 Exception Scope 181 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. [...]... be raised simultaneously When a PL/SQL block is not enclosed by another block, control is transferred to the host environment, and the program cannot complete successfully This is illustrated by the following example: FOR EXAMPLE DECLARE e_exception1 EXCEPTION; BEGIN RAISE e_exception1; END; The following error message is displayed: DECLARE * ERROR at line 1: ORA-06510: PL/SQL: unhandled user-defined... given zip code You use nested PL/SQL blocks to achieve the desired results The original PL/SQL script does not contain any exception handlers Therefore, you are asked to identify possible errors that may occur and define exception handlers for them Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark LAB 9.1 Lab 9.1 Exercises 184 Create the following PL/SQL script: ch9_1a.sql,... 9.1 Exercises LAB 9.1 187 An error has occurred Done PL/SQL procedure successfully completed Enter value for sv_zip: 07024 old 2: v_zip VARCHAR2(5) := '&sv_zip'; new 2: v_zip VARCHAR2(5) := '07024'; Check if provided zipcode is valid An error has occurred PL/SQL procedure successfully completed D) Explain the difference in the outputs produced by versions 2 and 3 of the script ANSWER: Version 2 of... declared in the declaration section of a PL/SQL block: DECLARE exception_name EXCEPTION; Notice that this declaration looks similar to a variable declaration You specify an exception name followed by the keyword EXCEPTION Consider the following code fragment: FOR EXAMPLE DECLARE e_invalid_id EXCEPTION; In this example, the name of the exception is prefixed by the letter e This syntax is not required,... Tom Wojick, teaches too much PL/SQL procedure successfully completed In the version of the script shown next, the DBMS_OUTPUT.PUT_LINE statement displaying how many sections are taught by the instructor has been moved from the ELSE portion of the IF-THENELSE statement as well This eliminates the ELSE portion of the IF-THEN-ELSE statement In this case, the output produced by the script contains the number... same error message twice The first message is generated by the assignment statement in the executable section of the block, and the second message is generated by the assignment statement of the exception-handling section of this block Based on this example, you may conclude that when a runtime error occurs in the exception-handling section of the PL/SQL block, the exception-handling section of this block... DBMS_OUTPUT.PUT_LINE ('An error has occurred in the '|| 'program'); END; When executed, this example produces the following output: An error has occurred in the program PL/SQL procedure successfully completed In this example, the PL/SQL block is enclosed by another block, and the program can complete This is possible because the exception defined in the outer block is raised when the error occurs in the exception-handling... the exception NO_DATA_FOUND can be raised by the inner block Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark Lab 9.1 Exercises LAB 9.1 183 because the SELECT INTO statement does not contain a group function, COUNT() This function always returns a result, so when no rows are returned by the SELECT INTO statement, the value returned by COUNT(*) equals 0 Now, run this example... is used in the exception-handling section of the inner block, it is not followed by the exception name When run, this example produces the following output: The error has occurred PL/SQL procedure successfully completed WATCH OUT! It is important to note that when an exception is reraised in the block that is not enclosed by any other block, the program is unable to complete successfully Consider the... v_instructor_id NUMBER := &sv_instructor_id; v_instructor_id NUMBER := 101; Fernand Hanks, teaches 9 sections PL/SQL procedure successfully completed Enter value for sv_instructor_id: 102 old 2: v_instructor_id NUMBER := &sv_instructor_id; new 2: v_instructor_id NUMBER := 102; This instructor teaches too much PL/SQL procedure successfully completed Please purchase PDF Split-Merge on www.verypdf.com to remove . what exception might be raised by your PL/SQL block. For cases like this, there is a special exception handler called OTHERS. All predefined Oracle errors (exceptions). salutation, first_name, last_name, zip, registration_date, created _by, created_date, modified _by, modified_date) VALUES (STUDENT_ID_SEQ.NEXTVAL, 'Mr.',