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 : 21-08-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-19912 : cannot recover to target incarnation string
  • ora-02790 : File name is too long
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-19261 : XQ0041 - non empty URI in QName
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • ora-09912 : Malloc of name buffer(s) failed.
  • ora-09760 : osnpui: cannot send break message
  • ora-24812 : character set conversion to or from UCS2 failed
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-29551 : could not convert string to Unicode
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-30344 : number of child cols different from number of parent level cols
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-03251 : Cannot issue this command on SYSTEM tablespace
  • ora-22335 : The client cannot work with an altered type
  • ora-06711 : TLI Driver: error on bind
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-31465 : cannot obtain a lock on the subscription
  • ora-19668 : cannot do full restore of datafile string
  • ora-32812 : subscriber string does not exist
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-35018 : (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type.
  • ora-01497 : illegal option for ANALYZE CLUSTER
  • ora-01483 : invalid length for DATE or NUMBER bind variable
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-28540 : internal result set error
  • ora-28117 : integrity constraint violated - parent record not found
  • ora-26664 : cannot create STREAMS process string
  • ora-08275 : Environment variable unset
  • 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.