ORA-23515: materialized views and/or their indices exist in the tablespace

Cause : An attempt was made to drop a tablespace which contains materialized views and/or their indices.

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

Drop the materialized views in this tablespace. Also, find indices belonging to materialized views in this tablespace and drop then. Then try dropping the tablespace.

update : 22-08-2017

ORA-23515 - materialized views and/or their indices exist in the tablespace
ORA-23515 - materialized views and/or their indices exist in the tablespace

  • ora-01309 : invalid session
  • ora-16079 : standby archival not enabled
  • ora-29904 : error in executing ODCIIndexClose() routine
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-15083 : failed to communicate with ASMB background process
  • ora-02775 : Invalid request done signal
  • ora-12072 : updatable materialized view log data for "string"."string" cannot be created
  • ora-16078 : media recovery disabled
  • ora-23332 : group string is in use; cannot drop
  • ora-31514 : change set string disabled due to capture error
  • ora-38432 : EVALUATE operator only allowed on an expression column
  • ora-37086 : %s is not a valueset
  • ora-06954 : Illegal file name
  • ora-29852 : keyword IS is missing
  • ora-07405 : sptrap: cannot setup alternate signal stack.
  • ora-16076 : unknown standby database destination
  • ora-10372 : parallel query server kill event proc
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-01924 : role 'string' not granted or does not exist
  • ora-31113 : XDB configuration may not be updated with non-schema compliant data
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-13800 : concurrent DDL failure on SQL repository objects
  • ora-16075 : standby database destination mismatch
  • ora-03212 : Temporary Segment cannot be created in locally-managed tablespace
  • ora-02474 : Fixed hash area extents used (string) exceeds maximum allowed (string)
  • ora-31099 : XDB Security Internal Error
  • ora-38778 : Restore point 'string' already exists.
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-31675 : worker process interrupt for unexpected death of master process
  • 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.