Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3774 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 |
RMAN-06560: WARNING: backup set with key number will be read number times
NNO-00622: warning: too many auto-refresh failures for name "string", query expired
LPX-00115: element "~1S" is missing required attribute "~2S"
ORA-13759: User "string" cannot remove reference "string".
ORA-27198: skgfpvl: sbtpcvalidate returned error
ORA-40003: wordsize must be in the range string - string for BLAST-P
ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive
ORA-07223: slspool: fork error, unable to spawn spool process.
ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate
NNC-00408: name "string" exists but desired data does not
ORA-24327: need explicit attach before authenticating a user
ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT variable.
Oracle Errors 
