Bases de Datos

Ratio: 4 / 5

 ORA-00913: too many values.

Cause: The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT.

Action: Check the number of items in each set and change the SQL statement to make them equal.

Ratio: 4 / 5

ORA-01091: failure during startup force.

Cause: Unable to destroy the old SGA.

Action: Manually remove the old SGA and reissue the STARTUP command.

Ratio: 4 / 5

ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected.

Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.

Action: Find the other sessions and log them out and resubmit the command.

Ratio: 4 / 5

ORA-00918: column ambiguously defined.

Cause: A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.

Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above.