Skip to content

Oracle Error Library

Look up an Oracle Database error by its ORA- or PLS- code or message: what it means, why it happens, read-only checks and safe fixes, based on Oracle's own error reference.

Common errors 13

ORA-00001 unique constraint violatedAn INSERT, UPDATE or MERGE would duplicate a primary key, unique constraint or unique index value. ORA-02291 integrity constraint violated - parent key not foundA foreign key value has no matching parent row. ORA-00942 table or view does not existThe table is missing, in another schema, not granted, or has a quoted name. ORA-00904 invalid identifierA column or name that does not exist, is out of scope, or needs quotes. ORA-01722 invalid numberA string could not be converted to a number. ORA-12899 value too large for columnA string is longer than the column allows (in bytes or characters). ORA-06502 PL/SQL: value or conversion errorA value did not fit a PL/SQL variable: string too long, too many digits, bad conversion or NULL into NOT NULL. ORA-06512 at line (PL/SQL error stack)A stack line, not the real error: read the error above it and the unit and line it names. ORA-01403 no data foundA SELECT INTO returned no rows (NO_DATA_FOUND). ORA-00060 deadlock detected while waiting for resourceTransactions waited on each other in a cycle; Oracle rolled back one statement. ORA-01017 invalid credential or not authorized; logon deniedWrong user name or password, password case, or the wrong PDB or service. ORA-12154 cannot find alias (could not resolve the connect identifier)The client could not resolve the alias or connect identifier through tnsnames.ora, Easy Connect or LDAP. ORA-12514 service is not registered with the listenerA listener answered but does not know the requested SERVICE_NAME: wrong name, PDB or instance not open, or not registered yet.

PL/SQL & Triggers 11

ORA-06502 PL/SQL: value or conversion errorA value did not fit a PL/SQL variable: string too long, too many digits, bad conversion or NULL into NOT NULL. ORA-06512 at line (PL/SQL error stack)A stack line, not the real error: read the error above it and the unit and line it names. ORA-01403 no data foundA SELECT INTO returned no rows (NO_DATA_FOUND). ORA-01422 exact fetch returned more than the requested number of rowsA SELECT INTO or RETURNING INTO returned more than one row (TOO_MANY_ROWS). ORA-01008 value for bind variable placeholder was not providedA statement ran without a value for one of its bind placeholders (USING clause, repeated placeholder, driver binds). ORA-06550 line, column: (PL/SQL compilation error)A PL/SQL block failed to compile; the PLS- error on the next line says why. ORA-04091 table is mutating, trigger/function may not see itA row trigger or a function called from DML read or changed the table being modified. ORA-20000 user-defined error (RAISE_APPLICATION_ERROR, ORA-20000 to ORA-20999)An application error raised on purpose with RAISE_APPLICATION_ERROR; the message is the application's. PLS-00201 identifier must be declaredA name could not be resolved: misspelt, out of scope, missing, or no direct privilege (roles do not count in stored code). PLS-00103 Encountered the symbol ... when expecting one of the followingA PL/SQL syntax error: a missing semicolon, END or THEN, a reserved word as a name, or DDL in a block. PLS-00306 wrong number or types of arguments in callA call matches no declaration of the subprogram: wrong argument count, wrong types or no matching overload.
No errors match. Press Search to search full messages, or browse every error.