创建物化视图时遇见bug 9369183:

简介:
做数据库同步实验的时候创建prebuilt mv 时 总是提示 ora-32349 ,查询metalink后,发现这是一个bug。。。。
yang@rac1>create materialized view yangtab2
  2   on prebuilt table refresh fast
  3   as select * from yangtab2@linkyang;
 create materialized view yangtab2
       *
ERROR at line 1:
ORA-32349: cannot reference prebuilt table in definition query for materialized view

yang@rac1>alter table yangtab2 add constraint pk_yangtab2 primary key (id);
Table altered.
yang@rac1>create materialized view yangtab2
  2   on prebuilt table refresh fast
  3   as select * from yangtab2@linkyang;
create materialized view yangtab2
       *
ERROR at line 1:
ORA-32349: cannot reference prebuilt table in definition query for materialized view
Bug 9369183: MVIEW WITH PREBUILT TABLE ON SELECT FROM REMOTE TABLE RETURNS ORA-32349     
显示 Bug 属性 Bug 属性
类型     B - Defect     已在产品版本中修复     12.1
严重性     2 - Severe Loss of Service     产品版本     11.2.0.1
状态     80 - Development to Q/A     平台     46 - Linux x86
创建时间     10-Feb-2010     平台版本     NO DATA
更新时间     23-Dec-2010     基本 Bug     6815375
数据库版本     11.2.0.1         
影响平台     Generic         
产品源     Oracle         

显示相关产品 相关产品
产品线     Oracle Database Products     系列     Oracle Database
区域     Oracle Database     产品     5 - Oracle Server - Enterprise Edition
Hdr: 9369183 11.2.0.1 RDBMS 11.2.0.1 MATERIAL_VIEW PRODID-5 PORTID-46 6815375
Abstract: MVIEW WITH PREBUILT TABLE ON SELECT FROM REMOTE TABLE RETURNS ORA-32349
*** 02/10/10 08:30 pm ***
  BUG TYPE CHOSEN
  ===============
  Code
  SubComponent: Materialized Views
  ================================
  DETAILED PROBLEM DESCRIPTION
  ============================
  The ability to create an materialized view on prebuilt table with the same
  name as a remote table exists in 9i, 10g, and 11R1, but does not exist in
  11R2, hence the creation of this bug for 11R2.
  Test scenario:  
  Create table as user ABC in 9i database, and as user ABC in 11R2 database
  (tested in 9.2.0.8 and 11.2.0.1):
  CREATE TABLE TEST
  ( ID NUMBER,
  VAL NUMBER,
  VAL2 VARCHAR2(30),
  VAL3 CLOB,
  PRIMARY KEY (ID));
 
  Create database link (tested private dblink for user ABC, connecting to ABC
  in remote db) from 11R2 to 9i.
  Create database link (tested private dblink for user ABC, connecting to ABC
  in remote db) from 9i to 11R2.
  In 9i, as user ABC, issue:
  CREATE MATERIALIZED VIEW TEST ON PREBUILT TABLE FOR UPDATE AS SELECT * FROM
  TEST@;
  Materialized view created.
  -  Note that the mview/prebuilt table have the same name/same schema as the
  remote table in select clause of definition query
  -  You can do the above test above in 10g and 11R1, and you will be able to
  successfully create the mview.
  -  Please also note that you can successfully create the mview if the Test
  table exists locally but in a different schema.
 
  Drop the mview, then do the following: 
  In 11R2, as user ABC, issue:
 
  CREATE MATERIALIZED VIEW TEST ON PREBUILT TABLE FOR UPDATE AS SELECT * FROM
  TEST@STRM92P
       *
  ERROR at line 1:
  ORA-32349: cannot reference prebuilt table in definition query for
  materialized view
  -  This error is returned for this test in 11R2 only.
 
  Note that Bug 6815375 addressed an ORA-4020 returned on creation of mview
  with prebuilt table where prebuilt table is referenced as local table in
  definition query.  This bug was resolved with return of ORA-32349 for
  action.  Unfortunately, this error is now returned on mview with prebuilt
  table where prebuilt table is referenced as remote table in definition query
  (where the ORA-4020 did not occur in prior releases). 
  DIAGNOSTIC ANALYSIS
  ===================
  See above 
  WORKAROUND?
  ===========
  Yes 
  WORKAROUND INFORMATION
  ======================
  Create prebuilt table using different name as remote table in definition
  query.  However, for customer of this bug, plan is to drop mview in future
  with resultant change of prebuilt table to regular table - customer wants
  this table to have same name as remote table.  This is a reasonable request,
  as this worked previously without ORA-4020 or other error.
 
  TECHNICAL IMPACT
  ================
  See above
  RELATED ISSUES (bugs, forums, RFAs)
  ===================================
  Bug 6815375 - ATTEMPT TO CREATE A MV WITH 'ON PREBUILT TABLE' RESULTS IN A
  DEADLOCK
  HOW OFTEN DOES THE ISSUE REPRODUCE AT CUSTOMER SITE?
  ====================================================
  Always
 
  DOES THE ISSUE REPRODUCE INTERNALLY?
  ====================================
  Always
  IS A TESTCASE AVAILABLE?
  ========================
  Yes 
相关文章
|
6月前
|
安全 网络协议 搜索推荐
远控安全金标准,ToDesk、向日葵、网易UU安全功能盘点,是否能攻破防线
本文对ToDesk、向日葵和网易UU三款主流远程控制软件进行了安全性评测。远程控制技术虽带来便利,但也存在安全隐患。文章从设备授权管理、远程连接与数据传输、隐私安全机制及主动防诈保护四个方面展开分析。ToDesk在二次验证、金融窗口保护等方面表现突出;向日葵基础安全功能完善但缺乏创新;网易UU侧重基础功能,安全机制尚待完善。最终通过星级表对比,ToDesk综合表现最佳,向日葵次之,网易UU适合低风险场景。未来远控软件需向体系化、智能化方向发展以应对不断演变的威胁。
|
关系型数据库 MySQL Docker
docker环境下mysql镜像启动后权限更改问题的解决
在Docker环境下运行MySQL容器时,权限问题是一个常见的困扰。通过正确设置目录和文件的权限,可以确保MySQL容器顺利启动并正常运行。本文提供了多种解决方案,包括在主机上设置正确的权限、使用Dockerfile和Docker Compose进行配置、在容器启动后手动更改权限以及使用 `init`脚本自动更改权限。根据实际情况选择合适的方法,可以有效解决MySQL容器启动后的权限问题。希望本文对您在Docker环境下运行MySQL容器有所帮助。
2033 1
|
存储 开发框架 关系型数据库
【毕业设计之python系列】基Django的超市管理系统的设计与实现
【毕业设计之python系列】基Django的超市管理系统的设计与实现
740 0
|
1天前
|
云安全 人工智能 安全
AI被攻击怎么办?
阿里云提供 AI 全栈安全能力,其中对网络攻击的主动识别、智能阻断与快速响应构成其核心防线,依托原生安全防护为客户筑牢免疫屏障。
|
11天前
|
域名解析 人工智能
【实操攻略】手把手教学,免费领取.CN域名
即日起至2025年12月31日,购买万小智AI建站或云·企业官网,每单可免费领1个.CN域名首年!跟我了解领取攻略吧~
|
5天前
|
安全 Java Android开发
深度解析 Android 崩溃捕获原理及从崩溃到归因的闭环实践
崩溃堆栈全是 a.b.c?Native 错误查不到行号?本文详解 Android 崩溃采集全链路原理,教你如何把“天书”变“说明书”。RUM SDK 已支持一键接入。
449 192

热门文章

最新文章