Hi there, we created a text index (9ir2) like this:

begin
ctx_ddl.create_preference('wd_wp_items_pref',
'DETAIL_DATASTORE');
ctx_ddl.set_attribute('wd_wp_items_pref',
'detail_table',
'wd_web_page_items');
ctx_ddl.set_attribute('wd_wp_items_pref',
'detail_key',
'web_page_id');
ctx_ddl.set_attribute('wd_wp_items_pref',
'detail_lineno',
'seq');
ctx_ddl.set_attribute('wd_wp_items_pref',
'detail_text',
'text');
end;
/

drop index wd_web_pages_imt;

create index wd_web_pages_imt on wd_web_pages (text)
indextype is ctxsys.context
parameters('datastore wd_wp_items_pref');


So this text index was not created with any storage options. This is
obviously not the corect way to do things!

I know we can set the storage options by defining storage "preferences"
but does anyone know if these can be applied retrospectively or do we
need to drop and recreate the index? It is nearing the max extents
default of 200 on this system.



--
jeremy

We use Oracle 9iR2 on Solaris 8 with the Oracle HTTP Server and
mod_plsql