Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

ORA-29857: domain indexes and/or secondary objects exist in the tablespace  tips

Oracle Error Tips by Burleson Consulting

 

Oracle docs note this about ORA-29857:

ORA-29857: domain indexes and/or secondary objects exist in the tablespace
Cause: An attempt was made to drop a tablespace which contains secondary objects and/or domain indexes.
Action: Drop the domain indexes in his tablespace. Also, find the domain indexes which created secondary objects in this tablespace and drop them. Then try dropping the tablespace.

 

Many times, users become confronted with error ORA-29857 when trying to identify tablespaces.  For example, 

 

Question:

I want to detach, or delete,  a tablespace and datafile and got the error ORA-29857.  I  do not have a backup of my datafile, and am not in archive log mode.  I am trying to drop the tablespace with the objects owned by the files, but keep encountering ORA-29857. 

 

Answer:  To identify the indexes of the domain, try executing,

select index_name, table_owner, table_name, tablespace_name from user_indexes where index_type='DOMAIN';

The tablespace may not be specified, but you could at least see the potential indexes.  Remember that you should be connected with an index user status to run the above query.  If this is not possible, try ALL_INDEXES in place of USER_INDEXES,

select owner, index_name, table_owner, table_name, tablespace_name from all_indexes where index_type='DOMAIN';

As a last note, you should check and be sure that all indexes have clearly cut names, and monitor which tablespaces are created on which indexes.

  • NOTE: In domain indexes, data can be stored in default databases, which is set at the time of the index creation by the user that created the index, and this can be confusing when trying to identify the indexes in a domain in hopes of resolving ORA-29857


You may also want to check out this information page about Oracle domain indexes:

http://www.dba-oracle.com/t_ault_89_indextype_udt_opstatus.htm


 

 

  
 

 
 
 
 
 

 
 
 
 
 
 
Oracle training Excel
 
Oracle performance tuning software 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright ? 1996 -  2014

All rights reserved by Burleson

Oracle ? is the registered trademark of Oracle Corporation.


Hit Counter