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 IC77396 Status: Closed

DB2LOOK -E FAILS WITH SQL0304, WHEN SECPOLICYID GETS LARGER 32766

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2look -d <dbname> -e -o ddl.sql does not extract all objects 
of the database in question and fails with the following 
message: 
 
SQL0304N  A value cannot be assigned to a host variable because 
the value is not within the range of the host variable's data 
type. SQLSTATE=22003 
 
This happens, when SECPOLICYID in SYSCAT.SECURITYPOLICIES 
contains values larger than 32766.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9.                       * 
****************************************************************
Local Fix:
Drop all the SECURITY POLICYs with a SECPOLICYID larger than 
32766.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5 Fix Pack 9.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.07.2011
14.03.2012
14.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList