ORA-26530: unable to build materialized view refresh control list

Cause : The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.

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

Verify that the named materialized view(s) are properly defined and valid.

update : 23-05-2017
ORA-26530

ORA-26530 - unable to build materialized view refresh control list
ORA-26530 - unable to build materialized view refresh control list

  • ora-06574 : Function string references package state, cannot execute remotely
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-12803 : parallel query server lost contact with another server
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-02833 : Server was unable to close file
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-07243 : supplied buffer not big enough to hold entire line
  • ora-02771 : Illegal request time out value
  • ora-16703 : cannot set property while the database is enabled
  • ora-13409 : null or invalid pyramidLevel parameter
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-38441 : System could not derive the list of STORED and INDEXED attributes.
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-16556 : error message is in XML already
  • ora-09313 : slsprom: error prompting user
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-17613 : Failed to initialize Oracle Disk Manager library: string
  • ora-13464 : error loading GeoRaster data: string
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-36635 : (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.
  • ora-39204 : No subsetting of tablespaces is allowed for transportable import.
  • ora-26519 : no memory available to allocate
  • ora-39141 : dump file "string" is a duplicate of dump file "string"
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • 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.