The object about which you are adding a comment must be in your own schema or:
To add a comment to a table, view, or materialized view, you must have
TABLE system privilege.
To add a comment to a unified audit policy, you must have the
SYSTEM system privilege or the
To add a comment to an edition, you must have the
EDITION system privilege, granted either directly or through a role.
To add a comment to an indextype, you must have the
INDEXTYPE system privilege.
To add a comment to a mining model, you must have the
MODEL system privilege.
To add a comment to an operator, you must have the
OPERATOR system privilege.
AUDIT POLICY Clause
You can view the comments on a particular unified audit policy by querying the
AUDIT_UNIFIED_POLICY_COMMENTS data dictionary view.
You can view the comments on a particular table or column by querying the data dictionary views
You can query the data dictionary view
ALL_EDITION_COMMENTS to view comments associated with editions that are accessible to the current user. You can query
DBA_EDITION_COMMENTS to view comments associated with all editions in the database.
In earlier releases, you could use this clause to create a comment on a materialized view. You should now use the
VIEW clause for materialized views.
MATERIALIZED VIEW Clause
Specify the name of the materialized view to be commented. If you omit
schema, then Oracle Database assumes the materialized view is in your own schema.
You can view the comments on a particular mining model by querying the
COMMENTS column of the data dictionary views
Specify the text of the comment. Refer to "Text Literals" for a syntax description of
Creating Comments: Example
To insert an explanatory remark on the
job_id column of the
employees table, you might issue the following statement:
COMMENT ON COLUMN employees.job_id IS 'abbreviated job title';
To drop this comment from the database, issue the following statement:
COMMENT ON COLUMN employees.job_id IS '';