Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

connecting to a DB2 database using ODBC

56 views
Skip to first unread message

Luc Vermincksel

unread,
Nov 2, 1998, 3:00:00 AM11/2/98
to
We have made a PowerBuilder application which uses a Sybase SQL Anywhere
database.
Now this application has to converted to DB2 Universal database version 5.0
for Windows NT version 5.
But I have problems with connecting to the DB2 database from within
PowerBuilder.

On my PC I have installed the 32-bit version of PowerBuilder 6.5 (typical
installation) and then I installed the DB2 client application enabler.
Then I created an ODBC profile from within PowerBuilder using the IBM DB2
ODBC driver.
After I supplied all connection parameters I clicked on the last OK button
and PB was exited without any error message. When I restart PowerBuilder IM
noticed that the ODBC-profile was created but there was no DB-profile
created in PowerBuilder.
With MS Query I can connect to the same database (using the same
ODBC-profile) without any problem.


Then I have tried the same thing using the PB Intersolv OEM 3.01 32-bit DB2
ODBC-driver. To install this driver I had to re-run the setup of PB6.5 and
choose Custom installation.
From within PowerBuilder I could add an ODBC and a DB-profile without any
problem but when I tried to connect to the database I got the error message
"PB catalog tables could not be created and are not available for use".

And in the Database painter I got the error message [Intersolv][ODBC DB2
driver][DB2] SQL0805N package "QE.QECSV1" was not found. SQLstate=S1002 and
I saw no tables.

When I tried to connect using MS Query I got the same error message.

Can anyone help me with connecting to a DB2 database with one of these 2
ODBC drivers ?
Are there any differences between these 2 drivers regarding use in
conjunction with PowerBuilder, performance, capabilities, etc ?

Thanks,
Luc Vermincksel
TeSSA n.v.
Belgium

Jim O'Neil [Sybase]

unread,
Nov 2, 1998, 3:00:00 AM11/2/98
to
If you are using CAE version 5, there is a problem with the ODBC Administrator
abruptly causing a GPF or PowerBuilder to quit - this happens as well when you
run the ODBC Administrator from the Control Panel. Since your ODBC datasource
is defined, you can create a PowerBuilder/InfoMaker profile from that
datasource. Just select ODBC as your PowerBUilder interface and you will be
prompted for the rest of the information.

The Intersolv ODBC driver requires additional bind files to be bound to your
database. It sits on top of CAE, which has its own bind files. The message
referring to a package not being found indicates that the files for the
Intersolv ODBC driver have not been bound - the installation instructions for
that driver will tell you what to do.

Finally, the fact that you got the "Catalog Tables could not be created..."
message means you were connected. It just means that PowerBuilder failed to
create the repository or the five extended attribute tables (PBCATCOL, PBCATTBL,
etc.) that are available for storing extended attribute information about your
tables. There is a faxline on connecting to DB2 using CAE which may be helpful
for you in working through these issues. You can find it at the Technical
Documents link of http://support.sybase.com.

Jim O'Neil
Sybase Technical Support
jon...@sybase.com

0 new messages