ORA-12022: materialized view log on "string"."string" already has rowid

Cause : Materialized view log on the indicated table already has ROWID information.

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

No action required.

update : 20-09-2017

ORA-12022 - materialized view log on "string"."string" already has rowid
ORA-12022 - materialized view log on "string"."string" already has rowid

  • ora-08316 : sllfsk: Error seeking in file.
  • ora-37075 : (XSMCSESS03) You cannot rename a session-only dimension value.
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-19667 : cannot do incremental restore of datafile string
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-09815 : File name buffer overflow
  • ora-02383 : illegal cost factor
  • ora-01764 : new update value of join is not guaranteed to be unique
  • ora-31424 : change table has active subscriptions
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-02150 : invalid new tablespace name
  • ora-12643 : Client received internal error from server
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-14011 : names assigned to resulting partitions must be distinct
  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-09799 : File label retrieval failed.
  • ora-03132 : two-task default value overflow
  • ora-00150 : duplicate transaction ID
  • ora-24431 : Statement does not exist in the cache
  • ora-06953 : Not enough virtual memory
  • ora-16214 : apply stalled for apply delay
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-29827 : keyword USING is missing
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-14081 : new partition name must differ from the old partition name
  • 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.