暂无图片
大量硬解析错误
我来答
分享
Donnieyen
2019-11-27
大量硬解析错误

2019-11-04T06:47:36.613885+08:00
(3)😗****************************************************************
(3):An internal routine has requested a dump of selected redo.
(3):This usually happens following a specific internal error, when
(3):analysis of the redo logs will help Oracle Support with the
(3):diagnosis.
(3):It is recommended that you retain all the redo logs generated (by
(3):all the instances) during the past 12 hours, in case additional
(3):redo dumps are required to help with the diagnosis.
(3)😗****************************************************************
2019-11-04T07:27:40.955127+08:00
CUSTOMER(4)😗****************************************************************
CUSTOMER(4):An internal routine has requested a dump of selected redo.
CUSTOMER(4):This usually happens following a specific internal error, when
CUSTOMER(4):analysis of the redo logs will help Oracle Support with the
CUSTOMER(4):diagnosis.
CUSTOMER(4):It is recommended that you retain all the redo logs generated (by
CUSTOMER(4):all the instances) during the past 12 hours, in case additional
CUSTOMER(4):redo dumps are required to help with the diagnosis.
CUSTOMER(4)😗****************************************************************
2019-11-04T07:47:45.737154+08:00
Thread 1 advanced to log sequence 4992 (LGWR switch)
Current log# 2 seq# 4992 mem# 0: +DATA/ORCL/ONLINELOG/group_2.263.990479999
Current log# 2 seq# 4992 mem# 1: +FIR/ORCL/ONLINELOG/group_2.258.990480001
2019-11-04T07:47:45.918043+08:00
Archived Log entry 10389 added for T-1.S-4991 ID 0x85e56dfd LAD:1
2019-11-04T08:18:23.521335+08:00
Thread 1 advanced to log sequence 4993 (LGWR switch)
Current log# 1 seq# 4993 mem# 0: +DATA/ORCL/ONLINELOG/group_1.262.990479999
Current log# 1 seq# 4993 mem# 1: +FIR/ORCL/ONLINELOG/group_1.257.990480001
2019-11-04T08:18:23.700860+08:00
Archived Log entry 10390 added for T-1.S-4992 ID 0x85e56dfd LAD:1
2019-11-04T08:18:30.279835+08:00
WARNING: too many parse errors, count=100 SQL hash=0x750004bb
PARSE ERROR: ospid=31984, error=933 for statement:
2019-11-04T08:18:30.279933+08:00
DELETE FROM wriadvsqltrtnplanWHEREtaskid=:tidANDexecname=:executionnameAdditionalinformation:hd=0x11a7d79b0phd=0x1119ddc78flg=0x28cisid=0sid=0ciuid=0uid=020191104T08:18:30.280047+08:00PL/SQLCallStackobjectlineobjecthandlenumbername0x1c88ada48259typebodySYS.WRI_adv_sqlt_rtn_planWHERE task_id = :tid AND exec_name = :execution_name Additional information: hd=0x11a7d79b0 phd=0x1119ddc78 flg=0x28 cisid=0 sid=0 ciuid=0 uid=0 2019-11-04T08:18:30.280047+08:00 ----- PL/SQL Call Stack ----- object line object handle number name 0x1c88ada48 259 type body SYS.WRI_ADV_SQLTUNE.SUB_DELETE_EXECUTION
0x1ad65c1b8 2134 package body SYS.PRVT_ADVISOR.COMMON_DELETE_TASK
0x1ad65c1b8 7342 package body SYS.PRVT_ADVISOR.DELETE_EXPIRED_TASKS
0x1efd85b18 1 anonymous block
WARNING: too many parse errors, count=200 SQL hash=0x750004bb
PARSE ERROR: ospid=31984, error=933 for statement:
2019-11-04T08:18:30.410086+08:00
DELETE FROM wriadvsqltrtnplanWHEREtaskid=:tidANDexecname=:executionnameAdditionalinformation:hd=0x11a7d79b0phd=0x1119ddc78flg=0x28cisid=0sid=0ciuid=0uid=020191104T08:18:30.410201+08:00PL/SQLCallStackobjectlineobjecthandlenumbername0x1c88ada48259typebodySYS.WRI_adv_sqlt_rtn_planWHERE task_id = :tid AND exec_name = :execution_name Additional information: hd=0x11a7d79b0 phd=0x1119ddc78 flg=0x28 cisid=0 sid=0 ciuid=0 uid=0 2019-11-04T08:18:30.410201+08:00 ----- PL/SQL Call Stack ----- object line object handle number name 0x1c88ada48 259 type body SYS.WRI_ADV_SQLTUNE.SUB_DELETE_EXECUTION
0x1ad65c1b8 2134 package body SYS.PRVT_ADVISOR.COMMON_DELETE_TASK
0x1ad65c1b8 7342 package body SYS.PRVT_ADVISOR.DELETE_EXPIRED_TASKS
0x1efd85b18 1 anonymous block
WARNING: too many parse errors, count=300 SQL hash=0x750004bb
PARSE ERROR: ospid=31984, error=933 for statement:
2019-11-04T08:18:30.541247+08:00
DELETE FROM wri$_adv_sqlt_rtn_planWHERE task_id = :tid AND exec_name = :execution_name
Additional information: hd=0x11a7d79b0 phd=0x1119ddc78 flg=0x28 cisid=0 sid=0 ciuid=0 uid=0

我来答
添加附件
收藏
分享
问题补充
2条回答
默认
最新
gelyon

