ORA-23401: materialized view "string"."string" does not exist

Cause : A materialized view name was given to dbms_mview.refresh that is not in sys.snap$ or its associated views.

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

Provide a materialized view name that is in sys.snap$, all_mviews or user_mviews.

update : 29-06-2017
ORA-23401

ORA-23401 - materialized view "string"."string" does not exist
ORA-23401 - materialized view "string"."string" does not exist

  • ora-06523 : Maximum number of arguments exceeded
  • ora-23375 : feature is incompatible with database version at string
  • ora-27128 : unable to determine pagesize
  • ora-40215 : model string is incompatible with current operation
  • ora-13346 : the coordinates defining an arc are collinear
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-31157 : Invalid Content-Type charset
  • ora-27303 : additional information: string
  • ora-01110 : data file string: 'string'
  • ora-00078 : cannot dump variables by name
  • ora-13119 : invalid edge_id [string]
  • ora-15154 : cluster rolling upgrade incomplete
  • ora-19713 : invalid copy number: string
  • ora-26673 : duplicate column name string
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-02368 : file string is not valid for this load operation
  • ora-19999 : skip_row procedure was called
  • ora-24331 : user buffer too small
  • ora-27027 : sbtremove2 returned error
  • ora-09312 : slspool: error spooling file to printer
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-15062 : ASM disk is globally closed
  • ora-13705 : There was a instance shutdown/startup between the snapshots in the range [string, string].
  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-19116 : too many xmlspace declarations
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • 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.