CHAPTER 1. ConText Option User Messages
This chapter provides a list of the user errors you may receive while performing ConText Option operations, as well as an explanation of each error.
The errors are presented in numerical order, grouped according to type.
10000--10099: Access Control
DRG--10000 failed to read column %(1)s.%(2)s
| Cause: | Error occurred during read of specified text column. | |
| Action: | Check existence and privileges of column. | |
DRG--10001 can not access result table %(1)s
| Cause: | Specified table does not exist or server does not have write privileges. | |
| Action: | Check result table. | |
DRG--10002 can not insert into result table
| Cause: | Text server is not privileged to insert, tablespace exhausted. | |
| Action: | Check privileges and tablespace. | |
DRG--10003 failed to read column %(1)s.%(2)s
| Cause: | Error during read of specified text column. | |
| Action: | Check existence and privileges of column. | |
DRG--10004 can not access document table %(1)s
| Cause: | Specified table does not exist or server does not have write privileges. | |
| Action: | Check document table. | |
DRG--10005 can not insert into document table
| Cause: | ConText server is not privileged to insert, tablespace exhausted, or the document is too large. | |
| Action: | Check privileges, tablespace, or document size. | |
DRG--10006 failed to read column %(1)s.%(2)s
| Cause: | Error during read of specified highlight column. | |
| Action: | Check existence and privileges of column. | |
DRG--10007 can not access highlight table %(1)s
| Cause: | Specified table does not exist or server does not have write privileges. | |
| Action: | Check document table. | |
DRG--10008 can not insert into highlight table
| Cause: | ConText server is not privileged to insert, tablespace exhausted. | |
| Action: | Check privileges and tablespace. | |
DRG--10009 not allowed to access a table in another schema
| Cause: | You tried to use a result table in another user's schema. | |
| Action: | Create a result table in your own schema. | |
DRG--10010 required column does not exist in result table %(1)s
| Cause: | Specified table does not contain one or more of the following columns: TEXTKEY, SCORE, CONID, CURID. | |
| Action: | Check that the result table contains the required columns. | |
DRG--10011 invalid table or procedure name %(1)s
| Cause: | The specified table, column, or procedure name has an invalid format; the name is either too long or contains illegal characters. The error is probably caused by passing incorrect parameters. | |
| Action: | Check parameter values. | |
DRG--10012 can not execute callback %(1)s
| Cause: | The specified callback routine does not exist or you do not have execute permission on the routine. | |
| Action: | Check callback parameter. | |
DRG--10013 can not store system stored query
| Cause: | User doesn't have privilege to store system SQE. | |
| Action: | No action required. Only the table/view owner or users with the CTXADMIN role can store system SQEs for a text column in a table/view. | |
DRG--10014 can not remove system stored query
| Cause: | User doesn't have privilege to remove a system SQE. | |
| Action: | No action required. Only the table/view owner or users with the CTXADMIN role can delete system SQEs for a text column in a table/view. | |
10100--10199: Argument Processing
DRG--10100 invalid argument found: %(1)s\n
| Cause: | An invalid command argument was specified. | |
| Action: | Check the documentation for the legal arguments and re-execute the command. | |
DRG--10101 no value for argument: %(1)s\n
| Cause: | The specified argument requires value(s). | |
| Action: | Re-execute the command with the correct value(s) for the argument. | |
DRG--10102 mandatory argument missing: %(1)s\n
| Cause: | The specified argument is mandatory. | |
| Action: | Re-execute the command and specify the required argument. | |
10200--10299: Administration
DRG--10200 invalid server personality mask: %(1)s
| Cause: | The specification for the server personality mask is invalid. | |
| Action: | Check the documentation and specify a valid personality mask. | |
DRG--10201 loading of the Dictionary cache failed
| Cause: | The loading of the dictionary into cache failed, the dictionary may be in an inconsistent state. | |
| Action: | Run the dictionary QA report and contact Oracle Worldwide Support. | |
DRG--10202 server failed to register
| Cause: | The server failed to register itself with the data dictionary. | |
| Action: | Check the next error on the stack to determine cause of failure. | |
DRG--10203 server does not exist
| Cause: | Update was called with the name of a server that does not exist. | |
| Action: | Correct the name of the server. | |
DRG--10204 server update failed
| Cause: | The attempt to update the server failed. | |
| Action: | Check the next error on the stack to determine cause of failure. | |
DRG--10205 server deregister failed
| Cause: | The attempt to deregister the server from the data dictionary failed. | |
| Action: | Check the next error on the stack to determine cause of failure. | |
DRG--10206 update failed for queue %(1)s, status %(2)s
| Cause: | The specified queue does not exist or the new status specified is inappropriate for its present status | |
| Action: | Ensure that the queue name is correct and the status specified is valid. | |
10300--10399: Communication
DRG--10301 timed out waiting for responses from servers
| Cause: | Not enough servers are running to handle the current system load and a large backlog of commands has accumulated. This message may indicate that no servers are running or that an internal error occurred when one of the servers crashed. | |
| Action: | Check that enough servers are running and that they have the appropriate personality masks for the commands. For example, a DDL command might timeout if all the servers are setup to exclusively process Query commands. Also, check the server log files. | |
DRG--10302 interrupted waiting for responses from servers
| Cause: | A user interrupted the request before it was completed. | |
| Action: | Restart the request. | |
DRG--10303 could not queue given commands to be processed
| Cause: | The specified command or commands could not (all) be queued. This may indicate an extremely high system load, but it is more likely an internal error. | |
| Action: | Verify that ConText servers are running with the appropriate personality to process the command. | |
DRG--10304 unexpected error sending command(s) to ConText server
| Cause: | There was an unexpected error sending command(s) to ConText server. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--10305 pipe %(1)s is full
| Cause: | A command could not be sent to the specified pipe, because the pipe is full. | |
| Action: | Verify that ConText servers are running with the appropriate personality mask to process the commands on that pipe. | |
DRG--10306 server terminated unexpectedly while processing command
| 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 due to an internal error, contact Oracle Worldwide Support. | |
DRG--10307 no servers running
| Cause: | The command could not be processed because no ConText servers are running with the appropriate personality mask. | |
| Action: | Start ConText server(s) with appropriate personality mask(s). | |
DRG--10308 no server with the required %(1)s personality mask is running
| 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. | |
DRG--10309 insufficient %(1)s servers running for parallel %(2)s operation
| Cause: | Could not process parallel command because not enough ConText servers with the appropriate personality mask are running. | |
| Action: | Start enough ConText servers with appropriate personality mask to support the degree of parallelism requested. | |
DRG--10310 servers were shutdown before processing request
| 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. | |
10500--10599: DDL
DRG--10500 CREATE_INDEX failed: column spec %s
| Cause: | Failed to create text index for the specified column. | |
| Action: | Check the next errors on the stack to determine the reason for failure and take appropriate action. | |
DRG--10501 policy name must be specified
| Cause: | This procedure call requires a policy name as one of its arguments. | |
| Action: | Re-execute the procedure and specify a valid policy name. | |
DRG--10502 policy %(1)s does not exist
| Cause: | The specified policy does not exist or you do not have access to it. | |
| Action: | Check that the policy exists in your schema. If it doesn't exist, create a policy in your schema and re-execute the procedure. | |
DRG--10503 textkey must be specified -- table has no primary key
| 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. | |
DRG--10505 invalid preference id %(1)s for the %(2)s preference
| Cause: | The preference ID for the corresponding framework object is invalid. | |
| Action: | Re-execute the operation with the correct preference ID. | |
DRG--10506 table does not exist: %(1)s
| Cause: | The table, view, or synonym specified does not exist; or a permission problem occurred when reading the table. | |
| Action: | Re-execute the operation with the correct table, view, or synonym name. | |
DRG--10507 duplicate policy name: %(1)s
| Cause: | The specified policy already exists in the ConText data dictionary. | |
| Action: | Specify a different name for the policy you are creating or update/delete the existing policy. (Note: a policy can be updated/deleted only if a text index does not exist for the column in policy. | |
DRG--10508 procedure not yet implemented: %(1)s
| Cause: | This procedure is not currently implemented. | |
| Action: | Use an alternate procedure to achieve same result or contact Oracle Worldwide Support. | |
DRG--10509 invalid text column: %(1)s
| Cause: | The column specified is not valid. | |
| Action: | Check that the following conditions are met: | |
1) text column is a datatype supported by ConText Option
2) table name and column name are specified correctly
DRG--10510 textkey column %(1)s does not exist, is too long, or is not unique
| Cause: | The specified textkey is not a column of the text table or its length exceeds 64 bytes. | |
| Action: | Check the specified textkey. | |
DRG--10511 index does not exist for the specified policy
| Cause: | A text index has not been created for this policy. | |
| Action: | Create a text index for the policy before performing the operation. | |
DRG--10512 the dictionary cache is full
| Cause: | The memory allocated for the ConText data dictionary cache is exhausted. | |
| Action: | Increase the DICT_CACHE_SIZE configuration parameter and restart the server. | |
DRG--10513 load object preference failed: policy %(1)s
| Cause: | The ConText data dictionary contains invalid preferences for this policy. | |
| Action: | Contact your database administrator. | |
DRG--10514 preference does not exist: %(1)s
| Cause: | The specified preference does not exist. | |
| Action: | Re-execute with the correct preference name. | |
DRG--10515 preference in use, can not be deleted: %(1)s
| Cause: | The specified preference is referenced in one or more policies. | |
| Action: | Drop all policies that reference the preference before deleting the preference. | |
DRG--10516 failed to perform DDL operation due to an Oracle error
| Cause: | The requested DDL operation failed due to an Oracle error. | |
| Action: | Check the Oracle error on the stack to determine the cause of failure and take the appropriate action. | |
DRG--10517 cannot perform operation %(1)s because index exists for policy %(2)s
| Cause: | Requested operation failed because text index exists for the column. | |
| Action: | Drop the text index and re-execute the command to perform the operation. | |
DRG--10518 an operation is in progress which conflicts with %(1)s request
| Cause: | Another session is operating on this text index. Possible reasons for conflict include: | |
1) DML is requested, but DDL is in progress
2) DDL is requested, but DML is in progress
| Action: | Submit your request at a later time. | |
DRG--10519 this index is already being optimized
| Cause: | Only one process at a time can optimize an index and another session is currently optimizing this index. | |
| Action: | If the optimization type of the executing process is the same as type specified in the request, no action is necessary. If the types are different, the request should be resubmitted at a later time after the first optimization has completed. | |
DRG--10520 failed to drop text index: column policy=%(1)s
| Cause: | The drop index request failed due to an Oracle error. | |
| Action: | Check the Oracle error on the stack and take the appropriate action. | |
DRG--10521 failed to access the text index: column policy=%(1)s
| Cause: | Only one process at a time can modify a text index and another session is currently operating on the index. | |
| Action: | Submit the request at a later time. | |
DRG--10522 failed to release access to the text index: column policy=%(1)s
| Cause: | This is a system error. | |
| Action: | Contact Oracle customer support. | |
DRG--10523 policy %(1)s already exists
| Cause: | The specified policy already exists in the ConText data dictionary. | |
| Action: | First drop the policy if you want to re-create it. (Note: a policy can only be dropped if no text index exists for the policy.) | |
DRG--10524 table name is missing in the column specification
| Cause: | A table name has not been included in the column name for the policy specification. | |
| Action: | Table name is required for all policies except a template policy. To create a template policy, use 'TEMPLATE_POLICY' as the table name. The syntax for specification of a column name is '[owner.[table.]]column'. | |
DRG--10525 composite textkey not supported
| Cause: | Textkeys consisting of more than one column (or two columns in a master-detail table) are not supported in this release of ConText Option. A textkey must be a single column unique key whose length does not exceed 64 bytes (Note: a textkey in a master-detail table must be a 2 column unique key.) | |
| Action: | Create a suitable textkey via a unique index or primary or unique key constraints. | |
DRG--10526 cannot index object of type %(1)s
| Cause: | You tried to create a text index for a database object that isn't a TABLE, VIEW, or SYNONYM. ConText Option does not support text indexes for objects other than TABLES, VIEWS, or SYNONYMS. | |
| Action: | Re-execute request and specify a valid object. | |
DRG--10527 invalid indexing level %(1)
| Cause: | You attempted to create a text index using an unsupported indexing level. | |
| Action: | Check your preference settings. | |
DRG--10528 datatype of the textkey not supported
| Cause: | You attempted to create a policy on a table that has a textkey with an unsupported datatype. | |
| Action: | Change the textkey to one of the following supported datatypes: VARCHAR2, NUMBER, VARCHAR, DATE, CHAR, MLSLABEL | |
DRG--10529 invalid attribute name: object_name=%(1)s, attribute name=%(2)s
| Cause: | You attempted to set a value for an invalid attribute (not supported by the object). | |
| Action: | Specify the correct attribute name for the object. Consult the ConText Option documentation for a list of valid attributes. | |
DRG--10530 invalid attribute value: attribute name=%(1)s, attribute value=%(2)s
| Cause: | You attempted to set an invalid value for an attribute. | |
| Action: | Specify the correct attribute value for the datatype of the attribute. Consult the ConText Option documentation for a list of valid attribute values. | |
DRG--10531 parallel parameter must be > 0
| Cause: | An invalid parallel parameter has been specified. | |
| Action: | Specify a valid value for parallel. | |
DRG--10532 sharelevel parameter must be 1 or 0
| Cause: | An invalid sharelevel parameter value has been specified. | |
| Action: | Specify a value of 1 or 0 for sharelevel. | |
DRG--10533 invalid user name: %(1)s
| Cause: | An invalid user name has been specified. | |
| Action: | Specify a valid user name. | |
DRG--10534 index already exists
| Cause: | A text index cannot be created for the specified column because one already exists. | |
| Action: | No action necessary. | |
DRG--10535 failed to optimize text index: column policy=%(1)s
| Cause: | The requested optimize operation failed due to an Oracle error. | |
| Action: | Check the Oracle error on the stack and take the appropriate action. | |
DRG--10536 failed to create policy: policy owner differs from owner of table
| Cause: | The owner specified in the policy name differs from the owner in the column specification. Only the owner of a table can create a policy for a column in the table. The default owner of a policy is the current user. | |
| Action: | Re-execute the procedure with a modified policy name or column specification. | |
DRG--10537 textkey %(1)s's length of %(2)s exceeds limit
| Cause: | The textkey for this table exceeds the system limit. A textkey must be a single column unique key whose length does not exceed 64 bytes. (Note: a textkey in a master-detail table must be a 2 column unique key). | |
| Action: | Create a suitable textkey using either a unique index or primary or unique key constraints. | |
DRG--10538 unable to create text index %(1)s %(2)s
| Cause: | The preference attributes for the specified policy caused an invalid DDL statement to be generated. | |
| Action: | Check the server log which to determine the faulty SQL statement and correct the preference attributes for the specified policy. | |
DRG--10539 stop Word %(1)s already exists
| Cause: | The specified stop word already exists in the stoplist. | |
| Action: | Remove the duplicate stop word to re-create the stoplist. | |
DRG--10540 null Stop Words are not allowed
| Cause: | One of the entries specified in the stoplist does not have a stop word value. | |
| Action: | Remove the NULL entry or specify a stop word value for the entry to re-create the stoplist. | |
DRG--10541 length of the stop list entry %(1)s exceeded the limit
| Cause: | A stop list entry has exceeded the maximum length of 64 bytes. | |
| Action: | Reduce the length of the stoplist entry to re-create the stoplist. | |
DRG--10542 adding the word %(1)s to stop list exceeded the maximum limit
| Cause: | Stoplist entries have exceeded the maximum limit of 255. | |
| Action: | Limit the number of entries in the stoplist to 255. | |
DRG--10544 invalid framework object %(1)s for create preference
| Cause: | You attempted to create a preference with an invalid object type. | |
| Action: | Specify a valid framework object to create the preference. | |
DRG--10545 cannot create policy in another user's schema
| Cause: | You attempted to create a policy in another user's schema. | |
| Action: | Create the policy in your schema or have CTXSYS create the policy. | |
DRG--10547 preference %(1)s.%(2)s already exists
| Cause: | The specified preference already exists in the ConText data dictionary. | |
| Action: | Drop the existing preference before you re-create it. | |
DRG--10548 length of the user name %(1)s exceeded the limit
| Cause: | A user name has exceeded the maximum length of 30 bytes. | |
| Action: | Reduce the length of the user name to re-create it. | |
DRG--10549 length of the object name %(1)s exceeded the limit
| Cause: | An object name has exceeded the maximum length of 30 bytes. | |
| Action: | Reduce the length of the object name to re-create it. | |
DRG--10550 illegal syntax for policy or preference %(1)s name
| Cause: | The policy or preference specification may have additional periods(.) | |
| Action: | Check the syntax of the preference or policy to ensure additional periods are not present. | |
DRG--10551 length of the table name %(1)s exceeded the limit
| Cause: | A table name has exceeded the maximum length of 30 bytes. | |
| Action: | Reduce the length of the table name before you re-create it. | |
DRG--10552 length of the column name %(1)s exceeded the limit
| Cause: | A column name has exceeded the maximum length of 30 bytes. | |
| Action: | Reduce the length of the column name before you re-create it. | |
DRG--10553 illegal syntax for column specification %(1)s
| Cause: | The column specification may have additional periods(.) | |
| Action: | Check the syntax of the column specification to ensure additional periods are not present. | |
DRG--10554 parallel Index Optimization not supported for option %(1)s
| Cause: | You attempted to perform in-place index optimization in parallel. Parallel index optimization is supported for 2-table compaction only. | |
| Action: | Perform in-place index optimization serially or use the 2-table compaction method when optimizing in parallel. | |
DRG--10555 parallel Index Optimization failed to process %(1)s fully
| Cause: | This is an internal error detected during parallel processing. | |
| Action: | Contact Oracle support. Continue to use the original, unoptimized text index until the problem has been resolved. | |
DRG--10556 invalid Index Optimization option %(1)s specified
| Cause: | The specified option for index optimization is not supported. Supported options are:
1) DR_OPTIMIZE_LAZY_DELETES (garbage collection)
2) DR_OPTIMIZE_COMPACT_INDEXES (in-place compaction)
3) DR_OPTIMIZE_COMPACT_NEW (2-table compaction)
4) DR_OPTIMIZE_LAZY_DELETES_NEW (2-table compaction/garbage collection)
5) DEFRAGMENT_TO_NEW_TABLE (2-table compaction)
6) DEFRAGMENT_IN_PLACE (in-place compaction) | |
| Action: | Specify one of the supported options. | |
DRG--10557 a synonym cannot be used as a datasource
| Cause: | The datasource for a policy must be a table or a view. Creating policies against synonyms is not yet supported. | |
| Action: | Specify one of the supported datasources (table or view) for the policy. | |
DRG--10558 cannot create text index on a template policy %(1)s
| Cause: | A template policy was specified in the procedure call for creating a text index. | |
| Action: | Specify a column policy. | |
DRG--10559 textkey must be specified -- datasource is a view
| Cause: | When creating a policy with a view as the datasource, a column of the view must be specified as the textkey (primary key). | |
| Action: | Specify a column in the view as the textkey for the policy | |
DRG--10560 lineno column %(1)s does not exist, is too long, or is not unique
| Cause: | The lineno specified is not a column of the text table or its length exceeds 64 bytes. | |
| Action: | Check the specified lineno. | |
DRG--10561 lineno must be specified for master-detail datasource
| 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. | |
DRG--10562 lineno should be specified only for master-detail datasource
| Cause: | When creating a policy which is not a master-detail datasource, you can not specify a column for lineno. | |
| Action: | Do not specify the lineno column in this procedure call. | |
DRG--10563 textkey must be specified -- no composite primary key found
| 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. | |
DRG--10564 textkey column %(1)s is not part of a composite key
| 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. | |
DRG--10565 too many values for attribute %(1)s (maximum %(2)s)
| Cause: | You specified too many values for the attribute. | |
| Action: | Specify fewer values. | |
DRG--10566 mandatory attribute %(1)s is missing or null
| Cause: | You did not specify a mandatory attribute for the preference. | |
| Action: | Specify the mandatory attribute. | |
DRG--10567 duplicate policy or source id exists
| Cause: | Duplicate policy or source id exists. | |
| Action: | Use ctx_ddl.create_policy or create_source. | |
DRG--10568 source %(1)s does not exist
| Cause: | The specified source does not exist or you do not have access to it. | |
| Action: | Must first create the source. | |
DRG--10569 table or column does not exist: %(1)s
| Cause: | The table, view, synonym, or column specified does not exist. There may also be a permissions problem reading the table. | |
| Action: | Reinvoke the operation with the correct table name or column name. | |
DRG--10570 cannot create preference in another user's schema
| Cause: | You tried to create a preference for another user. | |
| Action: | Owner or CTXSYS or a user who has CTXADMIN role should create preference. | |
10600--10699: DML
DRG--10600 failed to register column %(1)s with DML Queue
| Cause: | The system could not set up triggers to monitor updates to the requested column. | |
| Action: | Check next error on stack to determine course of action. Contact Oracle Worldwide Support if necessary. Until this error is fixed, updates to the text columns in the given table are not automatically indexed. | |
DRG--10601 failed to deregister column with DML Queue
| Cause: | The system could not remove triggers set up to monitor updates to the requested table. | |
| Action: | Check next error on stack to determine course of action. Contact Oracle Worldwide Support if necessary. Until this error is fixed, updates to the text columns in the given table are not automatically indexed. | |
DRG--10602 failed to queue DML change to column %(1)s for primary key %(2)s
| Cause: | The system could not record that a change has been made to the given column. | |
| Action: | See next error on stack to determine course of action. Contact Oracle Worldwide Support if necessary. Until this error is fixed, updates to the text columns in the given table may not be indexed. | |
DRG--10603 failed to sync to current time
| Cause: | The system could not perform the requested sync operation. | |
| Action: | See next error on stack to determine course of action. | |
DRG--10604 failed to sync to date %(1)s
| Cause: | The system could not perform the requested sync operation. | |
| Action: | See next error on stack to determine course of action. | |
DRG--10605 failed to query the date to which system is synced
| Cause: | The system could not query the requested sync date. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--10606 server failed to access the DML Queue
| Cause: | The server encountered an error accessing the DML Queue. | |
| Action: | Check next error on stack to determine course of action. | |
DRG--10607 failed to requeue requests for server %(1)s
| 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: | Check next error on stack to determine course of action. | |
DRG--10608 timeout while waiting for DML to complete
| Cause: | Timeout occurred while waiting for the DML to complete. | |
| Action: | No action required. | |
10700--10799: Preference
DRG--10700 unknown preference parameter for %(1)s: %(2)s
| Cause: | The specified preference parameter is not recognized by ConText Option. | |
| Action: | Specify a valid preference parameter and resubmit the procedure. | |
DRG--10701 more than maximum %(3)s allowed values for parameter %(2)s for %(1)s
| Cause: | The number of values specified for the preference parameter exceeds the system limits. | |
| Action: | Correct the number of specified values and resubmit the procedure. | |
DRG--10702 expecting at least %(3)s values for parameter %(2)s for %(1)s
| Cause: | The number of values specified for the preference parameter does not match the number of expected parameter values. | |
| Action: | Correct the number of specified values and resubmit the procedure. | |
DRG--10703 value for %(1)s parameter %(2)s should be of type %(3)s
| Cause: | The value specified for the preference parameter is invalid. | |
| Action: | Correct the preference parameter and resubmit the procedure. | |
DRG--10704 value of %(1)s parameter %(2)s out of range %(3)s..%(4)s
| Cause: | The value specified for the preference parameter is not in the supported range of values. | |
| Action: | Correct the preference parameter and resubmit the procedure. | |
DRG--10705 parameter %(2)s for %(1)s was set to default value %(3)s
| Cause: | The value specified for the preference parameter was invalid and was replaced with the system default for the parameter. | |
| Action: | Correct preference setting and resubmit the procedure. | |
DRG--10706 parameter %(2)s for %(1)s is larger than maximum size (%(3)s bytes)
| Cause: | The length in bytes of the specified parameter exceeds the system limits. | |
| Action: | Correct the length of the preference parameter and resubmit the procedure. | |
DRG--10707 value of parameter %(2)s for %(1)s not valid for domain
| Cause: | The specified parameter, %(2)s, is in an enumerated domain, but the value specified is not valid for that domain. | |
| Action: | Correct the preference parameter and resubmit the procedure. | |
DRG--10708 printjoins and skipjoins have characters in common
| Cause: | The same characters were specified as both printjoin and skipjoin characters. Printjoin and skipjoin characters must be mutually exclusive. | |
| Action: | Correct the attribute values and resubmit the procedure. | |
DRG--10709 base-letter conversion not supported with current character set
| 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. | |
DRG--10826 no document with the specified textkey is found
| Cause: | There is no document with the specified textkey. | |
| Action: | Check the textkey. | |
10800--10899: Query
DRG--10800 query failed: %(1)s %(2)s %(3)s
| Cause: | The system failed to process the query. | |
| Action: | Check the errors on the stack and take the appropriate action. | |
DRG--10801 text query failed
| Cause: | The system was unable to process the CONTAINS portion of the query. | |
| Action: | Check the errors on the stack and take the appropriate action. | |
DRG--10802 unmatched quotes found: offset %(1)s
| Cause: | An unmatched quote was found. | |
| Action: | Balance the quotes and resubmit the query. | |
DRG--10803 unmatched parenthesis found: offset %(1)s
| Cause: | An unmatched parenthesis was found. | |
| Action: | Balance the parenthesis and resubmit the query. | |
DRG--10804 missing from clause found: offset %(1)s
| Cause: | The SELECT statement is missing the required FROM clause. | |
| Action: | Provide the required FROM clause and resubmit the query. | |
DRG--10805 duplicate from clause found: offset %(1)s
| Cause: | The SELECT statement has duplicate FROM clauses. | |
| Action: | Remove the duplicate FROM clauses and resubmit the query. | |
DRG--10806 where clause outside of a select statement found: offset %(1)s
| Cause: | A WHERE clause was detected outside the SELECT statement. | |
| Action: | Correct the SELECT statement syntax and resubmit the query. | |
DRG--10807 more than 1 where clause inside a select found: offset %(1)s
| Cause: | The SELECT statement contains more than one WHERE clause. | |
| Action: | Remove the additional WHERE clauses and resubmit the query. | |
DRG--10808 order by clause outside of a select statement found: offset %(1)s
| Cause: | An ORDER BY clause was detected outside the SELECT statement. | |
| Action: | Correct the SELECT statement syntax and resubmit the query. | |
DRG--10809 more than 1 order by clause inside a select found: offset %(1)s
| Cause: | The SELECT statement contains more than one ORDER BY clause. | |
| Action: | Remove the additional ORDER BY clauses and resubmit the query. | |
DRG--10810 group by clause outside of a select statement found: offset %(1)s
| Cause: | A GROUP BY clause was detected outside the SELECT statement. | |
| Action: | Correct the SELECT statement syntax and resubmit the query. | |
DRG--10811 more than 1 group by clause inside a select found: offset %(1)s
| Cause: | The SELECT statement contains more than one GROUP BY clause. | |
| Action: | Remove the additional GROUP BY clauses and resubmit the query. | |
DRG--10812 having clause outside of a select statement found: offset %(1)s
| Cause: | A HAVING clause was detected outside the SELECT statement. | |
| Action: | Correct the SELECT statement syntax and resubmit the query. | |
DRG--10813 more than 1 having clause inside a select found: offset %(1)s
| Cause: | The SELECT statement contains more than one HAVING clause. | |
| Action: | Remove the additional HAVING clauses and resubmit the query. | |
DRG--10814 keyword outside a select found: offset %(1)s
| Cause: | A keyword was detected outside the SELECT statement. | |
| Action: | Correct the SELECT statement syntax and resubmit the query. | |
DRG--10815 fuzzy match word is shorter than the minimum of 3 letters
| Cause: | The specified fuzzy match word did not meet the minimum length requirement. Fuzzy match words must consist of at least 3 characters. | |
| Action: | Specify a longer fuzzy match word and resubmit the query. | |
DRG--10816 display/highlight call failed
| Cause: | The system was unable to perform the display/highlight call. | |
| Action: | Check the next error on the stack to determine a course of action. | |
DRG--10817 CONTAINS term consists of stopword or phrase of stopwords: %(1)s
| Cause: | All the query terms in a CONTAINS() function are stop words. ConText Option does not support text queries that consist of only stop words. | |
| Action: | Specify only non-stop words or a combination of non-stop words and stop words in the CONTAINS() query expression and resubmit the query. | |
DRG--10818 soundex used when not specified in column policy
| Cause: | Soundex was specified in the query; however Soundex is not enabled for the text column. To use Soundex in a query, the SOUNDEX_AT_INDEX attribute must have been specified in the Wordlist preference for the column policy. | |
| Action: | Remove Soundex from the query or drop the text index for the column, update the column policy, and reindex the column. | |
DRG--10819 could not open contains cursor
| Cause: | An error occurred while trying to open a contains cursor. | |
| Action: | See accompanying error messages in the stack. | |
DRG--10820 invalid contains cursor id
| Cause: | You tried to fetch or close a contains cursor with an id which does not exist. | |
| Action: | Review fetch or close invocation. | |
DRG--10821 contains cursor is not open
| Cause: | You tried to fetch from a contains cursor which was not open. | |
| Action: | Remove soundex from the query or rebuild the column policy. | |
DRG--10822 duplicate query name
| Cause: | You tried to create a stored query with a name already used. | |
| Action: | Use a different name. | |
DRG--10823 invalid query name
| Cause: | The query name specified is not valid. | |
| Action: | Check the query name. | |
DRG--10824 invalid scope
| Cause: | The scope specified is not valid. | |
| Action: | Use SYSTEM or SESSION. | |
DRG--10825 stored query does not exist or has been redefined: %(1)s
| Cause: | The specified stored query does not exist or has been redefined. | |
| Action: | Check the query name. | |
10900--10999: Resource
DRG--10900 out of memory
| Cause: | The system could not allocate more memory. | |
| Action: | Contact your system administrator. | |
11000--11099: System Consistency
DRG--11000 failed to perform recovery for a server or client
| Cause: | The system could not perform recovery for a server or client. | |
| Action: | Contact Oracle Worldwide Support. | |
11100--11199: General User
DRG--11100 unable to connect to the database
| Cause: | The system failed to connect to an Oracle database. | |
| Action: | Check the Oracle error stack to determine cause of failure. In addition, check the specified connect string. | |
DRG--11101 failed to open file %(1)s
| Cause: | The system failed to open a file. | |
| Action: | Check whether the file exists and access permission is available. | |
DRG--11102 assigned lexer can not operate on %(1)s language setting
| Cause: | The ConText Option single byte Lexer has been specified in a multibyte language setting. | |
| Action: | Ensure that the RDBMS language setting is set correctly and the correct Lexer has been specified for the text columns in the database. | |
DRG--11104 ConText error:
| Cause: | A ConText error has occurred. | |
| Action: | Check the next error on stack to determine a course of action. | |
DRG--11105 display failed: column %(1)s
| Cause: | ConText Option failed to display selected rows. | |
| Action: | Check the errors on the stack and take appropriate action. | |
DRG--11106 user database session has terminated during this operation
| Cause: | The database session does not exist or has terminated. | |
| Action: | Determine why the user database session terminated while ConText operation was still being carried out. | |
DRG--11107 invalid path specification: %(1)s
| Cause: | The file could not be indexed because the specified file path is not valid. | |
| Action: | Check the path specification to ensure it is valid. | |
DRG--11108 invalid filename specified: %(1)s
| Cause: | The file could not be indexed because the specified filename is not valid. | |
| Action: | Check the filename for beginning or trailing spaces, invalid characters, or other such problems. | |
DRG--11109 assigned lexer does not support %(1)s query operator
| Cause: | This lexer does not support this query operator. | |
| Action: | Do not use the operator in your query. | |
11200--11299: Filter
DRG--11200 blaster filter failed with status %(1)d
| Cause: | An error occurred in the MasterSoft blaster filter for the column. | |
| Action: | Lookup the meaning of the blaster status code, and rectify the 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 document too big for target
12 Warning on conversion
13 Conversion cancelled
14 Invalid parameters on com line
15 File stored encrypted
16 Converter encountered fatal error
17 Lseek failed
DRG--11201 could not recognize format of input
| Cause: | The column policy specifies that the filter must automatically recognize the format of documents. A document could not be filtered because it does not conform to any format known to the filter. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--11202 invalid filter format %(1)s
| Cause: | The specified filter format number is invalid. | |
| Action: | Specify a valid filter format number. The ConText Option documentation contains a complete list of supported format filters. | |
DRG--11203 format %(1)d (%(2)d) is not supported
| Cause: | The autorecognize filter recognized this file format, but the format is not yet supported by the filter. | |
| Action: | Check the file format. | |
DRG--11204 user filter command is too long
| Cause: | The user filter command must be 32 characters or less. | |
| Action: | Reduce the user filter command to the supported length and call the Preference Creation procedure again. | |
DRG--11205 user filter command contains illegal characters
| Cause: | The user filter command cannot contain special characters such as slashes, parentheses, semicolons, etc. | |
| Action: | Remove all non-supported characters from the user filter command and call the Preference Creation procedure again. | |
DRG--11206 user filter command %(1)s could not be executed
| 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. | |
DRG--11207 user filter command exited with status %(1)s
| Cause: | The user filter command exited with the given error status. | |
| Action: | Check the error stack for required action. | |
DRG--11208 ORACLE_HOME is not set
| Cause: | ORACLE_HOME is not set. | |
| Action: | Ensure ORACLE_HOME is set correctly before running ctxsrv. | |
DRG--11209 markup is not supported for this document format
| Cause: | The filter does not support generating highlighting markup for the document format. | |
| Action: | No action required. | |
DRG--11210 ICF is not supported for this document format
| Cause: | The filter does not support generating ICF output for the document format. | |
| Action: | No action required. | |
DRG--11211 user-defined filter for format %(1)s registered mutiple times
| Cause: | The executable for the specified format already registered. | |
| Action: | Must remove the duplicate format if you want to re-create it. | |
DRG--11212 no format id registered for attribute=%(1)s
| Cause: | No value specified for format id. | |
| Action: | Must provide format id if you want to re-create it. | |
DRG--11213 no executable name provided for attribute=%(1)s
| Cause: | You did not provide an executable name. | |
| Action: | Must provide executable name if you want to re-create it. | |
DRG--11214 there is no filter available for this format
| Cause: | No user-defined filter or Blaster filter available for this format. | |
| Action: | Register a user-defined filter for this format. | |
DRG--11215 highlighting not supported when user-defined filter is used
| Cause: | A user-defined filter was used for this document. | |
| Action: | No action required. | |
DRG--11216 both FORMAT and EXECUTABLE cannot be used
| Cause: | Only one attribute is allowed to be set for this Tile. | |
| Action: | Specify either FORMAT or EXECUTABLE as the attribute for the Tile. | |
11300--11399: Translation
DRG--11300 failed to translate query
| Cause: | ConText Option could not parse or translate the SELECT statement. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11301 translated statement too long
| Cause: | There is not enough space to hold the translated query. | |
| Action: | Reduce the length of the query to be translated. | |
DRG--11302 expected search string
| Cause: | The second argument of the CONTAINS() function must be a string (query expression). | |
| Action: | Correct the CONTAINS() function syntax and resubmit the query. | |
DRG--11303 duplicate contains label '%(1)s'
| Cause: | This CONTAINS() label has already been specified. | |
| Action: | Ensure each CONTAINS() label is uniquely identified. | |
DRG--11304 contains label value '%(1)s' is too big
| Cause: | The numeric limit for a CONTAINS() label has been exceeded. | |
| Action: | Ensure all the labels are within the documented limits. | |
DRG--11305 score label '%(1)s' has no matching contains
| Cause: | The label in a SCORE() function does not have a matching CONTAINS(). | |
| Action: | Ensure all the labels referenced in SCORE() are defined in a CONTAINS() function. | |
DRG--11306 column '%(1)s' has no indexing policy
| Cause: | No text indexing policies defined for this column. | |
| Action: | Define a policy for the column and create a text index for the column. | |
DRG--11307 failed to parse contains()
| Cause: | The syntax of the CONTAINS() function is not valid. | |
| Action: | Correct the CONTAINS() function syntax and resubmit the query. | |
DRG--11308 failed to parse score()
| Cause: | The syntax of the SCORE() function is not valid | |
| Action: | Correct the SCORE() function syntax and resubmit the query. | |
DRG--11309 failed to parse handle()
| Cause: | The syntax of the HANDLE() function is not valid. | |
| Action: | Correct the HANDLE() function syntax and resubmit the query. | |
DRG--11310 failed to replace statement
| Cause: | The replacement of a portion of the rewritten statement has failed. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11311 failed to execute contains()
| Cause: | The system could not execute one of the CONTAINS() in the query couldn't. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11312 failed to execute query
| Cause: | The system could not execute a translated query. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11313 contains() outside WHERE clause
| Cause: | The CONTAINS() function is allowed only in a WHERE clause. | |
| Action: | Correct the query and resubmit. | |
DRG--11314 score() inside FROM clause
| Cause: | The SCORE() function is not allowed in a FROM clause. | |
| Action: | Correct the query and resubmit. | |
DRG--11315 handle() outside SELECT list
| Cause: | The HANDLE() function is allowed only in a SELECT list. | |
| Action: | Correct the query and resubmit. | |
DRG--11316 failed to parse bind variable name
| Cause: | A valid identifier must be specified after a colon. | |
| Action: | Correct the variable and resubmit the query. | |
DRG--11317 failed to parse SELECT list
| Cause: | A syntax error was detected while parsing a SELECT list. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11318 failed to parse FROM clause
| Cause: | A syntax error was detected while parsing a FROM clause. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11319 failed to parse WHERE clause
| Cause: | A syntax error was detected while parsing a WHERE clause. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11320 hierarchical query not allowed
| Cause: | Queries which use tree traversal clauses are not supported. | |
| Action: | If you want to use hierarchical queries, do not use CONTAINS(). | |
DRG--11321 failed to parse ORDER BY clause
| Cause: | A syntax error was detected while parsing an ORDER BY clause. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11322 failed to parse GROUP BY clause
| Cause: | A syntax error was detected while parsing a GROUP BY clause. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11323 failed to parse outside select
| Cause: | A syntax error was detected while parsing outside a SELECT clause. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11324 undefined parse state
| Cause: | An error occurred in an undefined parsing state. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--11325 translation component failure
| Cause: | One of the translation components failed. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--11326 failed to close query
| Cause: | Couldn't remove the information for a query from the dr$contains or dr$bind (internal) tables. | |
| Action: | Check that the query and session identifiers correspond to a query which has been executed. | |
DRG--11327 column '%(1)s' ambiguously defined
| 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. | |
DRG--11328 failed to save translated query
| Cause: | The system couldn't save a translated query. | |
| Action: | Check further messages for the cause of the error. | |
DRG--11329 session specific result table sharing level not supported
| Cause: | This mode of operation is not currently implemented. | |
| Action: | Specify query-specific or CONTAINS()-specific result table sharing levels. | |
DRG--11330 failed to allocate result table
| Cause: | Maximum number of result tables created or other Oracle error. | |
| Action: | Drop result tables for sessions which are no longer active. | |
11400--11499: ConText Linguistics
DRG--11400 failed to parse document with key %(1)s
| Cause: | The document specified for linguistic extraction could not be parsed. This could indicate that the document does not contain well-formed English. | |
| Action: | Check the document contents. | |
DRG--11401 policy name too long
| Cause: | The policy name parameter passed to the service request exceeds the maximum policy name size. | |
| Action: | Check policy parameter and resubmit request. | |
DRG--11402 result table name too long
| Cause: | The result table name parameter passed to the service request exceeds the maximum table name size. | |
| Action: | Check result table parameter and resubmit request. | |
DRG--11403 primary key value too long
| Cause: | The primary key value parameter passed to the service request exceeds the maximum primary key length (64 bytes). | |
| Action: | Check primary key parameter and resubmit request. | |
DRG--11404 no primary key value specified
| Cause: | The primary key value parameter passed to the service request is null. | |
| Action: | Ensure primary key is specified and resubmit request. | |
DRG--11405 negative timeout duration not allowed
| Cause: | The timeout duration parameter passed to the service request is negative. Timeout duration must be a positive number. | |
| Action: | Specify a positive value for the timeout duration parameter and resubmit request. | |
DRG--11406 no pending requests to submit
| Cause: | There are no pending requests to submit. | |
| Action: | No action required. | |
DRG--11407 theme result table %(1)s has incorrect format
| Cause: | The result table specified is missing an expected column or the columns in the table 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). | |
DRG--11408 catalog result table %(1)s has incorrect format
| Cause: | The result table specified is missing an expected column or the columns in the table 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). | |
DRG--11409 gist result table %(1)s has incorrect format
| Cause: | The result table specified is missing an expected column, or the columns in the table 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). | |
DRG--11410 could not insert into %(1)s result table
| Cause: | An ORACLE error occurred while linguistic output was being inserted into the result table. | |
| Action: | Check the ORACLE error stack and take appropriate action. | |
DRG--11411 could not find a document with primary key value %(1)s
| Cause: | The document for which a service was requested does not exist. | |
| Action: | Check the service request and the datasource to insure that the requested document exists with the correct primary key value. | |
DRG--11412 pending requests must be submitted before sending new requests
| Cause: | There are pending requests which must be submitted to the Services Queue before new requests can be made. | |
| Action: | Submit or cancel the pending requests. | |
DRG--11413 invalid request handle %(1)s
| Cause: | An invalid request handle was specified for the procedure. | |
| Action: | Check the request handle and re-execute the procedure. | |
DRG--11414 no requests to delete
| Cause: | The request is already running on a server, the request handle is invalid, or the request is not your request. | |
| Action: | If the request is already being processed, no action required. If the specified handle is invalid, specify a valid request handle and re-execute the CANCEL procedure. | |
DRG--11415 could not invoke %(1)s callback %(2)s
| Cause: | The specified callback routine does not exist or the requestor does not have EXECUTE permission for the routine. | |
| Action: | Specify an existing callback, create a new callback, or grant the requestor EXECUTE permission. | |
DRG--11416 ConText server terminated before completing request
| Cause: | The ConText server which was processing this service request terminated before finishing processing. | |
| Action: | Resubmit the request. | |
DRG--11417 %(1)s parser warning
| 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. | |
DRG--11418 %(1)s parser: insufficient document content
| 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. | |
DRG--11419 priority must be between 0 and 10
| Cause: | You specified a priority which was not between 1 and 10. | |
| Action: | Change the priority value specified. | |
DRG--11420 invalid settings label %(1)s
| Cause: | You specified an invalid settings label. | |
| Action: | Change the settings label specified. | |
DRG--11421 ConText linguistic services not enabled
| Cause: | You tried to use the L personality with a non-linguistic server. | |
| Action: | Use the full ConText server. | |
DRG--11422 linguistic initialization failed
| Cause: | Linguistic services initialization failed -- possibly out of memory. | |
11500--11599: Loader
DRG--11500 unexpected end of file at line %(1)s
| Cause: | The load file terminated before current record end. | |
| Action: | Check record and keywords at the end of the load file. | |
DRG--11501 column name expected, found %(1)s on line %(2)s
| Cause: | The column name or keyword are probably misspelled. | |
| Action: | Verify that the spelling and punctuation around the identified line are correct. | |
DRG--11502 identifier %(1)s found in place of column name on line %(2)s
| Cause: | The column name is probably misspelled. | |
| Action: | Verify that the spelling around the identifier line is correct. | |
DRG--11503 read of file failed at line %(1)s for file %(2)s
| Cause: | Invalid file name, wrong file type or file system error. | |
| Action: | Check file name, type and/or file integrity. | |
DRG--11504 long value may have overflowed at line %(1)s
| Cause: | LONG value reached end of load buffer. | |
| Action: | Check length of inserted data for current table. | |
DRG--11505 long value overflowed specified buffer on line %(1)s
| Cause: | LONG buffer length insufficient for LONG data length. | |
| Action: | Increase LONGSIZE parameter. | |
DRG--11506 insert statement overflows maximum statement size
| Cause: | Total length of insert statement exceeds the database maximum. | |
| Action: | Reduce the length of the column names or number of columns in the load file. | |
DRG--11507 invalid longsize parameter of %(1)s specified
| Cause: | Invalid option argument. | |
| Action: | Specify LONG buffer size in kilobytes above 0. | |
DRG--11508 long data on line %(1)s not found or invalid
| Cause: | Either invalid data or data file exists. | |
| Action: | Check that the file exists and is accessible, if using the separate option in ctxload. | |
DRG--11509 record ignored on line %(1)s because of error(s)
| Cause: | An error occurred while parsing this row's data. | |
| Action: | Move and amend line in error to alternate load file. | |
DRG--11510 file error trying to read separate file
| Cause: | File not found or could not be read while using the separate option. | |
| Action: | Check the name and location of the file specified in the load file. | |
DRG--11511 bad or missing %(2)s token on line %(1)s
| Cause: | The expected token was not found. | |
| Action: | Move and amend affected record to error load file. | |
DRG--11512 value expected on line %(1)s
| Cause: | The loader could not make sense of text where value expected. | |
| Action: | Move and amend affected record to error load file. | |
DRG--11513 start token not found on line %(1)s
| Cause: | Token could be misplaced or misspelled. | |
| Action: | Processing discontinued - amend record. | |
DRG--11514 encountered unrecoverable error on line %(1)s
| Cause: | See previous messages. | |
| Action: | See previous errors. | |
DRG--11515 value given is longer than defined length on line %(1)s
| Cause: | Data too long for column. | |
| Action: | Correct the column data length for insertion. | |
DRG--11516 load file specified could not be found
| Cause: | The specified load file could not be located. | |
| Action: | Verify that the name, location, access permission, and type of load file are correct. | |
DRG--11517 specified table does not contain a LONG or LONG RAW column
| Cause: | The loader only supports inserting text into LONG or LONG RAW datatype columns. | |
| Action: | Verify that LONG or LONG RAW column exists for specified table. | |
DRG--11518 bad syntax for thesaurus load file, line %(1)s
| Cause: | Load file must have specific format for loading thesaurus. | |
| Action: | Check documentation for description of correct format. | |
DRG--11519 truncating phrase since longer than max allowed length, line %(1)s
| Cause: | Encountered a phrase longer than maximum allowed length. | |
| Action: | Use a shorter phrase on the indicated line. | |
DRG--11520 unable to open or write to file %(1)s
| Cause: | An attempt to open or to write to the given file failed. | |
| Action: | Check with system administrator. | |
DRG--11521 cannot find thesaurus %(1)s
| Cause: | Thesaurus for export could not be found. | |
| Action: | Check spelling of thesaurus name. | |
11600--11699: URL Data Store
DRG--11600 URL store: %(1)s has permanently moved
| Cause: | The document referred to by the URL has permanently moved. | |
| Action: | Find the new address, if any, of the document. | |
DRG--11601 URL store: bad syntax on request for %(1)s
| Cause: | Client did not make correct request. | |
| Action: | Contact the ConText Server Group at Oracle Corporation. | |
DRG--11602 URL store: access to %(1)s requires authentication
| Cause: | User has to provide password or other authentication. | |
| Action: | Get required access, or check URL. | |
DRG--11603 URL store: payment required to access %(1)s
| Cause: | Payment is required before the URL can be accessed. | |
| Action: | Check URL, or pay if required if access necessary. | |
DRG--11604 URL store: access to %(1)s is denied
| Cause: | Access to the URL is denied. | |
| Action: | Check URL; if correct, do not try to access URL again. | |
DRG--11605 URL store: document specified by %(1)s not found
| Cause: | The document can not be found on the host specified. | |
DRG--11606 URL store: access to %(1)s timed out waiting for client request
| Cause: | Client did not make response within timeout period. | |
| Action: | Contact the ConText Server Group at Oracle Corporation. | |
DRG--11607 URL store: access to %(1)s was denied due to garbled response
| Cause: | Web server identified in URL doesn't obey HTTP protocol. | |
| Action: | Contact the Web administrator of the remote host. | |
DRG--11608 URL store: host portion of %(1)s specified incorrectly
| Cause: | Host portion of the URL could not be parsed. | |
DRG--11609 URL store: unable to open local file specified by %(1)s
| Cause: | Attempt to open local file failed. | |
DRG--11610 URL store: unable to read local file specified by %(1)s
| Cause: | Attempt to read local file failed . | |
| Action: | Contact your system administrator for read privileges on specified file. | |
DRG--11611 URL store: unknown protocol specified in %(1)s
| Cause: | The protocol parsed is neither http or file. | |
DRG--11612 URL store: unknown host specified in %(1)s
| Cause: | The address of the host specified could not be resolved. | |
DRG--11613 URL store: connection refused to host specified by %(1)s
| Cause: | Attempt to connect to host was forcibly refused. | |
DRG--11614 URL store: communication with host specified in %(1)s timed out
| Cause: | A network operation timed out. | |
| Action: | Try again later; the network connection may be down to Web server. | |
DRG--11615 URL store: write failed sending to %(1)s over network
| Cause: | Unknown error writing request to Web server. | |
| Action: | Check network connection. | |
DRG--11616 URL store: too many redirections trying to access %(1)s
| Cause: | Too long a chain of HTTP redirections given to the URL. | |
| Action: | Contact the Web administrator of the remote host. | |
DRG--11617 URL store: URL %(1)s is too long
| Cause: | The length of the URL string is longer than URLSIZE. | |
| Action: | Set URLSIZE attribute to a larger value. | |
DRG--11618 URL store: document identified by %(1)s is too large
| Cause: | Document larger than user-set maximum size. | |
| Action: | Do not access URL, or increase document size limit. | |
DRG--11619 URL store: row in table is empty
| Cause: | Row deleted or otherwise missing. | |
| Action: | Check table if necessary. | |
DRG--11620 URL store: thread operation error
| Cause: | Thread operation failed. | |
| Action: | Contact your system administrator. | |
DRG--11621 URL store: socket open error for %(1)s
| Cause: | Socket open failed; probably too many open file descriptors. | |
| Action: | Reduce the maximum number of threads started. | |
DRG--11622 URL store: unknown HTTP error getting %(1)s
| Cause: | HTTP error has occurred which ConText doesn't catch. | |
| Action: | Consult HTTP error codes; if valid, contact ConText at Oracle. | |
DRG--11623 URL store: unknown error getting %(1)s
| Cause: | Error has occurred which ConText Option doesn't catch. | |
| Action: | Contact the ConText Server Group at Oracle Corporation. | |
DRG--11624 invalid attribute %(2)s for %(1)s: proper range %(3)s to %(4)s
| Cause: | Error has occurred which ConText doesn't catch. | |
| Action: | Contact ConText at Oracle. | |
11700--11799: Thesaurus
DRG--11700 thesaurus %(1)s already exists
| Cause: | Thesaurus with same name exists. | |
DRG--11701 thesaurus %(1)s does not exist
| Cause: | Thesaurus does not exist. | |
| Action: | Use another thesaurus or create the specified thesaurus. | |
DRG--11702 %(1)s
| Cause: | Error while parsing thesaurus operator in query term. | |
| Action: | See error message for details. | |
11800--11899: Loader Engine
DRG--11800 loader source name missing
| Cause: | Source name is not provided. | |
| Action: | Provide a source name. | |
DRG--11801 source name %(1)s exists for user %(2)s
| Cause: | Duplicate source name for the same user. | |
| Action: | Use another source name. | |
DRG--11802 user %(1)s does not have CTXAPP role to create source
| Cause: | User does not have CTXAPP role. | |
| Action: | Grant user CTXAPP role or create source as CTXSYS. | |
DRG--11803 CTXAPP cannot create source for other users
| Cause: | CTXAPP cannot create source for other users. | |
| Action: | CTXAPP can only create source for itself. | |
DRG--11804 error while creating source
| Cause: | Oracle error encountered. | |
| Action: | Check the Oracle error and take appropriate action. | |
DRG--11805 table owner not the same as source owner
| Cause: | Table owner is not the same as source owner. | |
| Action: | Specify the correct source owner or table owner. | |
12000--12099: Translator
DRG--12000 user translator command is too long
| Cause: | The command specified for a user translator in a Translator preference exceeded the 32 character limit. | |
| Action: | Specify a command that is 32 characters or less. If the executable name specified in the command is longer than 32 characters, the executable name must be shortened or a wrapper must be created for the executable. | |
DRG--12001 user translator command contains illegal characters
| Cause: | The command specified for a user translator in a Translator preference contained special characters such as slashes, parentheses, semicolons, etc. | |
| Action: | specify a command that does not contain any special characters. If the executable name specified in the command contains special characters, the executable name must be changed to omit the characters or a wrapper must be created for the executable. | |
DRG--12002 user translator command %(1)s could not be executed
| 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. | |
DRG--12003 user filter translator exited with status %(1)s
| Cause: | The user translator command exited with the given error status. | |
| Action: | See the error stack in the index error log to determine the next course of action. | |
DRG--12004 ORACLE_HOME is not set
| Cause: | ORACLE_HOME is not set. | |
| Action: | Make sure ORACLE_HOME is set before starting a ConText server process using ctxsrv/ctxsrvx. | |
DRG--12005 user translator failed on file %(1)s
| Cause: | The user translator failed to translate the given file. | |
| Action: | Examine the log file for what command was executed. | |
DRG--12006 user translator failed to create temporary name
| Cause: | A temporary filename could not be generated by the translator. | |
| Action: | Contact Oracle Worldwide Support. | |
DRG--12007 translation failed
| Cause: | The translator object failed. | |
| Action: | If cause is not apparent, contact Oracle Worldwide Support. | |
DRG--12100 reader skipping file: %(1)s
| Cause: | The reader skipped this file because it could not be processed. | |
| Action: | Verify that the file and the translator are in good order. | |
