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

EXP-00058: Password Verify Function for string profile does not exist

1 Answers   MR,

---

ORA-26667: invalid STREAMS parameter string

1 Answers  

---

ORA-38441: System could not derive the list of STORED and INDEXED attributes.

1 Answers  

---

ORA-09762: sNeXT_instanceName: translation error.

1 Answers  

---

QSM-02031: materialized view cannot support any type of query rewrite

1 Answers  

---

ORA-21609: memory being resized without being allocated first

1 Answers  

---

RMAN-20039: format requires character when duplexing

1 Answers  

---

PCC-00141: Thread Safety is not implemented in this precompiler

1 Answers  

---

PLS-00588: unqualified instance attribute references allowed only in member methods

1 Answers  

---

NNL-00506: reset_stats [<server_list>] : reset Names server statistics

1 Answers  

---

ORA-22347: No changes to type specified for ALTER TYPE

1 Answers  

---

RMAN-06159: error while looking up backup set

1 Answers  

---