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

-901: INVALID SVAR LEN, PRODUCING FODC_APPERR

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
After replacing PD corruption with the db2cat tool, the same SQL
statement continues to produce -901 messages with "Invalid svar
len" for graphic or vargraphic columns.  As a result FODC_AppErr
folders are created.

db2cat takes the codepage and value from the catalog column
length and longlength and regenerates to cd->col_len and
cd->blob_len.  In this case the table Composite codepage and the
codepage for the vargraph column were set to 0.  Codepage 0 for
varchar/vargraphic is incorrect.  DB2 therefore needs to
retrieve the codepage from DBCSCODEPG for graphic data type
instead of CODEPAGE catalog.

In short, we need to fix db2cat's regenerate option.  The
col_len and blob_len should be
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to fix pack                                          *
****************************************************************
Local Fix:
Drop and recreate the table.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT17042 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.08.2017
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)