Answer / guest

Cause: The materialized view log did not exist or could not
be used.

Action: Use just REFRESH, which will reinstantiate the
entire table. If a materialized view log exists and the form
of the materialized view allows the use of a materialized
view log, REFRESH FAST will be available starting the next
time the materialized view is refreshed.

Please add more information about this Error

ORA-16735: Error executing dbms_logstdby.unskip_error procedure

1 Answers  

---

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

1 Answers  

---

ORA-27155: could not execute file

1 Answers  

---

ORA-12053: this is not a valid nested materialized view

1 Answers  

---

ORA-19637: backupPieceCreate requires file name when using DISK device

1 Answers  

---

DRG-12306: column string is too long for index set columns

1 Answers  

---

ORA-12495: cannot disable an enabled level, category, or release category

1 Answers  

---

NZE-29241: a buffer block needs to more space but its length is fixed

1 Answers  

---

TNS-12551: TNS:missing keyword

1 Answers  

---

ORA-28174: Kerberos ticket not provided by proxy

1 Answers  

---

ORA-13902: The specified file string is not a data file.

1 Answers  

---

ORA-25009: Nested table clause allowed only for INSTEAD OF triggers

1 Answers  

---