ITPub博客

首页 > 数据库 > Oracle > oracle ORA-03137: TTC 协议内部错误: [12333] [11] [88] [72] [] [] [] []

oracle ORA-03137: TTC 协议内部错误: [12333] [11] [88] [72] [] [] [] []

原创 Oracle 作者:wanglinghua0907 时间:2024-01-11 13:51:32 0 删除 编辑

ORA-03137: TTC 协议内部错误: [12333] [11] [88] [72] [] [] [] []

wed NOV 16 21:35:41 2022 Errors in file /oracle/app/di [1233?] [11] [88] (72] wed NOV 16 2022 T race dumping is performing wed NOV 16 2022 Sweep inc] [652215] : compl eted Sweep inc2] [652215]: compl eted wed NOV 16 21:36:51 2022 (i nci dent=652215) :

解决方法:(mos Doc ID 1361107.1)

1. Disable Bind Peeking A common thread through the database bugs listed above is that the problenn does not occur if bind peeking is shutoff. Temporarily disabling bind peeking allows you to confirm whether this is the case in your environment as well. This can be done dynamically: SQL> alter aptim_peek If the ORA-3137 [12333] error no longer reproduces after disabling bind peeking, then in most cases, the problem is due to one of the database bugs listed above, or due to some variant of lone of those bugs. Note: disabling bind peeking can have an impacton the database. Specifically, it can alter the explain plan for some queries that use bind variables. This should taken into account, particularly before considering the use of this option as a long-term workaround. 2. Apply Relevant Database Patches Whenever possible, the recornmended solution when running a database version 11.1.0.7 is to apply the most recent PSU patch. 11.1.0.7.8 patch_12419384 includes patchM03463. For 11.1.0.7, can be applied on top of 11.1.0.7.8 ( no conflict). Patch.;9Z.Q3.4é3 can also be applied individually but requires PSU 11.1.0.7.6 may also applicable to databases version 11.1.0.7 If you have disabled bind peeking as a test, and the error no longer reproduces, then applying one of these patches would be the next step. Alternatively, if you are unable to disable bind peeking for some reason, you may consider applying one of these patches as a diagnostic test in itself, to confirm whether the patch fixes the problem for you. fixes the SQL Loader issue that may affect database version 12, 1.02. Upgrade the Database to Version 11.2.0.3 Many of the above bugs are fixed in version 11.2.0.3 of the database. 4. Contact Oracle Support if the problem still persists For JDBC connections that have resulted in the ORA-3137 error, the above database-centric approaches have the issue almost all of the time. If disabling bind peeking has no effect and the ORA-3137 [12333] still occurs, please contact Oracle Support, as this is a relatively rare scenario in which further investigation is needed.

Doc ID 1361107.1



1.设置隐藏参数

配置隐藏参数_optim_peek_user_binds

alter system set "_optim_peek_user_binds"=false scope=both;

查看隐藏参数

col name for a30

col VALUE for a10

col DESCRIB for a40

set lines 200

SELECT x.ksppinm NAME, y.ksppstvl VALUE, x.ksppdesc describ

FROM SYS.x$ksppi x, SYS.x$ksppcv y

WHERE x.inst_id = USERENV ('Instance')

AND y.inst_id = USERENV ('Instance')

AND x.indx = y.indx

AND x.ksppinm LIKE '%&par%';


2.不行的话打补丁或者升级到11203以上


来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/69980685/viewspace-3003443/ ,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
Oracle ACE、sql server、oceanbase数据库专家,拥有7年以上的大型数据库运维经验,主方向oracle,擅长故障排除、诊断,大体量(TB)迁移,异常故障修复等。拥有丰富主导大型项目经验。服务行业包括:运营商、银行、金融业、政府单位、医疗、制造业、高校等等。

注册时间:2020-07-31

  • 博文量
    116
  • 访问量
    88776