ORA-12024: materialized view log on "string"."string" does not have primary key columns

Cause : Mtaeirailzde ive wlgo no htei nidctae dtbal edeosn o thvaep rmiayr ekyi noframtoin.

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

Add rpiamr ykyest ot h emtaeirailzde ive wlgo suign hteA LETRM AETRAILZIE DVEIWc ommadn.

update : 25-04-2017
ORA-12024

ORA-12024 - materialized view log on "string"."string" does not have primary key columns
ORA-12024 - materialized view log on "string"."string" does not have primary key columns

  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-16570 : operation requires restart of database "string"
  • ora-25292 : Buffer operations are not supported on the queue
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • ora-22604 : TDS handle already generated
  • ora-23606 : invalid object string
  • ora-24152 : cannot drop evaluation context string.string with dependents
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-02773 : Invalid maximum client wait time
  • ora-32811 : subscriber string already exists
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-01743 : only pure functions can be indexed
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-10640 : Operation not permitted during SYSTEM tablespace migration
  • ora-23356 : masterdef recognizes a master which does not recognize the masterdef
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-00315 : log string of thread string, wrong thread # string in header
  • ora-19371 : invalid update option
  • ora-31075 : invalid string declaration in XML Schema
  • ora-13417 : null or invalid layerNumber parameter
  • ora-14010 : this physical attribute may not be specified for an index partition
  • ora-22344 : can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
  • ora-40217 : priors table mismatched with training data
  • ora-06037 : NETDNT: connect failed, node unreachable
  • ora-24090 : at least one protocol must be enabled
  • ora-06029 : NETASY: port assignment failure
  • 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.