Oracle Error Codes
The ORA-12537 error occurs when the user has listed a 10g database SID with a 9i listener, it can create the problem because of invalid inter-version connections, due to an eBusiness Suite security feature.
The ORA-02063 error occurs in response to an error at a remote database or table. When an error is generated at a remote database it usually is accompanied by an ORA-02063.
The ORA-04030 error message is an error caused by a shortage of RAM on a dedicated (non-shared server) environment.
The ORA-00001 message is caused when trying to execute an INSERT or UPDATE statement that has generated a duplicate value in a restricted field.
Error ORA-00054 occurs when a user tries to execute a LOCK TABLE or SELECT FOR UPDATE command with the NOWAIT keyword when the resource is unavailable.
The ORA-00257 is a common Oracle error that typically concerns the amount of storage space set aside for archived log data.
The ORA-00984 is an error resulting from a column not being allowed in a particular area of the program.
ORA-00972 occurs when you have tried to reference a table, cluster, view, index, synonym, tablespace, or username with a value that is longer than 30 characters.
The ORA-00955 error message occurs when you are trying to create a table, view, index, synonym or other object that has a name that is already in use.
The ORA-00937 error message occurs when the GROUP BY command is improperly used. To resolve the error, you can remove the group function or column expression from the SELECT clause.
ORA-609 is an error message indicates that a client connection has failed to complete or that the connection was aborted without being successfully connected.
ORA-01034 is due to the Oracle system not being available or started up. This could derive from the System Global Area (SGA) needing more storage space.
The ORA-01403 error message “No Data Found” is often associated with SELECT INTO clauses, which fetch rows or sets of columns from a database.
ORA-01422 error is the exact fetch returning more than requested number of rows. Your SELECT INTO statement is retrieving multiple or zero rows of data.
ORA-01555 appears as a result of an Oracle read consistency mechanism. Oracle cannot access the original copy of the data from when the query started, and the changes cannot be undone by Oracle as they are made.
ORA-01652 is a failure in allocating the extent for the temp segment in the tablespace. The tablespace may be adjusted but the temp tablespace is unchanged.
Error ORA-01843 occurs when the user specifies a date that is not a valid calendar month. Proper formatting is the international standard (DD/MM/YYYY).
The ORA-01861 error message is triggered when a literal has been entered that fails to follow a format string.
The ORA-02291 error message states that you failed to match the primary key with the specified column when attempting to execute a reference to a table.
The source of an ORA-03113 is a broken connection between Client and Server process, a blanket end-of-file on a communication channel error.
The ORA-03135 is an error that often occurs when connecting from a remote location and the firewall in your network terminates the connection.
ORA-20000 is a generic error that usually accompanies another error or a stack of errors. It is part of the reserved section of PL/SQL user-defined errors.
The ORA-12899 is an Oracle error that occurs when the value entered into the column string is too large.
The ORA-03114 is an error message triggered when a user attempts a call to Oracle when no connection was established.
ORA-06508 occurs when a program unit being called is not found. This is due to the procedure being dropped or modified in an incompatible manner.
The ORA-02292 error indicates that an “integrity constraint was violated – child record found”.
This error essentially occurs when a user attempts to convert a string of data into a date, and in doing so specified a date passed in a particular format.
In order to correct the Oracle error, the user needs to edit the TO_DATE function to accommodate the extra information.
The cause of the ORA-01427 error is a subquery returning more than one row of information. Fortunately, ORA-01427 is a straightforward query error.
The “ORA-01400: cannot insert null into (string)” error occurs when you try to insert a NULL value in a column that does not accept NULL values.
ORA-01013: user requested cancel of current operation is what is known as an “information error” that gives the user information on the operation performed.
The “ORA-00922: missing or invalid option” error message is one of many Oracle errors, which does not point to a concrete and easily identifiable problem.
ORA-00920: invalid relational operator tips can easily be resolved with the addition or removal of relational operators within the Oracle language.
In the realm of manipulating data across multiple data tables, a common error encountered is the ORA-02291.
ORA-01861 results when literal does not match format string.
ORA-01422 error is the exact fetch returning more than requested number of rows.
Oracle Error Message ORA-04063 occurs when either an attempt to execute a stored procedure was made or an attempt to use a view that has errors was made.
The ORA-12541 message happens if the listener is either down as it attempts to make a connection or if it has not been started or properly configured.
ORA-24344 alerts the user that there is a problem of some kind within the code.
Error ORA-00905 is seen when a required keyword is missing. According to the Oracle documentation, the action for this error is to “correct the syntax.”
The ORA-28000 Error Message is triggered by attempting an invalid password too many times which results in the user getting locked out of the system.
The ORA-12801 is an Oracle error that has some confusing origins, but is described as an error resulting in some form from a parallel query server.
The ORA-01033 Error Message is related to the starting up or shutting down of Oracle. There are several possible causes and fixes to the problem.
ORA-00979 is related to the GROUP BY clause. In comparison to other Oracle errors, ORA-00979 is usually straightforward and can easily be solved.
ORA-00932 Error Message occurs when data types are incorrectly used. Try the following suggestions to resolve the issue and avoid seeing the same error.
ORA-00923 Error Message occurs when you try to execute a SELECT or REVOKE statement without a FROM keyword in its correct form and place.
The source of an ORA-00918 error comes from a mistake when attempting to join two or more tables that share the same name in across columns.
In essence, an ORA-00600 is an internal coding error. It is recommended that should the error be triggered, you should contact Oracle Support immediately.
The cause of an ORA-12545 error is a failed connection. This results from a target host or object not existing in the specified parameters of Oracle.
There are several possible causes for error ORA-12170: problems with the firewall, database is down, listener is down, sqlnet.ora parm is invalid, among others.
Error ORA-04031 stems from a lack of available System Global Area memory space. The error commonly occurs when working with large shared pools of memory.
Error ORA-01843 occurs when the user specifies a date that is not a valid calendar month. There are mainly two reasons the user sees this error.
Error ORA-01652 is a failure in allocating the extent for the temp segment in the tablespace. The tablespace may have been adjusted but the temp tablespace is unchanged.
Error ORA-01034 is due to the Oracle system not being available or started up. This could derive from the System Global Area (SGA) needing more storage space.
Error ORA-00907 is a syntax error commonly seen code is written manually. This error indicates a left parenthesis but no corresponding right parenthesis.
ORA-00604 occurs while processing a recursive SQL statement. If the situation described in the next error on the stack can be corrected, it should be corrected.
Error Ora-00942 means you are attempting to execute an SQL statement that references a table or view which does not exist. There are several possible causes for the “table or view does not exist” error.
The Oracle message known as “ora-12154” may be the most common error experienced by Oracle users. Luckily, the frustration of so many previous users has prompted some fairly straightforward solutions to the issue.
A common error to occur while using Oracle is the ORA-06502 error message. This is an error that results from a mistake in the arithmetic or the numeric value executed in a statement.
The impetus of the ORA-01017 error essentially derives from an incorrect username/password combination being entered to log on to Oracle.
Error Ora-00904 means you are attempting to execute an SQL statement that either has an invalid column name or a column name which does not currently exist.
The ORA-00911 error message, described as an invalid character error, typically is the result of a common syntax mistake.
The ORA-00933 error message is triggered by an SQL command being ended with an improper clause.
Some Oracle mistakes are not nearly as intimidating to resolve as the error message would seem to indicate. The ORA-00936 is the perfect example of such a case. This error provides an excellent case where thinking too hard about the answer will cost you far more time and effort than needed.
The ORA-01722 message is a fairly typical error in Oracle. It is an “invalid number” error, occurring during a failure when converting a character string to a valid number. While this type of error can be an easy fix, it can be caused by a multitude of numerical mistakes.
Error Ora-06512 means the backtrace message as the stack is being unwound by unhandled exceptions in your PLSQL code. This is a catch-all error for PLSQL exceptions and is commonly seen.
Some errors in Oracle can take far more time to diagnose than to fix. Locating the source of an ORA-12560 error can feel a bit like a wild goose chase. However, once the problem is traced the mistake can typically be hashed out.
Error ORA-00900 occurs if the Procedural Option is not installed and a SQL statement is issued that requires this option.
Error ORA-01031 means you are attempting to execute an operation for which you do not have appropriate privileges. There are several, possible causes for the ORA-01031 “Insufficient Privileges” error.