JR31478: CREATE NICKNAME ERROR WHEN CREATING NICKNAME BY USING MICROSOFT ODBC DRIVER WITHOUT VALID CARD AND NPAGES VALUE

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• You may create nickname failed when the remote table has an
  index on WINDOWS. This is because the wrapper gets invalid
  statistics data from the remote data source for the table.
  In the db2diag.log:
  INSTANCE: iidev5 NODE : 000   DB   : TEST
  APPHDL : 0-187        APPID: *LOCAL.iidev5.081211092014
  AUTHID : IIDEV5
  EDUID : 7969      EDUNAME: db2agent (TEST)
  FUNCTION: DB2 UDB, catalog services,
  sqlrlCatalogScan::checkLenValid, probe:10
  DATA #1 : String, 11 bytes
  PACKED_DESC
  DATA #2 : signed integer, 4 bytes
  9656
  DATA #3 : String, 33 bytes
  sqlrz_pd_verify failed with rc -4
  

Local fix

Problem summary

• Users affected:
    Users of the ODBC wrapper in InfoSphere Federation Server
  Problem description and summary:
    See error description
  

Problem conclusion

• Problem was first fixed in Version 9.1, FixPak 7 (s090308). This
  fix should be applied on the federation server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR31585

Fix information

• Fixed component name

  ODBC WRAPPER

• Fixed component ID

  5724N9707

Applicable component levels

• R910 PSN

     UP

• R911 PSN

     UP