home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65605 Status: Geschlossen

INCORRECT RC CODE AND BEHAVIOR WHEN A WRONG PATH OR FILE NAME FOR
RESPONSE FILE WAS SPECIFIED DURING THE SILENT INSTALLATION

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
During the silent installation of DB2 when a non-existing 
response file is specified an error message is displayed in a 
Windows Popup. 
 
For example, installing DB2 using the following command: 
 
setup.exe /u where is a non-existing response file 
 
The following error is displayed in a popup window 
 
 
ERROR: Problem encountered with response file 
 
'D:\DATA1\PK\UNIVERSAL\db2\Windows\samples\db2ese_.rsp'. The 
file does 
not exist. 
 
The installation process is stopped and is waiting for user 
action to click on 'OK' in the popup window. When clicked the 
installation returns with incorrect return code 0. This is 
suboptimal for a silent installation. 
 
 
 
LOCAL FIX: 
N/A
Problem-Zusammenfassung:
INCORRECT RC CODE AND BEHAVIOR WHEN A WRONG PATH OR FILE NAME 
FOR RESPONSE FILE WAS SPECIFIED DURING THE SILENT INSTALLATION
Local-Fix:
N/A
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
First Fixed in DB2 V9.1 FP9
Workaround
N/A
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65606 IC65607 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.01.2010
16.04.2010
16.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP9
Problem behoben lt. FixList in der Version
9.1.0.9 FixList