ORA-12028: materialized view type is not supported by master site string

Cause : Pre-Orcale8 matser sitse are nto able ot suppotr primayr key o rsubqueyr materailized ivews thta are albe to preform af ast rerfesh.

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

Createa ROWIDm ateriailzed viwe or us ea mastre tablef rom anO racle8s ite.

update : 29-06-2017

ORA-12028 - materialized view type is not supported by master site string
ORA-12028 - materialized view type is not supported by master site string

  • ora-07510 : scgbrm: $getlki unexpected return on lockid string
  • ora-23487 : object groups "string"."string" and "string"."string" do not have the same connection qualifier
  • ora-19955 : only one open thread is allowed to change the DBID
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-38762 : thread string redo log with scn string could not be found
  • ora-12730 : invalid equivalence class in regular expression
  • ora-13052 : unsupported geometric type for geometry string.string
  • ora-22611 : TDS version is not recognized
  • ora-25223 : user_data type used is not supported
  • ora-26099 : direct path context is already prepared
  • ora-31154 : invalid XML document
  • ora-19513 : failed to identify sequential file
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-01192 : must have at least one enabled thread
  • ora-29286 : internal error
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-06260 : NETNTT: cannot write to remote process
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-01059 : parse expected before a bind or execute
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-30114 : error when processing from command line
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-06927 : CMX: T_DATAIN received before all data written
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-30134 : reserved for future use
  • ora-25123 : Too many components specified in the name.
  • ora-16734 : error executing dbms_logstdby.skip_error procedure
  • ora-29512 : incorrectly formed name resolver specification
  • ora-02727 : osnpop: access error on orapop executable
  • 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.