Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Oracle 11.2.0.1 alarm log error ORA-03137 and binding variable snooping BUG9703463

2025-04-07 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

During the second inspection of oracle database in December 2017, it was found that a specific version of BUG was triggered by SQL statements in the oracle database of a certain city. The details are as follows: operating system version: windows server 2008R2 database version: oracle 11.2.0.1 problem description: during the second inspection in December 2017, an error was found in the alarm log, with the error message as follows: 1912 oracle 08:27:35 Tue Dec 19 08:27:35 2017

ORA-03137: internal error of TTC protocol: [12333] [6] [50] [48] []

Errors in file d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ trace\ orcl_ora_5480.trc (incident=36699):

Incident details in: d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ incident\ incdir_36699\ orcl_ora_5480_i36699.trc

18/12/2017 17:19:56 Mon Dec 18 17:19:56 2017

ORA-03137: internal error of TTC protocol: [12333] [6] [50] [48] []

Incident details in: d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ incident\ incdir_36554\ orcl_ora_4572_i36554.trc

Errors in file d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ trace\ orcl_ora_4572.trc (incident=36554):

16:18:58 ORA-03137: TTC protocol internal error: [12333] [6] [50] [48] []

Errors in file d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ trace\ orcl_ora_3968.trc (incident=36547):

Mon Dec 18 16:18:58 2017

Incident details in: d:\ app\ administrator\ diag\ rdbms\ orcl\ orcl\ incident\ incdir_36547\ orcl_ora_3968_i36547.trc found from the orcl_ora_5480_i36699.trc file that the application SQL statement that triggered ORA-03137 did use the binding variable:-sql_id=cjx2sya2mu4zm

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

And bill_no =: ParamBillNo3

Order by month desc, sid)) row_

Where rownum 0

View oracle metalink,ORA-03137 for ORA03137 and oracle 11.2.0.1 for windows server 2008R2: TTC protocol internal error: [12333] [6] [50] [48] related to the application of SQL statements using binding variables

Non-public Bug:9703463 (document ID 1615363.1):

Solution: 1. The patch to solve the ora-03137 error triggered by binding variables in Oracle 11.2.0.1 has been included in the PSU patch set Patch:10245351. You need to apply the patch set Patch:10245351 to the database.

Risk: oracle database application patch set may introduce new unknown BUG 2, disable oracle 11.2.0.1 bind variable function: alter system set "_ optim_peek_user_binds" = false; risk: will lead to database instability, resulting in inaccurate execution plan of application SQL statements 3. Upgrading the database version to version 11.2.0.3 or later can solve the ORA-03137 problem.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report