Parrallel tables with spatial operators

Question

I have a point in polygon script that works, but in order to speed up the creation of the point table (~175M rows) I tried adding PARALLEL 4 and /*+ PARALLEL (t,4) */ Only the parallel part is new to the create point table sql.
I used CTAS to create a point table like this:
CREATE TABLE &OUT_POINT_SCHEMA..&OUT_POINT_TABLE NOLOGGING PARALLEL 4 TABLESPACE ORDERS_02
AS
SELECT /*+ PARALLEL (t,4) */
  cast(lpad(to_char(LON/1000000, '999.000000'),11) || lpad(to_char(LAT/1000000, '99.000000'),10) as varchar2(21))   ULL, 
  MDSYS.SDO_GEOMETRY(2001, 8307, MDSYS.SDO_POINT_TYPE(LON/1000000, LAT/1000000, NULL), NULL, NULL)    GEOM
FROM
  &IN_POINT_SCHEMA..&IN_POINT_TABLE
WHERE
  LON is not null
GROUP BY
  LON, LAT;The spatial index was created like this:
CREATE INDEX &OUT_POINT_TABLE._SIDX ON &OUT_POINT_TABLE (GEOM) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS('TABLESPACE=ORDERS_IDX WORK_TABLESPACE=ORDERS_03 LAYER_GTYPE=POINT');In theory, should the sql still work when I use, for example SDO_INSIDE? Or are there other things that I need to take into consideration? In other words, would the fact that the spatial point table was created with a parallel option impact spatial queries. When I try to monitor the process of the point in polygon sql with a check_session script (I am not a DBA) I see 4 rows with the same sql text which I assume is due to the parallel 4 parameter and I am also seeing wait_events like async descriptor resize and wait_time -1. Sorry to be so vague but I am trying to figure out if this query has a chance of finishing or if i broke it by adding the parallel option. Any guidance or suggestions would be appreciated.
Thanks,
David

Answer 1

Yes, spatial operators (say SDO_INSIDE) can work in parallel queries.
If you can show us your query explain plan, it will be easier to see
how SDO_INSIDE is executed.