Error connecting to DB2 Sample database

[MrBonk]

I've just installed DB2 Personal Edition V8 and managed to get the sample
database created etc. However, when I attempt to connect to it in the CF
Administration data sources area, I get the following error:

Connection verification failed for data source: db2_sample
[]java.sql.SQLException: [Macromedia][DB2 JDBC Driver][DB2]PROGRAM NAME
DEFAULT.DDTEKA 0X4A44424334444232 NOT FOUND IN PLAN null
The root cause was that: java.sql.SQLException: [Macromedia][DB2 JDBC
Driver][DB2]PROGRAM NAME DEFAULT.DDTEKA 0X4A44424334444232 NOT FOUND IN PLAN
null

Can someone possibly shed some light on what's going on there?

[Brian Hogue]

Do you have the DB2 ODBC or JDBC installed? If yes, then I doubt that the
sample database uses Plan NULL. You probably need to use the DB2 software to
tell you what that plan name is. hth

-brian

"MrBonk" <webforumsuser@macromedia.com> wrote in message
news:dkmnq4$b3q$1@forums.macromedia.com...

> I've just installed DB2 Personal Edition V8 and managed to get the sample
> database created etc. However, when I attempt to connect to it in the CF
> Administration data sources area, I get the following error:
>
> Connection verification failed for data source: db2_sample
> []java.sql.SQLException: [Macromedia][DB2 JDBC Driver][DB2]PROGRAM NAME
> DEFAULT.DDTEKA 0X4A44424334444232 NOT FOUND IN PLAN null
> The root cause was that: java.sql.SQLException: [Macromedia][DB2 JDBC
> Driver][DB2]PROGRAM NAME DEFAULT.DDTEKA 0X4A44424334444232 NOT FOUND IN

PLAN

> null
>
> Can someone possibly shed some light on what's going on there?
>

[MrBonk]

Yeah, it's the JDBC, but I have no clue where to even start looking in DB2.
I'm only using it because I have to to test this app I'm working on.
Ultimately, it will end up on our corporate system, which is DB2 based only.
Beyond that, I'll be happy if I never see DB2 again! Talk about ridiculously
complicated......

[MrBonk]

Well, it turns out all I needed was the CF MX6.1 update (which apparently includes updated JDBC drivers) to solve the problem. I did that and all is well :-)