Neoview SQL Reference Manual (R2.3)

other-options
CONTINUE ON ERROR
If any of the maintain tasks return an error, that error is returned and execution continues
to the next task. Default is to continue on error.
STOP ON ERROR
If any of the maintain tasks return an error, that error is returned and execution stops.
RETURN DETAIL STATUS
displays detailed status message from each of the individual tasks. The default is OFF.
DISPLAY
displays the tasks that are scheduled to be executed without actually executing them.
DISPLAY DETAIL
displays the tasks and the queries that will be used to execute them without actually
executing the tasks.
control-options
DISABLE
disables the maintain task. A maintain command issued after the task has been disabled
will have no affect. The task will have to be explicitly enabled before performing it. This
option is only available for REORG TABLE and UPDATE STATISTICS TABLE tasks.
Disabling REORG of the table also disables REORG of all indexes.
ENABLE
enables the maintain task that was previously disable using the DISABLE command. This
option is only available for REORG TABLE and UPDATE STATISTICS TABLE tasks.
Enabling REORG of the table also enables REORG of all indexes.
These control options are available for:
• REORG and UPDATE STATISTICS for TABLE
• REORG, REFRESH, and UPDATE STATISTICS for materialized view
• Disabling REORG of table also disables reorg of all indexes
• Enabling of REORG of table also re-enables reorg of all indexes
The DISPLAY option can be used to see whether the status of the task is enabled or disabled.
For additional information on materialized views, see “CREATE MATERIALIZED VIEW
Statement” (page 60).
MAINTAIN MVGROUP
MAINTAIN MVGROUP mvgroupname, REFRESH mv-refresh-option
mv-refresh-option is:
[RECOMPUTE | CANCEL]
[{WITH | WITHOUT |DO ONLY} MVLOG CLEANUP
mvgroupname
is the ANSI name of the materialized view group to be maintained. It can be a one or two-part
name.
The REFRESH utility can be applied to both incremental MVs and recomputed MVs. The
REFRESH utility optimizes the refresh of MVGROUP. HP recommends that you gather all the
MVs to refresh at a specific time into one group and refresh them together.
If for any reason the refresh of some MVs in the MVGROUP fails, the utility reports the failures.
In case of partial failure, you can refresh either the whole MV group or specific MVs again. If
the base tables did not change since the last attempt to refresh, no performance penalty is incurred.
In an environment where updates happen continuously, all the MVs are affected by the second
refresh. Refreshing individual MVs out of group context might lead to a state where different
MVs in the group are not in sync with each other.
194 SQL Utilities