Informix - Problem description
| Problem IT09130 | Status: Closed |
RATIO_TO_REPORT IN GROUP BY CLAUSE CRASHES ENGINE | |
| product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
| Problem description: | |
With stores_demo database, following SQL crashes the engine:
==
select company, sum(ship_weight), sum(ship_charge),
ratio_to_report(sum(ship_charge)) over() * 100 as ratio_charge
from orders, customer
where orders.customer_num=customer.customer_num
group by 1,4;
==
11:31:58 Assert Failed: No Exception Handler
11:31:58 IBM Informix Dynamic Server Version 12.10.FC2
11:31:58 Who: Session(63, informix@server, 10155, 10af5b7d0)
Thread(231, sqlexec, 10af18d18, 10)
File: mtex.c Line: 517
11:31:58 Results: Exception Caught. Type: MT_EX_OS, Context:
mem
11:31:58 Action: Please notify IBM Informix Technical Support.
11:31:58 See Also: /space/ifmx/12.10.FC2/tmp/af.4cf1e8d,
shmem.4cf1e8d.0
11:34:08 Need to fix... buffers no longer in res segment
11:39:20 mtex.c, line 517, thread 231, proc id 10059, No
Exception Handler.
11:39:23 Fatal error in ADM VP at mt.c:14311
11:39:23 Unexpected virtual processor termination: pid = 10059,
exit status = 0x1.
11:39:24 PANIC: Attempting to bring system down | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * users having RATIO_TO_REPORT function and group by * * operation. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC6 * **************************************************************** | |
| Local Fix: | |
| Solution | |
Problem Fixed In IBM Informix Server 12.10.xC6 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.05.2015 30.12.2015 30.12.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
12.10.xC6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 12.10.xC6 |
|