The user-defined functions provided by Text Extender can return error states. Example:
SQL0443N User-defined function "DB2TX.CONTAINS" (specific name "DES5A") has returned an error SQLSTATE with diagnostic text "Cannot open message file". SQLSTATE=38702
The messages in this section are arranged by SQLSTATE number.
01H10 | The file file-name cannot be opened. |
What to do: Ensure that the file exists, and that the DB2 instance name has the necessary permissions to open it.
01H11 | The text handle is incomplete |
Explanation: An attempt was made to use a handle that has been initialized, but not completed. A partial handle was created using INIT_TEXT_HANDLE containing preset values for the document language and format. However, the handle has not been completed by a trigger.
What to do: Use only handles that have been completed. If the handle concerned is stored in a handle column, enable or reenable its corresponding text column.
01H12 | Search arguments too long. The second argument was ignored. |
Explanation: The REFINE UDF was used to combine two search arguments, but the combined length of the search arguments is greater than the maximum allowed for a LONG VARCHAR. The REFINE UDF returns the first search argument instead of a combined one.
What to do: Reduce the length of one or both search arguments, then repeat the query.
01H13 | A search argument contains a stopword. |
Explanation: The specified query contains at least one search term consisting only of stop words. The search term was ignored when processing the query.
What to do: Avoid using stop words in Text Extender queries.
01H14 | A language dictionary for linguistic processing is missing. |
Explanation: Text Extender linguistic services cannot find the dictionary files. The query is processed without linguistic support. The dictionary files corresponding to the specified language code(s) are not in the expected path.
What to do: For UNIX, check that the required dictionary is in the path {DB2TX_INSTOWNERHOMEDIR}/db2tx/dicts. For OS/2, check that the required dictionary is in the path specified in the text configuration settings. If necessary, install the required dictionary.
01H15 | A linguistic search term specification does not match the index type. |
Explanation: The linguistic specification of the search term of the query does not correspond to the type of index. For example, PRECISE FORM OF should not be used with a linguistic index. The default linguistic specification is used as shown in Table 5.
What to do: Adapt your application to prevent the specification of query options that conflict with the index type.
38700 | The Text Extender library is not current. |
Explanation: An attempt was made to use a handle that can be interpreted only by a later version of the Text Extender library.
What to do: Ensure that the path to the current library version is set correctly, and that you have the necessary permissions to access it.
Look in the DB2 catalog view SYSCAT.FUNCTIONS, in the IMPLEMENTATION column, for the UDF that caused the problem.
38701 | tracefile Cannot open this trace file. |
Explanation: An attempt was made to use a trace function that writes to the file DB2TX_TRACEFILE in the directory DB2TX_TRACEDIR. Either the file does not exist, cannot be found, or the necessary permissions for the file are not available.
38702 | Cannot open message file message-file. |
Explanation: A situation occurred that caused Text Extender to attempt to return a message. The file containing the messages either does not exist or cannot be found, or the necessary permissions for the file are not available.
What to do: Ensure that the file exists, that the path is set correctly, and that you have the necessary permissions to open the file.
38704 | The format of the text handle is incorrect. |
Explanation: A handle having an incorrect format was used as an argument for a Text Extender UDF.
What to do: Ensure that the handle was not produced by INIT_TEXT_HANDLE.
38705 | udfname Incorrect UDF declaration. |
Explanation: The specific name of a UDF has been changed in the script where the UDFs are declared. UDF names can be changed, but not their specific names.
What to do: Check the script DESCVDF.DDL that contains the UDF declarations, to ensure that the correct names are still being used. Check the names against those in the original distribution media.
38706 | attribute Cannot recognize this attribute value. |
Explanation: An attempt was made to set a CCSID, format, or language to an unknown value.
What to do: Refer to Information about text documents for the correct values.
38707 | The requested function is not yet supported. |
Explanation: The specified function is not yet supported.
What to do: Check the specified function.
38708 | return code |
Explanation: An error occurred while processing the search request.
What to do: Refer to the description of the return code in Chapter 12, Return codes.
38709 | Not enough memory available. |
Explanation: Not enough memory is available to run the UDF.
What to do: Close any unnecessary applications to free memory, then try again.
38710 | errornumber Cannot access the search results. |
Explanation: An error occurred while attempting to read the list of found documents (result list) returned by the search service.
What to do: Try repeating the search. If this is not successful, restart the search service. If the problem persists, report it to your local IBM representative, stating the error number.
38711 | Severe internal error. |
Explanation: A severe error occurred.
What to do: Report the error to your local IBM representative, stating the circumstances under which it occurred.
38712 | indexname Incorrect handle in this text index. |
Explanation: A handle has been damaged.
What to do: Use UPDATE INDEX to rebuild the index.
38714 | Shorten DB2TX_INSTOWNERHOMEDIR environment variable. |
Explanation: The name of the home directory of the instance owner must be no longer than 256 characters.
What to do: Use links to reduce the length of the directory name.
38717 | The specified thesaurus could be found. |
Explanation: The specified thesaurus cannot be found.
What to do: Check the specified thesaurus name.
38718 | The specified relation name could not be found in the thesaurus. |
Explanation: The specified relation does not exist in the specified thesaurus.
What to do: Ensure that the specified relation exists.
38719 | A search processing error occurred. Reason code: %s. |
Explanation: The search could not be made due to the specified reason.
What to do: Try to solve the problem reported by the reason code. If the specified reason is not helpful and no further information is found in the desdiag.log file, create a trace and report the information to your local IBM representative.
38720 | A shared memory attach error occurred. |
Explanation: The system is unable to get access to shared memory.
What to do: Check your system configuration and increase shared resources, or check the current shared resource usage (ipcs) and clean up resources that are no longer needed.
38721 | A semapore creation/access error occurred. |
Explanation: The system is unable to create or get access to a semaphore.
What to do: Check your system configuration and increase shared resources, or check the current shared resource usage (ipcs) and clean up resources that are no longer needed.
38722 | A search process didn't return. |
Explanation: An error occurred while processing the search request.
What to do: Verify your system configuration descfgcl and check if all nodes are up and running.
38723 | The index CCSID and query CCSID do not match. |
Explanation: The database CCSID used for the query string is not the same as the CCSID of the text index.
What to do: Disable the text index and recreate it using the CCSID of the database.
38724 | The section or model name is incorrect. |
Explanation: The specified section or model name in the query is incorrect.
What to do: Check the section or model name.
38726 | A model-file read error occurred. |
Explanation: The model-definition file was not found or cannot be opened.
What to do: Check that the model-definition file exists in the index directory.