Answer / guest

Cause: The explain_mview assumes that the materialized view
is going to be created as the Primary Key materialized view.
A Primary Key materialized view can not be created if the
base table does not have a primary key constraint.

Action: Add a primary key constraint to the base table, or
create the materialized view as Rowid MV by specifying the
WITH ROWID option. If the materialized view is a Rowid MV,
then it should be able to do complete refresh and even fast
refresh, given that the materialized view log on the master
table has a rowid.

Please add more information about this Error

ORA-30649: missing DIRECTORY keyword

1 Answers  

---

ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword

1 Answers  

---

DRG-12437: highlight table release failed

1 Answers  

---

IMG-00604: unable to access destination image data

1 Answers  

---

ORA-16006: audit_trail destination incompatible with database open mode

1 Answers  

---

ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint

1 Answers  

---

QSM-01044: join back attempted on a view for string

1 Answers  

---

QSM-01082: Joining materialized view, string, with table, string, not possible

1 Answers  

---

PLS-00211: CASE labels or ranges must not be duplicated in different WHEN clauses

1 Answers  

---

ORA-22809: nonexistent attribute

1 Answers  

---

ORA-28653: tables must both be index-organized

1 Answers  

---

IMG-00554: extra value in rotate operation

1 Answers  

---