DB2 - Problem description
Problem IC73931 | Status: Closed |
CRASH IN SQLQGMPPFLUSHNICKNAME WHEN RUNNING CREATE OR REPLACE NICKNAME STATEMENT ON NON CATALOG PARTITION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Problem Abstract: CRASH in sqlqgMPPFlushNickname when running CREATE OR REPLACE NICKNAME statement on non catalog partition When running CREATE OR REPLACE NICKNAME statement on any non catalog partition, db2 will encounter a segv and crash. The trap file will contain a stack similar to this: -------Frame------ ------Function + Offset------ 0x0900000009E12408 sqlqgMPPFlushNickname__FPUcT1P8sqlrr_cb + 0x2F0 0x09000000081FA79C sqlrl_drop_nickname_worker__FP8sqlrr_cbPUcUiT2T3b + 0xC 0x09000000079631B0 sqlnq_check_uniq_tabname__FP20sqlnq_multipart_name13sqlnq_FTBTYP EP3loc + 0x338 0x090000000971E2A8 sqlnq_table_new__FP20sqlnq_multipart_name13sqlnq_FTBTYPEi + 0x138 0x090000000A75ED70 sqlnq_create_nickname__FPP8stknode_i10actiontypePUcP3loc + 0x19C 0x090000000AA46AFC sqlnp_parser__FP8sqlnp_cb + 0x120 0x090000000AA5DD6C sqlnp_parser__FP8sqlnp_cb + 0x90 <snip> | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
1) only issue the statement on the catalog partition or 2) separate the "CREATE OR REPLACE NICKNAME" statement into separate "DROP" and "CREATE" statements | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 9.7 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.01.2011 11.01.2012 11.01.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |