Other effects of SET SESSION AUTHORIZATION: SET SESSION AUTHORIZATION causes the following to occur:
Other resources are preserved when SET SESSION AUTHORIZATION is executed, including declared global temporary tables. It is recommended that all declared global temporary tables be dropped or cleared before executing the SET SESSION AUTHORIZATION statement.
SET SESSION AUTHORIZATION restrictions: This statement can only be issued as the first statement that results in work that might be backed out during the unit of work. The following executable statements may be issued prior to executing SET SESSION AUTHORIZATION:
SET SESSION AUTHORIZATION is not allowed if any connections other than the connection to the current server exist, including any local connections to a non-default activation group.
SET SESSION AUTHORIZATION is not allowed if any held cursors are open or any held locators exist.
SET SESSION AUTHORIZATION scope: The scope of the SET SESSION AUTHORIZATION is the current thread. Other threads in the application process are unaffected.
(C) Copyright IBM Corporation 1992, 2006. All Rights Reserved.