Hi all,

In DB2 9.0 version, I executed the below query and found some junk values returned,

The value returned is : 4352454154452056494557205650524F4A2020202041532053 454C45435420414C4C2050524F4A4E4F2C2050524F4A4E414D 452C20444550544E4F2C2052455350454D502C205052535441 46462C2050525354444154452C205052454E444154452C204D 414A50524F4A2046524F4D2050524F4A

But the view 'MYVIEW' , exists in the database.

Similarly the names, and the constraints of the defined table constraints is also not returned properly with the below queries,
Does the system tables to fetch the above metadata changed in DB2 9.0 ?

thanks,
Sn

This looks to me as if you have some sort of issue with character encodings.

With which application do you issue your queries?
How was your database created?

p.s: Things work quite nicely for me on V9.

Indeed.
Interpreting the output as hex ASCII (or UNICODE) encoding, that output would read:
CREATE VIEW VPROJ AS SELECT ALL PROJNO, PROJNAME, DEPTNO, RESPEMP, PRSTAFF, PRSTDATE, PRENDATE, MAJPROJ FROM PROJ

Dear Stolze and Peter,

Thanks for the reply. I dint have any problem in retrieving the TEXT of the other objects like Functions, Stored Procedures from the SYSCAT.ROUTINE table. Do you mean that the fetching from SYSCAT.VIEWS alone need this UNICODE wrapper.


BTW, I connect to my DB2 using JDBC from a Java application.

Regards,
Sn

I think that your application is not interpreting the string as string but rather as binary data.