Note
For V4.4.2, REFRESH_REPORT was introduced starting from V4.4.2 BP2.
REFRESH_REPORT is used to generate a hierarchical diagnostic report for a single materialized view refresh task.
Limitations and considerations
Specify at least one of refresh_id and mv_name.
Syntax
DBMS_MVIEW.REFRESH_REPORT(
{refresh_id | mv_name}
[, format]
[, tenant_id])
Parameters
Parameter |
Note |
|---|---|
| refresh_id | The refresh ID uniquely identifies a batch of materialized view refreshes and is assigned by the new scheduling framework.
NoteYou can view the |
| mv_name | Specify the name of the materialized view (for example,SCHEMA.MV_NAME). |
| format | Optional. Specifies the report output format. Valid values:
|
| tenant_id | Currently onlysysTenant available, used to query the materialized view refresh reports of other tenants. |
Return value
- Return type:
CLOB. - Content format: Depends on the
formatparameter. It can be text inXMLorJSONformat.
Examples
Retrieve the diagnostic report in
XMLformat by using therefresh_idparameter.obclient> SELECT DBMS_MVIEW.REFRESH_REPORT(refresh_id=> 100023);Obtain a report in JSON format.
obclient> SELECT DBMS_MVIEW.REFRESH_REPORT(refresh_id=> 100023, format => 'JSON');Retrieve the most recently refreshed report by materialized view name.
obclient> SELECT DBMS_MVIEW.REFRESH_REPORT(mv_name=> 'TEST.MV_SALES_DAILY');The
systenant queries the refresh reports of other tenants.obclient> SELECT DBMS_MVIEW.REFRESH_REPORT(refresh_id=> 100023, tenant_id=> 1002);