30 DRG-10000 to DRG-52404
- DRG-10000: failed to read column string.string
-
Cause: Error during read of specified text column
- DRG-10001: can not access result table string
-
Cause: specified table does not exist or server does not have write privileges
- DRG-10002: can not insert into result table
-
Cause: text server is not privileged to insert, tablespace exhausted
- DRG-10011: invalid object name string
-
Cause: a table, column or procedure name specified had an invalid format. It is either too long or contains illegal characters. Probably you are passing in incorrect parameters.
- DRG-10015: id exceeds limit(2147483642) of a number
-
Cause: the limit of an id is 2147483642
- DRG-10016: you must be the owner to modify this object
-
Cause: you tried to modify an object which you do not own
- DRG-10017: you must be string to do this: string
-
Cause: you tried to modify an object which you have no privilege
- DRG-10018: Insufficient Privilege(s)
-
Cause: you tried to perform an action which you have no privilege(s)
- DRG-10019: Alter Session Set Current_Schema is not honoured by this API
-
Cause: Alter Session Set Current_Schema is not honoured by this API
- DRG-10020: invalid access to internal API
-
Cause: you tried to access to an internal API, which is not open to public
- DRG-10100: invalid argument found: string
-
Cause: invalid command argument was specified
- DRG-10101: no value for argument: string
-
Cause: this argument requires value(s)
- DRG-10102: mandatory argument missing: string
-
Cause: this argument is mandatory
- DRG-10103: illegal value for argument: string
-
Cause: an illegal value was passed to this argument
- DRG-10200: invalid server personality mask: string
-
Cause: the specification for the server personality mask is invalid
- DRG-10202: server failed to register
-
Cause: the server failed to register itself with the data dictionary
- DRG-10203: server named string does not exist
-
Cause: update was called with the name of a server that does not exist
- DRG-10204: server update failed
-
Cause: the attempt to update the server failed
- DRG-10205: server deregister failed
-
Cause: the attempt to deregister the server from the data dictionary failed
- DRG-10206: failed to perform recovery for a server or client
-
Cause: Contact oracle support
- DRG-10301: timed out waiting for responses from servers
-
Cause: Not enough servers are running to handle the current system load, and a large backlog of commands has accumulated; perhaps no servers are running. This message could also indicate an internal error where one of the servers has crashed trying to process a given request
- DRG-10302: interrupted waiting for responses from servers
-
Cause: User interrupted the request before it was completed
- DRG-10303: could not queue given commands to be processed
-
Cause: The given command or commands could not (all) be queued. This could indicate an extremely high system load, but it is more likely an internal error.
- DRG-10304: unexpected error sending command(s) to Oracle Text server
-
Cause: There was an unexpected error sending command(s) to server
- DRG-10305: pipe string is full
-
Cause: Could not send command to pipe, because the pipe was full
- 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.
- DRG-10307: no servers running
-
Cause: Could not process command because no servers are running with the correct personality mask.
- DRG-10308: no server with the required string personality mask is running
-
Cause: Could not process command because no servers are running with the correct personality mask.
- DRG-10309: not enough job queue processes
-
Cause: Could not process command because no servers with the correct personality mask are running.
- DRG-10310: servers were shutdown before processing request
-
Cause: The command could not be completed because the servers were shut down or terminated before processing the request.
- DRG-10311: remote send not supported
-
Cause: You tried to specify a database link in an index specification
- DRG-10312: logfile name must be specified
-
Cause: You tried to start logging without specifying a logfile name
- DRG-10313: logging has already been started
-
Cause: You tried to start logging even though logging has already been started
- DRG-10314: logging has not been started
-
Cause: You tried to stop logging even though logging has not been started
- DRG-10315: logging is not supported on MTS
-
Cause: You tried to start logging on MTS
- DRG-10500: CREATE_INDEX failed: column spec string
-
Cause: failed to create text index on the specified column
- DRG-10501: invalid stopword: string
-
Cause: The stopword specified cound be lexed into multiple tokens with current lexer preference
- DRG-10502: index string does not exist
-
Cause: the specified index does not exist or you do not have access to it.
- DRG-10503: table string cannot be indexed because it 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
- DRG-10504: primary key is required when using the DETAIL_DATASTORE
-
Cause: you tried to use the detail datastore to index a table with no primary key constraint
- DRG-10505: TRANSACTIONAL parameter not supported for NDATA
-
Cause: NDATA sections do not support the TRANSACTIONAL parameter
- DRG-10506: table does not exist: string
-
Cause: The table, view, or synonym specified does not exist. There may also be a permissions problem reading the table.
- DRG-10507: duplicate index name: string
-
Cause: the specified index already exists in the dictionary
- DRG-10508: TRANSACTIONAL parameter not supported for JSON INDEX
-
Cause: JSON search index does not support TRANSACTIONAL parameter
- DRG-10509: invalid text column: string
-
Cause: the column specified is not valid
- DRG-10510: stopword is missing
-
Cause: The stopword to be added was not specified.
- DRG-10511: index string does not exist or is incomplete
-
Cause: index creation is not complete
- DRG-10512: TRANSACTIONAL parameter not supported for CONTEXT SEARCH INDEX
-
Cause: CONTEXT search index does not support TRANSACTIONAL parameter
- DRG-10513: index string metadata is corrupt
-
Cause: dictionary contains bad preferences for this index
- DRG-10514: cannot create index with RIO$ prefix
-
Cause: user attempted to create an index whose name is prefixed with RIO$
- DRG-10515: Combination of parameters 'string' and 'string' is not supported
-
Cause: Parameters are incompatible.
- DRG-10516: failed to perform DDL operation due to an Oracle error
-
Cause: the ddl operation requested has failed because of an Oracle error
- DRG-10517: index string is already valid
-
Cause: The index was in a valid state and did not need the requested operation.
- DRG-10518: an operation is in progress which conflicts with string request
-
Cause: another session is operating on this index. it could be: a) DML is requested and DDL is in progress or b) DDL is requested and DML is in progress operation on the index
- DRG-10519: Shadow Index is not supported for 'search index'
-
Cause: attempt to create a shadow index on 'search index'
- DRG-10520: failed to drop index: string
-
Cause: Failed to drop index on the specified index
- DRG-10521: Operation not supported with string on a string Index
-
Cause: The operation uses a feature not supported for index type
- DRG-10525: missing REBUILD keyword
-
Cause: all Oracle Text alter index options require the REBUILD keyword
- DRG-10528: primary keys of type string are not allowed
-
Cause: you tried to create an index on a table with an illegal primary key datatype
- DRG-10531: parallel parameter must be > 0
-
Cause: you called create index with parallel = 0
- DRG-10532: table is not partitioned
-
Cause: you called parallel create index on non-partitioned table
- DRG-10533: invalid user name: string
-
Cause: you specified a user name that is invalid
- DRG-10535: failed to optimize text index string
-
Cause: the optimize operation requested has failed because of an Oracle error
- DRG-10536: Storage cannot be altered at index-level for partitioned indexes.
-
Cause: Alter-index operation was used to modify storage at index-level.
- DRG-10549: length of the object name string exceeded the limit
-
Cause: object name has exceeded the maximun length of 30 bytes
- DRG-10550: illegal syntax for index, preference, source or section name
-
Cause: name may have additional periods(.)
- DRG-10553: illegal syntax for column specification string
-
Cause: column specification may have additional periods(.)
- DRG-10561: index string is not valid for requested operation
-
Cause: The index was not in a valid state due to some prior error.
- DRG-10562: missing alter index parameter
-
Cause: The parameter string was missing
- DRG-10569: table or column does not exist: string
-
Cause: The table, view, synonym or column specified does not exist. There may also be a permissions problem reading the table.
- DRG-10573: index string is obsolete
-
Cause: you specified an obsolete index
- DRG-10574: failed to upgrade text index string
-
Cause: the upgrade operation has failed because of an Oracle error
- DRG-10579: must provide text query criteria
-
Cause: text query criteria is mandatory
- DRG-10581: indirect datastores cannot be used with long or lob text columns
-
Cause: You tried to create an index on a long or lob column using an indirect datastore such as the file or url datastores
- DRG-10582: column string does not exist in table string
-
Cause: you specified an invalid column
- DRG-10583: TRUNCATE INDEX failed: string
-
Cause: Failed to truncate index
- DRG-10584: failed to string string string due to an Oracle error
-
Cause: a DDL operation on an index object failed due to SQL error
- DRG-10594: string feature not supported for string Index
-
Cause: feature not supported for index type
- DRG-10595: ALTER INDEX string failed
-
Cause: failed to alter index
- DRG-10596: string feature not supported for string Search Index
-
Cause: Specified feature not supported for the index being created
- DRG-10597: invalid rebuild online operation
-
Cause: REBUILD ONLINE is not supported for requested operation.
- DRG-10598: invalid parallel operation
-
Cause: PARALLEL is not supported for requested operation.
- DRG-10599: column is not indexed
-
Cause: The column specified is not indexed.
- DRG-10600: Optimization encountered ORA-01555 error
-
Cause: Optimization ran into the snapshot too old error.
- DRG-10601: failed to remove pending DML for this index
-
Cause: The system could not remove triggers setup to monitor updates to the requested table
- DRG-10602: failed to queue DML change to column string for primary key string
-
Cause: The system could not record that a change had been made to the given column
- DRG-10606: server failed to access the DML Queue
-
Cause: The server had an error accessing the DML Queue
- DRG-10607: index meta data is not ready yet for queuing DML
-
Cause: the meta data for the index has not been created yet
- DRG-10608: rowid to primary key mapping not available in base table
-
Cause: Procedural replication is on and no rowid to primary key mapping available in base table
- DRG-10609: cannot encode composite key with more than 16 columns
-
Cause: Cannot encode composite key with more than 16 columns
- DRG-10610: Procedure not supported with Procedural replication on: string
-
Cause: This procedure is not supporeted when Procedural replciation is on
- DRG-10611: Unexpected DML operation for rowid: string
-
Cause: Sync on commit has encountered an unexpected sequence of DML operations
- DRG-10612: error occurred during sync-on-commit
-
Cause: An indexing error occurred during sync on-commit indexing
- DRG-10613: sync on-commit internal error
-
Cause: Sync on-commit encountered an unexpected error
- DRG-10700: preference does not exist: string
-
Cause: the preference name specified does not exists
- DRG-10701: preference string.string already exists
-
Cause: the specified preference already exists
- DRG-10702: cannot create or modify preference in another user's schema
-
Cause: you tried to create a preference for another user
- DRG-10703: invalid framework object string
-
Cause: you specified an invalid object type
- DRG-10704: preference string does not have an attribute named string
-
Cause: you tried to set value for a invalid attribute (not supported by the object.
- DRG-10705: invalid value string for attribute string
-
Cause: you tried to set an illegal value for an attribute
- DRG-10706: length of string exceeds maximum size of string
-
Cause: Parameter is too many bytes
- DRG-10707: a value is required for attribute string of preference string
-
Cause: A required attribute was not provided
- DRG-10708: invalid class id string for preference string
-
Cause: the specified class id is not correct for the specified preference
- DRG-10709: this preference is referenced by string and cannot be dropped
-
Cause: the specified preference is used as part of another preference and cannot be dropped until the referring preference is modified
- DRG-10710: Invalid value string for string attribute
-
Cause: Invalid value provided for save_copy attribute It should be one of these: (PLAINTEXT, FILTERED, NONE)
- DRG-10711: Invalid value for SAVE_COPY attribute: string
-
Cause: Invalid value provided for SAVE_COPY attribute. It should be a boolean value
- DRG-10712: preference string already has value for an attribute named string
-
Cause: Cannot call set_sec_grp_attr for an attribute whose value is already set in a preference
- DRG-10713: preference string does not have any value for attribute named string
-
Cause: Cannot call add_sec_grp_attr_val for an attribute without calling set_sec_grp_attr for the same attribute
- DRG-10714: cannot add or remove value for attribute named string
-
Cause: Cannot call add_sec_grp_attr_val or rem_sec_grp_attr_val for a boolean attribute
- DRG-10715: preference string has incompatible values for string and string
-
Cause: Cannot set related attributes to incompatible values
- DRG-10716: invalid prefix_ns_mapping attribute value string
-
Cause: Value of prefix_ns_mapping is neither of the form xmlns:pfx="ns" nor of the form xmlns="ns"
- DRG-10717: incompatible index settings
-
Cause: Invalid combination of PATH_SECTION_GROUP, DATAGUIDE attribute and NEVER_POPULATE
- DRG-10718: operation not supported with NEVER_POPULATE
-
Cause: Operation is not supported with NEVER_POPULATE index option
- DRG-10719: Value of stage_itab_max_rows can only be either 0 or >=1000
-
Cause: Invalid value for stage_itab_max_rows
- DRG-10720: Syntax only supported with JSON data type or constraint: string
-
Cause: The syntax was invalid.
- DRG-10721: ALTER INDEX does not support this operation
-
Cause: ALTER INDEX supported only with JSON_ENABLE and IS JSON constraint. Any degradation of the index state is not supported either.
- DRG-10722: string is a desupported preference
-
Cause: creating a preference which was desupported
- DRG-10723: string option cannot be enabled
-
Cause: An ALTER INDEX statement attempted to modify an option that is exclusive to JSON or XML Search Indexes.
- DRG-10724: invalid transition to SEARCH_ON string
-
Cause: An attempt was made to rebuild an index with a SEARCH_ON option that degrades the index state.
- DRG-10750: unknown parameter string
-
Cause: Unrecognized parameter
- DRG-10751: invalid value for parameter
-
Cause: Wrong data type or out of range
- DRG-10752: DEFAULT_INDEX_MEMORY cannot be greater than MAX_INDEX_MEMORY
-
Cause: You tried to set DEFAULT_INDEX_MEMORY to a value higher than the maximum set in MAX_INDEX_MEMORY
- DRG-10753: invalid size (in bytes) string string
-
Cause: You specified an incorrectly formatted size string
- DRG-10754: Size (in bytes) must be between string and string
-
Cause: You specified size (in bytes) which is outside the allowed range
- DRG-10755: string and string have characters in common
-
Cause: the join character sets cannot have characters in common
- DRG-10756: neither text indexing nor theme indexing has been selected
-
Cause: INDEX_TEXT and INDEX_THEMES preferences both cannot be FALSE.
- DRG-10757: stoplist cannot have more than 4096 stopwords
-
Cause: a stoplist cannot have more than 4096 stopwords. This includes stopthemes.
- DRG-10758: index owner does not have the privilege to use file or URL datastore
-
Cause: index owner does not have the Text Datastore Access Privilege
- DRG-10759: invalid role
-
Cause: the role does not exist in the database
- DRG-10760: illegal format for procedure name
-
Cause: the procedure name specified is invalid. For instance, it may have a semicolon
- DRG-10761: procedure string does not exist
-
Cause: the specified procedure could not be found
- DRG-10762: index owner does not have access to procedure string
-
Cause: the index owner does not have execute privilege on the specified procedure
- DRG-10763: value string is not a valid character set
-
Cause: the value specified for the filename_charset attribute of the file datastore is not a valid character set name
- DRG-10765: stoplist cannot have more than 250 stopclasses with stoppatterns
-
Cause: a stoplist cannot have more than 250 stopclasses with stoppatterns. This does not include NUMBERS stopclass.
- DRG-10766: Wildcard Index is not supported for string Index
-
Cause: Wildcard Index is not Supported for CTXCAT/CTXRULE index
- DRG-10767: Specified datastore is not supported on the policy
-
Cause: Using a datastore not supported on the policy for inmemory text
- DRG-10768: num_themes must be greater than zero
-
Cause: Providing a number less than zero for num_themes parameter
- DRG-10769: token_type is not suppported for this operation
-
Cause: chosen token_type is not supported for this operation
- DRG-10800: query failed: string string string
-
Cause: Failed to process the query
- DRG-10801: cannot create an SQE for another user
-
Cause: You tried to create an SQE for another user
- DRG-10816: display/highlight call failed
-
Cause: See the next error on the stack.
- DRG-10817: CONTAINS term consists of stopword or phrase of stopwords: string
-
Cause: One or more terms within a CONTAINS query consist of just a stopword or a phrase of just stopwords
- DRG-10819: could not open contains cursor
-
Cause: An error occurred while trying to open a contains cursor
- DRG-10820: invalid contains cursor id
-
Cause: You tried to fetch or close a contains cursor with an id which does not exist.
- DRG-10821: contains cursor is not open
-
Cause: You tried to fetch from a contains cursor which was not open.
- DRG-10822: duplicate query name
-
Cause: You tried to create a stored query with a name already used.
- DRG-10823: invalid query name
-
Cause: The query name specified is not valid
- DRG-10825: stored query does not exist: string
-
Cause: The specified stored query does not exist.
- DRG-10826: no document with the specified textkey is found
-
Cause: There is no document with the specified textkey.
- DRG-10827: open_con must be performed before count_last
-
Cause: last_count returns hit from in-memory query,so an in-memory query must be run before you can use count_last
- DRG-10828: token string is longer than maximum length for column string
-
Cause: A token to be inserted in the feedback table is longer than the maximum allowed column size.
- DRG-10829: feedback id string is longer than the maximum length of string bytes
-
Cause: Feedback id is longer than the maximum allowed length for the feedback_id column.
- DRG-10830: SHARELEVEL is not 0 or 1
-
Cause: You specified a sharelevel which is not 0 or 1
- DRG-10831: can not insert into feedback table string
-
Cause: Not privileged to insert.
- DRG-10832: can not delete from feedback table string
-
Cause: Not privileged to delete.
- DRG-10833: feedback failed
-
Cause: Failed to process feedback request
- DRG-10834: upper-case form of section name string too long
-
Cause: upper-case form of the section name is longer then supported length
- DRG-10835: WITHIN operator not supported for theme index
-
Cause: WITHIN operator used in theme index query
- DRG-10836: field section and attribute section can not be nested
-
Cause: A field section or a attribute section is specified in a nested section search
- DRG-10837: section string does not exist
-
Cause: The given section name does not exist in USER_SECTIONS
- DRG-10838: invalid SPAN argument supplied to NEAR
-
Cause: An invalid value was supplied for SPAN argument to NEAR
- DRG-10839: invalid ORDER argument supplied to NEAR
-
Cause: An invalid value was supplied for ORDER argument to NEAR
- DRG-10840: CONTAINS predicate including 0 is not supported by FIRST_ROWS hint
-
Cause: User attempts to issue a query with CONTAINS predicate including 0 while giving FIRST_ROWS hint.
- DRG-10841: invalid SCORE argument supplied to FUZZY
-
Cause: An invalid value was supplied for SCORE argument to FUZZY
- DRG-10842: invalid NUMRESULTS argument supplied to FUZZY
-
Cause: An invalid value was supplied for NUMRESULTS argument to FUZZY
- DRG-10843: invalid WEIGHT argument supplied to FUZZY
-
Cause: An invalid value was supplied for WEIGHT argument to FUZZY
- DRG-10844: index cannot execute this structured predicate efficiently
-
Cause: You specified a combination of condition and order by columns in a catsearch query which cannot be executed by the index's index set efficiently
- DRG-10845: column string is not indexed
-
Cause: You specified a column in a condition or order by which is not part of the ctxcat index
- DRG-10846: order by columns must be all ascending or all descending
-
Cause: You specified an order by clause which has some columns ascending and some descending. This is not currently supported by catsearch
- DRG-10847: catsearch requires prefix index for this type of query
-
Cause: For efficient execution of this Vgram query, we require presence of a prefix index.
- DRG-10848: invalid structured clause
-
Cause: you have specified an invalid structured clause
- DRG-10849: catsearch does not support functional invocation
-
Cause: the query plan for your query is invoking a catsearch operator functionally rather than as an index rowsource. The catsearch operator does not support functional invocation
- DRG-10850: CTXRULE indextype does not support the operator
-
Cause: Used an operator not supported by CTXRULE. Currently it only supports AND, NEAR, phrase, NOT, WITHIN, OR, ABOUT, EQUIVALENCE, STEM and THESAURUS operators
- DRG-10851: Invalid grammar string specified for query template
-
Cause: incorrect grammar specification
- DRG-10852: Invalid scoring type string specified for query template
-
Cause: incorrect scoring type specification
- DRG-10853: Catsearch does not support this operator
-
Cause: unsupported operator specified
- DRG-10854: Invalid scoring algorithm string specified for query template
-
Cause: incorrect scoring algorithm specification
- DRG-10855: CTXRULE indextype does not support the token type
-
Cause: Unsupported VGRAM token type 1.
- DRG-10856: SDATA section string does not exist
-
Cause: The given SDATA section name does not exist in USER_SECTIONS
- DRG-10857: literal is not compatible with the data type of the SDATA section
-
Cause: The given literal is not compatible with the data type of the specified SDATA section.
- DRG-10858: SDATA operator is not allowed in WITHIN
-
Cause: A field section or a attribute section is specified in a nested section search
- DRG-10859: Only one predefined scoring component can be used in DEFINESCORE
-
Cause: More than one predefined scoring component (i.e. RELEVANCE, OCCURRENCE, etc.) is used in the scoring expression of the DEFINESCORE operator
- DRG-10860: All expressions under the same WITHIN must use the same predefined scoring component
-
Cause: The query side of the same within mixes different types of scoring components(i.e. RELEVANCE, OCCURRENCE, etc.)
- DRG-10861: COMPLETION score must be used with WITHIN operator
-
Cause: The completion score is used without using the WITHIN operator
- DRG-10862: string attribute cannot be used with CTXRULE indexes
-
Cause: Used an attribute not supported by CTXRULE. This restriction is due to lack of wildcard support for CTXRULE indexes.
- DRG-10863: invalid ORDER argument supplied to NDATA
-
Cause: An invalid value was supplied for ORDER argument to NDATA
- DRG-10864: invalid PROXIMITY argument supplied to NDATA
-
Cause: An invalid value was supplied for PROXIMITY argument to NDATA
- DRG-10865: invalid datatype in user scoring expression
-
Cause: The scoring expression specified in DEFINESCORE or NORMALIZATION_EXPR in the query template either contains components with unsupported datatypes or does not return numerical values.
- DRG-10866: The right hand operand of MINUS cannot use IGNORE score
-
Cause: The IGNORE score is used as the right hand operand of MINUS
- DRG-10867: OCCURRENCE and COMPLETION score cannot be used with ABOUT in DEFINESCORE
-
Cause: The OCCURRENCE and COMPLETION score cannot be used with ABOUT queries
- DRG-10868: matches does not support functional invocation
-
Cause: the query plan for your query is invoking a matches operator functionally rather than as an index rowsource. The matches operator does not support functional invocation
- DRG-10869: Invalid span supplied to NEAR2 operator
-
Cause: Near2 span must be between 0 and 100
- DRG-10870: Invalid weight supplied to NEAR2 operator
-
Cause: Near2 weights must be between 0 and 10
- DRG-10871: NDATA operator not supported with string
-
Cause: NDATA operator is not supported in the specified operation
- DRG-10872: Characters cannot be outside string in an XML query
-
Cause: Charaters outside query element are not valid
- DRG-10873: Invalid characters location in the XML query
-
Cause: Charaters between certain elements are not allowed
- DRG-10874: Syntax error in XML Query Template
-
Cause: XML template is wrong. Possible causes include missing closing tag or receiving invalid attributes or characters.
- DRG-10875: Missing closing tag in XML Query
-
Cause: Some tag has been opened and not closed properly.
- DRG-10876: Invalid ordering of elements in XML Query
-
Cause: Occurrence of some element that should be only between another element that was not found
- DRG-10877: query should always start an XML Query
-
Cause: Either query is missing or is wrongly possitioned
- DRG-10878: Invalid ordering in XML Query: string should be string of string
-
Cause: Invalid ordering of tags as of specs
- DRG-10879: Invalid string element repetition in XML Query
-
Cause: Invalid repetition of XML element
- DRG-10880: Invalid nesting of string in XML Query
-
Cause: Invalid nesting of same element has been encountered
- DRG-10881: Invalid setting of savescore in ctxfiltercache
-
Cause: savescore argument must be true or false
- DRG-10882: Invalid setting of topn in ctxfiltercache
-
Cause: topn argument must be true or false
- DRG-10883: savescore must be true to use topn in ctxfiltercache
-
Cause: savescore must be true to use topn in ctxfiltercache
- DRG-10884: invalid use of ctxfiltercache with topn
-
Cause: ctxfiltercache with topn must be child of AND, THRESHOLD, or WEIGHT operators
- DRG-10885: ctxfiltercache operator requires non-zero query_filter_cache_size
-
Cause: used ctxfiltercache operator with zero query_filter_cache_size
- DRG-10886: topn must be used with order by score desc in ctxfiltercache
-
Cause: must order query results by score desc when topn argument is true
- DRG-10891: invalid MINREQD argument supplied to NEAR
-
Cause: An invalid value was supplied for MINREQD argument to NEAR
- DRG-10892: invalid THRESHOLD argument supplied to NDATA
-
Cause: An invalid value was supplied for the THRESHOLD argument to NDATA.
- DRG-10894: Missing regular expression in PATTERN
-
Cause: The syntax is PATTERN(regex). regex is missing.
- DRG-10895: Invalid regular expression in PATTERN
-
Cause: The syntax of the regular expression is incorrect
- DRG-10896: Regular expression specifies empty string in PATTERN
-
Cause: The expression ^$ has no match.
- DRG-10897: Regular expression matches too many words
-
Cause: The regular expression matches too many words.
- DRG-10898: ctxfiltercache is not supported with optimized for string SDATA
-
Cause: Used ctxfiltercache operator with unsupported SDATA.
- DRG-10900: out of memory
-
Cause: can not allocate more memory
- DRG-10901: memory deallocation failed
-
Cause: could not deallocate memory
- DRG-11000: invalid keyword string
-
Cause: A keyword was invalid.
- DRG-11001: missing keyword when expecting one of string
-
Cause: A keyword was missing.
- DRG-11002: missing value for string
-
Cause: A value for the argument was missing.
- DRG-11003: invalid value string for string
-
Cause: An invalid value was given for the argument
- DRG-11004: duplicate or conflicting value for string
-
Cause: More than one value has been specified for the argument
- DRG-11005: invalid create index parameter string
-
Cause: the supplied parameter string is not correct
- DRG-11006: invalid alter index parameter string
-
Cause: The parameter string was invalid.
- DRG-11007: multiple stopwords specified
-
Cause: Tried to add more than one stopword
- DRG-11008: invalid create index partition parameter string
-
Cause: The parameter string was invalid
- DRG-11009: parameter string is not supported at the partition level
-
Cause: The parameter is not supported at the partition level during index creation and index alteration
- DRG-11010: operator string is not supported for JSON
-
Cause: The operator is not supported for JSON
- DRG-11100: unable to connect to the database
-
Cause: failed to connect to Oracle database
- DRG-11101: failed to open file string
-
Cause: failed to open a file
- DRG-11102: assigned lexer can not operate on string language setting
-
Cause: Single byte lexer selected in multibyte language setting
- DRG-11104: Oracle Text error:
-
Cause: See the next error on stack
- DRG-11106: user database session has terminated during this operation
-
Cause: this database session does not exist or has terminated
- DRG-11107: invalid path specification: string
-
Cause: the path specified is not valid
- DRG-11108: invalid filename specified: string
-
Cause: the filename specified is not valid
- DRG-11109: assigned lexer does not support string query operator
-
Cause: This lexer does not support this query operator
- DRG-11111: value of string must be between string and string
-
Cause: You specified a value for the parameter which is out of range
- DRG-11112: length of string exceeds maximum of string
-
Cause: You specified a value for the parameter which is too long
- DRG-11113: value of string must be one of string
-
Cause: You specified a value for the parameter which is invalid
- DRG-11114: result table format is not correct for this operation
-
Cause: You specified a result table which has the wrong number, type, or names of columns for this operation.
- DRG-11115: a value for string must be specified
-
Cause: You did not specify a value for the parameter
- DRG-11116: value of string must be less than or equal to value of string
-
Cause: You specified values for the two parameters which are invalid
- DRG-11117: name is already used by an existing object
-
Cause: You tried to create an object whose name conflicts with an object of that type which already exists
- DRG-11118: object string does not exist
-
Cause: You tried to modify or drop an object which does not exist
- DRG-11119: operation is not supported by this index type
-
Cause: You tried to invoke an operation on an index which is not supported by the index type
- DRG-11120: failed to write to file string
-
Cause: failed to write to a file
- DRG-11121: failed to read from file string
-
Cause: failed to read from a file
- DRG-11122: unsupported section group
-
Cause: unsupported section group is specified for functional contains
- DRG-11123: theme indexing is not supported
-
Cause: theme indexing is on in the lexer preference for functional contains
- DRG-11124: invalid value string
-
Cause: you specified an invalid value
- DRG-11125: invalid format of existing log file string
-
Cause: the file specified by START_LOG already exists, and is not a previously written log file
- DRG-11126: context index is empty
-
Cause: the training table is empty or the context index of training table is not populated
- DRG-11127: inconsistent index policy with trained rule
-
Cause: the ctxrule index policy is inconsistent with the policy in which the rule was trained
- DRG-11128: invalid format of rule
-
Cause: the rule format is not valid for this operation
- DRG-11129: the rule table is empty
-
Cause: the rule table is empty
- DRG-11130: no data found in the collection
-
Cause: feature preparation program can not find any feature in the specified collection
- DRG-11131: Error from Oracle XML parser: string
-
Cause: The Oracle XML parser reported an error
- DRG-11132: Invalid character in logfile name
-
Cause: The logfile parameter to CTX_OUTPUT.START_LOG or CTX_OUTPUT.START_QUERY_LOG contains an invalid character (such as a forward slash)
- DRG-11133: failed to convert a datetime value [ora-number]
-
Cause: Failed to convert the datetime value.
- DRG-11134: The file string is currenly being used for logging by another process
-
Cause: The file is currently being used by another process.
- DRG-11135: feature not generally available
-
Cause: You tried to use a feature not generally available.
- DRG-11136: assigned lexer does not support entity extraction
-
Cause: This lexer does not support entity extraction
- DRG-11137: tracing is not supported on MTS
-
Cause: you tried to use ctx_output tracing in an MTS session
- DRG-11138: trace string is already enabled
-
Cause: you tried to enable a trace that is already enabled
- DRG-11139: trace string is not enabled
-
Cause: you tried to disable a trace that is not enabled
- DRG-11140: Section string is not MDATA
-
Cause: you tried to perform MDATA operation on non-mdata section
- DRG-11141: CTX_DDL.REMOVE_MDATA() and CTX_DDL.ADD_MDATA() not allowed for MDATA Section string
-
Cause: you tried to call CTX_DDL.REMOVE_MDATA() or CTX_DDL.ADD_MDATA() on a MDATA section which is created with ALLOW_ADD_REM parameter set to FALSE.
- DRG-11142: string cannot be string
-
Cause: The value for the specified parameter cannot be as specified
- DRG-11143: Only 64 errors can be traced
-
Cause: You tried to trace more than 64 errors with ctx_output
- DRG-11144: Invalid value for radius parameter: string
-
Cause: You specified invalid value for radius parameter
- DRG-11145: Invalid value for max_length parameter: string
-
Cause: You specified invalid value for max_length parameter
- DRG-11146: Invalid value for use_saved_copy: string
-
Cause: You specified invalid value for use_saved_copy parameter
- DRG-11147: Invalid lexer for ctx_doc.policy_stems
-
Cause: You specified/used a lexer which does not support ctx_doc.policy_stems
- DRG-11148: Invalid lexer for ctx_doc.policy_noun_phrases
-
Cause: You specified/used a lexer which does not support ctx_doc.policy_noun_phrases
- DRG-11149: Invalid lexer for ctx_doc.policy_part_of_speech
-
Cause: You specified/used a lexer which does not support ctx_doc.policy_part_of_speech
- DRG-11150: Reverse Index feature not enabled
-
Cause: Feature not enabled
- DRG-11151: Invalid value for max_inst in sentiment procedure
-
Cause: Sentiment procedure called with an invalid max_inst value.
- DRG-11152: Invalid value for type attribue in sentiment procedure
-
Cause: An invalid type attribute value was specified.
- DRG-11153: classifier string does not exist
-
Cause: The specified classifier did not exist.
- DRG-11154: topic cannot be null
-
Cause: The specified topic was null for a non-aggregate sentiment request.
- DRG-11155: Invalid Lexer for Default Sentiment Classifier
-
Cause: The specified lexer is not supported for the Default Sentiment Classifier.
- DRG-11156: user buffer too small
-
Cause: The user buffer is too small for the output data.
- DRG-11157: dataguide is not supported on MTS
-
Cause: you tried to create a dataguide enabled index in an MTS session
- DRG-11158: Only Path or NULL Section Group are allowed for inmemory text
-
Cause: you tried to use an invalid section group for inmemory text
- DRG-11159: JSON_ENABLE must be TRUE for inmemory text
-
Cause: Path Section Group must have json_enable true for inmemory text
- DRG-11160: Basic Lexer with index_themes is not allowed for inmemory text
-
Cause: Using a Basic Lexer with index_themes
- DRG-11161: Filter is not supported for inmemory text
-
Cause: Using an invalid Filter for inmemory text
- DRG-11162: Wordlist is not supported for inmemory text
-
Cause: Using an invalid Wordlist for inmemory text
- DRG-11163: JSON Dataguide flush failed
-
Cause: An internal error prevented JSON Dataguide information from being flushed to disk
- DRG-11164: Operator string is not supported with in-memory text index.
-
Cause: Using an operator that is not supported for in-memory text index.
- DRG-11165: Invalid Section Group with string Datastore for In-Memory Text.
-
Cause: When using Directory or Network Datastore, only NULL_SECTION_GROUP is allowed
- DRG-11166: Using JSON_ENABLE preference on an invalid column type.
-
Cause: An attempt was made to use Section Group's JSON_ENABLE preference on a non-JSON column.
- DRG-11203: INSO filter not supported on this platform
-
Cause: You tried to use the INSO filter on a platform which does not support it
- DRG-11204: user filter command is too long
-
Cause: The user filter command must be 32 characters or less
- DRG-11205: user filter command contains illegal characters
-
Cause: The user filter command cannot contain special characters such as slashes, parentheses, semicolons, etc.
- DRG-11206: user filter command string could not be executed
-
Cause: The user filter command could not be executed.
- DRG-11207: user filter command exited with status string
-
Cause: The user filter command exited with the given error status.
- DRG-11208: ORACLE_HOME is not set
-
Cause: ORACLE_HOME is not set
- DRG-11209: filename for string exceeds maximum length of string
-
Cause: Value of the file name is too long
- DRG-11210: format column must be a char, varchar, or varchar2 type
-
Cause: you specified a format column which is not a char, varchar, or varchar2 type.
- DRG-11211: charset column must be a char, varchar, or varchar2 type
-
Cause: you specified a charset column which is not a char, varchar, or varchar2 type.
- DRG-11212: procedure filter procedure name contains a semicolon
-
Cause: the procedure name specified had a semicolon
- DRG-11213: CTXSYS does not own procedure filter stored procedure: string
-
Cause: CTXSYS does not have execute privilege to the procedure filter stored procedure
- DRG-11214: execution of procedure filter stored procedure has failed
-
Cause: an error occur while executing the proedure filter stored procedure
- DRG-11215: index owner does not have access to filter stored procedure: string
-
Cause: the index owner does not have execute privilege of the procedure
- DRG-11216: length of datastore data exceeds limit
-
Cause: the length of the datastore data passed to the filter stored procedure is longer than the maximum length (32767 bytes)
- DRG-11217: INSO safe callout failed
-
Cause: The INSO safe callout cannot be executed
- DRG-11218: malformed mail line, line string
-
Cause: The mail message has an error at the indicated line
- DRG-11219: malformed mail configuration file, line string
-
Cause: mail filter configuration file has an error at the indicated line
- DRG-11220: Third-party filter is out of memory.
-
Cause: Third-party filter could not filter this document because it was unable to allocate sufficient virtual memory.
- DRG-11221: Third-party filter indicates this document is corrupted.
-
Cause: Third-party filter could not filter this document because this document is corrupted.
- DRG-11222: Third-party filter does not support this known document format.
-
Cause: Third-party filter was able to recognize the format of this document but could not filter it because this format is not supported.
- DRG-11223: Third-party filter indicates this document is password protected or encrypted.
-
Cause: Third-party filter encountered a password protected or encrypted document and could not filter it because this level of password protection or encryption is not supported.
- DRG-11224: Third-party filter is unable to create or write to temporary file.
-
Cause: Third-party filter could not filter this document because it was unable to create a temporary file or unable to write to a temporary file.
- DRG-11225: Third-party filter timed out.
-
Cause: Third-party filter could not filter this document because the filter timed out.
- DRG-11226: Error initializing third-party filter: string
-
Cause: There was an error initializing the third-party filter.
- DRG-11227: Third-party filter does not support this document format.
-
Cause: Third-party filter does not support the format of this document.
- DRG-11228: Charset filter does not support binary documents.
-
Cause: The format column specifies a binary document
- DRG-11229: configuration column must be a char, varchar, or varchar2 type
-
Cause: you specified a configuration column which is not a char, varchar, or varchar2 type.
- DRG-11301: error while indexing document
-
Cause: An error was encountered while indexing the document. The error may have occurred during lexing, parsing for sections, or other action during document tokenization
- DRG-11303: secondary indexes are not supported by this indextype
-
Cause: You attempted to create an index on an index-organized table, but the indextype does not support this action.
- DRG-11304: function-based indexes are not supported by this indextype
-
Cause: You attempted to create a function-based index but the indextype does not support this action.
- DRG-11305: create/alter index string is in progress in another session
-
Cause: you attempted to mark the index from INPROGRESS to FAILURE but create/alter on the same index is in progress in another session
- DRG-11306: operation cannot be performed on a policy
-
Cause: you attempted to perform an operation on a policy, but the operation is only valid for an index.
- DRG-11307: operation cannot be performed on an index
-
Cause: you attempted to perform an operation on an index, but the operation is only valid for a policy.
- DRG-11308: unsupported column expression string
-
Cause: You attempted to create an index with an unsupported column expression.
- DRG-11309: invalid filter by column: string of datatype string and size string
-
Cause: the column specified is not valid
- DRG-11310: invalid order by column: string of datatype string and size string
-
Cause: the column specified is not valid
- DRG-11311: string cannot be specified for this optimization mode
-
Cause: the specified option is not valid for this optimization mode
- DRG-11312: source and new policy must have same owner
-
Cause: the new policy has a different owner than the source policy
- DRG-11313: populate index error on index partition string
-
Cause: failed to polulate the text index on the specified partition
- DRG-11314: changing TRANSACTIONAL property on index with rows on pending queue not allowed
-
Cause: the index has pending unsynced rows
- DRG-11316: $S table cannot be created with string
-
Cause: the $S table cannot be created with the specified storage option
- DRG-11317: rowid string is not in the index
-
Cause: you specified an invalid rowid in ctx_ddl.add_mdata
- DRG-11318: error processing dr$sdata_update
-
Cause: there was an error
- DRG-11319: more than 1 index found on $I. OPTIMIZE REBUILD not supported
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11320: no index found on $I. OPTIMIZE REBUILD not supported
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11321: triggers detected on $I. OPTIMIZE REBUILD not supported
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11322: fast optimize not supported for big_io option
-
Cause: OPTIMIZE FAST is not supported with big_io option
- DRG-11323: merge optimize requires near_realtime option
-
Cause: OPTIMIZE MERGE requires near_realtime option
- DRG-11324: fast optimize not supported for separate_offsets option
-
Cause: OPTIMIZE FAST is not supported with separate_offsets option
- DRG-11325: stageitab only supported for context index
-
Cause: STAGEITAB requires context index
- DRG-11326: separate offsets only supported for context index
-
Cause: SEPARATE_OFFSETS requires context index
- DRG-11327: big_io only supported for context index
-
Cause: BIG_IO requires context index
- DRG-11328: optimize validation failed
-
Cause: optimize validation failed
- DRG-11332: Index already has STAGE_ITAB set
-
Cause: Index already has stage_itab set
- DRG-11333: Index does not have STAGE_ITAB set
-
Cause: Index does not have stage_itab set
- DRG-11334: Index already has BIG_IO set
-
Cause: Index already has big_io set
- DRG-11335: Index does not have BIG_IO set
-
Cause: Index does not have big_io set
- DRG-11336: Index already has SEPARATE_OFFSETS set
-
Cause: Index already has separate_offsets set
- DRG-11337: Index does not have SEPARATE_OFFSETS set
-
Cause: Index does not have separate_offsets set
- DRG-11338: policy string does not exist
-
Cause: the specified policy does not exist or you do not have access to it.
- DRG-11339: duplicate policy name: string
-
Cause: the specified policy already exists in the dictionary
- DRG-11341: Index optimization failed for one or more tokens
-
Cause: Index optimization generated an error for one or more tokens, possibly due to corruption of the token_info blob.
- DRG-11342: OPTIMIZE REBUILD not supported for partitioned $I and global $X
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11343: OPTIMIZE REBUILD not supported for current $I partitioning scheme
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11346: FORWARD INDEX only supported for context index
-
Cause: FORWARD INDEX needs context index
- DRG-11347: FORWARD INDEX does not exist for this index
-
Cause: FORWARD INDEX does not exist
- DRG-11348: OPTIMIZE REBUILD not supported for $I with character length semantics columns
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11349: FILTER CACHE only supported for context index
-
Cause: FILTER CACHE only for context index
- DRG-11350: SAVE COPY only supported for context index
-
Cause: SAVE COPY needs context index
- DRG-11351: Unable to fetch partition Id for given rowid: string
-
Cause: Not able to fetch partition id for given rowid
- DRG-11352: Not able to fetch partition name for given partition position: number
-
Cause: Not able to fetch partition name for given partition position
- DRG-11353: xml_enable is not allowed for a local index
-
Cause: Section group attribute xml_enable set to TRUE for a local index
- DRG-11354: stage_itab_max_rows not allowed without stage_itab storage preference
-
Cause: Storage option stage_itab_max_rows needs to be accompanied by stage_itab
- DRG-11355: Not able to fetch partition position from rowid: string
-
Cause: Not able to fetch partition position for given rowid
- DRG-11356: Optimize operations are not permitted on partition string
-
Cause: READ mode for this partition is set to FALSE. No optimize operations are permitted in this mode.
- DRG-11357: FORWARD INDEX must be specified at index, not partition level string
-
Cause: forward index was specified at partition level and not at index level
- DRG-11358: Save Copy must be specified at index, not partition level string
-
Cause: save copy was specified at partition level and not at index level
- DRG-11359: xml_save_copy can only be specified for xml enabled text index
-
Cause: xml_save_copy was specified for non-xml enabled text index
- DRG-11360: xml_forward_enable can only be specified for xml enabled text index
-
Cause: xml_forward_enable was specified for non-xml enabled text index
- DRG-11361: xml_forward_enable can not be enabled without xml_save_copy set to true
-
Cause: attempt to enable xml_forward_enable without xml_save_copy set to true
- DRG-11362: xml_enable is not allowed for non-XMLType columns
-
Cause: 'xml_enable' was set to TRUE for non-XMLType columns.
- DRG-11363: xml_enable is not allowed for XMLType OR storage
-
Cause: 'xml_enable' was set to TRUE for XMLType with object-relational storage.
- DRG-11364: index string is invisible
-
Cause: the index is marked as invisible. Only DML operations on the base table are allowed
- DRG-11365: FORWARD_INDEX cannot be specified for XML enabled text index.
-
Cause: The FORWARD_INDEX attribute was specified for an XML enabled text index.
- DRG-11366: SAVE_COPY cannot be specified for XML enabled text index.
-
Cause: The SAVE_COPY attribute was specified for an XML enabled text index.
- DRG-11367: Index is too fragmented to run optimize for all fragmented tokens.
-
Cause: More than 50% of tokens in $I are fragmented.
- DRG-11368: Invalid value for maxtokens attribute.
-
Cause: Maxtokens value was either less than zero or too high.
- DRG-11369: Stage itab row exceeds max allowable size.
-
Cause: Ctxagg optimize merge limits the size of rows to under 4K.
- DRG-11370: Error in optimize merge (ctxagg).
-
Cause: Internal error in optimize merge.
- DRG-11371: stage_itab_parallel not allowed without stage_itab storage preference
-
Cause: Storage option stage_itab_parallel needs to be accompanied by stage_itab
- DRG-11372: forward index storage preference cannot be specified with asynchronous update
-
Cause: Storage option Forward index specified along with asynchronous update
- DRG-11373: Invalid section type
-
Cause: Invalid section type parameter in optimize index
- DRG-11374: string not allowed when stage_itab_max_rows is set to 0.
-
Cause: Storage option specified is not allowed when stage_itab_max_rows is set to 0
- DRG-11375: string not allowed without stage_itab storage preference
-
Cause: Storage option specified needs to be accompanied by stage_itab
- DRG-11376: SIMPLIFIED_XML is not allowed with non xml enabled text index
-
Cause: Section group attribute XML_ENABLE not set to true when creating simplified XML Search Index
- DRG-11377: ADD_MDATA/REMOVE_MDATA API is not supported with stage_itab
-
Cause: Combination of features is not supported in this code version.
- DRG-11378: OPTIMIZE REBUILD not supported for Context Search index
-
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
- DRG-11379: invalid tablespace
-
Cause: Invalid tablespace specified in parameter list.
- DRG-11380: operation is not allowed on unsynced index
-
Cause: the index has pending unsynced rows
- DRG-11381: optimize fast mode is not supported in partitioned search index
-
Cause: The fast mode of opt is not supported for a partitioned search index
- DRG-11382: Cannot string a policy that is being used for an IMC Text column string
-
Cause: Attempt to drop or update a policy that is used on an IMC column.
- DRG-11383: string is not supported on a Sharded Database
-
Cause: Attempt to use an unsupported feature on a Sharded Database
- DRG-11384: cannot modify string option using partition granularity
-
Cause: An attempt was made to modify an option that can only be modified using global granularity or cannot be modified on a local index.
- DRG-11400: failed to parse document with key string
-
Cause: the document specified for linguistic extraction could not be parsed. This could indicate that the document is not well-formed English
- DRG-11403: primary key value too long
-
Cause: the primary key value parameter passed to the service request is longer than the maximum primary key length (64 bytes)
- DRG-11404: no primary key value specified
-
Cause: the primary key value parameter passed to the service request is null
- DRG-11410: could not insert into string result table
-
Cause: an ORACLE error occurred while linguistic output was being inserted into the result table
- DRG-11418: insufficient document content for linguistic parser
-
Cause: the document specified for linguistic extraction was parsed but the document content was insufficient for linguistic extraction by the specified parser.
- DRG-11422: linguistic initialization failed
-
Cause: linguistic services initialization failed
- DRG-11425: gist level string is invalid
-
Cause: invalid gist level
- DRG-11427: valid gist level values are string
-
Cause: Invalid gist level
- DRG-11428: document contains invalid characters
-
Cause: The document contains invalid characters
- DRG-11432: file error while accessing knowledge base
-
Cause: An oracle error was encountered during knowledge base access
- DRG-11435: primary key value is invalid
-
Cause: the primary key value parameter passed to the service request is not valid
- DRG-11439: index name length exceeds maximum of string bytes
-
Cause: the length of the index name is longer than the maximum index name size
- DRG-11440: operation not supported for the string language
-
Cause: the requested operation is not supported for the current language
- DRG-11441: gist numParagraphs string is invalid
-
Cause: invalid gist numparagraphs
- DRG-11442: valid gist numParagraphs values are string
-
Cause: invalid gist numparagraphs
- DRG-11443: gist maxPercent string is invalid
-
Cause: invalid gist max percent
- DRG-11444: valid gist maxPercent values are string
-
Cause: invalid gist max percent
- DRG-11445: rowid value is invalid: string
-
Cause: the rowid value parameter passed to the service request is not valid
- DRG-11446: supplied knowledge base file string not installed
-
Cause: Either using Oracle Express edition or supplied Knowledge Base was required but was not installed.
- DRG-11480: ctxkbtc memory allocation error: %(1)
-
Cause: Unable to allocate memory
- DRG-11481: linguistic feature not enabled
-
Cause: linguistic feature not enabled
- DRG-11500: column name expected, found string on line string
-
Cause: possibly miss-spelt column name or keyword
- DRG-11501: identifier string found in place of column name on line string
-
Cause: possibly miss-spelt column name
- DRG-11502: read of file failed at line string for file string
-
Cause: bad file name, wrong file_type or file system error
- DRG-11503: insert statement overflows maximum statement size
-
Cause: total length of statement exceeds database maximum
- DRG-11504: invalid longsize parameter of string specified
-
Cause: invalid option argument
- DRG-11505: long data on line string not found or invalid
-
Cause: either bad data or bad data file
- DRG-11506: record ignored on line string because of error(s)
-
Cause: an error occured parsing this row's data
- DRG-11507: file error trying to read file string
-
Cause: file not found or could not be read
- DRG-11508: bad or missing string token on line string
-
Cause: token expected was not found
- DRG-11509: value expected on line string
-
Cause: could not make sense of text where value expected
- DRG-11510: encountered unrecoverable error on line string
-
Cause: see previous messages
- DRG-11511: specified table does not contain a LONG RAW column
-
Cause: text must be inserted into a LONG RAW type column
- DRG-11512: bad syntax for thesaurus load file at line string
-
Cause: load file must have specific format for loading thesaurus
- DRG-11513: unable to open or write to file string
-
Cause: an attempt to open or to write to the given file failed
- DRG-11514: user string does not have UPDATE or SELECT privilege on string
-
Cause: user has not been granted UPDATE or SELECT privilege
- DRG-11515: not enough text key values
-
Cause: number of values provided does not match the number of text keys
- DRG-11516: user must be at least in role CTXUSER to perform this operation
-
Cause: user does not have CTXUSER, CXAPP or CTXADMIN role
- DRG-11517: error when validating text objects
-
Cause: see accompanying Oracle error
- DRG-11518: text table string does not have a LONG or LONG RAW column
-
Cause: table specified does not have a LONG or LONG RAW column
- DRG-11519: encounter error when exporting a LONG or LONG RAW column
-
Cause: see accompanying error message
- DRG-11520: error writing to file
-
Cause: file does not exist
- DRG-11521: encounter error when updating a LONG or LONG RAW column
-
Cause: see accompanying error message
- DRG-11522: no row exists for the text key(s) specified
-
Cause: no row in the table has the text key(s) specified
- DRG-11523: unable to lock the specified row for update
-
Cause: some other process has a lock on the row
- DRG-11524: primary key value is missing
-
Cause: primary key value is not provided
- DRG-11525: invalid commitafter parameter of string specified
-
Cause: invalid option argument
- DRG-11526: filename exceeds maximum length
-
Cause: value of the file name is too long
- DRG-11527: end token not found on line string
-
Cause: TEXTEND not found at end of record
- DRG-11528: LONG or LONG RAW column defintion found in structure data
-
Cause: could be misplaced
- DRG-11529: token exceeds maximum length
-
Cause: value of the column name or value is too long
- DRG-11530: token exceeds maximum length
-
Cause: value of the phrase or relation word is too long
- DRG-11531: start token not found on line string
-
Cause: <TEXTSTART: not found at start of record
- DRG-11532: error reading through end of line string for file string
-
Cause: characters encountered while reading through end of line
- DRG-11533: improper value of column string
-
Cause: value of the column is too long or mismatched quote
- DRG-11534: invalid column string
-
Cause: column does not exist or it's misspelled
- DRG-11535: error writing phrase or qualifier: string on line string to memory
-
Cause: not enough memory
- DRG-11600: URL store: string has permanently moved
-
Cause: the document referred to by the URL has permanently moved
- DRG-11601: URL store: bad syntax on request for string
-
Cause: client did not make correct request
- DRG-11602: URL store: access to string requires authentication
-
Cause: user has to provide password or other authentication
- DRG-11603: URL store: payment required to access string
-
Cause: payment is required before the URL can be accessed
- DRG-11604: URL store: access to string is denied
-
Cause: access to the URL is denied
- DRG-11605: URL store: document specified by string not found
-
Cause: the document can not be found on the host specified
- DRG-11606: URL store: access to string timed out waiting for client request
-
Cause: client did not make response within timeout period
- DRG-11607: URL store: access to string was denied due to garbled response
-
Cause: Web server identified in URL doesn't obey HTTP protocol
- DRG-11608: URL store: host portion of string specified incorrectly
-
Cause: host portion of the URL could not be parsed
- DRG-11609: URL store: unable to open local file specified by string
-
Cause: attempt to open local file failed
- DRG-11610: URL store: unable to read local file specified by string
-
Cause: attempt to read local file failed
- DRG-11611: URL store: unknown protocol specified in string
-
Cause: the protocol parsed is neither http or file
- DRG-11612: URL store: unknown host specified in string
-
Cause: the address of the host specified could not be resolved
- DRG-11613: URL store: connection refused to host specified by string
-
Cause: attempt to connect to host was forcibly refused
- DRG-11614: URL store: communication with host specified in string timed out
-
Cause: a network operation timed out
- DRG-11615: URL store: write failed sending to string over network
-
Cause: unknown error writing request to Web server
- DRG-11616: URL store: too many redirections trying to access string
-
Cause: too long a chain of HTTP redirections given the URL
- DRG-11617: URL store: URL string is too long
-
Cause: The length of the URL string is longer than URLSIZE
- DRG-11618: URL store: document identified by string is too large
-
Cause: document larger than user-set maximum size
- DRG-11619: URL store: row in table is empty
-
Cause: row deleted or otherwise missing
- DRG-11620: URL store: thread operation error
-
Cause: thread operation failed
- DRG-11621: URL store: socket open error for string
-
Cause: socket open failed; probably too many open file descriptors
- DRG-11622: URL store: getting string , unknown HTTP error string
-
Cause: an unexpected HTTP error has occurred
- DRG-11623: URL store: unknown error getting string
-
Cause: unexpected error
- DRG-11624: invalid attribute string for string: proper range string to string
-
Cause: unexpected error
- DRG-11625: MAXURLS * URLSIZE must be less than string
-
Cause: MAXURLS * URLSIZE cannot be larger than the limit
- DRG-11626: URL store: unknown protocol specified during redirect from string
-
Cause: the URL redirected to a site with neither http nor file protocol
- DRG-11627: URL store: not implemented error getting string
-
Cause: The remote host returned a 501 not implemented error
- DRG-11628: URL store: bad gateway error getting string
-
Cause: The remote host returned a 502 bad gateway error
- DRG-11629: URL store: service unavailable error getting string
-
Cause: The remote host returned a 503 service temporarily unavailable error
- DRG-11630: URL store: gateway timeout error getting string
-
Cause: The remote host returned a 504 gateway timeout error
- DRG-11700: thesaurus string already exists
-
Cause: thesaurus with same name exists
- DRG-11701: thesaurus string does not exist
-
Cause: thesaurus does not exist
- DRG-11702: string
-
Cause: error while parsing thesaurus operator in query term. see error message for details.
- DRG-11703: user string must have at least CTXAPP role to execute this function
-
Cause: privilege is not sufficient
- DRG-11704: phrase 'string' does not exist
-
Cause: phrase does not exist
- DRG-11705: multilevel jump from string to string
-
Cause: the thesaurus load file has a multilevel jump which could not be parsed.
- DRG-11706: invalid relation string
-
Cause: You specified an invalid relation. The set of valid relations will be displayed. Additionally, you may be able to specify a translation, which has the syntax languagename: where languagename can be any string up to 10 bytes
- DRG-11707: valid relations: string
-
Cause: You specified an invalid relation. The set of valid relations will be displayed. Additionally, you may be able to specify a translation, which has the syntax languagename: where languagename can be any string up to 10 bytes
- DRG-11708: too many thesauri
-
Cause: ctxkbtc cannot compile more than 16 thesauri
- DRG-11709: too many terms in thesaurus
-
Cause: number of thesaurus terms exceeds maximum
- DRG-11710: thesaurus term string too long
-
Cause: knowledge base does not permit terms longer than 80 characters
- DRG-11711: too much data for term string
-
Cause: internal limit on size of data per term
- DRG-11712: multiple Broader Terms for term string
-
Cause: There is a term in the thesaurus with multiple broader terms
- DRG-11713: multiple Preferred Terms per synonym ring
-
Cause: There is a synonym ring in the thesaurus with multiple preferred terms
- DRG-11714: synonyms have different Broader Terms
-
Cause: Some synonyms in a synonym ring have different broader terms
- DRG-11715: attempt to add a BT relation between 2 KB categories string and string
-
Cause: BT relation cannot be between two existing knowledge base categories
- DRG-11716: attempt to add Narrower Term string for non-Preferred Term string
-
Cause: only a PT can have NTs
- DRG-11717: attempt to add Related Term string to non-Preferred Term string
-
Cause: only a PT can have RTs
- DRG-11718: multiple Preferred Terms for term string
-
Cause: There are multiple preferred terms for this term
- DRG-11719: Broader Term hierarchy too deep
-
Cause: The broader term hierarchy in this thesaurus is too deep
- DRG-11720: too many synonyms per synonym ring
-
Cause: too many synonyms for a single preferred term
- DRG-11721: thesaurus string is empty
-
Cause: no entries in thesaurus
- DRG-11722: invalid language specification
-
Cause: language specification cannot be more than 10 characters
- DRG-11723: phrase cannot be NULL
-
Cause: you tried to add a NULL phrase to the thesaurus
- DRG-11724: phrase string already exists
-
Cause: phrase with same name exists
- DRG-11725: phrase does not have any synonyms
-
Cause: you tried to nominate a phrase with no synonyms to be the preferred term, or you tried to drop SYN from a phrase with no synonyms
- DRG-11726: phrase is not a preferred term
-
Cause: you tried to remove the preferred term relation from a phrase which is not a preferred term.
- DRG-11727: phrase does not have any related terms
-
Cause: you tried to drop a relation which does not exist
- DRG-11728: phrase does not have any broader terms of this type
-
Cause: you tried to drop a relation which does not exist
- DRG-11729: phrase does not have any narrower terms of this type
-
Cause: you tried to drop a relation which does not exist
- DRG-11730: relation does not exist
-
Cause: you tried to drop a relation which does not exist
- DRG-11731: translation does not exist
-
Cause: you tried to drop a translation which does not exist
- DRG-11732: phrase does not have any translations
-
Cause: you tried to drop translations which does not exists
- DRG-11733: more than one translation for the term in the specified language
-
Cause: the term has more than one translation in the specified language
- DRG-11734: missing homograph
-
Cause: A term of the form 'homograph(disambiguation)' is missing the the homograph.
- DRG-11735: missing disambiguation
-
Cause: A term of the form 'homograph(disambiguation)' is missing the the disambiguation (i.e., homograph()).
- DRG-11736: illegal text after disambiguated homograph
-
Cause: A term of the form 'homograph(disambiguation)' has text after the disambiguation (e.g, homograph(disambiguation) extra text".
- DRG-11737: Unsupported attribute value for thes_toktype
-
Cause: An invalid value was specified for thes_toktype attribute.
- DRG-11801: Continue
-
Cause: Enquire user to decide if continue is necessary HTTP_ERROR = 100
- DRG-11802: Switching Protocols
-
Cause: Telling client a protocol switching just happened HTTP_ERROR = 101
- DRG-11803: OK
-
Cause: Telling client things are ok HTTP_ERROR = 200
- DRG-11804: Created
-
Cause: Telling client things are created HTTP_ERROR = 201
- DRG-11805: Accepted
-
Cause: Telling client things are accepted but not commited HTTP_ERROR = 202
- DRG-11806: Non-authoritative Information
-
Cause: The returned metainformation is not the definitive set HTTP_ERROR = 203
- DRG-11807: No Content
-
Cause: request has been fulfilled but no new information found HTTP_ERROR = 204
- DRG-11808: Reset Content
-
Cause: Telling client to reset the document view HTTP_ERROR = 205
- DRG-11809: Partial Content
-
Cause: Telling client document content is a patial content HTTP_ERROR = 206
- DRG-11810: Partial Update OK
-
Cause: Telling client document is partially updated HTTP_ERROR = 207
- DRG-11811: Multiple Choices
-
Cause: Telling client multiple choices of resources is possible HTTP_ERROR = 300
- DRG-11812: Moved Permanently
-
Cause: The URI has been assigned a new permanent URI HTTP_ERROR = 301
- DRG-11813: Moved Temporarily
-
Cause: The URI resides temporarily under a different URI. HTTP_ERROR = 302
- DRG-11814: See Other
-
Cause: The URI can be found using GET METHOD under a different URI HTTP_ERROR = 303
- DRG-11815: Not Modified
-
Cause: Response to conditional GET, indicating document not modified. HTTP_ERROR = 304
- DRG-11816: Use Proxy
-
Cause: The client should use specified proxy to repeat the request HTTP_ERROR = 305
- DRG-11817: Proxy Redirect
-
Cause: Proxy redirection. Not used HTTP_ERROR = 306
- DRG-11818: Temporary Redirect
-
Cause: The resource is temporarily under a different URI. HTTP_ERROR = 307
- DRG-11819: Bad Request
-
Cause: The URL syntax is incorrect. Request rejected by server. HTTP_ERROR = 400
- DRG-11820: Unauthorized
-
Cause: The request requires further authentication. HTTP_ERROR = 401
- DRG-11821: Payment Required
-
Cause: Reserved for future use. HTTP_ERROR = 402
- DRG-11822: Forbidden
-
Cause: The server refuses to fulfil the request from client HTTP_ERROR = 403
- DRG-11823: Not Found
-
Cause: The server can not find the requested URI HTTP_ERROR = 404
- DRG-11824: Method Not Allowed
-
Cause: The user agent specified method not allowed HTTP_ERROR = 405
- DRG-11825: Not Acceptable
-
Cause: Requested resource is not acceptable according to request header HTTP_ERROR = 406
- DRG-11826: Proxy Authentication Required
-
Cause: The client must authenticate itself with the proxy. HTTP_ERROR = 407
- DRG-11827: Request Timeout
-
Cause: The server is tired of waiting for the requst HTTP_ERROR = 408
- DRG-11828: Conflict
-
Cause: The request conflicts with the current state of the URI HTTP_ERROR = 409
- DRG-11829: Gone
-
Cause: The resource is no longer available and no forwarding address. HTTP_ERROR = 410
- DRG-11830: Length Required
-
Cause: The server must receive a content-length header. HTTP_ERROR = 411
- DRG-11831: Precondition Failed
-
Cause: Telling the user agent that the resource failed preconditions HTTP_ERROR = 412
- DRG-11832: Request Entity Too Large
-
Cause: Request rejected because request entity is too large. HTTP_ERROR = 413
- DRG-11833: Request-URI Too Big
-
Cause: The server is refusing to accept the URI which is too big. HTTP_ERROR = 414
- DRG-11834: Unsupported Media Type
-
Cause: The server is refusing the request because of media type HTTP_ERROR = 415
- DRG-11835: Requested Range Not Satisfiable
-
Cause: The byte range request can not be satisfied by the resource extent. HTTP_ERROR = 416
- DRG-11836: Expectation Failed
-
Cause: Server can not meet the user agent's expectation. HTTP_ERROR = 417
- DRG-11837: Reauthorization Required
-
Cause: Reserved HTTP_ERROR = 418
- DRG-11838: Proxy Reauthentication Required
-
Cause: Reserved HTTP_ERROR = 419
- DRG-11839: Internal Server Error
-
Cause: The server encountered internal error in fulfilling the request. HTTP_ERROR = 500
- DRG-11840: Not Implemented
-
Cause: The server can't support a request feature which has yet to be implemented. HTTP_ERROR = 501
- DRG-11841: Bad Gateway
-
Cause: In serving the request, the server received invalid response from gateway. HTTP_ERROR = 502
- DRG-11842: Service Unavailable
-
Cause: Server overloaded or in maintenance mode. HTTP_ERROR = 503
- DRG-11843: Gateway Timeout
-
Cause: Upstream server did not timely respond to the gateway server. HTTP_ERROR = 504
- DRG-11844: HTTP Version Not Supported
-
Cause: The HTTP version in the request header is rejected by the server. HTTP_ERROR = 505
- DRG-11845: No Partial Update
-
Cause: Reserved HTTP_ERROR = 506
- DRG-11846: Response Is Stale
-
Cause: The the user agent knows the returned reponse is stale. HTTP_CACHE_ERROR = 10
- DRG-11847: Revalidation Failed
-
Cause: User agent's attempt to revalidate a stale response failed. HTTP_CACHE_ERROR = 11
- DRG-11848: Disconnected Operation
-
Cause: The cache is intentionally disconnected for a time period. HTTP_CACHE_ERROR = 12
- DRG-11849: Heuristic Expiration
-
Cause: Cache freshness lifetime and response age both greater than 24 hours. HTTP_CACHE_ERROR = 13
- DRG-11850: Transformation Applied
-
Cause: Telling cache manager, content encoding/media type has been changed in cache. HTTP_CACHE_ERROR = 14
- DRG-11851: Cache Related Warning
-
Cause: Arbitrary information about cache to be presented to logger. HTTP_CACHE_ERROR = 99
- DRG-11852: Can't Locate Remote Host
-
Cause: connection to remote host failed USER_AGENT_ERROR
- DRG-11853: No Host Name Found
-
Cause: The host name is not specicied in URI. USER_AGENT_ERROR
- DRG-11854: No File Name Found Or File Not Accessible
-
Cause: Unable to open the file specified USER_AGENT_ERROR
- DRG-11855: FTP Server Replies
-
Cause: FTP server responds to the agent request USER_AGENT_ERROR
- DRG-11856: FTP Server Doesn't Reply
-
Cause: No response from FTP server during operation. USER_AGENT_ERROR
- DRG-11857: Server Timed Out
-
Cause: Server operation timed out USER_AGENT_ERROR
- DRG-11858: Gopher Server Replies
-
Cause: Gopher server responds to the agent request. USER_AGENT_ERROR
- DRG-11859: Data Transfer Interrupted
-
Cause: Processing of URL request was interrupted USER_AGENT_ERROR
- DRG-11860: Connection Establishment Interrupted
-
Cause: Connection operation was interupped USER_AGENT_ERROR
- DRG-11861: CSO-server Replies
-
Cause: Telling client things are ok USER_AGENT_ERROR
- DRG-11862: This Is Probaly A HTTP Server 0.9 Or Less
-
Cause: A very old web server USER_AGENT_ERROR
- DRG-11863: Bad, Incomplete, Or Unknown Response
-
Cause: The server is mumbering something not understandable USER_AGENT_ERROR
- DRG-11864: Unknown Access Authentication Scheme
-
Cause: The server is using an unkown access authentication scheme USER_AGENT_ERROR
- DRG-11865: News Server Replies
-
Cause: News Server is responding USER_AGENT_ERROR
- DRG-11866: Please Try `ftp://' Instead Of `file://'
-
Cause: wrong access scheme is used. USER_AGENT_ERROR
- DRG-11867: Method Not Suited For Automatic Redirection
-
Cause: Telling client things are ok USER_AGENT_ERROR
- DRG-11868: Too Many Redirections
-
Cause: The web server setup configured too many redirections USER_AGENT_ERROR
- DRG-11869: Premature End Of File Detected
-
Cause: Detected end of file is unexpected USER_AGENT_ERROR
- DRG-11870: Response From WAIS Server Too Large -- Extra Lines Ignored
-
Cause: Response from WAIS caused buffer overflow USER_AGENT_ERROR
- DRG-11871: WAIS Server Doesn't Return Any Data
-
Cause: Bad WAIS Server USER_AGENT_ERROR
- DRG-11872: Can't Connect To WAIS Server
-
Cause: Connect to WAIS server failed USER_AGENT_ERROR
- DRG-11873: System Call Replies
-
Cause: register what system call replies USER_AGENT_ERROR
- DRG-11874: Wrong Or Unknown Access Scheme
-
Cause: Protocol class is wrongfully connected to ther server USER_AGENT_ERROR
- DRG-11875: Access Scheme Is Not Allowed
-
Cause: Telling client things are ok USER_AGENT_ERROR
- DRG-11876: When Your Are Connected, You Can Log In
-
Cause: Pass information to telnet agent USER_AGENT_ERROR
- DRG-11877: This Cache Version Has Expired And Will Be Automatically Reloaded
-
Cause: Need to tell user that cache entry has been reloaded USER_AGENT_ERROR
- DRG-11878: Loading New Rules Must Be Explicitly Acknowledged
-
Cause: Let user agent client be aware of new rule loading USER_AGENT_ERROR
- DRG-11879: Automatic Proxy Redirection Msut Be Explicitly Acknowledged
-
Cause: Let user agent client be aware of proxy redirection USER_AGENT_ERROR
- DRG-12001: Please enter username:
-
Cause: Prompt user for name W3CLIB_MSG = 0
- DRG-12002: Please enter username for proxy authentication:
-
Cause: Prompt user for name W3CLIB_MSG = 1
- DRG-12003: Please enter username for this FTP server:
-
Cause: Prompt user for name W3CLIB_MSG = 2
- DRG-12004: Password:
-
Cause: Prompt user for password W3CLIB_MSG = 3
- DRG-12005: Please give name of file to save in:
-
Cause: Prompt user for file name W3CLIB_MSG = 4
- DRG-12006: Plase enter account:
-
Cause: Prompt user for account W3CLIB_MSG = 5
- DRG-12007: You might not be allowed to use this method here, continue?
-
Cause: Warn user of deny of service. W3CLIB_MSG = 6
- DRG-12008: Location has moved, continue?
-
Cause: Warn user of location changes. W3CLIB_MSG = 7
- DRG-12009: A new set of rules is requested to be added to your setup - continue?
-
Cause: Warn user of rule changes. W3CLIB_MSG = 8
- DRG-12010: This file already exists - replace existing file?
-
Cause: Warn user of pending replacement W3CLIB_MSG = 9
- DRG-12011: Authentication failed - retry?
-
Cause: Warn user of authentication failure W3CLIB_MSG = 10
- DRG-12012: Proxy authentication failed - retry?
-
Cause: Warn user of proxy authentication failure W3CLIB_MSG = 11
- DRG-12013: This method has already been performed - repeat operation?
-
Cause: Warn user the repetition of previous method used W3CLIB_MSG = 12
- DRG-12014: This document is very big - continue operation?
-
Cause: Warn user of big document processing W3CLIB_MSG = 13
- DRG-12015: The source document for this operation has moved - continue?
-
Cause: Warn user of location changes W3CLIB_MSG = 14
- DRG-12016: The target document for this operation has moved - continue?
-
Cause: Warn user of destination document changes W3CLIB_MSG = 15
- DRG-12017: A redirection may change the behavior of this method - proceed anyway?
-
Cause: Warn user of redirection effects on method W3CLIB_MSG = 16
- DRG-12018: Encountered an automatic request for changing proxy - continue?
-
Cause: Warn user of automatic proxy change W3CLIB_MSG = 17
- DRG-12201: section group string already exists
-
Cause: Section group with the same name already exists
- DRG-12202: error while creating section group
-
Cause: detect an Oracle error while creating section group
- DRG-12203: section group string does not exist
-
Cause: section group provided does not exist
- DRG-12204: error while dropping section group string
-
Cause: detect an Oracle error while dropping a section group
- DRG-12205: error with sdata columns
-
Cause: detect an Oracle error while creating sdata columns
- DRG-12206: tag string already exists in section group string
-
Cause: the start tag provided already exists in the same Section
- DRG-12210: error while adding section string
-
Cause: detect an Oracle error while adding a section
- DRG-12211: section or section id string does not exist
-
Cause: Section name or Section id to be dropped does not exist
- DRG-12212: error while dropping section string
-
Cause: detect an Oracle error while dropping a Section
- DRG-12213: cannot create/drop section group or sections for other user
-
Cause: You can only create/drop section group objects of your own
- DRG-12217: tags cannot be more than 64 bytes
-
Cause: max limit of start and end tag is 64 bytes
- DRG-12218: section group name missing
-
Cause: must provide section group name
- DRG-12219: section name missing
-
Cause: must provide Section name when creating a Section
- DRG-12220: a valid tag must be provided
-
Cause: must provide tag when adding a section to a section group
- DRG-12223: section name string is a reserved name
-
Cause: you tried to name a section a reserved name
- DRG-12224: use ctx_ddl.create_section_group to create section groups
-
Cause: you tried to use ctx_ddl.create_preference to create a section group
- DRG-12225: this type of section cannot be added to this section group
-
Cause: You tried to add sections to the null section group, add a stop section to a non-auto section group, or add a zone or field section to the auto section group
- DRG-12226: a field section named string already exists in this section group
-
Cause: you tried to name an attribute or zone section the same name as an existing field section
- DRG-12227: a zone section named string already exists in this section group
-
Cause: you tried to name an attribute or field section the same name as an existing zone section
- DRG-12228: maximum number of field sections (string) exceeded
-
Cause: a section group has more than the maximum number of unique field sections
- DRG-12229: special section string already exists in this section group
-
Cause: you tried to add a special section which already exists
- DRG-12230: special section name must be one of string
-
Cause: you tried to add an invalid special section
- DRG-12231: an attr section named string already exists in this section group
-
Cause: you tried to name a field or zone section the same name as an existing attribute section
- DRG-12232: invalid attribute tag format
-
Cause: you specified a tag for use as an attribute tag which did not have the correct format. An attribute tag must have the form TAG@ATTR
- DRG-12233: xml sections cannot co-exist with other section types
-
Cause: you tried to add an xml section to a section group or index which already has zone, field, attr, or special sections, or you tried to add a zone, field, attr, or special section to a section group or index which already has xml sections
- DRG-12234: column string already mapped in section group string
-
Cause: you tried to add a column section which already exists
- DRG-12235: an sdata section named string already exists in this section group
-
Cause: you tried to name a non-sdata section the same name as an existing sdata section
- DRG-12236: an mdata section named string already exists in this section group
-
Cause: you tried to name a non-mdata section the same name as an existing mdata section
- DRG-12237: a section named string already exists in this section group
-
Cause: you tried to map a column but the section name is already being used by another section
- DRG-12238: maximum number of mdata sections (string) exceeded
-
Cause: a section group has more than the maximum number of unique mdata sections
- DRG-12239: maximum number of sdata sections (string) exceeded
-
Cause: a section group has more than the maximum number of unique sdata sections
- DRG-12240: ORDER BY column string must be indexed as an SDATA section
-
Cause: an order by column has been mapped to an MDATA section
- DRG-12241: column name string is not a valid section name
-
Cause: an order by or filter by column cannot be implicitly mapped to an SDATA section because the name is not valid as a section name
- DRG-12242: value of string is too large for section string
-
Cause: the value of a filter by or order by column is too large to be indexed
- DRG-12243: invalid datatype
-
Cause: the datatype specified for a sdata or mdata section is invalid
- DRG-12244: data conversion error for sdata section string
-
Cause: failed to convert data
- DRG-12245: SDATA operator not compatible with the sdata section string
-
Cause: failed to convert data
- DRG-12246: SDATA operand not compatible with the sdata section string
-
Cause: failed to convert data
- DRG-12247: maximum number of NDATA sections (string) exceeded
-
Cause: a section group has more than the maximum number of unique NDATA sections
- DRG-12248: a NDATA section named string already exists in this section group
-
Cause: you tried to name a non-NDATA section the same name as an existing NDATA section
- DRG-12253: optimized for string SDATA sections do not support string operation
-
Cause: An attempt was made to use an operation that is not supported for these SDATA sections.
- DRG-12254: order by for SDATA optmized for search only is not allowed
-
Cause: An attempt was made to use a query ordering by SDATA section that is optimized for search only.
- DRG-12255: invalid data type for SDATA section string
-
Cause: The data type of the SDATA section in the XML enabled context index was invalid.
- DRG-12256: SDATA section string is not optimized for search
-
Cause: Section attribute 'optimized_for' was not set to 'search' for the SDATA section in the XML enabled context index.
- DRG-12257: RANGE_SEARCH_ENABLE cannot co-exist with other section types.
-
Cause: An attempt was made to create an index with a section group having both RANGE_SEARCH_ENABLE on and other sections such as Attribute, Field, MDATA, NDATA, SDATA, Special, or Zone section.
- DRG-12258: sdata section string is too long
-
Cause: data too long for sdata section
- DRG-12300: an index with this column list already exists in the index set
-
Cause: You tried to add an index to an index set, but an index with the specified column list already exists
- DRG-12301: index does not exist in index set
-
Cause: You tried to remove an index from an index set, but the specified index was not found
- DRG-12302: invalid column list
-
Cause: You specified an invalid column list -- it may have a syntax error, duplicate columns, or invalid column names
- DRG-12303: cannot add more than 99 indexes to an index set
-
Cause: You tried to add too many indexes to the index set
- DRG-12304: index set string does not exist
-
Cause: You specified an invalid index set name
- DRG-12305: column string data type is not supported for index set columns
-
Cause: You specified a column in the column list of an index of an index set which does not have a valid datatype
- DRG-12306: column string is too long for index set columns
-
Cause: You specified a column in the column list of an index of an index set which is too long
- DRG-12307: column string is NULL and cannot be indexed
-
Cause: You tried to index a row where at least one of the meta columns was NULL.
- DRG-12308: use ctx_ddl.create_index_set to create index sets
-
Cause: you tried to use ctx_ddl.create_preference to create an index set
- DRG-12309: not to use compression on attributes lob column
-
Cause: you tried to use compression on attributes lob column for xml full text index
- DRG-12310: index set name exceeds maximum size of string
-
Cause: Index set name is too many bytes
- DRG-12400: template string is empty
-
Cause: The template is empty.
- DRG-12401: invalid template: query within a loop
-
Cause: A CTX EXEC tag cannot occur within a CTX REPEAT tag.
- DRG-12402: error processing template string, line string
-
Cause: An error occurred when processing a template.
- DRG-12403: template string was not found
-
Cause: The template does not exist.
- DRG-12404: more than one template string found
-
Cause: More than one template with the same name was found.
- DRG-12405: error occurred processing CTX REDIRECT or CTX LABEL tag
-
Cause: Error in syntax of a tag.
- DRG-12406: invalid CTX EXEC tag attribute (string)
-
Cause: The specified attribute is incorrectly specified.
- DRG-12407: invalid CTX REPEAT tag attribute (string)
-
Cause: The specified attribute is incorrectly specified.
- DRG-12408: invalid variable reference: string.string
-
Cause: The variable referenced does not exist.
- DRG-12409: syntax error for label in string
-
Cause: The SQL in a CTX EXEC tag has incorrect syntax for a label or label type.
- DRG-12410: could not process CTX EXEC tag
-
Cause: An error occurred when processing the SQL attribute of a CTX EXEC tag.
- DRG-12411: SQL processing error: string
-
Cause: Error executing SQL from SQL attribute of CTX EXEC tag.
- DRG-12412: missing or invalid Template Processor attribute (string)
-
Cause: The specified attribute was missing or invalid in a HTML input field.
- DRG-12422: write to client failed
-
Cause: See the following messages.
- DRG-12430: mandatory argument missing: string
-
Cause: This argument is mandatory.
- DRG-12431: configuration section string not found
-
Cause: Specified conf argument is invalid.
- DRG-12432: configuration file string not found or unreadable
-
Cause: An error occurred when processing the configuration file.
- DRG-12433: load of string JDBC driver class failed
-
Cause: Driver class is invalid.
- DRG-12434: connection failed using configuration string information
-
Cause: Configuration information is not correct.
- DRG-12435: highlight table allocation failed
-
Cause: See the following messages.
- DRG-12436: document table allocation failed
-
Cause: See the following messages.
- DRG-12437: highlight table release failed
-
Cause: See the following messages.
- DRG-12438: document table release failed
-
Cause: See the following messages.
- DRG-12439: highlight table read failed
-
Cause: See the following messages.
- DRG-12440: document table read failed
-
Cause: See the following messages.
- DRG-12441: counting the number of highlights failed
-
Cause: See the following messages.
- DRG-12500: stoplist string already exists
-
Cause: the specified stop list already exists
- DRG-12501: null stoplist is not allowed
-
Cause: the specified stop list is null
- DRG-12502: cannot modify stoplists owned by other users
-
Cause: You can only create/drop Stop List or Stop Word objects of your own
- DRG-12503: error while creating or dropping stoplist
-
Cause: detect an Oracle error while creating Stop List
- DRG-12504: stoplist string does not exist
-
Cause: the specified stop list does not exist
- DRG-12505: error while adding or removing a stop word
-
Cause: detect an Oracle error while adding or removing Stop Word
- DRG-12506: stop word string does not exist in stoplist string
-
Cause: the specified Stop Sord does not exist
- DRG-12507: stop word string already exists in this stoplist
-
Cause: the specified stop word already exists
- DRG-12508: null stop words are not allowed
-
Cause: the specified stop word is null
- DRG-12509: length of the stop word string exceeded the limit of string bytes
-
Cause: A stop list entry has exceeded the maximun length
- DRG-12511: use ctx_ddl.create_stoplist to create stoplists
-
Cause: you tried to use ctx_ddl.create_preference to create a stoplist
- DRG-12512: invalid stop class string
-
Cause: you specified an invalid stop class
- DRG-12513: valid stop classes are: string
-
Cause: You specified an invalid stop class
- DRG-12514: languages must be specified for stopwords in a MULTI_STOPLIST
-
Cause: You tried to add a stopword to a multi_stoplist without specifying the language of the stopword
- DRG-12515: cannot specify language for stopwords in a BASIC_STOPLIST
-
Cause: You tried to add a language-specific stopword to a basic stoplist.
- DRG-12516: language column must be specified when using the multi stoplist
-
Cause: you tried to create an index using a multi stoplist but you did not specify a language column
- DRG-12517: cannot add stopthemes to a MULTI_STOPLIST
-
Cause: you tried to add a stoptheme to a MULTI_STOPLIST. This is not supported in this version.
- DRG-12518: cannot use this option with MULTI_STOPLIST
-
Cause: index already has multi_stoplist
- DRG-12519: LANGUAGE COLUMN missing
-
Cause: index does not have a language column
- DRG-12520: LANGUAGE COLUMN mismatch
-
Cause: LANGUAGE COLUMN does not match language column of the Index
- DRG-12521: cannot add STOP PATTERN to NUMBERS stopclass
-
Cause: NUMBERS is a predefined stopclass to specify numeric values
- DRG-12522: stop class name cannot have a reserved symbol
-
Cause: character AMPERSAND is not supported for stop class name
- DRG-12600: user datastore procedure name contains a semicolon
-
Cause: the procedure name specified had a semicolon
- DRG-12601: invalid user datastore procedure name: string
-
Cause: the format of the procedure name is invalid. It should be in the form PACKAGENAME.PROCEDURENAME or PROCEDURENAME
- DRG-12602: index owner does not have access to user datastore procedure: string
-
Cause: the index owner does not have execute privilege of the procedure
- DRG-12603: CTXSYS does not own user datastore procedure: string
-
Cause: CTXSYS does not have execute privilege to the user datastore procedure
- DRG-12604: execution of user datastore procedure has failed
-
Cause: an error occur while executing the user datastore procedure
- DRG-12605: datatype of column number in COLUMNS list is not supported
-
Cause: one or more of the columns in the column list of the multi datastore are of a type which the multi datastore is unable to process
- DRG-12606: error encountered while parsing COLUMNS list
-
Cause: An oracle error was encountered while parsing the columns list of the multi datastore.
- DRG-12607: only ctxsys can create MULTI_COLUMN preferences
-
Cause: In order to create a multi column datastore preference, the effective user must be ctxsys.
- DRG-12700: seed word must be a single word
-
Cause: seed word is not a single word
- DRG-12800: Attribute NESTED_TYPE must have owner name as prefix
-
Cause: the attribute NESTED_TYPE does not have an owner name prefix
- DRG-12801: invalid type: string
-
Cause: invalid nested_type or
- DRG-12802: invalid type column: string
-
Cause: column specified does not exist in the type table
- DRG-12803: invalid text datatype
-
Cause: LONG and LONG RAW are not supported in nested table
- DRG-12900: Operation:string for index: string has already been started
-
Cause: the specified operation has been started
- DRG-13000: error while adding or removing a sub lexer
-
Cause: see next error
- DRG-13001: sub lexer and multi lexer must have the same owner
-
Cause: you specified a sub lexer which is not owned by the owner of the enclosing multi-lingual lexer preference
- DRG-13002: preference string is not a MULTI_LEXER
-
Cause: you tried to add a sub lexer to a lexer preference which cannot accept sub lexers. Only multi-lingual lexers can accept sub lexers.
- DRG-13003: preference string cannot be used as a sub lexer
-
Cause: you specified a preference for sub lexer which is not a lexer, or is a multi-lingual lexer or is an auto lexer
- DRG-13004: language is invalid
-
Cause: you specified an invalid language for the sub lexer or stopword
- DRG-13005: alt_value cannot be an NLS language name
-
Cause: you specified an NLS language name as the alt value
- DRG-13006: sub lexer for this language is not defined
-
Cause: you tried to remove a sub lexer for a language, but no sub lexer was defined for that language
- DRG-13007: cannot define an alternate value for the DEFAULT sub lexer
-
Cause: you tried to define an alternate value for the DEFAULT sub lexer
- DRG-13008: cannot remove the DEFAULT sub lexer
-
Cause: you tried to remove the DEFAULT sub lexer
- DRG-13009: multi lexer preference does not have a DEFAULT sub lexer
-
Cause: you tried to use a multi lexer preference which does not have a DEFAULT sub lexer defined
- DRG-13010: alt_value is already used by another sub lexer
-
Cause: you tried to specify an alt value which is already in use by another sub lexer in the lexer preference
- DRG-13011: language column must be specified when using the multi lexer
-
Cause: you tried to create an index using a multi lexer preference, but you did not specify a language column
- DRG-13012: language column must be a char, varchar, or varchar2 type
-
Cause: you specified a language column which is not a char, varchar, or varchar2 type.
- DRG-13013: cannot have language independent DEFAULT sub lexer
-
Cause: you tried to define a language independent DEFAULT sub lexer
- DRG-13014: base table has rows with language column value string
-
Cause: there are documents in the base table with language column value set to symbol for sublexer or stopword being removed
- DRG-13015: sublexer string already exists in the index
-
Cause: cannot add a sub_lexer more than once
- DRG-13100: index is not partitioned
-
Cause: you attempted to invoke a partition-level operation on an index which is not partitioned
- DRG-13101: partition string does not exist in this index
-
Cause: you specified a partition name which does not exist
- DRG-13102: index partition name must be specified
-
Cause: you attempted to invoke a partition-level operation on a partitioned index but did not specify the partition name
- DRG-13103: index table string is partitioned
-
Cause: you attempted to perform an exchange partition including indexes, but one or more of the internal index tables are partitioned.
- DRG-13104: indexes do not have equivalent settings for string
-
Cause: you attempted to perform an exchange partition including indexes, but the specified metadata setting is not equivalent across the two indexes, so the data cannot be exchanged
- DRG-13200: failed to load dictionary file string
-
Cause: failed to load a dictionary file
- DRG-13201: KOREAN_LEXER is desupported
-
Cause: Using lexer type KOREAN_LEXER which is desupported.
- DRG-13300: document size bigger than string bytes
-
Cause: size of the document being indexed is larger than the maximum supported size for the VARCHAR2 interface of stored procedure
- DRG-13301: syntax error in token data when expecting string, at line string
-
Cause: token data returned by the user-defined lexer procedure is incorrect
- DRG-13302: number of wildcard offsets must be in the range string..string, at line string
-
Cause: number of wildcard offsets specified as value for the wildcard attribute does not meet the supported range
- DRG-13303: value of wildcard offset must be in the range string..string, at line string
-
Cause: value of pre-normalized wildcard offset or post-normalized wildcard offset specified as value for the wildcard attribute does not meet the supported range
- DRG-13304: character referenced by wildcard attribute is not a wildcard character, at line string
-
Cause: The wildcard attribute value specified the offset of a wildcard character. The character at the specified offset is neither the '%' character nor the '_' character.
- DRG-13305: 'off' attribute value must be in the range string..string, at line string
-
Cause: value of 'off' attribute does not meet the supported range
- DRG-13306: 'len' attribute value must be in the range string..string, at line string
-
Cause: value of 'len' attribute does not meet the supported range
- DRG-13307: 'off'=string and 'len'=string references character past end-of-file of string character document, at line string
-
Cause: value of 'off' attribute plus value of 'len' attribute is greater than the number of characters in the document
- DRG-13308: query operator ABOUT not supported by USER_LEXER
-
Cause: the query contains an ABOUT operator while using USER_LEXER lexer type
- DRG-13309: operation not supported by USER_LEXER
-
Cause: USER_LEXER does not support this operation
- DRG-13310: index owner does not have EXECUTE privilege on USER_LEXER stored procedure string
-
Cause: user CTXSYS did not grant EXECUTE privilege on USER_LEXER stored procedure to the index owner
- DRG-13311: USER_LEXER stored procedure name contains a semicolon
-
Cause: the procedure name contains a semicolon character
- DRG-13312: user CTXSYS does not own USER_LEXER stored procedure string
-
Cause: CTXSYS does not have EXECUTE privilege on the USER_LEXER stored procedure
- DRG-13400: Oracle Data Mining was not installed
-
Cause: The function you used depends on Oracle Data Mining, which has not been installed yet.
- DRG-13401: the preference string type is not supported in this API
-
Cause: the type you have specified is not supported
- DRG-13500: Parameter_string must start with string
-
Cause: Wrong syntax for parameter_string.
- DRG-13501: Shadow Index Already Exists
-
Cause: A shadow index was previously created already
- DRG-13502: NOPOPULATE is not allowed in recreate_index_online
-
Cause: Specify NOPOPULATE in parameter_string in recreate_index_online
- DRG-13503: POPULATE is not allowed for a local index in create_shadow_index
-
Cause: Specify POPULATE for a local index during create_shadow_index
- DRG-13504: string has no shadow index
-
Cause: Tried to perform exchange shadow without creating shadow index first
- DRG-13505: Keyword string is not allowed here in parameter_string
-
Cause: Wrong syntax for parameter_string
- DRG-13506: string has no shadow part
-
Cause: Tried to perform exchange shadow part without creating shadow part first
- DRG-13507: SWAP and NOPOPULATE is incompatible
-
Cause: Specified SWAP and NOPOUPLATE in parameter string
- DRG-13508: Not all partitions for index string are swapped
-
Cause: try to swap an local partitioned index when not all partitions are swapped
- DRG-13509: error while swapping shadow index
-
Cause: an error occurred during the shadow index swap
- DRG-13510: shadow index does not exist
-
Cause: Tried to perform exchange shadow without creating shadow index first
- DRG-13511: Cannot sync until all partitions for index string are swapped
-
Cause: Tried to swap with sync a local partitioned index when not all partitions are swapped
- DRG-13600: Syntax error in the result set descriptor at string
-
Cause: The result set descriptor has a syntax error
- DRG-13601: Syntax error in the order attribute
-
Cause: The order attibute has a syntax error
- DRG-13602: Number parsing error in string
-
Cause: The number string is malformed
- DRG-13603: To many sort keys
-
Cause: Too many sort keys are specified
- DRG-13604: To many items to select
-
Cause: Too many select items are specified
- DRG-13606: start_hit_num is not specified or out of valid range number..number
-
Cause: start_hit_num is not specified or out of valid range
- DRG-13607: end_hit_num is not specified or out of valid range number..number
-
Cause: end_hit_num is not specified or out of valid range
- DRG-13608: Temporary lob not created for ctx_query.result_set_document
-
Cause: Temporary lob is not allocated for ctx_query.result_set_document
- DRG-13609: empty query is not allowed
-
Cause: No query is specified and result set descriptor has invalid elements
- DRG-13613: Missing index name
-
Cause: index name not specified in the API
- DRG-13614: result_set_inteface not supported with security policy
-
Cause: result set interface not supported with security policies
- DRG-13615: Only one snippet element allowed in result set interface
-
Cause: More than one snippet element specified with result set interface
- DRG-13617: invalid value for topn in result set interface
-
Cause: Cannot use topn less than or equal to zero
- DRG-13621: Duplicate group count element in result set interface
-
Cause: Group Count element specified more than once for group
- DRG-13622: Unsupported SDATA 'bucketby' value specified in the result set interface
-
Cause: An unsupported attribute value was specified for the 'bucketby' attribute.
- DRG-13624: invalid attribute value for 'collocates' in the result set interface
-
Cause: An unsupported attribute value was specified for a 'collocates' attribute.
- DRG-13625: more than one sentiment element in query
-
Cause: There was more than one sentiment element in the query.
- DRG-13626: too many Item elements in sentiment query
-
Cause: There were too many item elements in the sentiment query.
- DRG-13627: Invalid item attribute value for string in result set interface
-
Cause: There was an unsupported attribute value specified for the item attribute.
- DRG-13628: Invalid value for 'sortby' SDATA group count in the result set interface
-
Cause: An unsupported attribute value was specified for the 'sortby' attribute.
- DRG-13629: Invalid value for 'order' SDATA group count in the result set interface
-
Cause: An unsupported attribute value was specified for the 'order' attribute.
- DRG-13630: The 'bucketby' attribute is only supported for 'searchable' SDATA
-
Cause: The 'bucketby' attribute applies to 'searchable' SDATA sections only.
- DRG-13631: Empty queries are not supported with 'bucketby' single
-
Cause: Empty queries are supported with 'bucketby' range.
- DRG-13632: Auto lexer is not supported with 'collocates' in the result set interface
-
Cause: An unsupported lexer was specified for 'collocates'.
- DRG-13633: Error processing 'collocates' in the result set interface
-
Cause: Internal error processing the 'collocates' element.
- DRG-13700: Syntax error in the Extraction Rule Descriptor
-
Cause: The Extraction Rule descriptor has a syntax error
- DRG-13701: Invalid rule_id
-
Cause: rule_id is NULL or rule_id <= 0
- DRG-13702: Rule not found
-
Cause: No rule for given rule_id
- DRG-13703: Invalid Type Specified: string
-
Cause: An invalid entity type was specified
- DRG-13704: Invalid Entity Type List
-
Cause: An invalid entity type list was specified
- DRG-13705: Must use an Extract Policy
-
Cause: Using a non-extraction policy
- DRG-13706: Cannot use Entity Extraction Policy here
-
Cause: Using an entity extraction policy
- DRG-13707: Rule Engine Loading Failed
-
Cause: A user rule has an error
- DRG-13708: Dictionary Loading Failed
-
Cause: The user dictionary has an error
- DRG-13709: Unsupported Language Specified: string
-
Cause: Unsupported Language Specified
- DRG-13710: Syntax Error in Dictionary
-
Cause: Syntax error in dictionary
- DRG-13711: Stop Entity Not Found
-
Cause: Tried to remove a non-existent stop entity
- DRG-13712: User Dictionary already loaded
-
Cause: Tried to load a 2nd user dictionary to a policy
- DRG-13713: No User Dictionary loaded
-
Cause: No user dictionary loaded for this policy
- DRG-13714: Duplicate Stop Entity
-
Cause: Trying to load a duplicate uncompiled stop entity
- DRG-13715: Null name and type for Stop entity
-
Cause: Trying to load a stop entity with null name and type
- DRG-13716: Entity Extraction not enabled
-
Cause: Haven't loaded correct event
- DRG-13717: Null entry or alternate form in user dict
-
Cause: A entry or alternate form has null value
- DRG-13718: No entity type given in user dict
-
Cause: An entry was not given an entity type
- DRG-13719: File and Drop are mutually exclusive
-
Cause: Tried to run ctxload with file and drop
- DRG-13720: Stop entity already marked for deletion
-
Cause: Tried to re-drop a stop entity
- DRG-13721: Duplicate Type on Typelist
-
Cause: Duplicate type on typelist
- DRG-13722: Invalid Backreference
-
Cause: Backreference not between 1 and 10
- DRG-13723: Invalid Attribute: string
-
Cause: Unsupported Attribute
- DRG-13724: Invalid Attribute Value: string
-
Cause: Unsupported attribute value
- DRG-13725: Type Name Too Long
-
Cause: Type name more than 30 bytes
- DRG-13726: Invalid Tag: string
-
Cause: Unsupported Tag
- DRG-13727: Missing Tag: string
-
Cause: Missing Necessary Tag
- DRG-13728: Missing Attribute: string
-
Cause: Missing Necessary Attribute
- DRG-13729: Cyclic definition of rules, with type: string
-
Cause: Cyclic nested rules
- DRG-13730: Rules not found for the type: string
-
Cause: Rules doesn't exists for the type
- DRG-13731: Level of nesting exceeded
-
Cause: More than 5000 levels of nesting
- DRG-13732: Multiple types and backreferences are not supported
-
Cause: Using multiple types and backreferences is not supported
- DRG-13733: dictionary for string is empty
-
Cause: Dictionary to import is empty
- DRG-13734: Oracle supplied dictionary type "string" with backreference is not supported
-
Cause: Use of supplied dictionary types with backreference is not supported
- DRG-13735: Syntax error in the extraction rule: "number"
-
Cause: The extraction rule descriptor has a syntax error
- DRG-13900: Auto_Optimize Process is already started
-
Cause: Auto_Optimize Process is already started
- DRG-13901: Index must have stage_itab
-
Cause: Auto_Optimize works on indexes with stage_itab
- DRG-13902: Index/Partition already added to auto_optimize list
-
Cause: Index/Partition already added to auto_optimize list
- DRG-13903: Index/Partition not on the auto_optimize list
-
Cause: Index/Partition not on the auto_optimize list
- DRG-13904: Index/Partition has max_rows set to non-zero value
-
Cause: Index/Partition is using max_rows to merge
- DRG-13905: Index/Partition has auto optimization on
-
Cause: Index/Partition is using auto optimization
- DRG-50000: requested size larger than pagesize
-
Cause: The requested memoery size is larger than page size,
- DRG-50100: CORE LSF error: string
-
Cause: detect a CORE LSF error
- DRG-50101: CORE LEM error: string
-
Cause: detect a CORE LEM error while reading the error stack
- DRG-50102: error getting database compatibility
-
Cause: could not obtain database compatibility setting
- DRG-50200: Third-party filter internal error
-
Cause: Third-party filter could not filter this document because of an internal error.
- DRG-50300: error sending message from server to client
-
Cause: internal database error or internal Text error
- DRG-50301: server error reading request queue
-
Cause: database error or internal Text error
- DRG-50302: server error reading OOB break queue; cannot detect interrupts
-
Cause: database error or internal Text error
- DRG-50303: error in bufout
-
Cause: This is an internal error
- DRG-50304: error in execute()
-
Cause: This is an internal error
- DRG-50305: getcmd() called when one of the queue names is NULL
-
Cause: This is an internal error
- DRG-50400: maximum number of fuzzy match candidates exceeded: string
-
Cause: Internal error, probably result of large number of indexed words
- DRG-50401: failed to retrieve fuzzy match candidates from db: string
-
Cause: Internal error
- DRG-50402: Index validation failed for one or more tokens
-
Cause: Index validation generated an error for one or more tokens
- DRG-50500: only RULE_CLASSIFIER is accepted in this API
-
Cause: you specified an illegal classifier
- DRG-50501: classifier preference not specified
-
Cause: the classifier preference is not specified
- DRG-50502: cannot use RULE_CLASSIFIER in this API
-
Cause: you specified RULE_CLASSIFIER
- DRG-50503: unsupported classification method
-
Cause: you spcified an unsupported classification method
- DRG-50504: invalid column datatype for string table
-
Cause: the column datatype is invalid
- DRG-50505: invalid sentiment label
-
Cause: A sentiment label other than 0, 1 or 2 was present in the training table.
- DRG-50600: assertion failed
-
Cause: An internal check-condition has been violated
- DRG-50601: fatal error
-
Cause: A fatal error has occurred
- DRG-50603: unrecognized operation code string
-
Cause: Bad operation code was encountered (reached switch default:)
- DRG-50607: failed to obtain column info for cid string
-
Cause: internal error, probably a bug
- DRG-50608: unexpected end of data
-
Cause: internal error, probably a bug
- DRG-50609: pipe internal error
-
Cause: internal error, probably a bug
- DRG-50610: internal error: string
-
Cause: internal error, probably a bug
- DRG-50611: Third party lexer internal error: string
-
Cause: internal error from inxight lexer
- DRG-50612: internal error: you need to call bind first for this insertion mode
-
Cause: internal error
- DRG-50613: internal error: model type is not supported in drctrwpf
-
Cause: internal error
- DRG-50614: library loading error in string
-
Cause: internal error
- DRG-50615: Third party lexer timed out
-
Cause: Third-party auto lexer could not complete tokenization because the lexer timed out.
- DRG-50617: Query string too long: string
-
Cause: internal error
- DRG-50618: Failed to create XML context
-
Cause: internal error
- DRG-50700: unknown command (args=queue, command)
-
Cause: this is an internal error
- DRG-50701: error in listener.get_cmd()
-
Cause: this is an internal error
- DRG-50702: error in drtlsleep()
-
Cause: this is an internal error in a testing function
- DRG-50703: listener startup error
-
Cause: this is an internal error
- DRG-50704: Net8 listener is not running or cannot start external procedures
-
Cause: Oracle Text needs to call external code to complete your request, and could not start the extproc agent process.
- DRG-50800: failed to open cursor
-
Cause: Too many cursors open for internal queries
- DRG-50801: failed to parse cursor
-
Cause: parse error on an internal query
- DRG-50802: failed to bind input
-
Cause: bind error on an internal query
- DRG-50803: failed to define output
-
Cause: define error on an internal query
- DRG-50804: failed to exec cursor
-
Cause: exec error on an internal query
- DRG-50805: failed to close cursor
-
Cause: cursor close error on an internal query
- DRG-50806: failed to rollback
-
Cause: transaction rollback error
- DRG-50807: failed to commit
-
Cause: internal error
- DRG-50850: string
-
Cause: This is an oracle error
- DRG-50851: SQL execute failed
-
Cause: failed to execute a sql statement
- DRG-50852: failed to turn SQL trace on
-
Cause: internal error,
- DRG-50853: fetch error
-
Cause: fetch error on an internal query
- DRG-50855: logoff fail
-
Cause: Fail to logoff from the database
- DRG-50857: oracle error in string
-
Cause: this is an informational message
- DRG-50858: OCI error: string
-
Cause: a generic OCI error occurred
- DRG-50859: failed to allocate statement handle
-
Cause: This is an internal error
- DRG-50860: failed to prepare statement
-
Cause: This is an internal error
- DRG-50861: failed to obtain type descriptor
-
Cause: This is an internal error
- DRG-50862: failed to create new Oracle object
-
Cause: This is an internal error
- DRG-50863: string assignment failed
-
Cause: This is an internal error
- DRG-50864: number assignment failed
-
Cause: This is an internal error
- DRG-50865: failed to append to collection
-
Cause: This is an internal error
- DRG-50866: failed to resize string
-
Cause: This is an internal error
- DRG-50867: failed to free Oracle object
-
Cause: This is an internal error
- DRG-50868: failed to free statement handle
-
Cause: This is an internal error
- DRG-50900: text query parser error on line string, column string
-
Cause: bad query
- DRG-50901: text query parser syntax error on line string, column string
-
Cause: bad query
- DRG-50902: unexpected character string
-
Cause: bad query
- DRG-50903: invalid weight string
-
Cause: invalid weight
- DRG-50904: weight string outside valid range 0.1 to 10.0
-
Cause: invalid weight
- DRG-50905: invalid score threshold string
-
Cause: invalid score threshold
- DRG-50906: score threshold string is not an integer
-
Cause: invalid score threshold
- DRG-50907: score threshold string outside valid range 1 to 100
-
Cause: invalid score threshold
- DRG-50908: invalid maximum number of documents string
-
Cause: invalid maximum number of documents
- DRG-50909: maximum number of documents string is not an integer
-
Cause: invalid maximum number of documents
- DRG-50910: max documents requested string outside valid range 1 to 65535
-
Cause: invalid maximum number of documents
- DRG-50911: invalid first document number string
-
Cause: invalid first document number
- DRG-50912: first document number string is not an integer
-
Cause: invalid first document number
- DRG-50913: first document requested string is not a positive number
-
Cause: invalid first document number
- DRG-50914: invalid last document number string
-
Cause: invalid last document number
- DRG-50915: last document number string is not an integer
-
Cause: invalid last document number
- DRG-50916: last document string is less than first document
-
Cause: invalid last document number
- DRG-50917: escape on at end of text query string
-
Cause: unbalanced escape characters
- DRG-50918: mismatched close escape character
-
Cause: no matching open escape character for close escape
- DRG-50919: NEAR operand not a phrase, equivalence or another NEAR expression
-
Cause: invalid operand type for NEAR operator
- DRG-50920: part of phrase not itself a phrase or equivalence
-
Cause: invalid type of expression which is part of phrase
- DRG-50921: EQUIV operand not a word or another EQUIV expression
-
Cause: invalid operand type for EQUIV operator
- DRG-50922: PL/SQL execution failed for string
-
Cause: PL/SQL function may not exist or is returning bad value
- DRG-50923: could not rewrite PL/SQL for execution
-
Cause: parser internal
- DRG-50924: PL/SQL inside PL/SQL not supported
-
Cause: PL/SQL function call returned another PL/SQL call
- DRG-50925: could not parse return value of PL/SQL
-
Cause: string returned by PL/SQL function could not be parsed
- DRG-50926: invalid text query string
-
Cause: query string empty or made up of invalid characters
- DRG-50927: parser failed on line string on column string
-
Cause: bug
- DRG-50928: reserved failure on line string on column string
-
Cause: bug
- DRG-50929: parser internal on line string on column string
-
Cause: bug
- DRG-50930: parser memory failure on line string on column string
-
Cause: memory allocation or freeing error
- DRG-50931: parser not opened
-
Cause: bug
- DRG-50932: parser preference initialization failed
-
Cause: bug
- DRG-50933: parser hash insert failure
-
Cause: bug
- DRG-50934: parser hash create failure
-
Cause: bug
- DRG-50935: parser component failure
-
Cause: bug
- DRG-50936: query word string is too complex for index
-
Cause: bug
- DRG-50937: query too complex
-
Cause: query is too complex for our query evaluator
- DRG-50938: parser already bound
-
Cause: internal coding mistake
- DRG-50939: parser not set
-
Cause: bug
- DRG-50940: parser not parsed
-
Cause: bug
- DRG-50941: PL/SQL function string cannot be executed
-
Cause: PL/SQL function may not exist or cannot be executed by user
- DRG-50942: errors: stringstring
-
Cause: PL/SQL function encountered error -- this is the error message
- DRG-50943: query token too long on line string on column string
-
Cause: A query token is longer than 256 bytes
- DRG-50944: NEAR operator not supported for theme index
-
Cause: NEAR operator used in theme index query
- DRG-50945: Illegal phrase in query for theme index
-
Cause: Phrase incorrectly defined in theme index query
- DRG-50946: Invalid unary operator for theme index
-
Cause: Stemming, fuzzy match and soundex not allowed for theme index
- DRG-50947: ABOUT clause not allowed without a theme index
-
Cause: The query contains an ABOUT clause, but there is no theme index to support it
- DRG-50948: ABOUT clause required in the absence of a text index
-
Cause: There is no text index, but the query does not contain any about clause. With only a theme index present, each query term must belong to an ABOUT clause
- DRG-50949: too many SQEs
-
Cause: Too many SQEs to expand
- DRG-50950: circular SQE found
-
Cause: Circular SQE reference is found.
- DRG-50951: Unable to resolve element name for attribute string
-
Cause: XPATH expression such as A/*/@B or A//@B is not supported.
- DRG-50952: Section is not PATH section group
-
Cause: XPATH expression has section which is not created using PATH section group.
- DRG-50953: Unable to determine section name
-
Cause: XPATH expression should not end with . or *
- DRG-50954: Theme index is required for CTXCAT about queries
-
Cause: There is no theme index, but the catsearch query contains about clause. You must create a theme index before using ABOUT query against CTXCAT index
- DRG-50955: Missing comma in transform clause string
-
Cause: A transform clause in a query template is missing a comma
- DRG-50956: Theme index is required for THEMES transform queries
-
Cause: There is no theme index, but the operator TRANSFORM is used with THEMES as its parameter. You must create a theme index before using THEMES in TRASNFORM operator.
- DRG-50957: Missing textquery element in query template string
-
Cause: The textquery tag is missing or misspelled in a query template
- DRG-50958: Missing quote in transform clause string
-
Cause: A transform clause in a query template is missing a quote
- DRG-50959: Query length exceeds string bytes
-
Cause: the query length exceeds the maximum allowed length
- DRG-50960: Mild not operand not a term or phrase
-
Cause: invalid operand type for MNOT operator
- DRG-50961: Missing string for string clause
-
Cause: the specified tag is missing from the specified complex query clause
- DRG-50962: Query operators are not allowed in transform input string
-
Cause: You specified an operator (such as wildcard) in the input string for the transform operator
- DRG-51002: unexpected component failure
-
Cause: Internal error
- DRG-51017: unable to open storage buffer for fuzzy match candidates
-
Cause: Internal error, probably insufficient memory
- DRG-51019: unable to open or illegal format for fuzzy match data file: string
-
Cause: Unable to open OS file containing fuzzy matching information or the file was not of the correct format
- DRG-51020: out of memory in fuzzy matcher
-
Cause: Cannot allocate more memory
- DRG-51021: undefined error in fuzzy matcher
-
Cause: Internal error
- DRG-51022: undefined error in stemmer
-
Cause: Internal error
- DRG-51023: stemmer file cannot be opened
-
Cause: Unable to open OS file containing stemmer lexicon, or the file contents were not correct
- DRG-51024: out of memory in stemmer
-
Cause: Cannot allocate more memory
- DRG-51025: an invalid character was passed to the stemmer
-
Cause: Invalid character in word input to the stemmer
- DRG-51028: unexpected error in fuzzy match expansion: string
-
Cause: Internal error
- DRG-51029: unexpected error in stemmer expansion: string
-
Cause: Internal error
- DRG-51030: wildcard query expansion resulted in too many terms
-
Cause: User error
- DRG-51100: invalid program argument index
-
Cause: This is an internal error
- DRG-51101: argument processing callback failed
-
Cause: this is an internal error
- DRG-51200: open keymap failed for index id = string
-
Cause: Failed to initialize the keymap for the column id specified.
- DRG-51201: failed to perform DDL operation: database object string
-
Cause: Textkey mapping service failed on DDL operation
- DRG-51202: invalid key mapping operation mode : string
-
Cause: invalid keymap mode value found. This is an internal error
- DRG-51203: found doc ids without mappings during get maps
-
Cause: found doc ids without mappings during get mapping by doc ids, the index data and keymap service are out of synch.
- DRG-51300: error getting dml Queue lock
-
Cause: a server must have hung while processing the dml Queue, leaving it locked
- DRG-51301: error releasing dml Queue lock
-
Cause: internal database error, or perhaps someone dropped the lock while we were using it
- DRG-51311: DML lock handle previously allocated
-
Cause: internal error
- DRG-51312: DML lock internal error string
-
Cause: internal error
- DRG-51313: timeout while waiting for lock
-
Cause: most likely an internal error
- DRG-51314: index is not empty
-
Cause: you attempted to invoke populate_pending against an index which already has or has had indexed documents.
- DRG-51315: AGGMERGE lock internal error string
-
Cause: internal error
- DRG-51400: incomplete SEARCH_ON VALUE or SEARCH_ON TEXT_VALUE clause
-
Cause: An attempt was made to create or alter an XML Search Index with a SEARCH_ON VALUE or SEARCH_ON TEXT_VALUE clause that did not list a data type specification.
- DRG-51401: duplicate SEARCH_ON specification for string component
-
Cause: The specified parameter string for an XML or JSON Search Index had a duplicate SEARCH_ON clause for one the following: TEXT, NUMBER, BINARY_DOUBLE, TIMESTAMP or VARCHAR2.
- DRG-51402: cannot use SEARCH_ON feature with this index
-
Cause: An attempt was made to specify a SEARCH_ON clause as part of the index parameter string for an index that was not an XML Search Index or a JSON Search Index.
- DRG-51403: cannot index JSON type column string with this indextype
-
Cause: An attempt was made to create a CONTEXT or SEARCH INDEX with no FOR JSON clause on a JavaScript Object Notation (JSON) type column.
- DRG-51404: invalid token 'string' found for ALTER of string Search Index
-
Cause: An invalid token was found when parsing a parameter string that modified options specified to JSON or XML Search Index.
- DRG-51801: failed to seek in file: string
-
Cause: this is an internal error
- DRG-51802: failed to read from file: string
-
Cause: this is an internal error
- DRG-51803: failed to open file: string
-
Cause: this is an internal error
- DRG-51804: failed to write to file: string
-
Cause: this is an internal error
- DRG-52100: string returned internal error code string
-
Cause: this is an internal error
- DRG-52101: an invalid session handle was passed to Oracle Text
-
Cause: this is an internal error
- DRG-52102: an invalid transaction handle was passed to Oracle Text
-
Cause: this is an internal error
- DRG-52103: the Oracle Text environment could not reset
-
Cause: this is an internal error
- DRG-52104: the Oracle Text environment could not initialize
-
Cause: this is an internal error
- DRG-52105: no delete function found
-
Cause: this is an internal error
- DRG-52106: Oracle Text service results could not be committed
-
Cause: this is an internal error
- DRG-52107: ctxkbtc internal error
-
Cause: this is an internal error
- DRG-52108: failed to delete knowledge base user extension
-
Cause: this is an internal error
- DRG-52109: error in reading thesaurus
-
Cause: this is an internal error
- DRG-52110: error in writing extended knowledge base
-
Cause: this is an internal error
- DRG-52111: error in knowledge base cache
-
Cause: this is an internal error
- DRG-52112: improper Chinese string string of length number
-
Cause: this is an internal error
- DRG-52113: improper Japanese string string of length number
-
Cause: this is an internal error
- DRG-52200: invalid state during export
-
Cause: this is an internal error
- DRG-52201: imcompatible Oracle Text versions
-
Cause: attempting to import an incompatible version of Oracle Text data
- DRG-52202: invalid class name: string
-
Cause: the specified class name is not valid
- DRG-52203: invalid object name: string
-
Cause: the specified object name is not valid
- DRG-52204: error while registering index
-
Cause: this is an internal error
- DRG-52205: class string and object string already exists for this index
-
Cause: duplicate entry of class and object
- DRG-52206: error while registering index object
-
Cause: this is an internal error
- DRG-52207: the specified attribute does not exist: string
-
Cause: This is an internal error
- DRG-52208: the specified attribute already exist: string
-
Cause: This is an internal error
- DRG-52210: error while registering value for attribute: string
-
Cause: This is an internal error
- DRG-52211: error while registering partition
-
Cause: this is an internal error
- DRG-52212: error while registering cdi columns
-
Cause: this is an internal error
- DRG-52213: Insufficient privileges
-
Cause: this is an internal error
- DRG-52300: Index string.string does not exist
-
Cause: The given index does not exist for the current user
- DRG-52301: Query Stats is already enabled for this index
-
Cause: attempting to enable the query stats for an index for which it is already enabled
- DRG-52302: Query Stats is not enabled for this index
-
Cause: attempting to disable the query stats for an index for which it is not enabled
- DRG-52303: Option String is full
-
Cause: Index option string is full
- DRG-52304: This operation requires Query Stats to be enabled for the index
-
Cause: attempting to do an operation which required query stats option for the index to be enabled
- DRG-52305: Unknown value, string, passed in to stat_type
-
Cause: An invalid value is passed in to the parameter stat_type
- DRG-52400: Dictionary string already exists
-
Cause: The specified dictionary already exists
- DRG-52401: Invalid language string specified
-
Cause: Language specified is invalid
- DRG-52402: Dictionary name is invalid
-
Cause: The specified dictionary name is invalid
- DRG-52403: Dictionary string does not exist
-
Cause: The specified dictionary does not exist
- DRG-52404: policy_languages requires auto lexer
-
Cause: policy_languages requires the auto lexer to retrieve language information. The auto lexer was not specified, however.