Oracle 10g Error Messages
Contents |
Operating System-Specific Messages Accuracy of Messages Message Format Recognizing Variable Text in Messages Message Stacks Contacting Oracle Support Services Oracle Exception Messages Trace Files The Alert oracle sql error codes list File 2 ORA-00000 to ORA-00832 3 ORA-00910 to ORA-01497 4 ORA-01500
Oracle Error Codes List With Description
to ORA-02098 5 ORA-02140 to ORA-04099 6 ORA-04930 to ORA-07499 7 ORA-09870 to ORA-12100 8 ORA-07500 oracle error codes and solution pdf to ORA-09859 9 ORA-12150 to ORA-12236 10 ORA-12315 to ORA-12354 11 ORA-12400 to ORA-12497 12 ORA-12500 to ORA-12699 13 ORA-12700 to ORA-19380 14 ORA-19400 to ORA-24276 15
Oracle Error Codes Table
ORA-24280 to ORA-28674 16 ORA-29250 to ORA-32775 17 ORA-32800 to ORA-32848 18 ORA-33000 to ORA-37999 19 ORA-38029 to ORA-39962 20 ORA-40001 to ORA-40322 21 EXP-00000 to EXP-00107 22 IMP-00000 to IMP-00401 23 SQL*Loader-00100 to SQL*Loader-03120 24 KUP-00550 to KUP-11012 25 UDE-00001 to UDE-00053 26 UDI-00001 to UDI-00053 27 DBV-00200 to DBV-00200 28 NID-00001 to NID-00604 oracle database errors and solutions 29 DGM-16900 to DGM-17007 30 LCD-00100 to LCD-00219 31 QSM-00501 to QSM-03120 32 OCI-00601 to OCI-31199 33 RMAN-00550 to RMAN-20507 34 LRM-00100 to LRM-00123 35 LFI-00002 to LFI-01523 36 PLS-00049 to PLS-01913 37 PLW-05000 to PLW-07204 38 AMD-00100 to AMD-00160 39 CLSR-00001 to CLSR-06507 40 CLSS-00001 to CLSS-03202 41 PROC-00001 to PROC-00106 42 PROT-00001 to PROT-00807 43 TNS-00000 to TNS-12699 44 NNC-00001 to NNC-00501 45 NNO-00050 to NNO-00854 46 NNL-00001 to NNL-01078 47 NPL-00100 to NPL-00420 48 NNF-00001 to NNF-04009 49 NMP-00001 to NMP-00011 50 NCR-00001 to NCR-04028 51 NZE-28750 to NZE-29249 52 O2F-00301 to O2F-00341 53 O2I-00101 to O2I-00133 54 O2U-00200 to O2U-00212 55 PCB-00001 to PCB-00903 56 PCC-00001 to PCC-01515 57 PCC-02010 to PCC-02451 58 SQL-01075 to SQL-02157 59 AUD-00611 to AUD-00809 60 IMG-00001 to IMG-02014 61 VID-00611 to VID-00721 62 DRG-10000 to DRG-52210 63 LPX-00000 to LPX-00773 64 LSX-00001 to LSX-00344 Index Scripting on this page enhances content navigation, but does not change the content in any way.
Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level. Action: Either remove the unique restriction or do not insert the key. ORA-00017: session requested to set trace event Cause: The
Oracle 11g Error Codes Pdf
current session was requested to set a trace event by another session. Action: This is
Oracle Common Errors And Solutions
used internally; no action is required. ORA-00018: maximum number of sessions exceeded Cause: All session state objects are in use. Action: Increase oracle 11g error codes list with description the value of the SESSIONS initialization parameter. ORA-00019: maximum number of session licenses exceeded Cause: All licenses are in use. Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter. ORA-00020: maximum number of processes https://docs.oracle.com/cd/B19306_01/server.102/b14219/toc.htm (string) exceeded Cause: All process state objects are in use. Action: Increase the value of the PROCESSES initialization parameter. ORA-00021: session attached to some other process; cannot switch session Cause: The user session is currently used by others. Action: Do not switch to a session attached to some other process. ORA-00022: invalid session ID; access denied Cause: Either the session specified does not exist or the caller does not have the privilege to https://docs.oracle.com/cd/B19306_01/server.102/b14219/e0.htm access it. Action: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege. ORA-00023: session references process private memory; cannot detach session Cause: An attempt was made to detach the current session when it contains references to process private memory. Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session"s database links and/or cursors. Detaching a session with operating system privileges is always disallowed. ORA-00024: logins from more than one process not allowed in single-process mode Cause: Trying to login more than once from different processes for ORACLE started in single-process mode. Action: Logoff from the other process. ORA-00025: failed to allocate string Cause: Out of memory. Action: Restart with larger sga heap. ORA-00026: missing or invalid session ID Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION. Action: Retry with a valid session ID. ORA-00027: cannot kill current session Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session. Action: None. ORA-00028: your session has been killed Cause: A privileged user has killed your session and you are no lon
Interpreting Gateway Error Messages Mapped Errors Gateway Error Codes SQL Tracing and the Gateway Interpreting Gateway Error Messages The gateway architecture involves a number of separate components. Any component might detect and https://docs.oracle.com/cd/B19306_01/gateways.102/b16218/errors.htm report an error condition while processing SQL statements that refer to one or http://allthingsoracle.com/the-40-most-common-oracle-errors/ more DRDA database tables. This means that error situations can be complex, involving error codes and supporting data from multiple components. In all cases, however, the application ultimately receives a single Oracle error number or return code on which to act. Because most gateway messages exceed the 70-character message area in the Oracle SQLCA, error codes the programmatic interfaces and Oracle Call Interfaces that you use to access data through the gateway should use SQLGLM or OERHMS to view the entire text of messages. Refer to the programmer's guide to the Oracle precompilers for additional information about SQLGLM, and refer to the Oracle Call Interface Programmer's Guide for additional information about OERHMS. Error conditions encountered when using the gateway can originate from many sources: error codes list Errors detected by the Oracle integrating server Errors detected by the gateway Errors detected in the DRDA software, either on the requestor or server side Communication errors Errors detected by the server database Errors Detected by the Oracle Integrating Server Errors detected by the Oracle integrating server are reported back to the application or tool with the standard ORA- type message. Refer to the Oracle Database Error Messages for descriptions of these errors. For example, the following error message occurs when an undefined database link name is specified: ORA-02019: connection description for remote database not found Errors in the ORAE9100 to ORAE9199 range are reserved for the generic gateway layer (components of the gateway that are not specific to DRDA). Messages in this range are documented in Oracle Database Error Messages. Errors Detected by the Gateway Errors detected by the generic gateway are prefixed with HGO- and are documented in the Oracle Database Error Messages. An example of an error message is: HGOE00706: HGO: Missing equal sign for parameter in initialization file. Errors Detected in the DRDA Software Errors detected in the DRDA gateway, on the requestor or server side, are usually reported with error code ORAE28500, followed by a gatewayEspecific ex
industry long enough to remember the bad old days, when every developer and DBA had a pile of dusty Oracle user guides on their desks and, every time their database or application coughed up an error, would thumb through the books with mounting desperation. Fortunately, the times have moved on and we now all outsource our memories to Google and Bing and Baidu. Our desks are clear, but our need for external help whenever we are ambushed by unexpected errors is just as strong. Using tools Google have made available, I have put together a list of the ORA messages we collectively searched for the most in the first month of 2012. These messages (see a Billboard-style Top 40 Chart at the bottom of this article) are a mix of those generic errors that can mean pretty much anything, the error messages we see most rarely, and those common error numbers that we never seem able to memorise. ORA-12154: TNS:could not resolve the connect identifier specified (#1) Coming in at number 1, and googled more than twice as often as any other error message, this error is, almost appropriately, often the very first one you get on trying to establish a connection to your database. Simply put, it means that you have named the database you wish to be connected to and Oracle doesn’t know who the heck you’re talking about. This error is often caused by typos, maybe in your connection string, but possibly in your tnsnames.ora file. It is also possible that the tnsnames.ora file is not accessible or does not even exist. If it does, ensure that it contains the service name you are using; also go over it with a fine toothcomb to make sure it doesn’t have any unpaired parentheses or such. ORA-00600: internal error code, arguments: [%s], [%s],[%s], [%s], [%s] (#2) Coming in at number 2 is a generic error; it means something serious has gone wrong and you are going to need to roll up your sleeves, dig in, and find out what. But you are not without clues. Your alert.log file will contain the path to your trace file. You will want to look in it, as a record is written to the trace file every time an ORA-00600 error occurs. Take the information you get from your trace file and the first argument in the square brackets (the internal message number), and head over to My Oracle Support (Metalink). There you will find a handy ORA-0600 lookup tool (Note 153788.1) that will direct you to additional information that will help you solve your problem. ORA-1722: Invalid Number (#3) You get this error when your SQL tries to convert a non-numeric string into a number. This conversion might be explicit – to_number(‘I am looking for