Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
Cause: Error during read of specified text column.
Action: Check existence and privs of column.
Cause: Specified table does not exist or server does not have write privileges.
Cause: Text server is not privileged to insert, tablespace exhausted.
Action: Check privileges and tablespace.
Cause: Error during read of specified text column.
Action: Check existence and privs of column.
Cause: Specified table does not exist or server does not have write privileges.
Cause: Text server is not privileged to insert, tablespace exhausted, or the document is too large.
Action: Check privileges, tablespace, or document size.
Cause: Error during read of specified highlight column.
Action: Check existence and privs of column.
Cause: Specified table does not exist or server does not have write privileges.
Cause: ConText server is not privileged to insert, tablespace exhausted.
Action: Check privileges and tablespace.
Cause: You tried to use a result table in another schema.
Action: Create the result table in your own schema.
Cause: Specified table does not contain one or more of the following columns: TEXTKEY, SCORE, CONID, CURID.
Action: Check columns result table.
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.
Cause: Callback does not exist or you do not have execute permission.
Action: Check callback parameter.
Cause: User doesn't have privilege to store a system SQE.
Cause: User doesn't have privilege to remove a system SQE.
Cause: User doesn't have OS privilege to access file or file does not exist.
Action: Check file exists at specified location with proper access permission.
Cause: Invalid command argument was specified.
Action: Check the documentation for the legal arguments and re-execute the command.
Cause: This argument requires value(s).
Action: Re-execute the command with the correct argument value(s).
Cause: This argument is mandatory.
Action: Re-execute the command and specify the argument.
Cause: The specification for the server personality mask is invalid.
Action: Check the documentation and specify the correct mask.
Cause: Loading of the dictionary into cache failed, the dictionary may be in the inconsistent state.
Action: Run the dictionary QA report, contact Oracle Support with the QA report.
Cause: The server failed to register itself with the data dictionary.
Action: Look at the next error on the stack.
Cause: Update was called with the name of a server that does not exist.
Action: Correct the name of the server.
Cause: The attempt to update the server failed.
Action: Look at the next error on the stack.
Cause: The attempt to deregister the server from the data dictionary failed.
Action: Look at the next error on the stack.
Cause: The named queue does not exist or the new status is inappropriate for its present status.
Action: Ensure that the queue name and the status specified are correct.
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.
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.
Action: Check if any servers are running to process the command.
Cause: There was an unexpected error sending command(s) to ConText server.
Action: Contact Oracle support.
Cause: Could not send command to pipe, because the pipe was full.
Action: Check if any ConText servers are running to process the commands on that pipe.
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.
Action: If the server terminated had an internal error, contact support.
Cause: Could not process command because no ConText servers are running with the correct personality mask.
Action: Start some ConText servers with correct personality mask.
Cause: Could not process command because no ConText servers are running with the correct personality mask.
Action: Start one or more ConText servers with correct personality mask.
Cause: Could not process parallel command because not enough ConText servers with the correct personality mask are running.
Action: Start enough ConText servers with correct personality mask to support the degree of parallelism requested.
Cause: The command could not be completed because the ConText servers were shut down or terminated before processing the request.
Action: Start another ConText server with the correct personality mask.
Cause: Failed to create text index on the specified column.
Action: See the next errors on stack and take appropriate action.
Cause: Policy name must be specified for this procedure call.
Action: Reinvoke the procedure and specify the policy name.
Cause: The specified policy does not exist or you do not have access to it.
Action: Must first create the column policy.
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.
Action: Create a suitable textkey for the table or specify it explicitly in this procedure call.
Cause: The preference id for the corresponding framework object is invalid.
Action: Reinvoke the operation with the correct preference id.
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.
Cause: The specified policy already exists in the dictionary.
Action: This policy can be updated or deleted, however this is only allowed if there is no text index available on the text column.
Cause: This procedure is not implemented currently.
Action: Use an alternative procedure to achieve same result or call support.
Cause: The column specified is not valid.
Action: Check that the followings are valid: a) text column is of the datatype supported by ConText, b) valid table name, column name in the specification
Cause: The textkey specified is not a column of the text table or its length exceeds 64 bytes.
Action: Check the specified textkey.
Cause: Index has not been created for this policy.
Action: Create index before performing this operation.
Cause: The dictionary cache is full.
Action: Increase the DICT_CACHE_SIZE configuration parameter and restart the server.
Cause: Dictionary contains bad preferences for this policy.
Cause: The preference name specified does not exists.
Action: Retry with the correct preference name.
Cause: The preference name is referenced by one or more policy.
Action: Drop the policy before the preference can be deleted.
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.
Cause: Failed to perform the operation because index exists on the column.
Action: Drop index if you really want to carry out the 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 policy
Cause: At most one process at a time can optimize an index, and another session is optimizing this index.
Action: You could try again later; however, when the index has been optimized, it is probably not necessary to optimize it again.
Cause: The drop operation requested has failed because of an Oracle error.
Action: See the Oracle error on the stack and take the appropriate action.
Cause: Other session is operating on the index.
Cause: You encountered an internal error.
Action: Contact Oracle support.
Cause: The specified policy already exists.
Action: Must drop the policy if you want to re-create it.
Cause: The table name has not been specified in the policy name specification.
Action: If you want to create a template policy, use 'TEMPLATE_POLICY' as the table name. The syntax for policy name specification is '[owner.[table.]]column'.
Cause: A textkey needs to be a single column unique key whose length does not exceed 64 bytes (for a master-detail table a 2 column unique key is needed); no suitable candidate textkeys found.
Action: Create a suitable textkey via an unique index or primary or unique key constraints.
Cause: You tried to index an object that isn't a TABLE, VIEW, or SYNONYM.
Action: Do not try to index this object.
Cause: You tried to index using unsupported indexing level.
Action: Check your preference settings.
Cause: You tried to create a policy on the table that has illegal textkey datatype.
Action: Change the textkey to one of the followings: VARCHAR2, NUMBER, VARCHAR, DATE, CHAR, MLSLABEL
Cause: You tried to set value for a invalid attribute (not supported by the object.
Action: Specify the correct attribute name.
Cause: You tried to set an illegal value for an attribute.
Action: Specify the correct attribute value for the datatype of the attribute.
Cause: You called CREATE_INDEX with parallel = 0.
Cause: You called CONTAINS with sharelevel set to a value other than 1 or 0.
Action: Specify a value of 1 or 0.
Cause: You specified a user name that is invalid.
Action: Specify the correct user name.
Cause: You tried to create an index that already exists.
Cause: The optimize operation requested has failed because of an Oracle error.
Action: See the Oracle error on the stack and take the appropriate action.
Cause: The owner specified in the policy name differs from the owner in the column specification - defaults are the current user.
Action: Reinvoke the procedure with modified policy name or column spec.
Cause: A textkey needs to be a single column unique key whose length does not exceed 64 bytes (for a master-detail table a 2 column unique key is needed); no suitable candidate textkeys found.
Action: Create a suitable textkey via an unique index or primary or unique key constraints.
Cause: The preference attributes specified cause an invalid DDL statement to be generated.
Action: Check the server log which will contain the faulty SQL statement. Use that to correct the preference attributes for this policy.
Cause: The specified stop word already exists.
Action: Must remove the duplicate word if you want to re-create it.
Cause: The specified stop word is null.
Action: Must remove the null stop word if you want to re-create it.
Cause: A stop list entry has exceeded the maximum length of 64 bytes.
Action: Reduce the length of the stop list entry if you want to re-create it.
Cause: Stop list entries have exceeded the maximum limit of 255.
Action: Limit the number of entries in stop list to 255, if you want to re-create it.
Cause: You tried to create a preference with an invalid object type.
Action: Use a valid framework object to create the preference.
Cause: You tried to create a policy for another user.
Action: Datasource owner or CTXSYS should create policy.
Cause: The specified preference already exists.
Action: Must drop the preference if you want to re-create it.
Cause: User name has exceeded the maximum length of 30 bytes.
Action: Reduce the length of the user name if you want to re-create it.
Cause: Object name has exceeded the maximum length of 30 bytes.
Action: Reduce the length of the object name if you want to re-create it.
Cause: Policy or preference may have additional periods(.).
Action: Check the syntax of preference or policy name if you want to re-create it.
Cause: Table name has exceeded the maximum length of 30 bytes.
Action: Reduce the length of the user name if you want to re-create it.
Cause: Column name has exceeded the maximum length of 30 bytes.
Action: Reduce the length of the column name if you want to re-create it.
Cause: Column specification may have additional periods(.).
Action: Check the syntax of column specification if you want to re-create it.
Cause: Parallel Index Optimization is supported for 2-table compaction only.
Action: Run this option serially, or use the 2-table compaction option.
Cause: This is an internal error detected during parallel processing.
Action: Call Oracle support. Continue to use the original, unoptimized text index until the problem is resolved.
Cause: The option specified is not supported. Supported options are:
1. DR_OPTIMIZE_LAZY_DELETES or Garbage Collection
2. DR_OPTIMIZE_COMPACT_INDEXES or In-place compaction
3. DR_OPTIMIZE_COMPACT_NEW or 2-table compaction
Action: Specify one of the options listed above.
Cause: The datasource for a policy must be a table or a view. Creating policies against synonyms is not currently supported.
Cause: You tried to create a text index on a template policy.
Cause: When creating a policy with a view as the datasource, you must specify a column of the view to use as the primary key.
Cause: The lineno specified is not a column of the text table or its length exceeds 64 bytes.
Action: Check the specified lineno.
Cause: When creating a master-detail datasource, the lineno column of the detail table must be specified. The lineno column is unique among detail records of the same master record.
Action: Specify the lineno column in this procedure call.
Cause: When creating a policy which is not a master-detail datasource, you must not specify the lineno.
Action: Do not specify the lineno column in this procedure call.
Cause: A textkey for master-detail datasources needs to be a 2-column unique key. No such key was defined as a primary or unique key constraint.
Action: Create a suitable textkey for the table or specify it explicitly in this procedure call.
Cause: For master-detail datasources, the textkey column must be part of a 2-column unique composite key. The textkey column forms the major half, and the lineno forms the minor half.
Action: Check the specified textkey.
Cause: You specified too many values for the attribute.
Cause: You did not specify a mandatory attribute of the preference.
Action: Specify the mandatory attribute.
Cause: Duplicate policy or source id exists.
Action: Use ctx_ddl.create_policy or create_source.
Cause: The specified source does not exist or you do not have access to it.
Action: Must first create the source.
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.
Cause: You tried to create a preference for another user.
Action: Owner or CTXSYS or a user who has CTXADMIN. role should create preference
Cause: You specified an invalid object type.
Action: Use a valid framework object.
Cause: You specified an invalid framework class.
Action: Use a valid framework class.
Cause: The system could not setup triggers to monitor updates to the requested column.
Action: See next error on stack to determine course of action. Contact Oracle Support 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 remove triggers setup to monitor updates to the requested table.
Action: See next error on stack to determine course of action. Contact Oracle Support 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 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 do the sync.
Action: See next error on stack to determine course of action.
Cause: The system could not do the sync.
Action: See next error on stack to determine course of action.
Cause: The system could query the sync date.
Action: Contact Oracle Support.
Cause: The server was had an error accessing the DML Queue.
Action: See next error on stack.
Cause: The server apparently aborted while processing a batch of DML operations. The recovery mechanism attempted to requeue the primary keys that the aborted server was working on. However, the attempt to requeue these rows failed.
Action: See next error on stack.
Cause: Timeout occurred while waiting for the DML to complete.
Cause: Unrecognized preference parameter.
Action: Correct preference setting and resubmit.
Cause: Too many preference values.
Action: Adjust the number of values and resubmit.
Cause: Expecting more parameter values.
Action: Correct preference setting and resubmit.
Action: Correct preference setting and resubmit.
Cause: Parameter is out of range.
Action: Correct preference setting and resubmit.
Cause: Bad setting of a parameter, was set too default value.
Action: Correct preference setting and resubmit.
Cause: Parameter is too many bytes.
Action: Correct preference setting and resubmit.
Cause: The parameter, %(2)s, is in an enumerated domain, but its value is not valid for that domain.
Action: Correct preference setting and resubmit.
Cause: No character can be both a printjoin and a skipjoin. You tried to create a lexer preference where printjoins and skipjoins had characters in common.
Action: Correct the attribute values and resubmit.
Cause: Base-letter conversion is supported only for character sets of no more than 8 bits with base-letter form of no more than 8 bits.
Action: Disable base-letter conversion.
Cause: Failed to process the query.
Action: Check the errors on stack and take appropriate action.
Cause: Failed to process the contains part of the query.
Action: Check the errors on stack and take appropriate action.
Action: Balance the parenthesis.
Action: SELECT sub query missing required FROM clause.
Action: SELECT sub query has duplicate FROM clause.
Action: WHERE keyword must be inside a SELECT statement.
Action: More than 1 WHERE inside a SELECT.
Action: ORDER BY keyword must be inside a SELECT statement.
Action: More than 1 ORDER BY inside a select.
Action: ORDER BY keyword must be inside a select statement.
Action: More than 1 GROUP BY inside a SELECT.
Action: HAVING keyword must be inside a SELECT statement.
Action: More than 1 HAVING inside a SELECT.
Cause: The fuzzy match word must be at least 3 letters.
Action: Choose longer fuzzy match word.
Cause: See the next error on the stack.
Action: 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.
Action: Replace the stopword or use stopwords within phrases containing non-stopwords.
Cause: To use soundex in a query SOUNDEX_AT_INDEX must have been specified in the wordlist preference of the column policy.
Action: Remove soundex from the query or rebuild the column policy.
Cause: An error occurred while trying to open a contains cursor.
Action: See accompanying error messages in the stack.
Cause: You tried to fetch or close a contains cursor with an id which does not exist.
Action: Review fetch or close invocation.
Cause: You tried to fetch from a contains cursor which was not open.
Action: Remove soundex from the query or rebuild the column policy.
Cause: You tried to create a stored query with a name already used.
Cause: The query name specified is not valid.
Cause: The scope specified is not valid.
Action: Use SYSTEM or SESSION.
Cause: The specified stored query does not exist or has been redefined.
Cause: There is no document with the specified textkey.
Cause: Can not allocate more memory.
Action: Contact your system administrator.
Cause: Contact Oracle Support.
Action: Contact Oracle Support.
Cause: Failed to connect to Oracle database.
Action: Check the Oracle error and connect string.
Action: Check whether the file exist or access permission available.
Cause: Single byte lexer selected in multibyte language setting.
Action: Check RDBMS language setting or text columns lexer setting.
Cause: See the next error on stack.
Action: See the next error on stack.
Cause: Failed to display rows.
Action: Check the errors on stack and take appropriate action.
Cause: This database session does not exist or has terminated.
Action: Determine why the user database session terminated while ConText operation was still being carried out.
Cause: The path specified is not valid.
Action: Check the path specification.
Cause: The filename specified is not valid.
Action: Check the filename for beginning or trailing spaces, invalid characters, or other such problems.
Cause: This lexer does not support this query operator.
Action: Do not use the operator in your query.
Cause: A MasterSoft blaster filter failed.
Action: Lookup the meaning of the blaster status code, and rectify that problem.
The codes have the following meanings:
1 Error opening user file name
2 Error during read operation
3 Error opening conversion file
4 Error during write operation
5 Invalid data in conversion file
6 Error opening exception file
7 Error writing exception file
8 Error obtaining memory
9 Error invalid document
10 Error out of space on output
11 Conversion doc to big for tgt
12 Warning on conversion
13 Conversion cancelled
14 Invalid parameters on com line
15 File stored encrypted
16 Converter encountered fatal err
17 Lseek failed
Cause: This policy specifies that the filter must automatically recognize the format of documents. This document does not conform to any format known to the filter.
Action: Contact Oracle support.
Cause: The format number specified is invalid.
Action: Check the format number.
Cause: The autorecognizer recognized this format, but it is not yet supported by the filter.
Action: Check document format.
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.
Action: Check that the command exists in $ORACLE_HOME/ctx/bin, and that it is executable.
Cause: The user filter command exited with the given error status.
Cause: ORACLE_HOME is not set.
Action: Make sure ORACLE_HOME is set when running ctxsrv.
Cause: The filter does not support markup.
Cause: The filter does not support ICF.
Cause: The executable for the specified format already registered.
Action: Must remove the duplicate format if you want to re-create it.
Cause: No value specified for format id.
Action: Must provide format id if you want to re-create it.
Cause: You did not provide an executable name.
Action: Must provide executable name if you want to re-create it.
Cause: No user-defined filter or Blaster filter available for this format.
Action: Register a user-defined filter for this format.
Cause: A user-defined filter was used for this document.
Cause: Only one attribute is allowed to be set for this Tile.
Cause: Couldn't parse or translate SELECT statement.
Action: Check further messages for the cause of the error.
Cause: There is not enough space to hold the translated query.
Action: Reduce the length of the query to be translated.
Cause: The second argument of the contains() function must be a string.
Action: Check the contains() function syntax.
Cause: This contains() label has already been specified.
Action: Make sure the contains() labels are unique.
Cause: The numeric limit for a contains label has been exceeded.
Action: Make sure all the labels are within the documented limits.
Cause: The label in a score() function does not have a matching contains().
Action: Make sure all the labels referenced are defined.
Cause: There are no indexing policies defined for this column.
Action: Create a policy and index on this column.
Cause: The syntax of the contains() function is not valid.
Action: Check the contains() function syntax.
Cause: The syntax of the score() function is not valid.
Action: Check the score() function syntax.
Cause: The syntax of the handle() function is not valid.
Action: Check the handle() function syntax.
Cause: The replacement of a portion of the rewritten statement has failed.
Action: Check further messages for the cause of the error.
Cause: One of the contains() in the query couldn't be executed.
Action: Check further messages for the cause of the error.
Cause: Couldn't execute a translated query.
Action: Check further messages for the cause of the error.
Cause: The contains() function is allowed only in a WHERE clause
Action: Reformulate the query.
Cause: The score() function is not allowed in a FROM clause.
Action: Reformulate the query.
Cause: The handle() function is allowed only in a SELECT list.
Action: Reformulate the query.
Cause: A valid identifier must be specified after a colon.
Action: Make sure all the identifiers are valid.
Cause: A syntax error was detected while parsing a select list.
Action: Check further messages for the cause of the error.
Cause: A syntax error was detected while parsing a FROM clause.
Action: Check further messages for the cause of the error.
Cause: A syntax error was detected while parsing a WHERE clause.
Action: Check further messages for the cause of the error.
Cause: Queries which use tree traversal clauses are not supported.
Action: Do not use contains().
Cause: A syntax error was detected while parsing an ORDER BY clause.
Action: Check further messages for the cause of the error.
Cause: A syntax error was detected while parsing a GROUP BY clause.
Action: Check further messages for the cause of the error.
Cause: A syntax error was detected while parsing outside a SELECT clause.
Action: Check further messages for the cause of the error.
Cause: An error occurred in an undefined parsing state.
Action: Contact Oracle Support.
Cause: You encountered an internal error.
Action: Contact Oracle Support.
Cause: Couldn't remove the information for a query from the dr$contains or dr$bind tables.
Action: Check that the query and session identifiers correspond to a query which has been executed.
Cause: A column name used in a text function exists and has an indexing policy in more than one table. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN.
Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias, and a period (.), as in the examples above.
Cause: Couldn't save a translated query.
Action: Check further messages for the cause of the error.
Cause: This mode of operation is not implemented.
Action: Use query or contains specific result table sharing levels.
Cause: Maximum number of tables reached or other Oracle error.
Action: Drop result tables for sessions which are no longer active.
Cause: The document specified for linguistic extraction could not be parsed. This could indicate that the document is not well-formed English.
Action: Check the document contents.
Cause: The policy name parameter passed to the service request is longer than the maximum policy name size.
Action: Check policy parameter.
Cause: The result table name parameter passed to the service request is longer than the maximum table name size.
Action: Check result table parameter.
Cause: The primary key value parameter passed to the service request is longer than the maximum primary key length (64 bytes).
Action: Check primary key parameter.
Cause: The primary key value parameter passed to the service request is null.
Action: Check primary key parameter.
Cause: The timeout duration parameter passed to the service request is negative. Timeout duration must be a positive number.
Action: Check timeout duration parameter.
Cause: There are no pending requests to submit.
Cause: The result table specified is missing an expected column, or those columns are not the correct type or length.
Action: Check the names and types of the columns of the result table. The columns must include CID (NUMBER), PK (VARCHAR2(64)), THEME (VARCHAR2(2000)), and WEIGHT (NUMBER).
Cause: The result table specified is missing an expected column, or those columns are not the correct type or length.
Action: Check the names and types of the columns of the result table. The columns must include CID (NUMBER), PK (VARCHAR2(64)), CATALOG (VARCHAR2(2000)), and WEIGHT (NUMBER).
Cause: The result table specified is missing an expected column, or those columns are not the correct type or length.
Action: Check the names and types of the columns of the result table. The columns must include CID (NUMBER), PK (VARCHAR2(64)), POV (VARCHAR2(256)), and GIST (LONG).
Cause: An ORACLE error occurred while linguistic output was being inserted into the result table.
Action: Take action appropriate to the ORACLE error code.
Cause: The document specified for a service request does not exist.
Action: Check the service request and the datasource to insure that the requested document exists with the correct primary key value.
Cause: There are pending requests which must be submitted before new requests are sent.
Action: Submit or cancel the pending requests.
Cause: An invalid request handle was specified.
Action: Check the request handle.
Cause: The request is already running on a server, the request handle is invalid, or it is not your request.
Cause: The callback does not exist or the requestor does not have EXECUTE permission for this procedure.
Cause: The ConText server which was processing this service request terminated before finishing processing.
Cause: The document specified for linguistic extraction was parsed, but not with a high level of confidence using the specified parser.
Action: Check the document contents or try modifying linguistic settings
Cause: The document specified for linguistic extraction was parsed but the document content was insufficient for linguistic extraction by the specified parser.
Action: Check the document contents or try modifying linguistic settings.
Cause: You specified a priority which was not between 1 and 10.
Action: Change the priority value specified.
Cause: You specified an invalid settings label.
Action: Change the settings label specified.
Cause: You tried to the L personality with a non-linguistic server.
Action: Use the full ConText server.
Cause: Linguistic services initialization failed -- possibly out of memory.
Cause: The load file terminated before current record end.
Action: Check record and keywords at end of load file.
Cause: Possibly misspelled column name or keyword.
Action: Check spellings and punctuation around specified line.
Cause: Possibly misspelled column name.
Action: Check spellings around specified line.
Cause: Bad file name, wrong file_type or file system error.
Action: Check file name, type, and/or file integrity.
Cause: Long value reached end of load buffer.
Action: Check length of inserted data for current table.
Cause: Long buffer length insufficient for long data length.
Action: Increase longsize parameter.
Cause: Total length of statement exceeds database maximum.
Action: Reduce length of column names or number of columns.
Cause: Invalid option argument.
Action: Specify long buffer size in kbytes above 0.
Cause: Either bad data or bad data file.
Action: Check file exists and is accessible, if separate.
Cause: An error occurred parsing this row's data.
Action: Move and amend line in error to alternate load file.
Cause: Separate file not found or could not be read.
Action: Check name and location of separate file.
Cause: Token expected was not found.
Action: Move and amend record affected to error load file.
Cause: Could not make sense of text where value expected.
Action: Move and amend record affected to error load file.
Cause: Could be misplaced or misspelled.
Action: Processing discontinued - amend record.
Cause: Data too long for column.
Action: Correct data length for insertion.
Cause: Specified file could not be found.
Action: Check name, location, permissions, and type of load file.
Cause: Text must be inserted into a LONG or LONG RAW type column.
Action: Check table name and table definition.
Cause: Load file must have specific format for loading thesaurus.
Action: Check documentation for description of correct format.
Cause: Encountered a phrase longer than maximum allowed length.
Action: Use a shorter phrase on the indicated line.
Cause: An attempt to open or to write to the given file failed.
Action: Check with system administrator.
Cause: Thesaurus for export could not be found.
Action: Check spelling of thesaurus name.
Cause: The document referred to by the URL has permanently moved.
Action: Find the new address, if any, of the document.
Cause: Client did not make correct request.
Action: Contact ConText Group at Oracle.
Cause: User has to provide password or other authentication.
Action: Get required access, or check URL.
Cause: Payment is required before the URL can be accessed
Action: Check URL, or pay if required if access necessary
Cause: Access to the URL is denied.
Action: Check URL; if correct, do not try to access URL again.
Cause: The document can not be found on the host specified.
Cause: Client did not make response within timeout period.
Action: Contact ConText Group at Oracle.
Cause: Web server identified in URL doesn't obey HTTP protocol.
Action: Contact the Web administrator of the remote host.
Cause: Host portion of the URL could not be parsed.
Cause: Attempt to open local file failed.
Cause: Attempt to read local file failed.
Action: Contact system administrator.
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.
Action: Try again later; network connection may be down to Web server.
Cause: Unknown error writing request to Web server.
Action: Check network connection.
Cause: Too long a chain of HTTP redirections given the URL.
Action: Contact the Web administrator of the remote host.
Cause: The length of the URL string is longer than URLSIZE.
Action: Set URLSIZE attribute to a larger value.
Cause: Document larger than user-set maximum size.
Action: Do not access URL, or increase document size limit.
Cause: Row deleted or otherwise missing.
Action: Check table if necessary.
Cause: Thread operation failed.
Action: Contact system administrator.
Cause: Socket open failed; probably too many open file descriptors.
Action: Reduce the maximum number of threads started.
Cause: HTTP error has occurred which ConText doesn't catch.
Action: Consult HTTP error codes; if valid, contact ConText Group at Oracle.
Cause: Error has occurred which ConText doesn't catch.
Action: Contact ConText Group at Oracle.
Cause: Error has occurred which ConText doesn't catch.
Action: Contact ConText Group at Oracle.
Cause: Thesaurus with same name exists.
Cause: Thesaurus does not exist.
Action: Use another thesaurus or create it.
Cause: Error while parsing thesaurus operator in query term. See error message for details.
Cause: Privilege is not sufficient.
Action: Grant CTXAPP role to user.
Action: Use another phrase or create it.
Cause: Source name is not provided.
Action: Provide a source name.
Cause: Duplicate source name for the same user.
Action: Use another source name.
Cause: User does not have CTXAPP role.
Action: Grant CTXAPP role to user or create source as CTXSYS.
Cause: CTXAPP cannot create source for other users.
Action: CTXAPP can only create source for itself.
Cause: Oracle error encountered.
Action: Look at the Oracle error and take appropriate action.
Cause: Table owner is not the same as source owner.
Action: Specify the correct source owner or table owner.
Cause: Bin name is not provided.
Cause: Parent bin does not exist.
Action: Create the parent bin or provide a valid parent bin.
Cause: Bin with same name exists.
Action: Provide a different bin name.
Action: Provide an existing bin name.
Cause: An attempt was made to remove a non-existent query.
Action: Check query, policy names.
Cause: Position is less than 1 or greater than number of children.
Action: Check reordering list.
Cause: Bins are not all siblings.
Action: Check parent names of bins.
Cause: Reordering list has duplicate positions.
Action: Check reordering list.
Cause: Weight factor is in the wrong range.
Action: Adjust the weight factor.
Action: Check lexer specified.
Cause: User doesn't have necessary permissions.
Cause: Sibling bin name provided does not exist.
Cause: And group id for bin query must be positive.
Cause: Bin names indicating insertion point for peer bin are invalid.
Action: Check bin names, and make sure they are contiguous.
Cause: Allowing reparent operation will result in a cycle in the tree.
Action: Check parent bin id and the structure of the bin tree.
Cause: ctx_bin.get_id was called with an invalid path.
Action: Check path and the structure of the bin tree.
Cause: All the immediate children of a common parent must have unique names.
Cause: The user translator command must be 32 characters or less.
Cause: The user translator command cannot contain special characters such as slashes, parentheses, semicolons, etc.
Cause: The user translator command could not be executed.
Action: Check that the command exists in $ORACLE_HOME/ctx/bin, and that it is executable.
Cause: The user translator command exited with the given error status.
Cause: ORACLE_HOME is not set.
Action: Make sure ORACLE_HOME is set when running ctxsrv.
Cause: The user translator failed to translate the given file.
Action: Examine the log file for what command was executed.
Cause: A temporary filename could not be generated by the translator.
Action: Contact Oracle Support.
Cause: The translator object failed.
Action: If cause not apparent, contact Oracle Support.
Cause: The reader skipped this file because it could not be processed.
Action: Examine that the file and the translator are in good order.
