Re: problem wiht db connection

Hallo all,

I just solved the problem. The problem is on the db site, with the db
engine. It has nothing to do with the SQuirreL!  A good description
you can find at:

http://www-1.ibm.com/support/docview.wss?rs=71&dc=D600&uid=swg21215626

In sort. The db after the fixpac 8.1 FixPak 10 (also known as Version
8.2 FixPak 3), can encounter an SQL0443N error if invoking a DB2 Call
Level Interface (CLI) catalog function (such as SQLTables(),
SQLColumns(), or SQLStatistics()).

The solution:

db2 terminate
db2 connect to <database-name>
db2 bind <path>/db2schema.bnd blocking all grant public sqlerror continue
db2 terminate

Thanks all, have a nice day
Radoslaw

2007/7/17, Robert Manning <robert.m.manning@xxxxxxxxx>:
> Hello,
>
> Looks like you have 8.1 fixpak 11 installed.  You might try to get
> fixpak 14 (that's what I updated to recently).  There is some newer
> support for IBM's driver in the latest snapshot for getting more
> detailed error messages from the exceptions that DB2 driver throws.
> You may want to try that, and report back with a more detailed error
> message.  The snapshot can be found here:
>
> http://sourceforge.net/project/showfiles.php?group_id=28383&package_id=158128&release_id=523220
>
> The symptom appears to be that whenever SQuirreL asks the driver for
> metadata about tables, schemas, etc. the driver throws an Exception.
> I'm guessing - perhaps the system catalogs aren't installed/configured
> properly - or you don't have access to them?
>
> Rob

-- 
ITIL,RHCE,CCNA,Linux enthusiast.
M.Sc. Radoslaw Tomaszewski

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/