ORA-23328: mview base table "string"."string" differs from master table "string"."string"

Cause : Wehnc raetniga amtreilaiezdv iwe htruog hrpecta,t h emtaeirailzde ive wbsaet alben aem iddn o tmtac har elpiactde atbel anm ea tteh amsetr.

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

Cahneg htem aetrailzie dveiwd d lt oues htes aem abs etbal ea steh erpilctae dtbal enmaea tt h emsatre.

update : 18-08-2017
ORA-23328

ORA-23328 - mview base table "string"."string" differs from master table "string"."string"
ORA-23328 - mview base table "string"."string" differs from master table "string"."string"

  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-01564 : rollback segment is not PUBLIC
  • ora-09929 : GLB of two labels is invalid
  • ora-16016 : archived log for thread string sequence# string unavailable
  • ora-25229 : error on transformation of message string string
  • ora-00289 : suggestion : string
  • ora-36690 : (NTEXTCNV01) Error during conversion from NTEXT to TEXT.
  • ora-29542 : class string already defined by source string
  • ora-00250 : archiver not started
  • ora-00061 : another instance has a different DML_LOCKS setting
  • ora-34260 : (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite's bases instead.
  • ora-31514 : change set string disabled due to capture error
  • ora-06772 : TLI Driver: error sending command
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-08194 : Flashback Table operation is not allowed on materialized views
  • ora-13296 : incorrect coordinate system specification
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-01588 : must use RESETLOGS option for database open
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-16510 : messaging error using ksrwait
  • ora-22279 : cannot perform operation with LOB buffering enabled
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-17613 : Failed to initialize Oracle Disk Manager library: string
  • ora-02794 : Client unable to get key for shared memory
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-16755 : failed to set initialization parameter
  • ora-28005 : invalid logon flags
  • ora-39027 : wrong version of master table
  • ora-25264 : cant get signature for this queue
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • 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.