Oracle Error Messages

Error : ORA-00001: unique constraint (constraint_name) violated.
Cause: You tried to execute an INSERT or UPDATE statement that has created a duplicate value in a field restricted by a unique index.
Action: The options to resolve this Oracle error are:

.Drop the unique constraint
.Change the constraint to allow duplicate values
.Modify your SQL so that a duplicate value is not created

Error: ORA-00018: maximum number of sessions exceeded
Cause: You tried to execute a statement that requested a resource. Since the maximum number of sessions have been reached, Oracle will not process any new resource requests.
Action: The options to resolve this Oracle error are:
.You can wait a few minutes and try to re-execute the statement(s).
.You can shut down Oracle, increase the SESSIONS parameter in the initialization parameter file, and restart Oracle.

Error: ORA-00020: maximum number of processes num exceeded
Cause: You tried to execute a statement that requested a resource. Since the maximum number of processes have been reached, Oracle will not process any new requests.
Action: The options to resolve this Oracle error are:

.You can wait a few minutes and try to re-execute the statement(s).
.You can shut down Oracle, increase the PROCESSES parameter in the initialization parameter file, and restart Oracle.

Error: ORA-00023: session references process' private memory; cannot detach session
Cause: You tried to detach a session but it contains references to the process memory (PGA) through any of: an open network connection, a very large context area, or operating system privileges.
Action: The options to resolve this Oracle error are:

.If the session has an open network connection or a very large context area, you can try closing the session's database links and cursors.
.If the session has operating system privileges, you will not be able to detach the session.

Error: ORA-00028: your session has been killed
Cause: Your session has been killed by a privileged user (such as a DBA).
Action: The options to resolve this Oracle error are:
.Check with your DBA. Your session may have been killed due to a scheduled outage or other activity.

Error: ORA-00034: cannot COMMIT or ROLLBACK in current PL/SQL session
Cause: You tried to issue a COMMIT or ROLLBACK command from a PLSQL function, procedure, or package. However, COMMIT and ROLLBACK have been disabled with the following command:

ALTER SESSION DISABLE COMMIT IN PROCEDURE

Action: The options to resolve this Oracle error are:
.Do not issue a COMMIT or ROLLBACK command from your PLSQL function, procedure, or package while disabled.
Enable COMMIT or ROLLBACK for this PLSQL session.

Error: ORA-00051: time-out occurred while waiting for resource
Cause: You were waiting for a resource and you timed out. The may have been caused by an Oracle instance abnormally terminating.
Action: The options to resolve this Oracle error are:
.Restart the Oracle instance.

Error: ORA-00054: resource busy and acquire with NOWAIT specified
Cause: You tried to execute a LOCK TABLE or SELECT FOR UPDATE command with the NOWAIT keyword but the resource was unavailable.
Action: The options to resolve this Oracle error are:
.Wait and try the command again after a few minutes.
.Execute the command without the NOWAIT keyword.

Error: ORA-00057: maximum number of temporary table locks exceeded
Cause: The number of temporary tables has reached or exceeded the number of temporary table locks allowed by Oracle.
Action: The options to resolve this Oracle error are:
.This error is most commonly caused by an SQL statement that has performed a very large sort. The sort has created a number of temporary tables that has exceeded the limit specified in Oracle.
.To correct this problem, increase the TEMPORARY_TABLE_LOCKS parameter in Oracle and perform a restart in Oracle.

Error: ORA-00058: DB_BLOCK_SIZE must be num to mount this database not num
Cause: You tried to start a database whose DB_BLOCK_SIZE parameter value in the initialization file does not match the value used when the database was created.
Action: The options to resolve this Oracle error are:
.Make sure that you are mounting the correct database.
.Make sure that you are using the correct initialization file.
.You may need to change the DB_BLOCK_SIZE parameter in the initialization file.

Error: ORA-00060: deadlock detected while waiting for resource
Cause: You tried 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.
Action: The options to resolve this Oracle error are:
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.

