*********************************************************************** ** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1997. ** ** ALL RIGHTS RESERVED. ** ** ** *********************************************************************** Welcome to IBM* DB2 Universal Database* (DB2*) Text Extender FixPak U472366 for AIX Version 6.1.2 For installation instructions please see file install.txt This README file contains information for the following products and components: IBM DB2 UDB Text Extender for AIX INSTALLATION NOTES Pre-Requisites This FixPak requires the installation of the following products on the machine where the FixPak is to be installed: DB2 UDB Version 6.1 for AIX Latest DB2 fixpack Minimum database configuration values : APP_CTL_HEAP_SZ = 512 If the fixpack is installed on a server, the fixpack must be installed on each client connected to the server. ---------------------------------------------------------------------- 1. FIXED PROBLEMS 2. DOCUMENTATION CHANGES 2.1 Chapter 4. Administration 2.2 Chapter 10. Syntax of search argument 2.3 Chapter 16. Error event reason codes 3. RESTRICTIONS 4. HINTS 5. KNOWN PROBLEMS 6. MISCELLANEOUS 6.1 DB2 Family Newsletter 6.2 Customer Support 6.3 Corrective Service ********************************************************************** 1. FIXED PROBLEMS __________________ THIS FIXPACK INCLUDES FIXES SUPPLIED WITH FIXPAK U467824. New fixes : 1) Problem with linguistic services. rc: RC_LINGUISTIC_SERVICE_FAILED The problem occurs if multiple queries are running concurrently against the search server. If the problem persists after the fix please cleanup your temp directory. 2) Indexing problem with XML documents. Indexing process hangs. 3) Message in desdiag.log : message unavailable 4) DB2 unit of work hang caused by loop in text extender signal handling. 5) Sigpipe exception during query execution. already fixed with U467824. - Fix for processing of the FUNCTION keyword - Query using multiple sections specified with the SECTION keyword - SYNONYM FORM OF now supported for PRECISE index type - NT only: Abnormal termination of Search_Result UDF if the select list for the output of the UDF contained only one or two parameters - Various fixes for the thesaurus feature. Expansion list of thesaurus lookup is not normalized anymore. - Processing of &cicrc escape sequence in HTML documents - Fix for empty desadmtb.dat after crash during update index - Crash during index creation - NT only : RC_PARSER_SYNTAX_ERROR as result of a DBCS query - Invalid formatting of administration messages - AIX only : Support for DB2 instance creation with fenced userid Problem if instance owner userid was equal to an existing group name - AIX only: Support for locale Ja_JP.IBM-932 2 DOCUMENTATION CHANGES __________________________ 2.1 Chapter 4. Administration The sample for "Enabling external text files" has been updated. 3. Initialize the handle . For each row in a new table: db2 INSERT INTO db2tx.EXTFILE (FILEHANDLES) VALUES (db2tx.INIT_TEXT_HANDLE (850,'TDS','US_ENGLISH', 'd:\dmb\samples\tx')) . For an existing table, update the handle columns to reflect the external reference, specifying the name of the external file. db2 UPDATE db2tx.EXTFILE SET FILEHANDLES = (db2tx.FILE( FILEHANDLES, 'd:\dmb\samples\tx')) WHERE DOCID = 'doc1' 2.2 Chapter 10. Syntax of search argument FUZZY FORM OF the LANGUAGE parameter is not supported. Syntax: FUZZY FORM OF "word or phrase" 2.3 Chapter 16. Error event reason codes ______________________________________________________________________________ 504 Explanation : Document not indexed. Check the index log table for further information. Try to reset the index status and update the index. ______________________________________________________________________________ 621 Explanation : I/O problem. Try to reset the index status and update the index. ______________________________________________________________________________ 831 Explanation : Warning. The document has not been indexed. The reason for this warning is that the document is empty. ______________________________________________________________________________ 861 Explanation : Warning. The documnet has not been indexed. The reason for this warning could be that the document contains only stop words, blanks or non text information. _____________________________________________________________________________ 860 Explanation : File open error. Dictionary or thesaurus files not found. Check that the files are stored in the proper directory. ______________________________________________________________________________ 2008 Explanation : The document was not found. The reason for this error could be that the document was deleted during an index update run. If the document was an external file, check that the path and the file permissions are set correctly. ______________________________________________________________________________ 3. RESTRICTIONS _________________ - Currently comments are not supported in a thesaurus sgml input file. - The DUAL index type should not be used for large tables. Use indextype NGRAM with indexoption CASE_ENABLED instead. - Indexoption FEATURE_EXTRACTION should not be used for large tables. - STEMMED FORM OF for indextype normalized is only supported for US_ENGLISH. - The REFINE UDF does not support IS ABOUT or THESAURUS queries as a query refinement. - Format XML and RFT is not supported for indextype Ngram. - Format HTML is only supported for CCSID 819 for indextype Ngram. - Unicode documents cannot be indexed for indextype Ngram. - Masking is not allowed for SOUNDS LIKE. - The maximum number of model names in the model definition file is 50. - Stemming is not supported for thesaurus searches on a linguistic indextype. - Disks formatted with file system FAT If you have disks formatted with file system FAT you may encounter a problem during index update. The problem occurs if the file desadmtb.dat in directory \\index is updated. To find the index directory name and path for a given text column issue the following command: db2 select indexname, indexdirectory, tablename, columnname from db2tx.textcolumns You can correct this error by issuing: copy desadmtb.bak desadmtb.dat Then update the index by issuing: db2tx update index handle 4. HINTS - For databases with CCSID's other than 850 (Windows NT, OS/2) or 819 (UNIX) the sample command file 'txsample' has to be adapted. Change the CCSID value of the enable step for the Ngram indextype to your database CCSID. - If you are enabling a column with multiple indextypes make sure to add the HANDLENAME for lookup in the db2tx.textcolumns table to retrieve the prototype handle as input to the SEARCH_RESULT UDF. For an example see the txsample.udf file in the samples directory. - AIX only: If the desdiag.log file shows an error ...Shared Memory Access Failed try to remove pending shared resources. Required steps: - db2stop - txstop - ipcs | grep Drop pending listed resources - ipcrm -s nnnnnn ipcrm -m nnnnnn ipcrm -q nnnnnn - db2start - txstart - If the query terminates with reason code : RC_SE_SERVER_NOT_AVAILABLE first check if the search server has been started. If the search server had been started, check your DB2 database configuration. Most probably the problem is caused by a resource problem. Decrease the bufferpool sizes you have defined or decrease the number of buffpages. 5. KNOWN PROBLEMS __________________ - NT EEE: Running multiple enabling commands on the same table in parallel may result in RC 507 shown with db2tx get index status. Workaround: Run the enable commands sequentially. - NT only: Online documentation cannot be viewed using the supplied icons. The problem can be fixed by changing the target URL in the properties window of the Text Extender Administration and Programming icon to the complete path to the file desu9mst.htm. The file is stored in path \doc\html 6 MISCELLANEOUS __________________________ 6.1 DB2 Family Newsletter For the latest information about the DB2 family of products, you may subscribe to the "DB2 Family Newsletter" (English only). Simply send your request in a FAX to 1-905-316-4733, and include the following information: Name Company name Full mailing address Telephone number DB2 products you currently use 6.2 Customer Support _____________________ To speak to an IBM representative regarding assistance with this product, please call 1-800-CALL-AIX (1-800-225-5249). Customer support is also provided via Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. (1) CompuServe - To access the forums on CompuServe, execute GO IBMDB2. - If you don't have access to CompuServe, call 1-800-850-8199 for membership information in Canada or the US. (2) Usenet Newsgroup: comp.databases.ibm-db2 - This Internet Newsgroup is a general forum for discussing questions and/or problems encountered using the DB2 family of products. (3) (IBMLink) Talklink OS/2 BBS - To access the forums on IBMLink, go to the OS2BBS section. - If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the US. 6.3 Corrective Service _______________________ They can be downloaded electronically from the following location: (1) Internet - then go to ps/products/db2extenders/fixes// where is (eg. english-us, spanish, german, etc.) is the product name/version (eg. v12nt, v50aix, etc.) - Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page. (http://www.software.ibm.com/data/db2/db2tech/index.html) If you do not have access to any of the above locations, please call 1-800-CALL-AIX (1-800-225-5249) to request these FixPaks be sent to you in the mail. For countries other than US and Canada, please look at your local IBM OS/2 BBS or call your local DB2 Customer Service number for assistance in obtaining them. ---------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ---------------------------------------------------------------------- ************************************************************************ * * (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1997-2000. * ALL RIGHTS RESERVED. * ************************************************************************