Oracle案例02——ORA-12034: "SCOTT"."USER_TABLE" 上的实体化视图日志比上次刷新后的内容新

最近同事在交接工作时,发现有几个schedule job没有执行成功,我这边给看了下,其中一个是由于数据库迁移,调用dblink的host主机IP在tnsnames中没有变更导致,还有一个是无法视图的报错,即报错信息如下:

一、错误日志

通过查看schedual job报错日志,具体报错信息如下

ORA-12034:"SCOTT"."USER_TABLE" 上的实体化视图日志比上次刷新后的内容新
ORA-06512: 在 "SYS.DBMS_SNAPSHOT", line 2563
ORA-06512: 在 "SYS.DBMS_SNAPSHOT", line 2776
ORA-06512: 在 "SYS.DBMS_SNAPSHOT", line 2745
ORA-06512: 在 line 2

二、错误原因

一般出现这个错误是在刷新物化视图,方式为fast的时候会出现(ORA-12034 is a timing issue that occurs when performing a fast refresh of a materialized view.)

When a materialized view log is created for a master table, and a materialized view has been created with the REFRESH FAST option, the following timestamps will be used when validating log age.
At the materialized view site:
- Information about the last refresh time for each materialized view. The last refresh time is recorded as the timestamp when the last refresh completed successfully.
At the master table site:
- Information about the last refresh time for every materialized view using a materialized view log on that site.
The timestamps at the master site are used for two purposes:
- To maintain information concerning which rows are needed to fast refresh each individual registered materialized view.
- To maintain information concerning which rows can be purged from the materialized view log.
When a fast refresh starts, the last refresh timestamp from the materialized view site for the refreshing materialized view is compared to the oldest timestamp of ANY materialized view using the same materialized view log as the one currently being refreshed. If the oldest timestamp is newer than the materialized view site timestamp, ORA-12034 is raised. By doing this it is ensured that all changed rows since the last refresh will be refreshed, and if this can‘t be ensured, a complete refresh is forced. There‘s no exception to this behavior, and violating this main rule will result ORA-12034. 

1、Dropping / recreating the materialized view log on the master table.(在主表上删除或重建物化视图日志)

If a materialized view was created at time T1 and materialized view log was created at time T2, we can‘t ensure that all changes made between T1 and T2 will be in the materialized view after fast refresh. Therefore complete refresh is mandatory. 

2、Creating the materialized view before the materialized view log.(物化视图创建早于物化视图日志)

 The explanation here is the same as in Section 2.1. 

3、The previous refresh for the materialized view did not complete successfully.(之前的物化视图刷新没有成功)

When a refresh starts, the last refresh time of the materialized view is set to ‘01-JAN-1950‘. This guarantees that if the refresh fails for any reason, then an ORA-12034 error will be signaled and a complete refresh will be forced. When the refresh succeeds, this date is updated to the proper time. If it doesn‘t get updated because of some failure during the refresh, the next time the refresh runs, ‘01-JAN-1950‘ is used to validate the log age. 

4、 Creating a materialized view takes longer than the time it takes all other materialized views currently using the materialized view log to refresh.

If there are other materialized views using the materialized view log on the master table, and all of these other materialized views start their refreshes AFTER the new materialized view creation has started but complete their refreshes BEFORE the new materialized view creation has completed, then fast refreshes will fail with ORA-12034. Materialized view registration is based on the starting time of the creation, but as the last step of the operation. If that start time is older than the oldest timestamp currently registered, the new materialized view will not be registered. A complete refresh is required to register the materialized view, but it may not avoid the ORA-12034 error the next time a fast refresh is attempted.

There are three ways to resolve this problem:

- Stop the refresh of at least one other materialized view that is using the materialized view log before
creating the new one.
- In production system the previous option might not be possible. For this situation, a temporary materialized view can be created which uses the same log. If this temporary materialized view is not refreshed while the new materialized view is created, the new materialized view creation can complete successfully.
- Use deployment templates to create the materialized view environment at materialized view sites. This problem will not occur if deployment templates are used. See the Advanced Replication documentation for information about deployment templates. 

5 、Certain DDL changes to the master table have been performed.

6、 Master table reorganization.

7、 Materialized view registration failed at the master site.

8、Incorrect conversion of a materialized view log from ROWID to primary key.

9、Manual deletion of sys.slog$ entry for the materialized view.

三、解决方案

1、全量刷新物化视图

exec dbms_mview.refresh(‘SCOTT.USER_TABLE‘,‘C‘);

exec dbms_mview.refresh(‘SCOTT.USER_TABLE‘);

2、调整快速舒心日志内容

select * from sys.slog$
SELECT SOWNER, VNAME, MOWNER, MASTER, to_char(SNAPTIME,‘yyyy-mm-dd hh24:mi:ss‘) FROM SYS.SNAP_REFTIME$;
insert into sys.slog$ values(‘DHSH‘,‘USER_BASIC‘,NULL,171,NULL,to_date(‘2014-01-07 15:44:18‘,‘yyyy-mm-dd hh24:mi:ss‘),null,null);
commit;

四、附录

1、MOS方案

