Cause: Specified table does not exist or server does not have write privileges.

Action: Check the result table.

DRG-10002 can not insert into result table

Cause: Text server is not privileged to insert, tablespace is exhausted.

Action: Check privileges and tablespace.

DRG-10011 invalid object name string

Cause: A table, column or procedure name specified had an invalid format. It is either too long or contains illegal characters. Probably you are passing in incorrect parameters.

Action: Check parameter values.

DRG-10015 id exceeds limit(2147483642) of a number

Cause: The limit of an ID is 2147483642.

Action: Use an ID with value 214748364 or lower.

DRG-10016 you must be the owner to modify this object

Cause: An attempt was made to modify an object which you do not own.

Action: Have the owner modify the object.

DRG-10017 you must be string to do this: string

Cause: An attempt was made to modify an object which you have no privilege.

Action: Ask the owner modify the object.

DRG-10100 invalid argument found: string

Cause: Invalid command argument was specified.

Action: Check the documentation for the legal arguments and re-execute the command.

DRG-10101 no value for argument: string

Cause: This argument requires value(s).

Action: Re-execute the command with the correct argument value(s).

DRG-10102 mandatory argument missing: string

Cause: This argument is mandatory.

Action: Re-execute the command and specify the argument.

DRG-10103 illegal value for argument: string

Cause: An illegal value was passed to this argument.

Action: Check the documentation for the legal values for this argument.

DRG-10200 invalid server personality mask: string

Cause: The specification for the server personality mask is invalid.

Action: Check the documentation and specify the correct mask.

DRG-10202 server failed to register

Cause: The server failed to register itself with the data dictionary.

Action: Look at the next error on the stack.

DRG-10203 server named string does not exist

Cause: Update was called with the name of a server that does not exist.

Action: Correct the name of the server.

DRG-10204 server update failed

Cause: The attempt to update the server failed.

Action: Look at the next error on the stack.

DRG-10205 server deregister failed

Cause: The attempt to deregister the server from the data dictionary failed.

Action: Look at the next error on the stack.

DRG-10206 failed to perform recovery for a server or client

Cause: The attempt to perform recovery for a server or client failed.

Action: Contact Oracle Support Services.

DRG-10301 timed out waiting for responses from servers

Cause: Not enough servers are running to handle the current system load, and a large backlog of commands has accumulated; perhaps no servers are running. This message could also indicate an internal error where one of the servers has crashed trying to process a given request.

Action: Check that enough servers are running, and that they are processing commands of the correct type. For instance, a DDL command might timeout if all the servers are setup to exclusively process query commands. Also, check the server log files.

DRG-10302 interrupted waiting for responses from servers

Cause: User interrupted the request before it was completed.

Action: Restart the request.

DRG-10303 could not queue given commands to be processed

Cause: The given command or commands could not (all) be queued. This could indicate an extremely high system load, but it is more likely an internal error.

Action: Check if any servers are running to process the command.

DRG-10304 unexpected error sending command(s) to Oracle Text server

Cause: There was an unexpected error sending commands to the server.

Action: Contact Oracle Support Services.

DRG-10305 pipe string is full

Cause: Could not send command to pipe, because the pipe was full.

Action: Check if any servers are running to process the commands on that pipe.

DRG-10306 server terminated unexpectedly while processing command

Cause: The server shut down during execution of your command. This could be caused by a SHUTDOWN ABORT, or by an internal error in the server.

Action: If the server terminated had an internal error, then contact Oracle Support Services.

DRG-10307 no servers running

Cause: Could not process command because no servers are running with the correct personality mask.

Action: Start some servers with correct personality mask.

DRG-10308 no server with the required string personality mask is running

Cause: Could not process command because no servers are running with the correct personality mask.

Action: Start some servers with correct personality mask.

DRG-10309 not enough job queue processes

Cause: Could not process command because no servers with the correct personality mask are running.

Action: Increase the JOB_QUEUE_PROCESSES initialization parameter or reduce the parallel degree for this statement.

DRG-10310 servers were shutdown before processing request

Cause: The command could not be completed because the servers were shut down or terminated before processing the request.

Action: Start another server with the correct personality mask.

DRG-10311 remote send not supported

Cause: An attempt was made to specify a database link in an index specification.

Action: Specify only local index names.

DRG-10312 logfile name must be specified

