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 : 25-04-2017

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

  • ora-13199 : %s
  • ora-22982 : cannot create sub-view under this view
  • ora-02142 : missing or invalid ALTER TABLESPACE option
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-00347 : log string of thread string, expected block size string doesn't match string
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-07202 : sltln: invalid parameter to sltln.
  • ora-13026 : unknown element type for element string.string.string
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-01415 : too many distinct aggregate functions
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-29290 : invalid offset specified for seek
  • ora-22306 : type "string"."string" already exists
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-19952 : database should be mounted exclusively
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-12046 : cannot use trusted constraints for refreshing remote MV
  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-27504 : IPC error creating OSD context
  • ora-00400 : invalid release value string for parameter string
  • ora-06306 : IPA: Message write length error
  • ora-19692 : missing creation stamp on piece string
  • ora-16505 : site ID is invalid
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-36994 : (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
  • ora-01338 : Other process is attached to LogMiner session
  • 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.