DB2 - Problem description
Problem IT07463 | Status: Closed |
AFTER UPGRADING FROM V9.7.X TO V10.1 FP3, THE "UPGRADE DATA BASE" COMMAND MAY REPORT SQL1499W | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
After upgrading to DB2 v10.1 FP3 the 'upgrade database' command is used to upgrade the database. If the database is enabled for Text Search the command will appear to be successful: db2 upgrade database <databasename> SQL1499W Database upgrade was successful; however, additional user action may be required. See the administration notification log for more details. Attempting to manually execute the following Text Search stored procedures will fail. $ db2 "CALL SYSPROC.SYSTS_UPGRADE_CATALOG('', ?)" Value of output parameters -------------------------- Parameter Name : MESSAGE Parameter Value : CIE0002I The DB2 Text Search release level is current for the database. The system has not been upgraded. Return Status = 0 $ db2 "CALL SYSPROC.SYSTS_UPGRADE_INDEX('', ?)" SQL20427N An error occurred during a text search administration procedure or command. The error message is "CIE0409E The DB2 Text Search catalog has not been upgraded to the cur". SQLSTATE=38H14 In spite of the above error message, the Text Search catalog data should be updated. You can confirm this by checking that the correct DB2 version number is contained in sysibmts.systsdefaults table. select value from sysibmts.systsdefaults where name = 'VERSION' should return DB2 10.01.0003 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Text Search users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 5 or higher. * **************************************************************** | |
Local Fix: | |
None, the CIE0409E messages are incorrect and can be ignored. | |
Solution | |
Problem fixed in DB2 V10.1 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.03.2015 14.07.2015 14.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |