Re: Extents overlap
Vicente de Blas Bellido wrote:
> I have a problem that I don't know if is really dangerous or not.
> When I execute the oncheck -ce on an on-line instance I get this
> output
> :
>
> ERROR EXTENTS OVERLAP
> ERROR EXTENTS OVERLAP
>
> Is this a problem with the sysmaster database that doesn't have
> correct data, or it's a problem with the chuncks or the disks?
Vince,
it is a sign that partition headers for two different tables are both
claiming a piece of disk space. You should be able to use an SMI query
to eyeball which tables those might be.
select e1.dbsname, e1.tabname, e1.start, e1.size,
(e1.start + e1.size) e1_end,
e2.dbsname, e2.tabname, e2.start, e2.size,
(e2.start + e2.size) e2_end
from sysextents e1, sysextents e2
where (e2.start + e2.size) between e1.start and (e1.start + e1.size);
(Ugly, ain't it? But I'm not about to take the time to refine it.)
It is also possible that some extent of a table is listed in the same
disk space as an entry in the chunk free list somewhere. IN this case,
use the SMI table syschfree:
select chknum, extnum, f.start f_start, f.leng f_leng,
(f.start + leng) f_end,
dbsname, tabname, e.start e2_start, e.size,
(e.start + e.size) e_end
from syschfree f, sysextents e
where (e.start + e.size) between f.start and (f.start + leng)
or (f.start + leng) between e.start and (e.start + e.size)
order by 1, 2, 3, 4
Or some variation thereof...
--
-- Jake (In pursuit of undomesticated aquatic avians)
+----------------------------------------------------------+
|Aside from that, how did you enjoy the play, Mrs. Lincoln?|
+----------------------------------------------------------+