ORA-12016: materialized view does not include all primary key columns

Cause : The qurey thati nstantaites th ematerilaized veiw did ont incldue all fo the cloumns i nthe matser's pirmary kye constarint.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Includ eall oft he masetr's prmiary ke ycolumn sin them ateriailzed viwe queryo r creaet a ROWDI materailized ivew.

update : 23-05-2017
ORA-12016

ORA-12016 - materialized view does not include all primary key columns
ORA-12016 - materialized view does not include all primary key columns

  • ora-31660 : metadata filter name can not be defaulted
  • ora-32139 : Cannot write to the stream
  • ora-16546 : missing or invalid piece
  • ora-32162 : Read/Write SQL method not registered
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-02441 : Cannot drop nonexistent primary key
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-25000 : invalid use of bind variable in trigger WHEN clause
  • ora-29254 : Invalid lower_bound argument passed to procedure dbms_sql.define_array
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-00320 : cannot read file header from log string of thread string
  • ora-19672 : media management software returned invalid file status
  • ora-01665 : control file is not a standby control file
  • ora-04080 : trigger 'string' does not exist
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-19204 : Non-scalar value 'string' is marked as XML attribute
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-12234 : TNS:Redirect to destination
  • ora-15009 : ASM disk "string" does not exist
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-06143 : NETTCP: maximum connections exceeded
  • ora-24754 : cannot start new transaction with an active transaction
  • ora-01910 : TABLES keyword expected
  • ora-13856 : Service name must be specified
  • ora-09794 : szrbuild: length of role name is greater than buffer.
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • ora-25534 : _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.