RE: Toad 11 possible Bug

i am using this query to find them 

 SELECT  index_name
  FROM user_ind_columns
 WHERE index_name NOT LIKE 'BIN$%' 
MINUS
SELECT  index_name 
  FROM user_indexes;  


Saurabh
To: [email protected]
From: [email protected]
Date: Tue, 4 Oct 2011 20:36:33 +0000
Subject: RE: [toad] Toad 11 possible Bug


















 



  


    
      
      
      



Oops, there is a difference.  With an invisible index, the index is really there, but invisible, and with a virtual index, it’s not really there.
 
 
 
 


From: [email protected] [mailto:[email protected]]
On Behalf Of John Dorlon

Sent: Tuesday, October 04, 2011 3:34 PM

To: [email protected]

Subject: RE: [toad] Toad 11 possible Bug


 
  




You’re right.  We are expecting them to be listed in user/all/dba_indexes, but we aren’t finding them because they are not there.
 
They are present in sys.ind$, but the fact that there is no segment makes them missing from sys.seg$, which is why we don’t see them
 in user/all/dba_indexes.   I’m not sure if Oracle would consider this a bug or not.
 
I suppose I can work around it by querying user/all/dba_objects where object_type = ‘INDEX’, but that’s going to cause problems for
 other users because sometimes depending on privileges, an index will be in ALL_INDEXES but not ALL_OBJECTS. 

 
As a workaround, if you have Oracle 11g, you can use an invisible index instead.  As far as I can tell, the concept in Oracle is the
 same, and these do show up in Toad.
 
 
 


From: [email protected] [mailto:[email protected]]
On Behalf Of pathak saurabh

Sent: Tuesday, October 04, 2011 2:23 PM

To: [email protected]

Subject: [toad] Toad 11 possible Bug


 
 







Describe window is not able to identify the virtual indexes on a table. 



eg. 



create index <> on t_name.col_name NOSEGMENT. 



and then describe the table and verify the index  tab. The recently created index is not listed there.




Saurabh