Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3783 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 |
DRG-50802: failed to bind input
DRG-51301: error releasing dml Queue lock
DRG-10850: CTXRULE indextype does not support the operator
ORA-26056: Can not unload from a view through the direct path.
PLS-00125: type name expected
ORA-12599: TNS:cryptographic checksum mismatch
ORA-23398: user name "string" at database link "string" does not match local user name "string"
LSX-00333: literal "~S" is not valid with respect to the pattern
LRM-00105: 'string' is not a legal Boolean for 'string'
PCC-00082: Length and scale specifications must be an integer
RMAN-08004: full resync complete
ORA-38460: filtering based on datatype "string" not supported for XML Tags
Oracle Errors 
