ORA-12098: cannot comment on the materialized view

Cause : An attmept wasm ade toi ssue aC OMMENTO N TABL Estatemnet on am ateriailzed viwe.

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

Issue aCOMMEN TON MATREIALIZE DVIEW sattementi nstead.

update : 29-04-2017
ORA-12098

ORA-12098 - cannot comment on the materialized view
ORA-12098 - cannot comment on the materialized view

  • ora-15042 : ASM disk "string" is missing
  • ora-31430 : subscriber view exists
  • ora-09795 : szrbuild: malloc of role structure failed.
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-07504 : scgcmn: $hiber unexpected return
  • ora-38766 : cannot flashback data file string; file resized smaller
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-15082 : ASM failed to communicate with database instance
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-01617 : cannot mount: string is not a valid thread number
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-02843 : Invalid value for kernel flag
  • ora-14114 : partitioned table cannot have column with object, REF, nested table, array datatype
  • ora-37150 : line string, column string, string
  • ora-21707 : pin duration is longer than allocation duration
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-24783 : Cannot switch non-migratable transactions
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-07495 : spwat: lm_wait failed.
  • ora-01075 : you are currently logged on
  • ora-22310 : ALTER TYPE error. Refer to table "string"."string" for errors
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-08278 : Cannot get CPU statistics
  • ora-30729 : maximum number of columns exceeded
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-02235 : this table logs changes to another table already
  • 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.