Error: ORA-00063: LOG_FILES initialization parameter exceeded
Cause: The value of the LOG_FILES parameter must be as large as the highest number log that exists.
Action: The options to resolve this Oracle error are:
.Increase the LOG_FILES parameter value in the initialization file and then perform an Oracle warm start.

Error: ORA-00068: invalid value num for parameter num, must be between num and num
Cause: The value for the initialization parameter must be between the numbers specified in this error message.
Action: The options to resolve this Oracle error are:
.Update the initialization parameter accordingly.

Error: ORA-00071: process number must be between 1 and num
Cause: You tried to specify a process number that was not valid.
Action: The options to resolve this Oracle error are:
.Specify a process number that is between 1 and the number listed in the error message.

Error: ORA-00078: cannot dump variables by name
Cause: You tried to dump a variable by name, but your system does not support this option.
Action: The options to resolve this Oracle error are:
.Try the PEEK command.

Error: ORA-00100: no data found
Cause: An application tried to access data that was either inaccessible or does not exist.
Action: The options to resolve this Oracle error are:
.This error must be handled within the application. Modify the application accordingly.

Error: ORA-00107: failed to connect to network listener process
Cause: The network listener process was not been successfully started.
Action: The options to resolve this Oracle error are:
.Make sure that the network configuration file is set up correctly.
.Make sure that the client-side address is set up correctly.
.Make sure that the listener initialization parameter file is set up correctly.

Error: ORA-00201: control file version num incompatible with Oracle version num
Cause: The control file was created by a version of Oracle that is different than the version of Oracle that you are currently running.
Action: The options to resolve this Oracle error are:
.Restart Oracle with a version of Oracle that is the same as the control file.
.Create a new control file using the CREATE CONTROLFILE command.

Error: ORA-00257: archiver is stuck. CONNECT INTERNAL only, until freed
Cause: While trying to archive a redo log file, the ARCH process encountered an error.
Action: The options to resolve this Oracle error are:
.This error can be caused when the destination device does not have enough storage space to store the redo log file.
.Check that the initialization parameter ARCHIVE_LOG_DEST in the initialization file is set correctly.
.It may be helpful to check the archiver trace file for more details on the problem.

Note: If this problem is not resolved, Oracle will stop executing transactions.

Error: ORA-00301: error in adding log file <name> - file cannot be created
Cause: You tried to create a redo log file, but the creation failed.
Action: The options to resolve this Oracle error are:
.Check if there is enough storage space on the device.
.Check if the device is available.
.Check if the file name is correct.
Once the cause of the problem has been corrected, re-execute the command.

Error: ORA-00304: requested INSTANCE_NUMBER is busy
Cause: You tried to start an Oracle instance by using an INSTANCE_NUMBER parameter value that is already in use.
Action: The options to resolve this Oracle error are:
.Modify the INSTANCE_NUMBER initialization parameter in the initialization file to use another number. Then try restarting the instance.
.Wait for recovery to finish for that instance number.

Error: ORA-00361: cannot remove last log member name group num
Cause: You tried to remove the last member of a redo log group.
Action: The options to resolve this Oracle error are:
.You can try deleting the log using the DROP log file command.

Error: ORA-00401: the value for parameter name is not supported by this release
Cause: You tried to specify a value in the initialization file that is not supported by this release of Oracle.
Action: The options to resolve this Oracle error are:
.You need to enter a value that is supported by your version of Oracle, or remove the parameter value from the initialization file so that the default value is used.

Error: ORA-00900: invalid SQL statement
Cause: The statement that you've tried to execute is not a valid SQL statement.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you are trying to create a procedure and the Procedural Option is not installed.
.To determine if the Procedural Option has been installed, open an Oracle session using SQL*Plus. If the PL/SQL banner does not display, then you know that the Procedural Option has not been installed.

Error: ORA-00902: invalid datatype
Cause: You tried to tried to execute a CREATE TABLE or ALTER TABLE statement that contained an invalid datatype.
Action: The options to resolve this Oracle error are:
.This error occurs when you try to execute a CREATE TABLE or ALTER TABLE statement that contains a datatype that does not exist. List of valid Oracle datatypes.