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-32845: Messaging Gateway agent is already running

1 Answers  

---

RMAN-08020: including standby controlfile in backupset

1 Answers  

---

ORA-01537: cannot add data file 'string' - file already part of database

2 Answers  

---

ORA-12513: TNS:service handler found but it has registered for a different protocol

1 Answers  

---

ORA-27213: failed to unload Media Management Library

1 Answers  

---

RMAN-08536: channel string: autobackup found: string

1 Answers  

---

ORA-13607: The specified task or object string already exists

1 Answers  

---

NNF-04004: Invalid string in inputfile

1 Answers  

---

ORA-14134: indexes cannot use both DESC and REVERSE

1 Answers  

---

TNS-01306: nt secondary err code: number

1 Answers  

---

TNS-01090: No longer listening on: string

1 Answers  

---

ORA-32837: invalid configuration state string

1 Answers  

---