Index going to SYSTEM tablespace?

Question

I've set up a basic_storage preference where INDX is my tablespace name as follows:
BEGIN
ctx_ddl.create_preference('MYSTORE', 'BASIC_STORAGE');
ctx_ddl.set_attribute('MYSTORE', 'I_TABLE_CLAUSE',
'tablespace INDX storage (initial 32K)');
ctx_ddl.set_attribute('MYSTORE', 'K_TABLE_CLAUSE',
'tablespace INDX storage (initial 32K)');
ctx_ddl.set_attribute('MYSTORE', 'R_TABLE_CLAUSE',
'tablespace INDX storage (initial 32K)');
ctx_ddl.set_attribute('MYSTORE', 'N_TABLE_CLAUSE',
'tablespace INDX storage (initial 32K)');
ctx_ddl.set_attribute('MYSTORE', 'I_INDEX_CLAUSE',
'tablespace INDX storage (initial 32K)');
END;
Then I create my context index like this:
CREATE INDEX I_FORM_TITLE_WORD ON FORMS(FORM_TITLE)
indextype is ctxsys.context
PARAMETERS('storage MYSTORE populate');
Everything seems to get created properly with no errors but I have questions regarding the storage parameters:
1. I get the following when I select index_name, tablespace_name from user_indexes:
DR$I_FORM_TITLE_WORD$X INDX
I_FORM_TITLE_WORD SYSTEM
Why is I_FORM_TITLE_WORD in the SYSTEM tablespace and is it possible to move it to INDX?
2. I get the following when I select table_name, tablespace_name from user_tables:
DR$I_FORM_TITLE_WORD$I INDX
DR$I_FORM_TITLE_WORD$K
DR$I_FORM_TITLE_WORD$N
DR$I_FORM_TITLE_WORD$R INDX
Why is there nothing listed for the KEYMAP and NEGATIVE LIST tables?
Any insight into these questions/concerns would be greatly appreciated.
Thanks,
Diane
null

Answer 1

Thanks for the info regarding the K and N tables but I'm still confused about how the I_FORM_TITLE_WORD got created in the SYSTEM tablespace.
I agree that I don't want I_FORM_TITLE_WORD in the SYSTEM tablespace if possible. That's the main reason for my posting.
First, I thought because I specified:
PARAMETERS('storage MYSTORE populate')
in the index creation that it would automatically put all pieces (index and table parts) into my INDX tablespace.
Second, even if the above failed to be true, I created the index as a user that has it's own separate tablespace set as a default. So at least why wasn't the I_FORM_TITLE_WORD created in that user's tablespace?
Diane
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Adeeva ([email protected]):
I'd recommend creating a separate tablespace
called CTX_INDX or similar. Using SYSTEM as
the default can be dangerous if you don't
know what's going to be loaded into it. If
you didn't specify a storage clause, this
is where they go. Plus, some of the little
admin tables that get created by the system
don't give you the option.
The K and N tables are created as Index Organised Tables (IOT) and still create
as per the STORAGE definitions, but you
just can't see this in the view.<HR></BLOCKQUOTE>
null