DB2 - Problem description
Problem IC83040 | Status: Closed |
ALTER TABLE ON A TABLE OF WHICH AN INVALID VIEW HAS REFERENCES TO CAN ABEND DB2 WITH SIGNAL 11 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If a view is created but marked as invalid at the creation time (for example, the CREATE VIEW statement returns a warning message SQL20480W), an ALTER TABLE statement on the table of which the view has references to can abend DB2 with signal 11. This APAR does NOT apply to if the view was created successfully but later marked invalid. A possible call stack in the db2diag.log is: 5 sqlnq_qtb::generate_unambiguous_name 6 sqlnq_qun::generate_unambiguous_name .. 18 sqlnq_handle_named_ref_in_src 19 sqlnq_sem 20 sqlnp_smactn 21 sqlnp_parser 22 sqlnp_main 23 sqlnq_handle_sql_stmt 24 sqlnn_regen_trigger 25 sqlrlDropDepTriggers 26 sqlrlalt 27 sqlnq_alter_table_end 28 sqlnq_alter_table_stmt 29 sqlnp_smactn ==================================== | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 Fix Pack 1 * **************************************************************** | |
Local Fix: | |
Recreating the view with a valid syntax before running the ALTER TABLE statement. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 version 10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.05.2012 07.11.2012 07.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |