Oracle Error Messages

Error: ORA-04000: the sum of PCTUSED and PCTFREE cannot exceed 100
Cause: You tried to create a cluster or table where the PCTUSED and PCTFREE added together exceeded 100.
Action: The options to resolve this Oracle error are:
.Try specifying values for PCTUSED and PCTFREE where these values added together do not exceed 100.

Error: ORA-04031: unable to allocate num bytes of shared memory num, num, num
Cause: You tried to use more shared memory than was available. SGA private memory has been exhausted.
Action: The options to resolve this Oracle error are:
.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.

Error: ORA-04088: error during execution of trigger name.name
Cause: You tried to execute a trigger, but a runtime error occurred.
Action: The options to resolve this Oracle error are:
.Check the triggers that were involved.

Error: ORA-04091: table name is mutating, trigger/function may not see it
Cause: A statement executed a trigger or custom PL/SQL function. That trigger/function tried to modify or query a table that is currently being modified by the statement that fired the trigger/function.
Action: The options to resolve this Oracle error are:
.Re-write the trigger/function so that it does not try to modify/query the table in question.

Error: ORA-04092: cannot COMMIT or ROLLBACK in a trigger
Cause: You tried to perform a COMMIT or ROLLBACK in a trigger. This is not allowed.
Action: The options to resolve this Oracle error are:
.Re-write your trigger so that COMMITs and ROLLBACKs are not issued.

Error: ORA-04098: trigger name is invalid and failed re-validation
Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.
Action: The options to resolve this Oracle error are:
.Resolve the compilation/authorization errors.
.Disable the trigger.
.Drop the trigger.
You can also try running the following command to check for errors on the trigger:

show errors trigger trigger_name;

Replace trigger_name with the name of your trigger.

Error: ORA-06500: PL/SQL: storage error
Cause: You ran out of memory or memory was corrupted.
Action: The options to resolve this Oracle error are:
.Contact customer support.

Error: ORA-06501: PL/SQL: program error
Cause: This is a generic "Contact Oracle support" message because an internal problem was encountered.
Action: The options to resolve this Oracle error are:
.Contact customer support.

Error: ORA-06502: PL/SQL: numeric or value error
Cause: You tried to tried to execute a statement that resulted in an arithmetic, numeric, string, conversion, or constraint error.
Action: This error can be caused by many circumstances. The following are two examples of how to resolve this Oracle error:
.This error occurs when you try to assign a value to a numeric variable, but the value is larger than the variable can handle.
.This error also occurs if you are trying to assign a non-numeric value to a numeric variable.

Error: ORA-06503: PL/SQL: Function returned without value
Cause: You tried to call a PLSQL function, but the function was missing a RETURN statement.
Action: The options to resolve this Oracle error are:
.Try re-writing the function to include a RETURN statement. Or if you don't want to return a value, re-write your function as a procedure.
.Every function must return a value.

Error: ORA-06508: PL/SQL: could not find program unit being called
Cause: You tried to call a stored procedure, but the stored procedure could not be found.
Action: The options to resolve this Oracle error are:
.The stored procedure may have been dropped. Try re-creating the stored procedure.
.The stored procedure may have compiled with errors. Try fixing the errors and re-compiling.

Error: ORA-06510: unhandled user-defined exception
Cause: You tried to execute a block of code that raised a user-defined exception, but there was no exception block code to handle this exception.
Action: The options to resolve this Oracle error are:
.Remove the user-defined exception from the code.
.Add exception code to handle the user-defined exception.

Error: ORA-06511: PL/SQL: cursor already open
Cause: You tried to open a cursor that was already open.
Action: The options to resolve this Oracle error are:
.Try closing the cursor, then you can re-open it.

Error: ORA-06512: at line <number>
Cause: This error message indicates the line number in the PLSQL code that the error resulted.
Action: For example, if you had the following PLSQL code:
declare
v_number number(2);
begin
v_number := 100;
end;

You would receive the following error message:
"ORA-06502:PL/SQL: numericor value error:number precision too large
ORA-06512: at line 4"

.The first line of the error message (ie: ORA-06502) indicates the error that occurred, while the second line of the error message (ie: ORA-06512) indicates that the error occurred at line 4 of the PLSQL code.
.In this example, you've tried to assign a 3 digit number to a variable called v_number that can only handle 2 digits. You could correct this error by redefining the v_number variable as number(3).

declare
v_number number(3);
begin
v_number := 100;
end;
[/b]

Error: ORA-06514: PL/SQL: The remote call cannot be handled by the server
Cause: You tried to execute a stored procedure that had cursor variables as parameters. Stored procedures on your server can not handle this.
Action: The options to resolve this Oracle error are:
.Try to avoid using cursor variables as parameters for stored procedures.
.Upgrade your server to support cursor variables as parameters for stored procedures.

Error: ORA-06515: PL/SQL: unhandled exception error
Cause: You tried to execute a block of PLSQL code that raised an exception that was not handled by your code.
Action: The options to resolve this Oracle error are:
.Try to fix your code so that this exception is not raised.
.Modify your code to handle this exception. To learn more about handling exceptions, go to our Exception Handling webpages.

Error: ORA-06550: line num, column num: str
Cause: You tried to compile a block of PLSQL code, but a compilation error occurred.
Action: The options to resolve this Oracle error are:
.Refer to the line and column numbers (in the error message) to find the compilation error and correct it. Then try recompiling your code.

Error: ORA-06564: object name does not exist
Cause: You tried to reference an object that either does not exist or you do not have privileges to access it.
Action: The options to resolve this Oracle error are:
.If the object does not exist, create this object.
.If you do not have privileges to this object, ask the object owner or DBA to grant you access to it.

Error: ORA-06572: function name has out arguments
Cause: You tried to execute an SQL statement that referenced a package or function that contained an OUT parameter. This is not allowed.
Action: The options to resolve this Oracle error are:
.Remove the OUT parameter from the package or function, and re-execute the SQL statement.

Error: ORA-06575: function name is in an invalid state
Cause: You tried to execute an SQL statement that referenced a PLSQL function that is in an invalid state. This happens when the function is compiled with errors.
Action: The options to resolve this Oracle error are:
.Correct the errors and then re-compile the function. Then re-execute the SQL statement.

Error: ORA-08002: sequence NAME.CURRVAL is not yet defined in this session
Cause: You tried to execute a CURRVAL command on a sequence before the NEXTVAL command was executed at least once.
Action: The options to resolve this Oracle error are:
.Try executing the NEXTVAL command for the sequence, initially. Then call the CURRVAL command.

Error: ORA-08103: object no longer exists
Cause: You tried to execute an operation that referenced an object that has been deleted by another user.
Action: The options to resolve this Oracle error are:
.Re-create the object.
.Remove your reference to the object.

Error: ORA-12154: TNS:could not resolve service name
Cause: You tried to connect to Oracle, but the service name is either missing from the TNSNAMES.ORA file or is incorrectly defined.
Action: The options to resolve this Oracle error are:
.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 (ie: open bracket without the corresponding close bracket), the file will be rendered unusable.