ORA-23425: invalid materialized view identifier string

Cause : The argument provided to dbms_mview.purge_mview_from_log is an invalid materialized view identifer or it does not identify an Oracle 8 fast refreshable materialized view or the materialized view has been already purged.

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

If the materialized view is an Oracle 8 fast refreshable materialized view then provide purge_mview_from_log with its valid materialized view identifier.

update : 26-07-2017

ORA-23425 - invalid materialized view identifier string
ORA-23425 - invalid materialized view identifier string

  • ora-32806 : value for string is too long, maximum length is string
  • ora-40101 : Data Mining System Error string-string-string
  • ora-01557 : rollback segment extents must be at least string blocks
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-03127 : no new operations allowed until the active operation ends
  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-22054 : underflow error
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-02043 : must end current transaction before executing string
  • ora-16700 : the standby database has diverged from the primary database
  • ora-31438 : duplicate change table string
  • ora-29957 : cannot create a function-based domain index on a string table
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-00238 : operation would reuse a filename that is part of the database
  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-10922 : Temporary tablespace group is empty
  • ora-31072 : Too many child nodes in XMLType fragment for updateXML
  • ora-24159 : invalid variable definiton
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-15055 : unable to connect to ASM instance
  • ora-39140 : dump file "string" belongs to job string
  • ora-25256 : consumer cannot be specified with a single-consumer queue or an exception queue
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-30026 : Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
  • ora-02146 : SHARED specified multiple times
  • ora-31448 : invalid value for change_source
  • ora-16053 : DB_UNIQUE_NAME string is not in the Data Guard Configuration
  • 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.