25 DRG-10000 to DRG-52404

Cause: Error during read of specified text column

Cause: specified table does not exist or server does not have write privileges

Cause: text server is not privileged to insert, tablespace exhausted

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.

Cause: the limit of an id is 2147483642

Cause: you tried to modify an object which you do not own

Cause: you tried to modify an object which you have no privilege

Cause: invalid command argument was specified

Cause: this argument requires value(s)

Cause: this argument is mandatory

Cause: an illegal value was passed to this argument

Cause: the specification for the server personality mask is invalid

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

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

Cause: the attempt to update the server failed

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

Cause: Contact oracle support

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

Cause: User interrupted the request before it was completed

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.

Cause: There was an unexpected error sending command(s) to server

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

Cause: The server shutdown during execution of your command. This could be caused by a shutdown abort, or by an internal error in the server.

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

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

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

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

Cause: You tried to specify a database link in an index specification

Cause: You tried to start logging without specifying a logfile name

Cause: You tried to start logging even though logging has already been started

Cause: You tried to stop logging even though logging has not been started

Cause: You tried to start logging on MTS

Cause: failed to create text index on the specified column

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

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

Cause: a textkey 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

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

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

Cause: the specified index already exists in the dictionary

Cause: the column specified is not valid

Cause: The stopword to be added was not specified.

Cause: index creation is not complete

Cause: dictionary contains bad preferences for this index

Cause: the ddl operation requested has failed because of an Oracle error

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

Cause: another session is operating on this index. it could be: a) DML is requested and DDL is in progress or b) DDL is requested and DML is in progress operation on the index

Cause: Failed to drop index on the specified index

Cause: all Oracle Text alter index options require the REBUILD keyword

Cause: you tried to create an index on a table with an illegal primary key datatype

Cause: you called create index with parallel = 0

Cause: you called parallel create index on non-partitioned table

Cause: you specified a user name that is invalid

Cause: the optimize operation requested has failed because of an Oracle error

Cause: object name has exceeded the maximun length of 30 bytes

Cause: name may have additional periods(.)

Cause: column specification may have additional periods(.)

Cause: The index was not in a valid state due to some prior error.

Cause: The parameter string was missing

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

Cause: you specified an obsolete index

Cause: the upgrade operation has failed because of an Oracle error

Cause: text query criteria is mandatory

Cause: attempted to create index with parallel servers

Cause: You tried to create an index on a long or lob column using an indirect datastore such as the file or url datastores

Cause: you specified an invalid column

Cause: Failed to truncate index

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

Cause: failed to alter index

Cause: REBUILD ONLINE is not supported for requested operation.

Cause: PARALLEL is not supported for requested operation.

Cause: The column specified is not indexed.

Cause: Optimization ran into the snapshot too old error.

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

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

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

Cause: the meta data for the index has not been created yet

Cause: Procedural replication is on and no rowid to primary key mapping available in base table

Cause: Cannot encode composite key with more than 16 columns

Cause: This procedure is not supporeted when Procedural replciation is on

Cause: the preference name specified does not exists

Cause: the specified preference already exists

Cause: you tried to create a preference for another user

Cause: you specified an invalid object type

