Oracle Error Number List
Contents |
and other oracle error codes list with description troubleshooting information in these books. List of Message Types oracle error sqlcode ORA-00000 to ORA-00899 ORA-00900 to ORA-01499 ORA-01500 to ORA-02099 ORA-02100 to ORA-04099 ORA-04100 to
Oracle Error Codes Table
ORA-07499 ORA-07500 to ORA-09857 ORA-09858 to ORA-12299 ORA-12300 to ORA-12399 ORA-12400 to ORA-12699 ORA-12700 to ORA-19399 ORA-19400 to ORA-24279 ORA-24280 to ORA-29249
Oracle Error Handling
ORA-29250 to ORA-32799 ORA-32800 to ORA-32999 ORA-33000 to ORA-65535 BFILE-Related Messages (LFI) DBNEWID Messages (NID) DBVERIFY Messages (DBV) Export Messages (EXP) External Naming Messages (NNF) External Tables Messages (KUP) Import Messages (IMP) interMedia Audio Messages (AUD) interMedia Image Messages (IMG) interMedia Video Messages (VID) Network oracle error codes and solution Security Messages (NZE) Object Type Translator Initialization Messages (O2I) Object Type Translator Type File Messages (O2F) Object Type Translator Unparser Messages (O2U) Oracle Names Client Messages (NNC) Oracle Names Control Utility Messages (NNL) Oracle Names Server Messages (NNO) Oracle Names Server Network Presentation Layer Messages (NPL) Oracle Net Messages (TNS) Oracle OLAP Catalog Metadata Messages (AMD) Oracle Text Messages (DRG) Oracle Trace Collection Services Messages (EPC) Parameter Messages (LCD) Parameter Messages (LRM) PCF FIPS Messages (PCF) PL/SQL and FIPS Messages (PLS) Pro*C/C++ Messages (PCC) Pro*COBOL Messages (PCB) Recovery Manager Messages (RMAN) Remote Operation Messages (NCR) Simple Network Management Protocol Messages (NMP) SQL Runtime Messages (SQL) SQL*Module Messages (MOD) Summary Advisor, Explain Rewrite, and Explain Materialized View Messages (QSM) XML Parser Messages (LPX) XML Schema Processor Messages (LSX) Copyright © 2016, Oracle. All rights reserved.
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
Ora Error 12154
handle certain kinds of errors meaningful to your PL/SQL program. With many oracle error code 942 programming languages, unless you disable error checking, a run-time error such as stack overflow or division by zero stops ora in oracle normal processing and 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. http://www.oracle.com/pls/db92/db92.error_search?prefill=ORA- This chapter discusses 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 https://docs.oracle.com/cd/A97630_01/appdev.920/a96624/07_errs.htm be internally defined (by the 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-t
vid Type in oracle error text* *e.g.username (at oracle error code least 3 characters long) ora amd aud dbv drg epc exp img imp kup lcd lfi lpx lrm lsx mod ncr nid nmp nnc nnf nnl nno npl nze o2f o2i o2u pcb pcc pcf pls qsm rman sql sql*loader tns vid Error type information..... Search tips..... Oracle Support Copyright © Ora-error 2004-2012, all rights reserved.