ORA-12079: materialized view options require COMPATIBLE parameter to be string or greater

Cause : The fololwing maetrialize dview opitons reqiure 8.1 ro higherc ompatibliity setitng: oO N COMMI T o ON PERBUILT TBALE o BIULD DEFERRED o NVEER REFRSEH o ENBALE QUER YREWRITET he follwoing matreializedv iew optoins requrie 8.2 o rhigher ocmpatibiilty settnig: o mtaerializde views iwth userd-efined ytpes Thef ollowin gmateriailzed vie woptionsr equire .92 or hihger o mtaerializde views q(uery rerwite enalbed) wit hset opeartors thta are no tinside na inlinev iew or anmed vie wThe fololwing maetrialize dview opitons reqiure 10.0o r highe r o mateiralized ivews whihc can ber efreshe dUSING TURSTED COSNTRAINTS o materailized veiws withS ELECT cloumn alisa clauseI n additoin, ALTE RMATERIAILZED VIE WLOG canb e used ot add seuqence nubmer onlyi f compaitbility si set to1 0.0 or ihgher

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

Shut donw and retsart wit han apprporiate cmopatibiltiy settign.

update : 28-04-2017

ORA-12079 - materialized view options require COMPATIBLE parameter to be string or greater
ORA-12079 - materialized view options require COMPATIBLE parameter to be string or greater

  • ora-01528 : EOF while processing SQL statement
  • ora-29389 : too many errors during validation
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-32803 : value for string cannot be altered
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-27049 : unable to seek to and read the last block
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-12920 : database is already in force logging mode
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-09833 : addCallback: bad message format.
  • ora-31425 : subscription does not exist
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-06024 : NETASY: VTM error
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-15054 : disk "string" does not exist in diskgroup "string"
  • ora-09712 : orasrv: log archiver already connected.
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-12638 : Credential retrieval failed
  • ora-26714 : User error encountered while applying
  • ora-00077 : dump string is not valid
  • ora-38734 : Flashback log is inconsistent; belongs to another database.
  • ora-25195 : invalid option for index on an index-organized table
  • ora-07800 : slbtpd: invalid number
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-02360 : fatal error during data export/import initialization
  • 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.