暂无图片
Trace Bucket Dump 在trace目录的文件中的信息是否需要关注并解决
我来答
分享
Edward
2022-09-17
Trace Bucket Dump 在trace目录的文件中的信息是否需要关注并解决

1、近期trace目录中出现了包含
cdmp关键字的文件夹
image.png
2、这些文件夹中文件名包括Bucket关键字
image.png
3、查询其中一个文件,主要内容如下:
Trace file /u01/app/oracle/diag/rdbms/easdb/easdb1/trace/cdmp_20220916100401/easdb1_ora_143792_bucket.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: mwrac1
Release: 4.1.12-112.16.4.el7uek.x86_64
Version: #2 SMP Mon Mar 12 23:57:12 PDT 2018
Machine: x86_64
Instance name: easdb1
Redo thread mounted by this instance: 1
Oracle process number: 47
Unix process pid: 143792, image: oracle@mwrac1

*** 2022-09-16 10:04:01.774
*** SESSION ID:(1791.23913) 2022-09-16 10:04:01.774

*** 2022-09-16 10:04:01.774
Process diagnostic dump for oracle@mwrac1, OS id=143792,
pid: 47, proc_ser: 243, sid: 1791, sess_ser: 23913

current sql: UPDATE T_LOG_App SET FIsSuccessed = 1 WHERE FID = :1
client details:
O/S info: user: root, term: unknown, ospid: 1234
machine: web1 program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
Current Wait Stack:
0: waiting for ‘SQLNet message from client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95769 seq_num=30235 snap_id=1
wait times: snap=1 min 11 sec, exc=1 min 11 sec, total=1 min 11 sec
wait times: max=infinite, heur=1 min 11 sec
wait counts: calls=0 os=0
in_wait=1 iflags=0x1a0
Wait State:
fixed_waits=0 flags=0x22 boundary=(nil)/-1
Session Wait History:
elapsed time of 0.000013 sec since current wait
0: waited for 'SQL
Net message to client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95768 seq_num=30234 snap_id=1
wait times: snap=0.000003 sec, exc=0.000003 sec, total=0.000003 sec
wait times: max=infinite
wait counts: calls=0 os=0
occurred after 0.000101 sec of elapsed time
1: waited for ‘reliable message’
channel context=0x136151d988, channel handle=0x1411545a08, broadcast message=0x1257cb1b38
wait_id=95767 seq_num=30233 snap_id=1
wait times: snap=0.000618 sec, exc=0.000618 sec, total=0.000618 sec
wait times: max=infinite
wait counts: calls=1 os=1
occurred after 0.000078 sec of elapsed time
2: waited for ‘reliable message’
channel context=0x136151d988, channel handle=0x1411545a08, broadcast message=0x1257cb1208
wait_id=95766 seq_num=30232 snap_id=1
wait times: snap=0.000468 sec, exc=0.000468 sec, total=0.000468 sec
wait times: max=infinite
wait counts: calls=1 os=1
occurred after 0.001207 sec of elapsed time
3: waited for ‘SQLNet message from client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95765 seq_num=30231 snap_id=1
wait times: snap=0.052078 sec, exc=0.052078 sec, total=0.052078 sec
wait times: max=infinite
wait counts: calls=0 os=0
occurred after 0.000013 sec of elapsed time
4: waited for 'SQL
Net message to client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95764 seq_num=30230 snap_id=1
wait times: snap=0.000001 sec, exc=0.000001 sec, total=0.000001 sec
wait times: max=infinite
wait counts: calls=0 os=0
occurred after 0.000029 sec of elapsed time
5: waited for ‘log file sync’
buffer#=0xb715, sync scn=0xfa87bc61, =0x0
wait_id=95763 seq_num=30229 snap_id=1
wait times: snap=0.000182 sec, exc=0.000182 sec, total=0.000182 sec
wait times: max=infinite
wait counts: calls=1 os=1
occurred after 0.000050 sec of elapsed time
6: waited for ‘reliable message’
channel context=0x136151d988, channel handle=0x1411545a08, broadcast message=0x1257cb1518
wait_id=95762 seq_num=30228 snap_id=1
wait times: snap=0.000471 sec, exc=0.000471 sec, total=0.000471 sec
wait times: max=infinite
wait counts: calls=1 os=1
occurred after 0.000087 sec of elapsed time
7: waited for ‘reliable message’
channel context=0x136151d988, channel handle=0x1411545a08, broadcast message=0x14115c8a90
wait_id=95761 seq_num=30227 snap_id=1
wait times: snap=0.000448 sec, exc=0.000448 sec, total=0.000448 sec
wait times: max=infinite
wait counts: calls=1 os=1
occurred after 0.001206 sec of elapsed time
8: waited for ‘SQLNet message from client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95760 seq_num=30226 snap_id=1
wait times: snap=0.000892 sec, exc=0.000892 sec, total=0.000892 sec
wait times: max=infinite
wait counts: calls=0 os=0
occurred after 0.000012 sec of elapsed time
9: waited for 'SQL
Net message to client’
driver id=0x54435000, #bytes=0x1, =0x0
wait_id=95759 seq_num=30225 snap_id=1
wait times: snap=0.000002 sec, exc=0.000002 sec, total=0.000002 sec
wait times: max=infinite
wait counts: calls=0 os=0
occurred after 0.000030 sec of elapsed time
Sampled Session History of session 1791 serial 23913

