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 : 28-04-2017
ORA-23314

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-16812 : log apply service not running on apply instance recorded by the broker
  • ora-12591 : TNS:event signal failure
  • ora-01235 : END BACKUP failed for string file(s) and succeeded for string
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-40253 : no target counter examples were found
  • ora-00250 : archiver not started
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-06958 : Failed to access configuration file
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-19727 : cannot plug data [string] at level string into database running Oracle string
  • ora-22995 : TABLESPACE DEFAULT option is invalid in this context
  • ora-06132 : NETTCP: access denied, wrong password
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-29915 : cannot select FOR UPDATE from collection operand
  • ora-29849 : error occurred in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-21611 : key length [string] is invalid
  • ora-22057 : bad integer length [string]
  • ora-32808 : message system link string does not exist
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-31688 : Worker process string failed during startup.
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-13004 : the specified buffer size is invalid
  • ora-02167 : LOGFILE clause specified more than once
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • ora-31624 : A job cannot be modified after it has started.
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-30483 : window functions are not allowed here
  • 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.