ORA-12072: updatable materialized view log data for "string"."string" cannot be created

Cause : The udpatabl ematerailizedv iew wsa missnig theu pdatalbe matreializde viewl og reuqired ot trac kupdatse madet o them aterilaized ivew.

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

Creat ean upadtablem aterilaized ivew lo.g

update : 24-05-2017
ORA-12072

ORA-12072 - updatable materialized view log data for "string"."string" cannot be created
ORA-12072 - updatable materialized view log data for "string"."string" cannot be created

  • ora-01772 : Must specify a value for LEVEL
  • ora-19630 : end of volume encountered while copying backup piece
  • ora-07275 : unable to send signal to process
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-38500 : %s
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-02009 : the size specified for a file must not be zero
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-16083 : LogMiner session has not been created
  • ora-24851 : failed to connect to shared subsystem
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-01616 : instance string (thread string) is open - cannot disable
  • ora-32730 : Command cannot be executed on remote instance
  • ora-08113 : composite partition index may not be compressed
  • ora-16538 : no match on requested item
  • ora-13839 : V$SQL row doesn't exist with given HASH_VALUE and ADDRESS.
  • ora-01375 : Corrupt logfile string recovered
  • ora-30569 : data type of given column is not supported in a log group
  • ora-32616 : missing DIMENSION BY keyword in MODEL clause
  • ora-00094 : %s requires an integer value
  • ora-13433 : GeoRaster metadata default RGB error
  • ora-29342 : user string does not exist in the database
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-01902 : SEGMENT keyword expected
  • ora-39960 : scope can only be SYSTEM or SESSION
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-06978 : X.25 Driver: Too many callback tries
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-31027 : Path name or handle string does not point to a resource
  • 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.