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

LSX-00284: duplicate constraint name "~S"

1 Answers  

---

ORA-25186: INCLUDING clause specified for index-organized table without OVERFLOW

1 Answers  

---

TNS-12204: TNS:received data refused from an application

1 Answers  

---

NNL-00567: reorder_ns [<server_address>] : Generate the enhanced discovery file

1 Answers  

---

DRG-11841: Bad Gateway

1 Answers  

---

CLSR-01003: Error number encountered during mounting database

1 Answers  

---

ORA-29842: option not supported with the version string of the indextype interface

1 Answers  

---

SQL*Loader-00954: Error shipping index to read buffer across 2-task

1 Answers  

---

ORA-38422: invalid datatype for the attribute: string

1 Answers  

---

ORA-23433: executing against wrong master site string

1 Answers  

---

ORA-14275: cannot reuse lower-bound partition as resulting partition

1 Answers  

---

TNS-01181: Internal registration connection limit reached

1 Answers  

---