当所有列长度综合超过1048576时可能引发的一个dump错误，session会自动关闭。一般只有列很多且单列较“宽”时可能出现该错误。
已经测试的在10.2.0.1,以及10.2.0.3上均可以再现该问题，测试方法：
create table test
( c000 char(2000),
c001 char(2000),
...
c523 char(2000),
c524 char(576));
-- sum of all column size is 1048576(0x100000).
Run next shell script.
while [ 1 ]
do
echo "set feedback off"
echo "select * from test where c001 = 'A';"
done | sqlplus -s scott/tiger
Note 245840.1 Information on the sections in this article
以上循环执行一段时间后session会被关闭，告警日志中出现
ORA-07445: exception encountered: core dump [kpopfr()+339] [SIGFPE] [Integer divide by zero][0x002327FF5] [] []的记录。没有在9i版本上测试，不能确定其影响。
该bug在10.2.0.4 patch set中已被修复，也可以通过小补丁形式修复，Oracle发布的小布丁只针对10.2.0.3版本，即10.2.0.1上是不能打的。
附bug描述原文：
Subject: Bug 5753629 - Query may dump [in kpopfr / kposdi]
Doc ID: 5753629.8 Type: PATCH
Modified Date : 03-APR-2009 Status: PUBLISHED
@ Note to support: do not edit this note - it is auto generated
Bug 5753629 Query may dump [in kpopfr / kposdi]
This note gives a brief overview of bug 5753629.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.
Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions < 11
Versions confirmed as being affected
* 10.2.0.3
Platforms affected Generic (all / most platforms affected)
Fixed:
This issue is fixed in
* 10.2.0.3 Patch 9 on Windows Platforms
* 10.2.0.4 (Server Patch Set)
* 11.1.0.6 (Base Release)
* Process May Dump (ORA-7445) / Abend / Abort
* Dump in or under kpopfr / kposdi
* (None Specified)
Symptoms:
Related To:
Description
Repeatedly executing a query can lead to a dump in kpopfr.
eg:
create table test
( c000 char(2000),
c001 char(2000),
...
c523 char(2000),
c524 char(576));
-- sum of all column size is 1048576(0x100000).
Run next shell script.
while [ 1 ]
do
echo "set feedback off"
echo "select * from test where c001 = 'A';"
done | sqlplus -s scott/tiger
^
Dump occurs
Please note: The above is a summary description only. Actual symptoms can vary. Matching to any
symptoms here does not confirm that you are encountering this problem. Always consult with Oracle
Support for advice.
References
Bug 5753629 (This link will only work for PUBLISHED bugs)