ORA-00951: cluster not empty
Cause: A DROP CLUSTER statement specified a cluster that is not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause is specified. Tables may also be removed from a cluster by using the DROP TABLE command
Action: Either specify the INCLUDING TABLES clause in the DROP CLUSTER statement or remove all tables from the cluster with the DROP TABLE command before issuing the DROP CLUSTER command
ORA-00950: invalid DROP option
Cause: A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW
Action: Check the command syntax, specify a valid DROP option, then retry the statement
ORA-00949: illegal reference to remote database
Cause: This is an internal error message not usually issued
Action: Contact Oracle Support Services
ORA-00948: ALTER CLUSTER statement no longer supported
Cause: The ALTER CLUSTER statement has been withdrawn
Action: To add data to a cluster from an existing table, use the following series of SQL statements: CREATE TABLE newtable SELECT * FROM oldtable CLUSTER clustername;DROP oldtable;RENAME TABLE newtable oldtable;
ORA-00947: not enough values
Cause: This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in: WHERE (A,B) IN (SELECT C FROM …) Another common cause of this error is an INSERT statement in which the VALUES or SELECT clause does not contain enough values needed for the INSERT, as in INSERT INTO EMP(EMPNO,ENAME) VALUES(‘JONES’)
Action: Check the number of items in each set and change the SQL statement to make them equal
ORA-00946: missing TO keyword
Cause: A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered
Action: Check the syntax for the GRANT command, insert the keyword TO where required, and retry the statement
ORA-00945: specified clustered column does not exist
Cause: A column specified in the cluster clause of a CREATE TABLE statement is not a column in this table
Action: Re-execute the statement, using the names of columns defined for the table
ORA-00944: insufficient number of clustered columns
Cause: An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created
Action: Specify all cluster columns in the CREATE TABLE statement, then retry it
ORA-00943: cluster does not exist
Cause: The current user owns no cluster by the specified name
Action: Specify a valid cluster name following the keyword CLUSTER, then retry the statement
ORA-00942: table or view does not exist
Cause: The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it
Action: Check each of the following: the spelling of the table or view name. that a view is not specified where a table is required. that an existing table or view name exists. Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table. Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted