Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3762 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-11624: invalid attribute string for string: proper range string to string
ORA-30445: workload queries not found
PLS-00581: inheritance is not supported for opaque types
NNL-01042: Data streams answered by server: number
PCC-02019: Preprocessor warning at line number, column number, file string:
ORA-16707: The value of the property string is invalid. The valid values are string.
ORA-08431: raw data missing zero as defined in picture
DRG-11620: URL store: thread operation error
TNS-02515: Encryption/crypto-checksumming: unknown control type
ORA-22930: directory does not exist
ORA-07635: smsdbp: $SETPRT failure
ORA-12031: cannot use primary key columns from materialized view log on "string"."string"
Oracle Errors 
