Well, this time, I took an example from publib:
CALL SYSPROC.ALTOBJ('VALIDATE', CAST (NULL AS VARCHAR(2048)), 123, ?)
I ran it and I get the same error:
SQL0443N Routine "SYSPROC.ALTOBJ" (specific name "ALTOBJ") has
returned an
error SQLSTATE with diagnostic text "DBA7904, DBAD". SQLSTATE=38553
BTW, sometime I get diagnostic text as "SQL0669" in the above error
message. These messages lead to nowhere...I don't know how db2 throw a
diagnostic text which is not given in any of the documents! Anyways,
looks like none have idea about using this procedure...I just take
alternate way to get my things done...
Thanks for your time...
> Perhaps you could post the DDL of the table that you are attempting to
> modify, plus any of its indexes,constraints,triggers,views and
> foreign-keys for that table, and the exact parameters that you are
> passing to sysproc.altobj.
Gert van der Kooij - 12 Jul 2006 23:10 GMT
> SQL0443N Routine "SYSPROC.ALTOBJ" (specific name "ALTOBJ") has
> returned an
> error SQLSTATE with diagnostic text "DBA7904, DBAD". SQLSTATE=38553
c:\>db2 ? dba7904
DBA7904N The user does not have "<authority name>" authority,
which is required to run the SYSPROC.ALTOBJ stored
procedure.
Explanation:
Both DBADM and LOAD authorities are required to run the
SYSPROC.ALTOBJ stored procedure.
User Response:
Obtain the necessary authorities before running the stored
procedure.