Cause: An attempt was made to start logging without specifying a log file name.

Action: Specify a log file name.

DRG-10313 logging has already been started

Cause: An attempt was made to start logging even though logging has already been started.

Action: Stop logging first or ignore this message.

DRG-10314 logging has not been started

Cause: An attempt was made to stop logging even though logging has not been started.

Action: Start logging first or ignore this message.

DRG-10315 logging is not supported on MTS

Cause: You tried to start logging on MTS

Action:

DRG-10500 CREATE_INDEX failed: column spec string

Cause: Failed to create text index on the specified column.

Action: See the next errors on stack and take appropriate action.

DRG-10501 invalid stopword: string

Cause: The stopword specified could be lexed into multiple tokens with current lexer preference.

Action: Check lexer preference and respecify the stopword.

DRG-10502 index string does not exist

Cause: The specified index does not exist or you do not have access to it.

Action: Check the name of the index and your access to it.

DRG-10503 table string cannot be indexed because it has no primary key

Cause: A text key needs to be a single column unique key whose length does not exceed 64 bytes. no such key was defined as an unique index or declared as a primary or unique key constraint.

Action: Create a suitable text key for the table or specify it explicitly in this procedure call.

DRG-10504 primary key is required when using the DETAIL_DATASTORE

Cause: you tried to use the detail datastore to index a table with no primary key constraint

Action: Add a primary key constraint on the table

DRG-10506 table does not exist: string

Cause: The table, view, or synonym specified does not exist. There may also be a permissions problem reading the table.

Action: Reinvoke the operation with the correct table name.

DRG-10507 duplicate index name: string

Cause: The specified index already exists in the dictionary.

Action: This index can be updated or deleted, however this is only allowed if there is no text index available on the text column.

DRG-10509 invalid text column: string

Cause: The column specified is not valid.

Action: Check that the following are valid:

Text column is of supported datatype

Valid table name, column name in the specification

DRG-10510 stopword is missing

Cause: The stopword to be added was not specified.

Action: Specify the stopword.

DRG-10511 index string does not exist or is incomplete

Cause: Index creation is not complete.

Action: Create index before performing this operation.

DRG-10513 index string metadata is corrupt

Cause: Dictionary contains bad preferences for this index.

Action: Contact your database administrator.

DRG-10516 failed to perform DDL operation due to an Oracle error

Cause: The DDL operation requested has failed because of an Oracle error.

Action: See the Oracle error on the stack and take the appropriate action.

DRG-10517 index string is already valid

Cause: The index was in a valid state and did not need the requested operation.

Action: Check the requested operation.

DRG-10518 an operation is in progress which conflicts with string request

Cause: Another session is operating on this index. It could be:

DML is requested and DDL is in progress or

DDL is requested and DML is in progress operation on the index

Action: Try again later.

DRG-10520 failed to drop index: string

Cause: Failed to drop index on the specified index.

Action: See the Oracle error on the stack and take the appropriate action.

Cause: The table, view, synonym or column specified does not exist. There may also be a permissions problem reading the table.

Action: Reinvoke the operation with the correct table name or column name.

DRG-10573 index string is obsolete

Cause: An obsolete index was specified.

Action: Perform UPGRADE_INDEX on the index.

DRG-10574 failed to upgrade text index string

Cause: The upgrade operation has failed because of an Oracle error.

Action: See the Oracle error on the stack and take the appropriate action.

DRG-10579 must provide text query criteria

Cause: Text query criteria is mandatory.

Action: Provide text query criteria.

DRG-10580 parallel indexing is not supported: string

Cause: An attempt was made to create index with parallel servers.

Action: Drop index and set parallel to 1 in create index.

DRG-10581 indirect datastores cannot be used with long or lob text columns

Cause: An attempt was made to create an index on a log or LOB column using an indirect datastore such as the file or URL datastores.

Action: Use a direct datastore or a VARCHAR column.

DRG-10582 column string does not exist in table string

Cause: An invalid column was specified.

Action: Specify a valid column.

DRG-10583 TRUNCATE INDEX failed: string

Cause: Failed to truncate the specified index.

Action: See the next errors on the stack and take appropriate action.

DRG-10584 failed to stringstringstring due to an Oracle error

Cause: A DDL operation on an index object failed due to SQL error.

Action: See the accompanying error.

DRG-10595 ALTER INDEX string failed

