oracle 11.2.0.1 for windows server2008r2告警ORA-03137

2017.10.20贵州一地市oracle 11.2.0.1医保相关应用程序功能异常无法运行,查看数据库告警日志有如下报错:

Fri Oct 20 16:03:04 2017
Trace dumping is performing id=[cdmp_20171020160304]
Fri Oct 20 16:03:05 2017
Sweep [inc][140434]: completed
Sweep [inc2][140434]: completed
Fri Oct 20 16:12:40 2017
Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_4756.trc (incident=140155):
ORA-03137: TTC 协议内部错误: [12333] [6] [50] [48] [] [] [] []
Incident details in: e:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_140155\orcl_ora_4756_i140155.trc
Fri Oct 20 16:12:41 2017
Trace dumping is performing id=[cdmp_20171020161241]

查看告警日志提示的trc文件:

Dump file e:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_140155\orcl_ora_4756_i140155.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.1 Service Pack 1 
CPU : 24 - type 8664, 12 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:45309M/65508M, Ph+PgF:110993M/131015M 
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 32
Windows thread id: 4756, image: ORACLE.EXE (SHAD)

*** 2017-10-20 16:12:40.170
*** SESSION ID:(515.23643) 2017-10-20 16:12:40.170
*** CLIENT ID:() 2017-10-20 16:12:40.170
*** SERVICE NAME:(orcl) 2017-10-20 16:12:40.170
*** MODULE NAME:() 2017-10-20 16:12:40.170
*** ACTION NAME:() 2017-10-20 16:12:40.170

Dump continued from file: e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_4756.trc
ORA-03137: TTC 协议内部错误: [12333] [6] [50] [48] [] [] [] []

========= Dump for incident 140155 (ORA 3137 [12333]) ========

*** 2017-10-20 16:12:40.170
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=905vd7vnpuh6n) -----
select *

from (select row_.*, rownum NumRow from (select * from (select

sid,

code,

to_char(month,'yyyyMM') as month ,

hisid,

bill_no,

state,

billdate,

hospital_id,

patient_id,

patient_name,

admission_number,

admission_disease_name,

disease_name,

claim_name,

benefit_name,

bmino,

benefit_group_name,

item_date,

dept_id,

dept_name,

item_id,

item_name,

item_type,

physician_name,

bmi_convered_amount,

bmi_nopay,

reject_reson,

remrk,

version_no,

hospital_backs,

versionstate,

rule_name,

back_reson,

reback_reason,

processState,

is_approval,

nvl(version,1) as version,

nvl(trickProgress,0) as trickProgress,

nvl(is_retrick,0) as is_retrick,

PERIOD,

billex.NUMBER01 as Number01,

billex.NUMBER02 as Number02,

billex.NUMBER03 as Number03,

billex.NUMBER05 as Number05,

billex.NUMBER06 as Number06,

billex.NUMBER07 as Number07,

HOSPITAL_REMARK_DETAIL,

decode(bitand((select sum(distinct(nvl(g.rule_bit, 0))) from gz_list g where g.business_type = '0'),rule_bit),0,0,1) as BUSINESS_TYPE,

REFEEDBACK_REASON_DETAIL,

(select sum(a.reject_money) from dw_opinion_details b join dw_billdetail a on a.id =b.detailid

where b.code=dw_opinions.code and b.version_no=dw_opinions.version_no and b.month=dw_opinions.month ) as sumrejectmoney

from dw_opinions left join dw_bill_ex billex on dw_opinions.hisid = billex.billid

where 1=1 and month =to_date(:ParamMonth0,'yyyyMM') and hospital_id = :ParamHospitalId1 and version_no = :versionno2 order by month desc,sid)) row_ where rownum <= 10)

where NumRow > 0

查询oracle metalink了解到这是oracle 11.2.0.1自身的一个Bug 9445675(文档 ID 1361107.1),与oracle数据库的绑定变量窥探有关  

根据trc文件提示到的sql可知,sql语句确实使用了绑定变量,解决改问题的方法有3种:

1、取消数据库的绑定变量窥探:alter system set "_optim_peek_user_binds"=false;

注意取消绑定变量窥探对数据库有影响,会改变sql的执行计划

2、对数据库打补丁

PSU 11.1.0.7.8 Patch 12419384 includes Patch:9703463

For 11.1.0.7, Patch 9243912

Patch:9703463  can also be applied individually but requires PSU 11.1.0.7.6 

Patch:8625762  may also be applicable to databases version 11.1.0.7

Patch:18841764 fixes the SQL Loader issue that may affect database version 12.1.0.2

3、升级数据库到11.2.0.3及以上版本

