ORA-32344: cannot create a secondary materialized view with synonym as base table

Cause : It is not supported to create a secondary materialized view with synonym in the FROM clause.

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

Removed the synonym(s) from the statement.

update : 24-08-2017
ORA-32344

ORA-32344 - cannot create a secondary materialized view with synonym as base table
ORA-32344 - cannot create a secondary materialized view with synonym as base table

  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-24414 : Only number sessions could be started.
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-13125 : partition key is already set
  • ora-38468 : column "string" is not identified as a column storing expressions.
  • ora-31642 : the following SQL statement fails: string
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-13441 : GeoRaster metadata SRS error
  • ora-01232 : cannot start online backup - file string is being made read-only
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-19756 : corrupt block number string found in change tracking file
  • ora-30970 : option not supported for XML Index
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-31458 : an internal error occurred
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-06793 : TLI Driver: server cannot create new process
  • ora-16130 : supplemental log information is missing from log stream
  • ora-13500 : SYSAUX DATAFILE clause specified more than once
  • ora-19020 : invalid dereference of XMLType columns
  • ora-07824 : sspain: $SETIMR failure
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-23409 : could not find an unused refresh group number
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-07248 : sfwfb: write error, unable to write database block.
  • ora-06925 : CMX: disconnect during connect request
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-30444 : rewrite terminated by the sql analyzer
  • 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.