All Error Codes In Oracle
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 kinds of errors meaningful to your
Sql Server Error Codes
PL/SQL program. With many programming languages, unless you disable error checking, a run-time error mysql error codes such as stack overflow or division by zero stops normal processing and returns control to the operating system. With PL/SQL, a
Exception No Data Found Oracle
mechanism called exception handling lets you "bulletproof" your program so that it can continue operating in the presence of errors. This chapter discusses the following topics: Overview of PL/SQL Error Handling Advantages of PL/SQL Exceptions http://docs.oracle.com/cd/B28359_01/nav/lookup.htm?id=ERRMG 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 run-time system) or user defined. Examples of internally defined exceptions include division by zero and out of memory. https://docs.oracle.com/cd/A97630_01/appdev.920/a96624/07_errs.htm 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 the company has zero earnings, the predefined exception ZERO_DIVIDE is raised. This stops normal execution of the block and transfers control to the exception handlers. The optional OTHERS handler catches all exceptions that the block does not
expressiontable or view does not existend-of-file on communication channelTNS:listener unknown in connect descriptorinsufficient privilegesPL/SQL: numeric or value error stringTNS:protocol adapter errorORACLE not availabletarget host or object does not existinvalid numberunable http://www.ora-code.com/ to allocate string bytes of shared memoryresource busy and acquire http://psoug.org/oraerror.htm with NOWAIT specifiederror occurred at recursive SQL level stringORACLE initialization or shutdown in progressarchiver error. Connect internal only, until freedsnapshot too oldunable to extend temp segment by string in tablespaceCredential retrieval failedmissing or invalid optioninvalid username/password; logon deniedunable to create INITIAL extent error codes for segmentout of process memory when trying to allocate string bytesshared memory realm does not existcannot insert NULLTNS:unable to connect to destinationremote database not found'>ora-02019exception encountered: core dumpinconsistent datatypesno data foundTNS:operation timed outPL/SQL: could not find programexisting state of packages has been discardedmaximum number of processes exceedederror signaled in parallel query serverORACLE instance oracle error codes terminated. Disconnection forcedTNS:packet writer failuresee ORA-12699missing right parenthesisname is already used by an existing objectcannot identify/lock data fileinvalid file operationquoted string not properly terminated Oracle Error Code Collections AMD AUD CLS DBV DGM DRG EXP IMG IMP KUP LCD LFI LPX LRM LSX NCR NID NMP NNC NNF NNL NNO NPL NZE O2F O2I O2U OCI ORA-CODE PCB PCC PLS PLW PRO QSM RMA SQL TNS UDE UDI VID Google Search: ORA-00000 to ORA-00237 ORA-00056 ORA-00057 ORA-00058 ORA-00059 ORA-00060 ORA-00061 ORA-00062 ORA-00063 ORA-00064 ORA-00065 ORA-00066 ORA-00067 ORA-00068 ORA-00069 ORA-00070 ORA-00071 ORA-00072 ORA-00073 ORA-00074 ORA-00075
Code Library mySQL Code Library PHP Code Library JavaScript Code Library Oracle Terms & Definitions Oracle Error Codes PSOUG Community Blogs Oracle Jobs Board PSOUG Forum Oracle User Group Directory Free Oracle Magazines Online Learning Center PSOUG Presentations Advanced Code Search News and Events Sponsors Page Submit Code Contact Us We have over 18,000 Oracle Error Codes currently indexed for searching, including error codes for SQL*Loader, RMAN, NNL, TNS, DRG, IMG, PCC, LPX, LSX, and many others. Type the Oracle Error code into the Search box to find the associated error: Or, browse the Oracle Error list below: ORA-00000: Normal, successful completion ORA-00001: Unique constraint (string.string) violated ORA-00017: Session requested to set trace event ORA-00018: Maximum number of sessions exceeded ORA-00019: Maximum number of session licenses exceeded ORA-00020: Maximum number of processes (string) exceeded ORA-00021: Session attached to some other process; cannot ... ORA-00022: Invalid session ID; access denied ORA-00023: Session references process private memory; cann... ORA-00024: Logins from more than one process not allowed i... ORA-00025: Failed to allocate string ORA-00026: Missing or invalid session ID ORA-00027: Cannot kill current session ORA-00028: Your session has been killed ORA-00029: Session is not a user session ORA-00030: User session ID does not exist. ORA-00031: Session marked for kill ORA-00032: Invalid session migration password ORA-00033: Current session has empty migration password ORA-00034: Cannot string in current PL/SQL session ORA-00036: Maximum number of recursive SQL levels (string)... ORA-00037: Cannot switch to a session belonging to a diffe... ORA-00038: Cannot create session: server group belongs to ... ORA-00040: Active time limit exceeded - call aborted ORA-00041: Active time limit exceeded - session terminated ORA-00042: Unknown Service name string ORA-00050: Operating system error occurred while obtaining... ORA-00051: Timeout occurred while waiting for a resource ORA-00052: Maximum number of enqueue resources (string) ex... ORA-00053: Maximum number of enqueues exceeded ORA-00054: Resource busy and acquire with NOWAIT specified ORA-00055: Maximum number of DML locks exceeded ORA-00056: DDL lock on object "string.string" is already h... ORA-00057: Maximum number of temporary table locks exceeded ORA-00058: DB_BLOCK_SIZE must be string to mount this data... ORA-00059: Maximum number of DB_FILES exceeded ORA-00060: Deadlock detected whi