Re: what is user_objects.DATA_OBJECT_ID?

Well,

The concept is the same, but the specific details are different for context server.

I don't know the internal arrangements,
but it is still a case of an object without a data segment - in this case you have
a DOMAIN index, which allows for a
user (or Context programmer) defined
structure. This could, for example, mean that the context software knows that the index definition is actually redirecting it to a 'hidden' table with a couple of other indexes.

One guess why the two databases give
different reports is that the two indexes seem to have been created some years
apart, so perhaps some internal convention in Context has changed in the interim.

Sorry I can't help further.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar - UK, April 3rd - 5th
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases


G M wrote in message <50a5e6b6.0203081933.7682bc15_at_posting.google.com>...


>Thanks for your reply.

>

>

>This index is not partitioned on either of them:

>

>on db1:

>

>SQL> select INDEX_NAME, INDEX_TYPE,PARTITIONED from user_indexes

>  2  where INDEX_NAME = 'COREREF_ABSTRACT';

>

>INDEX_NAME                     INDEX_TYPE                  PAR

>------------------------------ --------------------------- ---

>COREREF_ABSTRACT               DOMAIN                      NO

>

>

>SQL> select PARAMETERS from user_indexes where INDEX_NAME =

>'COREREF_ABSTRACT';

>

>PARAMETERS

>---------------------------------------------------------------------------

-----


>memory 50M

>

>

>on db2:

>

>SQL> select INDEX_NAME, INDEX_TYPE,PARTITIONED from user_indexes

>  2  where INDEX_NAME = 'COREREF_ABSTRACT';

>

>INDEX_NAME                     INDEX_TYPE                  PAR

>------------------------------ --------------------------- ---

>COREREF_ABSTRACT               DOMAIN                      NO

>

>SQL> select PARAMETERS from user_indexes where INDEX_NAME =

>'COREREF_ABSTRACT';

>

>PARAMETERS

>---------------------------------------------------------------------------

-----


>sync memory 50M

>

>

>Actually this index was created on "db1" manually (see the script

>below) and I want to find out where this index's data is:

>

>---

>

>BEGIN

>ctxsys.driimp.create_index('COREREF_TITLE','CORE_REF',USER,

>'REFID','2','TITLE','1',

>'1600','789189','8130','789190',

>NULL, NULL, NULL );

>

>

>ctxsys.driimp.set_object('DATASTORE','DIRECT_DATASTORE',0);

>

>ctxsys.driimp.set_object('DATATYPE','CHAR_DATATYPE',0);

>

>ctxsys.driimp.set_object('DATAX','SYNCH_DATAX',0);

>

>ctxsys.driimp.set_object('FILTER','NULL_FILTER',0);

>

>ctxsys.driimp.set_object('SECTION_GROUP','NULL_SECTION_GROUP',0);

>

>ctxsys.driimp.set_object('LEXER','BASIC_LEXER',3);

>ctxsys.driimp.set_value('INDEX_TEXT','1');

>ctxsys.driimp.set_value('INDEX_THEMES','0');

>ctxsys.driimp.set_value('WHITESPACE','-_/(){}[]#@,<>:"|+=&');

>

>ctxsys.driimp.set_object('WORDLIST','BASIC_WORDLIST',1);

>ctxsys.driimp.set_value('STEMMER','1');

>

>ctxsys.driimp.set_object('STOPLIST','BASIC_STOPLIST',365);

>

>CREATE INDEX "ISI"."COREREF_ABSTRACT" ON "CORE_REF" ("ABSTRACT" )

>INDEXTYPE IS "CTXSYS"."CONTEXT" PARAMETERS ('sync memory 50M') ;

>ctxsys.driimp.set_value('STOP_WORD','a');

>ctxsys.driimp.set_value('STOP_WORD','about');

>ctxsys.driimp.set_value('STOP_WORD','above');

>ctxsys.driimp.set_value('STOP_WORD','abs');

>--

>-- many similar statments here with different word

>--

>ctxsys.driimp.set_value('STOP_WORD','you');

>ctxsys.driimp.set_value('STOP_WORD','your');

>ctxsys.driimp.set_value('STOP_WORD','yours');

>ctxsys.driimp.set_value('STOP_WORD','yourself');

>ctxsys.driimp.set_value('STOP_WORD','yourselves');

>

>ctxsys.driimp.set_value('STOP_WORD','yr');

>

>ctxsys.driimp.set_object('STORAGE','BASIC_STORAGE',6);

>ctxsys.driimp.set_value('I_TABLE_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>ctxsys.driimp.set_value('K_TABLE_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>ctxsys.driimp.set_value('R_TABLE_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>ctxsys.driimp.set_value('N_TABLE_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>ctxsys.driimp.set_value('I_INDEX_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>ctxsys.driimp.set_value('P_TABLE_CLAUSE','tablespace RESINDEX storage

>(initial 1000M next 500M pctincrease 0)');

>

>commit;

>COMMIT; END;

>

>CREATE INDEX "ISI"."COREREF_ABSTRACT" ON "CORE_REF" ("ABSTRACT" )

>INDEXTYPE IS "CTXSYS"."CONTEXT" PARAMETERS ('memory 50M') ;

>

>------

>

>I had to pass the parameter ('memory 50M') in order to execute the

>statement, it was originally ('sync memory 50M') from the db2 dump

>file.

>

>basically I just want to make sure the index was created correctly

>(with data) in "db1". How could I check that?

>

>Guang