Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3858 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-29844: duplicate operator name specified
PCC-00018: Expected "string", but found "string" at line number in file string
ORA-01724: floating point precision is out of range (1 to 126)
ORA-16710: The resource guard is out of memory.
LSX-00246: invalid QName "~S"
ORA-08263: ora_addr: cannot free listener address
ORA-28534: Heterogeneous Services preprocessing error
SQL*Loader-00426: count of elements in VARRAY string comes after the data for the varray
NNL-01078: Access/Create File Error : string
ORA-40273: invalid model type string for Adaptive Bayes Network algorithm
NNL-00970: System query index number: number
ORA-06438: ssaio: the asynchronous read was unable to read from the database file.
Oracle Errors 
