ORA-32345: fail to refresh the materialized view string.string due to the changed synonym

Cause : The definition of one or more synonyms in the from clause have changed. The structure of the materialized view has become invalid.

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

Restore the synonym(s) or drop the materialized view and recreate it again.

update : 27-05-2017
ORA-32345

ORA-32345 - fail to refresh the materialized view string.string due to the changed synonym
ORA-32345 - fail to refresh the materialized view string.string due to the changed synonym

  • ora-22303 : type "string"."string" not found
  • ora-19725 : can not acquire plug-in enqueue
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-04016 : sequence string no longer exists
  • ora-19912 : cannot recover to target incarnation string
  • ora-00264 : no recovery required
  • ora-01028 : internal two task error
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-27017 : skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-10568 : Failed to allocate recovery state object: out of SGA memory
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-29962 : fatal error occurred in the execution of ODCIINDEXALTER routine
  • ora-23394 : duplicate propagator
  • ora-29291 : file remove operation failed
  • ora-25248 : duplicate agent specified in the agent list
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-39005 : inconsistent arguments
  • ora-07449 : sc: usnewlock failed.
  • ora-02801 : Operations timed out
  • ora-37150 : line string, column string, string
  • ora-26731 : %s 'string' does not exist
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-17611 : ksfd: file 'string' cannot be accessed, global open closed
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-30688 : maximum program calling depth exceeded
  • ora-01516 : nonexistent log file, datafile, or tempfile "string"
  • ora-29800 : invalid name for operator
  • 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.