Diagnosing ORA-12034 Materialized View Log Younger Than Last Refresh (文档 ID 204127.1)

(1)Error Definition and Description

Error Definition

Oracle 8i and below: ORA-12034: "snapshot log on "%s"."%s" younger than last refresh"
Oracle 9i and above: ORA-12034: "materialized view log on "%s"."%s" younger than last refresh"

Cause: The materialized view log was younger than the last refresh.
Action: A complete refresh is required before the next fast refresh.

Note: A complete refresh can be done using the command:

execute dbms_mview.refresh(‘"CORP"."NM_SV_RANGE"‘,‘C‘);

2、全量刷新物化视图

原文地址:https://www.cnblogs.com/rangle/p/8480394.html

时间: 2024-10-03 15:21:26

Oracle案例02——ORA-12034: "SCOTT"."USER_TABLE" 上的实体化视图日志比上次刷新后的内容新的相关文章

Oracle实体化视图

1.减轻网络负担:通过MV将数据从一个数据库分发到多个不同的数据库上,通过对多个数据库访问来减轻对单个数据库的网络负担. 2.搭建分发环境:通过从一个中央数据库将数据分发到多个节点数据库,达到分发数据的目的. 3.复制数据子集:MV可以进行行级/列级的筛选,这样可以复制需要的那一部分数据. create materialized view [view_name] {TABLESPACE (表空间名)}              --保存表空间 {BUILD [DEFERRED|IMMEDIATE

Oracle数据库入门——物化视图日志结构

物化视图的快速刷新要求基本必须建立物化视图日志,这篇文章简单描述一下物化视图日志中各个字段的含义和用途. 物化视图日志的名称为MLOG$_后面跟基表的名称,如果表名的长度超过20位,则只取前20位,当截短后出现名称重复时,Oracle会自动在物化视图日志名称后面加上数字作为序号. 物化视图日志在建立时有多种选项:可以指定为ROWID.PRIMARY KEY和OBJECT ID几种类型,同时还可以指定SEQUENCE或明确指定列名.上面这些情况产生的物化视图日志的结构都不相同. 任何物化视图都会包

Oracle数据库入门——如何根据物化视图日志快速刷新物化视图

Oracle物化视图的快速刷新机制是通过物化视图日志完成的.Oracle如何通过一个物化视图日志就可以支持多个物化视图的快速刷新呢,本文简单的描述一下刷新的原理. 首先,看一下物化视图的结构:SQL> create table t(id number, name varchar2(30), num number);表已创建. SQL> create materialized view log on t with rowid, sequence(id, name) including new v

Oracle 物化视图日志

一.物化视图日志是什么 oracle 的物化视图的快速刷新要求必须建立物化视图日志,通过物化视图日志可以实现增量刷新功能. 官方文档给出的对物化视图日志的释义: A materialized view log is required on a master to perform a fast refresh on materialized views based on the master. When you create a materialized view log for a master

【oracle案例】RMAN-06556

1.1.1. RMAN-06556 日期:2014-05-21 16:33 环境:测试环境 [情景描述] 使用RMAN进行了全库备份,但是在进行不完全恢复的时候遇到报错,提示某个数据文件必须从比给出的SCN更早的备份中恢复. [报错信息] 备份数据库: RMAN> backup database plus archivelog; Starting backup at 2014-05-21 15:02:13 current log archived ...... Finished backup a

【oracle案例】ORA-19573

1.1.1. ORA-19573 日期:2014-05-21 17:25 环境:测试环境 [情景描述] 数据库实例处于OPEN状态(READ WRITE),这时在RMAN中执行数据库还原.恢复操作遇到报错. [报错信息] RMAN> run { 2> allocate channel ch1 type disk; 3> allocate channel ch2 type disk; 4> set until scn 1520939; 5> restore database;

ORACLE配置tnsnames.ora文件实例

ORACLE配置tnsnames.ora文件实例客户机为了和服务器连接,必须先和服务器上的监听进程联络.ORACLE通过tnsnames.ora文件中的连接描述符来说明连接信息.一般tnsnames.ora 是建立在客户机上的.如果是客户机/服务器结构,整个网络上只有一台机器安装了ORACLE数据库服务器,那么只需在每个要访问ORACLE服务器的客户机上定义该文件,在服务器上无需定义.但是,如果网络上有多台机器均安装了ORACLE数据库服务器,并且服务器之间有数据共享的要求,那么在每台服务器上都

【oracle案例】ORA-19502,ORA-27072

1.1.1. ORA-19502,ORA-27072 日期:2014-05-12 00:12 环境:测试机 [错误号] $ oerr ora 19502 19502, 00000, "write error on file\"%s\", block number %s (block size=%s)" // *Cause: write error on output file // *Action: check the file $ oerr ora 27072 2

【翻译自mos文章】怎么检查Oracle Advanced Security Option 是否被安装上?

怎么检查Oracle Advanced Security Option 是否被安装上? 来源于: How To Check if Oracle Advanced Security Option is Installed ? (文档 ID 549989.1) 适用于: Advanced Networking Option - Version 9.2.0.1 to 11.2.0.3 [Release 9.2 to 11.2] Information in this document applies