ORA-23360: only one materialized view for master table "string" can be created

Cause : Tyrign ot rcetaem oer hta noen amtreilaiezdv iwe no agvie nmsatre atbel ni htes aem erpg ruop.

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

Ceraet htees tohre amtreilaiezdv iwesi na idfefrnetr e pgoru pa taontehrs iet.

update : 27-04-2017

ORA-23360 - only one materialized view for master table "string" can be created
ORA-23360 - only one materialized view for master table "string" can be created

  • ora-30192 : reserved for future use
  • ora-16512 : parameter exceeded maximum size limit
  • ora-06532 : Subscript outside of limit
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-29805 : missing COLUMN keyword
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-38756 : Flashback is already turned off for this tablespace.
  • ora-16240 : Waiting for logfile (thread# string, sequence# string)
  • ora-29813 : non-supported object type with associate statement
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-38714 : Instance recovery required.
  • ora-28004 : invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-28593 : agent control utility: command terminated with error
  • ora-00395 : online logs for the clone database must be renamed
  • ora-19665 : size string in file header does not match actual file size of string
  • ora-32120 : Buffer size is less than amount specified
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-13499 : %s
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-10372 : parallel query server kill event proc
  • ora-09764 : osnmop: access error on oracle executable
  • ora-02221 : invalid MAXEXTENTS storage option value
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-27023 : skgfqsbi: media manager protocol error
  • 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.