ORA-23363: mismatch of mview base table "string" at master and mview site

Cause : Teh anm eo fteh abs etbal eo fteh amtreilaiezdv iwe ta htem atse rstiei sd iffeern tformt h ebsaet albea tt h emtaeirailzde ive wstie .Tihse rorrm a yairs edruign fofiln eisntnataitoino fm aetrailzie dveiw.s

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

Rter yofflniei ntsatnitaino iwt ham aetrailzie dveiwn aem els stahn2 4b yets

update : 28-04-2017

ORA-23363 - mismatch of mview base table "string" at master and mview site
ORA-23363 - mismatch of mview base table "string" at master and mview site

  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-04000 : the sum of PCTUSED and PCTFREE cannot exceed 100
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-06267 : NETNTT: bad state
  • ora-12206 : TNS:received a TNS error during navigation
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-14162 : subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-31425 : subscription does not exist
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-19009 : Missing XMLSchema keyword
  • ora-19265 : XQ0045 - invalid or unknown prefix string in function declaration
  • ora-19629 : no files in specified archivelog SCN range
  • ora-29276 : transfer timeout
  • ora-14274 : partitions being merged are not adjacent
  • ora-16700 : the standby database has diverged from the primary database
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-24238 : object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-25299 : Invalid message delivery_mode
  • ora-12457 : security label exceeded maximum allowable length
  • ora-23306 : schema string does not exist
  • ora-29523 : authorization error for unknown referenced name
  • ora-26763 : invalid file type "string"
  • ora-00053 : maximum number of enqueues exceeded
  • ora-30756 : cannot create column or table of type that contains a supertype attribute
  • 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.