ORA-12002: there is no materialized view log on table "string"."string"

Cause : There was no materialized view log on the master table.

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

Create a materialized view log on the master table.

update : 23-08-2017
ORA-12002

ORA-12002 - there is no materialized view log on table "string"."string"
ORA-12002 - there is no materialized view log on table "string"."string"

  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-00447 : fatal error in background process
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-31533 : only one change set (string) is allowed in change source
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-17502 : ksfdcre:string Failed to create file string
  • ora-14100 : partition extended table name cannot refer to a remote object
  • ora-27210 : syntax error in device PARMS
  • ora-32639 : Aggregate functions on reference MODELs are not allowed
  • ora-30971 : illegal operation on the Path Table
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-30108 : invalid positional parameter value 'string'
  • ora-13342 : an arc geometry has fewer than three coordinates
  • ora-29301 : wrong DBMS_PITR package function/procedure order
  • ora-32635 : not a single cell reference predicate
  • ora-00828 : specified value of shared_pool_reserved_size inconsistent with internal settings
  • ora-12591 : TNS:event signal failure
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-25177 : UNRECOVERABLE option not permitted
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-06773 : TLI Driver: error reading command
  • ora-36646 : (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • 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.