DB2 FOR LUW / DB2FORLUW / A50 - DB2

This problem occurs when you do a silent installation of DB2 on 
Windows. That is, it occurs when you install using the "-u 
<response file>" option of the setup command. 
 
When you do a silent installation of DB2 on Windows and the 
response file keyword CLIENT_IMPORT_PROFILE specifies a file 
name without a path name, it ought to apply the configuration 
profile that is in the same directory as the response file. 
 
But if the response file is on a network drive you get error 
DBI20073E in the installation log if the response file keyword 
CLIENT_IMPORT_PROFILE specifies just a file name without a path 
name. 
 
The installation log contains a message like this: 
 
 MSI [...] Invoking remote custom action. [...] Entrypoint: 
CallURECA 
 1: ERROR:DBI20073E The specified command failed because the 
value specified for a 
 keyword in the response file was invalid. Value: 
 "<full path name to the client configuration file in the same 
directory as the response file>". Keyword: 
"[...]CLIENT_IMPORT_PROFILE".

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who install DB2 on Windows                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************

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
 

Problem was first fixed in Version 10.5 Fix Pack 3. 
This fix should be applied for whatever DB2 product you are 
installing when you get the error.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.08.2013
28.02.2014
28.02.2014