In this article I am listing the common oracle errors that are mostly encountered.
So lets start identifying the errors their causes and the actions that should be taken when such errors are displayed..
| |
Error |
Cause |
Action |
|
| 1 |
ORA Error |
In an attempt to make a basic peer-to-peer (single protocol network) connection. |
- Verify that the Database Is Running.
- Perform a Loopback Test.
- Check that same protocol support is installed as on the database server.
- Check base connectivity for underlying network transport.
- Check that the client computer has the tnsnames.ora and the sqlnet.ora files in the correct locations.
- Test the Net8 foundation layer.
|
| 2 |
ORA-00001: unique constraint ( constraint_name ) violated |
Trying to execute an INSERT or UPDATE statement that has created a duplicate value in a field restricted by a unique index |
- Drop the unique constraint
- Change the constraint to allow duplicate values
- Modify your SQL so that a duplicate value is not created
|
| 3 |
ORA-00054: resource busy and acquire with NOWAIT specified |
Trying to execute a LOCK TABLE or SELECT FOR UPDATE command with the NOWAIT keyword but the resource was unavailable. |
- Wait and try the command again after a few minutes.
- Execute the command without the NOWAIT keyword.
|
| 4 |
ORA-00060: deadlock detected while waiting for resource |
Trying to execute a statement, but your session was deadlocked because another session had the same resource locked. The statement(s) that you tried to execute have been rolled back. |
- You can wait a few minutes and try to re-execute the statement(s) that were rolled back.
- You can execute a ROLLBACK and re-execute all statements since the last COMMIT was executed.
|
| 5 |
ORA-00200: controlfile could not be created |
It was not possible to create the controlfile. |
Check that there is sufficient disk space and no conflicts in filenames and try to create the controlfile again. |
| 6 |
ORA-00312: online log string thread string: `string` |
This message reports the filename for details of another message. |
See the associated messages for the appropriate action to take. |
| 7 |
ORA-00235: control file fixed table inconsistent due to concurrent update |
Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. |
Retry the operation. |
| 8 |
ORA-00313: open failed for members of log group string of thread string |
The online log cannot be opened. May not be able to find file. |
See accompanying errors and make log available. |
| 9 |
ORA-00320: cannot read file header from log string of thread string |
The file is not available. |
Restore the log file. |
|
| 10 |
ORA-00321: log string of thread string, cannot update log file header |
Cannot write to the log file. |
Restore the access to the file. |
| 11 |
ORA-00396: error string required fallback to single-pass recovery |
The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error. |
Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process. |
| 12 |
ORA-12154: TNS:could not resolve the connect identifier specified |
You tried to connect to Oracle, but the service name is either missing from the TNSNAMES.ORA file or is incorrectly defined. |
- Make sure that the TNSNAMES.ORA file exists and is in the correct directory.
- Make sure that the service name that you are connecting to is included in the TNSNAMES.ORA file and that it is correctly defined.
- Make sure that there are no syntax errors in the TNSNAMES.ORA file. For example, if there are unmatched brackets in the file, the file will be rendered unusable.
|
| 13 |
ORA-06512: at stringline string |
Backtrace message as the stack is unwound by unhandled exceptions. |
- Fix the problem causing the exception or write an exception handler for this condition.
- Contact your application administrator or DBA.
|
| 14 |
ORA-00904: invalid column name |
Trying to execute a SQL statement that included an invalid column name or the column name is missing. |
- The column name must begin with a letter.
- The column name can not be longer than 30 characters.
- The column name must be made up of alphanumeric characters or the following special characters: $, _, and #. If the column name uses any other characters, it must be enclosed in double quotation marks.
- The column name can not be a reserved word.
|
| 15 |
ORA-01722: invalid number |
You executed an SQL statement that tried to convert a string to a number, but it was unsuccessful. |
- Only numeric fields or character fields that contain numeric values can be used in arithmetic operations. Make sure that all expressions evaluate to numbers.
- If you are adding or subtracting from dates, make sure that you added/substracted a numeric value from the date.
|
| 16 |
ORA-00600: internal error code; arguments: [string], [string], [string], [string], [string], [string], [string], [string]
|
This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition. |
Report as a bug - the first argument is the internal error number |
| 17 |
ORA-00936: missing expression |
Trying to execute a SQL statement but you omitted a part of the syntax. |
This error most commonly occurs when you try to execute a SELECT statement and forget to the list of the columns in the SELECT statement. |
| 18 |
ORA-01034: Oracle not available |
Oracle is not started up. Possible causes may be that either the SGA requires more space than was allocated for it or the operating-system variable pointing to the instance is improperly defined. |
- Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages.
- If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly.
- See the platform specific Oracle documentation.
|
| 19 |
ORA-12545: Connect failed because target host or object does not exist |
The address specified is not valid, or the program being connected to does not exist. |
- Ensure the ADDRESS parameters have been entered correctly.
- Ensure that the executable for the server exists.
- If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.
|
|
|
| 20 |
ORA-00942: table or view does not exist |
- SQL statement is executed that references a table or view that either does not exist.
- You do not have access to the table or view, or the table or view belongs to another schema and you didn't reference the table by the schema name.
|
- If this error occurred because the table or view does not exist, you will need to create the table or view.
- If this error occurred because you do not have access to the table or view, you will need to have the owner of the table/view, or a DBA grant you the appropriate privileges to this object.
- If this error occurred because the table/view belongs to another schema and you didn't reference the table by the schema name, you will need to rewrite your SQL to include the schema name.
|
| 21 |
ORA-03113: end-of-file on communication channel |
You encountered an unexpected end-of-file on the communication channel. |
- Check for network problems and review the SQL*Net setup.
- Look in the alert.log file for any errors.
- Test to see whether the server process is dead and whether a trace file was generated at failure time.
|
| 22 |
ORA-06502: PL/SQL: numeric or value error |
The
executed statement resulted in an arithmetic, numeric, string, conversion, or constraint error. |
Change the data, how it is manipulated, or how it is declared so that values do not violate constraints. |
| 23 |
ORA-04031: unable to allocate num bytes of shared memory num, num, num |
Tried
to use more shared memory than was available. SGA private memory has been exhausted. |
- Reduce your use of shared memory.
- Increase the SHARED_POOL_SIZE initialization parameter in the initialization file.
- Use the DBMS_SHARED_POOL package to pin large packages.
|
|
| 24 |
ORA-01756: quoted string not properly terminated |
A quoted string is not terminated with a single quote mark (') |
Insert the closing quote and retry the statement. |
| 25 |
ORA-29283: invalid file operation |
An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system. |
Verify file and directory access privileges on the file system, and if reading, verify that the file exists. |
| 26 |
ORA-00020: maximum number of processes num exceeded |
All process state objects are in use. |
- Wait a few minutes and try to re-execute the statement(s).
- Shut down Oracle, increase the PROCESSES parameter in the initialization parameter file, and restart Oracle.
|
| 27 |
ORA-12203: TNS:unable to connect to destination |
- Invalid address specified or destination is not listening.
- This error can also occur because of underlying network or network transport problems.
|
- Verify that the net service name you entered was correct.
- Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct.
- Ensure that the destination process (for example the listener) is running at the remote node.
|
| 28 |
ORA-01017: invalid username/password; logon denied |
Logging into Oracle with an invalid username/password combination. |
Enter a valid username and password combination in the correct format.
If the username and password are entered together, the format is: username/password |
| 29 |
ORA-01403: no data found |
- Executing a SELECT INTO statement and no rows were returned.
- Referencing an uninitialized row in a table.
- Reading past the end of file with the UTL_FILE package.
|
Terminate processing of the data. |
| 30 |
ORA-01033: ORACLE initialization or shutdown in progress |
An attempt was made to log on while Oracle is being started up or shutdown |
Wait a few minutes. Then retry the operation. |
