DBMS_MVIEW.REFRESH Tries To Enable Row Movement For Matview Log
(Doc ID 2310432.1)
Last updated on FEBRUARY 17, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database - Enterprise Edition - Version 12.2.0.1 and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
In 11.2.0.3 as part of refresh process this procedure was executing
>> alter table "SCHEMA_NAME"."MLOG$__
Now in 12.2.0.1 the same procedure first execute:
>> alter table "SCHEMA_NAME"."MLOG$__
and then if row movement for mlog$ is disabled it turns it on:
>> alter table "SCHEMA_NAME"."MLOG$__
and then shrinks mlog$.
Constantly shrinking mlog$ during peak workload hours leads to user sessions waiting for TM locks on mlog$
Goal
To turn implicit shrinking of logs by refresh procedure off
Solution
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
Goal |
Solution |