N**********d
发帖数: 9292 | 1 网上搜了一下，好些都是说
Refer to
ORA-24550 Signal Received Error From Client Based Application [ID 1284564.1]
BUG 9342118 : OCISTMTRELEASE CRASHES WITH CORE DUMP WHEN CALLED OUTSIDE A
TRANSACTION
但是这些具体内容是什么，好像都看不到啊。
还有人说创建一个文件：
$TNS_ADMIN/sqlnet.ora
里面放三行
DIAG_ADR_ENABLED=OFF
DIAG_DDE_ENABLED=FALSE
DIAG_SIGHANDLER_ENABLED=FALSE
这个也在客户端加了，然后重启程序，但是还是没效果，程序还是照样崩溃。
先谢谢大家了 |
c*****d
发帖数: 6045 | 2 如果确认是bug 9342118，看metalink上的文档
PROBLEM:
--------
Calling OCIStmtRelease() outside a transaction terminates program with core
dump.
You can avoid by either using a tag or by calling OCIStmtRelease() inside an
open transaction. I can't repro with 10.2 client but I can repro with 11.1.
0.7 and 11.2.0.1 client whereas the database versions doesn't have any
impact.
WORKAROUND:
-----------
Either using a tag nor calling OCIStmtRelease() inside an open transaction
can be counted a a valid workaround as they can't be implemented and indeed
opening a transaction to call OCIStmntRelease() is helpfull.
Currently the customer is not using statement caching [ make using tags
useless ] and he can't review its complete code to check whether
OCIStmtRelease() is only called inside an open transaction. |
N**********d
发帖数: 9292 | 3 呃，谢谢了，用的occi，没有直接用到OCIStmtRelease
core
an
1.
【在 c*****d 的大作中提到】
: 如果确认是bug 9342118，看metalink上的文档
: PROBLEM:
: --------
: Calling OCIStmtRelease() outside a transaction terminates program with core
: dump.
: You can avoid by either using a tag or by calling OCIStmtRelease() inside an
: open transaction. I can't repro with 10.2 client but I can repro with 11.1.
: 0.7 and 11.2.0.1 client whereas the database versions doesn't have any
: impact.
: WORKAROUND:
|
