IBM (R) DB2 (R) Net Search Extender Release Notes Version 8.1.4.1 (C) Copyright International Business Machines Corporation 2001, 2003. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ------------------------------------------------------------------------ Table of Contents DOCUMENTATION HINTS AND TIPS PREREQUISITES PROBLEMS ------------------------------------------------------------------------ Welcome to IBM DB2 Net Search Extender Version 8.1.4.1 This file contains information that was not available when the "IBM DB2 Net Search Extender Administration and User's Guide" was put on CD-ROM or printed. DOCUMENTATION ______________ Note that the following information has been added to the latest English version of the book but not to the most recent translated versions. 1. Chapter 2: Installation verification For a partitioned database setup on AIX, a new sample has been shipped. The usage is: nsesample_partitioned database_name[node_number][table_space_filename] 2. Chapter 2: Windows installation The Microsoft Cluster Server is not supported by Net Search Extender. 3. Chapter 11: CONTROL command - LIST parameter The output of the command "db2text control list ..." contains the update progress including the numbers of inserted, updated, and deleted documents. When using a replication capture table, there are no document update operations. Insert operations can be either from an insert or an update operation on the source table the index was created on. 4. Chapter 13: ALTER INDEX command - Usage If the index is created with a cache option, the alter index command is not allowed for the index directory when the index is activated. You need to deactivate the cache first. 5. Chapter 13: CREATE INDEX command - REPLICATION CAPTURE TABLE parameter In the list of supported server types, 'DB2 z/OS v8.1 and later' is incorrect. It should be 'DB2 z/OS v7.2 and later'. 6. Chapter 17: Defining a document model for XML documents - Element parameters When writing an XML Document Model file, the 'locator' must be identical to the tags in the XML document. 7. Chapter 17: What happens when an Outside In document is indexed The default SCCOPT_FALLBACKFORMAT for a document where the format can not be automatically recognized is FI_ASCII. 8. Appendix C: Table 14 row "OPERATION" and Table 16 row "IBMSNAP_OPERATION" When using a replication capture table, update operations are split into a delete and an insert operation. In this case, an insert operation in the event table can be either from an insert, or an update operation on the source table the index was created on. 9. Appendix F Message CTE0360 is not described and not translated. It covers product messages after message translation was completed. HINTS AND TIPS ______________ 1. DB2TEXT START command on Windows Ensure that the user running the command is a member of the Administrators group. Otherwise, the 'db2text start' command will fail with the following message: CTE0218 Function "OpenSCManager()" failed with error code "5". 2. DB2EXT- service on Windows Ensure that the Net Search Extender instance service "DB2EXT-" is running under a user account rather than the system account. Otherwise, you can not enable your database. 3. Escape character during search During search, only single-byte characters are allowed as ESCAPE characters. No double-byte characters are allowed. 4. Drop table Before dropping a table with one or more text indexes, issue the following command for each text index: db2text drop index for text If you drop the table before dropping the index, parts of the index still exist. For example, the administration tables and text index files. If you accidentally drop the table first, you can still drop the index and do a cleanup using the db2text drop index command, even though the table no longer exists. 5. Drop database Before dropping a database with one or more text indexes, issue the following command for each text index: db2text drop index for text If you did not use this command, you have to manually delete all index files in and belonging to this text index. Note that if the indexes from a dropped database are created with an automatic update, you will also need to edit ctedem.dat. To do this, remove all entries belonging to dropped database, and cleanup the scheduler file using the following command: db2text stop force cd ~/sqllib/db2ext for UNIX or cd \sqllib\\db2ext for Windows Edit ctedem.dat with an available editor to remove those lines. 6. As the Net Search Extender event log messages are always in the DB2 server language, event log messages for commands issued from the DB2 Control Center might be displayed in a different language than the DB2 Control Center is running in. 7. If the following DB2 Control Center message displays: 'No license for Net Search Extender found', ensure that the DB2 Administration Server is running, as this message is displayed even, if the license is installed. Check DB2 documentation for information on how to setup and start the DB2 Administration Server. 8. Datalink columns For some applications, the heap size value described in the documentation is too small. Therefore, use following configuration update: db2 update dbm cfg using JAVA_HEAP_SZ 2048 9. If you have modified the db2cli.ini and have problems using Net Search Extender, restore the original version of db2cli.ini. 10.Client Server interoperability It is necessary to install the same Net Search Extender Fix Pack level on both the server and client side. Interoperability from client to server and vice versa is only possible for the list of supported platforms found in the documentation. 11.This version of Net Search Extender supports the syntax of DB2 Text Information Extender V7.2. However, if you incorrectly specify the syntax, the command is finally parsed according to the Net Search Extender V8.1 syntax. This may result in a misleading error message. 12.Indexing performance If the indexing performance decreases during the index update, this may be due to error and warning messages being written to the event log table. 13.Log size If the indexing process is not completed, because the error and warning messages require more space than the available DB2 log size, DB2 will rollback the whole transaction and not commit the log table entries. This means that you will not be able to see the entries. Check the DB2 documentation for information on how to increase your transaction log to avoid this situation. 14.On AIX, to search on large cache tables with the Stored Procedure requires a change to the "maxdata" setting of the db2fmp executable. To do this, logon as instance owner and issue the following commands: db2stop cd ~/sqllib/adm cp db2fmp db2fmp.org /usr/bin/echo '\0040\0\0\0' | dd of=db2fmp bs=4 count=1 seek=19 conv=notrunc To switch back to the original settings, issue the following commands: db2stop cd ~/sqllib/adm cp db2fmp.org db2fmp Note that this change reduces the maximum heap size from 1.2 GB to 0.5 GB. This may influence other applications using this DB2 instance. 15.When using the Create Index Wizard within DB2 Control Center, ensure that the Net Search Extender instance service is running before you click on the "Finish" button. If the instance service is not running, an error message is displayed and the text index is not created. 16.Searching for "" (two consecutive doublequotes) is not supported. 17.Partitioned database support (AIX only) a)Ensure that the DB2 setup is completed as described in the DB2 documentation. The NFS mount needs to be configured with root access and setuid. b)During search, the RESULT LIMIT is evaluated on every node. This means if you have specified RESULT LIMIT 3 and use 4 nodes, you could get up to 12 results. c)If a problem occurs during "db2text start" no detailed message is given as to which of the available nodes are affected. Issuing a second "db2text start" will try to start the service on each of the nodes. If the following message is displayed: CTE0185 The update and locking services are already active the db2text start was successful. 18.Using DBCS object names If you use DBCS object names with db2text administration commands, it is necessary to enclose those names within double quotes to avoid uppercase transformation. 19.Index on nickname with incremental index update using DB2 Replication. If initial updates on two or more indexes are started at the same time, the update command may return a SQL0803N error. In this case, try the update command again. 20.Migration from Text Information Extender 7.2 to Net Search Extender 8.1.x on UNIX After DB2 instance migration, the previous 'sqllib' directory is renamed to 'sqllib_v71'. If you have text indexes stored on the default index directory, move the 'sqllib_v71/db2ext/indexes' directory to the new sqllib directory, 'sqllib/db2ext/indexes'. Ignore the following messages in the migration log file: "SQL0478N DROP or REVOKE on object type object-type1 cannot be processed because there is an object object-name, of type object-type2, which depends on it." The Net Search Extender Administration and User's Guide contains more information about migration, please see Appendix A. 21.Fenced search on Linux If you are using RedHat Version 7.x, you can switch the search UDFs (contains, score, and numberofmatches) from 'fenced' mode to 'not fenced' mode to improve performance. To do this: *log in as root user *change the following functions in /opt/IBM/db2/V8.1/db2ext/ddl/ctecudf.ddl db2ext.textSearch_1K16 db2ext.contains_1K16 db2ext.nmatches_1K16 db2ext.score_1K16 db2ext.textSearch_be1 db2ext.unpack_text_key *cd /opt/IBM/db2/V8.1/lib *cp libctecp.a libctecp.so Where you need to change the keyword 'fenced' to 'not fenced': *log in as instance owner *cd ~/sqllib/db2ext/ddl *connect to the database where you would like to change the search UDFs *call db2 -tvf ctedudf.ddl db2 -tvf ctecudf.ddl 22.Changes to AIX install filesets Use the new AIX pre-requisites: - xlC.aix43.rte 6.0.0.5 on AIX 4.3.3 - xlC.aix50.rte 6.0.0.5 on AIX 5.x PREREQUISITES _____________ Before you install NSE 8.1 Fix Pack 4 please verify that DB2 Version 8.1 Fix Pack 4 is installed. PROBLEMS ________ Windows and UNIX ---------------- 1. Do not use duplicate cache column names. You will not get an error during text index creation or index update, but the search will not work. In this case, you will get an SQL error message that duplicate columns were used. 2. If indexing DATALINK values produces warnings that are too large to display, you will get the following error message: "java.lang.Exception: Error in UDF setSQLmessage.". SQLSTATE=01H80 In this case, check the SQLSTATE. The numbers are described in Appendix K. Data Link messages. 3. Wrong shared memory size requested If you specify a too small maximum cache size during an "activate cache" command, you will get an incorrect figure for the required cache size in the resulting error message. Check the cache size using the DB2EXT.MAXIMUM_CACHE_SIZE and DB2EXT.PCTFREE functions. Correct the maximum cache size with the db2text alter index command and start the process again. 4. Old search syntax with thesaurus usage does not work. You need to reformulate your query using the new search syntax. UNIX ---- 5. Using INSO file format On AIX, it is required to set the environment variables: - DB2ENVLIST='LIBPATH' and - DB2LIBPATH=/sqllib/lib:/usr/opt/db2_08_01/lib. If the variables are not set, an error message occurs during index update, stating that the INSO libraries are not found. It is not recommended to use format specification INSO for XML, HTML or plain text documents. When such a format can not be correctly determined, the document will be indexed as plain text. If special characters or the encoding of special characters are used within such a document, the search will not work correctly. If possible, those formats should be indexed with their own format specifier. 6. Linux search problem with the wrong LANG environment variable If you use a 7-bit ASCII code page as the LANG variable setting, the following error might occur: "SearchString parse: check LANG & locale charmap values." To avoid this, change your LANG variable to a 8-bit LANG value, restart DB2 and try again. 7. SunOS 5.8 and search using zh_TW.BIG5 or ko_KR.BIG5 Net Search Extender does not work with the locales zh_TW.BIG5 or ko_KR.BIG5 on SunOS 5.8. Instead use SunOS 5.9, as this problem is fixed. Windows ------- 8. File access problems If you encounter file access problems, for example, on a document model, text index, or thesaurus, ensure that the user has the correct password and authorizations for running the Net Search Extender instance services. This especially applies to shared resources on mapped network drives. 9. Cache not usable During search or activate cache the following error message may be displayed: "CTE0271 Cache not usable, DEACTIVATE and ACTIVATE RECREATE required." To solve this problem, check your system settings and try to increase the amount of paging space and free memory. DB2 Control Center ------------------ 10.Unexpected messages on Solaris When using DB2 Control Center on the Solaris Operating Environment, error messages might be displayed if several actions are taken within a short period of time. For example: CTE0151 Token "CONTROL" is unexpected. Check the command syntax. As this is a concurrency problem, ignore the messages and wait a short period of time before retrying the actions. Partitioned database support (AIX) ---------------------------------- 11.cteprcrx terminated abnormally (UNIX) Check that the used instance does not have a separate fenced user ID. To check this, list the file .fenced file in /sqllib/adm, where the instance owner is the owner of .fenced. 12.Update index seems to loop Check that your file system has enough free space to store the index files. ------------------------------------------------------------------------ ------------------------------------------------------------------------ Appendix A. Notices IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact: IBM Canada Limited Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CANADA Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious, and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both, and have been used in at least one of the documents in the DB2 UDB documentation library: ACF/VTAM AISPO AIX AIXwindows AnyNet APPN AS/400 BookManager C Set++ C/370 CICS Database 2 DataHub DataJoiner DataPropagator DataRefresher DB2 DB2 Connect DB2 Extenders DB2 OLAP Server DB2 Universal Database Distributed Relational Database Architecture DRDA eServer Extended Services FFST First Failure Support Technology IBM IMS IMS/ESA iSeries LAN Distance MVS MVS/ESA MVS/XA Net.Data NetView OS/390 OS/400 PowerPC pSeries QBIC QMF RACF RISC System/6000 RS/6000 S/370 SP SQL/400 SQL/DS System/370 System/390 SystemView Tivoli VisualAge VM/ESA VSE/ESA VTAM WebExplorer WebSphere WIN-OS/2 z/OS zSeries Trademarks of Other Companies The following terms are trademarks or registered trademarks of other companies and have been used in at least one of the documents in the DB2 UDB documentation library: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Solaris, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Outside In is a registered trademark of Stellent, Inc. Copyright (R) 1996-2003 Stellent, Inc. All rights reserved. Other company, product, or service names may be trademarks or service marks of others. (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001, 2003. ALL RIGHTS RESERVED.