DB2 v8fp5 sqlstate 01517

Document directory

• APAR number
• Reported component name
• Reported component ID
• Reported release
• Status
• PE
• HiPer
• Special attention
• Submitted date
• Closed date
• Last modified Date
• APAR is sysrouted from one or more of the following:
• APAR is sysrouted to one or more of the following:
• Fixed component name
• Fixed component ID
• R810 pSN
• R820 pSN
• R910 pSN

Problem Summary

• USERS AFFECTED:AllPROBLEM DESCRIPTION:Inserting large amount of multi-byte character data into aCLOB column can result in data corruption. The result data inthe CLOB column in such case would contain characters 0xFC.PROBLEM SUMMARY:The problem can occur when working with large lob data (>128kB).The lob data is processed in chunks as they are passed by theclient.  When an internal lob processing buffer containg thedata chunks is full and there is still data to process, the lobdata is translated by codepage conversion functions, moved intoa temporary table and next chunk of data is processed.  In thisparticular defect situation the buffer full condition occurs inthe middle of the multi-byte character.  The last byte in thebuffer is not valid multi-byte character so it suppose to beremembered and used as the first character of the followingchunk.  Due to a defect this dangling character is dropped,causing all the next multi-byte characters in the followingchunk to be byte shifted.Good data: 006A0061  00760061  002E006C  0061006E    .j.a.v.a...l.a.n 0067002E  00530074  00720069  006E0067    .g...S.t.r.i.n.g 0022003E  003C0021  005B0043  00440041    .".>.<.!.[.C.D.ABad data (byte shifted): 74007200  69006E00  67002200  3E003C00    t.r.i.n.g.".>.<. 21005B00  43004400  41005400  41005B00    !.[.C.D.A.T.A.[. 63006F00  6D002E00  61007000  74007200    c.o.m...a.p.t.r.Since these byte shifted characters may be invalid (according tothe used codepage), the the codepage conversion functions canthrow a warning like this:  SQLSTATE 01517:  A character that could not be converted was  replaced with a substitute character.A db2 trace of the problem would show errors SQLO_DBCSTRUNCfollowed by SQLO_BUFFSMALL:| | | sqlnlscpcv data[probe 13]| | | | sqlnlsCodePageConvert entry| | | | | sqlnlscpcv_noUTF entry| | | | | sqlnlscpcv_noUTF data[probe 1]| | | | | | sqlnls_valtab entry| | | | | | sqlnls_valtab exit| | | | | sqlnlscpcv_noUTF exit[rc=0x870F00C0=SQLO_DBCSTRUNC]| | | | sqlnlsCodePageConvert data[probe 170]| | | | sqlnlsCodePageConvert exit[rc=0x870F00C0=SQLO_DBCSTRUNC]| | | sqlnlscpcv exit[rc=0x870F00C0=SQLO_DBCSTRUNC]| | sqlnlscpcv exit[rc=0x870F00BC=SQLO_BUFFSMALL]| sqlocpcv exit[rc=0x870F00BC=SQLO_BUFFSMALL]sqlricpcv exit[rc=0x870F00BC=SQLO_BUFFSMALL]sqlri_write_lob_field entry

Problem conclusion

• First fixed in DB2 UDB Version 8, FixPak 5 (s040212).

Temporary fix

Comments

APAR Information

• APAR number

  Jr25158

• Reported component name

  DB2 udb wse win

• Reported component ID

  5765f3501

• Reported release

  820

• Status

  Closed per

• PE

  Nope

• HiPer

  Nohiper

• Special attention

  Nospecatt

• Submitted date

  2006-10-30

• Closed date

  2006-10-30

• Last modified Date

  2006-10-30

• APAR is sysrouted from one or more of the following:
• APAR is sysrouted to one or more of the following:

Fix Information

• Fixed component name

  DB2 udb wse win

• Fixed component ID

  5765f3501

Applicable component levels

• R810 pSN

  Up

• R820 pSN

  Up

• R910 pSN

  Up