Cause: you tried to set value for a invalid attribute (not supported by the object.

Cause: you tried to set an illegal value for an attribute

Cause: Parameter is too many bytes

Cause: A required attribute was not provided

Cause: the specified class id is not correct for the specified preference

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

Cause: Invalid value provided for save_copy attribute It should be one of these: (PLAINTEXT, FILTERED, NONE)

Cause: Invalid value provided for SAVE_COPY attribute. It should be a boolean value

Cause: Cannot call set_sec_grp_attr for an attribute whose value is already set in a preference

Cause: Cannot call add_sec_grp_attr_val for an attribute without calling set_sec_grp_attr for the same attribute

Cause: Cannot call add_sec_grp_attr_val or rem_sec_grp_attr_val for a boolean attribute

Cause: Cannot set related attributes to incompatible values

Cause: Value of prefix_ns_mapping is neither of the form xmlns:pfx="ns" nor of the form xmlns="ns"

Cause: Invalid combination of PATH_SECTION_GROUP, DATAGUIDE attribute and NEVER_POPULATE

Cause: Operation is not supported with NEVER_POPULATE index option

Cause: Invalid value for stage_itab_max_rows

Cause: The syntax was invalid.

Cause: ALTER INDEX supported only with JSON_ENABLE and IS JSON constraint. Any degradation of the index state is not supported either.

Cause: Unrecognized parameter

Cause: Wrong data type or out of range

Cause: You tried to set DEFAULT_INDEX_MEMORY to a value higher than the maximum set in MAX_INDEX_MEMORY

Cause: You specified an incorrectly formatted size string

Cause: You specified size (in bytes) which is outside the allowed range

Cause: the join character sets cannot have characters in common

Cause: INDEX_TEXT and INDEX_THEMES preferences both cannot be FALSE.

Cause: a stoplist cannot have more than 4096 stopwords. This includes stopthemes.

Cause: index owner does not have the role defined in FILE_ACCESS_ROLE

Cause: the role does not exist in the database

Cause: the procedure name specified is invalid. For instance, it may have a semicolon

Cause: the specified procedure could not be found

Cause: the index owner does not have execute privilege on the specified procedure

Cause: the value specified for the filename_charset attribute of the file datastore is not a valid character set name

Cause: For security reasons, only SYS can modify the FILE_ACCESS_ROLE system parameter

Cause: a stoplist cannot have more than 250 stopclasses with stoppatterns. This does not include NUMBERS stopclass.

Cause: Failed to process the query

Cause: You tried to create an SQE for another user

Cause: See the next error on the stack.

Cause: One or more terms within a CONTAINS query consist of just a stopword or a phrase of just stopwords

Cause: An error occurred while trying to open a contains cursor

Cause: You tried to fetch or close a contains cursor with an id which does not exist.

Cause: You tried to fetch from a contains cursor which was not open.

Cause: You tried to create a stored query with a name already used.

Cause: The query name specified is not valid

Cause: The specified stored query does not exist.

Cause: There is no document with the specified textkey.

Cause: last_count returns hit from in-memory query,so an in-memory query must be run before you can use count_last

Cause: A token to be inserted in the feedback table is longer than the maximum allowed column size.

Cause: Feedback id is longer than the maximum allowed length for the feedback_id column.

Cause: You specified a sharelevel which is not 0 or 1

Cause: Not privileged to insert.

Cause: Not privileged to delete.

Cause: Failed to process feedback request

Cause: upper-case form of the section name is longer then supported length

Cause: WITHIN operator used in theme index query

Cause: A field section or a attribute section is specified in a nested section search

Cause: The given section name does not exist in USER_SECTIONS

Cause: An invalid value was supplied for SPAN argument to NEAR

Cause: An invalid value was supplied for ORDER argument to NEAR

Cause: User attempts to issue a query with CONTAINS predicate including 0 while giving FIRST_ROWS hint.

Cause: An invalid value was supplied for SCORE argument to FUZZY

Cause: An invalid value was supplied for NUMRESULTS argument to FUZZY

Cause: An invalid value was supplied for WEIGHT argument to FUZZY

Cause: You specified a combination of condition and order by columns in a catsearch query which cannot be executed by the index's index set efficiently

Cause: You specified a column in a condition or order by which is not part of the ctxcat index

Cause: You specified an order by clause which has some columns ascending and some descending. This is not currently supported by catsearch

Cause: For efficient execution of this Vgram query, we require presence of a prefix index.

Cause: you have specified an invalid structured clause

Cause: the query plan for your query is invoking a catsearch operator functionally rather than as an index rowsource. The catsearch operator does not support functional invocation

Cause: Used an operator not supported by CTXRULE. Currently it only supports AND, NEAR, phrase, NOT, WITHIN, OR, ABOUT, EQUIVALENCE, STEM and THESAURUS operators

Cause: incorrect grammar specification

Cause: incorrect scoring type specification

Cause: unsupported operator specified

Cause: incorrect scoring algorithm specification

Cause: Unsupported VGRAM token type 1.

Cause: The given SDATA section name does not exist in USER_SECTIONS

Cause: The given literal is not compatible with the data type of the specified SDATA section.

Cause: A field section or a attribute section is specified in a nested section search

Cause: More than one predefined scoring component (i.e. RELEVANCE, OCCURRENCE, etc.) is used in the scoring expression of the DEFINESCORE operator

Cause: The query side of the same within mixes different types of scoring components(i.e. RELEVANCE, OCCURRENCE, etc.)

Cause: The completion score is used without using the WITHIN operator

Cause: Used an attribute not supported by CTXRULE. This restriction is due to lack of wildcard support for CTXRULE indexes.

Cause: An invalid value was supplied for ORDER argument to NDATA

Cause: An invalid value was supplied for PROXIMITY argument to NDATA

Cause: The scoring expression specified in DEFINESCORE or NORMALIZATION_EXPR in the query template either contains components with unsupported datatypes or does not return numerical values.

Cause: The IGNORE score is used as the right hand operand of MINUS

Cause: The OCCURRENCE and COMPLETION score cannot be used with ABOUT queries

Cause: the query plan for your query is invoking a matches operator functionally rather than as an index rowsource. The matches operator does not support functional invocation

Cause: Near2 span must be between 0 and 100

Cause: Near2 weights must be between 0 and 10

Cause: NDATA operator is not supported in the specified operation

Cause: Charaters outside query element are not valid

Cause: Charaters between certain elements are not allowed

Cause: XML template is wrong. Possible causes include missing closing tag or receiving invalid attributes or characters.

Cause: Some tag has been opened and not closed properly.

Cause: Occurrence of some element that should be only between another element that was not found

Cause: Either query is missing or is wrongly possitioned

Cause: Invalid ordering of tags as of specs

Cause: Invalid repetition of XML element

Cause: Invalid nesting of same element has been encountered

Cause: savescore argument must be true or false

Cause: topn argument must be true or false

Cause: savescore must be true to use topn in ctxfiltercache

Cause: ctxfiltercache with topn must be child of AND, THRESHOLD, or WEIGHT operators

Cause: used ctxfiltercache operator with zero query_filter_cache_size

Cause: must order query results by score desc when topn argument is true

Cause: Index partition has been set to non-readable mode

Cause: CTXIN operator is not rightmost child of AND node

Cause: The given Filter section name does not exist in USER_SECTIONS

Cause: The predicate query cursor was not found.

Cause: An invalid value was supplied for MINREQD argument to NEAR

Cause: An invalid value was supplied for the THRESHOLD argument to NDATA.

Cause: The CTXIN query was run in parallel.

Cause: The syntax is PATTERN(regex). regex is missing.

Cause: The syntax of the regular expression is incorrect

Cause: The expression ^$ has no match.

Cause: The regular expression matches too many words.

Cause: Used ctxfiltercache operator with unsupported SDATA.

Cause: can not allocate more memory

Cause: A keyword was invalid.

Cause: A keyword was missing.

Cause: A value for the argument was missing.

Cause: An invalid value was given for the argument

Cause: More than one value has been specified for the argument

Cause: the supplied parameter string is not correct

Cause: The parameter string was invalid.

Cause: Tried to add more than one stopword

Cause: The parameter string was invalid

Cause: failed to connect to Oracle database

Cause: failed to open a file

Cause: Single byte lexer selected in multibyte language setting

Cause: See the next error on stack

Cause: this database session does not exist or has terminated

Cause: the path specified is not valid

Cause: the filename specified is not valid

Cause: This lexer does not support this query operator

Cause: You specified a value for the parameter which is out of range

Cause: You specified a value for the parameter which is too long

Cause: You specified a value for the parameter which is invalid

Cause: You specified a result table which has the wrong number, type, or names of columns for this operation.

Cause: You did not specify a value for the parameter

Cause: You specified values for the two parameters which are invalid

Cause: You tried to create an object whose name conflicts with an object of that type which already exists

Cause: You tried to modify or drop an object which does not exist

Cause: You tried to invoke an operation on an index which is not supported by the index type

Cause: failed to write to a file

Cause: failed to read from a file

Cause: unsupported section group is specified for functional contains

Cause: theme indexing is on in the lexer preference for functional contains

Cause: you specified an invalid value

Cause: the file specified by START_LOG already exists, and is not a previously written log file

Cause: the training table is empty or the context index of training table is not populated

Cause: the ctxrule index policy is inconsistent with the policy in which the rule was trained

Cause: the rule format is not valid for this operation

Cause: the rule table is empty

Cause: feature preparation program can not find any feature in the specified collection

Cause: The Oracle XML parser reported an error

Cause: The logfile parameter to CTX_OUTPUT.START_LOG or CTX_OUTPUT.START_QUERY_LOG contains an invalid character (such as a forward slash)

Cause: Failed to convert the datetime value.

Cause: The file is currently being used by another process.

Cause: You tried to use a feature not generally available.

Cause: This lexer does not support entity extraction

Cause: you tried to use ctx_output tracing in an MTS session

Cause: you tried to enable a trace that is already enabled

Cause: you tried to disable a trace that is not enabled

Cause: you tried to perform MDATA operation on non-mdata section

Cause: you tried to call CTX_DDL.REMOVE_MDATA() or CTX_DDL.ADD_MDATA() on a MDATA section which is created with ALLOW_ADD_REM parameter set to FALSE.

Cause: The value for the specified parameter cannot be as specified

Cause: You tried to trace more than 64 errors with ctx_output

Cause: You specified invalid value for radius parameter

Cause: You specified invalid value for max_length parameter

Cause: You specified invalid value for use_saved_copy parameter

Cause: You specified/used a lexer which does not support ctx_doc.policy_stems

Cause: You specified/used a lexer which does not support ctx_doc.policy_noun_phrases

Cause: You specified/used a lexer which does not support ctx_doc.policy_part_of_speech

Cause: Feature not enabled

Cause: Sentiment procedure called with an invalid max_inst value.

Cause: An invalid type attribute value was specified.

Cause: The specified classifier did not exist.

Cause: The specified topic was null for a non-aggregate sentiment request.

Cause: The specified lexer is not supported for the Default Sentiment Classifier.

Cause: You tried to use the INSO filter on a platform which does not support it

Cause: The user filter command must be 32 characters or less

Cause: The user filter command cannot contain special characters such as slashes, parentheses, semicolons, etc.

Cause: The user filter command could not be executed.

Cause: The user filter command exited with the given error status.

Cause: ORACLE_HOME is not set

Cause: Value of the file name is too long

Cause: you specified a format column which is not a char, varchar, or varchar2 type.

Cause: you specified a charset column which is not a char, varchar, or varchar2 type.

Cause: the procedure name specified had a semicolon

Cause: CTXSYS does not have execute privilege to the procedure filter stored procedure

Cause: an error occur while executing the proedure filter stored procedure

Cause: the index owner does not have execute privilege of the procedure

Cause: the length of the datastore data passed to the filter stored procedure is longer than the maximum length (32767 bytes)

Cause: The INSO safe callout cannot be executed

Cause: The mail message has an error at the indicated line

Cause: mail filter configuration file has an error at the indicated line

Cause: Third-party filter could not filter this document because it was unable to allocate sufficient virtual memory.

Cause: Third-party filter could not filter this document because this document is corrupted.

Cause: Third-party filter was able to recognize the format of this document but could not filter it because this format is not supported.

Cause: Third-party filter encountered a password protected or encrypted document and could not filter it because this level of password protection or encryption is not supported.

Cause: Third-party filter could not filter this document because it was unable to create a temporary file or unable to write to a temporary file.

Cause: Third-party filter could not filter this document because the filter timed out.

Cause: There was an error initializing the third-party filter.

Cause: Third-party filter does not support the format of this document.

Cause: The format column specifies a binary document

Cause: you specified a configuration column which is not a char, varchar, or varchar2 type.

Cause: An error was encountered while indexing the document. The error may have occurred during lexing, parsing for sections, or other action during document tokenization

Cause: You attempted to create an index on an index-organized table, but the indextype does not support this action.

Cause: You attempted to create a function-based index but the indextype does not support this action.

Cause: you attempted to mark the index from INPROGRESS to FAILURE but create/alter on the same index is in progress in another session

Cause: you attempted to perform an operation on a policy, but the operation is only valid for an index.

Cause: you attempted to perform an operation on an index, but the operation is only valid for a policy.

Cause: You attempted to create an index with an unsupported column expression.

Cause: the column specified is not valid

Cause: the column specified is not valid

Cause: the specified option is not valid for this optimization mode

Cause: the new policy has a different owner than the source policy

Cause: failed to polulate the text index on the specified partition

Cause: the index has pending unsynced rows

Cause: the $S table cannot be created with the specified storage option

Cause: you specified an invalid rowid in ctx_ddl.add_mdata

Cause: there was an error

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: OPTIMIZE FAST is not supported with big_io option

Cause: OPTIMIZE MERGE requires near_realtime option

Cause: OPTIMIZE FAST is not supported with separate_offsets option

Cause: STAGEITAB requires context index

Cause: SEPARATE_OFFSETS requires context index

Cause: BIG_IO requires context index

Cause: optimize validation failed

Cause: Index already has stage_itab set

Cause: Index does not have stage_itab set

Cause: Index already has big_io set

Cause: Index does not have big_io set

Cause: Index already has separate_offsets set

Cause: Index does not have separate_offsets set

Cause: the specified policy does not exist or you do not have access to it.

Cause: the $A table cannot be created with the specified storage option

Cause: the $F table cannot be created with the specified storage option

Cause: Index optimization generated an error for one or more tokens, possibly due to corruption of the token_info blob.

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: SPLIT DOLLARI doesn't generate any output for empty mapping table

Cause: Index optimization was interrupted by ctx_adm.stop_optimize

Cause: FORWARD INDEX needs context index

Cause: FORWARD INDEX does not exist

Cause: OPTIMIZE REBUILD is not supported due to the specified reason

Cause: FILTER CACHE only for context index

Cause: SAVE COPY needs context index

Cause: Not able to fetch partition id for given rowid

Cause: Not able to fetch partition name for given partition position

Cause: Section group attribute xml_enable set to TRUE for a local index

Cause: Storage option stage_itab_max_rows needs to be accompanied by stage_itab

Cause: Not able to fetch partition position for given rowid

Cause: READ mode for this partition is set to FALSE. No optimize operations are permitted in this mode.

Cause: forward index was specified at partition level and not at index level

Cause: save copy was specified at partition level and not at index level

Cause: xml_save_copy was specified for non-xml enabled text index

Cause: xml_forward_enable was specified for non-xml enabled text index

Cause: attempt to enable xml_forward_enable without xml_save_copy set to true

Cause: 'xml_enable' was set to TRUE for non-XMLType columns.

Cause: 'xml_enable' was set to TRUE for XMLType with object-relational storage.

Cause: the index is marked as invisible. Only DML operations on the base table are allowed

Cause: The FORWARD_INDEX attribute was specified for an XML enabled text index.

Cause: The SAVE_COPY attribute was specified for an XML enabled text index.

Cause: More than 50% of tokens in $I are fragmented.

Cause: Maxtokens value was either less than zero or too high.

Cause: Ctxagg optimize merge limits the size of rows to under 4K.

Cause: Internal error in optimize merge.

Cause: Storage option stage_itab_parallel needs to be accompanied by stage_itab

Cause: Storage option Forward index specified along with asynchronous update

Cause: the document specified for linguistic extraction could not be parsed. This could indicate that the document is not well-formed English

Cause: the primary key value parameter passed to the service request is longer than the maximum primary key length (64 bytes)

Cause: the primary key value parameter passed to the service request is null

Cause: an ORACLE error occurred while linguistic output was being inserted into the result table

Cause: the document specified for linguistic extraction was parsed but the document content was insufficient for linguistic extraction by the specified parser.

Cause: linguistic services initialization failed

Cause: invalid gist level

Cause: Invalid gist level

Cause: The document contains invalid characters

Cause: An oracle error was encountered during knowledge base access

Cause: the primary key value parameter passed to the service request is not valid

Cause: the length of the index name is longer than the maximum index name size

Cause: the requested operation is not supported for the current language

Cause: invalid gist numparagraphs

Cause: invalid gist numparagraphs

Cause: invalid gist max percent

Cause: invalid gist max percent

Cause: the rowid value parameter passed to the service request is not valid

Cause: Either using Oracle Express edition or supplied Knowledge Base was required but was not installed.

Cause: Unable to allocate memory

Cause: linguistic feature not enabled

Cause: possibly miss-spelt column name or keyword

Cause: possibly miss-spelt column name

Cause: bad file name, wrong file_type or file system error

Cause: total length of statement exceeds database maximum

Cause: invalid option argument

Cause: either bad data or bad data file

Cause: an error occured parsing this row's data

Cause: file not found or could not be read

Cause: token expected was not found

Cause: could not make sense of text where value expected

Cause: see previous messages

Cause: text must be inserted into a LONG RAW type column

Cause: load file must have specific format for loading thesaurus

Cause: an attempt to open or to write to the given file failed

Cause: user has not been granted UPDATE or SELECT privilege

Cause: number of values provided does not match the number of text keys

Cause: user does not have CTXUSER, CXAPP or CTXADMIN role

Cause: see accompanying Oracle error

Cause: table specified does not have a LONG or LONG RAW column

Cause: see accompanying error message

Cause: file does not exist

Cause: see accompanying error message

Cause: no row in the table has the text key(s) specified

Cause: some other process has a lock on the row

Cause: primary key value is not provided

Cause: invalid option argument

Cause: value of the file name is too long

Cause: TEXTEND not found at end of record

Cause: could be misplaced

Cause: value of the column name or value is too long

Cause: value of the phrase or relation word is too long

Cause: <TEXTSTART: not found at start of record

Cause: characters encountered while reading through end of line

Cause: value of the column is too long or mismatched quote

Cause: column does not exist or it's misspelled

Cause: not enough memory

Cause: the document referred to by the URL has permanently moved

Cause: client did not make correct request

Cause: user has to provide password or other authentication

Cause: payment is required before the URL can be accessed

Cause: access to the URL is denied

Cause: the document can not be found on the host specified

Cause: client did not make response within timeout period

Cause: Web server identified in URL doesn't obey HTTP protocol

Cause: host portion of the URL could not be parsed

Cause: attempt to open local file failed

Cause: attempt to read local file failed

Cause: the protocol parsed is neither http or file

Cause: the address of the host specified could not be resolved

Cause: attempt to connect to host was forcibly refused

Cause: a network operation timed out

Cause: unknown error writing request to Web server

Cause: too long a chain of HTTP redirections given the URL

Cause: The length of the URL string is longer than URLSIZE

Cause: document larger than user-set maximum size

Cause: row deleted or otherwise missing

Cause: thread operation failed

Cause: socket open failed; probably too many open file descriptors

Cause: an unexpected HTTP error has occurred

Cause: unexpected error

Cause: unexpected error

Cause: MAXURLS * URLSIZE cannot be larger than the limit

Cause: the URL redirected to a site with neither http nor file protocol

Cause: The remote host returned a 501 not implemented error

Cause: The remote host returned a 502 bad gateway error

Cause: The remote host returned a 503 service temporarily unavailable error

Cause: The remote host returned a 504 gateway timeout error

Cause: thesaurus with same name exists

Cause: thesaurus does not exist

Cause: error while parsing thesaurus operator in query term. see error message for details.

Cause: privilege is not sufficient

Cause: phrase does not exist

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

Cause: You specified an invalid relation. 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

Cause: You specified an invalid relation. 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

Cause: ctxkbtc cannot compile more than 16 thesauri

Cause: number of thesaurus terms exceeds maximum

Cause: knowledge base does not permit terms longer than 80 characters

Cause: internal limit on size of data per term

Cause: There is a term in the thesaurus with multiple broader terms

Cause: There is a synonym ring in the thesaurus with multiple preferred terms

Cause: Some synonyms in a synonym ring have different broader terms

Cause: BT relation cannot be between two existing knowledge base categories

Cause: only a PT can have NTs

Cause: only a PT can have RTs

Cause: There are multiple preferred terms for this term

Cause: The broader term hierarchy in this thesaurus is too deep

Cause: too many synonyms for a single preferred term

Cause: no entries in thesaurus

Cause: language specification cannot be more than 10 characters

Cause: you tried to add a NULL phrase to the thesaurus

Cause: phrase with same name exists

Cause: you tried to nominate a phrase with no synonyms to be the preferred term, or you tried to drop SYN from a phrase with no synonyms

Cause: you tried to remove the preferred term relation from a phrase which is not a preferred term.

Cause: you tried to drop a relation which does not exist

Cause: you tried to drop a relation which does not exist

Cause: you tried to drop a relation which does not exist

Cause: you tried to drop a relation which does not exist

Cause: you tried to drop a translation which does not exist

Cause: you tried to drop translations which does not exists

Cause: the term has more than one translation in the specified language

Cause: A term of the form 'homograph(disambiguation)' is missing the the homograph.

Cause: A term of the form 'homograph(disambiguation)' is missing the the disambiguation (i.e., homograph()).

Cause: A term of the form 'homograph(disambiguation)' has text after the disambiguation (e.g, homograph(disambiguation) extra text".

Cause: An invalid value was specified for thes_toktype attribute.

Cause: Enquire user to decide if continue is necessary HTTP_ERROR = 100

Cause: Telling client a protocol switching just happened HTTP_ERROR = 101

Cause: Telling client things are ok HTTP_ERROR = 200

Cause: Telling client things are created HTTP_ERROR = 201

Cause: Telling client things are accepted but not commited HTTP_ERROR = 202

Cause: The returned metainformation is not the definitive set HTTP_ERROR = 203

Cause: request has been fulfilled but no new information found HTTP_ERROR = 204

Cause: Telling client to reset the document view HTTP_ERROR = 205

Cause: Telling client document content is a patial content HTTP_ERROR = 206

Cause: Telling client document is partially updated HTTP_ERROR = 207

Cause: Telling client multiple choices of resources is possible HTTP_ERROR = 300

Cause: The URI has been assigned a new permanent URI HTTP_ERROR = 301

Cause: The URI resides temporarily under a different URI. HTTP_ERROR = 302

Cause: The URI can be found using GET METHOD under a different URI HTTP_ERROR = 303

Cause: Response to conditional GET, indicating document not modified. HTTP_ERROR = 304

Cause: The client should use specified proxy to repeat the request HTTP_ERROR = 305

Cause: Proxy redirection. Not used HTTP_ERROR = 306

Cause: The resource is temporarily under a different URI. HTTP_ERROR = 307

Cause: The URL syntax is incorrect. Request rejected by server. HTTP_ERROR = 400

Cause: The request requires further authentication. HTTP_ERROR = 401

Cause: Reserved for future use. HTTP_ERROR = 402

Cause: The server refuses to fulfil the request from client HTTP_ERROR = 403

Cause: The server can not find the requested URI HTTP_ERROR = 404

Cause: The user agent specified method not allowed HTTP_ERROR = 405

Cause: Requested resource is not acceptable according to request header HTTP_ERROR = 406

Cause: The client must authenticate itself with the proxy. HTTP_ERROR = 407

Cause: The server is tired of waiting for the requst HTTP_ERROR = 408

Cause: The request conflicts with the current state of the URI HTTP_ERROR = 409

Cause: The resource is no longer available and no forwarding address. HTTP_ERROR = 410

Cause: The server must receive a content-length header. HTTP_ERROR = 411

Cause: Telling the user agent that the resource failed preconditions HTTP_ERROR = 412

Cause: Request rejected because request entity is too large. HTTP_ERROR = 413

Cause: The server is refusing to accept the URI which is too big. HTTP_ERROR = 414

Cause: The server is refusing the request because of media type HTTP_ERROR = 415

Cause: The byte range request can not be satisfied by the resource extent. HTTP_ERROR = 416

Cause: Server can not meet the user agent's expectation. HTTP_ERROR = 417

Cause: Reserved HTTP_ERROR = 418

Cause: Reserved HTTP_ERROR = 419

Cause: The server encountered internal error in fulfilling the request. HTTP_ERROR = 500

Cause: The server can't support a request feature which has yet to be implemented. HTTP_ERROR = 501

Cause: In serving the request, the server received invalid response from gateway. HTTP_ERROR = 502

Cause: Server overloaded or in maintenance mode. HTTP_ERROR = 503

Cause: Upstream server did not timely respond to the gateway server. HTTP_ERROR = 504

Cause: The HTTP version in the request header is rejected by the server. HTTP_ERROR = 505

Cause: Reserved HTTP_ERROR = 506

Cause: The the user agent knows the returned reponse is stale. HTTP_CACHE_ERROR = 10

Cause: User agent's attempt to revalidate a stale response failed. HTTP_CACHE_ERROR = 11

Cause: The cache is intentionally disconnected for a time period. HTTP_CACHE_ERROR = 12

Cause: Cache freshness lifetime and response age both greater than 24 hours. HTTP_CACHE_ERROR = 13

Cause: Telling cache manager, content encoding/media type has been changed in cache. HTTP_CACHE_ERROR = 14

Cause: Arbitrary information about cache to be presented to logger. HTTP_CACHE_ERROR = 99

Cause: connection to remote host failed USER_AGENT_ERROR

Cause: The host name is not specicied in URI. USER_AGENT_ERROR

Cause: Unable to open the file specified USER_AGENT_ERROR

Cause: FTP server responds to the agent request USER_AGENT_ERROR

Cause: No response from FTP server during operation. USER_AGENT_ERROR

Cause: Server operation timed out USER_AGENT_ERROR

Cause: Gopher server responds to the agent request. USER_AGENT_ERROR

Cause: Processing of URL request was interrupted USER_AGENT_ERROR

Cause: Connection operation was interupped USER_AGENT_ERROR

Cause: Telling client things are ok USER_AGENT_ERROR

Cause: A very old web server USER_AGENT_ERROR

Cause: The server is mumbering something not understandable USER_AGENT_ERROR

Cause: The server is using an unkown access authentication scheme USER_AGENT_ERROR

Cause: News Server is responding USER_AGENT_ERROR

Cause: wrong access scheme is used. USER_AGENT_ERROR

Cause: Telling client things are ok USER_AGENT_ERROR

Cause: The web server setup configured too many redirections USER_AGENT_ERROR

Cause: Detected end of file is unexpected USER_AGENT_ERROR

Cause: Response from WAIS caused buffer overflow USER_AGENT_ERROR

Cause: Bad WAIS Server USER_AGENT_ERROR

Cause: Connect to WAIS server failed USER_AGENT_ERROR

Cause: register what system call replies USER_AGENT_ERROR

Cause: Protocol class is wrongfully connected to ther server USER_AGENT_ERROR

Cause: Telling client things are ok USER_AGENT_ERROR

Cause: Pass information to telnet agent USER_AGENT_ERROR

Cause: Need to tell user that cache entry has been reloaded USER_AGENT_ERROR

Cause: Let user agent client be aware of new rule loading USER_AGENT_ERROR

Cause: Let user agent client be aware of proxy redirection USER_AGENT_ERROR

Cause: Prompt user for name W3CLIB_MSG = 0

Cause: Prompt user for name W3CLIB_MSG = 1

Cause: Prompt user for name W3CLIB_MSG = 2

Cause: Prompt user for password W3CLIB_MSG = 3

Cause: Prompt user for file name W3CLIB_MSG = 4

Cause: Prompt user for account W3CLIB_MSG = 5

Cause: Warn user of deny of service. W3CLIB_MSG = 6

Cause: Warn user of location changes. W3CLIB_MSG = 7

Cause: Warn user of rule changes. W3CLIB_MSG = 8

Cause: Warn user of pending replacement W3CLIB_MSG = 9

Cause: Warn user of authentication failure W3CLIB_MSG = 10

Cause: Warn user of proxy authentication failure W3CLIB_MSG = 11

Cause: Warn user the repetition of previous method used W3CLIB_MSG = 12

Cause: Warn user of big document processing W3CLIB_MSG = 13

Cause: Warn user of location changes W3CLIB_MSG = 14

Cause: Warn user of destination document changes W3CLIB_MSG = 15

Cause: Warn user of redirection effects on method W3CLIB_MSG = 16

Cause: Warn user of automatic proxy change W3CLIB_MSG = 17

Cause: Section group with the same name already exists

Cause: detect an Oracle error while creating section group

Cause: section group provided does not exist

Cause: detect an Oracle error while dropping a section group

Cause: the start tag provided already exists in the same Section

Cause: detect an Oracle error while adding a section

Cause: Section name or Section id to be dropped does not exist

Cause: detect an Oracle error while dropping a Section

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

Cause: max limit of start and end tag is 64 bytes

Cause: must provide section group name

Cause: must provide Section name when creating a Section

Cause: must provide tag when adding a section to a section group

Cause: you tried to name a section a reserved name

Cause: you tried to use ctx_ddl.create_preference to create a section group

Cause: You tried 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

Cause: you tried to name an attribute or zone section the same name as an existing field section

Cause: you tried to name an attribute or field section the same name as an existing zone section

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

Cause: you tried to add a special section which already exists

Cause: you tried to add an invalid special section

Cause: you tried to name a field or zone section the same name as an existing attribute section

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

Cause: you tried 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

Cause: you tried to add a column section which already exists

Cause: you tried to name a non-sdata section the same name as an existing sdata section

Cause: you tried to name a non-mdata section the same name as an existing mdata section

Cause: you tried to map a column but the section name is already being used by another section

Cause: a section group has more than the maximum number of unique mdata sections

Cause: a section group has more than the maximum number of unique sdata sections

Cause: an order by column has been mapped to an MDATA section

Cause: an order by or filter by column cannot be implicitly mapped to an SDATA section because the name is not valid as a section name

Cause: the value of a filter by or order by column is too large to be indexed

Cause: the datatype specified for a sdata or mdata section is invalid

Cause: failed to convert data

Cause: failed to convert data

Cause: failed to convert data

Cause: a section group has more than the maximum number of unique NDATA sections

Cause: you tried to name a non-NDATA section the same name as an existing NDATA section

Cause: you tried to name a non-MVDATA section the same name as an existing MVDATA section

Cause: a section group has more than the maximum number of unique mvdata sections

Cause: you tried to add MVDATA section in XML_SECTION_GROUP

Cause: No valid rowid(s) provided with MVDATA update procedure

Cause: An attempt was made to use an operation that is not supported for these SDATA sections.

Cause: An attempt was made to use a query ordering by SDATA section that is optimized for search only.

Cause: The data type of the SDATA section in the XML enabled context index was invalid.

Cause: Section attribute 'optimized_for' was not set to 'search' for the SDATA section in the XML enabled context index.

Cause: An attempt was made to create an index with a section group having both RANGE_SEARCH_ENABLE on and other sections such as Attribute, Field, MDATA, NDATA, SDATA, Special, or Zone section.

Cause: You tried to add an index to an index set, but an index with the specified column list already exists

Cause: You tried to remove an index from an index set, but the specified index was not found

Cause: You specified an invalid column list -- it may have a syntax error, duplicate columns, or invalid column names

Cause: You tried to add too many indexes to the index set

Cause: You specified an invalid index set name

Cause: You specified a column in the column list of an index of an index set which does not have a valid datatype

Cause: You specified a column in the column list of an index of an index set which is too long

Cause: You tried to index a row where at least one of the meta columns was NULL.

Cause: you tried to use ctx_ddl.create_preference to create an index set

Cause: you tried to use compression on attributes lob column for xml full text index

Cause: Index set name is too many bytes

Cause: The template is empty.

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

Cause: An error occurred when processing a template.

Cause: The template does not exist.

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

Cause: Error in syntax of a tag.

Cause: The specified attribute is incorrectly specified.

Cause: The specified attribute is incorrectly specified.

Cause: The variable referenced does not exist.

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

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

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

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

Cause: See the following messages.

Cause: This argument is mandatory.

Cause: Specified conf argument is invalid.

Cause: An error occurred when processing the configuration file.

Cause: Driver class is invalid.

Cause: Configuration information is not correct.

Cause: See the following messages.

Cause: See the following messages.

Cause: See the following messages.

Cause: See the following messages.

Cause: See the following messages.

Cause: See the following messages.

Cause: See the following messages.

Cause: the specified stop list already exists

Cause: the specified stop list is null

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

Cause: detect an Oracle error while creating Stop List

Cause: the specified stop list does not exist

Cause: detect an Oracle error while adding or removing Stop Word

Cause: the specified Stop Sord does not exist

Cause: the specified stop word already exists

Cause: the specified stop word is null

Cause: A stop list entry has exceeded the maximun length

Cause: you tried to use ctx_ddl.create_preference to create a stoplist

Cause: you specified an invalid stop class

Cause: You specified an invalid stop class

Cause: You tried to add a stopword to a multi_stoplist without specifying the language of the stopword

Cause: You tried to add a language-specific stopword to a basic stoplist.

Cause: you tried to create an index using a multi stoplist but you did not specify a language column

Cause: you tried to add a stoptheme to a MULTI_STOPLIST. This is not supported in this version.

Cause: index already has multi_stoplist

Cause: index does not have a language column

Cause: LANGUAGE COLUMN does not match language column of the Index

Cause: NUMBERS is a predefined stopclass to specify numeric values

Cause: the procedure name specified had a semicolon

Cause: the format of the procedure name is invalid. It should be in the form PACKAGENAME.PROCEDURENAME or PROCEDURENAME

Cause: the index owner does not have execute privilege of the procedure

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

Cause: an error occur while executing the user datastore procedure

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

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

Cause: In order to create a multi column datastore preference, the effective user must be ctxsys.

Cause: seed word is not a single word

Cause: the attribute NESTED_TYPE does not have an owner name prefix

Cause: invalid nested_type or

Cause: column specified does not exist in the type table

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

Cause: the specified operation has been started

Cause: see next error

Cause: you specified a sub lexer which is not owned by the owner of the enclosing multi-lingual lexer preference

Cause: you tried to add a sub lexer to a lexer preference which cannot accept sub lexers. Only multi-lingual lexers can accept sub lexers.

Cause: you specified a preference for sub lexer which is not a lexer, or is a multi-lingual lexer or is an auto lexer

Cause: you specified an invalid language for the sub lexer or stopword

Cause: you specified an NLS language name as the alt value

Cause: you tried to remove a sub lexer for a language, but no sub lexer was defined for that language

Cause: you tried to define an alternate value for the DEFAULT sub lexer

Cause: you tried to remove the DEFAULT sub lexer

Cause: you tried to use a multi lexer preference which does not have a DEFAULT sub lexer defined

Cause: you tried to specify an alt value which is already in use by another sub lexer in the lexer preference

Cause: you tried to create an index using a multi lexer preference, but you did not specify a language column

Cause: you specified a language column which is not a char, varchar, or varchar2 type.

Cause: you tried to define a language independent DEFAULT sub lexer

Cause: there are documents in the base table with language column value set to symbol for sublexer or stopword being removed

Cause: cannot add a sub_lexer more than once

Cause: you attempted to invoke a partition-level operation on an index which is not partitioned

Cause: you specified a partition name which does not exist

Cause: you attempted to invoke a partition-level operation on a partitioned index but did not specify the partition name

Cause: you attempted to perform an exchange partition including indexes, but one or more of the internal index tables are partitioned.

Cause: you attempted to perform an exchange partition including indexes, but the specified metadata setting is not equivalent across the two indexes, so the data cannot be exchanged

Cause: failed to load a dictionary file

Cause: Using lexer type KOREAN_LEXER which is desupported.

Cause: size of the document being indexed is larger than the maximum supported size for the VARCHAR2 interface of stored procedure

Cause: token data returned by the user-defined lexer procedure is incorrect

Cause: number of wildcard offsets specified as value for the wildcard attribute does not meet the supported range

Cause: value of pre-normalized wildcard offset or post-normalized wildcard offset specified as value for the wildcard attribute does not meet the supported range

Cause: The wildcard attribute value specified the offset of a wildcard character. The character at the specified offset is neither the '%' character nor the '_' character.

Cause: value of 'off' attribute does not meet the supported range

Cause: value of 'len' attribute does not meet the supported range

Cause: value of 'off' attribute plus value of 'len' attribute is greater than the number of characters in the document

Cause: the query contains an ABOUT operator while using USER_LEXER lexer type

Cause: USER_LEXER does not support this operation

Cause: user CTXSYS did not grant EXECUTE privilege on USER_LEXER stored procedure to the index owner

Cause: the procedure name contains a semicolon character

Cause: CTXSYS does not have EXECUTE privilege on the USER_LEXER stored procedure

Cause: The function you used depends on Oracle Data Mining, which has not been installed yet.

Cause: the type you have specified is not supported

Cause: Wrong syntax for parameter_string.

Cause: A shadow index was previously created already

Cause: Specify NOPOPULATE in parameter_string in recreate_index_online

Cause: Specify POPULATE for a local index during create_shadow_index

Cause: Tried to perform exchange shadow without creating shadow index first

Cause: Wrong syntax for parameter_string

Cause: Tried to perform exchange shadow part without creating shadow part first

Cause: Specified SWAP and NOPOUPLATE in parameter string

Cause: try to swap an local partitioned index when not all partitions are swapped

Cause: an error occurred during the shadow index swap

Cause: Tried to perform exchange shadow without creating shadow index first

Cause: The result set descriptor has a syntax error

Cause: The order attibute has a syntax error

Cause: The number string is malformed

Cause: Too many sort keys are specified

Cause: Too many select items are specified

Cause: Too many group tags are specified

Cause: start_hit_num is not specified or out of valid range

Cause: end_hit_num is not specified or out of valid range

Cause: Temporary lob is not allocated for ctx_query.result_set_document

Cause: No query is specified and result set descriptor has invalid elements

Cause: MVDATA group values not specified in RSI

Cause: MVDATA group values not specified in RSI

Cause: Path element not specified for the ctx_tree element

Cause: index name not specified in the API

Cause: result set interface not supported with security policies

Cause: More than one snippet element specified with result set interface

Cause: Cannot use group values and topn for the same group counting

Cause: Cannot use topn less than or equal to zero

Cause: Cannot do group count for facets with no data

Cause: Invalid value provided for sortby criteria in result set interface

Cause: Invalid value provided for order criteria in result set interface

Cause: Group Count element specified more than once for group

Cause: An unsupported attribute value was specified for the 'bucketby' attribute.

Cause: The 'bucketby' attribute must be specified for SDATA group.

Cause: An unsupported attribute value was specified for a 'collocates' attribute.

Cause: There was more than one sentiment element in the query.

Cause: There were too many item elements in the sentiment query.

Cause: There was an unsupported attribute value specified for the item attribute.

Cause: An unsupported attribute value was specified for the 'sortby' attribute.

Cause: An unsupported attribute value was specified for the 'order' attribute.

Cause: The 'bucketby' attribute applies to 'searchable' SDATA sections only.

Cause: Empty queries are supported with 'bucketby' range.

Cause: An unsupported lexer was specified for 'collocates'.

Cause: Internal error processing the 'collocates' element.

Cause: The Extraction Rule descriptor has a syntax error

Cause: rule_id is NULL or rule_id <= 0

Cause: No rule for given rule_id

Cause: An invalid entity type was specified

Cause: An invalid entity type list was specified

Cause: Using a non-extraction policy

Cause: Using an entity extraction policy

Cause: A user rule has an error

Cause: The user dictionary has an error

Cause: Unsupported Language Specified

Cause: Syntax error in dictionary

Cause: Tried to remove a non-existent stop entity

Cause: Tried to load a 2nd user dictionary to a policy

Cause: No user dictionary loaded for this policy

Cause: Trying to load a duplicate uncompiled stop entity

Cause: Trying to load a stop entity with null name and type

Cause: Haven't loaded correct event

Cause: A entry or alternate form has null value

Cause: An entry was not given an entity type

Cause: Tried to run ctxload with file and drop

Cause: Tried to re-drop a stop entity

Cause: Duplicate type on typelist

Cause: Backreference not between 1 and 10

Cause: Unsupported Attribute

Cause: Unsupported attribute value

Cause: Type name more than 30 bytes

Cause: Unsupported Tag

Cause: Missing Necessary Tag

Cause: Missing Necessary Attribute

Cause: The given MVDATA section name does not exist in USER_SECTIONS

Cause: The given literal is not compatible with the data type of the specified MVDATA section.

Cause: failed to convert data

Cause: failed to convert data

Cause: failed to create data

Cause: failed to create data

Cause: The path specified in ctx_tree.add_node() adds the node with the same name in the same tree at the same level

Cause: failed to lookup input node

Cause: path is empty

Cause: Big_io option not specified for MVDATA index

Cause: MVDATA section not specified for ctx_tree usage

Cause: The path specified in ctx_tree.add_node() is invalid.

Cause: Index-level big_io was not specified

Cause: Filter Section contains non-unique values

Cause: Only one Filter Section allowed in a Section Group

Cause: Big_io option not specified for Filter Section index

Cause: Auto_Optimize Process is already started

Cause: Auto_Optimize works on indexes with stage_itab

Cause: Index/Partition already added to auto_optimize list

Cause: Index/Partition not on the auto_optimize list

Cause: Index/Partition is using max_rows to merge

Cause: Index/Partition is using auto optimization

Cause: The requested memoery size is larger than page size,

Cause: detect a CORE LSF error

Cause: detect a CORE LEM error while reading the error stack

Cause: could not obtain database compatibility setting

Cause: Third-party filter could not filter this document because of an internal error.

Cause: internal database error or internal Text error

Cause: database error or internal Text error

Cause: database error or internal Text error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: Internal error, probably result of large number of indexed words

Cause: Internal error

Cause: Index validation generated an error for one or more tokens

Cause: Index validation generated an error for one or more tokens

Cause: you specified an illegal classifier

Cause: the classifier preference is not specified

Cause: you specified RULE_CLASSIFIER

Cause: you spcified an unsupported classification method

Cause: the column datatype is invalid

Cause: A sentiment label other than 0, 1 or 2 was present in the training table.

Cause: An internal check-condition has been violated

Cause: A fatal error has occurred

Cause: Bad operation code was encountered (reached switch default:)

Cause: internal error, probably a bug

Cause: internal error, probably a bug

Cause: internal error, probably a bug

Cause: internal error, probably a bug

Cause: internal error from inxight lexer

Cause: internal error

Cause: internal error

Cause: internal error

Cause: Third-party auto lexer could not complete tokenization because the lexer timed out.

Cause: internal error

Cause: internal error

Cause: internal error

Cause: this is an internal error

Cause: this is an internal error

Cause: this is an internal error in a testing function

Cause: this is an internal error

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

Cause: Too many cursors open for internal queries

Cause: parse error on an internal query

Cause: bind error on an internal query

Cause: define error on an internal query

Cause: exec error on an internal query

Cause: cursor close error on an internal query

Cause: transaction rollback error

Cause: internal error

Cause: This is an oracle error

Cause: failed to execute a sql statement

Cause: internal error,

Cause: fetch error on an internal query

Cause: Fail to logoff from the database

Cause: this is an informational message

Cause: a generic OCI error occurred

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: This is an internal error

Cause: bad query

Cause: bad query

Cause: bad query

Cause: invalid weight

Cause: invalid weight

Cause: invalid score threshold

Cause: invalid score threshold

Cause: invalid score threshold

Cause: invalid maximum number of documents

Cause: invalid maximum number of documents

Cause: invalid maximum number of documents

Cause: invalid first document number

Cause: invalid first document number

Cause: invalid first document number

Cause: invalid last document number

Cause: invalid last document number

Cause: invalid last document number

Cause: unbalanced escape characters

Cause: no matching open escape character for close escape

Cause: invalid operand type for NEAR operator

Cause: invalid type of expression which is part of phrase

Cause: invalid operand type for EQUIV operator

Cause: PL/SQL function may not exist or is returning bad value

Cause: parser internal

Cause: PL/SQL function call returned another PL/SQL call

Cause: string returned by PL/SQL function could not be parsed

Cause: query string empty or made up of invalid characters

Cause: bug

Cause: bug

Cause: bug

Cause: memory allocation or freeing error

Cause: bug

Cause: bug

Cause: bug

Cause: bug

Cause: bug

Cause: bug

Cause: query is too complex for our query evaluator

Cause: internal coding mistake

Cause: bug

Cause: bug