2 Day Developer > Using PL/SQL > Handling PL/SQL Errors > Summary of Predefined PL/SQ...
Summary of Predefined PL/SQL Exceptions |
Previous |
Next |
An internal exception is raised automatically if your PL/SQL program violates an Oracle rule or exceeds a system-dependent limit. In PL/SQL common Oracle errors are predefined as exceptions. For example, PL/SQL raises the predefined exception NO_DATA_FOUND
if a SELECT
INTO
statement returns no rows. To handle unexpected Oracle errors, you can use the OTHERS
handler.
PL/SQL declares predefined exceptions globally in package STANDARD
so you do not need to declare them. You can write handlers for predefined exceptions using the predefined names. Table: Predefined PL/SQL Exceptions lists some of the predefined exceptions.
Predefined PL/SQL Exceptions
Exception | Description |
---|---|
A program attempts to assign values to the attributes of an uninitialized object |
|
None of the choices in the |
|
A program attempts to apply collection methods other than |
|
A program attempts to open a cursor that is already open. A cursor must be closed before it can be reopened. A cursor |
|
A program attempts to store duplicate values in a column that is constrained by a unique index. |
|
A program attempts a cursor operation that is not allowed, such as closing an unopened cursor. |
|
In a SQL statement, the conversion of a character string into a number fails because the string does not represent a valid number. (In procedural statements, |
|
A program attempts to log on to Oracle Database XE with a user name or password that is not valid. |
|
A Because this exception is used internally by some SQL functions to signal completion, do not rely on this exception being propagated if you raise it within a function that is called as part of a query. |
|
A program issues a database call without being connected to Oracle Database XE. |
|
The host cursor variable and PL/SQL cursor variable involved in an assignment have incompatible return types. When an open host cursor variable is passed to a stored subprogram, the return types of the actual and formal parameters must be compatible. |
|
A program references a nested table or varray element using an index number larger than the number of elements in the collection. |
|
A program references a nested table or varray element using an index number (-1 for example) that is outside the legal range. |
|
A |
|
An arithmetic, conversion, truncation, or size-constraint error occurs. For example, when your program selects a column value into a character variable, if the value is longer than the declared length of the variable, PL/SQL cancels the assignment and raises |
|
A program attempts to divide a number by zero. |