CTE0100 | A DB2 operation failed. DB2 information: "%2" "%4". |
Explanation: A DB2 error occurred that does not allow further processing.
What to do: For more detailed information on this DB2 error, use db2 ? SQLxxx.
CTE0101 | A search engine operation failed. Reason code: "%2", "%3", "%4", "%5", "%6" . |
Explanation: A Search Engine error occurred that does not allow further processing.
What to do: For more detailed information, see the Search Engine reason code descriptions.
CTE0102 | A general system function failed. Error: "%2". |
Explanation: A system error occurred that does not allow further processing.
What to do: Additional information can be found on UNIX in the errno.h header file.
CTE0103 | An internal error occurred. Location: "%1", "%2". |
Explanation: An internal processing error that does not allow further processing. Try to start and stop the update and locking services, as well as DB2.
What to do: If the error persists, start a trace and also check the db2diag.log.
CTE0104 | Memory allocation error (search engine). |
Explanation: The system has run out of memory.
What to do: Increase the available memory size for the instance owner, or stop other processes running parallel.
CTE0105 | Memory allocation error. |
Explanation: The system has run out of memory.
What to do: Increase the available memory size for the user, or stop other processes running parallel.
CTE0106 | Table "%1"."%2" has no primary key. |
Explanation: You tried to create an index on a table that does not have a primary key.
What to do: Call the db2 alter table to ensure the existence of a primary key. Then try to create the index again.
CTE0107 | Directory "%1" does not exist. |
Explanation: You specified a directory which does not exist.
What to do: Create the directory, ensure accessibility to the instance owner. Then try to specify the directory again. Note that in a distributed DB2 envionment, this directory has to exist on every physical node.
CTE0108 | The internal size "%4" of the key columns on object "%1"."%2" is larger than maximum allowed size of "%3". |
Explanation: The internal representation of the key columns exceeds the maximum size.
What to do: Change the layout of the table before creating the index again. Use smaller key columns, which also benefit performance.
CTE0109 | The number of key columns "%3" on object "%1"."%2" is larger than the allowed maximum of "%4". |
Explanation: A maximum number of 14 key columns is supported.
What to do: Change the layout of the table before creating the index again.
CTE0111 | The file "%1" is not readable. |
Explanation: The file specified cannot be read.
What to do: Check the access rights for the file. Take into account that the Stored Procedure runs as a fenced user ID, which may also require rights to work on this file.
CTE0112 | The file "%1" cannot be opened. |
Explanation: The file specified could not be opened.
What to do: Verify that the file is correctly specified.
CTE0113 | Error converting model file "%1" to UTF8 encoding. |
Explanation: The specified CCSID or the default database CCSID does not match the model file CCSID.
What to do: Ensure correct specification of the model file CCSID.
CTE0114 | Unable to register document model "%1" in file "%2". |
Explanation: The model file could not be used.
What to do: Check that the model file syntax is correctly specified.
CTE0115 | A locking problem occurred. Lock Manager information: "%1" "%2". |
Explanation: An internal locking problem occurred.
What to do: Check the current locks using the db2text control command. Using the same command, clean up the pending locks. If this does not help, stop and restart the locking and update services.
CTE0116 | Operation conflicts with existing lock. |
Explanation: You have tried to use a command that is currently not allowed when other commands are running on the index.
What to do: Check the locks held on this index to see which commands are currently running. Wait until the other commands have finished. If the operation is no longer running but the lock is still active, clean up the locks for the index and try again.
CTE0117 | All available lock space for databases is used. Change the configuration. |
Explanation: You tried to work on more databases than are configured in your lock file.
What to do: Change the number of databases you want to work in parallel with in your lock configuration db2extlm.cfg. Restart the update and locking services using the db2text stop and db2text start commands.
CTE0118 | All available lock space for indexes on a databases is used. Change the configuration. |
Explanation: You tried to work on more indexes for one database than are configured in your lock file.
What to do: Change the number of indexes you want to work in parallel with in your lock configuration file db2extlm.cfg. Restart the update and locking services using the db2text stop and db2text start commands.
CTE0119 | All available space for locks on an index is used. |
Explanation: The operations you are running require more locks for one index than are configured in your lock configuration file.
What to do: Change the number of locks you want to work in parallel with in your lock configuration db2extlm.cfg. Restart the update and locking services using the db2text stop and db2text start commands.
CTE0120 | Update and locking services configuration file error. |
Explanation: The configuration file db2extlm.cfg is in error.
What to do: Check the db2extlm.cfg file and correct the error. Restart the update and locking services using the command db2text start.
CTE0121 | The update and locking services configuration file cannot be opened. |
Explanation: The file db2extlm.cfg could not be opened.
What to do: Check if the file exists and that it can be accessed. If the file cannot be accessed, try to update your db2 instance using db2iupdt.
CTE0122 | A syntax error was found in the update and locking services configuration file. |
Explanation: A syntax error was found in the update and locking services configuration file.
What to do: Check the update and locking services configuration file for errors.
CTE0126 | The update and locking service input file "%1" is corrupted. |
Explanation: A required file for update and locking services is corrupted.
What to do: Check if the file exists and if it can be accessed. If you can access the file, rename the file and restart the update and locking services. The file should be created again. However, this action removes all of the specified frequency updates for create index.
CTE0127 | An update and locking service error has occurred. Reason code: "%1". |
Explanation: An internal error has occurred in the update and locking service area.
What to do: Stop DB2 and Net Search Extender and then clean up your shared resources. Try to start both again. If this does not work, report the problem to your IBM representative.
CTE0129 | NULL values are not allowed to be passed as parameters. |
Explanation: DB2 has passed a NULL value to an internal user-defined function.
What to do: First make sure the specified base table has a primary key. Change your select statement to avoid this problem. Switch on the trace function and pass the returned information on to IBM Services.
CTE0130 | The specified search argument exceeds the maximum length. The current search argument length is "%1" and the maximum supported length is "%2". |
Explanation: The length of the specified search argument is "%1". The maximum length must not exceed "%2".
What to do: Reduce the length of your search argument to "%2".
CTE0131 | The user-defined function "%1". "%2" does not exist. |
Explanation: The specified user-defined function does not exist in this database.
What to do: Check the name specified for this user-defined function, or register the user-defined function in the database you are using.
CTE0132 | The text index "%1". "%2" does not exist. |
Explanation: The specified text index does not exist in this database.
What to do: Check the name specified and the database you are using. Use the db2ext.textcolumns view to see the existing text indexes.
CTE0133 | The text index "%1". "%2" already exists. |
Explanation: The text index that you specified already exists in this database.
What to do: Check the name specified and the database you are using. Use the db2ext.textcolumns view to see the existing text indexes.
CTE0135 | The object "%1". "%2" does not exist. |
Explanation: The specified object name does not exist in this database.
What to do: Check the object name specified and the database you are using.
CTE0136 | The column "%1" does not exist in "%2"."%3". |
Explanation: The specified column does not exist.
What to do: Check the column name that you specified. Check the table, view, or database you are using.
CTE0137 | The table space "%1" does not exist. |
Explanation: The specified tablespace does not exist in this database.
What to do: Check the name specified and the database you are using.
CTE0138 | The table space "%1" is not regular. |
Explanation: The specified table space is not regular. The event table can only be created in a regular table space.
What to do: Use this command again with a regular table space.
CTE0139 | The environment variable "%1" is not set. |
Explanation: A required environment variable is not set.
What to do: Check your environment, specify the required variable, and use the command again.
CTE0140 | The database "%1" is already enabled for text. |
Explanation: The database you specified is already enabled for text.
What to do: Check the name that you specified. Also check the DB2DBDFT variable that implies an implicit connection.
CTE0141 | The database "%1" is not enabled for text. |
Explanation: The database you specified is not enabled for text.
What to do: Check the database name you specified and the DB2DBDFT variable. If the database name is correct, use the command db2text enable database for text.
CTE0142 | The command requires control authority on "%1". "%2" granted to user "%3". |
Explanation: You do not have the authority to use this command.
What to do: Only the owner of this table can use this command or provide you with the required authorization.
CTE0143 | The command requires database administration authority for user "%1". |
Explanation: You do not have the required authority to use this command.
What to do: Only the owner of the database can use this command or provide you with the required authorization.
CTE0144 | There is at least one text index active in database "%1". |
Explanation: You cannot disable your database until all text indexes are dropped.
What to do: See the db2ext.textcolumns view for the existing indexes. Drop the existing indexes using the DROP INDEX command or specify the FORCE option with the DISABLE DATABASE command.
CTE0145 | The CCSID "%1" is not supported. |
Explanation: The CCSID that you specified is not supported.
What to do: Specify a valid CCSID.
CTE0146 | The language "%1" is not supported. |
Explanation: The specified language is not supported.
What to do: Specify a valid language.
CTE0147 | The format "%1" is not supported. |
Explanation: The specified format is not supported.
What to do: Specify a valid format.
CTE0148 | The specified format "%1" does not accept a model file. |
Explanation: The format "%1" does not support model files.
What to do: Use a format that accepts a model file, or remove the model file from your command.
CTE0149 | Too many terms (beginning with "%1") are specified for the index update frequency. |
Explanation: The syntax for the update frequency is not correct.
What to do: Ensure that the DAY, HOUR, and MINUTE parameters are only specified once.
CTE0150 | Unexpected end of command. Check the command syntax. |
Explanation: The command syntax is not correct.
What to do: Check the command syntax. Verify that you specified the required parameters.
CTE0151 | Token "%1" is unexpected. Check the command syntax. |
Explanation: The syntax of the command is not correct.
What to do: Check the command syntax and verify that the token you are using is allowed in the specific command.
CTE0152 | Token "%1"is too long. |
Explanation: The token is too long.
What to do: Check the command syntax and verify that the token is reduced to the maximum size allowed.
CTE0153 | Token "%1" occurs twice in the update frequency. |
Explanation: You specified an incorrect syntax for the update frequency.
What to do: Ensure that the DAY, HOUR, and MINUTE parameters are only specified once.
CTE0154 | The value "%1" for "%2" is out of range. The valid range is "%3" - "%4". |
Explanation: You specified an incorrect value. The value should be in the allowed range.
What to do: Update your command. Change the value to match those in the allowed range.
CTE0155 | The search string is empty. |
Explanation: You specified an empty search string.
What to do: Check that the search string includes valid alphanumeric characters.
CTE0157 | Syntax error near "%1". |
Explanation: You specified an incorrect search syntax.
What to do: Check the syntax near %1. Correct and try again.
CTE0158 | The freetext search string is missing. |
Explanation: Specify a freetext string.
What to do: Check that the search string after "is about" includes valid alphanumeric characters.
CTE0159 | Search string exceeds the allowed length of "%1". |
Explanation: The search string is too long.
What to do: Reduce the size of the search string and try again.
CTE0160 | No section name has been specified in the search string. |
Explanation: You need to specify a valid section name.
What to do: Add a valid section name and try again.
CTE0162 | The escape command could not be processed. |
Explanation: Your search string includes too many special characters that can be used as masking characters.
What to do: Reduce the number of special characters in your search term, or avoid the escape command. The following special characters can be used: ! * + , _ . : ; { } ~ | ? [ ] ` = \
CTE0163 | No thesaurus name specified in thesaurus clause. |
Explanation: A thesaurus search is requested without a thesaurus name.
What to do: Specify a thesaurus name in your search argument.
CTE0164 | Syntax error in thesaurus relation "%1". |
Explanation: The specified syntax for the thesaurus relation is not correct.
What to do: Update the thesaurus relation according to the syntax specification.
CTE0166 | Freetext must be the last statement in search query. |
Explanation: It is not allowed to have further operators after the "is about" token.
What to do: Rewrite the query string. The last operator must be "is about".
CTE0167 | Syntax error in free text query "%1". |
Explanation: The syntax for the free text string is not correct.
What to do: Update the free text string according to the syntax specification.
CTE0168 | A left parenthesis in a section statement is missing. |
Explanation: The syntax for the section statement is not correct.
What to do: Update the section statement according to the syntax specification.
CTE0169 | A comma or right parenthesis is missing in a section statement. |
Explanation: The syntax for the section statement is not correct.
What to do: Update the section statement according to the syntax specification.
CTE0170 | A closing double quote is missing. |
Explanation: The specified syntax for the search term is not correct.
What to do: Update the search term according to the syntax specification.
CTE0171 | An open double quote for a section name is missing. |
Explanation: The syntax for the section statement is not correct.
What to do: Update the section statement according to the syntax specification.
CTE0172 | The closing double quote for the section name is missing. |
Explanation: The syntax for the section statement is not correct.
What to do: Update the section statement according to the syntax specification.
CTE0173 | One escape character must be defined in an escape clause. |
Explanation: There can be no more than one character in an escape clause.
What to do: Remove the additional characters in the escape clause.
CTE0174 | A blank character is not allowed as an escape character. |
Explanation: It is not allowed to have a blank character in an escape clause.
What to do: Change the escape clause to a clause with a valid character.
CTE0175 | An escape clause is defined but no mask character is found in the search phrase. |
Explanation: An escape clause is specified without using a mask character.
What to do: Remove the escape clause.
CTE0176 | The succeeding character of an escape character in the phrase is neither the same character nor a mask character. |
Explanation: The character after the escape character must be either a masking character or the escape character itself.
What to do: Change the search string to correctly use the escape character.
CTE0177 | The number value "%1" is invalid. |
Explanation: The specified number in the search argument is not valid.
What to do: Check the documentation about the valid range. Update the value in the search argument.
CTE0178 | Mask characters in fuzzy phrase must be preceded by an escape character. |
Explanation: Masking together with fuzzy search is not allowed.
What to do: Update the search string with an escape character.
CTE0179 | Thesaurus name "%1" exceeds allowed length of "%2". |
Explanation: Primary keys longer than 60 bytes are not supported.
What to do: Change the layout of the table before creating the index again.
CTE0180 | Thesaurus "%1" can not be found. |
Explanation: The thesaurus specified cannot be found.
What to do: Check that the thesaurus files are located in the thesaurus directory or fully qualified.
CTE0181 | Library "%1" cannot be loaded. |
Explanation: A library cannot be found.
What to do: Check that the library is located in the library path and available. Start and stop DB2 to ensure that the current settings are used.
CTE0182 | Function "%1" cannot be loaded from library "%2". |
Explanation: A library entry point cannot be loaded.
What to do: The library accessed seems to be invalid. Check that the library is specified only once.
CTE0183 | Error occurred using shared system resources. |
Explanation: A request to shared system resources like shared memory or semaphores cannot be fulfilled.
What to do: Check the current system status and configuration. On UNIX use the ipcs command to check the resources. Stop all applications, such as DB2 and DB2 Net Search Extender. If further resources are listed, clean them up using ipcrm.
CTE0184 | No db2text start command was issued. |
Explanation: A command was called which requires the locking and update services.
What to do: Start the update and locking services with db2text start.
CTE0185 | The update and locking services are already active. |
Explanation: A db2text start is issued but the update and locking services are already running.
What to do: No further action.
CTE0186 | Update and locking service error occurred, check db2diag.log for details. |
Explanation: An update and locking service error occurred.
What to do: Check the db2diag.log for further information, or clean up your shared resources. See also CTE0183.
CTE0187 | Update and locking services are still active, use FORCE option to stop the services. |
Explanation: The db2text stop command has not stopped the locking services, there are still processes running.
What to do: Check with db2text control which processes are running and wait for those to finish. If you need to stop them, use the FORCE option.
CTE0188 | There is a temporary problem using update and locking services. Please try again. |
Explanation: The db2text stop command has not stopped the locking services. Programs are still running or an inconsistent situation is found.
What to do: Check with db2text control which processes are running and wait for those to finish. To stop them, use the FORCE option.
CTE0189 | The executable program "%1" cannot be found. |
Explanation: The program file cannot be located or accessed.
What to do: Check if the program file is located in the bin or adm directory of the DB2 server. The installation is corrupt if the file cannot be found.
CTE0190 | The executable program "%1" cannot be started. |
Explanation: The program cannot be started.
What to do: Check if the program is located in the bin or adm directory of the DB2 server and that the appropriated libraries are installed. For further information, call the program manually on the server.
CTE0191 | The drop index operation is incomplete. Check db2diag.log for details. |
Explanation: The drop index operation is incomplete, possibly caused by the FORCE option.
What to do: Using the FORCE option drops everything regardless of any errors. Check the index directory for pending files and remove these manually.
CTE0192 | Errors occurred in an update index operation. Check event table "%1". "%2" and db2diag.log for details. |
Explanation: During the index update process, any document errors are written to the event table.
What to do: Check the event table for more information about the document errors. Clean up the event log after the problems have been fixed.
CTE0194 | The type "%1" of column "%2" is not supported. |
Explanation: You used a column that is not in the list of the supported ones.
What to do: Check create index for a list of valid columns for Keys and Indexing. Make the appropriate changes to the command and try again.
CTE0195 | "%1" is not an absolute path. |
Explanation: An absolute path on the server is required.
What to do: Check the path and write an absolute path in the command.
CTE0198 | No corresponding text index. |
Explanation: There is no text index on the column.
What to do: Check if the text index still exists.
CTE0199 | There is no text index corresponding to column "%1" of table "%2". |
Explanation: You tried to search on a column without a text index.
What to do: Check the column you are searching on, or create a text index on the column.
CTE0200 | At least one command option must be specified. |
Explanation: The ALTER INDEX command changes the characteristics of an index, such as the update and storage options. None of the characteristics to be changed was specified.
What to do: Specify at least one command option. Refer to the command syntax for all possible options.
CTE0201 | There is a conflict with an existing text index on the same column. |
Explanation: A text index defined on the same column was created with different parameters from this create index command.
What to do: Correct the parameter values in the create index command. Make sure that following parameters have the same value for the existing index and the index to be created: ccsid, language, format, document model, index configuration, column function, and attributes.
CTE0202 | The object "%1"."%2" must be a view when key columns are specified. |
Explanation: The specified object is not a view. The KEY COLUMNS FOR INDEX ON VIEW clause is only allowed when indexing a column of a view.
What to do: Remove the KEY COLUMNS FOR INDEX ON VIEW(SQL-columname-list) clause.
CTE0203 | The text index "%1"."%2" was not created with the CACHE TABLE option. This is required for command execution. |
Explanation: This command can only be executed if the specified index was created with the CACHE TABLE option.
What to do: Create an index with CACHE TABLE option. Refer to the documentation for the command syntax.
CTE0204 | An attribute name is missing. Add "AS <attribute name>" to the attribute expression. |
Explanation: Whenever a column expression is used in the attribute expression, an attribute name must be supplied. For example: (C1+C2 AS myname).
What to do: Add "AS <attribute name>" to the attribute expression.
CTE0205 | CACHE TABLE expressions are not valid. |
Explanation: The column list in the cache table expression is not valid.
What to do: Correct the cache table column list in the create index command. Make sure the columns exist in the specified table. If a function is applied on a column, verify that it is used correctly.
CTE0206 | ATTRIBUTE expressions are not valid. |
Explanation: The column list in the attribute expression is not valid.
What to do: Correct the attribute column list in the create index command. Make sure the columns exist in the specified table. If a function is applied on a column, verify that it is used correctly.
CTE0207 | KEY COLUMNS FOR INDEX ON VIEW not specified for index on view "%1"."%2". |
Explanation: If indexes on views are created, the KEY COLUMNS FOR INDEX ON VIEW(SQL-columname-list) clause must be specified. The list of column names specifies the columns that UNIQUELY identify a row in the view.
What to do: Include the KEY COLUMNS FOR INDEX ON VIEW(SQL-columname-list) clause in the create index command.
CTE0208 | INITIAL SEARCH RESULT ORDER columns are not valid. |
Explanation: The column list in the INITIAL SEARCH RESULT ORDER(SQL-order-by list) expression is not valid.
What to do: Correct the order by column list in the create index command. Check if the syntax is correct and the columns exist in the specified table. If a function is applied on a column, verify that it is used correctly.
CTE0209 | The type "%1" of attribute column "%2" is not supported, type DOUBLE is required. |
Explanation: For attribute columns, the only supported data type is DOUBLE.
What to do: Make sure the attribute columns of the table with the text column to be indexed are of type DOUBLE. It may be possible to use cast operators in attribute column expressions. Refer to the SQL Reference for data types which can be casted to double.
CTE0210 | The value "%1" for index configuration parameter "%2" is not valid. A valid value is "%3". |
Explanation: The specified value for the configuration parameter is incorrect. For valid values of the parameters refer to the command syntax.
What to do: Correct the index configuration parameter value in the create index command.
CTE0211 | "%1" is not a valid index configuration parameter. |
Explanation: The index configuration option is not known.
What to do: Check the create index command syntax. Valid index configuration options are TreatNumbersAsWords and IndexStopWords. These have to be comma separated: index configuration(treatnumberaswords 1, indexstopwords 1).
CTE0212 | Internal index configuration file "%1" could not be saved. |
Explanation: The internal configuration file for the index could not be saved.
What to do: Make sure the instance owner has write permissions to the directory the file should be saved in. If a file with the same name already exists, make sure that it is writable for the instance owner.
CTE0213 | Internal index configuration file template "%1" could not be loaded. |
Explanation: The internal index configuration file template could not be read.
What to do: Make sure the file exists in the correct location and is readable.
CTE0214 | Internal error when setting new entry "[%1],%2=%3" for index configuration file. |
Explanation: Internal error while writing an internal configuration file for the index.
What to do: If the file exists, check if it is readable and writable for the instance owner. Check that there is enough space on the device where the file is located.
CTE0215 | Index creation on alias "%1"."%2" is not supported. Use base table "%3"."%4" instead. |
Explanation: The index cannot be created on the alias.
What to do: Type in the create index command with the base table.
CTE0217 | The schedule service is already active. |
Explanation: The service is already active, you do not need to start it.
What to do: No action required.
CTE0218 | Function "%1" failed with error code "%2". |
Explanation: A Windows function failed with the specified error code which does not allow further processing.
What to do: Use the specified Windows system error code to get detailed error information.
CTE0219 | The service "%1" could not be opened. Error code "%2". |
Explanation: The specified service cannot be found on the Windows system.
What to do: Check if the specified service is installed on the Windows system. Use the specified Windows system error code to get detailed error information.
CTE0220 | The DB2 instance profile path could not be found. |
Explanation: Internal DB2 function to obtain the DB2 instance profile path failed.
What to do: Create a DB2 instance without specifying the instance profile path information and retry the command.
CTE0221 | UpdateFrequency "%1" is incorrectly specified. |
Explanation: The syntax for the update frequency statement is not correct.
What to do: Correct the update frequency statement according to the syntax specification.
CTE0222 | The schedule service input file "%1" is corrupted. |
Explanation: The scheduler file containing index update information is corrupted.
What to do: Use your system editor and try to correct the problem. Maybe an entry has been truncated, or the ending line character has been deleted. If this does not restore the file content, try the following:
CTE0223 | File "%1" could not be closed. |
Explanation: The file specified cannot be closed.
What to do: Verify that the file is correctly specified.
CTE0224 | File "%1" could not be copied to "%2". |
Explanation: The first file cannot be copied to the second file.
What to do: Verify that the files are correctly specified. Check if the second file already exists and is read only. Also check if there is enough free space on the system.
CTE0225 | File "%1" could not be removed. |
Explanation: The file specified cannot be removed from the system.
What to do: Verify that the file is specified correctly and check the file access rights.
CTE0225 | File "%1" could not be removed. |
Explanation: The file specified cannot be removed from the system.
What to do: Verify that the file is specified correctly and check the file access rights.
CTE0227 | A write operation on file "%1" failed. |
Explanation: The file specified is not writable.
What to do: Verify that the file is correctly specified and check the file access rights. Also check if there is enough free space on the system.
CTE0228 | The user has insufficient access rights at the operating system level. |
Explanation: The command requires administrator rights at the operating system level.
What to do: Ensure that you have operating system administrator rights. Check if you are a member of the administrator group.
CTE0231 | "%1" is not defined in same nodegroup ("%4") as the tablespace of "%2"."%3". |
Explanation: The tablespace of the administration tables is required to be distributed over different nodes in exactly the same way as the table containing the text column to be indexed. To enforce this, it is checked whether the specified tablespace is defined in the same nodegroup.
What to do: Specify a tablespace that is defined in the same nodegroup as the table containing the text column to be indexed.
CTE0232 | The specified or default tablespace "%1" is not single-noded. This is necessary for an index on a view, or when the CACHE TABLE option is specified. |
Explanation: An index on a view or with the CACHE TABLE option enabled is only supported for tables on a single node.
What to do: Put the table in a single-noded tablespace if the default tablespace caused this error. Alternatively, specify another single-noded tablespace, if you specified a multi-noded tablespace.
CTE0233 | There is a conflicting administration command running. Please retry this command later. |
Explanation: Another administration command is still running or terminated abnormally without releasing the command lock.
What to do: Check with CONTROL LIST which locks are still active. If there is an active lock but no command running, clear the lock manually using the CONTROL CLEAR command. Be aware that someone else may be running the administration command holding the lock.
CTE0234 | There is a conflicting administration command running on a text index. Please retry this command later, or specify the FORCE option of a DISABLE DATABASE command. |
Explanation: Another administration command is still running or terminated abnormally without releasing the command lock.
What to do: Check with CONTROL LIST which locks are still active. If there is an active lock but no command running, clear the lock manually using the CONTROL CLEAR command. Be aware that someone else may be running the administration command holding the lock. For a DISABLE DATABASE command you may specify the FORCE option which stops all other commands on that database.
CTE0235 | No valid license found for DB2 Net Search Extender. |
Explanation: There was no valid license found for DB2 Net Search Extender.
What to do: Check whether the license was correctly installed with db2lic. Make sure existing instances are updated after the product install.
CTE0236 | Only Node0 is supported on MPP instances. |
Explanation: Text Indexes can only be created on MPP instances, if the table with the text column to be indexed resides on Node0.
What to do: Check the node group of the tablespace in which the table is defined.
CTE0237 | Internal error: log table "%1"."%2" contains an invalid operation "%3". |
Explanation: The log table keeps track of operations executed on the table containing the indexed text column. This table might be corrupted, as it contains an entry not written by DB2 Net Search Extender.
What to do: Check the log table and delete the corrupted entry.
CTE0238 | Internal error: table "%1"."%2" contains an incorrect syntax expression in column "%3". |
Explanation: There is an error in the expression list in the specified text column.
What to do: Check the delimiter Begin and End pairs.
CTE0239 | Internal error: total length of index properties "%1" exceeds maximum "%2". |
Explanation: The maximum size of the index properties (1016 bytes) is exceeded. The properties contain the instance, index, and work directory as well as other information.
What to do: Make sure these path names are not too long.
CTE0240 | Internal error: setting environment variable "%1" failed. |
Explanation: Setting the specified environment variable failed. There may be a problem with the environment setup.
What to do: Check your OS specific guidelines.
CTE0241 | Internal error: datalink UDF "%1"."%2" returns type "%3". The expected type is: "%4". |
Explanation: The datalink UDF used to fetch the content of a datalink reference is defined with an unexpected datatype.
What to do: Extract the definition of the datalink UDF from SYSCAT.FUNCTIONS and report the error to IBM services.
CTE0242 | Value "%1" for parameter "%2" is invalid. |
Explanation: The search stored procedure or the table valued function DB2EXT.TEXTSEARCH was called with invalid parameters.
What to do: Correct the parameter values of the search stored procedure or table valued function. For valid parameters refer to the documentation.
CTE0243 | The cache for text index "%1"."%2" has not been activated. |
Explanation: A Net Search Extender operation requires an activated cache. The cache is currently not activated. These are the possible reasons:
What to do: Perform a DB2TEXT ACTIVATE CACHE command for the index and rerun the Net Search Extender operation.
CTE0244 | Internal error: call to "%1" returns rc="%2", SQLCODE="%3". |
Explanation: An internal processing error occurred when calling an internal function.
What to do: If the error persists, start a trace and check the db2diag.log. Report the error.
CTE0245 | The requested cache size exceeds the available cache size. Increase the maximum cache size to a value > "%1" or decrease the pctfree value. |
Explanation: The cache size necessary to load all data exceeds the MAXIMUM CACHE SIZE value for an index. This can be detected during activation of the cache (the DB2TEXT ACTIVATE command), or by an index update operation while the cache is activated.
What to do: If the error was reported in a DB2EXT ACTIVATE command, recalculate the maximum cache size using the DB2EXT.MAXIMUM_CACHE_SIZE function and alter the MAXIMUM CACHE SIZE setting for the index. Eventually decrease the PCTFREE value. If the maximum number of documents is exceeded during incremental update, rebuild the cache with the commands db2 deactivate cache and db2text activate cache recreate.
CTE0246 | File "%1" is empty. |
Explanation: A DB2TEXT CREATE INDEX command failed because the document model file specified in the command is empty.
What to do: Specify a valid document model file in the command.
CTE0247 | A DB2 Net Search Extender stored procedure could not be created. |
Explanation: A DB2TEXT ENABLE DATABASE command failed to create the internal stored procedure DB2EXT.CTESRVSP.
What to do: Check the additional DB2 error message associated with a CREATE PROCEDURE statement for details. If the error cannot be corrected by removing an existing stored procedure with an identical name, start a trace and report the error.
CTE0248 | The generated search string is too long. Reduce the complexity of search query. |
Explanation: A Net Search Extender query is too long or too complex to be processed by the base search engine. The complexity is affected by thesaurus expansions, FUZZY FORM OF expressions, and masking characters.
What to do: Reduce complexity or length of the query.
CTE0249 | Executable program "%1" terminated abnormally. |
Explanation: When executing a Net Search Extender command, the executable "%1" was called, but terminated abnormally.
What to do: Verify, that the executable was not terminated explicitly by user interaction, for example, a signal. If not, start a trace, rerun the command, and report the error.
CTE0250 | The return type "%1" of column type transformation function "%2"."%3" is not supported. |
Explanation: In a DB2TEXT CREATE INDEX command a column type transformation was specified that returns an unsupported datatype. Supported datatypes are: CHARACTER, VARCHAR, LONG VARCHAR, CLOB, GRAPHIC, VARGRAPHIC, LONG VARGRAPHIC, DBCLOB, BLOB, and DATALINK.
What to do: Choose a different column type transformation function.
CTE0251 | Internal error: the column type "%1" is not supported. |
Explanation: A column type is used that is not in the list of supported types.
What to do: Check create index for a list of valid columns for Keys and Indexing. Make the appropriate changes to the command and try again. If the error persists, start a trace and also check the db2diag.log. Report the error to IBM Services.
CTE0252 | The parameter "%1" is missing. |
Explanation: Internal error - when executing a Net Search Extender command, an administration executable program was called with a missing parameter "%1".
What to do: Try to change Net Search Extender parameter commands to avoid the problem. If the error persists, switch on the trace function and report the error to IBM Services.
CTE0253 | The document listed in the log view was not found. |
Explanation: The contents of a text document that is listed in the log view has changed and could not be accessed.
What to do: Check that the document exists and the read/access permissions of the text documents to be included in the index.
CTE0254 | The cache for index "%1" is already activated. |
Explanation: The index has already been activated with the ACTIVATE CACHE command.
What to do: Check the specified index name and the database that you are using.
CTE0255 | A column name for a cache result column expression is missing. Add "AS <cache column name>" to the expression. |
Explanation: A cache result column expression must be named. For example: 'C1+C2 AS myresult'.
What to do: Add "AS <cache column name>" to the expression.
CTE0256 | The query necessary to select data for indexing failed. Reduce the complexity of the attribute, cache table, or the initial search result order expressions. |
Explanation: Net Search Extender creates a query from the expressions in your command to select data for indexing from the database. The query failed because it was too complex.
What to do: Reduce the complexity of attribute, cache table, or initial search result order expressions.
CTE0257 | Error creating shared memory. |
Explanation: The shared memory resource could not be created due to a previous error or permission problem.
What to do: Check db2diag.log for further information, or clean up your shared resources. See also error CTE0183.
CTE0258 | Shared memory version error. |
Explanation: The shared memory resource could not be accessed because it is corrupted or there is a version conflict.
What to do: Check db2diag.log for further information. Disable and re-enable the database and then try again.
CTE0259 | Cannot insert entry in global shared memory. Entry already exists. |
Explanation: An entry to be inserted in global shared memory already exists because of a previous error.
What to do: Check db2diag.log for further information. Restart the update and locking services using the commands db2text stop and db2text start.
CTE0260 | Cannot access entry in global shared memory. Entry not found. |
Explanation: An entry to be removed from global shared memory does not exist because of a previous error.
What to do: Check db2diag.log for further information. Try to restart the update and locking services using the commands db2text stop and db2text start.
CTE0261 | There is at least one cache activated for a text index in this instance. Deactivate the cache for any activated index using the DEACTIVATE CACHE command, or use the FORCE option to stop. |
Explanation: The db2text stop command can only be used if you run a DEACTIVATE CACHE command for all text indexes that have been activated with the ACTIVATE CACHE command.
What to do: Deactivate the cache for any activated index using the DEACTIVATE CACHE command or use the FORCE option to stop.
CTE0262 | The value for parameter "%1" is too long. |
Explanation: The value exceeds the maximum allowable size.
What to do: Check the maximum size.
CTE0263 | The text index "%1"."%2" was created with the RECREATE INDEX ON UPDATE option. In this context, the UPDATE MINIMUM or COMMITCOUNT FOR UPDATE may not be specified. |
Explanation: Update minimum and commitcount for update are only effective if the index is updated incrementally.
What to do: If you want to recreate the index each time an update is performed, remove the UPDATE MINIMUM and COMMITCOUNT FOR UPDATE settings. If you want to use UPDATE MINIMUM and COMMITCOUNT FOR UPDATE, do not specify RECREATE INDEX ON UPDATE.
CTE0264 | Errors occurred in an activate index operation. Check event view "%1"."%2" and the db2diag.log for details. |
Explanation: During the index activate process, errors are written to the event table and the db2diag.log file.
What to do: Check the event table for more information about the document errors. Clean up the event log after the problems have been fixed.
CTE0265 | The tablespace of a user table or administration tablespace ("%1") is not only defined on node 0. |
Explanation: If text indexes are created on MPP instances, the tablespace of the user table must only reside on Node0.
What to do: Use a table where the tablespace resides on Node0.
CTE0266 | ValueFrom "%1" must be smaller than ValueTo "%2". |
Explanation: The values specified in the attribute search are not valid. If the search syntax is 'BETWEEN ValueFrom AND ValueTo', the lower boundary (ValueFrom) must be smaller than upper boundary(ValueTo).
What to do: Change the boundaries in the 'BETWEEN ValueFrom AND ValueTo' clause.
CTE0267 | The Net Search Extender database objects in the database "%1" are in an inconsistent state. |
Explanation: At least one DB2 Net Search Extender object is missing or corrupted. Either the database has not been migrated after installation of a new DB2 Net Search Extender product version, or a database user has changed or dropped Net Search Extender internal object(s). In this case, all text indexes are lost and the database has to be disabled for text.
What to do: For a database migration to the current version please follow the migration description found in the DB2 Net Search Extender documentation. Alternatively, issue a DB2TEXT DISABLE DATABASE command using the FORCE option. You can then enable the database for text again by using the DB2TEXT ENABLE DATABASE command.
CTE0270 | Logtable "%1"."%2" could not be modified after incremental update. Entries are to be processed during the next UPDATE. |
Explanation: When starting an incremental index update, a timestamp is created. This serves as a threshold for change records to be processed. Changes occurring concurrently to the incremental update are then processed later, during the next update. In certain situations, there can be changes in transactions that are uncommitted at the time the update starts, but are committed while the index update is being performed. This may potentially lead to inconsistencies.
To avoid such an inconsistent situation, the change records prior to the threshold timestamp are not deleted from the logtable, although they have been partially processed. On the next incremental update the changes will be re-applied to the index.
What to do: On the next index update the changes are re-applied to the index. In case of delete operations, this can lead to the following error: CTE0101: ItlEnReasonCode_Docmap_ docid_not_found.
Note that this error can be ignored, as the document was already deleted. If CTE0270 errors frequently occur, consider dropping and re-creating the index with a modified timestamp threshold for incremental index update. For example: db2text "CREATE INDEX ... INDEX CONFIGURATION(UPDATEDELAY 30)"
This means that processing during an incremental update run only changes records older than 30 seconds and avoids interference with concurrent change transactions of less than 30 seconds.
CTE0273 | The cache for index "%1","%2" is already activated. |
Explanation: The index has already been activated with the ACTIVATE CACHE command.
What to do: Check the specified index name and the database that you are using.
CTE0274 | The target database system "%1" for the connection is not supported. |
Explanation: You tried to execute a DB2TEXT command with a connection to a database system that is not supported by DB2 Net Search Extender.
CTE0275 | The type and version information for server "%1" could not be found. |
Explanation: The type and version information for the server could not be found in the DB2 catalog view 'SERVERS'.
What to do: Make sure that the DB2 federated environment is set up correctly.
CTE0276 | The datalink UDF could not be found. |
Explanation: The datalink UDF is not registered as a user defined function in the database.
What to do: Execute the command 'db2 -tvf ctedlcud.ddl' in the directory db2ext/ddl.
CTE0277 | A cache memory segment could not be attached. |
Explanation: The system cannot allocate enough memory to load a large cache segment, or the cache segment cannot be opened because it has been previously deleted.
What to do: Check your system settings and increase the amount of paging space and free memory. For large cache sizes you may need to prepare your system. Refer to the DB2 Net Search Extender documentation. Use the DEACTIVATE and ACTIVATE [RECREATE] commands to recreate the cache. If the problem persists, check db2diag.log for additional information.
CTE0278 | On an AIX 32-bit system, change the MAXDATA setting before activating a large cache. |
Explanation: When you use the search stored procedure on an AIX 32-bit system, you may need to change the MAXDATA setting for the db2fmp executable.
What to do: Refer to the DB2 Net Search Extender documentation for details about changing the MAXDATA setting.
CTE0279 | The size of the cached data has reached a system limit. |
Explanation: By decreasing the PCTFREE value, you can increase the maximum data size during cache activation. This enables the system to reserve less freespace in the cache.
What to do: Use a lower PCTFREE value or reduce your amount of text data to be cached. Use the DEACTIVATE and ACTIVATE [RECREATE] commands to recreate the cache.
CTE0280 | There is not enough disk space to write persistent cache files. |
Explanation: The system can not write a large enough file for persistent cache in the cache directory.
What to do: Change the persistent cache directory to an empty file system by using the ALTER INDEX command. Alternatively, reduce the cache size by decreasing the PCTFREE or MAXIMUM CACHE SIZE values or by using a temporary cache.
CTE0281 | Deletion of persistent cache file "%1" has failed. |
Explanation: The file does not exist or cannot be accessed.
What to do: Check if this file still exists and delete it manually. ";
CTE0282 | The number of documents in the cache has reached a system limit. |
Explanation: By decreasing the PCTFREE value, you can increase the maximum number of document entries to be cached during cache activation. This enables the system to reserve less freespace in the cache.
What to do: Use a lower PCTFREE value or reduce the amount of document entries in the cache. Use the DEACTIVATE and ACTIVATE [RECREATE] commands to recreate the cache.
CTE0283 | A cache memory segment could not be created. |
Explanation: The system cannot allocate enough memory for loading a large cache segment into memory. By decreasing the PCTFREE value, you achieve a smaller cache segment size.
What to do: Check your system settings and increase the amount of paging space and free memory. You can also decrease the cache size by using a lower PCTREE value. For large cache sizes, you may need to prepare your system. Refer to the DB2 Net Search Extender documentation. Use the DEACTIVATE and ACTIVATE [RECREATE] commands to recreate the cache. If the problem persists, check db2diag.log for additional information.
CTE0284 | The text index is located on node "%1", but the search function was called on node "%2". |
Explanation: The search stored procedure or table valued function DB2EXT.TEXTSEARCH was not called on the node where the index is located. The search function will not automatically be distributed to the correct node.
What to do: Set the DB2NODE environment variable to the node where the index is connected before connecting to the database.
CTE0285 | Search function is not allowed for a text index which is distributed to multiple nodes. |
Explanation: The table valued function DB2EXT.TEXTSEARCH must not be called with indexes that are distributed to multiple nodes, since it will not be automatically distributed to the correct nodes, but executed on the coordinator node.
What to do: Use the CONTAINS, SCORE or NUMBEROFMATCHES function in a multiple node environment.
CTE0286 | No row found in "%1"."IBMSNAP_REGISTER" for source table "%2"."%3" and capture change table "%4"."%5". |
Explanation: No valid entry was found in the IBMSNAP_REGISTER table for the replication capture table characteristics specified in the DB2TEXT CREATE INDEX command. A valid entry must contain the specified source table for the index incolumns SOURCE_OWNER and SOURCE_NAME, with SOURCE_VIEW_QUAL=0 and the specified replication capture table in columns PHYS_CHANGE_OWNER and PHYS_CHANGE_TABLE.
Possible causes: The specified source table was not registered as a replication source for the replication capture table.
What to do: Register the source table correctly for DB2 Replication, or specify a correct replication capture table for the source table.
CTE0287 | Invalid value "%1" for "%2" in "%3"."IBMSNAP_REGISTER" for source table "%4"."%5" and capture change table "%6"."%7". |
Explanation: A replication setting found in the IBMSNAP_REGISTER table is not allowed. Possible causes: 1.The column CHG_UPD_TO_DEL_INS does not contain the value 'Y'. 2.The column CCD_CONDENSED contains the value 'Y'.
What to do: When registering the source table for DB2 Replication, ensure that update operations are transformed into pairs of delete and insert operations. In addition, ensure that no condensed replication capture tables are used.
CTE0288 | Source table "%1"."%2" and capture change table "%3"."%4" are on different servers ("%5" and "%6"). |
Explanation: The specified source table and replication capture table must reside on the same server.
CTE0289 | The wrapper "%1" is not supported. |
Explanation: The wrapper is not supported. Refer to the DB2 Net Search Extender documentation for a list of supported wrappers. See page (WRAPPER) for information.
CTE0290 | The alias "%1"."%2" is not allowed in the replication clause. |
Explanation: You are not allowed to specify an alias for a nickname in a replication clause.
What to do: Specify the nickname instead of the alias, or create a new nickname for the remote table.
CTE0451 | The specified document format "%1" is not supported by the highlighting UDF. |
Explanation: The document format "%1" does not support highlighting.
What to do: Use a document format that is supported by the highlighting UDF.
CTE0452 | Syntax error near option "%1" in the highlighting UDF. |
Explanation: You specified an incorrect syntax near the specified option.
What to do: Check the syntax near option %1. Correct and try again.
CTE0453 | The return size of the highlighting UDF is too small. |
Explanation: The requested parts of the highlighted document does not fit into the return parameter of the highlighting UDF.
What to do: Decrease the window number, the window size and/or the number of sections from which hits should be displayed. This will reduce the document parts returned to the user.
CTE0454 | Error converting the parameters of the highlighting UDF from codepage "%1" to codepage UTF8. |
Explanation: The parameters of the highlighting UDF in the specified CCSID (which may be the default database CCSID), cannot be converted to UTF8.
What to do: Ensure correct specification of the CCSID.
CTE0455 | The database codepage "%1" is not supported in the highlighting UDF. |
Explanation: The database has a codepage which is not supported by the highlighting UDF.
CTE0456 | The highlighting UDF only supports documents in codepage UTF8. |
Explanation: Only documents in codepage UTF8 support the highlighting UDF.
CTE0457 | The value "%1" for parameter "%2" is not valid in the highlighting UDF. |
Explanation: A value for a highlighting parameter is not valid.
What to do: Check the parameter value and ensure that the value is allowed in the data range.
CTE0841 | Missing command option "%1". |
Explanation: A required command option was not specified.
What to do: Check the specified parameters and add the missing parameter.
CTE0842 | No value is specified for the command option "%1". |
Explanation: A required value for a command option was not specified.
What to do: Check the specified parameters and add the missing option.
CTE0843 | No numeric value is specified for the command option "%1". |
Explanation: A string instead of a number has been specified.
What to do: Check the specified parameters and change the string to the correct number.
CTE0844 | The definition file path "%1" is too long. |
Explanation: The specified path is too long and could not be processed.
What to do: Use a shorter path and try again.
CTE0845 | No definition file is specified. |
Explanation: The definition file needs to be specified.
What to do: Add a valid definition file and try the call again.
CTE0846 | The definition file name "%1" is too long. |
Explanation: The specified definition file name is too long.
What to do: Reduce the length of the definition file name to the size allowed.
CTE0847 | The definition file "%1" does not exist. |
Explanation: The specified definition file could not be found.
What to do: Check that the definition file is in the correct path and can be accessed by the current user.
CTE0849 | The dictionary file "%1" could not be locked. |
Explanation: The process was not able to lock the dictionary file. Either you do not have write access, or another process has opened the file for writing.
What to do: Check the running processes to ensure that no process is locking the dictionary file and check your access rights.
CTE0850 | Output file "%1" already exists. |
Explanation: The specified output file could not be overwritten.
What to do: Check that you are able to create the thesaurus in the specified directory.
CTE0851 | The integrity of the dictionary file "%1" is lost. |
Explanation: The thesaurus dictionary files are corrupted.
What to do: Clean up the directory and compile your definition file again.
CTE0852 | Dictionary file "%1" version error. |
Explanation: Your dictionary file was generated with an older version of the thesaurus compiler.
What to do: Compile your definition file again with the current version of the thesaurus compiler.
CTE0853 | The existing dictionary "%1" cannot be overwritten. |
Explanation: An existing dictionary cannot be overwritten.
What to do: Check your write access right on the dictionary file, its directory location and subdirectory location.
CTE0855 | A thesaurus term is incorrectly specified. |
Explanation: There is a syntax error in your definition file.
What to do: Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
CTE0856 | The definition file "%1" is empty. |
Explanation: An empty definition file is not allowed.
What to do: Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
CTE0857 | No block starting line found in file "%1" at line "%2". |
Explanation: There is a syntax error in your definition error.
What to do: A block has to start with ':WORDS'. Check your DB2 Net Search Extender documentation for information on thesaurus concepts.
CTE0858 | An invalid relationship is specified in file "%1" at line "%2". |
Explanation: There is a syntax error in your definition error.
What to do: You have to examine your 'associated-term-definition'. Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file.
CTE0859 | The relationship number is out of range in file "%1" at line "%2". |
Explanation: The user-defined relations are all based on the associative type. They are identified by unique numbers between 1 and 128.
What to do: Verify your relationship numbers.
CTE0861 | No terms are defined in file "%1" at line "%2". |
Explanation: Required terms are not specified.
What to do: Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file.
CTE0861 | The thesaurus term in file "%1" at line "%2" is too long. |
Explanation: The length of the thesaurus term is restricted to 64 bytes.
What to do: Alter the size of your thesaurus term and try again.
CTE0862 | Strength is incorrectly specified in file "%1" at line "%2". |
Explanation: There is a syntax error in your definition file.
What to do: Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
CTE0863 | Strength is out of range in file "%1" at line "%2". |
Explanation: The strength value should be specified between 1 and 100.
What to do: Change the strength value so that it is a numerical value from 1 to 100.
CTE0864 | Internal error: Thesaurus compiler failed with reason code "%1". |
Explanation: An internal processing error occurred that does not allow further processing. Try to start and stop the update and locking services, as well as DB2.
What to do: If the error persists, start a trace and also check the db2diag.log.
CTE0865 | The directory "%1" could not be created. |
Explanation: The specified directory could not be created.
What to do: Check if the directory already exists and the permissions on the directory.
CTE0866 | The directory "%1" could not be removed. |
Explanation: The directory could not be removed.
What to do: Check that you have write permissions on the specified directory.