DB2 - Problembeschreibung
Problem IC66934 | Status: Geschlossen |
"DB2TS START FOR TEXT" FAILS IN A NON-ROOT SETUP WITH ERROR SQL20427N/CIE00707 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
In a non-root setup of DB2 V9.5 and V9.7, if the instance is active and the text search component is installed during a work with existing install, text search may not be configured properly. The install log file would show the following error: ERROR:IQQG0026E The configuration file /home/jeevat/sqllib/db2tss/config/config.xml has an error. It is advised in the post install steps, to update the instance since some were active. Since text search is not properly configured, while trying to start text search you may get the following error: $ db2ts start for text SQL20427N An error occurred during a text search administration procedure or command. The error message is "CIE00395 No db2ts start command was issued. ". SQLSTATE=38H14 After applying the fix, you will see the following message in the Post Install Steps of the log: DB2 Text Search has not been configured. Run the db2isetup command to configure the DB2 Text Search server. Manual configuration steps can be found in the DB2 Text Search documentation "http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com. ibm.db2.luw.admin.ts.doc/doc/t0052690.html". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * In a non-root setup of DB2 V9.5 and V9.7, if the instance is * * * * active and the text search component is installed during a * * work * * with existing install, text search may not be configured * * properly. The install log file would show the following * * error: * * * * ERROR:IQQG0026E The configuration file * * /home/jeevat/sqllib/db2tss/config/config.xml has an error. * * * * It is advised in the post install steps, to update the * * instance * * since some were active. * * * * Since text search is not properly configured, while trying * * to * * start text search you may get the following error: * * * * $ db2ts start for text * * SQL20427N An error occurred during a text search * * administration * * procedure or command. The error message is "CIE00395 No * * db2ts * * start command was issued. ". SQLSTATE=38H14 * * * * After applying the fix, you will see the following message * * in * * the Post Install Steps of the log: * * * * DB2 Text Search has not been configured. Run the db2isetup * * command to configure the DB2 Text Search server. Manual * * configuration steps can be found in the DB2 Text Search * * documentation * * "http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/co * ibm.db2.luw.admin.ts.doc/doc/t0052690.html". * **************************************************************** * RECOMMENDATION: * * Upgrade your DB2 V9.5 to Fix Pack 6; or * * Upgrade your DB2 V9.7 to Fix Pack 2. * **************************************************************** | |
Local-Fix: | |
1) Stop the instance using 'db2stop', then run 'db2isetup' to configure text search; or 2) Stop the instance using 'db2stop', then run 'db2nrupdt' to update the instance and manually configure text search. See the "Configuring DB2 Text Search using the Configuration Tool" in the Information Center for more details. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
The fix will be delivered in V9.5 Fix Pack 6 and V9.7 Fix Pack 2. Once the customer has applied the fix, the post install message will indicate to the user that they will need to configure Text Search. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66965 IC66986 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.03.2010 31.05.2010 31.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5., 9.5.FP6, 9.7. | |
Problem behoben lt. FixList in der Version |