ORA-23314: database is not a materialized view site for "string"."string"

Cause : The invocation database is not a materialized view database for the given object group.

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

Connect to the desired materialized view database and retry the request, or make the invocation database a materialized view site with create_mview_repschema or create_mview_repgroup.

update : 25-06-2017

ORA-23314 - database is not a materialized view site for "string"."string"
ORA-23314 - database is not a materialized view site for "string"."string"

  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-23393 : the user is already the propagator
  • ora-39157 : error appending extension to file "string"
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-26054 : Direct Path Context prepared for a different mode than operation requested.
  • ora-16164 : LGWR network server host detach error
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-13481 : the destination type is not supported
  • ora-16100 : not a valid Logical Standby database
  • ora-09951 : Unable to create file
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-06568 : obsolete ICD procedure called
  • ora-32630 : multiple assignment in automatic order MODEL
  • ora-28595 : Extproc agent : Invalid DLL Path
  • ora-28150 : proxy not authorized to connect as client
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-27103 : internal error
  • ora-02424 : potential circular view references or unknown referenced tables
  • ora-30204 : buffer is not large enougth
  • ora-06308 : IPA: No more connections available
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-32631 : illegal use of objects in MODEL
  • ora-32639 : Aggregate functions on reference MODELs are not allowed
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-22993 : specified input amount is greater than actual source amount
  • ora-07202 : sltln: invalid parameter to sltln.
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • 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.