My Oracle Support Banner

How to Cancel a Refresh Operation of a Materialized View (MV) When it is Scheduled via Job (Doc ID 806833.1)

Last updated on FEBRUARY 21, 2024

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Refreshing a materialized view (MV) is controlled by either

  • a user of the RDBMS initiating a refresh
  • a commit
  • a job scheduled to run at pre-determined times

This article deals with the scenario where an MV is refreshed via a scheduled job, similar to the following definition:

Note that the NEXT phrase specifies that the MV should be refreshed automatically every day at 01:00 at night (1 AM).

If this job fails to complete, the job subsystem will reschedule the job to run again.

This may lead to a situation where the system becomes busy always attempting to complete a refresh, specifically if the MV is more complex than the one shown in this (simple) example.

The solution below explains how to stop a job from running and from being rescheduled over and over so that corrective action can be taken.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.