|
Problem IC95243
|
Status: Closed |
DB2_INSTALL AND INSTALLFIXPACK COMMANDS CANNOT FIND THE DEFAULT FILE LOCATION OF THE NLPACK |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
db2_install and installFixPack on the older db2 version,
Language support module can be installed without any operator
intervention even if nlpack location is not specified with -c
option, but ones on db2 v10.1 version cannot find the default
file location of the nlpack and requires its location by the
following intervention message:
ex,
root $ ls
nlpack server
root $ cd server
root $ ./installFixPack -d -b /work/TMP/TEST/INSTALL/V101GA_ESE
-p /work/TMP/TEST/INSTALL/V101FP1_ESE
...
Task #36 start
Description: Product Messages - Japanese
Estimated time 37 second(s)
Enter the location of the CD labeled "" or press enter to accept
the default path.
Volume label
Type 'a' to abort the installation.
[/work/TMP/V101FP1/server/db2/aix/install/../../..]: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* nlpack users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 fixpack 3 *
**************************************************************** |
| Local Fix: |
Input the full pathname of nlpack location like below
[/work/TMP/V101FP1/server/db2/aix/install/../../..]:
/work/TMP/V101FP1/nlpack/ |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 version 10.5 fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
