Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Error message when you use Microsoft ODBC Driver for DB2 to access an IBM DB2 table and when the IBM DB2 table name is longer than 18 characters: "Invalid string or buffer length"

FIX: Error message when you use Microsoft ODBC Driver for DB2 to access an IBM DB2 table and when the IBM DB2 table name is longer than 18 characters: "Invalid string or buffer length"

Symptoms

When you use Microsoft ODBC Driver for DB2 to access an IBM DB2 table on an IBM DB2 Universal Database (UDB) for z/OS system, you receive the following error message:
[S1090] [Microsoft][ODBC DB2 Driver] Invalid string or buffer length.
This problem occurs when the IBM DB2 table name is longer than 18 characters.

Notes
  • The exact format of this error message may vary depending on the application that uses ODBC Driver for DB2.
  • IBM DB2 UDB for z/OS was previously known as IBM DB2/MVS.
  • This issue also occurs in Microsoft Host Integration Server 2006.

↑ Back to the top

Cause

ODBC Driver for DB2 is designed to support a maximum table name length of 18 characters when ODBC Driver for DB2 connects to an IBM DB2 UDB for z/OS system. This length corresponds to the maximum table name length that is supported by IBM DB2 UDB for z/OS versions that are earlier than IBM DB2 UDB for z/OS version 8.

↑ Back to the top

Resolution

Host Integration Server 2006

To resolve this problem, obtain the latest service pack for Host Integration Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
979497 How to obtain the latest Host Integration Server 2006 service pack

Host Integration Server 2004

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatformSP requirement
Db2oledb.dll6.0.2048.0488,96003-Nov-200617:31x86SP1
Db2oledb.hNot Applicable24,57903-Nov-200617:36Not ApplicableSP1
Ddmstr.dll6.0.2048.044,03203-Nov-200617:31x86SP1
Drdaresync.exe6.0.2048.0337,40803-Nov-200617:32x86SP1
Microsoft.hostintegration.dataaccesslibrary.dll6.0.2048.086,01603-Nov-200617:31x86SP1
Microsoft.hostintegration.dataaccesstool.exe6.0.2048.02,703,36003-Nov-200617:32x86SP1
Microsoft.hostintegration.msdb2client.dll6.0.2048.0114,68803-Nov-200617:31x86SP1
Mseidb2c.dll6.0.2048.071,68003-Nov-200617:31x86SP1
Mseidb2d.dll6.0.2048.0435,20003-Nov-200617:31x86SP1
Mseidrda.dll6.0.2048.0695,80803-Nov-200617:32x86SP1
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

After you apply this hotfix, ODBC Driver for DB2 can access IBM DB2 tables that have table names that are up to 128 characters long. This length is the maximum unqualified table name length that is supported by IBM DB2 UDB for z/OS version 8.

For more information about a problem that occurs when you use ODBC Driver for DB2 to access an IBM DB2 table that has a column name that is 30 characters long, click the following article number to view the article in the Microsoft Knowledge Base:

924453 FIX: Error message when you use Microsoft ODBC Driver for DB2 to access an IBM DB2 table that has a column name that is 30 characters long: "General error"

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kb, kbpubtypekc, kbqfe, kbhotfixserver, kbentirenet, kbbug, kbfix, kbautohotfix

↑ Back to the top

Article Info
Article ID : 924452
Revision : 2
Created on : 7/20/2020
Published on : 7/20/2020
Exists online : False
Views : 101