Trying to Connect to Universe database - FAILED

joycerecacho · Post by **joycerecacho** » Tue Feb 19, 2013 9:28 am

Hi everybody.

I am trying to execute a Query at theUniverse Database but the following message returns:

ReportJobCategory..DS_JOBS (OpenPath failed for - /opt/IBM/InformationServer/Server/branded_odbc):
ReportJobCategory..DS_JOBS.lnk_DS_JOBS: DSD.BCIOpenR call to function OCONV failed.

When the query is executed on Administrator (Command), the result is ok, but through ODBC stage this error is shown.

Query:
SELECT JOBNO, CATEGORY, NAME FROM DS_JOBS WHERE TRIM(JOBNO) <> '' AND TRIM(CATEGORY) <> '' ORDER BY CATEGORY, NAME, JOBNO;

What can it be?

Thanks, guys!!

Best Regards.

ray.wurlod · Post by **ray.wurlod** » Tue Feb 19, 2013 4:16 pm

How are you describing the "UniVerse" database in .odbc.ini and uvodbc.config ?

chulett · Post by **chulett** » Tue Feb 19, 2013 5:03 pm

Have you considered using a Server job with the UV stage?

joycerecacho · Post by **joycerecacho** » Tue Feb 19, 2013 8:14 pm

chulett wrote:Have you considered using a Server job with the UV stage? ...

Hi my friend.
Let me correct something.
Actually I am punctually working in a project wich they use server jobs. I forgot to mention this important point.

The thing is:
We have tested and both ODBC stage and universe stage return this error.
When we run a job that uses an Oracle stage, it runs ok. No warnings and right result.

Do you know what it can be?
I am talking about version 8.5 Enterprise Edition, but a server job.

Thanks anyway!!

chulett · Post by **chulett** » Tue Feb 19, 2013 9:05 pm

Well... then we're not only in the wrong forum but your job type in your initial post is wrong. Let me fix both of those.

chulett · Post by **chulett** » Tue Feb 19, 2013 9:07 pm

The UV stage wouldn't return that error as far as I know. What happens if you use the UV stage as a source and select "localuv" as the data source? I don't recall if you can select that from a list or if you have to type it in but it should work just fine.

joycerecacho · Post by **joycerecacho** » Tue Feb 19, 2013 9:39 pm

Chulett,
That's exactly what I have done.
Actually it is a very simple job where there is a universe stage as the source and its result goes to a sequential file.
The query is that one I mentioned above.
I've already changed the uvodbc.config letting that one wich was created during the instalation process (the default one) and the problem still happens.

I don't know which configuration could solve this.
Thank uuuu

ray.wurlod · Post by **ray.wurlod** » Tue Feb 19, 2013 11:18 pm

Make sure that this entry appears in the project's uvodbc.config file.

Code: Select all

<localuv>
DBMSTYPE = UNIVERSE

In your UniVerse stage, specify localuv as the DSN.

joycerecacho · Post by **joycerecacho** » Wed Feb 20, 2013 6:45 am

Hi my friend.
This command exists at the uvodbc.config and the DSN in the Universe stage is exactly like you mentioned.

Remembering that this error occurrs also with ODBC stages.
When it is an Oracle stage, the data returns ok.

Thanks guys!

joycerecacho · Post by **joycerecacho** » Wed Feb 20, 2013 8:45 am

I found the problem guys!
The thing is that the file .odbc.ini was in a Windows format, with Windows 'end of lines': char 13, char 10.
When we changed it to Unix format, the job worked!!!

Tks guys for your help!

chulett · Post by **chulett** » Wed Feb 20, 2013 8:50 am

So... how in the heck did you end up with DOS delimiters in your file? Are you transferring them to a PC for editing and then transferring them back rather than editing them directly on the UNIX server? If so, you needs to learn yourself some vi.

rameshrr3 · Post by **rameshrr3** » Thu Mar 14, 2013 2:51 pm

You should have seen them thro' vi . The additional DOS character ( Carriage Return) will usually show up as ^M in vi. You may not be able to see it when you do "cat filename".

My favorite utility for control characters remains unix's "od"
od -c and od -x to be specific