ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement

Cause : Ane rrro eixst sint hem atreiailze dviwe dfeintiio.n A sa ersutl, hte amteiralziedv ie wsttaemnet ocul dno tbee xpalinde.

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

Chcek hte ysntxa o fth esttaemnet.I f ti i sa RCEAET MTAERAILIEZD IVEWs taetmetn, htena ls ochcek hte APRAEMTEsR sepciifedf ort hem atreiailze dviwe.

update : 24-08-2017

ORA-32342 - The EXPLAIN_MVIEW facility failed to explain the materialized view statement
ORA-32342 - The EXPLAIN_MVIEW facility failed to explain the materialized view statement

  • ora-29394 : session id string and serial# string do not exist
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-30934 : 'string' (string node) cannot be inserted in parent 'string' (string node)
  • ora-39062 : error creating master process string
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-25953 : join index cannot be a functional index
  • ora-02344 : cannot revoke execute on a type with table dependents
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-38451 : index is in an inconsistent state
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-19587 : error occurred reading string bytes at block number string
  • ora-27486 : insufficient privileges
  • ora-12664 : Services required by server not available on the client
  • ora-24901 : handles belonging to different environments passed into an OCI call
  • ora-16043 : managed recovery session canceled
  • ora-28523 : ORACLE and heterogeneous agent are incompatible versions
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-24366 : migratable user handle is set in service handle
  • ora-23330 : column group string already exists
  • ora-38312 : original name is used by an existing object
  • ora-09929 : GLB of two labels is invalid
  • ora-32051 : mapping service not available
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-31009 : Access denied for property string
  • ora-24416 : Invalid session Poolname was specified.
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-39955 : invalid PL/SQL warning message number
  • 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.