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 IC84018 Status: Geschlossen

FILENAME IN DB2LOOK -O PARAMETER IS CONVERTED INTO LOWER-CASE AND IT MAY
INDUCE 'DB2LOOK UTILITY COULD NOT OPEN FILE' ERROR

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
On Windows systems, if you specify an output filename in 
upper-case letters by the -o option in the db2look utility, the 
file is created in lower-case. 
 
  In addition, if you specify an output file pathname in 
multi-byte letters, the different multi-byte named file may be 
created or db2look fails with 'db2look utility could not open 
file' error. 
 
  There is no such problem on Unix based systems.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.5 FixPak 10                         * 
****************************************************************
Local-Fix:
Not use upper-case or multi-byte letters as an output file 
pathname
Lösung
Problem was first fixed in Version 9.5 FixPak 10
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84046 IC87893 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.06.2012
26.10.2012
26.10.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.5.0.10 FixList