RTree index build fails with ORA-13230

Question

Hi all,
We are running Oracle8i Enterprise Edition Release 8.1.7.0.0 on Windows NT.
Our spatial table PKT_KP has exactly 1349162 records, and the statements:
DROP INDEX PKT_KP_INDX FORCE;
CREATE INDEX PKT_KP_INDX ON PKT_KP (GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('SDO_INDX_DIMS=2 SDO_RTR_PCTFREE=0 SDO_FANOUT=40
SDO_COMMIT_INTERVAL=512 SDO_ MAX_MEMORY=25000000 TABLESPACE=DKMINDX INITIAL=64K NEXT=64K
MAXEXTENTS=UNLIMITED');
produced the following error list:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13230: failed to create temporary table [GST_KF_INDX_tr2$$] during R-tree creation
ORA-29400: data cartridge error
ORA-00907: missing right parenthesis
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 8
ORA-06512: at line 1
I read carefully all documents here on this error and I've tried every suggestion, especially undocumented SDO_ MAX_MEMORY parameter with the several values: 25000000, 33554432, 67108864, etc.
1. Plenty of free space in the tablespace DKMINDX
2. Plenty of free space in the TEMP tablespace
3. Temporary table GST_KF_INDX_tr0$$ exists, and has 1349162 records
4. Temporary table GST_KF_INDX_tr1$$ exists, and has no records
Does anyone have any ideas?
Thanks in advance,
Zdravko

Answer 1

Hi,
In 8.1.7.0 I was able to create an r-tree index on a table with over 10 million points using the following command (which I wouldn't recommend in 9i):
create index mydata_sidx on mydata(geometry)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS('INITIAL=400M NEXT=25M PCTINCREASE=0 SDO_RTR_PCTFREE=0');
In my procedure I didn't actually set the tablespace in the create index - I think I set the user's default tablespace to the tablespace I wanted the index to go into.
Also, if I remember correctly, in 8.1.7 r-tree index builds required a lot of temp space, so you might want to check to make sure you have plenty (this was changed in 9i). Also, you might want to remove stuff like sdo_commit_interval, which is not used for r-tree index builds. If your data is only 2d you won't need sdo_indx_dims.
All that said, I don't ever remember seeing "missing right parenthesis".
I did just notice you have a space between sdo_ and max_memory.
So if I were you, I'd use a more modest create index statement:
from system account:
alter user whoever default tablespace dkmindx;
connect whoever/whoeverspassword
DROP INDEX PKT_KP_INDX FORCE;
CREATE INDEX PKT_KP_INDX ON PKT_KP (GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS (SDO_RTR_PCTFREE=0
INITIAL=64M NEXT=10M');