Pl/sql Error Codes List
Contents |
Churchill Run-time errors arise from design faults, coding mistakes, hardware failures, and many other sources. Although you cannot anticipate all possible errors, you can plan to handle certain oracle sql error codes kinds of errors meaningful to your PL/SQL program. With many programming languages,
Oracle Sqlerrm
unless you disable error checking, a run-time error such as stack overflow or division by zero stops normal processing and oracle error codes list with description returns control to the operating system. 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 discusses types of exceptions in oracle the following topics: Overview of PL/SQL Error Handling Advantages of PL/SQL Exceptions Predefined PL/SQL Exceptions Defining Your Own PL/SQL Exceptions How PL/SQL Exceptions Are Raised How PL/SQL Exceptions Propagate Reraising a PL/SQL Exception Handling Raised PL/SQL Exceptions Tips for Handling PL/SQL Errors Overview of PL/SQL Error Handling In PL/SQL, a warning or error condition is called an exception. Exceptions can be internally defined (by the
Exception No Data Found Oracle
run-time 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. User-defined exceptions must be raised explicitly by RAISE statements, which can also raise predefined exceptions. To handle raised exceptions, you write separate routines called exception handlers. After an exception handler runs, the current block stops executing and the enclosing block resumes with the next statement. If there is no enclosing block, control returns to the host environment. In the example below, you calculate and store a price-to-earnings ratio for a company with ticker symbol XYZ. If
errors. The latter are called exceptions. Note: The language of warning and error messages depends on the NLS_LANGUAGE parameter. For dup_val_on_index information about this parameter, see Oracle Database Globalization Support Guide. Topics Compile-Time user defined exception in oracle Warnings Overview of Exception Handling Internally Defined Exceptions Predefined Exceptions User-Defined Exceptions Redeclared Predefined Exceptions Raising Exceptions Explicitly
Oracle Raise_application_error
Exception Propagation Unhandled Exceptions Error Code and Error Message Retrieval Continuing Execution After Handling Exceptions Retrying Transactions After Handling Exceptions See Also: "Exception Handling in Triggers" "Handling FORALL Exceptions After https://docs.oracle.com/cd/A97630_01/appdev.920/a96624/07_errs.htm FORALL Statement Completes" Tip: If you have problems creating or running PL/SQL code, check the Oracle Database trace files. The USER_DUMP_DEST initialization parameter specifies the current location of the trace files. You can find the value of this parameter by issuing SHOW PARAMETER USER_DUMP_DEST. For more information about trace files, see Oracle Database Performance Tuning Guide. Compile-Time Warnings While compiling stored https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/errors.htm PL/SQL units, the PL/SQL compiler generates warnings for conditions that are not serious enough to cause errors and prevent compilation—for example, using a deprecated PL/SQL feature. To see warnings (and errors) generated during compilation, either query the static data dictionary view *_ERRORS (described in Oracle Database Reference) or, in the SQL*Plus environment, use the command SHOW ERRORS. The message code of a PL/SQL warning has the form PLW-nnnnn. For the message codes of all PL/SQL warnings, see Oracle Database Error Messages. Table 11-1 summarizes the categories of warnings. Table 11-1 Compile-Time Warning Categories Category Description Example SEVERE Condition might cause unexpected action or wrong results. Aliasing problems with parameters PERFORMANCE Condition might cause performance problems. Passing a VARCHAR2 value to a NUMBER column in an INSERT statement INFORMATIONAL Condition does not affect performance or correctness, but you might want to change it to make the code more maintainable. Code that can never run By setting the compilation parameter PLSQL_WARNINGS, you can: Enable and disable all warnings, one or more categories of warnings, or specific warnings Treat specific warnings a
MySQL MariaDB PostgreSQL SQLite MS Office Excel Access Word Web Development HTML CSS Color Picker Languages C Language More ASCII https://www.techonthenet.com/oracle/errors/ Table Linux UNIX Java Clipart Techie Humor Advertisement Oracle Basics Oracle Advanced Alter Table Alter Tablespace Change Password Check Constraints Comments in SQL Create Schema Create Schema Statement Create Table Create Table As Create Tablespace Create User Data Types Declare Variables Drop Table Drop Tablespace Drop User Error Messages Find Default Tablespace Find error codes Users Find Users Logged In Find Version Information Functions Global Temporary Grant/Revoke Privileges Indexes Literals Local Temporary Primary Keys Procedures Roles Sequences Set Default Tablespace Synonyms System Tables Unique Constraints Views Oracle Cursors Oracle Exception Handling Oracle Foreign Keys Oracle Loops/Conditionals Oracle Transactions Oracle Triggers String/Char Functions Numeric/Math Functions Date/Time Functions Conversion Functions error codes list Analytic Functions Advanced Functions NEXT: TUTORIAL COMPLETE Oracle / PLSQL: Oracle Error Messages The following is a listing of Oracle Error Messages: 00001-00899 ORA-00001 ORA-00018 ORA-00020 ORA-00023 ORA-00028 ORA-00034 ORA-00051 ORA-00054 ORA-00057 ORA-00058 ORA-00060 ORA-00063 ORA-00068 ORA-00071 ORA-00078 ORA-00100 ORA-00107 ORA-00201 ORA-00257 ORA-00301 ORA-00304 ORA-00361 ORA-00401 00900-00999 ORA-00900 ORA-00902 ORA-00903 ORA-00904 ORA-00905 ORA-00906 ORA-00907 ORA-00908 ORA-00909 ORA-00910 ORA-00911 ORA-00913 ORA-00917 ORA-00918 ORA-00919 ORA-00920 ORA-00923 ORA-00924 ORA-00925 ORA-00926 ORA-00927 ORA-00928 ORA-00931 ORA-00932 ORA-00933 ORA-00934 ORA-00935 ORA-00936 ORA-00937 ORA-00938 ORA-00939 ORA-00942 ORA-00946 ORA-00947 ORA-00948 ORA-00955 ORA-00957 ORA-00960 ORA-00962 ORA-00971 ORA-00972 ORA-00975 ORA-00979 ORA-00980 ORA-00984 ORA-00985 ORA-00995 01000-01399 ORA-01000 ORA-01001 ORA-01002 ORA-01004 ORA-01005 ORA-01006 ORA-01007 ORA-01008 ORA-01012 ORA-01013 ORA-01014 ORA-01017 ORA-01023 ORA-01031 ORA-01033 ORA-01034 ORA-01035 ORA-01037 ORA-01039 ORA-01040 ORA-01042 ORA-01045 ORA-01052 ORA-01074 ORA-01089 ORA-01109 ORA-01113 ORA-01114 ORA-01133 ORA-01200 ORA-01234 01400-01499 ORA-01400 ORA-01401 ORA-01402 ORA-01403 ORA-01404 ORA-01405 ORA-01406 ORA-01407 ORA-01408 ORA-01416 ORA-01417 ORA-01418 ORA-01422 ORA-01423 ORA-01424 ORA-01425 ORA-01426 ORA-01427 ORA-01428 ORA-01429 ORA-01430 ORA-01432 ORA-01433 ORA-01434 ORA-01435 ORA-01436 ORA-01437 ORA-01438 ORA-01439 ORA-01440