由于项目功能使用紧急,临时取消数据库绑定变量,应用功能能够正常使用,事后再做oracle 11.2.0.1 to 11.2.0.4的升级。

时间: 2024-07-31 13:19:26

oracle 11.2.0.1 for windows server2008r2告警ORA-03137的相关文章

oracle 11.2.0.1 for windows server2012R2应用p12429529_112010_MSWIN-x86-64补丁

> > > > > > > > >> > >>> > > > > > > > > > > > > > >

oracle 11.2.0.1告警日志报错ORA-03137与绑定变量窥探BUG9703463

2017年12月份第二次oracle数据库巡检中,发现某一地市oracle数据库发现SQL语句触发特定版本BUG,详细信息如下: 操作系统版本:windows server 2008R2数据库版本:oracle 11.2.0.1问题描述:2017年12月份第二次巡检中,发现告警日志报错,报错信息如下:19/12/2017 08:27:35 Tue Dec 19 08:27:35 2017 ORA-03137: TTC 协议内部错误: [12333] [6] [50] [48] [] [] []

oracle 11.1.0.7版本也会出现access$表丢失导致数据库无法启动

下面我们来看看oracle 11.1.0.7版本也会出现access$表丢失导致数据库无法启动,有需要了解的朋友可以进入看看吧. 有网友咨询数据库启动报ora-01092:ORACLE 实例终止.强制断开连接,请求帮忙处理 数据库版本 Trace file d:appadministratordiagrdbmsorclorcltraceorcl_ora_5648.trc Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64b

solaris x86安装ORACLE 11.2.0.3因SWAP不足报错

solaris x86安装ORACLE 11.2.0.3软件时因SWAP不足报错: INFO: ld: fatal: mmap anon failed 1.ORACLE软件安装到86%时报错,图忘截了.日志如下: /oracle/u01/app/oracle/product/11.2.0/ INFO: db_1/lib/sysliblist` -R /opt/SUNWcluster/lib -R/export/home/oracle/u01/app/oracle/product/11.2.0/d

Oracle 11.2.0.3 ORA-12012ORA-29280 ORA-06512

  Oracle 11.2.0.3 ORA-12012ORA-29280 ORA-06512   问题现象: db alert日志中出现如下告警信息: Errors in file/app/oracle/diag/rdbms/cctv/CCTV2/trace/CCTV2_j000_1370.trc: ORA-12012: error on auto execute of job"ORACLE_OCM"."MGMT_CONFIG_JOB_2_2" ORA-29

[20130320]升级oracle 11.2.0.1到11.2.0.3.txt

[20130320]升级oracle 11.2.0.1到11.2.0.3.txt 一直想升级自己的测试环境从oracle 11.2.0.1到11.2.0.3.我的使用版本是 SQL> select * from v$version where rownum BANNER -------------------------------------------------------------------------------- Oracle Database 11g Enterprise Ed

ORACLE 11.2.0.4 dg搭建及对DDL的支持验证

    今天,有同事问ORACLE 11.2.0.4 dataguard是否对DDL支持:由于,我工作中oracle 11g的dataguard环境很少,所以对她的研究不是很多:因此,对于有疑问的知识,最好的办法就是用实验数据进行验证了.     首先,先说明下实验结论:ORACLE 11.2.0.4的dataguard对DDL是支持的.     服务器环境: 主库 [oracle@oradbs ~]$ uname -a Linux oradbs 2.6.18-194.el5 #1 SMP Tu

Oracle 11.2.0.1升级到11.2.0.3

Oracle  11.2.0.1升级到11.2.0.3 最近听了李光老师的关于oracle的升级公开课,深有感悟,之前一直想自己测试的,没有下定决心,这几天自己在虚拟机上测试了一下,测试的过程如下,当然这个只是一些基本的步骤,实际的生产环境我想比这个复杂的多了,但是不用急,慢慢来,循序渐进吧... 由于blog的文档结构没有办法显示,所以这里我截取我的文档结构图: 数据库情况 单实例非ASM存储 ORACLE_SID : orcl ORACLE_HOME: /u01/app/oracle/pro

SUSE 11.1 安装ORACLE 11.2.0.3 ASM非RAC双机过程纪要

SUSE 11.1 安装ORACLE 11.2.0.3 ASM非RAC双机过程纪要 增加用户和组: /usr/sbin/groupadd -g 501 oinstall /usr/sbin/groupadd -g 502 dba /usr/sbin/groupadd -g 503 oper /usr/sbin/groupadd -g 504 asmadmin /usr/sbin/groupadd -g 505 asmoper /usr/sbin/groupadd -g 506 asmdba us