Cannot view data from ODBC stage.

gordonxiao · Post by **gordonxiao** » Fri May 13, 2005 4:02 am

Dear all,

We are using DataStage 7.5 Server Edition. We can import ODBC table definition into DataStage.

However, when we try to click the View Data button from the ODBC stage, we get the following error message:

DSBrowser..ODBC_0.DSLink2: DSD.BCIOpenR call to OCONV failed.

Please help.

Thanks,
Gordon

ArndW · Post by **ArndW** » Fri May 13, 2005 5:15 am

I don't know exactly what is causing it, but the reference to a call to OCONV might point to some data type conversion. What data types are you using in your columns, and can you remove the columns one-by-one until the error goes away in order to narrow down the problem?

chulett · Post by **chulett** » Fri May 13, 2005 6:31 am

What makes you think you can use OCONV in your SQL statements?

Sure sounds from the error that that is what you are trying to do, and I would guess via custom sql. You'll have to wait until the data gets into your job and then, in a transformer, apply the OCONV (and any other DataStage specific) logic.

Can you post it? Your SQL, that is...

ray.wurlod · Post by **ray.wurlod** » Fri May 13, 2005 6:35 pm

I think that the problem may, indeed, be a bug. OCONV could be being called by DSD.BCIOpenR (which opens the connection for reading). With the ODBC stage, if a data element is set to Date or Time, then an "implicit" conversion is performed - it's most likely that this uses Oconv (or Iconv, depending on direction).

Try reverting the data element to Default, see if that makes any difference. If it does, report the bug through your support provider, with a reproducible case, and let us know the outcome of your test.

chulett · Post by **chulett** » Fri May 13, 2005 8:04 pm

ray.wurlod wrote:I think that the problem may, indeed, be a bug. OCONV could be being called by DSD.BCIOpenR (which opens the connection for reading). With the ODBC stage, if a data element is set to Date or Time, then an "implicit" conversion is performed - it's most likely that this uses Oconv (or Iconv, depending on direction).

Really??

Apologies then if that's the case, I assumed it was because of a derivation specifically added to the stage.

gordonxiao · Post by **gordonxiao** » Tue May 17, 2005 7:30 pm

ray.wurlod wrote:I think that the problem may, indeed, be a bug. OCONV could be being called by DSD.BCIOpenR (which opens the connection for reading). With the ODBC stage, if a data element is set to Date or Time, then an "implicit" conversion is performed - it's most likely that this uses Oconv (or Iconv, depending on direction).

Try reverting the data element to Default, see if that makes any difference. If it does, report the bug through your support provider, with a reproducible case, and let us know the outcome of your test.

Thanks, Roy! I've also heard that there is a bug relating to ODBC manipulation in DS 7.5 (for AIX). In fact, we couldn't even import table definition from ODBC source. Others told us that this issue could be fixed if we replace the DS 7.5 branded_odbc directory with DS 7.1/7.0 branded_odbc directory. So we did. However, we encountered the new problem as I described in my last post.

Because this issue happened in the environment of our customer's, I will perform some test according to your instructions then let you know the result.

Thanks all again!

Gordon