Oracle Error Number Variable
Contents |
shot at without result. —Winston Churchill Run-time errors arise from design faults, coding mistakes, hardware failures, and many sqlerrm in oracle other sources. Although you cannot anticipate all possible errors, you ora-06502 can plan to handle certain kinds of errors meaningful to your PL/SQL program. With many programming
Oracle Exception
languages, unless you disable error checking, a run-time error such as stack overflow or division by zero stops normal processing and returns control to the operating system.
Ora-06512
With PL/SQL, a mechanism called exception handling lets you "bulletproof" your program so that it can continue operating in the presence of errors. This chapter contains these topics: Overview of PL/SQL Runtime Error Handling Advantages of PL/SQL Exceptions Summary of Predefined PL/SQL Exceptions Defining Your Own PL/SQL Exceptions How PL/SQL Exceptions Are Raised How raise_application_error PL/SQL Exceptions Propagate Reraising a PL/SQL Exception Handling Raised PL/SQL Exceptions Tips for Handling PL/SQL Errors Overview of PL/SQL Compile-Time Warnings Overview of PL/SQL Runtime Error Handling In PL/SQL, an error condition is called an exception. Exceptions can be internally defined (by the runtime system) or user defined. Examples of internally defined exceptions include division by zero and out of memory. Some common internal exceptions have predefined names, such as ZERO_DIVIDE and STORAGE_ERROR. The other internal exceptions can be given names. You can define exceptions of your own in the declarative part of any PL/SQL block, subprogram, or package. For example, you might define an exception named insufficient_funds to flag overdrawn bank accounts. Unlike internal exceptions, user-defined exceptions must be given names. When an error occurs, an exception is raised. That is, normal execution stops and control transfers to the exception-handling part of your PL/SQL block or subprogram. Internal exceptions are raised implicitly (automatically) by the run-time system. Use
Oracle error is no data found, in which case
Pragma Exception_init
SQLCODE returns +100. For user-defined exceptions, SQLCODE returns +1, ora-01403 or a value you assign if the exception is associated with an Oracle sqlcode error number through pragma EXCEPTION_INIT. Syntax sqlcode function ::= Description of the illustration sqlcode_function.gif Usage Notes SQLCODE is only useful in an https://docs.oracle.com/cd/B13789_01/appdev.101/b10807/07_errs.htm exception handler. Outside a handler, SQLCODE always returns 0. SQLCODE is especially useful in the OTHERS exception handler, because it lets you identify which internal exception was raised. You cannot use SQLCODE directly in a SQL statement. Assign the value of SQLCODE to a local https://docs.oracle.com/cd/B19306_01/appdev.102/b14261/sqlcode_function.htm variable first. When using pragma RESTRICT_REFERENCES to assert the purity of a stored function, you cannot specify the constraints WNPS and RNPS if the function calls SQLCODE. Examples Example 13-6 shows the use of SQLCODE and SQLERRM. Example 13-6 Using SQLCODE and SQLERRM DECLARE name employees.last_name%TYPE; v_code NUMBER; v_errm VARCHAR2(64); BEGIN SELECT last_name INTO name FROM employees WHERE employee_id = 1000; EXCEPTION WHEN OTHERS THEN v_code := SQLCODE; v_errm := SUBSTR(SQLERRM, 1 , 64); DBMS_OUTPUT.PUT_LINE('The error code is ' || v_code || '- ' || v_errm); END; / For examples, see the following: Example 10-11, "Displaying SQLCODE and SQLERRM" Related Topics "Exception Definition" "SQLERRM Function" "Retrieving the Error Code and Error Message: SQLCODE and SQLERRM" Scripting on this page enhances content navigation, but does not change the content in any way.
Server MySQL MariaDB PostgreSQL SQLite MS Office Excel Access Word Web Development HTML CSS Color Picker Languages C Language More ASCII Table Linux UNIX Java https://www.techonthenet.com/oracle/exceptions/sqlerrm.php Clipart Techie Humor Advertisement Oracle Basics Oracle Advanced Oracle Cursors Oracle Exception Handling Named Programmer-Defined Exception Named System Exception WHEN OTHERS Clause SQLCODE SQLERRM Oracle Foreign Keys Oracle Loops/Conditionals http://www.java2s.com/Tutorial/Oracle/0480__PL-SQL-Programming/Errormessagecodeandtext.htm Oracle Transactions Oracle Triggers String/Char Functions Numeric/Math Functions Date/Time Functions Conversion Functions Analytic Functions Advanced Functions NEXT: Declare Cursor Oracle / PLSQL: SQLERRM Function This Oracle tutorial explains oracle error how to use the Oracle/PLSQL SQLERRM function with syntax and examples. What does the SQLERRM Function do? The SQLERRM function returns the error message associated with the most recently raised error exception. This function should only be used within the Exception Handling section of your code. Syntax The syntax for the SQLERRM function in Oracle/PLSQL is: SQLERRM oracle error number Parameters or Arguments There are no parameters or arguments for the SQLERRM function. Note See also the SQLCODE function. Example Since EXCEPTION HANDLING is usually written with the following syntax: EXCEPTION WHEN exception_name1 THEN [statements] WHEN exception_name2 THEN [statements] WHEN exception_name_n THEN [statements] WHEN OTHERS THEN [statements] END [procedure_name]; You could use the SQLERRM function to raise an error as follows: EXCEPTION WHEN OTHERS THEN raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM); END; Or you could log the error to a table using the SQLERRM function as follows: EXCEPTION WHEN OTHERS THEN err_code := SQLCODE; err_msg := SUBSTR(SQLERRM, 1, 200); INSERT INTO audit_table (error_number, error_message) VALUES (err_code, err_msg); END; NEXT: Declare Cursor Share this page: Advertisement Back to top Home | About Us | Contact Us | Testimonials | Donate While using this site, you agree to have read and accepted our Terms of Service and Privacy Policy. We use advertisements to support this website and fund the development of new content. Copyright © 2003-2016 TechOnTheNet.com. All rights reserved.
FunctionsRegular Expressions FunctionsStatistical FunctionsLinear Regression FunctionsPL SQL Data TypesPL SQL StatementsPL SQL OperatorsPL SQL ProgrammingCursorCollectionsFunction Procedure PackagesTriggerSQL PLUS Session EnvironmentSystem Tables Data DictionarySystem PackagesObject OrientedXMLLarge ObjectsTransactionUser PrivilegeError message code and text : Handle Exception«PL SQL Programming«Oracle PL/SQL TutorialOracle PL/SQL TutorialPL SQL ProgrammingHandle ExceptionSQL> DECLARE 2 e_TooManyEmployee EXCEPTION; -- Exception to indicate an error condition 3 v_ErrorCode NUMBER; -- Variable to hold the error message code 4 v_ErrorText VARCHAR2(200); -- Variable to hold the error message text 5 6 BEGIN 7 RAISE e_TooManyEmployee; 8 EXCEPTION 9 WHEN e_TooManyEmployee THEN 10 DBMS_OUTPUT.put_line('e_TooManyEmployee'); 11 v_ErrorText := SUBSTR(SQLERRM, 1, 200); -- Note the use of SUBSTR here. 12 DBMS_OUTPUT.put_line(v_ErrorText); 13 /* SQLERRM(0) */ 14 v_ErrorText := SUBSTR(SQLERRM(0), 1, 200); 15 DBMS_OUTPUT.put_line(v_ErrorText); 16 17 /* SQLERRM(100) */ 18 v_ErrorText := SUBSTR(SQLERRM(100), 1, 200); 19 DBMS_OUTPUT.put_line(v_ErrorText); 20 21 /* SQLERRM(10) */ 22 v_ErrorText := SUBSTR(SQLERRM(10), 1, 200); 23 DBMS_OUTPUT.put_line(v_ErrorText); 24 25 /* SQLERRM with no argument */ 26 v_ErrorText := SUBSTR(SQLERRM, 1, 200); 27 DBMS_OUTPUT.put_line(v_ErrorText); 28 29 /* SQLERRM(-1) */ 30 v_ErrorText := SUBSTR(SQLERRM(-1), 1, 200); 31 DBMS_OUTPUT.put_line(v_ErrorText); 32 33 /* SQLERRM(-54) */ 34 v_ErrorText := SUBSTR(SQLERRM(-54), 1, 200); 35 DBMS_OUTPUT.put_line(v_ErrorText); 36 37 38 WHEN OTHERS THEN 39 v_ErrorCode := SQLCODE; 40 END; 41 / e_TooManyEmployee User-Defined Exception ORA-0000: normal, successful completion ORA-01403: no data found -10: non-ORACLE exception User-Defined Exception ORA-00001: unique constraint (.) violated ORA-00054: resource bu