Operand value exceeds system limits in sdo_aggr_mbr

Question

Hi-- i'm trying to get the MBR of a fairly large geometry (1429 vertices) and run into a strange problem:
when i:
select sdo_aggr_mbr(shape)
from FEEDER_LINES_SDO
where subname = 'OCEANO';
i get what i expect:
SDO_GEOMETRY(2003, 82212, NULL, SDO_ELEM_INFO_ARRAY(1,1003, 3),SDO_ORDINATE_ARRAY(712103.736,3876977.34, 733591.744, 3896557.18))
however when i try to get the subname in my query as well:
select subname ,sdo_aggr_mbr(shape)
from FEEDER_LINES_SDO
where subname = 'OCEANO'
group by subname;
i get
ERROR at line 1:
ORA-22813: operand value exceeds system limits
The query fails with "ORA-00937: not a single-group group function" when i leave out the group by clause
i can get around it with a kludge, but would like to know why the group by fails
the kludge:
select subname,min(t.x) minx, min(t.y) miny, max(t.x) maxx, max(t.y) maxy from
FEEDER_LINES_SDO c,
TABLE(SDO_UTIL.GETVERTICES(c.shape)) t
where subname = 'OCEANO'
group by subname;
SUBNAME MINX MINY MAXX MAXY
OCEANO     712103.736 3876977.34 733591.744 3896557.18
where minx(), miny() etc are variations on:
function minx (geom_in mdsys.sdo_geometry)
return number DETERMINISTIC IS
begin
return sdo_geom.sdo_min_mbr_ordinate(geom_in,1);
end;
the group by expression seems to work fine on geometries with less than 1200 vertices. Is there a system parameter i can change?
elvis{44}% oerr ora 22813
22813, 00000, "operand value exceeds system limits"
// *Cause:  Object or Collection value was too large. The size of the value
// might have exceeded 30k in a SORT context, or the size might be
// too big for available memory.
// *Action:  Choose another value and retry the operation.
i am running oracle 9.2.0.1 on solaris8
any insight on this will be greatly appreciated
cheers
--kassim

Answer 1

Hi Kassim,
At KMS I recently ran into the same ORA-22813, when running this cursor SQL
     CURSOR lcur_montage IS
     select m.mont_id, m.sys_PK, m.krtp_id, m.mont_geom, m.til_dato_id , m.forloeb      
     from MTK_montage m
     where m.fra_dato_id = in_dato_id
     and m.krtp_id = 1           
     order by m.mont_id;
Omitting the order by clause makes it work fine. If I alternatively omit the SDO_geometry m.mont_geom as a select item, the query also works.
Our problem seems to arise when trying to sort selected rows, which contain large objects such as SDO_geometry.
Yesterday we played around with SORT_AREA_SIZE, but to no avail. It turns out to be a known bug.
When I today search for ORA-22813 in MetaLink, the first list item is
1.
9.2.0.X Patch Sets - List of Bug Fixes by Problem Type
Type: Note
Doc ID: 217194.1
Score: 63%
Modified Date: 18-FEB-2003
Status: PUBLISHED
Platform: Generic issue
Product: Oracle Server - Enterprise Edition
which unfortunately will not open and reveal its content.
On the other hand trying MetaLink -> Bugs -> search for 'ORA-22813' gives amongst others Bug 2656107, which looks a lot like my problem.
For Oracle eyes: - when will this bug be fixed? Does it solve the problem at hand?
- regards
Jens Ole Jensen
Kort & MatrikelStyrelsen (WWW: http://www.kms.dk)
Danmark  
version: (32 bit) Oracle9i Enterprise Edition Release 9.2.0.2.0 - Production on Sun/SunOS 5.8 (64 bit)