A DB2 error occurred that does not allow further processing.
For more detailed information on this DB2 error, use db2 ? SQLxxx.
A Search Engine error occurred that does not allow further processing.
For more detailed information, see the Search Engine reason code descriptions.
A system error occurred that does not allow further processing.
Additional information can be found on UNIX in the errno.h header file.
An internal processing error that does not allow further processing. Try to start and stop the update and locking services, as well as DB2.
If the error persists, start a trace and also check the db2diag.log.
The system has run out of memory.
Increase the available memory size for the instance owner, or stop other processes running parallel.
The system has run out of memory.
Increase the available memory size for the user, or stop other processes running parallel.
You tried to create an index on a table that does not have a primary key.
Call the db2 alter table to ensure the existence of a primary key. Then try to create the index again.
You specified a directory which does not exist.
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.
The internal representation of the key columns exceeds the maximum size.
Change the layout of the table before creating the index again. Use smaller key columns, which also benefit performance.
A maximum number of 14 key columns is supported.
Change the layout of the table before creating the index again.
The file specified cannot be read.
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.
The file specified could not be opened.
Verify that the file is correctly specified.
The specified CCSID or the default database CCSID does not match the model file CCSID.
Ensure correct specification of the model file CCSID.
The model file could not be used.
Check that the model file syntax is correctly specified.
An internal locking problem occurred.
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.
You have tried to use a command that is currently not allowed when other commands are running on the index.
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.
You tried to work on more databases than are configured in your lock file.
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.
You tried to work on more indexes for one database than are configured in your lock file.
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.
The operations you are running require more locks for one index than are configured in your lock configuration file.
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.
The configuration file db2extlm.cfg is in error.
Check the db2extlm.cfg file and correct the error. Restart the update and locking services using the command db2text start.
The file db2extlm.cfg could not be opened.
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.
A syntax error was found in the update and locking services configuration file.
Check the update and locking services configuration file for errors.
A required file for update and locking services is corrupted.
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.
An internal error has occurred in the update and locking service area.
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.
DB2 has passed a NULL value to an internal user-defined function.
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.
The length of the specified search argument is "%1". The maximum length must not exceed "%2".
Reduce the length of your search argument to "%2".
The specified user-defined function does not exist in this database.
Check the name specified for this user-defined function, or register the user-defined function in the database you are using.
The specified text index does not exist in this database.
Check the name specified and the database you are using. Use the db2ext.textcolumns view to see the existing text indexes.
The text index that you specified already exists in this database.
Check the name specified and the database you are using. Use the db2ext.textcolumns view to see the existing text indexes.
The specified object name does not exist in this database.
Check the object name specified and the database you are using.
The specified column does not exist.
Check the column name that you specified. Check the table, view, or database you are using.
The specified tablespace does not exist in this database.
Check the name specified and the database you are using.
The specified table space is not regular. The event table can only be created in a regular table space.
Use this command again with a regular table space.
A required environment variable is not set.
Check your environment, specify the required variable, and use the command again.
The database you specified is already enabled for text.
Check the name that you specified. Also check the DB2DBDFT variable that implies an implicit connection.
The database you specified is not enabled for text.
Check the database name you specified and the DB2DBDFT variable. If the database name is correct, use the command db2text enable database for text.
You do not have the authority to use this command.
Only the owner of this table can use this command or provide you with the required authorization.
You do not have the required authority to use this command.
Only the owner of the database can use this command or provide you with the required authorization.
You cannot disable your database until all text indexes are dropped.
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.
The CCSID that you specified is not supported.
Specify a valid CCSID.
The specified language is not supported.
Specify a valid language.
The specified format is not supported.
Specify a valid format.
The format "%1" does not support model files.
Use a format that accepts a model file, or remove the model file from your command.
The syntax for the update frequency is not correct.
Ensure that the DAY, HOUR, and MINUTE parameters are only specified once.
The command syntax is not correct.
Check the command syntax. Verify that you specified the required parameters.
The syntax of the command is not correct.
Check the command syntax and verify that the token you are using is allowed in the specific command.
The token is too long.
Check the command syntax and verify that the token is reduced to the maximum size allowed.
You specified an incorrect syntax for the update frequency.
Ensure that the DAY, HOUR, and MINUTE parameters are only specified once.
You specified an incorrect value. The value should be in the allowed range.
Update your command. Change the value to match those in the allowed range.
You specified an empty search string.
Check that the search string includes valid alphanumeric characters.
You specified an incorrect search syntax.
Check the syntax near %1. Correct and try again.
Specify a freetext string.
Check that the search string after "is about" includes valid alphanumeric characters.
The search string is too long.
Reduce the size of the search string and try again.
You need to specify a valid section name.
Add a valid section name and try again.
Your search string includes too many special characters that can be used as masking characters.
Reduce the number of special characters in your search term, or avoid the escape command. The following special characters can be used: ! * + , _ . : ; { } ~ | ? [ ] ` = \
A thesaurus search is requested without a thesaurus name.
Specify a thesaurus name in your search argument.
The specified syntax for the thesaurus relation is not correct.
Update the thesaurus relation according to the syntax specification.
It is not allowed to have further operators after the "is about" token.
Rewrite the query string. The last operator must be "is about".
The syntax for the free text string is not correct.
Update the free text string according to the syntax specification.
The syntax for the section statement is not correct.
Update the section statement according to the syntax specification.
The syntax for the section statement is not correct.
Update the section statement according to the syntax specification.
The specified syntax for the search term is not correct.
Update the search term according to the syntax specification.
The syntax for the section statement is not correct.
Update the section statement according to the syntax specification.
The syntax for the section statement is not correct.
Update the section statement according to the syntax specification.
There can be no more than one character in an escape clause.
Remove the additional characters in the escape clause.
It is not allowed to have a blank character in an escape clause.
Change the escape clause to a clause with a valid character.
An escape clause is specified without using a mask character.
Remove the escape clause.
The character after the escape character must be either a masking character or the escape character itself.
Change the search string to correctly use the escape character.
The specified number in the search argument is not valid.
Check the documentation about the valid range. Update the value in the search argument.
Masking together with fuzzy search is not allowed.
Update the search string with an escape character.
Primary keys longer than 60 bytes are not supported.
Change the layout of the table before creating the index again.
The thesaurus specified cannot be found.
Check that the thesaurus files are located in the thesaurus directory or fully qualified.
A library cannot be found.
Check that the library is located in the library path and available. Start and stop DB2 to ensure that the current settings are used.
A library entry point cannot be loaded.
The library accessed seems to be invalid. Check that the library is specified only once.
A request to shared system resources like shared memory or semaphores cannot be fulfilled.
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.
A command was called which requires the locking and update services.
Start the update and locking services with db2text start.
A db2text start is issued but the update and locking services are already running.
No further action.
An update and locking service error occurred.
Check the db2diag.log for further information, or clean up your shared resources. See also CTE0183.
The db2text stop command has not stopped the locking services, there are still processes running.
Check with db2text control which processes are running and wait for those to finish. If you need to stop them, use the FORCE option.
The db2text stop command has not stopped the locking services. Programs are still running or an inconsistent situation is found.
Check with db2text control which processes are running and wait for those to finish. To stop them, use the FORCE option.
The program file cannot be located or accessed.
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.
The program cannot be started.
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.
The drop index operation is incomplete, possibly caused by the FORCE option.
Using the FORCE option drops everything regardless of any errors. Check the index directory for pending files and remove these manually.
During the index update process, any document errors are written to the event table.
Check the event table for more information about the document errors. Clean up the event log after the problems have been fixed.
You used a column that is not in the list of the supported ones.
Check create index for a list of valid columns for Keys and Indexing. Make the appropriate changes to the command and try again.
An absolute path on the server is required.
Check the path and write an absolute path in the command.
There is no text index on the column.
Check if the text index still exists.
You tried to search on a column without a text index.
Check the column you are searching on, or create a text index on the column.
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.
Specify at least one command option. Refer to the command syntax for all possible options.
A text index defined on the same column was created with different parameters from this create index command.
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.
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.
Remove the KEY COLUMNS FOR INDEX ON VIEW(SQL-columname-list) clause.
This command can only be executed if the specified index was created with the CACHE TABLE option.
Create an index with CACHE TABLE option. Refer to the documentation for the command syntax.
Whenever a column expression is used in the attribute expression, an attribute name must be supplied. For example: (C1+C2 AS myname).
Add "AS <attribute name>" to the attribute expression.
The column list in the cache table expression is not valid.
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.
The column list in the attribute expression is not valid.
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.
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.
Include the KEY COLUMNS FOR INDEX ON VIEW(SQL-columname-list) clause in the create index command.
The column list in the INITIAL SEARCH RESULT ORDER(SQL-order-by list) expression is not valid.
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.
For attribute columns, the only supported data type is DOUBLE.
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.
The specified value for the configuration parameter is incorrect. For valid values of the parameters refer to the command syntax.
Correct the index configuration parameter value in the create index command.
The index configuration option is not known.
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).
The internal configuration file for the index could not be saved.
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.
The internal index configuration file template could not be read.
Make sure the file exists in the correct location and is readable.
Internal error while writing an internal configuration file for the index.
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.
The index cannot be created on the alias.
Type in the create index command with the base table.
The service is already active, you do not need to start it.
No action required.
A Windows function failed with the specified error code which does not allow further processing.
Use the specified Windows system error code to get detailed error information.
The specified service cannot be found on the Windows system.
Check if the specified service is installed on the Windows system. Use the specified Windows system error code to get detailed error information.
Internal DB2 function to obtain the DB2 instance profile path failed.
Create a DB2 instance without specifying the instance profile path information and retry the command.
The syntax for the update frequency statement is not correct.
Correct the update frequency statement according to the syntax specification.
The scheduler file containing index update information is corrupted.
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:
The file specified cannot be closed.
Verify that the file is correctly specified.
The first file cannot be copied to the second file.
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.
The file specified cannot be removed from the system.
Verify that the file is specified correctly and check the file access rights.
The file specified cannot be removed from the system.
Verify that the file is specified correctly and check the file access rights.
The file specified is not writable.
Verify that the file is correctly specified and check the file access rights. Also check if there is enough free space on the system.
The command requires administrator rights at the operating system level.
Ensure that you have operating system administrator rights. Check if you are a member of the administrator group.
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.
Specify a tablespace that is defined in the same nodegroup as the table containing the text column to be indexed.
An index on a view or with the CACHE TABLE option enabled is only supported for tables on a single node.
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.
Another administration command is still running or terminated abnormally without releasing the command lock.
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.
Another administration command is still running or terminated abnormally without releasing the command lock.
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.
There was no valid license found for DB2 Net Search Extender.
Check whether the license was correctly installed with db2lic. Make sure existing instances are updated after the product install.
Text Indexes can only be created on MPP instances, if the table with the text column to be indexed resides on Node0.
Check the node group of the tablespace in which the table is defined.
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.
Check the log table and delete the corrupted entry.
There is an error in the expression list in the specified text column.
Check the delimiter Begin and End pairs.
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.
Make sure these path names are not too long.
Setting the specified environment variable failed. There may be a problem with the environment setup.
Check your OS specific guidelines.
The datalink UDF used to fetch the content of a datalink reference is defined with an unexpected datatype.
Extract the definition of the datalink UDF from SYSCAT.FUNCTIONS and report the error to IBM services.
The search stored procedure or the table valued function DB2EXT.TEXTSEARCH was called with invalid parameters.
Correct the parameter values of the search stored procedure or table valued function. For valid parameters refer to the documentation.
A Net Search Extender operation requires an activated cache. The cache is currently not activated. These are the possible reasons:
Perform a DB2TEXT ACTIVATE CACHE command for the index and rerun the Net Search Extender operation.
An internal processing error occurred when calling an internal function.
If the error persists, start a trace and check the db2diag.log. Report the error.
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.
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.
A DB2TEXT CREATE INDEX command failed because the document model file specified in the command is empty.
Specify a valid document model file in the command.
A DB2TEXT ENABLE DATABASE command failed to create the internal stored procedure DB2EXT.CTESRVSP.
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.
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.
Reduce complexity or length of the query.
When executing a Net Search Extender command, the executable "%1" was called, but terminated abnormally.
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.
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.
Choose a different column type transformation function.
A column type is used that is not in the list of supported types.
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.
Internal error - when executing a Net Search Extender command, an administration executable program was called with a missing parameter "%1".
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.
The contents of a text document that is listed in the log view has changed and could not be accessed.
Check that the document exists and the read/access permissions of the text documents to be included in the index.
The index has already been activated with the ACTIVATE CACHE command.
Check the specified index name and the database that you are using.
A cache result column expression must be named. For example: 'C1+C2 AS myresult'.
Add "AS <cache column name>" to the expression.
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.
Reduce the complexity of attribute, cache table, or initial search result order expressions.
The shared memory resource could not be created due to a previous error or permission problem.
Check db2diag.log for further information, or clean up your shared resources. See also error CTE0183.
The shared memory resource could not be accessed because it is corrupted or there is a version conflict.
Check db2diag.log for further information. Disable and re-enable the database and then try again.
An entry to be inserted in global shared memory already exists because of a previous error.
Check db2diag.log for further information. Restart the update and locking services using the commands db2text stop and db2text start.
An entry to be removed from global shared memory does not exist because of a previous error.
Check db2diag.log for further information. Try to restart the update and locking services using the commands db2text stop and db2text start.
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.
Deactivate the cache for any activated index using the DEACTIVATE CACHE command or use the FORCE option to stop.
The value exceeds the maximum allowable size.
Check the maximum size.
Update minimum and commitcount for update are only effective if the index is updated incrementally.
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.
During the index activate process, errors are written to the event table and the db2diag.log file.
Check the event table for more information about the document errors. Clean up the event log after the problems have been fixed.
If text indexes are created on MPP instances, the tablespace of the user table must only reside on Node0.
Use a table where the tablespace resides on Node0.
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).
Change the boundaries in the 'BETWEEN ValueFrom AND ValueTo' clause.
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.
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.
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.
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.
The index has already been activated with the ACTIVATE CACHE command.
Check the specified index name and the database that you are using.
You tried to execute a DB2TEXT command with a connection to a database system that is not supported by DB2 Net Search Extender.
The type and version information for the server could not be found in the DB2 catalog view 'SERVERS'.
Make sure that the DB2 federated environment is set up correctly.
The datalink UDF is not registered as a user defined function in the database.
Execute the command 'db2 -tvf ctedlcud.ddl' in the directory db2ext/ddl.
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.
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.
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.
Refer to the DB2 Net Search Extender documentation for details about changing the MAXDATA setting.
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.
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.
The system can not write a large enough file for persistent cache in the cache directory.
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.
The file does not exist or cannot be accessed.
Check if this file still exists and delete it manually. ";
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.
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.
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.
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.
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.
Set the DB2NODE environment variable to the node where the index is connected before connecting to the database.
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.
Use the CONTAINS, SCORE or NUMBEROFMATCHES function in a multiple node environment.
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.
Register the source table correctly for DB2 Replication, or specify a correct replication capture table for the source table.
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'.
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.
The specified source table and replication capture table must reside on the same server.
The wrapper is not supported. Refer to the DB2 Net Search Extender documentation for a list of supported wrappers. See page *** for information.
You are not allowed to specify an alias for a nickname in a replication clause.
Specify the nickname instead of the alias, or create a new nickname for the remote table.
This message number is reserved for specific Net Search Extender errors.
Respond to the specific error message.
The document format "%1" does not support highlighting.
Use a document format that is supported by the highlighting UDF.
You specified an incorrect syntax near the specified option.
Check the syntax near option %1. Correct and try again.
The requested parts of the highlighted document does not fit into the return parameter of the highlighting UDF.
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.
The parameters of the highlighting UDF in the specified CCSID (which may be the default database CCSID), cannot be converted to UTF8.
Ensure correct specification of the CCSID.
The database has a codepage which is not supported by the highlighting UDF.
Only documents in codepage UTF8 support the highlighting UDF.
A value for a highlighting parameter is not valid.
Check the parameter value and ensure that the value is allowed in the data range.
A required command option was not specified.
Check the specified parameters and add the missing parameter.
A required value for a command option was not specified.
Check the specified parameters and add the missing option.
A string instead of a number has been specified.
Check the specified parameters and change the string to the correct number.
The specified path is too long and could not be processed.
Use a shorter path and try again.
The definition file needs to be specified.
Add a valid definition file and try the call again.
The specified definition file name is too long.
Reduce the length of the definition file name to the size allowed.
The specified definition file could not be found.
Check that the definition file is in the correct path and can be accessed by the current user.
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.
Check the running processes to ensure that no process is locking the dictionary file and check your access rights.
The specified output file could not be overwritten.
Check that you are able to create the thesaurus in the specified directory.
The thesaurus dictionary files are corrupted.
Clean up the directory and compile your definition file again.
Your dictionary file was generated with an older version of the thesaurus compiler.
Compile your definition file again with the current version of the thesaurus compiler.
An existing dictionary cannot be overwritten.
Check your write access right on the dictionary file, its directory location and subdirectory location.
There is a syntax error in your definition file.
Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
An empty definition file is not allowed.
Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
There is a syntax error in your definition error.
A block has to start with ':WORDS'. Check your DB2 Net Search Extender documentation for information on thesaurus concepts.
There is a syntax error in your definition error.
You have to examine your 'associated-term-definition'. Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file.
The user-defined relations are all based on the associative type. They are identified by unique numbers between 1 and 128.
Verify your relationship numbers.
Required terms are not specified.
Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file.
The length of the thesaurus term is restricted to 64 bytes.
Alter the size of your thesaurus term and try again.
There is a syntax error in your definition file.
Check your DB2 Net Search Extender documentation for information on creating a thesaurus definition file and thesaurus support.
The strength value should be specified between 1 and 100.
Change the strength value so that it is a numerical value from 1 to 100.
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.
If the error persists, start a trace and also check the db2diag.log.
The specified directory could not be created.
Check if the directory already exists and the permissions on the directory.
The directory could not be removed.
Check that you have write permissions on the specified directory.