QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3180 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 |
EXP-00055: %s.string is marked not exportable
LSX-00156: type is final and no derivations are allowed
NZE-29102: Cannot add certificate bag.
IMG-02008: 2FF08 - color histogram feature cannot be determined
ORA-07487: scg_init_lm: cannot create lock manager instance.
DRG-12231: an attr section named string already exists in this section group
NNL-00012: invalid "string" value "string"
ORA-13408: invalid blockSize storage parameter
ORA-19615: some files not found in backup set
ORA-16095: Dependent destination removal for inactivation
ORA-06561: given statement is not supported by package DBMS_SQL
NZE-28818: No package context provided.
Oracle Errors 
