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 : 26-06-2017

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-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-12407 : unauthorized operation for policy string
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-13773 : insufficient privileges to select data from the cursor cache
  • ora-39070 : Unable to open the log file.
  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-26718 : transaction limit reached
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-01322 : No such table
  • ora-12560 : TNS:protocol adapter error
  • ora-32319 : Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
  • ora-38775 : cannot disable flash recovery area - flashback database is enabled
  • ora-24402 : error occured while creating connections in the pool
  • ora-01224 : group number in header string does not match GROUP string
  • ora-13146 : could not find table substitution variable string
  • ora-12319 : database (link name string) is already open
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-27464 : invalid schedule type string
  • ora-13909 : Invalid combination of threshold value and operator.
  • ora-12643 : Client received internal error from server
  • ora-39080 : failed to create queues "string" and "string" for Data Pump job
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-08463 : overflow converting decimal number to Oracle number
  • ora-13788 : invalid recommendation type
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • 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.