home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84354 Status: Closed

DB2LOOK -D <DBNAME> -F -M -L -A -E -O DB2LOOK.TXT RETURNS SQL0811N
TRYING TO SELECT ALTERNATIVE DATA TYPES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If the database contains alternative data types the db2look -d 
<dbname> -f -m -l -a -e -o db2look.txt will fail with SQL0811N 
error. 
 
No errors appear in the db2diag.log and db2 does not crash.  The 
DDL cannot be extracted. 
 
There is no known work-around for this issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2LOOK users with alternative data types.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW version 10fp1                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
03.12.2012
03.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList