Oracle Error Messages

Error: ORA-01846: not a valid day of the week
Cause: You tried to enter a date value, but you specified a day of the week that is not valid.
Action: The options to resolve this Oracle error are:
.Enter a valid day of the week.
For the D format code, 1-7 are valid values.
For the DAY format code, Sunday-Saturday are valid values.
For the DD format code, 1-31 are valid values.
For the DDD format code, 1-366 are valid values.
For the DY format code, Sun-Sat are valid values.

Error: ORA-01847: day of month must be between 1 and last day of month
Cause: You tried to enter a date value, but you specified a day of the month that is not valid for the specified month.
Action: The options to resolve this Oracle error are:
.Enter a valid day of the month. You may want to consider using the to_date function if you are not already using it.

Error: ORA-01858: a non-numeric character found where a digit was expected
Cause: You tried to enter a date value using a specified date format, but you entered a non-numeric character where a numeric character was expected.
Action: The options to resolve this Oracle error are:
.Check the date formats recognized by the to_date function. Correct the date value and retry.

Error: ORA-01861: literal does not match format string
Cause: You tried to enter a literal with a format string, but the length of the format string was not the same length as the literal.
Action: The options to resolve this Oracle error are:
.Re-enter the literal so that it matches the format string.

Error: ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected
Cause: You tried to execute an operation that required either the ONLINE or OFFLINE keyword.
Action: The options to resolve this Oracle error are:
.Insert the missing keyword and re-execute the operation.

Error: ORA-01918: user name does not exist
Cause: You tried to execute a command that specified a user name or role name that does not exist.
Action: The options to resolve this Oracle error are:
.Correct the command and re-execute.

Error: ORA-01950: no privileges on tablespace "name"
Cause: You tried to give the user a tablespace quota, but it failed because the user does not have the necessary system privileges.
Action: The options to resolve this Oracle error are:
.Grant the user the necessary system privileges to create objects in the tablespace.
.Grant the user a specific space resource in the tablespace.

Error: ORA-02003: invalid USERENV parameter
Cause: You tried to call the USERENV function, but specified an invalid parameter.
Action: The options to resolve this Oracle error are:
.Specify a valid USERENV parameter.

Error: ORA-02011: duplicate database link name
Cause: You tried to create a database link (using the CREATE DATABASE LINK command), but a link with that name already exists.
Action: The options to resolve this Oracle error are:
.Either specify a new name or drop the existing database link.

Error: ORA-02024: database link not found
Cause: You tried to drop a database link, but it could not be found in the dictionary.
Action: The options to resolve this Oracle error are:
.Specify a valid name and then re-execute the drop command.

Error: ORA-02069: global_names parameter must be set to TRUE for this operation
Cause: You tried to execute an operation that requires a remote mapping. This can not be done because the parameter called GLOBAL_NAMES is not set to TRUE.
Action: The options to resolve this Oracle error are:
.Try setting the GLOBAL_NAMES parameter to TRUE with the following statement:
ALTER SESSION SET GLOBAL_NAMES = TRUE;

Error: ORA-02086: database link name is too long
Cause: The name of a database or database link name can not exceed 128 characters.
Action: The options to resolve this Oracle error are:
.Specify a valid database name or database link name that is no more than 128 characters.

Error: ORA-02256: number of referencing columns must match referenced columns
Cause: You tried to reference a table using a unique or primary key, but the columns that you listed did not match the primary key.
Action: The options to resolve this Oracle error are:
.This error can also occur when you try to create a foreign key that references a table, but you've listed different columns in your foreign key that do not match the primary key. To resolve this problem, modify your foreign key to reference the correct column list.

Error: ORA-02260: table can have only one primary key
Cause: You tried to create a primary key for a table that already has a primary key.
Action: The options to resolve this Oracle error are:
.You can drop the existing primary key for the table and create a new primary key.

Error: ORA-02268: referenced table does not have a primary key
Cause: You tried to reference a table using a unique or primary key.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you try to create a foreign key that references a table that doesn't have a primary key. To resolve this problem, create a primary key on the referenced table. Then re-execute your command to create the foreign key.

Error: ORA-02270: no matching unique or primary key for this column-list
Cause: You tried to reference a table using a unique or primary key, but the columns that you listed did not match the primary key, or a primary key does not exist for this table.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you try to create a foreign key that references a table that doesn't have a primary key. To resolve this problem, create a primary key on the referenced table. Then re-execute your command to create the foreign key.

Error: ORA-02290: check constraint <constraint_name> violated
Cause: You tried to execute an SQL statement that violated a check constraint.
Action: The options to resolve this Oracle error are:
.Rewrite the SQL statement so that the check constraint is not violated.

Error: ORA-02291: integrity constraint <constraint name> violated - parent key not found
Cause: You tried to reference a table using a unique or primary key, but the columns that you listed did not match the primary key, or a primary key does not exist for this table.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you have a parent-child relationship established between two tables through a foreign key. You then have tried to insert a value into the child table, but the corresponding value does not exist in the parent table.
.To correct this problem, you need to insert the value into the parent table first and then you can insert the corresponding value into the child table.

Error: ORA-02292: integrity constraint <constraint name> violated - child record found
Cause: You tried to DELETE a record from a parent table (as referenced by a foreign key), but a record in the child table exists.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you have a parent-child relationship established between two tables through a foreign key. You then have tried to delete a value into the parent table, but the corresponding value exists in the child table.
.To correct this problem, you need to update or delete the value into the child table first and then you can delete the corresponding value into the parent table.

Error: ORA-02293: cannot enable <constraint name> - check constraint violated
Cause: You tried to add or enable a check constraint to an existing table using an ALTER TABLE command, but the command failed because the existing data in the table did not comply with the check constraint.
Action: The options to resolve this Oracle error are:
.Rewrite the SQL statement so that the check constraint is not violated, or remove the data from the table that does not comply with your check constraint.

Error: ORA-02298: cannot enable name - parent keys not found
Cause: You tried to execute an ALTER TABLE ENABLE CONSTRAINT command, but it failed because your table has orphaned child records in it.
Action: The options to resolve this Oracle error are:
.Remove the orphaned child records from the child table (foreign key relationship), and then re-execute the ALTER TABLE ENABLE CONSTRAINT command.
.Create the missing parent records in the parent table (foreign key relationship), and then re-execute the ALTER TABLE ENABLE CONSTRAINT command.

Error: ORA-02437: cannot validate <name> - primary key violated
Cause: You tried to tried to enable a primary key constraint, but the columns in the primary key either contained NULL values or duplicates..
Action: The options to resolve this Oracle error are:
.This error occurs when you try to enable a primary key when there is data in the table, and the columns that make up the primary key contain either NULL values.
.This error occurs when you try to enable a primary key when there is data in the table, and the columns that make up the primary key contain duplicates.

Error: ORA-02444: cannot resolve referenced object in referential constraints
Cause: You tried to create a foreign key, but referenced an object that wasn't a table.
Action: The options to resolve this Oracle error are:
.This error can occur when you try to create a foreign key that references an object that isn't a table. Redefine your foreign key to reference a table.
.Please note that you should not try to use an Oracle system table in a foreign key.

Error: ORA-02449: unique/primary keys in table referenced by foreign keys
Cause: You tried to drop a table that is referenced as a parent table by a foreign key.
Action: The options to resolve this Oracle error are:
.This error commonly occurs when you have a parent-child relationship established between two tables through a foreign key. You then have tried to drop the parent table without removing the foreign key.
.To correct this problem, you need to drop the foreign key first and then you can drop the parent table.

Error: ORA-03113: end-of-file on communication channel
Cause: You encountered an unexpected end-of-file on the communication channel.
Action: The options to resolve this Oracle error are:
.This error could have been caused by one of the following reasons:
The shadow two-task process associated with a Net8 connect has terminated abnormally. If this is the case, try checking the setup files for the Net8 driver or check that the Net8 software is correctly installed.
The network went down.
The server went down.