oracle被一堆insert和update堵死

angle097113 2013-01-14 08:42:59
在生产环境下,几乎每天都会发生一次数据库被几百个insert和update堵死
造成应用中间件死掉
这个时候查看oracle是没有锁的,所以肯定排除掉了死锁的可能性
如下内容为数据库日志(有朋友说是redo过小造成的,但放大到多少合适呢?)

Thu Jan 10 09:53:03 2013
Thread 1 cannot allocate new log, sequence 5024
Checkpoint not complete
Current log# 1 seq# 5023 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5023 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 09:53:46 2013
Thread 1 advanced to log sequence 5024 (LGWR switch)
Current log# 2 seq# 5024 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5024 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 09:55:13 2013
Thread 1 cannot allocate new log, sequence 5025
Checkpoint not complete
Current log# 2 seq# 5024 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5024 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 09:55:51 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 09:55:51 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 09:55:52 2013
Thread 1 advanced to log sequence 5025 (LGWR switch)
Current log# 3 seq# 5025 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5025 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 09:57:05 2013
Thread 1 cannot allocate new log, sequence 5026
Checkpoint not complete
Current log# 3 seq# 5025 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5025 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 09:57:46 2013
Thread 1 advanced to log sequence 5026 (LGWR switch)
Current log# 1 seq# 5026 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5026 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 09:57:47 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 09:59:01 2013
Thread 1 cannot allocate new log, sequence 5027
Checkpoint not complete
Current log# 1 seq# 5026 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5026 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 09:59:40 2013
Thread 1 advanced to log sequence 5027 (LGWR switch)
Current log# 2 seq# 5027 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5027 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:00:53 2013
Thread 1 cannot allocate new log, sequence 5028
Checkpoint not complete
Current log# 2 seq# 5027 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5027 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:01:31 2013
Thread 1 advanced to log sequence 5028 (LGWR switch)
Current log# 3 seq# 5028 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5028 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 10:02:51 2013
Thread 1 cannot allocate new log, sequence 5029
Checkpoint not complete
Current log# 3 seq# 5028 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5028 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 10:03:31 2013
Thread 1 advanced to log sequence 5029 (LGWR switch)
Current log# 1 seq# 5029 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5029 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 10:04:54 2013
Thread 1 cannot allocate new log, sequence 5030
Checkpoint not complete
Current log# 1 seq# 5029 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5029 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 10:05:31 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 10:05:31 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 10:05:31 2013
Thread 1 advanced to log sequence 5030 (LGWR switch)
Current log# 2 seq# 5030 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5030 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:06:51 2013
Thread 1 cannot allocate new log, sequence 5031
Checkpoint not complete
Current log# 2 seq# 5030 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5030 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:07:29 2013
Thread 1 advanced to log sequence 5031 (LGWR switch)
Current log# 3 seq# 5031 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5031 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 10:08:58 2013
Thread 1 cannot allocate new log, sequence 5032
Checkpoint not complete
Current log# 3 seq# 5031 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5031 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
Thu Jan 10 10:09:32 2013
Thread 1 advanced to log sequence 5032 (LGWR switch)
Current log# 1 seq# 5032 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5032 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 10:10:55 2013
Thread 1 cannot allocate new log, sequence 5033
Checkpoint not complete
Current log# 1 seq# 5032 mem# 0: +DATA/gx/onlinelog/group_1.667.802435761
Current log# 1 seq# 5032 mem# 1: +DATA/gx/onlinelog/group_1.647.802435765
Thu Jan 10 10:11:32 2013
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Thu Jan 10 10:11:32 2013
Thread 1 advanced to log sequence 5033 (LGWR switch)
Current log# 2 seq# 5033 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5033 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:12:50 2013
Thread 1 cannot allocate new log, sequence 5034
Checkpoint not complete
Current log# 2 seq# 5033 mem# 0: +DATA/gx/onlinelog/group_2.669.802435767
Current log# 2 seq# 5033 mem# 1: +DATA/gx/onlinelog/group_2.668.802435771
Thu Jan 10 10:13:23 2013
Thread 1 advanced to log sequence 5034 (LGWR switch)
Current log# 3 seq# 5034 mem# 0: +DATA/gx/onlinelog/group_3.267.802435775
Current log# 3 seq# 5034 mem# 1: +DATA/gx/onlinelog/group_3.266.802435779
...全文
533 6 打赏 收藏 转发到动态 举报
写回复
用AI写文章
6 条回复
切换为时间正序
请发表友善的回复…
发表回复
fly518 2013-02-01
  • 打赏
  • 举报
