QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3152 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-32103: error from OCI call
PLS-00377: internal type PLS_INTEGER is not included in this release of PL/SQL
PLS-00131: Pragma string expects 2nd argument to be a procedure
ORA-07655: slsprom:$TRNLOG failure
ORA-36812: (XSTBLFUNC06) Invalid Syntax at '?'.
PLS-00225: subprogram or cursor 'string' reference is out of scope
IMG-00561: input format does not support channel selection
DRG-10000: failed to read column string.string
RMAN-06045: LEVEL option not supported for archive log or current/standby controlfile copies
ORA-07588: spdcr: $GETJPIW get image name failure
ORA-07600: slkmnm: $GETSYIW failure
LPX-00243: element attribute value must be enclosed in quotes
Oracle Errors 
