BCI Error

Bala · Post by **Bala** » Mon Oct 14, 2002 9:30 pm

Pls help if anyone knows:
1. In UNIX,tried to connect DB2 with BCI function(SQLConnect).
2. Failed with error message:
"SQLSTAT=IM003,CODE=80,[DataStage][SQL Client][ODBC]Specifed driver
could not be loaded"
3. What is wrong?
4. Pls advice the entries of uvodbc.config

regards,
Bala

ray.wurlod · Post by **ray.wurlod** » Tue Oct 15, 2002 4:49 pm

There's not enough information in the question to provide "the" answer.
First thing we need to know is what platform you are on (UNIX or Windows), because the answer will be different. For example, if you're on UNIX, you may not have relinked /.uvlibs to point to the location where the drivers and the odbc.ini file reside.
Second thing we need to know is whether you're using the Merant ODBC drivers that ship with DataStage, or a different ODBC driver. The Merant drivers have licensing issues when you try to use BCI functions - that is, they are specifically licensed for DataStage to use.
The uvodbc.config file should not require very much at all for a DB2 data source; simply the name of the data source and DBMSTYPE = ODBC.

Bala · Post by **Bala** » Tue Oct 22, 2002 11:41 pm

Hi Ray,
Thanks for your reply.
We are having DS 5.2 on UNIX(Sun Solaris5.

.
We have reliked /.dslibs already and not using Merant ODBC drivers.
Before relink, we got the following error:
==============================================
CleanCsmartTable1..JobControl (BCI DB2ExecSqlUM): SQL State = IM002,
DBMS
error code = 0
[DataStage][SQL Client][ODBC][MERANT][ODBC lib] Data source name not
found
and no default driver specified
==============================================
After relink, it gives the follwoing error:
===============================================
"SQLSTAT=IM003,CODE=80,[DataStage][SQL Client][ODBC]Specifed driver
could not be loaded"
===============================================
Please advice.

Thanks.

ray.wurlod · Post by **ray.wurlod** » Wed Oct 23, 2002 6:31 pm

First guess is that you haven't edited .odbc.ini to include the data source name to which you're trying to connect.
Once you've done this, the data source name also needs to be recorded in uvodbc.config in the project; the easiest way to do this is to begin to import a table definition from that data source. The entry in uvodbc.config needs, as a minimum, the data source name surrounded by angle brackets followed by a line specifying that it is an ODBC data source. For example (spaces around "=" are mandatory):

<YIBBADA>
DBMSTYPE = ODBC

Bala · Post by **Bala** » Wed Oct 23, 2002 9:07 pm

Thanks for immediate reply.

We had the entries in .odbc.ini file as you have mentioned.
We understand that this type of odbc is "Wire protocol", which was not working. The following is the old entry in .odbc.ini
********
[DB2 Wire Protocol]
Driver=/prod/applc/ds_appls/Ascential/DataStage/DSEngine/../branded_odbc/lib/VMdb217.so
Description=DataDirect 4.00 DB2 Wire Protocol Driver
....
*******
So, We are tring "Non-wire protocol", in which we are adviced to make driver specification entries in the dsenv file.
*******
ODBCINI=$dshome/.odbc.ini; export ODBCINI
DB2DIR=/opt/IBMdb2/V7.1; export DB2DIR
*******
Along with the respective entries we have added the path in LD_LIBRARY_PATH

Still, we are unable to get the connection.
So, please advice if you have any lights.

Thanks.

ray.wurlod · Post by **ray.wurlod** » Fri Oct 25, 2002 5:34 pm

"Driver could not be loaded" means exactly what it says.
You now need to use the test utilities in the branded_odbc directory, to determine whether there's a problem with the library or with the ODBC driver manager. I believe Ascential support has a paper on how to do this, which will save me a lot of typing. Please contact them.