Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02180: no primary key constraint in the master table
- 1 Answers
- 3840 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-30101: unknown parameter name 'string'
ORA-02422: missing or invalid schema element
LCD-00211: unexpected delimiter [string]
PCC-02384: Missing array length specifier
ORA-01278: error creating file 'string'
RMAN-07502: List of Files Unknown to the Database
ORA-00068: invalid value string for parameter string, must be between string and string
ORA-07500: scglaa: $cantim unexpected return
ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
PLS-00413: identifier in CURRENT OF clause is not a cursor name
DRG-50301: server error reading request queue
PROC-00016: Cannot retrieve any more subkeys for the given keyhandle
Oracle Errors 
