• You must own any table containing columns you rename.

• Columns in X100 and heap tables can be renamed irrespective of the partition type or the partitioning state.

• The name of the new column must conform to the naming rules for columns (see Object Naming Rules).

• There must be no column already existing in the table having the same name.

• You cannot rename columns in a system catalog or in any table owned by the super user $ingres.

• If any procedures, views, constraints, or integrities refer to the table column being renamed, the rename operation will fail with errors. The rename operation also will fail if there are any procedures, rules, integrities, referential or check constraints, non-grant permits, or security alarms dependent on the table of the column being renamed.

• The ALTER TABLE RENAME COLUMN operation can be rolled back.

• Any forms, join definitions, or reports that refer to the old table column name will be invalidated; these must be recreated and reloaded. Any copydb or unloaddb scripts generated before renaming columns can no longer be used for reload operations.

• ALTER TABLE statements are not supported in Ingres Star. For more information, see the Star User Guide.

• Procedures are not permitted to execute ALTER TABLE statements.

• If a renamed table column is registered with Ingres Replicator, the dd_regist_tables and dd_regist_columns catalogs must be updated for the replication to work. For more information, see the Replicator User Guide.