Oracle - Errores y soluciones

Ratio: 4 / 5

ORA-00972: identifier is too long.

Cause: An identifier with more than 30 characters was specified.

Action: Specify at most 30 characters.

Ratio: 4 / 5

ORA-01036: illegal variable name/number

Cause: Unable to find bind context on user side

Action: Make sure that the variable being bound is in the sql statement.

Ratio: 4 / 5

ORA-01037: maximum cursor memory exceeded

Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor.

Action: Attempting to process a complex sql statement which consumed all available memory of the cursor.

Ratio: 4 / 5

 ORA-01003: no statement parsed

Cause: A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.

Action: Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor.

Ratio: 4 / 5

ORA-00912: input parameter too long

Cause: one of your input strings was too long

Action: shorten the input parameter length

Ratio: 4 / 5

ORA-00953: missing or invalid index name

Cause: An index name of the form [ <identifier> . ] <identifier> is expected but not present. If OIDINDEX clause, index name must be <identifier>

Action: Enter an appropriate index name.