回复
在堵死的时候,看看v$session_wait有哪些等待事件呀,看看awr报告啥的,alert日志没什么有用信息
angle097113 2013-01-17
  • 打赏
  • 举报
回复
引用 2 楼 ruihuahan 的回复:
Thu Jan 10 09:53:03 2013 Thread 1 cannot allocate new log, sequence 5024 Thu Jan 10 09:55:13 2013 Thread 1 cannot allocate new log, sequence 5025 Thu Jan 10 09:57:05 2013 Thread 1 ca……
这个数据库是非归档模式
angle097113 2013-01-17
  • 打赏
  • 举报
回复
目前是三组REDO各50M
linwaterbin 2013-01-17
  • 打赏
  • 举报
回复
引用 4 楼 angle097113 的回复:
引用 2 楼 ruihuahan 的回复:Thu Jan 10 09:53:03 2013
Thread 1 cannot allocate new log, sequence 5024
Thu Jan 10 09:55:13 2013
Thread 1 cannot allocate new log, sequence 5025
Thu Jan 10 09:57……
为什么不设为归档!!??
ruihuahan 2013-01-15
  • 打赏
  • 举报
回复
Thu Jan 10 09:53:03 2013 Thread 1 cannot allocate new log, sequence 5024 Thu Jan 10 09:55:13 2013 Thread 1 cannot allocate new log, sequence 5025 Thu Jan 10 09:57:05 2013 Thread 1 cannot allocate new log, sequence 5026 Thu Jan 10 09:59:01 2013 Thread 1 cannot allocate new log, sequence 5027 ==================================================== 同意楼上,上午9-10点,应该是业务高峰期,日志切换太过频繁,平均 2 分钟。可能都来不及归档。 建议增加日志大小。把日志切换间隔控制在30分钟左右为好。
iqlife 2013-01-14
  • 打赏
  • 举报
回复
问题的确和redo的大小有关,你的redo的情况贴出来 select * from v$log; select * from v$logfile; 一般增加redo大小,默认是50M, 再者增加redo日志组的数量
内容概要:LTK8319是一款单通道H桥有刷直流电机驱动器,工作电压范围为2.5V至12V,支持最高3.9A的峰值电流和2.5A的平均电流驱动能力,适用于小家电、玩具、电子锁、机器人等小型电动设备。该芯片通过两个逻辑输入(INA和INB)控制电机的正转、反转、停止与刹车,并支持PWM调速控制。集成欠压锁定(UVLO)、过温保护(TSD)及自动故障恢复功能,确保系统安全可靠运行。当INA和INB持续为低电平时,芯片进入低功耗休眠模式,显著降低静态功耗。采用ESOP-8封装,符合环保无铅标准。; 适合人群:电子工程师、嵌入式系统开发者、电机控制技术人员,以及从事小型机电产品研发的设计人员;具备基本电路知识和电机控制经验者更佳。; 使用场景及目标:①用于驱动小型有刷直流电机或步进电机的一个绕组,实现精确的方向与速度控制;②适用于电池供电设备中对功耗敏感的应用,利用休眠模式延长续航时间;③在电机启停频繁、负载波动大的场合,发挥其电流控制与保护机制优势,提升系统稳定性。; 阅读建议:此文档提供了详细的电气特性、功能逻辑表、保护机制与时序参数,建议结合典型应用电路进行硬件设计,并重点关注电源去耦电容选型、散热布局及PWM频率设置(不超过100kHz),以确保系统可靠运行。

3,499

社区成员

发帖
与我相关
我的任务
社区描述
Oracle 高级技术相关讨论专区
社区管理员
  • 高级技术社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