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 : 22-09-2017
ORA-23425

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

  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-31500 : change source string is not a ManualLog change source
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-06554 : package DBMS_STANDARD must be created before using PL/SQL
  • ora-02791 : Unable to open file for use with asynchronous I/O
  • ora-19717 : for non-OMF search the pattern must be specified
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-12490 : DBHIGH cannot be lowered
  • ora-03242 : Tablespace migration retried 500 times
  • ora-12003 : materialized view "string"."string" does not exist
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-25184 : column name expected
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-32810 : foreign queue string is not registered
  • ora-16550 : truncated result
  • ora-14138 : An unexpected error encountered during drop table operation
  • ora-13481 : the destination type is not supported
  • ora-12541 : TNS:no listener
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-00317 : file type string in header is not log file
  • ora-02794 : Client unable to get key for shared memory
  • ora-19999 : skip_row procedure was called
  • ora-14192 : cannot modify physical index attributes of a Hash index partition
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-19618 : cannot name files after restoreValidate has been called
  • ora-19575 : expected string blocks in file string, found string
  • ora-12198 : TNS:could not find path to destination
  • 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.