SourceForge has been redesigned. Learn more.
Close

#572 DB2:z/OS v8 bad column names, 2.6.1

2.6.1
closed-invalid
None
5
2007-10-30
2007-10-26
Anonymous
No

I don't recall the issue with 2.5.x, but with a clean install of 2.6.1, the Tables -> Columns display shows only numbers (4, 6, 18...) in the heading, which I guess are the keys into syscolumns, rather than the column names. LUW databases are OK.

Using either Type 2 or Type 4 driver.

Discussion

  • Nobody/Anonymous

    Logged In: NO

    welllll. on a client machine with the 20071001 snapshot, and the v7 client driver Type 2, column names are displayed correctly.

     
  • Rob Manning

    Rob Manning - 2007-10-26

    Logged In: YES
    user_id=1287991
    Originator: NO

    We use JDBC API to get the columns for a table. I'm guessing there is a bug in the driver. Do you have the latest fixpak installed?

    Rob

     
  • Nobody/Anonymous

    Logged In: NO

    this is the content of bldlevel in db2java.zip

    /wsdb/db2_v82fps/n061108 (the date on the class files 11/08/06 and 11/09/06)

    the db2jcc.jar is from 11/03/06

    the install is 8.2.14 ESE/xp.

    I browsed the APARs (bug list) at DB2, but didn't see anything apropos.

    reverting to 2.5.1, same. I don't have the chance to go to 8.2.15, since that would require
    re-binding the utilities at each z/OS subsystem, and that's not my call.

     
  • Nobody/Anonymous

    Logged In: NO

    there's a bind, db2schema.bnd, which must have gotten blown away at some point. it's said that this will make the SQL* catalog tables available.

    sorry about the confusion.

     
  • Rob Manning

    Rob Manning - 2007-10-30

    Logged In: YES
    user_id=1287991
    Originator: NO

    No problem - glad to hear the problem is solved.

    ROb

     
  • Rob Manning

    Rob Manning - 2007-10-30
    • milestone: --> 2.6.1
    • assigned_to: nobody --> manningr
    • status: open --> closed-invalid
     

Log in to post a comment.