1 – COMMENT IS string
The COMMENT IS clause can be used to modify the comment stored
with the query outline. The COMMENT ON statement is identical in
function to the ALTER OUTLINE . . . COMMENT IS clause.
This clause is equivalent to the COMMENT ON procedure.
2 – COMPILE
The COMPILE option can be applied to query outlines that have
been made invalid by DROP TABLE or DROP INDEX. If the tables and
indices have been recreated then the query outline will be made
valid again. For example, once re-validated the optimizer will
try to use that query outline.
NOTE
There is a possibility that the query outline although
marked valid will not be used because of changes in the
index definition. There is too little information stored
with the query outline to perform a complete consistency
check. If possible, queries using this outline should be run
to verify correct index and table usage.
If the query outline is currently valid then this clause is
ignored by Oracle Rdb.
3 – MOVE_TO
MOVE TO is valid only for multischema databases. You must be
attached explicitly or implicitly with the MULTISCHEMA IS ON
clause. The MOVE TO clause can be used to move the query outline
to a different catalog and schema. An error will be raised if
this clause is specified in a non-multischema environment.
The target catalog and schema must exist in this database.
4 – RENAME_TO
The RENAME TO clause can be used to change the name of the
outline. The new name must not already exist in the database.
If RENAME TO is used in a multischema database, attached with
MULTISCHEMA IS ON, then only the multischema name is modified
not the STORED NAME of the object. To change the STORED NAME of
the query outline you must attach to the database explicitly with
the MULTISCHEMA IS OFF clause (see the example below). Please
note that the STORED NAME for the query outline may have been
generated by Oracle Rdb.
NOTE
Any queries using the OPTIMIZE USING clause will also need
to be changed to reference this new outline name.