JR40758: SQL0901N ERROR MESSAGE "COLUMN NUMBER OUT OF RANGE" RETURNED WHEN QUERYING DATA FROM AN JDBC NICKNAME.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The error is due to a limitation of current JDBC wrapper. When
  the length of remote table column names are more than 30
  letters, the local column name will be truncated. So if there
  are more than two column name in such condition and the first 30
  letters are all the same, the JDBC nickname will only create one
  column with truncated column name for these remote column and
  eliminate some columns.
  
  Reproducing scripts:
  
  a. Remote data source table (4 columns):
  CREATE TABLE  "<remote_schema>"."<remote_table_name>" (
    "This_column_name_length_is_more_than_30_letters1"
  varchar(255),
    "This_column_name_length_is_more_than_30_letters2"
  varchar(255),
    "This_column_name_length_is_more_than_30_letters3"
  varchar(255),
  J "This_column_name_length_is_more_than_30_letters4"
  varchar(255)
  )
  
  b. Local Nickname (only 1 column):
  db2=> describe table "<local_schema>"."<local_nickname>"
  THIS_COLUMN_NAME_LENGTH_IS_MOR    SYSIBM    VARCHAR
  255     0 Yes
  
  c. Test result:
  db2 => select * from "<local_schema>"."<local_nickname>"
  SQL0901N  The SQL statement failed because of a non-severe
  system error.
  Subsequent SQL statements can be processed.  (Reason "column
  number out of range".)  SQLSTATE=58004
  

Local fix

• Choose either of the following ways to get rid of the error:
  1. Add or set the server option OLD_NAME_GEN to 'Y'
  2. Make sure the first 30 letters of every remote column name
  are different or less than 30 letters.
  

Problem summary

• User affected:
    Users of the JDBC wrapper in InfoSphere Federation Server
  Problem description and summay:
    See error description
  

Problem conclusion

• Problem was fistly fixed in Version 9.7, FixPak 6. 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:

Fix information

• Fixed component name

  FEDSRVR JDBC WR

• Fixed component ID

  5724N9714

Applicable component levels

• R970 PSY

     UP