logo  
Google
 

DB2 SQL-Error: -153

SQLState: 42809

Short Description: C THE STATEMENT REFERENCES WHICH IDENTIFIES AN RATHER THAN AN

The object object-name was specified as part of a statement, and refers to an object of type object-type instead of the expected type expected-object-type. The type of the object that is provided with the statement must match the type that is identified by expected-object-type. For example, if the satement is DROP ALIAS TED.T1, then TED.T1 must be an alias name. If object-type or expected-object-type is TABLE, and object-type or expected-object-type is a particular type of table, then the type of table was not valid for the statement that was specified. System action: The statement cannot be executed. Programmer response: Change the statement to match the type of object that is identified by expected-object-type. For example: v An ALTER VIEW statement must reference an existing view. v A COMMENT ON ALIAS statement must specify the name of an alias, and not the name of a table or view. v A COMMENT ON TABLE statement must reference an existing table or view. v A CREATE INDEX statement with the UNIQUE keyword must specify a table that is not a materialized query table. v A CREATE TRIGGER statement must specify a table in the ON clause that is not a materialized query table. That is, a trigger cannot be defined for a materialized query table. v A DROP ALIAS statement must specify the name of an alias, and not the name of a table or view. v A DROP TABLE statement must reference an existing table. If an alias is specified, then the table that the alias refers to is dropped. Use the DROP ALIAS statement to drop the alias. v A DROP VIEW statement must reference an existing view. v A REFRESH TABLE statement must refer to a materialized query table.

 <-  BACK TO INDEX