It's a bug, seen in 9.2.0.x (not sure exactly which point-version), I think I remember -- what version are you using (always useful to include in your original post)?
Scan MetaLink on keywords like "DBA_SEGMENTS DBA_EXTENTS BYTES". If I recall, it had something to do with having more than 100,000 segments or extents in a tablespace or datafile -- a very surprising and disturbing bug, but ultimately only of concern to monitoring tools. I believe that the SUM(BYTES) from DBA_EXTENTS was correct and that BYTES in DBA_SEGMENTS was incorrect. Classic "buried update" problem, perhaps?
genegurevich@xxxxxxxxxxxxxxxxxxxxx wrote:
I don't think this is the case: 1* select sum(bytes/1024)/1024 from dba_segments where segment_name like 'BIN%' and tablespace_name = 'CCS_X_017' SQL> / SUM(BYTES/1024)/1024 -------------------- There is no dropped objects in this tablespace. thank you Gene Gurevich Oracle MySQL Operations - OMO 224-405-4079"Allen, Brandon" <Brandon.Allen@On eNeck.com> To <genegurevich@xxxxxxxxxxxxxxxxxxxxx 05/09/2007 04:26 >, <oracle-l@xxxxxxxxxxxxx> PM cc Subject RE: dba_extents and dba_segmentsJust a guess - maybe the dba_segments view filters out dropped objects (i.e. those in the recycle bin), while dba_extents does not?
-- //www.freelists.org/webpage/oracle-l
