|
Problem IT01639
|
Status: Closed |
ANONYMOUS BLOCK FAILS WITH SQL0551N AFTER 3 OR MORE HADR TAKEOVER. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Running an anonymous block will fail with SQL0551N (no
authorization) after three or more HADR takeover.
The following steps illustrate how users encounter this problem.
1. Create a SQL procedure, then grant EXECUTE privilege to
non-admin user.
2. Run the procedure as the non-admin user who has EXECUTE
granted within an anonymous block.
3. Perform step 2 after each takeover HADR. The call to
procedure within an anonymous block will eventually fail with
SQL0551N after 3 or more takeovers.
begin
declare t time;
call appl1.proc1(t);
end
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0551N "NEWTON" does not have the required authorization or
privilege to
perform operation "EXECUTE" on object
"USER1.SQL131036262596530".
SQLSTATE=42501 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Uses who use anonymous blocks in HADR systems. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to V10.5 FixPack 4 or later. *
**************************************************************** |
| Local Fix: |
Restart the HADR pair like as below to recover from the
SQL0551N.
1. Deactivate HADR Primary, then deactivate HADR Standby.
2. Activate HADR Standby, then activate HADR Primary. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in DB2 V10.5 FixPack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.05.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
