Hi ,

DB2 v6.1(FP10), AIX4.3.3

When i run db2exfmt i am getting the following error. Any idea about this problem??.
As per SQL code 727, i rebound the packages(db2rbind dbname /l all). But still i am getting the same error.

-----------------
Connecting to the Database.
Connect to Database Successful.
Error during Select, near line 822.

Error Message =
SQL0727N An error occurred during implicit system action type "1".
Information returned for the error includes SQLCODE "-551", SQLSTATE
"42501" and message tokens "USER1|SELECT|SYSIBM.SYSTABLES".
SQLSTATE=56098


SQLCA
Size = 136
SQLCODE = -727
Tokens = 1 þ -551 þ 42501 þ USER1|SELECT|SYSIBM.SYSTABLES
Function= SQLRPRIV
RC = 0xFFFF877E = -30850
Reason = 0x0000 = 0
Reason2 = 0x0000 = 0
Line # = 772
Warning flags =

Press ENTER to Continue ...

The user USER1 does not have authority to perform a select on SYSIBM.SYSTABLES

Make sure USER1 has the privileges

Cheers

Sathyaram

Here are some thoughts and I hope this helps. The actual error is

SQLCODE "-551"

Which states that the userid does not have the privileges to perform the operation.

That kind of ties in with
Function= SQLRPRIV

Check whether the user has privileges on the explain tables.

Look up db2exfmt in the administration guide, performance.

Thank you.

Actually USER1 left the company. So we revoked all privileges from USER1.

After getting this error, I tried to grant all privileges(connect,bindadd,dbadm) to this USER1. And explicitly i granted select privilege on SYSIBM.SYSTABLES. But still i was getting the same error.

When i see the SQLCODE 551, it is asking me to grant the package privilege to PUBLIC. But my audit team will not allow me to grant to PUBLIC.

Actually i used 'instance id' to do db2exfmt. So my doubt is eventhough i revoke privileges from USER1, why the 'instance id' itself can not do db2exfmt?

Thank you very much in advance.

Regards
Prakash

Are you getting the same error with sysadm as well or is it a different error?

I think the bind statement that -551 asks to be run is the same that has to be run after a fixpak upgrade. That is what gives users the ability to use nullid packages.

The other thought that comes to mind is the fact that the user, user1 was invalidated - that may have invalidated access to the explain tables. Maybe you can create a set of explain tables again for the user.