Cause: Failed to alter index.

Action: See the next errors on stack and take appropriate action.

DRG-10597 invalid rebuild online operation

Cause: REBUILD ONLINE is not supported for requested operation.

Action: Alter index without the online option.

DRG-10598 invalid parallel operation

Cause: PARALLEL is not supported for requested operation.

Action: Alter index without the parallel option.

DRG-10599 column is not indexed

Cause: The column specified is not indexed.

Action: Create an index on the column before performing this operation.

DRG-10601 failed to remove pending DML for this index

Cause: The system could not remove triggers setup to monitor updates to the requested table.

Action: See next error on stack to determine course of action. Contact Oracle Support Services if necessary. Until this error is fixed, updates to all text columns in the given table may not be indexed.

Cause: The system could not record that a change had been made to the given column.

Action: See next error on stack to determine course of action. Contact Oracle Support Services if necessary. Until this error is fixed, updates to all text columns in the given table may not be indexed.

DRG-10606 server failed to access the DML Queue

Cause: The server was had an error accessing the DML Queue.

Action: See next error on stack.

DRG-10700 preference does not exist: string

Cause: The preference name specified does not exists.

Action: Retry with the correct preference name.

DRG-10701 preference string already exists

Cause: The specified preference already exists.

Action: Drop the preference if you want to re-create it.

DRG-10702 cannot create or modify preference in another user's schema

Cause: An attempt was made to create or modify in another user's schema.

Action: Owner or CTXSYS or a user who has CTXADMIN role should create preference.

DRG-10703 invalid framework object string

Cause: You specified an invalid object type.

Action: Use a valid framework object.

DRG-10704 preference string does not have an attribute named string

