ChemOffice.Com - CambridgeSoft

Administrator
the actual version of the CambridgeSoft Oracle Cartridge
software.
• select * from
cscartridge.globals;
returns the whole table of cartridge
infromation
• select value from
cscartridge.globals where id =
'VERSION'
reyurns only the version of the cartridge
Checking for fields indexed
by the cartridge
The cartridge maintains the all_csc_indexes table in
its own schema or in the tablespacedesignated in
PARAMETERS when creating the index. The
columns of this table are:
• OWNER
• INDEX_NAME
• TABLE_NAME
• COLUMN_NAME
• COLUMN_TYPE
All of the fields are defined as VARCHAR2(30)
columns. Every index created by the cartridge has
an entry in this table. The content of this table can
be retrieved by the public. By retrieving the content
the client program can know if a column is
supposed to contain chemical structures.
For Example:
select * from
cscartridge.all_csc_indexes where
owner = 'me' and
table_name = 'my_table' and
column_name = 'my_column'
What to do if creating
an index fails
When the user executes a CREATE INDEX
command, the cartridge reads all the rows from the
table, and creates its own tables for fast
substructure search.
There are three different outcomes of the execution
of the CREATE INDEX command
1. Success indicated by an "index created"
message usually displayed by the client
program
2. Invalid data in one or more records indicated
by an "ORA-29863: warning in the execution
of ODCIINDEXCREATE routine" message.
In this case the user should check the content
of the CsCartridge.Index_name_E table for
the unhandled records, which are logged by the
cartridge. The index is usable as it is, the noninterpreted
records should be manually
reviewed and corrected. The
CsCartridge.Index_name_E table contains the
rowid-s of the failed rows, and an error
message, The user has to locate the failed rows
by the rowid, and correct the errors.
3. If an exception is thrown by ORACLE, which
is not handled by the cartridge, then the index
creation results in an ORA-xxxxx message, and
a call stack. If this happens, then the index is
marked by Oracle as
LOADING/FAILED/UNUSABLE, and the
only command a user can execute regarding the
index is the ALTER INDEX REBUILD
command. The following:
ALTER INDEX ixname REBUILD
PARAMETERS('CONTINUE_POPULATIN
G');
198•CS Oracle Cartridge
CambridgeSoft
What to do if creating an index fails