Connecting Tech Pros Worldwide Help | Site Map
 
 
LinkBack Thread Tools Search this Thread
  #1  
Old November 12th, 2005, 07:24 AM
Doug Ly
Guest
 
Posts: n/a
Default Error code when using DB2 Command Center

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.SQLC2D01". SQLSTATE=42501

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


  #2  
Old November 12th, 2005, 07:24 AM
Mark A
Guest
 
Posts: n/a
Default Re: Error code when using DB2 Command Center

"Doug Ly" <deadlock@dev.null> wrote in message
news:GTMoc.10821$kc3.3246@newssvr23.news.prodigy.c om...[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.SQLC2D01". 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.


 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Popular Articles

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over 205,248 network members.