QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3475 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-07290: sksagdi: specified directory for archiving does not exist.
ORA-13525: error with computing space usage for sysaux occupant
ORA-04084: cannot change NEW values for this trigger type
ORA-12615: TNS:preempt error
O2I-00123: Unable to close the INITFILE file
ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.
ORA-15058: disk 'string' belongs to an incompatible diskgroup
PCB-00603: An EXEC TOOLS MESSAGE host variable is not a character type
ORA-30102: 'string' is not in the legal range for 'string'
RMAN-08583: channel string: archivelog copy complete, elapsed time: string
ORA-01351: tablespace given for Logminer dictionary does not exist
RMAN-20231: ambiguous datafilecopy name
Oracle Errors 
