|
Problem IT36155
|
Status: Closed |
NON-FATAL AF GENERATED WHEN DELETING A PARENT VIA THE SECOND COLUMN IN THE PRIMARY KEY WITH A CHILD FOREIGN KEY INDEX DISABLED
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
Given a primary key constraint of a parent (fk_part1 int,
fk_part2 int) with a child having a foreign key (parent_fk_part1
int, parent_fk_part2), if the fk constraint is added with INDEX
DISABLED then the following stack from a non-fatal AF may be
reported
afstack
mt_ex_throw_sig
afsig_handler
chkchildren
chkrowcons
dodmlrow
dodelupd
excommand
sq_execute_workhorse
sq_execute
sqmain
spawn_thread
th_init_initgls
startup |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC6 (when available). *
**************************************************************** |
| Local Fix: |
Delete via the full primary key - i.e. use both columns for the
candidate delete |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC6 (when available). *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC15 and 14.10.xC6. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.03.2021
18.05.2021
18.05.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
