- ORA-00001
unique constraint violatedAn INSERT, UPDATE or MERGE tried to store a value that already exists in a column protected by a primary key or unique constraint. Find the constraint named in the message, see which columns it covers, and either change the value or update the existing row instead. - ORA-00020
maximum number of processes exceededThe instance reached its PROCESSES limit, so new connections are refused. Find out who is holding the connections, fix any connection leak, and raise PROCESSES only if the load is real. - ORA-00054
resource busy and acquire with NOWAIT specifiedAnother session holds a lock on the object or rows you need, and your statement was not allowed to wait for it. Find the blocking session, let it commit or roll back, then run your statement again. - ORA-00060
deadlock detected while waiting for resourceTwo sessions were each waiting for a lock the other held. Oracle broke the cycle by rolling back one statement in one of them. Make sessions lock rows in the same order, and index foreign key columns. - ORA-00257
archiver errorThe database cannot archive its redo logs, almost always because the archive destination or the fast recovery area is full. Sessions hang and new logins fail until space is freed. Back up and remove archive logs with RMAN, or enlarge the destination. - ORA-00600
internal error codeAn internal check inside the Oracle kernel failed. This is not a mistake in your SQL as such: it usually points to an Oracle bug or corruption. The first argument identifies the problem; look it up in My Oracle Support with the trace file in hand. - ORA-00904
invalid identifierOracle cannot find a column or name used in the statement. Usually the column is misspelled, belongs to another table, was created in quotes with a different case, or is a SELECT-list alias used in the WHERE clause. - ORA-00907
missing right parenthesisThe parser reached a point where it expected a closing parenthesis. Sometimes one really is missing, but often something inside the parentheses is not allowed there — such as ORDER BY inside an IN subquery or a wrong column definition in CREATE TABLE. - ORA-00911
invalid characterThe statement contains a character Oracle cannot accept at that point. In practice this is often a curly quote pasted from Word, Outlook or a web page, or an invisible character. Retype the quotes and the part around the error. - ORA-00913
too many valuesThe statement supplies more values than there are columns to receive them. Compare the column list with the VALUES list or the SELECT list, or the columns of a subquery with what the comparison expects. - ORA-00918
column ambiguously definedA column name exists in more than one table of the query and Oracle cannot tell which one you mean. Prefix the column with the table alias. - ORA-00932
inconsistent datatypesTwo values that must have the same type do not. The message says what Oracle expected and what it got. Convert one side explicitly with TO_DATE, TO_CHAR or TO_NUMBER, or fix the expression. - ORA-00933
SQL command not properly endedOracle reached text after what it considered the end of the statement. Common causes are a trailing semicolon in dynamic SQL, the keyword AS before a table alias, or a clause in the wrong place. - ORA-00936
missing expressionOracle expected a column, value or expression and found nothing usable — typically a trailing or double comma in the SELECT list, an empty SELECT, or a keyword where a value should be. - ORA-00942
table or view does not existOracle cannot find the table or view — or it exists but you have no privilege on it. Check the name and the schema prefix, then the privileges. Oracle deliberately shows the same error in both cases. - ORA-00947
not enough valuesThe statement supplies fewer values than there are columns to fill. Compare the column list with the VALUES or SELECT list and add what is missing. - ORA-00955
name is already used by an existing objectAn object with that name already exists in the schema. Tables, views, sequences, synonyms and most other objects share one namespace, so the existing object may be of another type. Rename, drop it, or make the script safe to re-run. - ORA-00979
not a GROUP BY expressionThe SELECT list contains a column that is neither in GROUP BY nor inside an aggregate function. Add it to GROUP BY, or wrap it in an aggregate such as MAX. - ORA-01000
maximum open cursors exceededOne session has more cursors open than OPEN_CURSORS allows. This is usually a leak: the application does not close its statements or result sets. Fix the leak first; raising the limit only delays the error. - ORA-01017
invalid username/password; logon deniedThe database rejected the login. Usually the password is wrong (passwords are case-sensitive), but the user may also not exist in the database or PDB you reached, or a SYSDBA login may not match the password file. - ORA-01031
insufficient privilegesYour user is missing a system or object privilege needed for the statement — for example CREATE TABLE, ALTER SYSTEM or EXECUTE on a package. Inside definer’s-rights PL/SQL, privileges granted through roles do not count. - ORA-01034
ORACLE not availableThe instance you tried to reach is not running. Either the database is down, or the client is pointing at a different instance than you think. Check the instance and ORACLE_SID, then start the database if it should be running. - ORA-01400
cannot insert NULL into columnAn INSERT left a NOT NULL column empty. The message names the column. Supply a value, give the column a default, or let a trigger or identity column fill it. - ORA-01403
no data foundIn PL/SQL, a SELECT … INTO returned no row (or code read an associative-array element that does not exist). Handle the NO_DATA_FOUND exception, or write the query so that “no row” is a normal result. - ORA-01422
exact fetch returns more than requested number of rowsIn PL/SQL, a SELECT … INTO returned more than one row. Make the WHERE clause unique, pick one row deliberately, or fetch into a collection or loop. - ORA-01427
single-row subquery returns more than one rowA subquery used where one value is expected — after =, or in the SELECT list — returned several rows. Use IN or EXISTS, aggregate the subquery, or make it return a single row. - ORA-01438
value larger than specified precisionA number has too many digits for its NUMBER(p,s) column. Remember that the digits before the decimal point are limited to p minus s. Fix the value or widen the column. - ORA-01476
divisor is equal to zeroAn expression divided by zero. Protect the division with NULLIF so that a zero divisor gives NULL instead of an error. - ORA-01555
snapshot too oldA long-running query needed an older version of some data to stay read-consistent, but that undo had already been overwritten. Make the query faster, keep undo longer (UNDO_RETENTION and a large enough undo tablespace), and avoid committing inside a loop over an open cursor. - ORA-01652
unable to extend temp segmentA sort, hash join or similar operation ran out of temporary tablespace. Very often the real cause is a bad execution plan, not a small tablespace. Find the statement using TEMP, fix it, and only then add space. - ORA-01653
unable to extend tableThe table needs a new extent and the tablespace has no room for it. Check the free space and the autoextend limits, then add or resize a datafile. - ORA-01722
invalid numberOracle tried to convert a character value to a number and the text was not a valid number. Often a VARCHAR2 column is compared to a number, so one bad row anywhere in the table breaks the query. - ORA-01843
not a valid monthA date string has a month Oracle cannot accept for the format in use. Usually the day and month are swapped, the month name is in another language, or the session’s default date format differs. Always use TO_DATE with an explicit format. - ORA-01861
literal does not match format stringA date string does not fit the format mask, or the session’s default date format if you gave none. Compare the string with the mask character by character, or use DATE '2026-10-15'. - ORA-02291
integrity constraint violated - parent key not foundYou inserted or updated a child row whose foreign key value has no matching row in the parent table. Insert the parent first, or correct the value. - ORA-02292
integrity constraint violated - child record foundYou tried to delete or change a parent row that child rows still reference. Delete or reassign the child rows first, or use ON DELETE CASCADE if that is the real rule. - ORA-03113
end-of-file on communication channelThe connection between the client and the server process was cut unexpectedly. The cause can be on either side: a server process that died, a network device closing idle connections, or a database that went down. Start with the alert log. - ORA-04031
unable to allocate shared memoryA memory pool in the SGA, usually the shared pool, could not provide a contiguous chunk. Common causes are SQL without bind variables, a pool that is too small, or fragmentation. Use bind variables first; flushing the pool is only a temporary relief. - ORA-04091
table is mutating, trigger/function may not see itA row-level trigger, or a function it calls, queried or changed the table that is being modified. The table is mid-change and its contents are not consistent. Use a compound trigger, or move the logic out of the row trigger. - ORA-06502
PL/SQL: numeric or value errorA PL/SQL assignment or conversion failed: most often a string is longer than the variable can hold (character string buffer too small), a text cannot become a number, or NULL went into a NOT NULL variable. - ORA-06550
PL/SQL compilation errorAn anonymous PL/SQL block failed to compile. ORA-06550 only gives the position: the real error is the PLS- line right after it. Read that one, and go to the line and column shown. - ORA-12154
TNS: could not resolve the connect identifierThe client could not turn the connection name you used into an address. The alias is not in the tnsnames.ora the client is reading, or the client is reading a different file than you think. Fix the alias or connect with host:port/service directly. - ORA-12170
TNS:Connect timeout occurredThe client tried to reach the database and got no answer in time. Usually a firewall silently drops the packets, or the host or port is wrong. Test whether the port is reachable from the client’s own machine. - ORA-12514
TNS: listener does not know of service requestedThe connection reached the listener, but the listener has no database service with the name you asked for. Check the service name, check that the database or PDB is open, and check that it is registered with this listener. - ORA-12541
TNS:no listenerThe client reached the host, but nothing is listening on that port. The listener is stopped, or the port in your connection is wrong. Start the listener or correct the port. - ORA-12899
value too large for columnA value is longer than the column allows. The message shows the actual and maximum length. With multi-byte data, a column sized in BYTE can overflow even when the text looks short enough — Turkish letters such as ğ, ş and ı take two bytes in AL32UTF8. - ORA-28000
the account is lockedThe account was locked, usually after too many failed logins (FAILED_LOGIN_ATTEMPTS in the profile), or by an administrator. A DBA can unlock it, but find out what keeps sending the wrong password first, or it will lock again. - ORA-28001
the password has expiredThe account’s password passed its PASSWORD_LIFE_TIME. Change the password. For application accounts, update it everywhere it is stored, and use a profile that fits a service account. - PLS-00201
identifier must be declaredPL/SQL cannot see the name you used. It is misspelled, not declared, in another schema without a prefix, or you lack the privilege. A privilege that comes through a role does not count inside a stored unit. - PLS-00306
wrong number or types of argumentsThe call does not match any version of the procedure or function: the number of arguments is wrong, or a type does not fit. Compare the call with the current specification.
Oracle is a registered trademark of Oracle Corporation. SQLlightspeed is not affiliated with Oracle.