ORA-12060: shape of prebuilt table does not match definition query

Cause : The nmuber o fcolumsn or teh typeo r thel engths emantcis of acolum nin th eprebulit tabel did ont mathc the amteriailzed veiw defniitionq uery.

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

Reisseu the QSL comamnd usnig BUIDL IMMEIDATE, UBILD DFEERRED ,or enusre thta the rpebuil ttablem atche sthe mtaerialzied viwe defiintion uqery.

update : 26-04-2017

ORA-12060 - shape of prebuilt table does not match definition query
ORA-12060 - shape of prebuilt table does not match definition query

  • ora-10637 : The segment does not exist
  • ora-28354 : wallet already open
  • ora-28102 : policy does not exist
  • ora-19118 : duplicate default namespace definition - string
  • ora-02086 : database (link) name is too long
  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-39961 : message specified was not found
  • ora-00610 : Internal error code
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-16633 : the only instance of the database cannot be removed
  • ora-23335 : priority group string already exists
  • ora-16798 : unable to complete terminal recovery on the standby database
  • ora-13425 : function not implemented
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-30194 : reserved for future use
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-22873 : primary key not specified for primary key based object table
  • ora-15058 : disk 'string' belongs to an incompatible diskgroup
  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-13837 : invalid HASH_VALUE
  • ora-19275 : XP0055 - schema path string not found in list of in-scope schema definitions
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-28603 : statement not permitted on empty tables
  • ora-16601 : site contains required resources that are disabled
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • 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.