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

IMP-00002: failed to open string for read

1 Answers  

---

ORA-01527: error while reading file

1 Answers  

---

ORA-29395: cannot set the initial consumer group to string

1 Answers  

---

ORA-14157: invalid subpartition name

1 Answers  

---

ORA-08312: sllfop: unrecognized processing option

1 Answers  

---

ORA-01245: offline file string will be lost if RESETLOGS is done

2 Answers  

---

PLS-00643: booleans, index tables, records and cursors not allowed in SQL statements

1 Answers  

---

ORA-23381: generated object for base object string.string@string does not exist

1 Answers  

---

ORA-09285: sllfop: unrecognizable processing option, incorrect format

1 Answers  

---

ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists

1 Answers  

---

ORA-12500: TNS:listener failed to start a dedicated server process

1 Answers  

---

ORA-01511: error in renaming log/data files

1 Answers  

---