Error with Microsoft ODBC for Oracle. BCI Error.

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
pavlicic
Participant
Posts: 7
Joined: Thu Jul 14, 2005 5:00 am

Error with Microsoft ODBC for Oracle. BCI Error.

Post by pavlicic »

Hi all,

I've got this error with a Microsoft ODBC for Oracle in a job:

DSR.MetaGeta(GET.DSNINFO)(SQLConnect('prueba','siacrh')): BCI Error:
SQLSTATE=NA000,CODE=0,[DataStage][SQL Client][ODBC][Microsoft][ODBC driver for Oracle][Oracle]

Anyone know what's the problem? With Oracle ODBC works fine.

Thanks in advance
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

GET.DSNINFO should help a bit - it is trying to get the DSN and something is going wrong. Have you declared this as a SYSTEM dsn?
pavlicic
Participant
Posts: 7
Joined: Thu Jul 14, 2005 5:00 am

Post by pavlicic »

ArndW wrote:GET.DSNINFO should help a bit - it is trying to get the DSN and something is going wrong. Have you declared this as a SYSTEM dsn? ...
yes, it's a system dsn
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Can you access the DB using that DSN through MSQuery?
pavlicic
Participant
Posts: 7
Joined: Thu Jul 14, 2005 5:00 am

Post by pavlicic »

How can i use MSQuery? I don't know this tool...
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I comes as part of the extras for Microsoft Office and also with access and I think it might be available as a separate download from Microsoft as well. It is a simple tool and we've used it for years to check base connectivity for ODBC. If it doesn't work in MSQUERY then don't bother trying to figure out why it isn't working with DataStage.
Chuah
Participant
Posts: 46
Joined: Thu May 18, 2006 9:13 pm
Location: Melbourne

Post by Chuah »

Why not use the Oracle ODBC if that works ? You might want to try to reinstall your MS ODBC drivers.
Post Reply