Cause: An attempt was made to set value for a invalid attribute (not supported by the object.

Action: Specify the correct attribute name.

DRG-10705 invalid value string for attribute string

Cause: An attempt was made to set an illegal value for an attribute.

Action: Specify the correct attribute value for the datatype of the attribute.

DRG-10706 length of string exceeds maximum size of string

Cause: Parameter is too many bytes.

Action: Correct preference setting and resubmit.

DRG-10707 a value is required for attribute string of preference string

Cause: A required attribute was not provided.

Action: Correct preference setting and resubmit.

DRG-10708 invalid class id string for preference string

Cause: The specified class ID is not correct for the specified preference.

Action: Specify the correct class ID.

DRG-10709 this preference is referenced by string and cannot be dropped

Cause: The specified preference is used as part of another preference and cannot be dropped until the referring preference is modified.

DRG-11703 user string must have at least CTXAPP role to execute this function

Cause: Privilege is not sufficient.

Action: Grant user CTXAPP role.

DRG-11704 phrase string does not exist

Cause: Phrase does not exist.

Action: Use another phrase or create it.

DRG-11705 multilevel jump from string to string

Cause: The thesaurus load file has a multilevel jump which could not be parsed.

Action: Correct thesaurus file.

DRG-11706 invalid relation string

Cause: An invalid relation was specified.

Action: The set of valid relations will be displayed. Additionally, you may be able to specify a translation, which has the syntax languagename, where languagename can be any string up to 10 bytes. Specify a valid relation and resubmit.

DRG-11707 valid relations: string

Cause: An invalid relation was specified.

Action: The set of valid relations will be displayed. Additionally, you may be able to specify a translation, which has the syntax languagename, where languagename can be any string up to 10 bytes.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12203 section group string does not exist

Cause: Section group provided does not exist.

Action: Provide an existing section group.

DRG-12204 error while dropping section group string

Cause: Detected an Oracle error while dropping a section group.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12206 tag string already exists in section group string

Cause: The start tag provided already exists in the same section.

Action: Provide another start tag.

DRG-12210 error while adding section string

Cause: Detected an Oracle error while adding a section.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12211 section or section id string does not exist

Cause: Section name or section ID to be dropped does not exist.

Action: Provide an existing section name or section ID.

DRG-12212 error while dropping section string

Cause: Detected an Oracle error while dropping a section.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12213 cannot create/drop section group or sections for other user

Cause: You can only create/drop section group objects of your own.

Action: Have the other user create/drop his/her own objects.

DRG-12217 tags cannot be more than 64 bytes

Cause: Maximum limit of start and end tag is 64 bytes.

Action: Provide a shorter start and end tag.

DRG-12218 section group name missing

Cause: A section group name must be provided.

Action: Provide a section group name when creating section or section group.

DRG-12219 section name missing

Cause: A section name must be provided when creating a section.

Action: Provide a section name.

DRG-12220 a valid tag must be provided

Cause: A tag must be provided when adding a section to a section group.

Action: Provide a tag.

DRG-12223 section name string is a reserved name

Cause: An attempt was made to name a section a reserved name.

Action: Do not use the reserved name.

DRG-12224 use ctx_ddl.create_section_group to create section groups

Cause: An attempt was made to use CTX_DDL.CREATE_PREFERENCE to create a section group.

Action: Use CTX_DDL.CREATE_SECTION_GROUP.

DRG-12225 this type of section cannot be added to this section group

Cause: An attempt was made to add sections to the null section group, add a stop section to a non-auto section group, or add a zone or field section to the auto section group.

Action: Do not add this type of section to this section group.

DRG-12226 a field section named string already exists in this section group

Cause: An attempt was made to name an attribute or zone section the same name as an existing field section.

Action: Use another name.

DRG-12227 a zone section named string already exists in this section group

Cause: An attempt was made to name an attribute or zone section the same name as an existing field section.

Action: Use another name.

DRG-12228 maximum number of field sections (string) exceeded

Cause: A section group has more than the maximum number of unique field sections.

Action: Use fewer unique field sections.

DRG-12229 special section string already exists in this section group

Cause: An attempt was made to add a special section which already exists.

Action: No action required.

DRG-12230 special section name must be one of string

Cause: An attempt was made to add an invalid special section.

Action: Use a valid special section.

DRG-12231 an attr section named string already exists in this section group

Cause: An attempt was made to name a field or zone section the same name as an existing attribute section.

Action: Use another name.

DRG-12232 invalid attribute tag format

Cause: A tag was specified for use as an attribute tag which did not have the correct format. An attribute tag must have the form TAG@ATTR.

Action: Use the correct format.

DRG-12233 xml sections cannot co-exist with other section types

Cause: An attempt was made to add an xml section to a section group or index which already has zone, field, attr, or special sections. Or, you tried to add a zone, field, attr, or special section to a section group or index which already has xml sections.

Action:

DRG-12300 an index with this column list already exists in the index set

Cause: An attempt was made to add an index to an index set, but an index with the specified column list already exists.

Action:

DRG-12301 index does not exist in index set

Cause: An attempt was made to remove an index from an index set, but the specified index was not found.

Action:

DRG-12302 invalid column list

Cause: An invalid column list was specified -- it may have a syntax error, duplicate columns, or invalid column names.

Action:

DRG-12303 cannot add more than 99 indexes to an index set

Cause: An attempt was made to add too many indexes to the index set.

Action:

DRG-12304 index set string does not exist

Cause: An invalid index set name was specified.

Action:

DRG-12305 column string data type is not supported for index set columns

Cause: An attempt was made to specify a column in the column list of an index of an index set which does not have a valid datatype.

Action: Use only DATE, NUMBER, CHAR, or VARCHAR2 columns in index column lists.

DRG-12306 column string is too long for index set columns

Cause: An attempt was made to specify a column in the column list of an index of an index set which is too long.

Action: CHAR and VARCHAR2 columns must be 30 bytes or less max length.

DRG-12307 column string is NULL and cannot be indexed

Cause: An attempt was made to index a row where at least one of the meta columns was NULL.

Action: Provide a value for the meta column and reindex the row.

DRG-12308 use ctx_ddl.create_index_set to create index sets

Cause: An attempt was made to use CTX_DDL.CREATE_PREFERENCE to create an index set.

Action: Use CTX_DDL.CREATE_INDEX_SET.

DRG-12400 template string is empty

Cause: The template is empty.

Action: Check the template was installed successfully.

DRG-12401 invalid template: query within a loop

Cause: A CTX EXEC tag cannot occur within a CTX REPEAT tag.

Action: Remove the CTX EXEC tag.

DRG-12402 error processing template string, line string

Cause: An error occurred when processing a template.

Action: See other errors on the stack and take the appropriate action.

DRG-12403 template string was not found

Cause: The template does not exist.

Action: Check the name of the template and check that it is installed.

DRG-12404 more than one template string found

Cause: More than one template with the same name was found.

Action: Remove templates as appropriate.

DRG-12405 error occurred processing CTX REDIRECT or CTX LABEL tag

Cause: Error in syntax of a tag.

Action: Correct the syntax of the tag.

DRG-12406 invalid CTX EXEC tag attribute (string)

Cause: The specified attribute is incorrectly specified.

Action: Check the syntax of the specified attribute.

DRG-12407 invalid CTX REPEAT tag attribute (string)

Cause: The specified attribute is incorrectly specified.

Action: Check the syntax of the specified attribute.

DRG-12408 invalid variable reference: string

Cause: The variable referenced does not exist.

Action: Check the label and column name.

DRG-12409 syntax error for label in string

Cause: The SQL in a CTX EXEC tag has incorrect syntax for a label or label type.

Action: Check the SQL attribute of the CTX EXEC tag.

DRG-12410 could not process CTX EXEC tag

Cause: An error occurred when processing the SQL attribute of a CTX EXEC tag.

Action: See other errors on the stack and take the appropriate action.

DRG-12411 SQL processing error: string

Cause: Error executing SQL from SQL attribute of CTX EXEC tag.

Action: Check the SQL in the SQL attribute.

DRG-12412 missing or invalid Template Processor attribute (string)

Cause: The specified attribute was missing or invalid in a HTML input field.

Action: Check the Template Processor-specific attributes in the INPUT, SELECT, RADIO and CHECKBOX tags of the template.

DRG-12422 write to client failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12430 mandatory argument missing: string

Cause: This argument is mandatory.

Action: Re-submit the URL with this argument supplied.

DRG-12431 configuration section string not found

Cause: Specified configuration argument is invalid.

Action: Re-submit the URL with this argument corrected.

DRG-12432 configuration file string not found or unreadable

Cause: An error occurred when processing the configuration file.

Action: Contact the administrator.

DRG-12433 load of string JDBC driver class failed

Cause: Driver class is invalid.

Action: Contact the administrator to modify configuration.

DRG-12434 connection failed using configuration string information

Cause: Configuration information is not correct.

Action: Contact the administrator to modify configuration.

DRG-12435 highlight table allocation failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12436 document table allocation failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12437 highlight table release failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12438 document table release failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12439 highlight table read failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12440 document table read failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12441 counting the number of highlights failed

Cause: See the following messages.

Action: Contact the administrator.

DRG-12500 stoplist string already exists

Cause: The specified stop list already exists.

Action: Remove the duplicate stop list if you want to re-create it.

DRG-12501 null stoplist is not allowed

Cause: The specified stop list is null.

Action: Specify a valid stop list.

DRG-12502 cannot modify stoplists owned by other users

Cause: You can only create/drop Stop List or Stop Word objects of your own.

Action: Have the other user create/drop his/her own objects.

DRG-12503 error while creating or dropping stoplist

Cause: Detected an Oracle error while creating Stop List.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12504 stoplist string does not exist

Cause: The specified stop list does not exist.

Action: Check that the Stop List is valid.

DRG-12505 error while adding or removing a stop word

Cause: Detected an Oracle error while adding or removing Stop Word.

Action: See the accompanying Oracle error and take appropriate action.

DRG-12506 stop word string does not exist in stoplist string

Cause: The specified Stop word does not exist.

Action: Check that the Stop Word is valid.

DRG-12507 stop word string already exists in this stoplist

Cause: The specified stop word already exists.

Action: Remove the duplicate word if you want to re-create it.

DRG-12508 null stop words are not allowed

Cause: The specified stop word is null.

Action: Remove the null stop word if you want to re-create it.

DRG-12509 length of the stop word string exceeded the limit of string bytes

Cause: A stop list entry has exceeded the maximum length.

Action: Reduce the length of the stop list entry.

DRG-12511 use ctx_ddl.create_stoplist to create stoplists

Cause: An attempt was made to use CTX_DDL.CREATE_PREFERENCE to create a stop list.

Action: Use CTX_DDL.CREATE_STOPLIST.

DRG-12512 invalid stop class string

Cause: You specified an invalid stop class.

Action: Specify a valid stop class.

DRG-12513 valid stop classes are: string

Cause: You specified an invalid stop class.

Action: The valid stop class are listed.

DRG-12514 languages must be specified for stopwords in a MULTI_STOPLIST

Cause: An attempt was made to add a stopword to a MULTI_STOPLIST without specifying the language of the stopword.

Action: Specify the language of the stopword.

DRG-12515 cannot specify language for stopwords in a BASIC_STOPLIST

Cause: An attempt was made to add a language-specific stopword to a BASIC_STOPLIST.

Action: Do not specify language for the stopword.

DRG-12516 language column must be specified when using the multi stoplist

Cause: An attempt was made to create an index using a MULTI_STOPLIST but a language column was not specified.

Action: Specify a language column.

DRG-12517 cannot add stopthemes to a MULTI_STOPLIST

Cause: An attempt was made to add a stoptheme to a MULTI_STOPLIST. This is not supported in this version.

Action:

DRG-12600 user datastore procedure contains a semicolon

Cause: The procedure name specified included a semicolon.

Action: Remove the semicolon or rename the procedure. The correct format is packagename.procedure_name.

DRG-12601 invalid user datastore procedure name: string

Cause: The format of the procedure name is invalid. It should be in the form packagename.procedurename or procedurename.

Action: Make sure the PROCEDURE attribute has the format packagename.procedurename or procedurename.

DRG-12602 index owner does not have access to user datastore procedure: string

Cause: The index owner does not have execute privilege for the procedure.

Action: Use CTXSYS to grant execute privilege for the procedure to the index owner.

DRG-12603 CTXSYS does not own user datastore procedure: string

Cause: CTXSYS does not have execute privilege to the user datastore procedure.

Action: Make sure the package is owned by CTXSYS and the procedure exists.

DRG-12604 execution of user datastore procedure has failed

Cause: An error occurred while executing the user datastore procedure.

Action: Check the datastore procedure.

DRG-12605 datatype of column number in COLUMNS list is not supported

Cause: One or more of the columns in the column list of the multi datastore are of a type which the multi datastore is unable to process.

Action: Change the column list of the multi datastore to contain only supported types. PL/SQL functions can be used in the column list to convert unsupported types to supported types.

DRG-12606 error encountered while parsing COLUMNS list

Cause: An oracle error was encountered while parsing the columns list of the multi datastore.

Action: See next error on stack and take appropriate action.

DRG-12607 only ctxsys can create MULTI_COLUMN preferences

Cause: In order to create a MULTI_COLUMN datastore preference, the effective user must be CTXSYS.

Action: Contact your DBA to create the preference as CTXSYS.

DRG-12700 seed word must be a single word

Cause: Seed word is not a single word.

Action: Use a single-word seed word.

DRG-12800 Attribute NESTED_TYPE must have owner name as prefix

Cause: The attribute NESTED_TYPE does not have an owner name prefix.

Action: Reset the attribute NESTED_TYPE to include owner name prefix.

DRG-12801 invalid type: string

Cause: Invalid nested_type.

Action: Check the owner and the type attribute names.

DRG-12802 invalid type column: string

Cause: Column specified does not exist in the type table.

Action: Check the type table.

DRG-12803 invalid text datatype

Cause: LONG and LONG RAW are not supported in nested table.

Action: Change text column to a supported data type.

DRG-12900 Operation: string for index: string has already been started

Cause: The specified operation has been started.

Action: No action required.

DRG-13000 error while adding or removing a sub lexer

Cause: See next error.

Action: See next error.

DRG-13001 sub lexer and multi lexer must have the same owner

Cause: A sub lexer was specified which is not owned by the owner of the enclosing multi-lingual lexer preference.

Action: Specify a sub lexer owned by the owner of the multi-lexer preference.

DRG-13002 preference string is not a MULTI_LEXER

Cause: An attempt was made to add a sub lexer to a lexer preference which cannot accept sub lexers. Only multi-lingual lexers can accept sub lexers.

Action: Specify a multi-lingual lexer.

DRG-13003 preference string cannot be used as a sub lexer

Cause: A preference was specified for sub lexer which is not a lexer, or is a multi-lingual lexer.

Action: Specify a sub lexer which is not a multi-lingual lexer.

DRG-13004 language is invalid

Cause: An invalid language was specified for the sub lexer or stopword.

Cause: Oracle Text needs to call external code to complete your request, and could not start the EXTPROC agent process.

Action: Start the listener if it is configured for external procedures and is not running. If your listener is running, then configure it for starting external procedures and restart it. Consult the Oracle9i Net Services Administrator's Guide for details.