ORA-25175 when trying to create materialized view, organization index SOLV

Question

Hi,
I'm trying to create a materialized view to compensate for non-normalized table.
I have table anormal, and mv is to be on distinct agency, company in that table.
Here goes:
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE    10.2.0.3.0      Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Productio
NLSRTL Version 10.2.0.3.0 - Production
SQL> create table anormal (company varchar2(8) not null
  2                       ,dept varchar2(8) not null
  3                       ,agency varchar2(8) not null
  4                       ,constraint anormal_pk primary key (company,dept));
Table created.
SQL> insert into anormal values('c1', 1, 'Ajax');
1 row created.
SQL> insert into anormal values('c1', 2, 'Ajax');
1 row created.
SQL> insert into anormal values('c1', 3, 'Acme');
1 row created.
SQL> insert into anormal values('c2', 1, 'Acme');
1 row created.
SQL> insert into anormal values('c2', 2, 'Acme');
1 row created.
SQL> commit;
Commit complete.
SQL> select * from anormal;
COMPANY  DEPT     AGENCY
c1       1        Ajax
c1       2        Ajax
c1       3        Acme
c2       1        Acme
c2       2        Acme
SQL> create materialized view agency_comp_mv
  2  organization index --primary key (agency, company)
  3  build deferred
  4  refresh on demand
  5  as
  6  select distinct agency, company from anormal
  7  /
select distinct agency, company from anormal
ERROR at line 6:
ORA-25175: no PRIMARY KEY constraint found
SQL>The error tells me that there is no primary key, but is there any way to add such?
- or is my problem rather that I cannot use DISTINCT with organization index?
Regards
Peter
bump
Message was edited by:
Peter Gjelstrup
<SOLVED>
Message was edited by:
Peter Gjelstrup

Answer 1

Thanks William,
I tried with ON PREBUILT TABLE, just to see what happens.
Building on my OP:
SQL> create table iot(agency varchar2(8) not null, company varchar2(8) not null
  2                  ,constraint iot_pk primary key (agency,company))
  3  organization index;
Table created.
SQL> insert into iot select distinct agency, company from anormal;
4 rows created.
SQL> commit;
Commit complete.
SQL> create materialized view iot on prebuilt table
  2  as
  3  select distinct agency, company from anormal;
Materialized view created.
SQL> select * from iot;
AGENCY   COMPANY
Acme     c1
Acme     c2
Ajax     c1
SQL> insert into anormal values('c3', 2, 'Foo');
insert into anormal values('c3', 2, 'Foo')
1 row created
SQL> select * from anormal;
COMPANY  DEPT     AGENCY
c1       1        Ajax
c1       2        Ajax
c1       3        Acme
c2       1        Acme
c2       2        Acme
c3       2        Foo
6 rows selected.
SQL> select * from iot;
AGENCY   COMPANY
Acme     c1
Acme     c2
Ajax     c1
3 rows selectedNow, try to refresh and MV
SQL> alter materialized view iot refresh complete;
Materialized view altered.
SQL> select object_type, to_char(last_ddl_time, 'hh:mi:ss'), status
  2    from user_objects where object_name = 'IOT';
OBJECT_TYPE         DDL_TIME STATUS
TABLE               10:40:42 VALID
MATERIALIZED VIEW   10:41:13 VALID
SQL> select * from iot;
AGENCY   COMPANY
Acme     c1
Acme     c2
Ajax     c1Agency "Foo" is not in MV,
Looks like that IOT select'ed from is indeed the MV:
SQL> drop table iot;
drop table iot
ERROR at line 1:
ORA-12083: must use DROP MATERIALIZED VIEW to drop "STIK"."IOT"
SQL>So, seems that Maxim is right, it just can't be done. And it seems my options are:
Create HEAP organized MV or
Create and maintain IOT
Regards
Peter