Bases de Datos

Ratio: 4 / 5

 ORA-00933: SQL command not properly ended.

Cause: The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order.

Action: Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces.

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.