我来答
添加附件
收藏
分享
问题补充
1条回答
默认
最新
有问题吗?

可以用tkprof 命令解析一下这些后缀为.trc 的trace 文件,看着像是对数据库开启trace 没有关掉

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


请输入正文
提交
相关推荐
数据库alert日志
回答 3
你要是之前的alert内容不需要了,就不需要备份alert日志。不过空间够的话,建议备份。
UNDO表空间清理
回答 1
已采纳
查看active状态的segmentSELECTb.usn,tablespacename,segmentname,bytes"ExtentSize",count(extentid)
Oracle全面扫描一个几乎为空的散列聚簇表与全面扫描一个满的散列聚簇表所花的时间一样吗?
回答 1
已采纳
所花的时间是一样的。原因如下:散列聚簇索引表中的数据就是索引,没有物理索引。Oracle取得一行的键值,会使用内部函数或提供的方法计算其散列值,然后使用这个散列值得出数据应该在磁盘上的哪个位置,所以花
对于亿级存量数据的这种 ,除归档转储/分区/分表外 ,Oracle还有其他可选的优化措施吗?
回答 2
物化视图
Oracle 触发器没有生效是写错了吗?
回答 1
beforeinsertorupdate改为afterinsertorupdate
rhel 7.9 11g rac 补丁18370031安装
回答 1
看错误提示,感觉是文件被锁定:1.可以看看文件是否具有读写权限2.看看$ORACLEHOME/.patchstorage文件是否存在,如果没有其它补丁正在执行的话,可以重命名一下,再试试能打补丁不重点
SQLPLUS下如何修改编辑器?
回答 2
已采纳
在ORACLEHOME/sqlplus/admin目录下有个glogin.sql,在其中加入一行:defineeditorvi保存退出在sqlplus命令行直接ed编辑a.sql文件sqlplus/a
运行了一段时间的oracle11g单实例,增加dg,能直接通过配置备库完成数据同步到备库么
回答 2
1.首先检查是否开启了归档,没有开启归档需要重启库开启归档2.开启归档和forcelogging后,通过远程duplicate或者主库备份、备库恢复的方式搭建DG搭建步骤参考https://www.m
oracle如何配置开机自启
回答 1
第一步:$cd$ORACLEHOME/bin$vidbstart编辑dbstart,将ORACLEHOMELISTNER$1修改成ORACLEHOMELISTNER$ORACLEHOME第二步:编辑/
AWR分析报告问题求助:数据库突然变得卡慢,想知道是什么原因引起的
回答 2
enq:TXrowlockcontention:%DBtime40.8%以下sql查询一下锁selects.SID,s.SERIAL,s.MACHINE,s.TYPE,l.TYPE,l.CTIME,l