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 : 27-05-2017
ORA-23425

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

  • ora-16705 : internal error in resource guard
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-25175 : no PRIMARY KEY constraint found
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-06108 : NETTCP: connect to host failed
  • ora-09755 : osngpn: port allocation failure.
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-00023 : session references process private memory; cannot detach session
  • ora-32815 : message system link string is referenced by a foreign queue
  • ora-12726 : unmatched bracket in regular expression
  • ora-31659 : status message was invalid type - detaching job
  • ora-19713 : invalid copy number: string
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-04932 : increment or adjust of sequence number failed
  • ora-01904 : DATAFILE keyword expected
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-27154 : post/wait create failed
  • ora-24756 : transaction does not exist
  • ora-30360 : REF not supported with query rewrite
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-15173 : entry 'string' does not exist in directory 'string'
  • ora-19513 : failed to identify sequential file
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-08447 : syntax error in USAGE clause in mask options
  • 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.