We're trying to use SQL Assist in the DB2 Control Center for DB2/LUW 9.5 and
we are getting the following error:
"Routine "SYSIBM.SQLTABL ES" (specific name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI :-727". SQLSTATE=38553"
If I try to call the SP directly I get the same error:
call sysibm.sqltable s('','ACCTASGN' ,'AUTO_NUMBERS' ,'','');
SQL0443N Routine "SYSIBM.SQLTABL ES" (specific name "TABLES") has returned
an
error SQLSTATE with diagnostic text "SYSIBM:CLI :-727". SQLSTATE=38553
Looking up SQL727 I get this:
SQL0727N An error occurred during implicit system action type
"<action-type>". Information returned for the error includes
SQLCODE "<sqlcode>" , SQLSTATE "<sqlstate> " and message tokens
"<token-list>".
Explanation:
The processing of a statement or command has caused the database manager
to implicitly perform additional processing. During this processing an
error was encountered. The action attempted is shown by the
"<action-type>":
1 implicit rebind of a package
2 implicit prepare of a cached dynamic SQL statement
3 implicit regeneration of a view
4 This return code is reserved for use by DB2.
5 incremental bind of a static SQL statement, not bound during
package bind time
6 implicit prepare of a reoptimizable statement containing
host-variables, special registers, or parameter markers
7 implicit regeneration of a trigger
8 implicit regeneration of a function
9 implicit regeneration of a check constraint
10 implicit instantiation of a global variable
The sqlcode, sqlstate and message token list (each token is separated by
the vertical bar character) are provided. The message tokens may be
truncated. See the corresponding message for the "<sqlcode>" for further
explanation of the error.
The original SQL statement or command that caused the "<action-type>"
cannot be processed and the implicit system action was not successful.
Federated system users: You may have received this message because you
dynamically prepared an SQL statement in a pass-through session and then
tried to execute the statement after the session was closed.
User response:
Check the message associated with the SQLCODE of the SQL statement that
failed. Follow the action suggested by that message.
For an invalid package, the REBIND command can be used to recreate the
error or to explicitly validate the package once the cause of the error
has been resolved.
For a failure while regenerating a view, the name of the view that
failed is recorded in the administration notification log. The failing
view can be dropped or a change made to the statement or command that
caused the view regeneration.
Federated system users: If the statement that failed was dynamically
prepared in a pass-through session, open another pass-through session,
write and prepare the statement again, and execute it while the session
is still open.
sqlcode: -727
sqlstate: 56098
But because the error doesn't return the error parameters I can't figure out
on what object the error is occuring. Any thoughts?
There is no problem when I'm logged in to CC with DBA access. Only with a
user that has less permissions, so I assume it's some sort of permission
issue for that user.
Thanks,
Frank
we are getting the following error:
"Routine "SYSIBM.SQLTABL ES" (specific name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI :-727". SQLSTATE=38553"
If I try to call the SP directly I get the same error:
call sysibm.sqltable s('','ACCTASGN' ,'AUTO_NUMBERS' ,'','');
SQL0443N Routine "SYSIBM.SQLTABL ES" (specific name "TABLES") has returned
an
error SQLSTATE with diagnostic text "SYSIBM:CLI :-727". SQLSTATE=38553
Looking up SQL727 I get this:
SQL0727N An error occurred during implicit system action type
"<action-type>". Information returned for the error includes
SQLCODE "<sqlcode>" , SQLSTATE "<sqlstate> " and message tokens
"<token-list>".
Explanation:
The processing of a statement or command has caused the database manager
to implicitly perform additional processing. During this processing an
error was encountered. The action attempted is shown by the
"<action-type>":
1 implicit rebind of a package
2 implicit prepare of a cached dynamic SQL statement
3 implicit regeneration of a view
4 This return code is reserved for use by DB2.
5 incremental bind of a static SQL statement, not bound during
package bind time
6 implicit prepare of a reoptimizable statement containing
host-variables, special registers, or parameter markers
7 implicit regeneration of a trigger
8 implicit regeneration of a function
9 implicit regeneration of a check constraint
10 implicit instantiation of a global variable
The sqlcode, sqlstate and message token list (each token is separated by
the vertical bar character) are provided. The message tokens may be
truncated. See the corresponding message for the "<sqlcode>" for further
explanation of the error.
The original SQL statement or command that caused the "<action-type>"
cannot be processed and the implicit system action was not successful.
Federated system users: You may have received this message because you
dynamically prepared an SQL statement in a pass-through session and then
tried to execute the statement after the session was closed.
User response:
Check the message associated with the SQLCODE of the SQL statement that
failed. Follow the action suggested by that message.
For an invalid package, the REBIND command can be used to recreate the
error or to explicitly validate the package once the cause of the error
has been resolved.
For a failure while regenerating a view, the name of the view that
failed is recorded in the administration notification log. The failing
view can be dropped or a change made to the statement or command that
caused the view regeneration.
Federated system users: If the statement that failed was dynamically
prepared in a pass-through session, open another pass-through session,
write and prepare the statement again, and execute it while the session
is still open.
sqlcode: -727
sqlstate: 56098
But because the error doesn't return the error parameters I can't figure out
on what object the error is occuring. Any thoughts?
There is no problem when I'm logged in to CC with DBA access. Only with a
user that has less permissions, so I assume it's some sort of permission
issue for that user.
Thanks,
Frank