Basic text search error codes

Basic text searching has specific error messages.

The following table lists error codes for basic text searching.
SQLstate Description
BTS01 bts error, assertion failed. File %FILE%, line %LINE%
BTS02 bts internal error. File %FILE%, line %LINE%
BTS03 bts error - could not set trace level to %PARAM1% for trace class %PARAM2%
BTS04 bts error - could not set trace output file to %PARAM1%
BTS05 bts error - unique index not supported
BTS06 bts error - cluster index not supported
BTS08 bts error - cannot query the table %TABLENAME%
BTS09 bts error - BTS index only supports extspaces and sbspaces
BTS10 bts error - cannot get connection descriptor
BTS11 bts error - extspace not specified
BTS12 bts error - cannot determine index owner
BTS13 bts error - cannot determine index name
BTS14 bts error - cannot create directory %PARAM1%
BTS15 bts error - current vpclass (%VPCLASS%) is not specified as noyield
BTS16 bts error - too many virtual processors running (%NUMVPS%) for the current vpclass (%VPCLASS%), 1 is the maximum
BTS17 bts error - out of memory
BTS18 bts error - SQL Boolean expression are not supported with bts_contains
BTS19 bts error - cannot query with a null value
BTS20 bts error - invalid value for index delete parameter: %PARAM1% should be either immediate or deferred
BTS21 bts error - unsupported type: %PARAM1%
BTS22 bts error - bts_contains requires an index on the search column
BTS23 bts error - cannot register end-of-transaction-callback
BTS24 bts error - invalid value for %PARAM1% parameter: %PARAM2% should be an integer value greater than 0
BTS25 bts error - CLOB or BLOB is too large, must be less than or equal to 2,147,483,647 bytes
BTS26 bts error - clob or blob is too large, must be less than or equal to 2,147,483,647
BTS27 bts error - BTS indexes in external spaces only permitted on primary or standard servers
BTS28 bts error - invalid value for the %PARAM1% parameter: %PARAM2% should be "unlimited" or an integer value greater than 0
BTS29 bts error - invalid value for the %PARAM1% parameter: %PARAM2% should be either "and" or "or"
BTS30 bts error - invalid value for the PARAM1% parameter: %PARAM2% should be either yes or no
BTS31 bts error - invalid value for the %PARAM1% parameter: %PARAM2% should be either yes, yes_with_tag or no
BTS32 bts error - invalid value for the %PARAM1% parameter: %PARAM2% should be either yes, yes_with_database_name or no
BTS33 bts error - incorrect value for the %PARAM1% parameter: %PARAM2% should be either yes, yes_with_positions, yes_with_offsets or no
BTS34 bts error - uppercase characters are not allowed in stopwords
BTS35 bts internal error - mi_open() failed. File %FILE%, line %LINE%
BTS36 bts internal error - mi_lo_open() failed. File %FILE%, line %LINE%
BTS37 bts internal error - mi_lo_seek() failed. File %FILE%, line %LINE%
BTS38 bts internal error - mi_lo_read() failed. File %FILE%, line %LINE%
BTS39 bts internal error - ifx_int8toasc() failed. File %FILE%, line %LINE%
BTS40 bts internal error - mi_lo_spec_init() failed. File %FILE%, line %LINE%
BTS41 bts internal error - mi_lo_create() failed. File %FILE%, line %LINE%
BTS42 bts internal error - mi_lo_increfcount() failed. File %FILE%, line %LINE%
BTS43 bts internal error - ifx_int8cvlong() failed. File %FILE%, line %LINE%
BTS44 bts internal error - mi_lo_write() failed. File %FILE%, line %LINE%
BTS45 bts error - cannot open file %FILENAME%
BTS46 bts error - cannot create file %FILENAME%
BTS47 bts error - xml syntax error
BTS48 bts error - invalid hex specification: \x%PARAM1%%PARAM2%
BTS49 bts error - the GLS character name '%PARAM1%' is not found
BTS50 bts error - if either xmltags is specified or all_xmltags is enabled, then include_contents must be enabled if strip_xmltags is enabled
BTS51 bts error - xmlpath_processing cannot be enabled unless either xmltags is specified or all_xmltags is enabled.
BTS52 bts error – parameter %PARAM1% and %PARAM2% parameters are mutually exclusive
BTS53 bts error - invalid value for the %PARAM1% parameter: %PARAM2% should be a lower value
BTS54 bts error - cannot write to file %FILENAME%
BTS55 bts error - cannot read from file %FILENAME%
BTS56 bts error - bad magic number on file %FILENAME%
BTS57 bts error - the specified table (%TABLENAME%) is not in the database
BTS58 bts error - column (%COLUMNNAME%) not found in specified table (%TABLENAME%)
BTS59 bts error - column (%COLUMNNAME%) in specified table (%TABLENAME%) is not of type char, varchar, nchar, nvarchar or lvarchar
BTS60 bts error - cannot acquire exclusive lock for %PARAM1%
BTS61 bts error - cannot acquire read lock for %PARAM1%
BTS62 bts error - cannot acquire write lock for %PARAM1%
BTS63 bts error - parameter %PARAM1% is not implemented yet"
BTS64 bts error - %PARAM1% contains a '/' character which indicates an xmlpath however xmlpath_processing is not enabled. Either remove the '/' in the xmltag or enable xmlpath_processing"
BTS65 bts error - invalid value for tempspace parameter: %PARAM1% should be an existing extspace or sbspace
BTS66 bts error - the include_contents cannot be enabled unless the xmltags, all_xmltags, json_names or all_json_names parameter is enabledbts error - include_contents cannot be enabled unless either xmltags is specified or all_xmltags is enabled
BTS67 bts error - include_namespaces cannot be enabled unless either xmltags is specified or all_xmltags is enabled
BTS68 bts error - include_subtag_text cannot be enabled unless either xmltags is specified or all_xmltags is enabled
BTS69 bts error - %PARAM1% only works with on one bts virtual processor
BTS70 bts internal error - mi_lo_specset_sbspace() failed. File %FILE%, line %LINE%
BTS71 bts internal error - mi_lo_stat() failed. File %FILE%, line %LINE%
BTS72 bts internal error - mi_lo_stat_cspec() failed. File %FILE%, line %LINE%
BTS73 bts error - sbspace %PARAM1% is not logged
BTS74 bts error - sbspace for FSE is not set
BTS75 bts error - SBSPACENAME not set in onconfig file
BTS76 bts error - transaction uses too much memory. Perform smaller transactions or increase the value of the xact_memory parameter on the index
BTS77 bts error - invalid value for xact_memory: %PARAM1% should be either unlimited or the maximum amount of memory (between 1 and %PARAM2% kilobytes)
BTS78 bts error - SQL create index and drop index are not supported on updatable secondary nodes
BTS79 bts error - not implemented yet
BTS80 bts error - database must be logged
BTS81 bts error - not in a transaction
BTS82 bts error - xpath syntax error
BTS83 bts internal error - mi_file_seek failed. File %FILE%, line %LINE%
BTS84 bts internal error - mi_lo_decrefcount failed. File %FILE%, line %LINE%
BTS85 bts internal error - mi_lo_from_string failed. File %FILE%, line %LINE%
BTS86 bts internal error - mi_lo_release() failed. File %FILE%, line %LINE%
BTS87 bts internal error - mi_lo_to_string failed. File %FILE%, line %LINE%
BTS88 bts error - no lo handle found in file %PARAM1%
BTS89 bts error - valid lo handle found in file %PARAM1%
BTS90 bts error - CLucene index exists and is locked
BTS91 bts error - CLucene index exists
BTS92 bts error - CLucene index does not exist
BTS93 bts error - the parameter %PARAM1% should be in the form of name="value"
BTS94 bts error - missing a double quotation mark: ". The parameter %PARAM1% should be in the form of name="value"
BTS95 bts error - missing the closing parenthesis: ). The parameter %PARAM1% should be in the form of name="(values)"
BTS96 bts error - missing a double quotation mark: ". The parameter %PARAM1% should be in the form of name="(values)"
BTS97 bts error - missing a comma (,) between parameters
BTS98 bts error - duplicate parameters, %PARAM1%, were specified
BTS99 bts clucene error: Unknown error: %PARAM1%
BTSA1 bts clucene error: IO error: %PARAM1%
BTSA2 bts clucene error: Null pointer error: %PARAM1%
BTSA3 bts clucene error: Runtime error: %PARAM1%
BTSA4 bts clucene error: Illegal argument: %PARAM1%
BTSA5 bts clucene error: Parse error: %PARAM1%
BTSA6 bts clucene error: Token manager error: %PARAM1%
BTSA7 bts clucene error: Unsupported operation: %PARAM1%
BTSA8 bts clucene error: Invalid state: %PARAM1%
BTSA9 bts clucene error: Index out of bounds: %PARAM1%
BTSB0 bts clucene error: Too Many Clauses: %PARAM1%
BTSB1 bts clucene error: RAM Transaction error: %PARAM1%
BTSB2 bts clucene error: Invalid Cast: %PARAM1%
BTSC0 GLS Error: An attempt to create a locale with incompatible code sets has occurred
BTSC1 GLS Error: Bad format found in the codeset registry file
BTSC2 GLS Error: Either locale or code set conversion specifiers, i.e., GLS or NLS environment variables, is incorrect, or the codeset name registry file could not be found
BTSC3 GLS Error: Not enough memory to allocate a new locale object or a new codeset conversion object
BTSC4 GLS Error: The locale contains characters that are wider than the library allows
BTSC5 GLS Error: The locale object version is not compatible with the current library
BTSC6 GLS Error: The locale or codeset conversion file could not be found, is not readable, or has the wrong format
BTSC7 GLS Error: Unknown %PARAM1%
BTSC8 bts internal error - mi_lo_stat_size() failed. File %FILE%, line %LINE%
BTSC9 bts internal error - biginttoasc() failed. File %FILE%, line %LINE%
BTSD0 bts error - invalid canonical map[%PARAM1%]: zero length original character string
BTSD1 bts error - invalid canonical map[%PARAM1%]: %PARAM2% is an uppercase character. Uppercase characters are not allowed in canonical maps
BTSD2 bts error - invalid canonical map[%PARAM1%]: missing %PARAM2% in mapped characters specification
BTSD3 bts error - invalid canonical map[%PARAM1%]: missing %PARAM2% in original characters specification
BTSD4 bts error - invalid canonical map[%PARAM1%]: missing : in mapped characters specification
BTSD5 bts error - invalid canonical map[%PARAM1%]: missing ] in alternates of original characters specification
BTSD6 bts error - invalid canonical map[%PARAM1%]: spaces found in original character string at %PARAM2%
BTSD7 bts error - invalid canonical map[%PARAM1%]: trailing characters found
BTSD8 bts error - missing the closing parenthesis, ), in a string that has an opening parenthesis: (
BTSD9 bts error - missing the column name in table:%PARAM1%. Use the form table:table_name.column_name
BTSE0 bts error - parameter %PARAM1% is not updatable
BTSE1 bts error - unknown parameter name: %PARAM1%
BTSE2 bts error - recursive params parameter
BTSE3 bts error - invalid value for the %PARAM1% parameter: %PARAM2% is too long
BTSE4 bts error - invalid flag for the create_mode parameter: %PARAM1%
BTSE5 bts error - invalid value for the create_mode parameter: %PARAM1% should be a hexadecimal number
BTSE6 bts error - %PARAM1% encoding is not supported for %PARAM2%
BTSE7 bts error - UDR analyzer function %PARAM1% not found
BTSE8 bts error - UDR analyzer function id not found for %PARAM1%
BTSE9 bts error - default analyzer already set
BTSF0 bts error - empty stopwords field specification
BTSF1 bts error - invalid analyzer value: %PARAM1%
BTSF2 bts error - invalid value for the analyzer parameter: %PARAM1%
BTSF3 bts error - no analyzer specified for field: %PARAM1%
BTSF4 bts error - no field name in field:analyzer specification: %PARAM1%
BTSF5 bts error - the field %PARAM1% appears multiple times in the stopwords list
BTSF6 bts error - a stopwords list cannot be specified for the analyzer: %PARAM1%
BTSF7 bts error - too many colons found in stopwords field specification
BTSF8 bts error - too many colons found in field:analyzer specification: %PARAM1%
BTSF9 bts error - there is no snowball stemmer language specified after the period
BTSG0 bts error - there is no snowball stemmer language support for the $DB_LOCALE setting: %PARAM1%
BTSG1 bts error - there is no snowball stemmer language support for the specified language: %PARAM1%
BTSG2 bts error - internal index length %PARAM1% is too long. The maximum is %PARAM2%
BTSG3 bts error - bts_lock_setup: cannot get vp lock pointer
BTSG4 bts error - bts_lock_setup: vp is not locked
BTSG5 bts error - bts_lock_setup: vp is not locked by the current transaction
BTSG6 bts error - not (-) operator may not be specified in thesaurus
BTSG7 bts error - and (+) operator may not be specified in thesaurus
BTSG8 bts error - cannot determine index owner of thesaurus index %PARAM1%
BTSG9 bts error - cannot lock thesaurus index %PARAM1%
BTSH0 bts error - cannot read thesaurus index parameters for %PARAM1%
BTSH1 bts error - the index %PARAM1% does not have the thesaurus parameter set
BTSH2 bts error - thesaurus index cannot be fragmented
BTSH3 bts error - invalid term found in thesaurus. Only word terms should be specified
BTSH4 bts error - the %PARAM1% attribute must be specified
BTSH5 bts error - the text or file attribute must be specified
BTSH6 bts error - the copy_temp attribute can only be specified on an index in an sbspace
BTSH7 bts error - the field is not in the document
BTSH8 bts error - the directory cannot contain a bts index
BTSH9 bts error - the ID is out of bounds
BTSI0 bts error - must be a DBSA to use parameter %PARM1%
BTSI1 bts error - cannot cast json value to bson value: %MSG%
BTSI2 bts error - bson or json types cannot be used in a composite index
BTSI3 bts error - the json_path_processing parameter cannot be enabled unless the json_names parameter is specified or the all_json_names parameter is enabled
BTSI4 bts error - the only_json_values parameter requires that the include_contents is enabled when json_names is specified or all_json_names is enabled
BTSI5 bts error - bson format error decoding type %TYPE% (%SIZE% bytes) at byte %POS% of %MAX% total bytes
BTSI6 bts error - the total number of expected bytes recorded in the bson value, %LEN%, exceeds the actual length of the bson value, %MAX% bytes
BTSI7 bts error - bson format error: %BYTES% bytes of the bson value after the end-of-value mark were not processed
BTSI8 bts error - the json_names, all_json_names, only_json_values, or ignore_json_format_errors parameter can be specified only with bson or json types
BTSI9 bts error - bson or json types cannot be used when xmltags is specified or all_xmltags is enabled
BTSJ0 bts error - json format error at %POS%: extra characters following right brace (})
BTSJ1 bts error - json format error at %POS%: missing right square bracket (])
BTSJ2 bts error - json format error at %POS%: invalid number
BTSJ3 bts error - json format error at %POS%: missing colon (:) separator between name and value
BTSJ4 bts error - json format error at %POS%: missing document
BTSJ5 bts error - json format error at %POS%: missing left brace ({)
BTSJ6 bts error - json format error at %POS%: missing name
BTSJ7 bts error - json format error at %POS%: missing right brace (})
BTSJ8 bts error - json format error at %POS%: missing value
BTSJ9 bts error - json format error at %POS%: missing double quote (") in string