ORA-23400: invalid materialized view name "string"

Cause : A null, misspelled, or badly formed materialized view name was given to dbms_mview.refresh.

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

Provide a valid materialized view name to dbms_mview.refresh.

update : 29-04-2017

ORA-23400 - invalid materialized view name "string"
ORA-23400 - invalid materialized view name "string"

  • ora-35756 : (VCTODT02) 'number' is not a valid date because number is out of range for a year.
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-16219 : This database is not preparing to switch over.
  • ora-09282 : sllfrb: error reading records
  • ora-24351 : invalid date passed into OCI call
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-31110 : Action failed as resource string is locked by name
  • ora-23433 : executing against wrong master site string
  • ora-27463 : invalid program type string
  • ora-08271 : sksabln: Buffer size not large enough for archive control string
  • ora-00398 : abort thread recovery due to reconfiguration
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-31220 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location.
  • ora-26058 : unexpected error fetching metadata for column string in table string
  • ora-31164 : cannot load object-relational XML attribute using direct path
  • ora-08199 : Flashback Table operation is not supported on this object
  • ora-16156 : LGWR archive log dependency not allowed if database is standby protected
  • ora-13017 : unrecognized line partition shape
  • ora-22856 : cannot add columns to object tables
  • ora-36618 : (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD.
  • ora-28040 : No matching authentication protocol
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-31216 : DBMS_LDAP: PL/SQL - Invalid LDAP rdn.
  • ora-01205 : not a data file - type number in header is string
  • ora-07477 : scgcmn: lock manager not initialized.
  • ora-36154 : (XSMXAGGR01) workspace object is not a data variable.
  • ora-12829 : Deadlock - itls occupied by siblings at block string of file 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.