Error code when using DB2 Command Center

[Doug Ly]

Hi ,

connect to Blah user blah using blah

------------------------------------------------------------------------

Database Connection Information

Database server = DB2/6000 7.2.3
SQL authorization ID = Blah
Local database alias = Blah
I recieved this error message when using the DB2 command center.

--------------------------- Command entered ----------------------------
select *
from Db2inst1.test
------------------------------------------------------------------------

SQL0551N "Blah" does not have the privilege to perform operation "EXECUTE"
on
object "NULLID.SQLC2D0 1". SQLSTATE=42501

It's weird because I can do anything with that account on Lotus Approach or
WinSQL.
Thank you for your help.

[Mark A]

Re: Error code when using DB2 Command Center

"Doug Ly" <deadlock@dev.n ull> wrote in message
news:GTMoc.1082 1$kc3.3246@news svr23.news.prod igy.com...[color=blue]
> Hi ,
>
> connect to Blah user blah using blah
>
> ------------------------------------------------------------------------
>
> Database Connection Information
>
> Database server = DB2/6000 7.2.3
> SQL authorization ID = Blah
> Local database alias = Blah
> I recieved this error message when using the DB2 command center.
>
> --------------------------- Command entered ----------------------------
> select *
> from Db2inst1.test
> ------------------------------------------------------------------------
>
> SQL0551N "Blah" does not have the privilege to perform operation[/color]
"EXECUTE"[color=blue]
> on
> object "NULLID.SQLC2D0 1". SQLSTATE=42501
>
> It's weird because I can do anything with that account on Lotus Approach[/color]
or[color=blue]
> WinSQL.
> Thank you for your help.
>[/color]
Lotus is probably using the ODBC interface, and the Command Center is using
the CLI. Try rebinding the packages using the Client Configuration Assistant
or grant execute on the package to public (or whatever). The rebind should
have been performed with each fixpak upgrade, but it may have been missed.