Wrong Results When Creating Materialized View On Remote View Based on External Table
(Doc ID 467642.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.
Creating a materialized view based on remote table works fine, but when the materialized view is based on a remote view, data in the mview is wrong.
Varchar2 columns contain nulls, columns which are not empty contain invalid data (source data is unique against a set of columns but the result is not).
Any select statement used in mview definition works correctly (there is some data in varchar2 columns and the data is unique).
Database Versions Involved:
Master : 22.214.171.124 - Mview : 10.2.0.3 : Problem reproduces
Master : 126.96.36.199 - Mview : 188.8.131.52 : Problem reproduces
Master : 10.2.0.3 - Mview : 10.2.0.3 : ORA-1452 creating the Mview
Master : 10.2.0.3 - Mview : 184.108.40.206 : Not tested
Local Mview on 220.127.116.11 : Data correct
Local Mview on 10.2.0.3 : Data correct.
Steps to Reproduce:
CREATE TABLE test1
(M_ROW$$ default '00000000.0000.0000',
GM***||' ('||R**_G****||')' FROM
Data in table test1 is nulled.
If table is created on 10.2.0.3 based directly on the table on 18.104.22.168 without rowid, the results are correct:
CREATE TABLE test2
'3', 'm****-w****') ||')'
WHERE k**_*i IS NOT NULL AND k**_g* IS NOT NULL AND k**_g*** IS NOT NULL;
If the mview is created directly on the table on 22.214.171.124 the results are correct.
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