Error occurred during link open processing

mchivuku · Post by **mchivuku** » Tue Jan 13, 2009 1:04 am

Hi ,

I have many posts on similar topic ,but nothing worked for me ,as I have set all the configuration parameters right.

/opt/IBM/InformationServer/Server/DSEngine/.odbc.ini

[ODBC Data Sources]

ARTSTDB=DataDirect DB2 Wire Protocol Driver for ARIW3

[ARTSTDB]
Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb223.so
Description=DataDirect DB2 Wire Protocol Driver for ARIW3
AddStringToCreateTable=
AlternateID=
Database=ARTSTDB
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=9.149.68.96
IsolationLevel=CURSOR_STABILITY
LogonID=dsadm
Password=ds8ariw3
Package=DB2 package name
PackageOwner=db2inst1
TcpPort=50001
WithHold=1

/opt/IBM/InformationServer/Server/DSEngine/uvodbc.config

<localuv>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 127.0.0.1
<ARTSTDB>
DBMSTYPE =

Database 1 entry:

Database alias = ARTSTDB
Database name = ARTSTDB
Node name = ARIDD000
Database release level = c.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =

db2 => connect to artstdb user dsadm
Enter current password for dsadm:

Database Connection Information

Database server = DB2/LINUXZ64 9.5.2
SQL authorization ID = DSADM
Local database alias = ARTSTDB

My job looks like ,

DB2 Stage ----> Tfm ----> Sequential File

Am getting the following error while trying to view data,

Cfrt03_Openbillap..DB2_UDB_API_0: Error occurred during link open processing.
Cfrt03_Openbillap..DB2_UDB_API_0.DSLink1: DSP.Open GCI $DSP.Open error -100.

But if the job is executed it works fine,the sequential file is loaded with all the 154 rows successfully.

I am able to import metadata.

Kindly help

chulett · Post by **chulett** » Tue Jan 13, 2009 7:07 am

So... the job runs fine but 'view data' does not work? Does the DB2 stage optionally use ODBC or something? Unsure why you'd post that data source otherwise.

Mike · Post by **Mike** » Tue Jan 13, 2009 8:18 am

Right. The ODBC information is completely irrelevant since the DB2 stage uses native connectivity. A -100 usually means no data found. Is there a job parameter that is evaluating differently between your "view data" and when the job actually runs?

Mike

chulett · Post by **chulett** » Tue Jan 13, 2009 9:10 am

Ah... using environment variables, perhaps?