DELETE FROM wridvqlttnlan ……语句解析发生错误,检查下这个语句,重新分析下这个表的统计信息之类的

暂无图片 评论
暂无图片 有用 0
打赏 0
周勇

M00n Report “ORA-00933: SQL Command Not Properly Ended” Frequently in 12.2.0.1 (文档 ID 2321436.1)

err号匹配该文档,都是err=933,报错也一样,可以参考。

In 12.2.0.1,M00n slave processes report ‘ORA-00933’ frequently in alert log:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2017-08-30T22:18:49.533322+08:00
Errors in file /u01/app/oracle/diag/rdbms///trace/_m002_77817.trc:
ORA-00933: SQL command not properly ended ★
2017-08-30T22:18:52.591018+08:00
WARNING: too many parse errors, count=100 SQL hash=0x750004bb
PARSE ERROR: ospid=77817, error=933 for statement:
2017-08-30T22:18:52.591247+08:00
DELETE FROM wriadvsqltrtnplanWHEREtaskid=:tidANDexecname=:executionnameAdditionalinformation:hd=0x1ef6f9e2a0phd=0x1ef6f9f6c8flg=0x28cisid=0sid=0ciuid=0uid=020170830T22:18:52.591466+08:00PL/SQLCallStackobjectlineobjecthandlenumbername0x2095465080259typebodySYS.WRI_adv_sqlt_rtn_planWHERE task_id = :tid AND exec_name = :execution_name Additional information: hd=0x1ef6f9e2a0 phd=0x1ef6f9f6c8 flg=0x28 cisid=0 sid=0 ciuid=0 uid=0 2017-08-30T22:18:52.591466+08:00 ----- PL/SQL Call Stack ----- object line object handle number name 0x2095465080 259 type body SYS.WRI_ADV_SQLTUNE.SUB_DELETE_EXECUTION
0x219fa47d70 2134 package body SYS.PRVT_ADVISOR.COMMON_DELETE_TASK
0x219fa47d70 7342 package body SYS.PRVT_ADVISOR.DELETE_EXPIRED_TASKS
0x1f9f816918 1 anonymous block
2017-08-30T22:57:39.000273+08:00
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Running an errorstack shows which delete statement it fails:
SQL>alter system set events ‘933 trace name errorstack level 3’;

2017-09-01T08:20:36.837653+08:00

DELETE FROM wri$_adv_sqlt_rtn_planWHERE task_id = :tid AND exec_name = :execution_name

You may confirm in SQL*Plus:

SQL> DELETE FROM wri$_adv_sqlt_rtn_planWHERE task_id=1 AND exec_name = ‘aaa’;

DELETE FROM wri$_adv_sqlt_rtn_planWHERE task_id=1 AND exec_name = ‘aaa’

ERROR at line 1:

ORA-00933: SQL command not properly ended

CAUSE
This is due to following internal bug:

Bug 26764561 ORA-00933 IN SYS.WRI$_ADV_SQLTUNE.SUB_DELETE_EXECUTION

SOLUTION

  1. Fixed in release 18.1

  2. Apply Patch 26764561

暂无图片 评论
暂无图片 有用 0
打赏 0
回答交流
Markdown


请输入正文
提交
相关推荐
enq: TX - row lock contention ---- 为什么锁的是系统的表?
回答 5
已采纳
查询会话ID为1516,1613的详细信息,另外userid57是哪个用户?
oracle ADG 级联备库 Error 12154 received logging on to the standby 这个现象正常吗?
回答 2
配置都没问题,就是主库的tnsnames.ora没配级联备库的信息。
Oracle数据库中比如有个查询需要导出40w数据,有没有设置数据库查询超时时间的参数控制?
回答 3
超时还有个经常看到的报错是:ORA01555causedbySQLstatementbelow1)具体分析提供的SQLID,看是否能够调优2)增加快照过期时间,及要考虑undo的大小
能不能用一个user账号 ,管理oracle下同一个SID下的多个表空间?
回答 2
ORACLESID是操作系统的环境变量啊建议您了解下基本的概念呢。
Docker内安装Oracle19c 创建用户带#
回答 2
已采纳
C这种类型么?那是因为你创建的是容器数据库,而你是在CDB中创建用户,在CDB中创建用户必须要加C不想这样操作的话,可以创建个pdb,然后连接pdb,在pdb中创建用户,就类似在11g操作一样也可以重
有什么办法查看历史锁表是哪个表引起的吗?
回答 1
历史锁表是看过去锁的SQL吗?还是看过去一段时间,哪个表上的锁比较多?
Oracle数据库为什么说位图索引适合用于读密集的环境,而不适合写密集的环境?
回答 1
已采纳
一个位图索引键条目会指向很多行的数据。如果一个会话修改了索引列的数据,那么在大多数情况下,这个索引条目指向的所有行都会被锁定。倘若其他会话也需要更新同样的位图索引条目,那这个会话就会被“关在门外”。这
Oracle RMAN 中list能根据时间自动排序吗?
回答 1
已采纳
listbackupsetsummary;
自动任务执行了,却又没执行?
回答 2
已采纳
提供两个思路,我现在手头没环境,您可以先自行测试下:可能是环境变量问题,sh里引入bashrc试下也可能是cron解析的事情,比如写成bashc'nohup…'试试
oracle RMAN 能不能 直接把数据备份到异机上?
回答 2
已采纳
没法直接备份,挂一个NFS到你的源库就可以了。