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-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.

1 Answers  

---

ORA-36682: (XSDPART20) Partition name string appears twice.

1 Answers  

---

ORA-01092: ORACLE instance terminated. Disconnection forced

1 Answers  

---

ORA-02443: Cannot drop constraint - nonexistent constraint

1 Answers  

---

ORA-24388: Unsupported functionality in fast path mode

1 Answers  

---

---

ORA-32809: foreign queue string is already registered

1 Answers  

---

NZE-28771: Data source is not yet initialized.

1 Answers  

---

ORA-02490: missing required file size in RESIZE clause

1 Answers  

---

ORA-16086: standby database does not contain available standby log files

1 Answers  

---

RMAN-06494: %s = string is out of range (string-string)

1 Answers  

---

PCB-00211: VARYING not supported with PIC N or PIC G variable "string"

1 Answers  

---

RMAN-06729: no backup of the SPFILE found to restore

1 Answers  

---