My Oracle Support Banner

Poorly Performing Materialized-View Refresh With Index Compression High (Doc ID 2677070.1)

Last updated on JUNE 12, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 19.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

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.

After introducing compression and encryption (for HIPAA compliance), a complete materialized-view refresh of  million rows is running for at least nineteen hours and not completing.

 The DDL in question is:

INSERT /*+ BYPASS_RECURSIVE_CHECK */
INTO <<<>>
.
.
.
SELECT ...
FROM  <<<>>>

SQL ID: 4pg5cdvctcd53


Was invoked by SQL_ID cks88p3q530h8:

  BEGIN

  DBMS_SNAPSHOT.REFRESH(
  LIST => '<<<>>>'
  ,METHOD => 'C'
  ,PUSH_DEFERRED_RPC => TRUE
  ,REFRESH_AFTER_ERRORS => FALSE
  ,PURGE_OPTION => 1
  ,PARALLELISM => 0
  ,ATOMIC_REFRESH => TRUE
  ,NESTED => FALSE
  ,OUT_OF_PLACE => FALSE
  ,SKIP_EXT_DATA => FALSE);

  END;


Changes

 This database was migrated  via Data Pump to a different host.

Compression and Encryption was introduced (for HIPAA compliance).

The index on the Mview was compressed using COMPRESS ADVANCED HIGH.

 

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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