-607 OPERATION OR OPTION operation IS NOT DEFINED FOR THIS OBJECT

Explanation

The operation or option cannot be performed on the object specified in the SQL statement.

For example, this SQL code might be issued for the following situations:

• The ownership of most system objects cannot be transferred if their OWNER is SYSIBM or if their schema begins with SYS.
• CREATE or DROP statements cannot be issued for objects in the the Db2 catalog (DSNDB06) database.
• LOGGED and NOT LOGGED cannot be set when you create or alter a table space in the Db2 catalog (DSNDB06) database.
• Catalog and directory objects cannot be cloned.
• Data change operations such as these cannot be performed on a directory table:
  • ALTER TABLE
  • ALTER TABLESPACE
  • DELETE
  • MERGE
  • UPDATE
  • RENAME TABLE
• The following operations are not allowed for an index on a directory table:
  • ALTER INDEX
  • CREATE INDEX
  • DROP INDEX
  • RENAME INDEX
  
• A directory table cannot be:
  • The parent table in a referential relationship
  • The triggering table in a trigger
  
• An ALTER TABLE statement that specifies operation cannot be specified on a catalog table.
• A period specification must not be used if the table reference is not a table.
• The operation is a SELECT statement, and a target of the operation is a directory object. Db2 cannot convert the SELECT statement to the UR isolation level. For example, the following SQL statement cannot be executed because the SELECT operation against directory object SYSIBM.SYSLGRNX cannot be converted to the UR isolation level:

  UPDATE T1 SET C1 = (SELECT C1 FROM T1)
    WHERE EXISTS(SELECT LGRDBID FROM SYSIBM.SYSLGRNX);

• FL 508 An ALTER TABLESPACE statement that includes a MOVE TABLE clause must not specify a catalog or directory table space.
• An ALTER TABLE statement that specified an ADD VERSIONING clause on a security-related catalog table must specify the corresponding catalog history table.