DB2 - Problem description
Problem IT39257 | Status: Closed |
TRANSFER OWNERSHIP OF A COMPILED TRIGGER IS MISSING INVALIDATION. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
After restoring a database in another instance. Privileges from the original instance owner are transferred to the new one and then revoked. The transfer ownership of a trigger from the old instance owner to the new instance owner does not succeed. On subsequent operations on the base table which fires the trigger, the operation will fail and report an error like this one, where DB2V105 is the original instance owner. DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0723N An error occurred in a triggered SQL statement in trigger "SCH.TRG1". Information returned for the error includes SQLCODE "-551", SQLSTATE "42501" and message tokens "DB2V105|EXECUTE|SCH.P1337189768". SQLSTATE=09000 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Any DB2 installation * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to Db2 V11.1.4.5 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Any DB2 installation * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to Db2 V11.1.4.5 * **************************************************************** | |
Comment | |
Fixed in Db2 V11.1.4.5 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.11.2021 30.11.2021 01.12.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |