BCI

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
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

"BCI" stands for "BASIC SQL Client Interface",
which is the set of functions DataStage uses to connect to, send SQL
statements to and retrieve results from, ODBC and UV data sources.
The BCI functions mimic functions described in the ODBC API.

The DataStage component you were using was DSR.MetaGeta (which
obtains metadata from the data source), and it was attempting to
retrieve a list of table names from Red Brick Warehouse (GET.TABLES).
You were attempting to connect to Red Brick Warehouse via a DSN
called MxRBWarehouse, logging in as the user SYSTEM (case is
irrelevant).

There is usually an extra line or two with this error message,
providing an SQL State, a DBMS Code, and text of the error message
returned by the ODBC driver (in this case you are using the Red Brick
ODBC driver). Sometimes you need to reset the job before the
remainder of this message is copied from the &PH& directory into the
job log. If it's happening during import of table definition, check
that you are using the correct password for the user SYSTEM.

There are several manuals, but without the error code it is difficult
to direct you to the appropriate one. Sometimes the relevant manual
is not a DataStage manual; for example the InterCall manual is to be
found on an IBM web site (this describes error codes of the forms
31xxx and 81xxx).

Get back to us with the full error, and we can supply more detailed
analysis.
morneh
Participant
Posts: 17
Joined: Wed Jan 28, 2004 8:09 am
Contact:

Post by morneh »

I seem to have inherited this problem. I've been able to get Redbrick and Datastage talking to each other. My headache comes in with Informix.

We're running Sun Solaris 9, Informix 7.31 fd3, SQL Server 2000 and DataStage 7.

The error I'm receiving is:
DSR.MetaGeta(GET.TABLES)(SQLConnect('MedClear','mis')): BCI Error:
SQLSTATE=IM003,CODE=80,[DataStage][SQL Client][ODBC]Specified driver could not be loaded

The other problem is with a SQL Server connection. It looks like it connects and then crashes with:
DSR.MetaGeta(GET.TABLES)(SQLConnect('MxHealthSQL','mis')): BCI Error:
SQLSTATE=08001,CODE=11,[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver]nt unabl
SQLSTATE=01000,CODE=146,[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver][libssclient19]ConnectionOpen (connect()).

Any suggestions or help with either/or these problems will be greatly appreciated.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This is not, strictly speaking, a BCI problem, though it was discovered when your job has attempted to use a BCI function (behind an ODBC stage, for example).
The problem is that the DataDirect driver indicated by your data source name could not be loaded by the ODBC driver manager. This may be because your shared library path environment variable (LD_LIBRARY_PATH) does not include its directory, or that you've upgraded at some time and not relinked the libraries. Or one of a number of other reasons. Search the archive for "driver manager" as well as the keywords from the error messages that were generated.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply